ATR 42 Tail Strike During Night Pushback at Lyon Saint-Exupéry

Casualties unknown • FR

An Airlinair ATR 42-500 struck a blast fence during a night pushback maneuver, resulting in damage to the aircraft's tail cone.

What happened

On the night of January 27, 2009, an ATR 42-500, registration F-GPYD, operated by Airlinair, was undergoing a pushback maneuver at Lyon Saint-Exupéry Airport. The flight, a scheduled passenger service bound for Rouen, was slightly delayed. During the procedure, the flight crew requested the start of engine number one while the aircraft was still being pushed back.

As the maneuver progressed, the ground crew experienced a sudden halt. The headset operator, focused on monitoring the engine start, did not immediately realize the aircraft had struck an obstacle. The crew also failed to identify the impact, as they mistakenly attributed the sudden jolt to a previously experienced issue involving a tow bar fuse. The collision was only identified after a third-party ground agent, positioned on the other side of a blast fence, signaled that an anomaly had occurred. Upon inspection, the ground crew discovered that the aircraft's tail cone had struck the blast fence, resulting in approximately 50 centimeters of damage to the cone dome.

The investigation

The BEA investigation examined the configuration of the parking stand, the ground crew's performance, and the cockpit procedures. Investigators found that the white stop marker, which should have indicated the limit for the nose gear, had been erased during recent pavement repairs. Furthermore, the blast fence, which was relatively tall due to nearby buildings, lacked any lighting at the time of the incident.

Technical reviews of the ground crew's composition revealed that the tug driver was working with a relatively inexperienced headset operator who had only been performing these duties for six weeks. The investigation also noted that the driver felt overwhelmed by the simultaneous requirement to manage the pushback and monitor the engine start requested by the crew.

Findings

Several contributing factors led to the collision:

  • The engine start during pushback significantly increased the workload of the ground crew, diverting the headset operator's attention away from monitoring the aircraft's surroundings.
  • The absence of the white stop marker at the parking stand removed a critical visual reference for the tug driver.
  • The lack of lighting on the blast fence made the obstacle difficult to perceive during the night maneuver.
  • The flight crew's haste to recover from a delay contributed to the decision to start an engine during the pushback.
  • The ground crew's inability to recognize the impact was compounded by the crew's misinterpretation of the physical jolt as a recurring mechanical issue.

Probable cause

The collision was caused by the ground crew's loss of situational awareness due to an increased workload during an engine start, exacerbated by the lack of a visual stop marker and unlit obstacles.

Frequently asked questions

What happened in the 2009-01-27 Bureau d’Enquêtes et d’Analyses pour la sécurité de l’aviation civile Zone Sud - Bâtiment 153 200 rue de Paris Aéroport du Bourget 93352 Le Bourget Cedex - France T : +33 1 49 92 72 00 - F : +33 1 49 92 72 03 www.bea.aero Incident survenu le 27 janvier 2009 sur l’aérodrome de Lyon Saint-Exupéry accident near FR?

An Airlinair ATR 42-500 struck a blast fence during a night pushback maneuver, resulting in damage to the aircraft's tail cone.

What aircraft was involved and where did it happen?

The accident on 2009-01-27 involved a Bureau d’Enquêtes et d’Analyses pour la sécurité de l’aviation civile Zone Sud - Bâtiment 153 200 rue de Paris Aéroport du Bourget 93352 Le Bourget Cedex - France T : +33 1 49 92 72 00 - F : +33 1 49 92 72 03 www.bea.aero Incident survenu le 27 janvier 2009 sur l’aérodrome de Lyon Saint-Exupéry, at FR.

What was the probable cause of the accident?

The collision was caused by the ground crew's loss of situational awareness due to an increased workload during an engine start, exacerbated by the lack of a visual stop marker and unlit obstacles.

Loading the flight search…