An A320's LAV and CARGO Smoke Detector Fault ECAMs alerted in rapid succession during descent. The Captain did not declare an emergency but ATC treated the event as such.

Date: 2009-12 · Aircraft: A320 · Phase: descent

Anomalies: aircraft-equipment-problem-less-severe

Synopsis

An A320's LAV and CARGO Smoke Detector Fault ECAMs alerted in rapid succession during descent. The Captain did not declare an emergency but ATC treated the event as such.

Narrative

Descending we encountered multiple ECAMS. Forward Cargo Smoke Detector Fault; Aft Cargo Smoke Detector Fault; LAV Smoke Detector Fault and Cargo Smoke Detector Fault. One following the other. Captain flew and gave ECAM to First Officer. Captain advised Center of potential emergency developing involving the potential of smoke in aircraft asking for priority handling. Center acknowledged giving us direct to the destination VOR. Center switched us to Approach Control. Approach Control assigned us Runway 36 while ATIS showed landing south. I questioned the runway and he said 'Understand smoke in cockpit and you have declared an emergency?' Captain advised 'Negative; we had a potential problem but have not declared an emergency.' Captain further advised we can land to the south but would like to keep speed up. Aircraft approached the VOR at 280 knots. Approach advised 'Equipment standing by.' Captain advised equipment 'Not necessary' and ATC advised 'Standard operations for airport.' Aircraft landed without incident. Briefed Flight Managers accordingly and called Dispatch and briefed as well. I chose to get ATC in the loop in the case of further escalation of the event. Miscommunication between Center and Approach Control. How would I do things differently? May have completed ECAM before advising ATC. That said; with all the ECAMS going off at once; I felt the potential for further escalation of the event and made the decision to do so.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.