THE UBER RIDE
Elaine
When using a
ride share service such as Uber or Lyft, one makes the following assumptions:
1.
That the driver can speak and communicate in English.
2.
That the driver reads English.
3.
That the driver can use and understand directions the navigation system
posts.
4.
When going to an airport, the driver knows what an airport terminal
looks like.
Occasionally I use a shuttle service to Burbank Airport
when I travel to the Bay Area alone.
When we were in Boston in May, we used Uber quite successfully. (In retrospect, think it is hard to get lost going
between The Commons and Cambridge.) Having
to go to the Bay Area, I decided to use Uber for my trip to Burbank
Airport. Uber was a couple of dollars
more but I knew that there would be no possibility of a ride share as there
would be with the shuttle service.
BIG MISTAKE!!!
Since my flight was a 2 p.m., calling for an Uber at
11:45 to noon would work. For some reason,
I called earlier--more like 11:30 a.m.
My street is a one block cul de sac and most residents of the city do
not even realize it exists. Therefore,
when I saw the driver come around the block and up my street I felt so positive
regarding my choice.
The car was a much older Hyundai and it was obvious
that the Uber driver (Mario) had just purchased the car and become an
driver. Mario said Burbank Airport like
he was hoping I would change my mind. That should have been clue no. 1. From my house, Burbank Airport is easy--134
freeway to Hollywood Way North and you're at the airport in about a half hour
depending on traffic. At one point, I
almost asked if he knew how to get to the airport. In retrospect, I should have.
Mario turned on to Fair Oaks Avenue and proceeded north
to Pasadena Avenue--not my route of choice but was okay. When we got to the split where there is a
choice of 210 freeway or 134, to my shock, Mario took the 210 Freeway North. Thought that maybe there was traffic on the
134 and he would go to the 210 to the 2 Freeway to the 134 (which I've done) but NO!! After a
considerable drive on the 210 North, we got off the 210 and headed back on the
freeway going south. We made it to the
134 going west so I thought we were on track.
Near the zoo, Mario decides to go on the 5 freeway
south. (For those non-Angelinos, you can
get to the Burbank Airport via the 5 freeway north--not south.) Then we quickly get off the 5 going south and
end up near Forest Lawn Cemetery--an area quite picturesque. Giving Mario the benefit of the doubt, I
figured, again, that there must be a traffic issue and it was traffic avoidance
and we were going to take the scenic route.
As quickly as we got off the freeway, we were back
on--this time going east on the 134 freeway.
(Please remember that we needed to go the 134 West--not East). Then we got off the 134 East and got back on
going west--finally the right direction!!!
But no--Mario decides to take the 5 North.
We're on the 5
north and I knew we really were in trouble when I saw him pass the exit sign with
the plane (signaling the airport) on
it. Instead, we got off an exit
later. At first I saw street signs I
recognized--Hollywood Way, etc.
Then we got into a
construction area. We're driving around
the area--going this way and that, stopping at dead ends over and over
again. At one of the dead ends, I
started to panic. Mario stopped the
car--was this a set up for an assault. After
all, we were in a dead end area with no homes or businesses around. At that point, I figured I could take him
down if he tried anything, since I work out (it was obvious that he didn't) and
we were both about the same height.
Then Mario turns the car around and we end up literally
at the back of Burbank Airport. Mario
looks at me, quite proud, and says "that this is the airport", (after all, we did see planes). At that point, I realized that Mario had
never been to an airport, much less ever been on a plane. At that point, Mario finally admitted that he
was having a "problem" with his navigation system. In plain English, he could not follow the
navigation directions; therefore, the constant on and off the
freeway.
Now what do I do--call for
an Uber and get Mario again.
Thank God for cell phones and the Maps icon. Typed in Burbank Airport and found that we
were 1.5 miles from the entrance--at the back.
Put the app on speaker and realized he still couldn't navigate. He literally could not understand
directions. If we needed to go left, he looked
and I pointed in that direction. This
went on for 1.5 miles including through the construction area we'd been through
at least 3 times until we finally got to the front of the airport. Then, instead of taking the road to the terminals
(It was obvious he could not read or comprehend English), we go to the car
rental return route. That mistake was easy
because he just backed out to the correct road.
Finally, after over an hour for what should have been an uneventful 30
minute drive, we were at the terminal.
Thanked Mario and got in to the terminal as the 1 p.m.
flight to Oakland was airborne. Thank
God I was on the 2 p.m. flight.!!! While
we were waiting to board, I was talking to people in line about my ordeal. One woman said that she was in an Uber and
the driver literally blamed her because he tried to get on the freeway via an
off ramp.
Doesn't end there. Get my credit card statement with the charge
for my Uber ride not $31.20 but $46.60.
I was charged an extra $15 for the time we spent driving around. Called the credit card company and explained
what happened. $15 was deducted from my
statement.
Scam--since this trip,
I've read that there is an Uber scam with their drivers taking unnecessary time
or routes to increase their trip receipts.
So Beware!!! and beware of the Marios of this world who are Uber
drivers!!!