37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1038250 |
Time | |
Date | 201209 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | MD-82 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Component | |
Aircraft Component | Pneumatic System |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural Published Material / Policy |
Narrative:
After takeoff I noticed what I thought was an abnormally high pneumatic duct pressure - 70 psi. We discussed the condition and looked in the QRH and the aircraft operating manual for guidance. Finding none; I noted the duct pressure at several different altitudes/power settings for a possible logbook write up. Aware that there used to be a procedure for bleeding this duct pressure off by use of the airfoil anti-ice system and that now the procedure doesn't exist I decided to call maintenance control for advice prior to making any logbook entries. During those communications I was asked to take the aircraft on the next flight and troubleshoot the system by activating the airfoil anti-ice system. At this point I decided the system was not in proper working order and decided to enter [the discrepancy] into the logbook. Eventually the aircraft was taken out of service for repair/troubleshooting. Another consideration for electing not to troubleshoot the problem on the next leg was that our previous [but no longer published] procedure called for activation of the airfoil anti-ice switch while leaving the crossfeeds closed to drain the pressure build up. This meant that activation of the airfoil anti-ice switch would have activated the system for two and a half minutes; [a period of exposure I deemed to be unacceptable]. Our airline needs to remind maintenance not to advise or suggest that flight crews do troubleshooting during revenue flights; especially using a procedure that no longer exists. I believe the technician that I spoke with was well intended in his advice but; nonetheless; doing so was not the proper action given [currently published procedures].
Original NASA ASRS Text
Title: An MD-82 Captain was unwilling to accept the Maintenance request that he fly his next leg in an aircraft displaying symptoms of a pneumatic system problem in order to troubleshoot the system using a no longer current procedure. After landing the aircraft was taken out of service.
Narrative: After takeoff I noticed what I thought was an abnormally high pneumatic duct pressure - 70 PSI. We discussed the condition and looked in the QRH and the Aircraft Operating Manual for guidance. Finding none; I noted the duct pressure at several different altitudes/power settings for a possible logbook write up. Aware that there used to be a procedure for bleeding this duct pressure off by use of the airfoil anti-ice system and that now the procedure doesn't exist I decided to call Maintenance Control for advice prior to making any logbook entries. During those communications I was asked to take the aircraft on the next flight and troubleshoot the system by activating the airfoil anti-ice system. At this point I decided the system was not in proper working order and decided to enter [the discrepancy] into the logbook. Eventually the aircraft was taken out of service for repair/troubleshooting. Another consideration for electing not to troubleshoot the problem on the next leg was that our previous [but no longer published] procedure called for activation of the airfoil anti-ice switch while leaving the crossfeeds closed to drain the pressure build up. This meant that activation of the airfoil anti-ice switch would have activated the system for two and a half minutes; [a period of exposure I deemed to be unacceptable]. Our airline needs to remind Maintenance not to advise or suggest that flight crews do troubleshooting during revenue flights; especially using a procedure that no longer exists. I believe the Technician that I spoke with was well intended in his advice but; nonetheless; doing so was not the proper action given [currently published procedures].
Data retrieved from NASA's ASRS site as of July 2013 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.