37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 760321 |
Time | |
Date | 200711 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : zzz.airport |
State Reference | US |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Controlling Facilities | tower : zzz.tower |
Operator | common carrier : air carrier |
Make Model Name | A320 |
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 |
Experience | flight time last 90 days : 200 flight time total : 16000 flight time type : 4500 |
ASRS Report | 760321 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Experience | flight time last 90 days : 130 flight time total : 9000 flight time type : 3000 |
ASRS Report | 760322 |
Events | |
Anomaly | aircraft equipment problem : critical maintenance problem : improper documentation maintenance problem : non compliance with mel non adherence : published procedure non adherence : far |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | other |
Factors | |
Maintenance | contributing factor : briefing performance deficiency : non compliance with legal requirements performance deficiency : logbook entry performance deficiency : fault isolation performance deficiency : training performance deficiency : testing |
Supplementary | |
Problem Areas | Company Maintenance Human Performance Aircraft |
Primary Problem | Maintenance Human Performance |
Narrative:
Potential illegal maintenance release. Aircraft had class ii maintenance message deferred concerning flight controls. Inbound aircraft had the adr 2 fail on takeoff roll in ZZZ and after contact with maintenance control continued inbound to ZZZ1. Maintenance control contacted contract maintenance at ZZZ1 to troubleshoot and release airplane. Contract maintenance seemed very unfamiliar and uncomfortable with what he was doing. Was coached through the bulk (if not entire) process via cell phone. The adr was not repairable and maintenance control deferred the unit and issued a maintenance release. The deferral required all flight controls to operate 'normal' and included a list of flight system that specifically had to be 'normal.' my check pilot captain noted that 1 item listed on the deferral was 1 letter different than a class ii maintenance message (sfcc versus sfcs). The fleet has hammered home that class ii maintenance messages are advisory only. They are generally redundant system and the message is just an indicator that the system needs attention. Flight progress normally to ZZZ. At the arrival gate there were multiple mechanics to look over the deferred system. The pilots scheduled to take the plane indicated to us that it appeared this plane was not legal to fly. Apparently a different maintenance controller was on duty and he felt the system were in conflict and the plane was removed from service. It appears I was convinced to operate a plane that was not legal to fly. If so; then company jeopardized the safety of myself; my crew and 160 passenger. Maintaining an aircraft cannot be subject to negotiation and opinions of what 'might' be ok. Pilots do not have the detailed resources available to us to determine the inner workings of the aircraft system and potential conflicts. When we departed ZZZ1; I thought we had complied with the maintenance release. After arrival and the flurry of activity I became very concerned that we had 'been had.' I called maintenance control 4 hours later to ask what the outcome was and discovered the aircraft had been OTS since we parked it. Maintenance control indicated it was over a 'difference of opinions.' that is not acceptable. Callback conversation with reporter revealed the following information: reporter stated with the previous flight controls class 2 system fault; the #2 adr (air data reference) fault and then an sfcs (slat/flap control system) fault; all this deferred and being told by company maintenance control they were legal and the fault messages were only 'advisory;' only to find out later the aircraft was taken out of service was not acceptable and an unsafe and inadequate maintenance approach to safety.
Original NASA ASRS Text
Title: AN AIRBUS A320 FLIGHT CREW REALIZES LATER THE ACFT THEY HAD FLOWN MAY HAVE BEEN RELEASED WITH A MAINT DEFERRAL THAT WAS NOT LEGAL.
Narrative: POTENTIAL ILLEGAL MAINT RELEASE. ACFT HAD CLASS II MAINT MESSAGE DEFERRED CONCERNING FLT CTLS. INBOUND ACFT HAD THE ADR 2 FAIL ON TKOF ROLL IN ZZZ AND AFTER CONTACT WITH MAINT CTL CONTINUED INBOUND TO ZZZ1. MAINT CTL CONTACTED CONTRACT MAINT AT ZZZ1 TO TROUBLESHOOT AND RELEASE AIRPLANE. CONTRACT MAINT SEEMED VERY UNFAMILIAR AND UNCOMFORTABLE WITH WHAT HE WAS DOING. WAS COACHED THROUGH THE BULK (IF NOT ENTIRE) PROCESS VIA CELL PHONE. THE ADR WAS NOT REPAIRABLE AND MAINT CTL DEFERRED THE UNIT AND ISSUED A MAINT RELEASE. THE DEFERRAL REQUIRED ALL FLT CTLS TO OPERATE 'NORMAL' AND INCLUDED A LIST OF FLT SYS THAT SPECIFICALLY HAD TO BE 'NORMAL.' MY CHK PLT CAPT NOTED THAT 1 ITEM LISTED ON THE DEFERRAL WAS 1 LETTER DIFFERENT THAN A CLASS II MAINT MESSAGE (SFCC VERSUS SFCS). THE FLEET HAS HAMMERED HOME THAT CLASS II MAINT MESSAGES ARE ADVISORY ONLY. THEY ARE GENERALLY REDUNDANT SYS AND THE MESSAGE IS JUST AN INDICATOR THAT THE SYS NEEDS ATTN. FLT PROGRESS NORMALLY TO ZZZ. AT THE ARR GATE THERE WERE MULTIPLE MECHS TO LOOK OVER THE DEFERRED SYS. THE PLTS SCHEDULED TO TAKE THE PLANE INDICATED TO US THAT IT APPEARED THIS PLANE WAS NOT LEGAL TO FLY. APPARENTLY A DIFFERENT MAINT CTLR WAS ON DUTY AND HE FELT THE SYS WERE IN CONFLICT AND THE PLANE WAS REMOVED FROM SVC. IT APPEARS I WAS CONVINCED TO OPERATE A PLANE THAT WAS NOT LEGAL TO FLY. IF SO; THEN COMPANY JEOPARDIZED THE SAFETY OF MYSELF; MY CREW AND 160 PAX. MAINTAINING AN ACFT CANNOT BE SUBJECT TO NEGOTIATION AND OPINIONS OF WHAT 'MIGHT' BE OK. PLTS DO NOT HAVE THE DETAILED RESOURCES AVAILABLE TO US TO DETERMINE THE INNER WORKINGS OF THE ACFT SYS AND POTENTIAL CONFLICTS. WHEN WE DEPARTED ZZZ1; I THOUGHT WE HAD COMPLIED WITH THE MAINT RELEASE. AFTER ARR AND THE FLURRY OF ACTIVITY I BECAME VERY CONCERNED THAT WE HAD 'BEEN HAD.' I CALLED MAINT CTL 4 HRS LATER TO ASK WHAT THE OUTCOME WAS AND DISCOVERED THE ACFT HAD BEEN OTS SINCE WE PARKED IT. MAINT CTL INDICATED IT WAS OVER A 'DIFFERENCE OF OPINIONS.' THAT IS NOT ACCEPTABLE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: REPORTER STATED WITH THE PREVIOUS FLIGHT CONTROLS CLASS 2 SYSTEM FAULT; THE #2 ADR (AIR DATA REFERENCE) FAULT AND THEN AN SFCS (SLAT/FLAP CONTROL SYSTEM) FAULT; ALL THIS DEFERRED AND BEING TOLD BY COMPANY MAINT CONTROL THEY WERE LEGAL AND THE FAULT MESSAGES WERE ONLY 'ADVISORY;' ONLY TO FIND OUT LATER THE ACFT WAS TAKEN OUT OF SERVICE WAS NOT ACCEPTABLE AND AN UNSAFE AND INADEQUATE MAINT APPROACH TO SAFETY.
Data retrieved from NASA's ASRS site as of January 2009 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.