Boeing 777 Contacts Jetblast Fence During Dubai Pushback

Casualties unknown • Stand G17, Dubai International Airport, Dubai, United Arab Emirates, AE

An Emirates Airline Boeing 777-300 sustained damage to its aft fuselage after striking a jetblast fence and light pole during a non-standard pushback at Dubai International Airport.

What happened

On 19 October 2013, an Emirates Airline Boeing 777-300, registration A6-ENK, was being pushed back from Stand G17 at Dubai International Airport for a scheduled flight to Geneva. During the maneuver, the pushback operator initiated a left turn after the aircraft had moved only 10 to 15 feet along the stand centerline. This turn was intended to avoid potential wingtip contact with an aircraft parked at the adjacent stand. However, the movement placed the aircraft on a collision course with a jetblast fence protecting a service road. The lower aft fuselage of the Boeing 777-300 struck the fence, and the right-hand horizontal stabilizer subsequently hit a light pole. The impact caused damage to the fuselage, dislodged two static discharge wicks, and bent a light pole. The ground crew and flight crew were initially unaware of the contact, which was only discovered after a ground handling agent witnessed the incident.

The investigation

Investigators from the GCAA AAIS examined the pushback sequence and the operational procedures for Stand G17. The investigation focused on the visibility from the tug cab and the adherence to established protocols. It was established that the pushback operator and the headset mechanic were positioned in the tug cab, a location that prevented them from observing the aircraft's tail area or the proximity of the fuselage to the fence. The investigation also reviewed the training and familiarization records of the ground personnel involved.

Findings

  • The primary cause of the impact was the use of pushback actions that deviated from the established non-standard procedure for Stand G17.
  • The pushback operator failed to follow the correct procedure because approximately nine weeks had passed since they had last read the specific instructions for that stand.
  • Situational awareness was severely limited because the position of the headset mechanic and the pushback operator in the tug cab obscured their view of the aircraft's aft section.
  • There was a lack of a formal system to ensure operators were regularly familiarizing themselves with non-standard procedures.
  • The existing procedures did not mandate the use of wingwalkers or a specific briefing between the ground crew members for this constrained area.

Safety action

Following the incident, several safety measures were implemented, including:

  • The requirement for wingwalkers during all pushback operations at Stand G17 and similar constrained stands.
  • Updates to the ground handling agent's procedures to include laminated safety alerts and 'Read & Sign' mechanisms for all operators.
  • The installation of enhanced airfield markings, such as additional stop marks and reflectors, at Dubai International Airport.
  • The development of audio and visual training aids to improve personnel familiarization with non-standard maneuvers.

Probable cause

The incident was caused by the pushback operator's failure to adhere to the specific non-standard pushback procedures for Stand G17, compounded by limited visibility of the aircraft's tail area from the tug cab.

All Boeing 777-300 accidents →

Frequently asked questions

What happened in the 2013-10-18 Boeing 777-300 accident near Stand G17, Dubai International Airport, Dubai, United Arab Emirates, AE?

An Emirates Airline Boeing 777-300 sustained damage to its aft fuselage after striking a jetblast fence and light pole during a non-standard pushback at Dubai International Airport.

What aircraft was involved and where did it happen?

The accident on 2013-10-18 involved a Boeing 777-300, registration A6-ENK, at Stand G17, Dubai International Airport, Dubai, United Arab Emirates, AE.

What was the probable cause of the accident?

The incident was caused by the pushback operator's failure to adhere to the specific non-standard pushback procedures for Stand G17, compounded by limited visibility of the aircraft's tail area from the tug cab.

Loading the flight search…