37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 785944 |
Time | |
Date | 200805 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : sna.airport |
State Reference | CA |
Altitude | msl bound lower : 3000 msl bound upper : 4000 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : sct.tracon |
Operator | general aviation : personal |
Make Model Name | M-20 Series Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Navigation In Use | other other |
Flight Phase | descent : approach |
Route In Use | arrival : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : multi engine pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 30 flight time total : 2500 flight time type : 50 |
ASRS Report | 785944 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | aircraft equipment problem : critical non adherence : published procedure non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : separated traffic flight crew : overcame equipment problem flight crew : overrode automation |
Supplementary | |
Problem Areas | Aircraft Flight Crew Human Performance |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation |
Narrative:
While being vectored to final; I flew through the localizer on 2 occasions. The plane has a garmin G1000 system. I was receiving incorrect sensing; and ATC gave me an emergency evasive turn order. I executed this without delay; but I was somewhat shaken that this occurred while in IMC. I was busy resetting my altitude and heading functions on the G1000 when I finally figured out my problem. The G1000 automatically switches to the localizer frequency (111.75) and this is an approach that I have flown weekly for at least 2 1/2 yrs. On this particular day; however; the switch was to 111.70. I still have no idea why the switch was not to 111.75. Once I figured out the problem; the approach went without incident. I am going to make sure this never happens again by going into the menu system of the G1000 and turning off the automatic-switch function. This will require me to manually tune in the frequency when I switch to the v-loc display on the panel.
Original NASA ASRS Text
Title: M20 PLT RECORDS TWO TRACK DEVIATIONS RELATIVE TO THE LOCALIZER BY WHICH HE WAS CLRED. DISCOVERS AVIONICS HAD FAILED TO AUTOMATICALLY SWITCH TO LOC FREQ AS EXPECTED.
Narrative: WHILE BEING VECTORED TO FINAL; I FLEW THROUGH THE LOC ON 2 OCCASIONS. THE PLANE HAS A GARMIN G1000 SYS. I WAS RECEIVING INCORRECT SENSING; AND ATC GAVE ME AN EMER EVASIVE TURN ORDER. I EXECUTED THIS WITHOUT DELAY; BUT I WAS SOMEWHAT SHAKEN THAT THIS OCCURRED WHILE IN IMC. I WAS BUSY RESETTING MY ALT AND HDG FUNCTIONS ON THE G1000 WHEN I FINALLY FIGURED OUT MY PROB. THE G1000 AUTOMATICALLY SWITCHES TO THE LOC FREQ (111.75) AND THIS IS AN APCH THAT I HAVE FLOWN WEEKLY FOR AT LEAST 2 1/2 YRS. ON THIS PARTICULAR DAY; HOWEVER; THE SWITCH WAS TO 111.70. I STILL HAVE NO IDEA WHY THE SWITCH WAS NOT TO 111.75. ONCE I FIGURED OUT THE PROB; THE APCH WENT WITHOUT INCIDENT. I AM GOING TO MAKE SURE THIS NEVER HAPPENS AGAIN BY GOING INTO THE MENU SYS OF THE G1000 AND TURNING OFF THE AUTO-SWITCH FUNCTION. THIS WILL REQUIRE ME TO MANUALLY TUNE IN THE FREQ WHEN I SWITCH TO THE V-LOC DISPLAY ON THE PANEL.
Data retrieved from NASA's ASRS site as of May 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.