37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 640114 |
Time | |
Date | 200412 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : zzz.airport |
State Reference | US |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | A321 |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level ground : maintenance ground : parked |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | maintenance : technician |
Qualification | technician : powerplant technician : airframe |
Experience | maintenance lead technician : 7 maintenance technician : 20 |
ASRS Report | 640114 |
Person 2 | |
Affiliation | company : air carrier |
Function | maintenance : technician oversight : coordinator |
Events | |
Anomaly | aircraft equipment problem : critical maintenance problem : non compliance with mel non adherence : far non adherence : published procedure |
Independent Detector | aircraft equipment other aircraft equipment : fire detection system other flight crewa other flight crewb other other : 1 |
Resolutory Action | flight crew : diverted to another airport |
Consequence | other |
Factors | |
Maintenance | performance deficiency : non compliance with legal requirements |
Supplementary | |
Problem Areas | Maintenance Human Performance Chart Or Publication Aircraft |
Primary Problem | Maintenance Human Performance |
Narrative:
I was sent to gate for a fire indication on #1 engine. The handle had a red light on, so I first did a flight report and a bite check on the #1 fire detection unit. The report showed nothing and the #1 fdu reported a #1 engine loop B, no other indications were present. When pulling the #1 engine loop B circuit breaker, the light went out. I then called maintenance control, and he told me to MEL the system (B loop) and turn off the B loop. I told him you can't turn off the B loop on an airbus, only boeing. Then he told me to pull the circuit breaker, collar it, and make a note of it in the logbook. I told him that wasn't a special procedure in the MEL book. I then called my lead to come out. We had no fdu in ZZZ, so we switched #1 with the APU position, the problem followed and then MEL'ed the APU a and B loops, pulled the two circuit breaker's and sent the aircraft in that condition. The aircraft was flying from ZZZ to ZZZ1 and diverted into ZZZ2. When recalling ECAM in flight, it showed a message 'APU fire.' the fire loops can be MEL'ed but not the entire fdu, and since the false indication originated from the fdu, it should have been changed before flight, possibly giving the pilot a false indication in-flight, making him think he needed to land as soon as possible. Callback conversation with reporter revealed the following information: the reporter said there was no indication on the fire detector unit of an internal fault. The unit would have been changed if another was in stock but having none available, the decision was made to render the auxiliary power unit inoperative and defer per the MEL and use the removed fire detection unit in #1 engine. Fixed #1 engine fire detection system, but caused a false fire warning in the auxiliary power unit and a diversion.
Original NASA ASRS Text
Title: AN A319 WAS DISPATCHED WITH #1 FIRE DETECTION UNIT SWAPPED WITH THE AUXILIARY POWER UNIT FIRE DETECTION UNIT DUE TO PARTS AVAILABILITY. ACFT DIVERTED DUE TO FALSE AUXILIARY POWER UNIT FIRE INDICATION.
Narrative: I WAS SENT TO GATE FOR A FIRE INDICATION ON #1 ENG. THE HANDLE HAD A RED LIGHT ON, SO I FIRST DID A FLT RPT AND A BITE CHK ON THE #1 FIRE DETECTION UNIT. THE RPT SHOWED NOTHING AND THE #1 FDU RPTED A #1 ENG LOOP B, NO OTHER INDICATIONS WERE PRESENT. WHEN PULLING THE #1 ENG LOOP B CIRCUIT BREAKER, THE LIGHT WENT OUT. I THEN CALLED MAINT CTL, AND HE TOLD ME TO MEL THE SYSTEM (B LOOP) AND TURN OFF THE B LOOP. I TOLD HIM YOU CAN'T TURN OFF THE B LOOP ON AN AIRBUS, ONLY BOEING. THEN HE TOLD ME TO PULL THE CB, COLLAR IT, AND MAKE A NOTE OF IT IN THE LOGBOOK. I TOLD HIM THAT WASN'T A SPECIAL PROC IN THE MEL BOOK. I THEN CALLED MY LEAD TO COME OUT. WE HAD NO FDU IN ZZZ, SO WE SWITCHED #1 WITH THE APU POS, THE PROB FOLLOWED AND THEN MEL'ED THE APU A AND B LOOPS, PULLED THE TWO CB'S AND SENT THE ACFT IN THAT CONDITION. THE ACFT WAS FLYING FROM ZZZ TO ZZZ1 AND DIVERTED INTO ZZZ2. WHEN RECALLING ECAM IN FLT, IT SHOWED A MESSAGE 'APU FIRE.' THE FIRE LOOPS CAN BE MEL'ED BUT NOT THE ENTIRE FDU, AND SINCE THE FALSE INDICATION ORIGINATED FROM THE FDU, IT SHOULD HAVE BEEN CHANGED BEFORE FLT, POSSIBLY GIVING THE PLT A FALSE INDICATION INFLT, MAKING HIM THINK HE NEEDED TO LAND ASAP. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR SAID THERE WAS NO INDICATION ON THE FIRE DETECTOR UNIT OF AN INTERNAL FAULT. THE UNIT WOULD HAVE BEEN CHANGED IF ANOTHER WAS IN STOCK BUT HAVING NONE AVAILABLE, THE DECISION WAS MADE TO RENDER THE AUXILIARY POWER UNIT INOP AND DEFER PER THE MEL AND USE THE REMOVED FIRE DETECTION UNIT IN #1 ENG. FIXED #1 ENG FIRE DETECTION SYSTEM, BUT CAUSED A FALSE FIRE WARNING IN THE AUXILIARY POWER UNIT AND A DIVERSION.
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.