Casualties unknown

2024-09-20: Airbus A321 (PH-YHA) — Transavia Airlines — en route, FR

en route, FR

On September 20, 2024, an Airbus A321 (registration PH-YHA) operated by Transavia Airlines was involved in an aviation accident near en route, FR. Investigators recorded the probable cause as: Failure of the Digital Radio and Audio Integrated Management System (DRAIMS). This summary draws on records from the French Bureau d'Enquêtes et d'Analyses (BEA); 9 related events involving the same aircraft type or operator are linked below.

Sourcesthe French Bureau d'Enquêtes et d'Analyses (BEA)Primary reportUpdated 1785058346Data APIEditorial standards
Airbus A321
Photo: Julien.scavini / CC BY-SA 3.0, via Wikimedia Commons

Interim report details three incidents in Sep 2024 and Jan/Apr 2025 involving Aer Lingus and Transavia Airbus A320/A321 aircraft, where DRAIMS failures led to loss of transponder, ACAS, and radio communication.

History of the Flights

Interim report from the BEA covers three incidents involving Airbus A320/A321 aircraft, all attributed to failures of the Digital Radio and Audio Integrated Management System (DRAIMS). The affected flights experienced difficulties with or loss of radiocommunication, unavailability of transponder and/or ACAS, and degraded approach and landing capabilities. The report notes that for all three flights, these issues are explained by a DRAIMS failure.

Serious Incident to Airbus A320 (EI-NSF) – 20 September 2024

The Aer Lingus flight EIN50V, an Airbus A320-251N registered EI-NSF, departed Dublin for Bordeaux-Mérignac at 06:24 UTC. In cruise at FL 330, approximately 15 minutes before descent, the captain heard crackling in his headset. The RMP 1 screen alternated between normal display and an amber VHF PAGE NOT AVAIL message; RMP 2 alternated with a blank screen. The crew received repeated ECAM alerts including NAV ATC/XPDR STBY, TCAS STBY, COM RMP 2 OFF, and COM RMP 1 FAULT. At 07:22, the aircraft disappeared from radar. The controller conducted a radio check; the crew reported a communication system and transponder problem. Radio contact was lost. The aircraft reappeared briefly twice but disappeared again at 07:27 until the end of the flight. The crew attempted to reset the RMPs and select squawk 7600 without success. The cockpit fell silent; crew could not hear each other in headsets. The captain consulted the air-ground communication failure procedure and, being in VMC, decided to continue to the destination airport, Bordeaux-Mérignac. Coordination between civil and military units began. Brest ACC initiated the alert phase (ALERFA) at 07:31. The military saw the aircraft on Flightradar24 and primary radar. At 07:33, the crew started descent. At 07:34, RMP 2 became active, allowing transmission on 121.800 MHz, which corresponded to Tarbes-Lourdes-Pyrénées ground frequency. Radio contact was made with that controller, who relayed the crew's position and intentions to Bordeaux approach. The crew then transmitted on 121.5 MHz and Mérignac approach frequency without response. Radio contact was re-established at 07:39 on 121.5 MHz with Mont-de-Marsan CDC. The crew reported descending to FL 80 on STAR CNA 2K, confirmed they did not require assistance, and requested a frequency. At 07:41, Bordeaux ACC, monitoring 121.5 MHz, instructed them to contact Bordeaux on 132.990 MHz. The distress phase (DESTRESFA) was activated. Minimum separation between flight EIN50V and British Airways Euroflyer flight EFW59L was 3.2 NM horizontally and about 175 ft vertically. At 07:42, the crew contacted Bordeaux ACC on 132.990 MHz. After transfer to approach, the crew reported descending through FL 100 to FL 80. The controller asked for confirmation and instructed EFW59L to turn left heading 090°. Both crews read back and turned; this double read-back was not noticed. The crew of EIN50V transmitted a PAN PAN message. They could not select ILS 23 frequency automatically; they used RMP STBY NAV to select it manually. After two holding patterns at VAGNA IAF, they were cleared for ILS 23 approach and landed without further incident. Post-flight maintenance tested the transponder and RMPs with no anomalies found; the return flight was uneventful.

Incident to Airbus A321 (PH-YHA) – 13 January 2025

The Transavia flight TRA59M, an Airbus A321-252NX registered PH-YHA, departed Granada for Amsterdam at 19:24 UTC. In cruise at FL 340, at 20:48, the crew observed ECAM alerts NAV LS TUNING DISAGREE, NAV ATC/XPDR STBY, and TCAS STBY memo. The STBY NAV function activated without crew action; radio frequencies on both RMPs desynchronized. The TCAS repeatedly entered STBY mode. Between 20:48 and 21:07, the aircraft disappeared from radar six times and reappeared with seemingly random transponder codes (2107, 1001, 2110, 2111). Mode C was lost intermittently; the transponder IDENT function activated several times without crew action. Audio was lost several times on the co-pilot's side; his transmissions were not received. The alert phase (ALERFA) was activated by Bordeaux ACC at 20:57. The crew could not process ECAM messages due to continuous appearance and disappearance. They attempted to reset each RMP. At 21:07, they were transferred to Brest ACC on 125.965 MHz, but their transmission was received on the previous Bordeaux frequency. They informed Bordeaux ACC that they could no longer change radio frequency.

Incident to Airbus A321 (PH-YHC) – 29 April 2025

The report also includes an incident involving another Transavia Airbus A321-252NX, registered PH-YHC, on 29 April 2025 around 10:30 UTC. No further details are provided in this interim report; the flight is grouped with the others as experiencing similar DRAIMS-related issues.

Probable cause

Failure of the Digital Radio and Audio Integrated Management System (DRAIMS).