Casualties unknown

2024-01-28: Bombardier BD-700-1A11 Global 5000 (CS-GLY) — Dubai International Airport, AE

Dubai International Airport, AE

On January 28, 2024, a Bombardier BD-700-1A11 Global 5000 (registration CS-GLY) was involved in an aviation accident near Dubai International Airport, AE. Investigators recorded the probable cause as: The causes of the runway incursion serious incident were the Tower controller’s use of non-standard phraseology in the conditional clearance issued to the Aircraft for crossing the runway, which led to the flight crew incorrectly identifying an aircraft… This summary draws on records from the UAE Air Accident Investigation Sector (GCAA AAIS).

Sourcesthe UAE Air Accident Investigation Sector (GCAA AAIS)Primary reportUpdated 1784424886Data APIEditorial standards
Aircraft registered CS-GLY
Aircraft registered CS-GLY. Photo: André Gerwing / CC BY-SA 4.0, via Wikimedia Commons

A serious incident occurred on 29 January 2024 at Dubai International Airport when a Bombardier Global 5000 (CS-GLY) crossing runway 30R experienced a runway incursion as an Airbus A330-343 (HZ-AQ14) took off. Minimum separation was about 1,330 meters. The investigation identified non-standard phraseology by the tower controller and the flight crew's failure to seek clarification as causes.

History of Flight

On 29 January 2024, a Bombardier BD-700-1A11 Global 5000 aircraft, registration CS-GLY, operated by NetJets Transportes Aereos S.A., was conducting a ferry flight (NJE316K) from London Biggin Hill Airport to Dubai International Airport. The aircraft landed on runway 30L and vacated the runway. It then needed to taxi to its parking stand, which required crossing runway 30R via specific taxiways. The flight crew received a conditional clearance to cross runway 30R. However, during the crossing, another aircraft, an Airbus A330-343 (registration HZ-AQ14) operated by Saudi Arabian Airlines, took off from the same runway. The minimum distance between the two aircraft was approximately 1,330 meters when the departing aircraft lifted off while the crossing aircraft was at the edge of the runway. This event was classified as a serious incident.

Causes

The Air Accident Investigation Sector (AAIS) determined that the causes of the runway incursion serious incident were:

  • The tower controller’s use of non-standard phraseology in the conditional clearance issued to the Global 5000 for crossing the runway, which led the flight crew to incorrectly identify an aircraft taxiing ahead as the conditional aircraft.
  • The flight crew did not seek clarification from the tower controller despite being uncertain about the taxiway lights being off beyond the stop bars and the guidance lights for crossing the runway.

Contributing Factors

The AAIS identified the following contributing factors:

  • The Global 5000 was not yet on tower frequency when the controller issued the take-off clearance to the A330 for runway 30R, resulting in the flight crew being unaware of the departure.
  • Improper handling of the stop bars at taxiway Mike 2 led to their activation nearly simultaneously with the Global 5000 crossing, preventing the flight crew from noticing the stop bars activation as they passed.

Safety Recommendations

The AAIS issued four safety recommendations to the air navigation service provider: 1. Emphasize to air traffic controllers the importance of using correct standard phraseology that enhances pilots’ situational awareness. 2. Ensure adherence to revised standard operating procedures for selecting holding point stop bars. 3. Study the potential for improving the current system functionality to allow automatic activation of stop bars based on updated standard operating procedures. 4. Incorporate familiarization training for air traffic controllers with actual night-time conditions on the airfield.

Additionally, one safety recommendation was addressed to NetJets Transportes Aereos S.A. to assess the effectiveness of the safety measures taken following the incident, ensuring that the safety efforts are both efficient and effective.

Probable cause

The causes of the runway incursion serious incident were the Tower controller’s use of non-standard phraseology in the conditional clearance issued to the Aircraft for crossing the runway, which led to the flight crew incorrectly identifying an aircraft taxiing ahead as the conditional aircraft. Additionally, the flight crew did not seek clarification from the Tower controller despite being uncertain about the taxiway lights being off beyond the stop bars and the guidance lights for crossing the runway.