37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1186334 |
Time | |
Date | 201407 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | OAKX.ARTCC |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Dawn |
Aircraft 1 | |
Make Model Name | B747-200 |
Flight Phase | Descent |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Flight Deck / Cabin / Aircraft Event Other / Unknown |
Narrative:
Just before entering afghanistan airspace the pilot not flying contacted kabul ATC on VHF 2. I was monitoring VHF 1 (karachi ATC) and also listening in on VHF 2. When I heard the pilot not flying telling kabul that our destination was kabul (oakb) I corrected him and told him that our destination was bagram (oaix) and he relayed that to kabul ATC. Abeam kandahar (oakn) I did my approach briefing and we continued our flight. At siblo we got radar vectors by kabul ATC. After extensive vectoring for approach we realized that something was not right since our position did not match up with our bagram approach in the FMS. When we told the ATC controller that our destination was bagram he advised that was news to him. He was vectoring us for an approach to kabul. We then got vectors for bagram and landed there. I've learned to make sure that ATC controller knows your landing airport and pay close attention to where he is vectoring you for an approach.
Original NASA ASRS Text
Title: A B747-200 First Officer; fatigued by duty cycles out of sync with his diurnal cycle; entered OAKB vice OAIX as their destination. Two failed vectors for landing occurred before the flight crew became aware of the anomaly and subsequent vectors to the correct airport were successful.
Narrative: Just before entering Afghanistan Airspace the pilot not flying contacted Kabul ATC on VHF 2. I was monitoring VHF 1 (Karachi ATC) and also listening in on VHF 2. When I heard the pilot not flying telling Kabul that our destination was Kabul (OAKB) I corrected him and told him that our destination was Bagram (OAIX) and he relayed that to Kabul ATC. Abeam Kandahar (OAKN) I did my approach briefing and we continued our flight. At SIBLO we got radar vectors by Kabul ATC. After extensive vectoring for Approach we realized that something was not right since our position did not match up with our Bagram Approach in the FMS. When we told the ATC Controller that our destination was Bagram he advised that was news to him. He was vectoring us for an approach to Kabul. We then got vectors for Bagram and landed there. I've learned to make sure that ATC controller knows your landing airport and pay close attention to where he is vectoring you for an approach.
Data retrieved from NASA's ASRS site 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.