MD11 FLC OPERATES ACFT IN CLASS II AIRSPACE WITH 1 FMC INOP.

Date: 2002-12 · Aircraft: MD-11 · Phase: ground

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

Synopsis

MD11 FLC OPERATES ACFT IN CLASS II AIRSPACE WITH 1 FMC INOP.

Narrative

I WAS ASSIGNED AS FO ON THE SECOND LEG OF FLT FOLLOWING ACCEPTANCE OF THE ACFT FROM 'A' CHK. AS WE PARKED THE ACFT ATZ; THE ACFT REJECTED THE GND PWR AS IT WAS SWITCHED FROM APU TO GPU. THIS RESULTED IN THE ACFT DEPWRING WITH THE RESULTANT SWITCH TO EMER PWR; AND THE SYS SHUTTING DOWN. WE REAPPLIED THE APU AND THE ACFT SYS BEGAN TO REBOOT. THE #1 FMC; HOWEVER; WOULD NOT RESET. WE CALLED FOR OUR MAINT; RPTED THE MALFUNCTION; PUT IT IN THE ACFT MAINT LOG AND THEY BEGAN TO TROUBLESHOOT THE SYS. WE WERE TOLD THAT A PART WOULD BE SUPPLIED AT A DOWNLINE STATION. WE WERE SENT AN AMENDED RELEASE REFLECTING MEL. WE COMPLIED WITH THE MAINT AND OPERATIONAL PROCS TO PROCEED. WE DEPARTED AND COMPLETED THE SEGMENT UNEVENTFULLY. WE TURNED THE ACFT OVER TO MAINT AND THEY TRIED TO RESET THE INOP COMPUTER. THE NEXT CREW ALSO ACCEPTED THE ACFT AND DEPARTED. THE FLT WAS CONDUCTED UNDER PROCS THAT WE WERE TRAINED TO; AND DID; FOLLOW. WE COMPLIED WITH THE PROCS AS SPELLED OUT IN THE MEL; FCOM. I SHOULD HAVE REJECTED THE ACFT FOR CLASS 2 NAV.

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