37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 528489 |
Time | |
Date | 200110 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : sby.airport |
State Reference | MD |
Altitude | msl bound lower : 3700 msl bound upper : 4000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : nhk.tracon |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : private |
Experience | flight time last 90 days : 11.8 flight time total : 430.6 flight time type : 269.8 |
ASRS Report | 528489 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | aircraft equipment problem : less severe altitude deviation : excursion from assigned altitude inflight encounter : weather non adherence : clearance non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : became reoriented flight crew : exited adverse environment flight crew : overcame equipment problem |
Supplementary | |
Problem Areas | Weather Aircraft Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On oct/sun/01, I departed ilg on an IFR flight plan to tgi. In sep/01, I had completed an instrument proficiency check since I had not flown on instruments or on an instrument flight plan for several years. I had trouble identing vors during the flight and periodically activated switches on the navigation/communication control console to monitor VOR identify transmission. Approaching sby, I was working with patuxent (nhk) approach on communication #1 and tacking sby on navigation #1. At about 12 NM from sby, I entered a scattered layer of clouds at 4000 ft, the altitude I had been assigned. The controller cleared me direct tgi and I turned to a new heading. At that point, I tried again to identify sby. In activating the switches on the control console, I inadvertently placed the output switch in the neutral position (neither speaker nor phone) but I did not realize the error. Several mins later, I realized the frequency was silent. I attempted to check in with approach, but received no response. I tried different radios and a different frequency without success. I assumed I had a radio failure and tried to connect a hand-held navigation/communication to an external antenna. While I was distracted by this effort, I lost approximately 300 ft of altitude. When I realized this, I corrected back to 4000 ft and recalled my training to 'fly the airplane.' I was in and out of IMC at this time. I continued to fly heading and altitude until I became clear of IMC. At this point, I attempted to raise approach on communication #1 and discovered the switch setting. Correcting the setting restored contact. I should have given priority to flying the assigned altitude and heading. Troubleshooting the communications problem was secondary. When I realized the correct priorities, I ultimately was able to solve the communications problem. Second, I should have used a more systematic approach to the communication problem. If I had focused on 'what was the last thing I did before losing communication?' I would have reexamined the console settings.
Original NASA ASRS Text
Title: AFTER RECENT INST PROFICIENCY CHK, GA FILES AND FLIES IFR. ENRTE, IMPROPER COM OP CAUSES PARTIAL NORDO SIT.
Narrative: ON OCT/SUN/01, I DEPARTED ILG ON AN IFR FLT PLAN TO TGI. IN SEP/01, I HAD COMPLETED AN INST PROFICIENCY CHK SINCE I HAD NOT FLOWN ON INSTS OR ON AN INST FLT PLAN FOR SEVERAL YEARS. I HAD TROUBLE IDENTING VORS DURING THE FLT AND PERIODICALLY ACTIVATED SWITCHES ON THE NAV/COM CTL CONSOLE TO MONITOR VOR IDENT XMISSION. APCHING SBY, I WAS WORKING WITH PATUXENT (NHK) APCH ON COM #1 AND TACKING SBY ON NAV #1. AT ABOUT 12 NM FROM SBY, I ENTERED A SCATTERED LAYER OF CLOUDS AT 4000 FT, THE ALT I HAD BEEN ASSIGNED. THE CTLR CLRED ME DIRECT TGI AND I TURNED TO A NEW HEADING. AT THAT POINT, I TRIED AGAIN TO IDENT SBY. IN ACTIVATING THE SWITCHES ON THE CTL CONSOLE, I INADVERTENTLY PLACED THE OUTPUT SWITCH IN THE NEUTRAL POS (NEITHER SPEAKER NOR PHONE) BUT I DID NOT REALIZE THE ERROR. SEVERAL MINS LATER, I REALIZED THE FREQ WAS SILENT. I ATTEMPTED TO CHK IN WITH APCH, BUT RECEIVED NO RESPONSE. I TRIED DIFFERENT RADIOS AND A DIFFERENT FREQ WITHOUT SUCCESS. I ASSUMED I HAD A RADIO FAILURE AND TRIED TO CONNECT A HAND-HELD NAV/COM TO AN EXTERNAL ANTENNA. WHILE I WAS DISTRACTED BY THIS EFFORT, I LOST APPROX 300 FT OF ALT. WHEN I REALIZED THIS, I CORRECTED BACK TO 4000 FT AND RECALLED MY TRAINING TO 'FLY THE AIRPLANE.' I WAS IN AND OUT OF IMC AT THIS TIME. I CONTINUED TO FLY HEADING AND ALT UNTIL I BECAME CLR OF IMC. AT THIS POINT, I ATTEMPTED TO RAISE APCH ON COM #1 AND DISCOVERED THE SWITCH SETTING. CORRECTING THE SETTING RESTORED CONTACT. I SHOULD HAVE GIVEN PRIORITY TO FLYING THE ASSIGNED ALT AND HEADING. TROUBLESHOOTING THE COMS PROB WAS SECONDARY. WHEN I REALIZED THE CORRECT PRIORITIES, I ULTIMATELY WAS ABLE TO SOLVE THE COMS PROB. SECOND, I SHOULD HAVE USED A MORE SYSTEMATIC APCH TO THE COM PROB. IF I HAD FOCUSED ON 'WHAT WAS THE LAST THING I DID BEFORE LOSING COM?' I WOULD HAVE REEXAMINED THE CONSOLE SETTINGS.
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.