37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 649470 |
Time | |
Date | 200503 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : eky.airport |
State Reference | AL |
Altitude | msl bound lower : 1100 msl bound upper : 3000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : bhm.tracon tower : iad.tower |
Operator | general aviation : corporate |
Make Model Name | SA-226 TC Metro II |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | descent : approach |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : single pilot oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 60 flight time total : 18500 flight time type : 400 |
ASRS Report | 649470 |
Events | |
Anomaly | aircraft equipment problem : critical altitude deviation : excursion from assigned altitude non adherence : published procedure non adherence : clearance non adherence : far |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : diverted to another airport flight crew : executed missed approach |
Consequence | Other |
Supplementary | |
Problem Areas | Company Flight Crew Human Performance Aircraft |
Primary Problem | Flight Crew Human Performance |
Narrative:
GPS 23 approach; eky; began descent to minimums before reaching FAF due to difficulty loading approach into a 'loaner' GPS unit installed in the aircraft. This unit is compatible with our normal installation; but a different model. I don't believe I got approach activated in time; therefore; misidented the FAF. Realizing an error; I executed a missed approach at that point. Diverted to bhm and the ILS (GS OTS at eky). I have never had this problem when making GPS approachs with my normal unit. Our GPS is currently being modified and should be back in airplane in a few days. I may be old fashioned; but I think that due to the number of steps and complexity required to set up a GPS approach; controllers should verify that the pilot is set up and verify name of FAF. Procedures are sometimes confusing and planforms cluttered. Names of waypoints also confusing.
Original NASA ASRS Text
Title: AN SA226 PLT; UTILIZING A REPLACEMENT GPS FMC UNIT; MISPROGRAMMED THE APCH THEN EXECUTED A MISSED APCH FOLLOWING AN EARLY DSCNT.
Narrative: GPS 23 APCH; EKY; BEGAN DSCNT TO MINIMUMS BEFORE REACHING FAF DUE TO DIFFICULTY LOADING APCH INTO A 'LOANER' GPS UNIT INSTALLED IN THE ACFT. THIS UNIT IS COMPATIBLE WITH OUR NORMAL INSTALLATION; BUT A DIFFERENT MODEL. I DON'T BELIEVE I GOT APCH ACTIVATED IN TIME; THEREFORE; MISIDENTED THE FAF. REALIZING AN ERROR; I EXECUTED A MISSED APCH AT THAT POINT. DIVERTED TO BHM AND THE ILS (GS OTS AT EKY). I HAVE NEVER HAD THIS PROB WHEN MAKING GPS APCHS WITH MY NORMAL UNIT. OUR GPS IS CURRENTLY BEING MODIFIED AND SHOULD BE BACK IN AIRPLANE IN A FEW DAYS. I MAY BE OLD FASHIONED; BUT I THINK THAT DUE TO THE NUMBER OF STEPS AND COMPLEXITY REQUIRED TO SET UP A GPS APCH; CTLRS SHOULD VERIFY THAT THE PLT IS SET UP AND VERIFY NAME OF FAF. PROCS ARE SOMETIMES CONFUSING AND PLANFORMS CLUTTERED. NAMES OF WAYPOINTS ALSO CONFUSING.
Data retrieved from NASA's ASRS site as of January 2009 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.