 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737-500 captain reports on engine run prior to takeoff #2 engine vibration indication abnormal. Advised by maintenance controller item is a carry forward deferred item not entered in logbook.
| Attributes | |
| ACN | 531888 |
| Time | |
| Date | 200111 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : zzz.airport |
| State Reference | US |
| Altitude | agl single value : 0 |
| Environment | |
| Weather Elements | Snow |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other |
| Flight Phase | ground other : run up |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 90 flight time total : 9000 flight time type : 2719 |
| ASRS Report | 531888 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | aircraft equipment problem : critical other anomaly other |
| Independent Detector | aircraft equipment other aircraft equipment : #2 engine vibration ind other flight crewa other flight crewb |
| Resolutory Action | none taken : detected after the fact |
| Consequence | other Other |
| Factors | |
| Maintenance | performance deficiency : logbook entry |
| Supplementary | |
| Problem Areas | FAA Chart Or Publication Aircraft Maintenance Human Performance |
| Primary Problem | Chart Or Publication |
| Situations | |
| Publication | MAINT. MANUAL PROCEDURE |
Narrative:
Departing runway 16R at ZZZ airport with moderate snow and 1 mi visibility. During 70% N1 engine run-up, #2 engine indicated an abnormal level 3 vibration indication. We accomplished this procedure 2 times on the runway before canceling our takeoff. We found a dry spot on the taxiway that allowed us to run up the engine and verify we didn't just have ice contamination on the fan blades. After contacting maintenance, we returned to the gate for a maintenance inspection of the #2 engine. Upon calling the air carrier maintenance engine controller, I was told that there was a previous history of this problem and it had been deferred using the carry forward deferral process. After once again reviewing the maintenance release document, dil and maintenance log history, I discovered that we did not have any knowledge of this critical deferral. There was a log item in the logbook on nov/sun/01 indicating the previous vibration problem, but was not on our paperwork. I was told by maintenance that in this case nothing had been entered into the metered section, which would have created the carry forward deferral in our dil/log history. It is my understanding that the captain is required to have the ability to determine the maintenance status of the aircraft, which does not occur using this carry forward deferral process. I would suggest creating of deferral section on the maintenance release document or entering them into the logbook.
Original NASA ASRS Text
Title: A B737-500 CAPT RPTS ON ENG RUN PRIOR TO TKOF #2 ENG VIBRATION INDICATION ABNORMAL. ADVISED BY MAINT CTLR ITEM IS A CARRY FORWARD DEFERRED ITEM NOT ENTERED IN LOGBOOK.
Narrative: DEPARTING RWY 16R AT ZZZ ARPT WITH MODERATE SNOW AND 1 MI VISIBILITY. DURING 70% N1 ENG RUN-UP, #2 ENG INDICATED AN ABNORMAL LEVEL 3 VIBRATION INDICATION. WE ACCOMPLISHED THIS PROC 2 TIMES ON THE RWY BEFORE CANCELING OUR TKOF. WE FOUND A DRY SPOT ON THE TXWY THAT ALLOWED US TO RUN UP THE ENG AND VERIFY WE DIDN'T JUST HAVE ICE CONTAMINATION ON THE FAN BLADES. AFTER CONTACTING MAINT, WE RETURNED TO THE GATE FOR A MAINT INSPECTION OF THE #2 ENG. UPON CALLING THE ACR MAINT ENG CTLR, I WAS TOLD THAT THERE WAS A PREVIOUS HISTORY OF THIS PROB AND IT HAD BEEN DEFERRED USING THE CARRY FORWARD DEFERRAL PROCESS. AFTER ONCE AGAIN REVIEWING THE MAINT RELEASE DOCUMENT, DIL AND MAINT LOG HISTORY, I DISCOVERED THAT WE DID NOT HAVE ANY KNOWLEDGE OF THIS CRITICAL DEFERRAL. THERE WAS A LOG ITEM IN THE LOGBOOK ON NOV/SUN/01 INDICATING THE PREVIOUS VIBRATION PROB, BUT WAS NOT ON OUR PAPERWORK. I WAS TOLD BY MAINT THAT IN THIS CASE NOTHING HAD BEEN ENTERED INTO THE METERED SECTION, WHICH WOULD HAVE CREATED THE CARRY FORWARD DEFERRAL IN OUR DIL/LOG HISTORY. IT IS MY UNDERSTANDING THAT THE CAPT IS REQUIRED TO HAVE THE ABILITY TO DETERMINE THE MAINT STATUS OF THE ACFT, WHICH DOES NOT OCCUR USING THIS CARRY FORWARD DEFERRAL PROCESS. I WOULD SUGGEST CREATING OF DEFERRAL SECTION ON THE MAINT RELEASE DOCUMENT OR ENTERING THEM INTO THE LOGBOOK.
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.