|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1201 To 1800|
|Locale Reference||airport : zzz.airport|
|Altitude||agl single value : 0|
|Operator||common carrier : air carrier|
|Make Model Name||B777-200|
|Operating Under FAR Part||Part 121|
|Flight Phase||ground : maintenance|
ground : takeoff roll
|Affiliation||company : air carrier|
|Function||flight crew : first officer|
|Experience||flight time last 90 days : 220|
flight time total : 6000
flight time type : 2200
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Experience||flight time last 90 days : 240|
flight time total : 25000
flight time type : 300
|Anomaly||aircraft equipment problem : less severe|
maintenance problem : improper maintenance
non adherence : company policies
|Independent Detector||other flight crewa|
|Resolutory Action||none taken : anomaly accepted|
|Problem Areas||Maintenance Human Performance|
Flight Crew Human Performance
Dispatched with incorrect FMC navigation database. During preflight; the captain and I both overlooked the FMC identify page navigation data was XX3 versus the required XX4. Shortly after reaching cruise altitude; we attempted to load the arrival and approach. The FMC page ZZZ arrs only contained runways: no approachs or arrs. We suspected a corrupt load of the navigation data and contacted dispatch and maintenance. While waiting for their reply we also called another flight near us to ask about the condition of their navigation data. They said they were ok; with navigation data XX4. Well; that was when we figured out what our problem was. We informed dispatch and maintenance we had XX3 navigation data installed and maintenance replied XX3 was for the B757/767. We submitted a report for improper FMC navigation data load XX3. Then we had several ACARS and satcom discussions with dispatch about our exact status and confirmed legality of continuing. Remainder of flight to ZZZ was uneventful. Observations: 1) although it is listed in the B777 flight manual; only 1 of our 4 pilots (one of the augmenting first officer's) knew we should be checking for an XX4 database. 2) loading the entire route during preflight; to include expected arrival and landing runway would have idented a problem. 3) if this flight had been ZZZZ or most any other european destination; we probably would not have found our navigation data error. Only asia airports were different. 4) flight manual description could be improved for captain and first officer check of FMC active database.
Original NASA ASRS Text
Title: 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.
Data retrieved from NASA's ASRS site as of May 2009 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.