An A319 fire warning indication and ECAM alerted at the gate after engine shutdown but maintenance f...

Attributes
ACN	971056
Time
Date	201109
Local Time Of Day	0601-1200
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Light	Daylight
Aircraft 1
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	Taxi
Flight Plan	IFR
Component
Aircraft Component	Powerplant Fire/Overheat Warning
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 150 Flight Crew Total 19000 Flight Crew Type 2000
Events
Anomaly	Aircraft Equipment Problem Critical Deviation - Procedural Maintenance

Narrative:

Soon after engine shutdown upon arrival; we experienced a brief (2 second) engine fire warning on the #2 engine; along with ECAM fire loop B fault. I reported the event via ACARS and verbally to maintenance. Maintenance action was 'insufficient time to troubleshoot' and then deferred the fire loop. They did not disable the fire loop from the system. After discussion with my first officer; dispatch; and maintenance; I refused the aircraft until troubleshooting was performed. Upon troubleshooting; maintenance discovered there is a maintenance tip for this known issue. They complied with the procedure and discovered that the #2 fire detection unit was faulty. They replaced the fdu and the flight operated normally. I am concerned that the primary response was to get the flight out on time rather than conduct any trouble shooting at all.

Original NASA ASRS Text

Title: An A319 Fire Warning indication and ECAM alerted at the gate after engine shutdown but maintenance failed to address the anomaly to avoid a departure delay so the Captain refused the aircraft. Maintenance then replaced the faulty Fire Detection Unit.

Narrative: Soon after engine shutdown upon arrival; we experienced a brief (2 second) Engine Fire Warning on the #2 engine; along with ECAM Fire Loop B fault. I reported the event via ACARS and verbally to Maintenance. Maintenance Action was 'Insufficient time to Troubleshoot' and then deferred the fire loop. They did not disable the fire loop from the system. After discussion with my First Officer; Dispatch; and Maintenance; I refused the aircraft until troubleshooting was performed. Upon troubleshooting; Maintenance discovered there is a Maintenance Tip for this known issue. They complied with the procedure and discovered that the #2 Fire Detection Unit was faulty. They replaced the FDU and the flight operated normally. I am concerned that the primary response was to get the flight out on time rather than conduct any trouble shooting at all.

Data retrieved from NASA's ASRS site as of April 2012 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.

An A319 fire warning indication and ECAM alerted at the gate after engine shutdown but maintenance failed to address the anomaly to avoid a departure delay so the captain refused the aircraft. Maintenance then replaced the faulty fire detection unit.