37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 492995 |
Time | |
Date | 200011 |
Day | Sun |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : rdu.airport |
State Reference | NC |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | IMC |
Weather Elements | Snow |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tower : rdu.tower |
Operator | general aviation : corporate |
Make Model Name | Merlin III |
Operating Under FAR Part | Part 91 |
Navigation In Use | ils localizer & glide slope : 5r |
Flight Phase | descent : approach landing : roll |
Route In Use | approach : instrument precision |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : cfi pilot : commercial pilot : instrument pilot : multi engine |
Experience | flight time last 90 days : 124 flight time total : 1360 flight time type : 198 |
ASRS Report | 492995 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | aircraft equipment problem : less severe inflight encounter : weather non adherence : published procedure non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued advisory none taken : detected after the fact |
Supplementary | |
Problem Areas | Weather Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
After being vectored to the runway 5R localizer and cleared for the approach, we intercepted the localizer and GS, contacted the tower on 127.45 (the only tower frequency in use). We were cleared to land on runway 5R. We completed the before landing checklist and I began reading altitude to the decision ht. The pilot stated he had a navigation flag on his HSI and asked if I was showing the same. I confirmed a navigation flag on my HSI. We checked the localizer frequency was correct and it was. At this point we had the airport in sight but were disoriented in our location due to the localizer failure, reduced visibility and nighttime conditions. We contacted the tower and told them of our navigation flag to see if they were showing a failure of the ILS. The tower asked if we had the airport in sight, we responded affirmative, and they responded cleared to land. We completed the approach visually and landed. After taxiing clear of the runway, the tower told us we were on the left side and to contact ground control. What caused the problem was the disbelief that we had lost the localizer. Initially, we thought it was temporary due to snow plows or ground equipment blocking the localizer antenna because the GS appeared to be functioning. Secondly, we were relying on the tower to report any discrepancy of the navigation equipment on the ground to us. Our third thought was that we had a total navigation failure with deteriorating WX limiting our options to complete the flight which had just happened to an associate of ours. At first indication of the localizer failure, we should have acted and declared missed approach instead of trying to troubleshoot the navigation indication. Then we could have tried to determine the problem and a course of action to complete the flight. We should have reacted just as taught from the beginning of instrument training and how to handle such a situation.
Original NASA ASRS Text
Title: SWIII ENCOUNTERS WX AND EQUIP PROB AND LANDS ON WRONG, PARALLEL RWY AT RDU.
Narrative: AFTER BEING VECTORED TO THE RWY 5R LOC AND CLRED FOR THE APCH, WE INTERCEPTED THE LOC AND GS, CONTACTED THE TWR ON 127.45 (THE ONLY TWR FREQ IN USE). WE WERE CLRED TO LAND ON RWY 5R. WE COMPLETED THE BEFORE LNDG CHKLIST AND I BEGAN READING ALT TO THE DECISION HT. THE PLT STATED HE HAD A NAV FLAG ON HIS HSI AND ASKED IF I WAS SHOWING THE SAME. I CONFIRMED A NAV FLAG ON MY HSI. WE CHKED THE LOC FREQ WAS CORRECT AND IT WAS. AT THIS POINT WE HAD THE ARPT IN SIGHT BUT WERE DISORIENTED IN OUR LOCATION DUE TO THE LOC FAILURE, REDUCED VISIBILITY AND NIGHTTIME CONDITIONS. WE CONTACTED THE TWR AND TOLD THEM OF OUR NAV FLAG TO SEE IF THEY WERE SHOWING A FAILURE OF THE ILS. THE TWR ASKED IF WE HAD THE ARPT IN SIGHT, WE RESPONDED AFFIRMATIVE, AND THEY RESPONDED CLRED TO LAND. WE COMPLETED THE APCH VISUALLY AND LANDED. AFTER TAXIING CLR OF THE RWY, THE TWR TOLD US WE WERE ON THE L SIDE AND TO CONTACT GND CTL. WHAT CAUSED THE PROB WAS THE DISBELIEF THAT WE HAD LOST THE LOC. INITIALLY, WE THOUGHT IT WAS TEMPORARY DUE TO SNOW PLOWS OR GND EQUIP BLOCKING THE LOC ANTENNA BECAUSE THE GS APPEARED TO BE FUNCTIONING. SECONDLY, WE WERE RELYING ON THE TWR TO RPT ANY DISCREPANCY OF THE NAV EQUIP ON THE GND TO US. OUR THIRD THOUGHT WAS THAT WE HAD A TOTAL NAV FAILURE WITH DETERIORATING WX LIMITING OUR OPTIONS TO COMPLETE THE FLT WHICH HAD JUST HAPPENED TO AN ASSOCIATE OF OURS. AT FIRST INDICATION OF THE LOC FAILURE, WE SHOULD HAVE ACTED AND DECLARED MISSED APCH INSTEAD OF TRYING TO TROUBLESHOOT THE NAV INDICATION. THEN WE COULD HAVE TRIED TO DETERMINE THE PROB AND A COURSE OF ACTION TO COMPLETE THE FLT. WE SHOULD HAVE REACTED JUST AS TAUGHT FROM THE BEGINNING OF INST TRAINING AND HOW TO HANDLE SUCH A SIT.
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.