Narrative:

We were in cruise flight northwest of ZZZ (approximately 100-150 mi) when we received an 'APU loop a fault.' the APU was off and the message was a crew awareness only. (No action.) about 2 mins later; the APU fire button illuminated red with no ECAM. Following the fcom procedure; I pushed the APU fire button out and armed the squib. After 10 seconds; I discharged the bottle and the light indicated 'discharged.' after contacting maintenance control and discussing our situation with them (at this point we were fairly certain it was an indication problem); we decided to go to ZZZ since the APU fire light was still on and the fcom said to land as soon as possible. The arrival into ZZZ was uneventful and we did the overweight landing checklist per the QRH. Upon arrival at the gate; I entered the overweight landing and the APU fire indication in the maintenance log. Contract maintenance did the required inspections and entered 3 MEL's in the book. They were MEL #49-10-01 APU inoperative; #26-13-01-3 APU fire detection system inoperative; and #26-22-01-2 APU agent discharge light inoperative -- which was entered and the required maintenance actions were performed. After maintenance control verified all requirements and inspections were complied with; the logbook was signed off and we made an uneventful trip to ZZZ1. I would like to add that according to contract maintenance; it appeared the squib did not discharge into the APU even though the cockpit indications said it did. On the trip to ZZZ1; I noticed that contract maintenance entered MEL 26-22-01-2 in the summary column as 'APU fire extinguishing system inoperative' which is actually MEL 26-22-0. I believe in my rush to get the passenger to their original destination I missed the incorrect write-up in the maintenance log. Going forward; I will be more diligent to ensure correct entries.

Google
 

Original NASA ASRS Text

Title: AN A320 DIVERTED DUE APU FIRE WARNING AND PRECAUTIONARY DISCHARGE OF FIRE EXTINGUISHER. CONTRACT MAINT ENTERED A WRONG MEL REF IN LOGBOOK.

Narrative: WE WERE IN CRUISE FLT NW OF ZZZ (APPROX 100-150 MI) WHEN WE RECEIVED AN 'APU LOOP A FAULT.' THE APU WAS OFF AND THE MESSAGE WAS A CREW AWARENESS ONLY. (NO ACTION.) ABOUT 2 MINS LATER; THE APU FIRE BUTTON ILLUMINATED RED WITH NO ECAM. FOLLOWING THE FCOM PROC; I PUSHED THE APU FIRE BUTTON OUT AND ARMED THE SQUIB. AFTER 10 SECONDS; I DISCHARGED THE BOTTLE AND THE LIGHT INDICATED 'DISCHARGED.' AFTER CONTACTING MAINT CTL AND DISCUSSING OUR SIT WITH THEM (AT THIS POINT WE WERE FAIRLY CERTAIN IT WAS AN INDICATION PROB); WE DECIDED TO GO TO ZZZ SINCE THE APU FIRE LIGHT WAS STILL ON AND THE FCOM SAID TO LAND ASAP. THE ARR INTO ZZZ WAS UNEVENTFUL AND WE DID THE OVERWT LNDG CHKLIST PER THE QRH. UPON ARR AT THE GATE; I ENTERED THE OVERWT LNDG AND THE APU FIRE INDICATION IN THE MAINT LOG. CONTRACT MAINT DID THE REQUIRED INSPECTIONS AND ENTERED 3 MEL'S IN THE BOOK. THEY WERE MEL #49-10-01 APU INOP; #26-13-01-3 APU FIRE DETECTION SYS INOP; AND #26-22-01-2 APU AGENT DISCHARGE LIGHT INOP -- WHICH WAS ENTERED AND THE REQUIRED MAINT ACTIONS WERE PERFORMED. AFTER MAINT CTL VERIFIED ALL REQUIREMENTS AND INSPECTIONS WERE COMPLIED WITH; THE LOGBOOK WAS SIGNED OFF AND WE MADE AN UNEVENTFUL TRIP TO ZZZ1. I WOULD LIKE TO ADD THAT ACCORDING TO CONTRACT MAINT; IT APPEARED THE SQUIB DID NOT DISCHARGE INTO THE APU EVEN THOUGH THE COCKPIT INDICATIONS SAID IT DID. ON THE TRIP TO ZZZ1; I NOTICED THAT CONTRACT MAINT ENTERED MEL 26-22-01-2 IN THE SUMMARY COLUMN AS 'APU FIRE EXTINGUISHING SYS INOP' WHICH IS ACTUALLY MEL 26-22-0. I BELIEVE IN MY RUSH TO GET THE PAX TO THEIR ORIGINAL DEST I MISSED THE INCORRECT WRITE-UP IN THE MAINT LOG. GOING FORWARD; I WILL BE MORE DILIGENT TO ENSURE CORRECT ENTRIES.

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.