Narrative:

We were beginning day three of the trip. We got to the airplane; performed our preflight duties to begin our trip. There was one outstanding maintenance issue that was being looked at and corrected. We pushed 18 minutes late due to the maintenance discrepancy and waited approximately another 45 minutes for departure. I was the pilot flying. Weather was day VMC. We were given a heading and told to contact departure. We cleaned the aircraft up and the after takeoff checklist was completed. Upon contacting departure control; were given instructions to climb to 10;000 feet and turn to a heading of 360. We were climbing through 3;000 feet when we were alerted by the crc (continuous repetitive chime) and an ECAM indication of an aft cargo fire. I leveled off the aircraft. Departure subsequently gave additional instructions at which time I [contacted ATC] stating the nature of our [situation]. We began the non normal methodology to deal with this fire indication. After looking to see if it was an immediate action item or ECAM exception we began to complete the ECAM actions. When our attention was to begin to deal with the fire; the ECAM had changed to smoke aft cargo detection fault. We followed with non normal methodology and completed the checklist and noted it was a crew awareness item. We began to evaluate this situation and told ATC that our condition did not appear as dire and we wanted to consult with company and maintenance. Upon their response that it was probably a cids malfunction and in agreement between dispatch and my first officer (first officer); I elected to continue.there had been history on this aircraft just 3 pages back of this smoke aft cargo detection fault. After things had settled down; my first officer and I discussed this issue a little more and he noted that we had no aft cargo smoke detection anymore. It was at this point I did call [to commercial radio] with dispatch and I told them we were going to divert because of that lack of detection. We went through the overweight landing checklist; the landing was virtually a non event and all items of concern were entered into the aml. Maintenance found that one of the smoke detectors had gone bad. We were removed from the trip as the time to repair was going to exceed our duty day.I have since had time to think and review this issue. First and foremost; there is no aft cargo fire ECAM in our checklist or manuals. We only have smoke fwd (aft) cargo smoke. Both of us read the ECAM indication and I stated it verbally aft cargo fire. We both agreed with the condition. Why would an issue with a smoke detector failing cause a false indication to give a fire condition. Something is not right. Either the programming is not correct and/or the program verbiage is not right. This was a very disconcerting event. At no time does any pilot want to be confronted with fire; but most assuredly a false condition causing a fire indication due to a failure of a cargo smoke detector is appalling. I have talked with those that are very familiar with the airbus 320 family and it was stated to me that this is a rare occurrence with the airbus; but it does happen. We absolutely need answers on this event; as I don't want any other pilot to experience an event such as this.

Google
 

Original NASA ASRS Text

Title: Airbus A321 flight crew reported receiving an aural alarm and an 'AFT CARGO FIRE' ECAM alert which later became a 'SMOKE AFT CARGO DET FAULT'. The crew elected to divert and land as a precaution. There was confusion about the indications and checklist procedures as there is no procedure for 'CARGO FIRE'; only for 'CARGO SMOKE'.

Narrative: We were beginning day three of the trip. We got to the airplane; performed our preflight duties to begin our trip. There was one outstanding maintenance issue that was being looked at and corrected. We pushed 18 minutes late due to the maintenance discrepancy and waited approximately another 45 minutes for departure. I was the Pilot Flying. Weather was day VMC. We were given a heading and told to contact departure. We cleaned the aircraft up and the After Takeoff Checklist was completed. Upon contacting departure control; were given instructions to climb to 10;000 feet and turn to a heading of 360. We were climbing through 3;000 feet when we were alerted by the CRC (Continuous Repetitive Chime) and an ECAM indication of an AFT CARGO FIRE. I leveled off the aircraft. Departure subsequently gave additional instructions at which time I [contacted ATC] stating the nature of our [situation]. We began the Non Normal Methodology to deal with this fire indication. After looking to see if it was an Immediate Action Item or ECAM Exception we began to complete the ECAM Actions. When our attention was to begin to deal with the fire; the ECAM had changed to SMOKE AFT CARGO DETECTION FAULT. We followed with Non Normal Methodology and completed the checklist and noted it was a Crew Awareness item. We began to evaluate this situation and told ATC that our condition did not appear as dire and we wanted to consult with company and maintenance. Upon their response that it was probably a CIDS malfunction and in agreement between Dispatch and my First Officer (FO); I elected to continue.There had been history on this aircraft just 3 pages back of this SMOKE AFT CARGO DETECTION FAULT. After things had settled down; my FO and I discussed this issue a little more and he noted that we had no Aft Cargo Smoke Detection anymore. It was at this point I did call [to commercial radio] with dispatch and I told them we were going to divert because of that lack of detection. We went through the Overweight Landing Checklist; the landing was virtually a non event and all items of concern were entered into the AML. Maintenance found that one of the smoke detectors had gone bad. We were removed from the trip as the time to repair was going to exceed our duty day.I have since had time to think and review this issue. First and foremost; there is no AFT CARGO FIRE ECAM in our checklist or manuals. We only have SMOKE FWD (AFT) CARGO SMOKE. Both of us read the ECAM indication and I stated it verbally AFT CARGO FIRE. We both agreed with the condition. Why would an issue with a smoke detector failing cause a false indication to give a fire condition. Something is not right. Either the programming is not correct and/or the program verbiage is not right. This was a very disconcerting event. At no time does any pilot want to be confronted with fire; but most assuredly a false condition causing a fire indication due to a failure of a cargo smoke detector is appalling. I have talked with those that are very familiar with the Airbus 320 family and it was stated to me that this is a rare occurrence with the Airbus; but it does happen. We absolutely need answers on this event; as I don't want any other pilot to experience an event such as this.

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