37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 862323 |
Time | |
Date | 200911 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | UHMM.ARTCC |
State Reference | FO |
Aircraft 1 | |
Make Model Name | B747-400 |
Operating Under FAR Part | Part 121 |
Flight Plan | IFR |
Component | |
Aircraft Component | Navigation Database |
Person 1 | |
Function | Captain Check Pilot Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 230 Flight Crew Total 14000 Flight Crew Type 10000 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Our flight was planned over alaska; russia and china. Shortly after entering russia at waypoint liski on G912; the magadan controller asked us where we were going and what our heading was. When I told him; he replied that was not our cleared route. I told him we were cleared along that route before departure from the us he then told us to turn left to a heading of 200 degrees and intercept A218. Shortly thereafter he gave us a new clearance: A218 oskon A803 local control B960 indik B155 kurak this route would not come up in our database at all. Nor was it on any of our charts. I told him we had an airway labeled A803 on our chart but at oskon it departed A218 back toward alaska. He insisted that A803 continued westward; but I told him on our chart it departs oskon and heads back northeastward. I called dispatch on sat phone. He told us these airways or fixes were not in his data base or on his charts either. I advised magadan control that I could not comply with the clearance because it was not on our charts and was not in our data base. By the way; our data base was current; and our charts were current. I checked the older chart which was still in our flight bag and it didn't have any of the airways or waypoints in this clearance as well. After some discussion back and forth; we asked for and were given the longitude and latitude for each of the waypoints along the new clearance until it intercepted our original route at kurak. We entered the long/lat for each of the positions into the FMC; noted the long/lat on the flight plan; and next to each long/lat wrote down the name of the fixes in parentheses. The relief crew was just coming on duty. We explained what had been happening; showed them our new route and the long/lats in lieu of the fixes on the flight plan. We had already asked dispatch for a new flight plan with some but not all of the new positions (it was close enough in order to monitor fuel and time) ; and instructed the relief pilots to use the new flight plan until we intercepted our original route; after which they could continue to use the original flight plan. The flight continued normally without incident. Someone might want to look into why those airways and fixes are not in any of our databases or charts; and why we were cleared on a route magadan knew nothing about.
Original NASA ASRS Text
Title: A B747-400 flight crew was advised by Magadan Control that their flight planned route is incorrect. When they provided the route as they understood it; the airways involved were not in the aircraft database.
Narrative: Our flight was planned over Alaska; Russia and China. Shortly after entering Russia at waypoint Liski on G912; the Magadan Controller asked us where we were going and what our heading was. When I told him; he replied that was not our cleared route. I told him we were cleared along that route before departure from the U.S. He then told us to turn left to a heading of 200 degrees and intercept A218. Shortly thereafter he gave us a new clearance: A218 OSKON A803 LC B960 INDIK B155 KURAK This route would not come up in our database at all. Nor was it on any of our charts. I told him we had an airway labeled A803 on our chart but at OSKON it departed A218 back toward Alaska. He insisted that A803 continued westward; but I told him on our chart it departs OSKON and heads back northeastward. I called dispatch on SAT phone. He told us these airways or fixes were not in his data base or on his charts either. I advised Magadan Control that I could not comply with the clearance because it was not on our charts and was not in our data base. By the way; our data base was current; and our charts were current. I checked the older chart which was still in our flight bag and it didn't have any of the airways or waypoints in this clearance as well. After some discussion back and forth; we asked for and were given the longitude and latitude for each of the waypoints along the new clearance until it intercepted our original route at KURAK. We entered the long/lat for each of the positions into the FMC; noted the long/lat on the flight plan; and next to each long/lat wrote down the name of the fixes in parentheses. The relief crew was just coming on duty. We explained what had been happening; showed them our new route and the long/lats in lieu of the fixes on the flight plan. We had already asked dispatch for a new flight plan with some but not all of the new positions (it was close enough in order to monitor fuel and time) ; and instructed the relief pilots to use the new flight plan until we intercepted our original route; after which they could continue to use the original flight plan. The flight continued normally without incident. Someone might want to look into why those airways and fixes are not in any of our databases or charts; and why we were cleared on a route Magadan knew nothing about.
Data retrieved from NASA's ASRS site as of April 2012 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.