37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 633106 |
Time | |
Date | 200410 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : ric.airport |
State Reference | VA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | M-20 F Executive 21 |
Operating Under FAR Part | Part 91 |
Flight Phase | landing : roll |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : commercial pilot : cfi pilot : multi engine |
Experience | flight time last 90 days : 80 flight time total : 3300 flight time type : 700 |
ASRS Report | 633106 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | incursion : runway non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Inbound, approximately 30 mi from the ric airport, I had selected the ILS runway 16 approach. Potomac approach approved and initiated vectors. I subsequently amended my request to the VOR 20 approach. Potomac approved the runway 20 approach. In hindsight, I can say that the ILS approach was adequately briefed and the VOR approach was not. I had made the VOR approach decision late. I successfully completed the approach segment and broke out in VMC. The tower operator asked if I had the runway and I responded only with my aircraft number. Neither the tower operator nor I articulated a runway number. I had both runways presented to me and I landed on runway 16, the wrong runway. The reasons for this occurrence are: 1) I had not briefed the VOR approach adequately and, I believe, was mentally 'up and locked' with the ILS runway 16, and 2) if either the tower operator or I had called a runway number I think I would have corrected my final approach segment and landed on the correct runway.
Original NASA ASRS Text
Title: M20P PLT EXECUTING VOR RWY 20 APCH LANDED ON RWY 16 AT RIC WITHOUT ATC CLRNC.
Narrative: INBOUND, APPROX 30 MI FROM THE RIC ARPT, I HAD SELECTED THE ILS RWY 16 APCH. POTOMAC APCH APPROVED AND INITIATED VECTORS. I SUBSEQUENTLY AMENDED MY REQUEST TO THE VOR 20 APCH. POTOMAC APPROVED THE RWY 20 APCH. IN HINDSIGHT, I CAN SAY THAT THE ILS APCH WAS ADEQUATELY BRIEFED AND THE VOR APCH WAS NOT. I HAD MADE THE VOR APCH DECISION LATE. I SUCCESSFULLY COMPLETED THE APCH SEGMENT AND BROKE OUT IN VMC. THE TWR OPERATOR ASKED IF I HAD THE RWY AND I RESPONDED ONLY WITH MY ACFT NUMBER. NEITHER THE TWR OPERATOR NOR I ARTICULATED A RWY NUMBER. I HAD BOTH RWYS PRESENTED TO ME AND I LANDED ON RWY 16, THE WRONG RWY. THE REASONS FOR THIS OCCURRENCE ARE: 1) I HAD NOT BRIEFED THE VOR APCH ADEQUATELY AND, I BELIEVE, WAS MENTALLY 'UP AND LOCKED' WITH THE ILS RWY 16, AND 2) IF EITHER THE TWR OPERATOR OR I HAD CALLED A RWY NUMBER I THINK I WOULD HAVE CORRECTED MY FINAL APCH SEGMENT AND LANDED ON THE CORRECT RWY.
Data retrieved from NASA's ASRS site as of July 2007 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.