37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1511535 |
Time | |
Date | 201801 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | TOA.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Direct |
Flight Plan | VFR |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Instrument |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
While in route from to toa; I checked with the tower 8 miles out 3;000 ft with the ATIS and requesting runway 29R. I was immediately given instructions for traffic deviations which were followed. This deviation placed me 3 miles and approximately 3;000 ft to the south of the field. Tower asked if I can enter a left base for what I believe was for my original intended runway of 29R. I responded yes and repeated runway 29R. There was a lot of traffic going on and similar call signs as my aircraft. At one point; I believe there was an aircraft assigned an ILS runway 29L (doesn't exist) prompting added confusion and another pilot communicating.I believe the tower was overwhelmed. Upon my 1/2 mile final to runway 29R I heard tower give another aircraft a landing clearance calling them #1 - which was impossible as I was just about to land.upon calling the tower. I was told I was to use runway 29L and there was confusion. I was told that I did confirm 29R via audio tape review and tower failed to correct. I never heard 29L just a left base to what I believe was my original request.I'm filing this report as a precautionary measure to document the incident. Tower said the incident will go for further review. Since the last communication was clear that I intended to use runway 29R; I'm not sure what could of been done differently during the high volume of calls - other than the controller requesting other pilots to hold off on communicating until my landing clearance was corrected - since it was determined I did in fact confirm runway 29R as my expected runway.
Original NASA ASRS Text
Title: General Aviation Pilot reported having difficulties landing VFR at a congested airport in a major city environment.
Narrative: While in route from to TOA; I checked with the tower 8 miles out 3;000 ft with the ATIS and requesting Runway 29R. I was immediately given instructions for traffic deviations which were followed. This deviation placed me 3 miles and approximately 3;000 ft to the south of the field. Tower asked if I can enter a left Base for what I believe was for my original intended Runway of 29R. I responded yes and repeated Runway 29R. There was a lot of traffic going on and similar call signs as my aircraft. At one point; I believe there was an aircraft assigned an ILS Runway 29L (doesn't exist) prompting added confusion and another pilot communicating.I believe the tower was overwhelmed. Upon my 1/2 mile final to Runway 29R I heard Tower give another aircraft a landing clearance calling them #1 - which was impossible as I was just about to land.Upon calling the tower. I was told I was to use Runway 29L and there was confusion. I was told that I did confirm 29R via audio tape review and tower failed to correct. I never heard 29L just a Left Base to what I believe was my original request.I'm filing this report as a precautionary measure to document the incident. Tower said the incident will go for further review. Since the last communication was clear that I intended to use Runway 29R; I'm not sure what could of been done differently during the high volume of calls - other than the controller requesting other pilots to hold off on communicating until my landing clearance was corrected - since it was determined I did in fact confirm Runway 29R as my expected runway.
Data retrieved from NASA's ASRS site 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.