37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 479680 |
Time | |
Date | 200007 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : hou.airport |
State Reference | TX |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : rno.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : preflight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 175 flight time total : 20000 flight time type : 18500 |
ASRS Report | 479680 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument pilot : multi engine |
Events | |
Anomaly | aircraft equipment problem : less severe maintenance problem : non compliance with mel maintenance problem : improper maintenance maintenance problem : improper documentation non adherence : published procedure |
Independent Detector | other other : 3 |
Resolutory Action | none taken : detected after the fact |
Consequence | other other |
Supplementary | |
Problem Areas | Aircraft Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We picked up an aircraft with a leading edge device indicator MEL'ed. I read the write-up in the logbook and discussed fuel planning with the speed and altitude restrs with dispatch. We complied with the MEL requirements for each flight. On the second leg, a jump seater monitored the leading edge device panel during the extension for takeoff. Having overheard my pretkof briefing where I included the MEL, he pointed out that I had briefed the #4 leading edge device indicator as being meld's, but in fact the #5 leading edge device indicator was not indicating properly. I checked the logbook again and noted that it was the #5 leading edge device that had been deferred and not the #4 leading edge device that was being carried on the release. So the release had been incorrect for 2 of my legs before I was able to correct the error with dispatch and have the #5 leading edge device listed on the release. I should have caught it sooner, but I had missed the difference between the write-up and the release and kept perpetuating the oversight.
Original NASA ASRS Text
Title: A B737 CAPT MISREAD THE MEL IN THE LOGBOOK AND RPTED TO DISPATCH THAT THE #4 LEADING EDGE DEVICE WAS MELD'S WHEN, IN FACT, IT WAS THE #5.
Narrative: WE PICKED UP AN ACFT WITH A LEADING EDGE DEVICE INDICATOR MEL'ED. I READ THE WRITE-UP IN THE LOGBOOK AND DISCUSSED FUEL PLANNING WITH THE SPD AND ALT RESTRS WITH DISPATCH. WE COMPLIED WITH THE MEL REQUIREMENTS FOR EACH FLT. ON THE SECOND LEG, A JUMP SEATER MONITORED THE LEADING EDGE DEVICE PANEL DURING THE EXTENSION FOR TKOF. HAVING OVERHEARD MY PRETKOF BRIEFING WHERE I INCLUDED THE MEL, HE POINTED OUT THAT I HAD BRIEFED THE #4 LEADING EDGE DEVICE INDICATOR AS BEING MELD'S, BUT IN FACT THE #5 LEADING EDGE DEVICE INDICATOR WAS NOT INDICATING PROPERLY. I CHKED THE LOGBOOK AGAIN AND NOTED THAT IT WAS THE #5 LEADING EDGE DEVICE THAT HAD BEEN DEFERRED AND NOT THE #4 LEADING EDGE DEVICE THAT WAS BEING CARRIED ON THE RELEASE. SO THE RELEASE HAD BEEN INCORRECT FOR 2 OF MY LEGS BEFORE I WAS ABLE TO CORRECT THE ERROR WITH DISPATCH AND HAVE THE #5 LEADING EDGE DEVICE LISTED ON THE RELEASE. I SHOULD HAVE CAUGHT IT SOONER, BUT I HAD MISSED THE DIFFERENCE BTWN THE WRITE-UP AND THE RELEASE AND KEPT PERPETUATING THE OVERSIGHT.
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.