Near-Miss at Dublin Airport Involving Two Airbus A320s and a Boeing 737

Casualties unknown • IE

A Boeing 737 narrowly avoided a collision with a stationary Airbus A320 during taxiing operations at Dublin Airport due to communication gaps and misunderstood instructions.

What happened

On 19 May 2018, a serious incident occurred at Dublin Airport involving three aircraft during taxiing operations. An Airbus A320, EI-DER, was stationary at the corner of Link 1 after being instructed to hold position to allow a company aircraft to depart. Simultaneously, a Boeing 737-8AS, EI-EBW, was taxiing toward the same area on the Ground frequency.

As EI-EBW approached, the pilot of EI-DER observed the Boeing 737 continuing its path toward the stationary Airbus. The commander of EI-DER transmitted a direct request for the Boeing 737 to hold position. However, because EI-EBW was still operating on the Ground frequency and had not yet been transferred to the Tower frequency, the crew did not hear the warning. The Boeing 737-8AS proceeded to pass in front of EI-DER, resulting in a very narrow margin of clearance. The pilot of EI-DER estimated the wingtip clearance was only approximately 3 meters. No injuries or damage to either aircraft were reported.

The investigation

The AAIU investigation examined ground radar recordings, controller statements, and flight crew testimonies. The investigation established that the Surface Movements Controller (SMC) had cleared EI-EBW to proceed to the holding point, but did not issue specific sequencing instructions to ensure it would yield to EI-DER.

Furthermore, the investigation found that the crew of EI-EBW misinterpreted an Air Traffic Control (ATC) instruction. While listening to the frequency, the crew heard an instruction for a different aircraft (EI-EAV) to give way to a Ryanair flight and mistakenly believed this instruction applied to their own movement relative to EI-DER.

Findings

  • The primary cause was taxiing in close proximity to a stationary aircraft without confirming the sequence in the queue.
  • The crew of EI-EBW misunderstood an ATC instruction intended for another aircraft.
  • The aircraft involved were operating on different communication frequencies, preventing the crew of EI-EBW from hearing the warning from EI-DER.
  • No specific sequencing instructions were provided to EI-EBW by the controller to manage the arrival into the queue.
  • The area of the incident is a known Aerodrome Hot Spot with a history of ground collisions.

Safety action

  • It is recommended that the Irish Aviation Authority amend procedures at Dublin Airport to include mandatory sequencing instructions whenever aircraft are queuing and joining from multiple different taxiways.

Probable cause

The incident was caused by an aircraft taxiing in close proximity to a stationary aircraft without confirming its position in the departure sequence, compounded by a lack of specific sequencing instructions from ATC and a misunderstanding of radio communications.

Frequently asked questions

What happened in the null aircraft accident near IE?

A Boeing 737 narrowly avoided a collision with a stationary Airbus A320 during taxiing operations at Dublin Airport due to communication gaps and misunderstood instructions.

What aircraft was involved and where did it happen?

The accident on null involved a aircraft, registration EI-EBW, at IE.

What was the probable cause of the accident?

The incident was caused by an aircraft taxiing in close proximity to a stationary aircraft without confirming its position in the departure sequence, compounded by a lack of specific sequencing instructions from ATC and a misunderstanding of radio communications.

Loading the flight search…