37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1021515 |
Time | |
Date | 201207 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | LAX.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Cessna Single Piston Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 129 Flight Crew Total 1171 Flight Crew Type 102 |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy |
Narrative:
This was my first time overflying lax. I asked smo ground prior to departure if it would be possible to overfly at lax at 3;500 ft. The ground controller said it was possible; and that I should expect to make a climbing right 270 at the shoreline after departure from runway 21; and then cross over the smo VOR before proceeding over lax. After departure; tower instructed me to proceed to the shoreline; and then make a climbing right 270 to 2;500 MSL. I climbed to 2;500; but then tower instructed me to climb to 3;500 and change frequencies. I initiated my climb and contacted lax tower as is required to fly the lax mini route.upon contacting lax tower and reporting my altitude; tower told me I was above his altitude and to contact sct approach on another frequency to overfly lax. After checking in with sct at 3;500 for the mini route; they informed me that I needed to talk to tower to fly that route and handed me back to lax. I reported back in with lax tower at 3;500 for the mini route; and tower said 'you will have to descend to 2;500 before I can clear you through the class bravo for the mini route.' I descended as directed.I was expecting a discrete beacon code and a bravo clearance. However; as I neared the edge of the class bravo airspace; tower hadn't told me anything. I figured that maybe because this was a special VFR transition route; a discrete code was not required. This made me uncomfortable; so just prior to entering the class B airspace I called lax tower one more time: 'tower; this is my first time flying this route. Just want to confirm what I'm doing is ok.' tower responded; 'affirmative; just keep flying that heading and hold that altitude. You're doing great.' after hearing that; I guessed I must be okay; and continued through the class B airspace over the top of lax at 2;500. Shortly after crossing over midfield at lax; tower advised; 'you are one mile from exiting class B airspace; radar services are terminated; squawk VFR...oops; looks like I never gave you a code. That's alright. Squawk VFR and contact hawthorne tower.' I responded; 'switching to hawthorne tower; good day.'I was very uncomfortable through the whole ordeal; but after asking tower if I was doing everything correctly and being told 'affirmative;' I was convinced that everything was going fine. However; upon being given the frequency change just prior to exiting class B airspace and having the controller admit to forgetting to assign a beacon code; I became very flustered and forgot to check on with hawthorne tower. Hawthorne tower called about a minute later; I responded; and the rest of the flight went smoothly.I think this whole event could have been avoided if there wasn't the confusion on what altitude I needed to climb initially to fly the route. Had either the ground controller or tower controller at smo told me I needed to be at 2;500 rather than 3;500 for the route; I would not have had to make the rapid descent to 2;500. If I hadn't had to make that descent; lax tower would have been able to clear me for the route 4-5 miles earlier and would have had more time to remember to give me a bravo clearance and discrete code. I believe the whole event was due to a breakdown in communications from all parties involved.
Original NASA ASRS Text
Title: A small light aircraft pilot attempting his first north to south crossing through the LAX Class B after taking off from SMO met with multiple conflicting ATC communications and clearances; ultimately confusing him to the point he forgot to contact Hawthorne Tower after completing the passage.
Narrative: This was my first time overflying LAX. I asked SMO Ground prior to departure if it would be possible to overfly at LAX at 3;500 FT. The Ground Controller said it was possible; and that I should expect to make a climbing right 270 at the shoreline after departure from Runway 21; and then cross over the SMO VOR before proceeding over LAX. After departure; Tower instructed me to proceed to the shoreline; and then make a climbing right 270 to 2;500 MSL. I climbed to 2;500; but then Tower instructed me to climb to 3;500 and change frequencies. I initiated my climb and contacted LAX Tower as is required to fly the LAX mini route.Upon contacting LAX Tower and reporting my altitude; Tower told me I was above his altitude and to contact SCT Approach on another frequency to overfly LAX. After checking in with SCT at 3;500 for the mini route; they informed me that I needed to talk to Tower to fly that route and handed me back to LAX. I reported back in with LAX Tower at 3;500 for the mini route; and Tower said 'you will have to descend to 2;500 before I can clear you through the Class Bravo for the mini route.' I descended as directed.I was expecting a discrete beacon code and a Bravo clearance. However; as I neared the edge of the Class Bravo airspace; Tower hadn't told me anything. I figured that maybe because this was a special VFR transition route; a discrete code was not required. This made me uncomfortable; so just prior to entering the Class B airspace I called LAX Tower one more time: 'Tower; this is my first time flying this route. Just want to confirm what I'm doing is OK.' Tower responded; 'Affirmative; just keep flying that heading and hold that altitude. You're doing great.' After hearing that; I guessed I must be okay; and continued through the Class B airspace over the top of LAX at 2;500. Shortly after crossing over midfield at LAX; Tower advised; 'you are one mile from exiting Class B airspace; radar services are terminated; squawk VFR...oops; looks like I never gave you a code. That's alright. Squawk VFR and contact Hawthorne Tower.' I responded; 'Switching to Hawthorne Tower; good day.'I was very uncomfortable through the whole ordeal; but after asking Tower if I was doing everything correctly and being told 'affirmative;' I was convinced that everything was going fine. However; upon being given the frequency change just prior to exiting Class B airspace and having the Controller admit to forgetting to assign a beacon code; I became very flustered and forgot to check on with Hawthorne Tower. Hawthorne Tower called about a minute later; I responded; and the rest of the flight went smoothly.I think this whole event could have been avoided if there wasn't the confusion on what altitude I needed to climb initially to fly the route. Had either the Ground Controller or Tower Controller at SMO told me I needed to be at 2;500 rather than 3;500 for the route; I would not have had to make the rapid descent to 2;500. If I hadn't had to make that descent; LAX Tower would have been able to clear me for the route 4-5 miles earlier and would have had more time to remember to give me a Bravo clearance and discrete code. I believe the whole event was due to a breakdown in communications from all parties involved.
Data retrieved from NASA's ASRS site as of July 2013 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.