Hawker Beechcraft 400XP Attempts Takeoff from Taxiway at Al Maktoum International

Casualties unknown • Al Maktoum International Airport, Dubai, AE

A flight crew mistakenly initiated a takeoff roll on a taxiway instead of the designated runway at Al Maktoum International Airport, narrowly avoiding a serious incident.

What happened

On 23 May 2014, a Hawker Beechcraft 400XP, registration AP-RBA, operated by Bahria Town Aviation, was involved in a serious incident at Al Maktoum International Airport in Dubai. The aircraft, which was scheduled to transport seven passengers from Dubai to Karachi, was following instructions for a rolling takeoff from runway 30.

During the taxi phase, the crew made a premature left turn at the junction of taxiway Whisky 16. Instead of continuing straight toward the assigned runway, the aircraft lined up on taxiway Victor. The crew proceeded to commence the takeoff roll on this taxiway. The error was only detected when the air traffic controller noticed an unusual amount of dust being kicked up behind the aircraft as it reached approximately 50 knots. The controller immediately ordered the captain to abort the maneuver, and the crew successfully rejected the takeoff. The aircraft was subsequently rerouted and eventually departed safely from the correct runway.

The investigation

The GCAA AAIS investigation examined the flight's operational history and environmental conditions. The crew had been on duty since 0100 UTC, having already operated two flight sectors earlier that day. During the stopover in Dubai, the aircraft experienced a four-hour delay due to refueling complications. This delay required the crew to manage ground operations personally under extreme heat, with temperatures reaching 40 °C and high humidity.

Investigators also reviewed the air traffic control procedures and the airport's regulatory framework. It was noted that the controller had issued a clearance for a rolling takeoff before the aircraft had fully cleared the taxiway junction, and the existing aerodrome manuals did not explicitly mandate a continuous visual watch of the maneuvering area.

Findings

  • The primary cause of the incident was flight crew tiredness resulting from operational demands and exposure to high temperatures, which led to a failure to verify the aircraft's position on the runway.
  • A contributing factor was that the tower controller did not maintain a continuous visual watch on the aircraft's movement on the ground.
  • The crew's situational awareness was degraded by the cumulative effects of an early duty start, a long delay, and intense heat.
  • The aircraft and crew were fully certified and qualified for the operation.

Safety action

Following the investigation, several safety recommendations were issued:

  • The operator should improve standards for crew accommodation to ensure adequate rest.
  • Al Maktoum International Airport controllers should maintain a continuous visual watch on all aircraft, vehicles, and personnel within the maneuvering area.
  • The GCAA should review Civil Aviation Regulations to ensure they align with ICAO standards regarding the requirement for controllers to visually monitor aircraft movement on the airfield.

Probable cause

The incident was caused by flight crew fatigue, exacerbated by high temperatures and operational delays, which resulted in the crew failing to confirm they were lined up on the correct runway.

Frequently asked questions

What happened in the 2014-05-22 Hawker Beechcraft 400XP accident near Al Maktoum International Airport, Dubai, AE?

A flight crew mistakenly initiated a takeoff roll on a taxiway instead of the designated runway at Al Maktoum International Airport, narrowly avoiding a serious incident.

What aircraft was involved and where did it happen?

The accident on 2014-05-22 involved a Hawker Beechcraft 400XP, registration AP-RBA, at Al Maktoum International Airport, Dubai, AE.

What was the probable cause of the accident?

The incident was caused by flight crew fatigue, exacerbated by high temperatures and operational delays, which resulted in the crew failing to confirm they were lined up on the correct runway.

Loading the flight search…