What happened
On the night of 21 July 2021, a ground collision occurred at Dubai International Airport involving a flydubai Boeing 737-800, registration A6-FER, and a Gulf Air Airbus A321-200, registration A9C-NC.
The flydubai aircraft was taxiing toward holding point Mike 13 for a scheduled flight to Kyrgyzstan, while the Gulf Air aircraft was positioned at holding point Mike 10 Alpha, preparing for departure to Bahrain. During the taxi sequence, the Ground controller provided instructions to both crews, but was simultaneously distracted by an incoming telephone call.
As the Boeing 737-800 proceeded, it turned toward the holding point where the Airbus A321-200 was stationary. At approximately 19:43 UTC, the left wingtip of the flydubai aircraft made contact with the tail section of the Gulf Air aircraft. The collision resulted in minor damage to the wingtip of A6-FER and the tail of A9C-NC.
The investigation
An investigation by the UAE Air Accident Investigation Sector (GCAA AAIS) examined the taxi clearances, air traffic control communications, and the physical limitations of the aircraft involved. The inquiry reviewed the Ground controller's instructions, noting that the controller had instructed both crews to "monitor" the Tower frequency rather than using the standard "contact" phraseology.
The investigation also analyzed the visibility from the cockpit, noting that the pilot's line of sight in the Airbus A321-200 is restricted when looking downward, which can obscure ground obstacles. Furthermore, the investigation looked into the accuracy of the Ground Movement Radar (GMR) and the lack of harmonized taxiing restrictions between local ATC procedures and the official Aeronautical Information Publication (AIP).
Findings
- The primary cause of the collision was a lack of effective conflict detection and management resulting from a breakdown in situational awareness among the Ground controller and the flight crews.
- The Ground controller's attention was diverted by an incoming telephone call, leading to a failure to instruct the flydubai aircraft to stop before reaching the stationary Gulf Air aircraft.
- The use of the phrase "monitor" instead of "contact" prevented the Gulf Air crew from actively coordinating with the Tower, contributing to an extended hold.
- There was a mutual assumption between the controller and the flydubai crew that the other party would mitigate the risk of a collision.
- Inconsistencies existed between local ATC taxi restrictions and the UAE AIP, meaning the flydubai crew was unaware of specific restrictions regarding taxiing behind aircraft at certain holding points.
- The Ground Movement Radar did not provide sufficient precision to clearly show the exact position of the aircraft's tail and nose relative to the stop bars.
Safety action
Following the incident, the GCAA amended the UAE AIP to explicitly prohibit aircraft from taxiing or holding behind other aircraft at specific points on taxiways Mike and November to prevent wingtip clearance issues. Dubai Air Navigation Services (dans) implemented internal safety bulletins and briefings to address taxi clearance hazards. Additionally, the GCAA has been conducting oversight to ensure these new restrictions are integrated into all operational and regulatory documentation.