37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1068307 |
Time | |
Date | 201302 |
Place | |
Locale Reference | ZZZZ.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | B747-400 |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Relief Pilot |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Our preflight and loading of the FMC was routine and seemed normal that day. We had requested via ACARS the flight and uploaded the flight plan and winds via ACARS. We then checked the route and everything seemed normal to us. Distances; as I recall never gave us a red flag that one coordinate may have been entered incorrectly. Our flight proceeded normally and the only event that seemed out of place was when ATC asked us to verify our next position after 160E. We told them and never heard anything about our flight path being off from our flight plan. We made company position reports in accordance with SOP and never heard from operations that our flight path was different from that of our filing. It turns out that our flight path deviated 120 NM from our flight plan. Somehow our coordinate of 34n160e got entered as 36n160e; causing the airplane to incur a gross navigational error. We landed at our destination without any ill effect towards the flight. We adhered to company procedures during the route verification check. It was I; the captain; and the first officer that accomplished this check. My suggestion is to have every crew member on duty on the flight deck when this check is being accomplished. CRM is a big part of the safety environment we try to cultivate and I think the more people involved in this route verification; the better prepared we will be.
Original NASA ASRS Text
Title: B747 flight crew is informed after the fact that they entered and flew to an oceanic waypoint that was not part of their flight plan. ATC noted the discrepancy in advance but did not question the flight crew.
Narrative: Our preflight and loading of the FMC was routine and seemed normal that day. We had requested via ACARS the flight and uploaded the flight plan and winds via ACARS. We then checked the route and everything seemed normal to us. Distances; as I recall never gave us a red flag that one coordinate may have been entered incorrectly. Our flight proceeded normally and the only event that seemed out of place was when ATC asked us to verify our next position after 160E. We told them and never heard anything about our flight path being off from our flight plan. We made company position reports in accordance with SOP and never heard from operations that our flight path was different from that of our filing. It turns out that our flight path deviated 120 NM from our flight plan. Somehow our coordinate of 34N160E got entered as 36N160E; causing the airplane to incur a gross navigational error. We landed at our destination without any ill effect towards the flight. We adhered to company procedures during the route verification check. It was I; the Captain; and the First Officer that accomplished this check. My suggestion is to have every crew member on duty on the flight deck when this check is being accomplished. CRM is a big part of the safety environment we try to cultivate and I think the more people involved in this route verification; the better prepared we will be.
Data retrieved from NASA's ASRS site as of July 2013 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.