|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1801 To 2400|
|Locale Reference||airport : jan|
|Controlling Facilities||tracon : jan|
tower : pdx
|Operator||general aviation : instructional|
|Make Model Name||Small Aircraft, Low Wing, 1 Eng, Fixed Gear|
|Flight Phase||descent : approach|
landing : missed approach
|Function||flight crew : single pilot|
|Qualification||pilot : private|
pilot : instrument
|Experience||flight time last 90 days : 10|
flight time total : 700
flight time type : 50
|Affiliation||government : faa|
|Function||controller : approach|
|Qualification||controller : radar|
|Anomaly||aircraft equipment problem : less severe|
non adherence : clearance
non adherence : published procedure
|Independent Detector||other flight crewa|
|Resolutory Action||controller : provided flight assist|
|Primary Problem||Flight Crew Human Performance|
|Air Traffic Incident||Pilot Deviation|
The first night ILS approach landed in a missed approach because the dg started rotating during the approach. I am not skilled enough to track the localizer with the standard wet compass. During the missed approach my radios developed a loud hiss so that I essentially could not hear anything the facility (tower or approach controller) was saying to me. I believe they could hear me ok. After 1-3 mins I determined that by resetting the switches on the audio panel normal communication was reestablished. (I assume that I had inadvertently 'touched' the audio panel during the approach, possibly to rechk the mkr bcn receiver, and 'turned on' one or more of the audio switches for the left navigation rcvrs during the process. The truth is that I don't know with certainty how I created the hissing that complicated the missed approach procedure). Tower personnel became aware that I was experiencing problems (I acknowledged this to them: climb, confess, communicate, fly the airplane) and one person seemed to give his total, absolute attention throughout the second ILS approach and touchdown phases. The dg was 'stable' during the approach phase (from the OM to touchdown).
Original NASA ASRS Text
Title: HAS TO MISS AN APCH BECAUSE OF INOP EQUIP ON THE ACFT.
Narrative: THE FIRST NIGHT ILS APCH LANDED IN A MISSED APCH BECAUSE THE DG STARTED ROTATING DURING THE APCH. I AM NOT SKILLED ENOUGH TO TRACK THE LOC WITH THE STANDARD WET COMPASS. DURING THE MISSED APCH MY RADIOS DEVELOPED A LOUD HISS SO THAT I ESSENTIALLY COULD NOT HEAR ANYTHING THE FACILITY (TWR OR APCH CTLR) WAS SAYING TO ME. I BELIEVE THEY COULD HEAR ME OK. AFTER 1-3 MINS I DETERMINED THAT BY RESETTING THE SWITCHES ON THE AUDIO PANEL NORMAL COM WAS REESTABLISHED. (I ASSUME THAT I HAD INADVERTENTLY 'TOUCHED' THE AUDIO PANEL DURING THE APCH, POSSIBLY TO RECHK THE MKR BCN RECEIVER, AND 'TURNED ON' ONE OR MORE OF THE AUDIO SWITCHES FOR THE L NAV RCVRS DURING THE PROCESS. THE TRUTH IS THAT I DON'T KNOW WITH CERTAINTY HOW I CREATED THE HISSING THAT COMPLICATED THE MISSED APCH PROC). TWR PERSONNEL BECAME AWARE THAT I WAS EXPERIENCING PROBLEMS (I ACKNOWLEDGED THIS TO THEM: CLB, CONFESS, COMMUNICATE, FLY THE AIRPLANE) AND ONE PERSON SEEMED TO GIVE HIS TOTAL, ABSOLUTE ATTN THROUGHOUT THE SECOND ILS APCH AND TOUCHDOWN PHASES. THE DG WAS 'STABLE' DURING THE APCH PHASE (FROM THE OM TO TOUCHDOWN).
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.