37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 470890 |
Time | |
Date | 200004 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : esl.vortac |
State Reference | VA |
Altitude | msl single value : 6000 |
Environment | |
Flight Conditions | Mixed |
Aircraft 1 | |
Controlling Facilities | artcc : zdc.artcc |
Operator | general aviation : personal |
Make Model Name | PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Navigation In Use | other vortac |
Flight Phase | cruise : level |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 35 flight time total : 2121 flight time type : 83 |
ASRS Report | 470890 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Events | |
Anomaly | non adherence : far non adherence : published procedure other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | other |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
Anticipating approach to iad, I began selecting expected frequencys in the 2 communication radios. When I heard iad tower controller, I realized I had removed ZDC frequency while still under its control. Luckily, I remembered the correct frequency, put it back in and called ZDC, 'level at 6000 ft.' center's immediate reply was 'roger, contact dulles approach, 'leading me to believe he'd been trying to contact me with that change while I'd been off his frequency. How it happened: I had used communication #1 radio throughout the 2 hour trip from ohio, except for ZDC which was weak on communication #1. So now ZDC was in communication #2, when I started to dial in expected frequencys for the approach and landing, forgetting that the active frequency was no longer on communication #1. How to do better: before ever selecting in a new frequency, verify which is the active frequency.
Original NASA ASRS Text
Title: PLT INADVERTENTLY LEAVES FREQ WHILE IN CTL OF ZDC.
Narrative: ANTICIPATING APCH TO IAD, I BEGAN SELECTING EXPECTED FREQS IN THE 2 COM RADIOS. WHEN I HEARD IAD TWR CTLR, I REALIZED I HAD REMOVED ZDC FREQ WHILE STILL UNDER ITS CTL. LUCKILY, I REMEMBERED THE CORRECT FREQ, PUT IT BACK IN AND CALLED ZDC, 'LEVEL AT 6000 FT.' CTR'S IMMEDIATE REPLY WAS 'ROGER, CONTACT DULLES APCH, 'LEADING ME TO BELIEVE HE'D BEEN TRYING TO CONTACT ME WITH THAT CHANGE WHILE I'D BEEN OFF HIS FREQ. HOW IT HAPPENED: I HAD USED COM #1 RADIO THROUGHOUT THE 2 HR TRIP FROM OHIO, EXCEPT FOR ZDC WHICH WAS WEAK ON COM #1. SO NOW ZDC WAS IN COM #2, WHEN I STARTED TO DIAL IN EXPECTED FREQS FOR THE APCH AND LNDG, FORGETTING THAT THE ACTIVE FREQ WAS NO LONGER ON COM #1. HOW TO DO BETTER: BEFORE EVER SELECTING IN A NEW FREQ, VERIFY WHICH IS THE ACTIVE FREQ.
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.