37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 173065 |
Time | |
Date | 199103 |
Day | Mon |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : w10 |
State Reference | VA |
Altitude | msl bound lower : 3000 msl bound upper : 3000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : iad |
Operator | general aviation : instructional |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | descent : approach |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : private |
Experience | flight time last 90 days : 31 flight time total : 237 flight time type : 100 |
ASRS Report | 173065 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | non adherence : clearance non adherence : far other anomaly other other anomaly other other spatial deviation |
Independent Detector | other controllera other other : unspecified cockpit |
Resolutory Action | flight crew : became reoriented flight crew : overcame equipment problem |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
During an IFR flight plan, on multiple approachs to local airports to keep current, I was preparing to enter a published hold after going missed and requested an ILS to hometown field. I was immediately given a vector and after turning to it, began to set up for the ILS. Two intxns are used to identify descent points and I dialed in the ILS frequency. I was still too far out to identification it, so I let it be and studied the plate. I was then given another vector to fly heading 02O degree. This is a standard vector, very familiar to me for intercepting the localizer. After a few mins on this heading, I then tried to identification the localizer. I was not wearing a headset as I normally do and the approach controller's voice was blaring over the morse identification for the localizer. I turned the volume down on the radio and turned up the volume for identify of the localizer. After a positive identification I turned down the navigation volume but neglected to turn the radio with the controller back up. Dulles approach was on communication 2 and the unicom was on communication 1. With the communication 2 turned down, I could not hear the dulles controller, but because I could hear chatter from unicom on communication 1, I did not recognize that communication 2 was silent. After blazing through the localizer, I began to investigate why I had not heard from the controller. My first reaction was to try squelch and then volume, whence my mistake was revealed to me. The controller was issuing a traffic callout to another aircraft about 'that small aircraft that's not talking to anyone' (his words). At the next transmission break I announced myself as on frequency and was issued a 180 degree turn. Dulles approach: 'ok sir, you've wandered into my approach path turn left 200 degree, and ah, as far as I'm concerned your practice approachs are over tonight, and you can plan a full stop on this ILS.' the ILS and landing proceeded west/O incident. On the ground, I called the approach supervisor and apologized for the mistake. Moral: when tuning navaids do not turn your communications all the way down. A clearance takes only a few seconds to be given.
Original NASA ASRS Text
Title: PLT OF SMA PRACTICING INSTRUMENT FLYING LOST COM WITH TRACON. OVERSHOT LOCALIZER AND PENETRATED TCA WITH TRAFFIC CONFLICT.
Narrative: DURING AN IFR FLT PLAN, ON MULTIPLE APCHS TO LCL ARPTS TO KEEP CURRENT, I WAS PREPARING TO ENTER A PUBLISHED HOLD AFTER GOING MISSED AND REQUESTED AN ILS TO HOMETOWN FIELD. I WAS IMMEDIATELY GIVEN A VECTOR AND AFTER TURNING TO IT, BEGAN TO SET UP FOR THE ILS. TWO INTXNS ARE USED TO IDENT DSNT POINTS AND I DIALED IN THE ILS FREQ. I WAS STILL TOO FAR OUT TO ID IT, SO I LET IT BE AND STUDIED THE PLATE. I WAS THEN GIVEN ANOTHER VECTOR TO FLY HDG 02O DEG. THIS IS A STANDARD VECTOR, VERY FAMILIAR TO ME FOR INTERCEPTING THE LOC. AFTER A FEW MINS ON THIS HDG, I THEN TRIED TO ID THE LOC. I WAS NOT WEARING A HEADSET AS I NORMALLY DO AND THE APCH CTLR'S VOICE WAS BLARING OVER THE MORSE ID FOR THE LOC. I TURNED THE VOLUME DOWN ON THE RADIO AND TURNED UP THE VOLUME FOR IDENT OF THE LOC. AFTER A POSITIVE ID I TURNED DOWN THE NAV VOLUME BUT NEGLECTED TO TURN THE RADIO WITH THE CTLR BACK UP. DULLES APCH WAS ON COM 2 AND THE UNICOM WAS ON COM 1. WITH THE COM 2 TURNED DOWN, I COULD NOT HEAR THE DULLES CTLR, BUT BECAUSE I COULD HEAR CHATTER FROM UNICOM ON COM 1, I DID NOT RECOGNIZE THAT COM 2 WAS SILENT. AFTER BLAZING THROUGH THE LOC, I BEGAN TO INVESTIGATE WHY I HAD NOT HEARD FROM THE CTLR. MY FIRST REACTION WAS TO TRY SQUELCH AND THEN VOLUME, WHENCE MY MISTAKE WAS REVEALED TO ME. THE CTLR WAS ISSUING A TFC CALLOUT TO ANOTHER ACFT ABOUT 'THAT SMA THAT'S NOT TALKING TO ANYONE' (HIS WORDS). AT THE NEXT XMISSION BREAK I ANNOUNCED MYSELF AS ON FREQ AND WAS ISSUED A 180 DEG TURN. DULLES APCH: 'OK SIR, YOU'VE WANDERED INTO MY APCH PATH TURN L 200 DEG, AND AH, AS FAR AS I'M CONCERNED YOUR PRACTICE APCHS ARE OVER TONIGHT, AND YOU CAN PLAN A FULL STOP ON THIS ILS.' THE ILS AND LNDG PROCEEDED W/O INCIDENT. ON THE GND, I CALLED THE APCH SUPVR AND APOLOGIZED FOR THE MISTAKE. MORAL: WHEN TUNING NAVAIDS DO NOT TURN YOUR COMS ALL THE WAY DOWN. A CLRNC TAKES ONLY A FEW SECS TO BE GIVEN.
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.