MD11 flight crew operates aircraft in class ii airspace with 1 FMC inoperative.

Attributes
ACN	568153
Time
Date	200212
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : hnl.airport
State Reference	HI
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	MD-11
Operating Under FAR Part	Part 121
Flight Phase	ground : parked
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 6100 flight time type : 850
ASRS Report	568153
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 22000 flight time type : 700
ASRS Report	568152
Events
Anomaly	aircraft equipment problem : less severe maintenance problem : non compliance with mel maintenance problem : improper maintenance non adherence : published procedure non adherence : far
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : anomaly accepted
Factors
Maintenance	performance deficiency : non compliance with legal requirements performance deficiency : logbook entry
Supplementary
Problem Areas	Company Flight Crew Human Performance Maintenance Human Performance Aircraft
Primary Problem	Flight Crew Human Performance

Narrative:

I was assigned as first officer on the second leg of flight following acceptance of the aircraft from 'a' check. As we parked the aircraft atz, the aircraft rejected the ground power as it was switched from APU to gpu. This resulted in the aircraft depwring with the resultant switch to emergency power, and the system shutting down. We reapplied the APU and the aircraft system began to reboot. The #1 FMC, however, would not reset. We called for our maintenance, reported the malfunction, put it in the aircraft maintenance log and they began to troubleshoot the system. 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 maintenance and operational procedures to proceed. We departed and completed the segment uneventfully. We turned the aircraft over to maintenance and they tried to reset the inoperative computer. The next crew also accepted the aircraft and departed. The flight was conducted under procedures that we were trained to, and did, follow. We complied with the procedures as spelled out in the MEL, fcom. I should have rejected the aircraft for class 2 navigation.

Original NASA ASRS Text

Title: 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.

Data retrieved from NASA's ASRS site as of July 2007 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.