37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1435865 |
Time | |
Date | 201703 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZYSH.ARTCC |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Widebody Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Relief Pilot Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 200 Flight Crew Type 9832 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
Company flight planning system failed to provide sufficient routing instructions from point of non-redispatch to intermediate dispatch airport. Non-redispatch routing passed through numerous areas which would have required emergency authority. Original dispatch release used zbaa as the intermediate dispatch airport enroute to vhhh. Due to pilot bulletin regarding company's new aircraft use of zbaa; the captain requested and received clarification from chief pilot and dispatch supervisor that zbaa was in fact 'legal' to use. Enroute; the dispatch release was updated to remove zbaa and instead use an intermediate redispatch from jmu VOR in shenyang fir directly to rjaa. The other international relief officer and I came on deck after the new release had been accepted; and this was part of the captain's change over briefing. Shortly after the captain left to begin his break; the redispatch message arrived; all was in order; and the redispatch was accepted. While comparing the redispatch message; the redispatch plan; and the non-redispatch plan; it was noted the flight planning software had built the non-redispatch as direct from the redispatch fix; jmu (in shenyang fir); to rjaa. If we had flown the route; we would have been flying off airways to leave china's shenyang fir; into japan's defense areas (jda); and through the company's self-imposed no fly area. Company flight planning system failed to provide sufficient routing instructions from point of non-redispatch to intermediate dispatch airport.
Original NASA ASRS Text
Title: Air carrier First Officer reported the company flight planning system failed to provide sufficient routing instructions from point of non-redispatch to an intermediate dispatch airport.
Narrative: Company flight planning system failed to provide sufficient routing instructions from point of non-redispatch to intermediate dispatch airport. Non-redispatch routing passed through numerous areas which would have required emergency authority. Original Dispatch release used ZBAA as the intermediate dispatch airport enroute to VHHH. Due to Pilot Bulletin regarding company's new aircraft use of ZBAA; the captain requested and received clarification from Chief Pilot and Dispatch Supervisor that ZBAA was in fact 'legal' to use. Enroute; the Dispatch release was updated to remove ZBAA and instead use an intermediate redispatch from JMU VOR in Shenyang FIR directly to RJAA. The other IRO and I came on deck after the new release had been accepted; and this was part of the captain's change over briefing. Shortly after the captain left to begin his break; the redispatch message arrived; all was in order; and the redispatch was accepted. While comparing the redispatch message; the redispatch plan; and the non-redispatch plan; it was noted the flight planning software had built the non-redispatch as direct from the redispatch fix; JMU (in Shenyang FIR); to RJAA. If we had flown the route; we would have been flying off airways to leave China's Shenyang FIR; into Japan's Defense Areas (JDA); and through the company's self-imposed no fly area. Company flight planning system failed to provide sufficient routing instructions from point of non-redispatch to intermediate dispatch airport.
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.