 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
The crew receiving aircraft after over weight landing did not notice there was no overweight landing inspection complete and logged in maintenance log.
| Attributes | |
| ACN | 586012 |
| Time | |
| Date | 200306 |
| Day | 200306 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : pdx.airport |
| State Reference | OR |
| Altitude | agl single value : 0 |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : cle.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : parked |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 250 flight time total : 7000 flight time type : 7000 |
| ASRS Report | 586012 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument pilot : multi engine |
| Experience | flight time last 90 days : 150 flight time total : 6000 flight time type : 1000 |
| ASRS Report | 586013 |
| Events | |
| Anomaly | maintenance problem : improper maintenance maintenance problem : improper documentation non adherence : company policies non adherence : far non adherence : published procedure other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | other other |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance Company Aircraft |
| Primary Problem | Flight Crew Human Performance |
Narrative:
I flew from oak to las where we were involved in an unscheduled aircraft swap (I was advised on the release to expect the swap). We hustled over to the next aircraft and started to get the aircraft ready to board. The flight was going to be close to full. As I checked the logbook I saw where the aircraft had returned after takeoff because the led's (leading edge devices) didn't retract. There was 1 write-up and it mentioned the led's (leading edge devices) and the aircraft weight upon landing had been 133000 pounds. I read the 'clearing' portion of the write-up and it had the usual listings of work per maintenance manuals, etc. I saw the heavy aircraft landing of course, but being in a little hurry to get going to pdx I just assumed everything was done. I was wrong. I flew the aircraft 2 legs. The next captain took the time to check it out and found the error. An 'overweight landing' inspection had not been accomplished. As I look at this event I feel as though I missed a good chance to make a 'good catch.' I had the feeling of something odd about the logbook entries, but I was in a hurry to keep the aircraft on-time that I just ignored it. A simple call to maintenance control to discuss the write-ups would have solved the whole thing. Supplemental information from acn 586013: we started an am trip from oak ending in geg, through las-pdx. In las, we were involved in an aircraft swap. We got to our departure gate and promptly performed our preflight duties to depart to pdx and geg, which we did. In filling out the aircraft logbook, I noticed the return to airport write-up for a leading edge device write up that was repaired by our maintenance in las and returned to service for us to fly to pdx. Therefore I assumed it was ok to fly. When we arrived in geg, the subsequent crew caught the overweight landing inspection requirement and called and informed the captain who called me and informed me of the situation.
Original NASA ASRS Text
Title: THE CREW RECEIVING ACFT AFTER OVER WT LNDG DID NOT NOTICE THERE WAS NO OVERWEIGHT LNDG INSPECTION COMPLETE AND LOGGED IN MAINT LOG.
Narrative: I FLEW FROM OAK TO LAS WHERE WE WERE INVOLVED IN AN UNSCHEDULED ACFT SWAP (I WAS ADVISED ON THE RELEASE TO EXPECT THE SWAP). WE HUSTLED OVER TO THE NEXT ACFT AND STARTED TO GET THE ACFT READY TO BOARD. THE FLT WAS GOING TO BE CLOSE TO FULL. AS I CHKED THE LOGBOOK I SAW WHERE THE ACFT HAD RETURNED AFTER TKOF BECAUSE THE LED'S (LEADING EDGE DEVICES) DIDN'T RETRACT. THERE WAS 1 WRITE-UP AND IT MENTIONED THE LED'S (LEADING EDGE DEVICES) AND THE ACFT WT UPON LNDG HAD BEEN 133000 LBS. I READ THE 'CLRING' PORTION OF THE WRITE-UP AND IT HAD THE USUAL LISTINGS OF WORK PER MAINT MANUALS, ETC. I SAW THE HVY ACFT LNDG OF COURSE, BUT BEING IN A LITTLE HURRY TO GET GOING TO PDX I JUST ASSUMED EVERYTHING WAS DONE. I WAS WRONG. I FLEW THE ACFT 2 LEGS. THE NEXT CAPT TOOK THE TIME TO CHK IT OUT AND FOUND THE ERROR. AN 'OVERWT LNDG' INSPECTION HAD NOT BEEN ACCOMPLISHED. AS I LOOK AT THIS EVENT I FEEL AS THOUGH I MISSED A GOOD CHANCE TO MAKE A 'GOOD CATCH.' I HAD THE FEELING OF SOMETHING ODD ABOUT THE LOGBOOK ENTRIES, BUT I WAS IN A HURRY TO KEEP THE ACFT ON-TIME THAT I JUST IGNORED IT. A SIMPLE CALL TO MAINT CTL TO DISCUSS THE WRITE-UPS WOULD HAVE SOLVED THE WHOLE THING. SUPPLEMENTAL INFO FROM ACN 586013: WE STARTED AN AM TRIP FROM OAK ENDING IN GEG, THROUGH LAS-PDX. IN LAS, WE WERE INVOLVED IN AN ACFT SWAP. WE GOT TO OUR DEP GATE AND PROMPTLY PERFORMED OUR PREFLT DUTIES TO DEPART TO PDX AND GEG, WHICH WE DID. IN FILLING OUT THE ACFT LOGBOOK, I NOTICED THE RETURN TO ARPT WRITE-UP FOR A LEADING EDGE DEVICE WRITE UP THAT WAS REPAIRED BY OUR MAINT IN LAS AND RETURNED TO SVC FOR US TO FLY TO PDX. THEREFORE I ASSUMED IT WAS OK TO FLY. WHEN WE ARRIVED IN GEG, THE SUBSEQUENT CREW CAUGHT THE OVERWT LNDG INSPECTION REQUIREMENT AND CALLED AND INFORMED THE CAPT WHO CALLED ME AND INFORMED ME OF THE SIT.
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.