B767-300 FLT CREW DISCOVERED DURING CRUISE THAT THEY FAILED TO UPDATE THE NAV DATABASE PRIOR TO DEP.
Synopsis
B767-300 FLT CREW DISCOVERED DURING CRUISE THAT THEY FAILED TO UPDATE THE NAV DATABASE PRIOR TO DEP.
Narrative
AFTER TKOF WHEN WE RECEIVED OUR FINAL CLRNC; I NOTICED THAT THE FINAL CLRNC WAYPOINTS DIDN'T MATCH OUR FLT PLAN AND FMC WAYPOINTS. WE MANUALLY ENTERED WAYPOINTS AND DID BEARING AND DISTANCE CHKS; FMC VERSUS CHART AND FLT PLAN AND PROCEEDED ON TO ZZZ. WHEN TRYING TO DETERMINE WHAT HAD CAUSED THIS; MY OPERATING EXPERIENCE CAPT SAID THAT DURING OUR LEGS CHK HE HAD RESPONDED TO MY GLASS TO PAPER CHK AND HAD SEEN BUT NOT CORRECTED THE WAYPOINT NAMES THAT WERE NOT CORRECT. IT WAS HIS FIRST LEG INTL. HE MISINTERPED MY WAYPOINTS CHALLENGE AND HAD NOT QUESTIONED HIS MISUNDERSTANDING. FURTHER CONFUSING THE ISSUE WAS THE FACT THAT WE HAD BOTH MENTALLY TRANSPOSED THE WRONG UTC TIME DATE AND HAD NOT UPDATED THE NAV DATABASE. THE OTHER TWIST BEING THE FACT THAT MAINT HAD NOT INSTALLED THE NEW NAV DATABASE. THERE WERE NO DEVS FROM OUR PLANNED RTE OR ATC PROCS. WE ALL LEARNED A LOT AND IT WAS A CLASSIC SERIES OF MINOR MISTAKES THAT COULD HAVE CAUSED A NAV ERROR. A SUGGESTION TO AVOID THIS ERROR IN THE FUTURE WOULD BE TO ATTACH A NOTE TO OUR FLT PLAN ON FLTS THAT MIGHT BE AFFECTED BY A DATABASE CHANGES.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.