 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
The pct controller alerts a BE40 flight crew that had tuned in the wrong localizer frequency for runway 19R versus runway 19L iad, va.
| Attributes | |
| ACN | 597716 |
| Time | |
| Date | 200310 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : iad.airport |
| State Reference | VA |
| Altitude | msl single value : 6000 |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : pct.tracon |
| Operator | general aviation : corporate |
| Make Model Name | Beechjet 400 |
| Operating Under FAR Part | Part 91 |
| Navigation In Use | ils localizer & glide slope : 19r ils other localizer |
| Flight Phase | descent : approach |
| Route In Use | approach : instrument precision |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : corporate |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : cfi pilot : atp |
| Experience | flight time last 90 days : 125 flight time total : 3865 flight time type : 1600 |
| ASRS Report | 597716 |
| Person 2 | |
| Affiliation | company : corporate |
| Function | flight crew : first officer |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 150 flight time total : 4500 flight time type : 900 |
| ASRS Report | 597568 |
| Events | |
| Anomaly | non adherence : clearance other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance controller : issued advisory flight crew : returned to original clearance flight crew : became reoriented |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance Environmental Factor |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
On arrival to washington-dulles airport (iad), we were given a heading to intercept the runway 19L localizer and track inbound. My copilot mistakenly entered the localizer frequency for runway 19R. We intercepted and tracked the runway 19R localizer. After a few mins, ATC asked us which runway we had requested. We told them runway 19L. We were then given a heading and told to intercept the runway 19L localizer. Nothing more was said by ATC about the error. I believe the causes of this error were crew fatigue and lack of CRM. We were both still very tired from multiple time zone changes as well as varying starting and stopping duty days. Our CRM failed because we did not both verify the correct localizer frequency for the approach. We do not normally brief and verify frequencys if we are expecting a visual approach to the airport. We have since started doing a full briefing of the ILS or other instrument approach we are using for guidance even if we are expecting a visual approach. Supplemental information from acn 597568: normally, both crew members verify all navigation frequencys. But on this leg, both crew members were fatigued. The frequencys were not verified by the other pilot, nor did I ask him to verify them. CRM broke down due to the fatigue of both pilots. The frequency was not idented, due to the VFR conditions at the airport.
Original NASA ASRS Text
Title: THE PCT CTLR ALERTS A BE40 FLT CREW THAT HAD TUNED IN THE WRONG LOC FREQ FOR RWY 19R VERSUS RWY 19L IAD, VA.
Narrative: ON ARR TO WASHINGTON-DULLES ARPT (IAD), WE WERE GIVEN A HEADING TO INTERCEPT THE RWY 19L LOC AND TRACK INBOUND. MY COPLT MISTAKENLY ENTERED THE LOC FREQ FOR RWY 19R. WE INTERCEPTED AND TRACKED THE RWY 19R LOC. AFTER A FEW MINS, ATC ASKED US WHICH RWY WE HAD REQUESTED. WE TOLD THEM RWY 19L. WE WERE THEN GIVEN A HEADING AND TOLD TO INTERCEPT THE RWY 19L LOC. NOTHING MORE WAS SAID BY ATC ABOUT THE ERROR. I BELIEVE THE CAUSES OF THIS ERROR WERE CREW FATIGUE AND LACK OF CRM. WE WERE BOTH STILL VERY TIRED FROM MULTIPLE TIME ZONE CHANGES AS WELL AS VARYING STARTING AND STOPPING DUTY DAYS. OUR CRM FAILED BECAUSE WE DID NOT BOTH VERIFY THE CORRECT LOC FREQ FOR THE APCH. WE DO NOT NORMALLY BRIEF AND VERIFY FREQS IF WE ARE EXPECTING A VISUAL APCH TO THE ARPT. WE HAVE SINCE STARTED DOING A FULL BRIEFING OF THE ILS OR OTHER INST APCH WE ARE USING FOR GUIDANCE EVEN IF WE ARE EXPECTING A VISUAL APCH. SUPPLEMENTAL INFO FROM ACN 597568: NORMALLY, BOTH CREW MEMBERS VERIFY ALL NAV FREQS. BUT ON THIS LEG, BOTH CREW MEMBERS WERE FATIGUED. THE FREQS WERE NOT VERIFIED BY THE OTHER PLT, NOR DID I ASK HIM TO VERIFY THEM. CRM BROKE DOWN DUE TO THE FATIGUE OF BOTH PLTS. THE FREQ WAS NOT IDENTED, DUE TO THE VFR CONDITIONS AT THE ARPT.
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.