37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 151806 |
Time | |
Date | 199007 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : mex |
State Reference | FO |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other |
Flight Phase | ground : preflight ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 240 flight time total : 8000 flight time type : 1000 |
ASRS Report | 151806 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 350 flight time total : 11600 flight time type : 4300 |
ASRS Report | 151813 |
Events | |
Anomaly | aircraft equipment problem : critical non adherence : far non adherence : published procedure |
Independent Detector | aircraft equipment other aircraft equipment : unspecified |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Departing mex at xa:30 first officer spooled engines for takeoff. #1 was warmed, #2 failed to spool but remained frozen at idle power. We returned to the gate and had maintenance check out the problem. The mechanic found and drained water in the fuel control unit. We were cleared to do a runup at the gate, with the engine now running properly. This took about 24 minutes and we pushed and departed with no further problems. En route I realized we did no paperwork on this and upon arrival at iah I asked maintenance what they wanted in the logbook, since it should be addressed. I was told to put in 'information' write-up. So I wrote something to the effect that the #2 engine failed to spool, return to gate, and maintenance did a quick repair to have us on our way. I thought about writing what specifics the mechanic told me, but did not want to put down something that was not totally accurate or complete, so left it like it was. I was later contacted by the company about the occurrence and determined that this episode was not a proper way to handle the situation. Lessons learned: always put it in the logbook and let maintenance do their own corrective action sign offs. Contributing factors. This particular pairing is very difficult to get proper/adequate rest because of the nature of how it is put together. The wakeup is tough enough, but trying to sleep at will beforehand is even worse. Anyway I felt like my judgement and alertness was compromised by the 3-4 hours of less than restful sleep. I'll work harder at making sure something like this improper practice is avoided. Callback conversation with reporter revealed the following: conversation mostly concerned the quality of his layover in mex. Reporter actually had about 2 hours sleep prior to the incident and he feels that this contributed to his possible complacent approach to the required logbook write-up. Callback conversation with reporter revealed the following: 151813. First officer had only 2 hours sleep prior to incident. This caused by being locked out of his room and unable to converse in spanish with hotel personnel.
Original NASA ASRS Text
Title: ACFT RETURNED TO GATE TO HAVE AN ENGINE ACCELERATION PROBLEM FIXED. CREW FAILED TO WRITE UP PROBLEM IN ACFT LOGBOOK.
Narrative: DEPARTING MEX AT XA:30 F/O SPOOLED ENGS FOR TKOF. #1 WAS WARMED, #2 FAILED TO SPOOL BUT REMAINED FROZEN AT IDLE PWR. WE RETURNED TO THE GATE AND HAD MAINT CHK OUT THE PROB. THE MECH FOUND AND DRAINED WATER IN THE FUEL CTL UNIT. WE WERE CLRED TO DO A RUNUP AT THE GATE, WITH THE ENG NOW RUNNING PROPERLY. THIS TOOK ABOUT 24 MINUTES AND WE PUSHED AND DEPARTED WITH NO FURTHER PROBS. ENRTE I REALIZED WE DID NO PAPERWORK ON THIS AND UPON ARR AT IAH I ASKED MAINT WHAT THEY WANTED IN THE LOGBOOK, SINCE IT SHOULD BE ADDRESSED. I WAS TOLD TO PUT IN 'INFO' WRITE-UP. SO I WROTE SOMETHING TO THE EFFECT THAT THE #2 ENG FAILED TO SPOOL, RETURN TO GATE, AND MAINT DID A QUICK REPAIR TO HAVE US ON OUR WAY. I THOUGHT ABOUT WRITING WHAT SPECIFICS THE MECH TOLD ME, BUT DID NOT WANT TO PUT DOWN SOMETHING THAT WAS NOT TOTALLY ACCURATE OR COMPLETE, SO LEFT IT LIKE IT WAS. I WAS LATER CONTACTED BY THE COMPANY ABOUT THE OCCURRENCE AND DETERMINED THAT THIS EPISODE WAS NOT A PROPER WAY TO HANDLE THE SITUATION. LESSONS LEARNED: ALWAYS PUT IT IN THE LOGBOOK AND LET MAINT DO THEIR OWN CORRECTIVE ACTION SIGN OFFS. CONTRIBUTING FACTORS. THIS PARTICULAR PAIRING IS VERY DIFFICULT TO GET PROPER/ADEQUATE REST BECAUSE OF THE NATURE OF HOW IT IS PUT TOGETHER. THE WAKEUP IS TOUGH ENOUGH, BUT TRYING TO SLEEP AT WILL BEFOREHAND IS EVEN WORSE. ANYWAY I FELT LIKE MY JUDGEMENT AND ALERTNESS WAS COMPROMISED BY THE 3-4 HOURS OF LESS THAN RESTFUL SLEEP. I'LL WORK HARDER AT MAKING SURE SOMETHING LIKE THIS IMPROPER PRACTICE IS AVOIDED. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING: CONVERSATION MOSTLY CONCERNED THE QUALITY OF HIS LAYOVER IN MEX. RPTR ACTUALLY HAD ABOUT 2 HOURS SLEEP PRIOR TO THE INCIDENT AND HE FEELS THAT THIS CONTRIBUTED TO HIS POSSIBLE COMPLACENT APCH TO THE REQUIRED LOGBOOK WRITE-UP. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING: 151813. F/O HAD ONLY 2 HOURS SLEEP PRIOR TO INCIDENT. THIS CAUSED BY BEING LOCKED OUT OF HIS ROOM AND UNABLE TO CONVERSE IN SPANISH WITH HOTEL PERSONNEL.
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.