B777 FLT CREW DISCOVERS AIRBORNE THAT A B767 NAV DATA BASE IS LOADED IN THEIR ACFT.

Date: 2008-04 · Aircraft: B777-200

Anomalies: aircraft-equipment-problem-less-severe|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-maintenance

Synopsis

B777 FLT CREW DISCOVERS AIRBORNE THAT A B767 NAV DATA BASE IS LOADED IN THEIR ACFT.

Narrative

DISPATCHED WITH INCORRECT FMC NAV DATABASE. DURING PREFLT; THE CAPT AND I BOTH OVERLOOKED THE FMC IDENT PAGE NAV DATA WAS XX3 VERSUS THE REQUIRED XX4. SHORTLY AFTER REACHING CRUISE ALT; WE ATTEMPTED TO LOAD THE ARR AND APCH. THE FMC PAGE ZZZ ARRS ONLY CONTAINED RWYS: NO APCHS OR ARRS. WE SUSPECTED A CORRUPT LOAD OF THE NAV DATA AND CONTACTED DISPATCH AND MAINT. WHILE WAITING FOR THEIR REPLY WE ALSO CALLED ANOTHER FLT NEAR US TO ASK ABOUT THE CONDITION OF THEIR NAV DATA. THEY SAID THEY WERE OK; WITH NAV DATA XX4. WELL; THAT WAS WHEN WE FIGURED OUT WHAT OUR PROB WAS. WE INFORMED DISPATCH AND MAINT WE HAD XX3 NAV DATA INSTALLED AND MAINT REPLIED XX3 WAS FOR THE B757/767. WE SUBMITTED A RPT FOR IMPROPER FMC NAV DATA LOAD XX3. THEN WE HAD SEVERAL ACARS AND SATCOM DISCUSSIONS WITH DISPATCH ABOUT OUR EXACT STATUS AND CONFIRMED LEGALITY OF CONTINUING. REMAINDER OF FLT TO ZZZ WAS UNEVENTFUL. OBSERVATIONS: 1) ALTHOUGH IT IS LISTED IN THE B777 FLT MANUAL; ONLY 1 OF OUR 4 PLTS (ONE OF THE AUGMENTING FO'S) KNEW WE SHOULD BE CHKING FOR AN XX4 DATABASE. 2) LOADING THE ENTIRE RTE DURING PREFLT; TO INCLUDE EXPECTED ARR AND LNDG RWY WOULD HAVE IDENTED A PROB. 3) IF THIS FLT HAD BEEN ZZZZ OR MOST ANY OTHER EUROPEAN DEST; WE PROBABLY WOULD NOT HAVE FOUND OUR NAV DATA ERROR. ONLY ASIA ARPTS WERE DIFFERENT. 4) FLT MANUAL DESCRIPTION COULD BE IMPROVED FOR CAPT AND FO CHK OF FMC ACTIVE DATABASE.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.