Thursday, January 30, 2025
HomeAircraft AccidentsEAT Leipzig Airbus A300-600 Sustains Tail Strike During Go Around at Leipzig

EAT Leipzig Airbus A300-600 Sustains Tail Strike During Go Around at Leipzig

Date: February 9, 2024

Location: Leipzig/Halle Airport, Germany

Aircraft: Airbus A300-600 Freighter, registration D-AZMO

Operator: EAT Leipzig

Flight Number: QY-995

Route: Tel Aviv (Israel) to Leipzig (Germany)

Occupants: 2 crew

Injuries: None

Damage: Substantial damage to aircraft and runway

Summary of Events

On February 9, 2024, an EAT Leipzig Airbus A300-600 freighter, operating as Flight QY-995 from Tel Aviv to Leipzig, experienced a tail strike during a go-around from runway 26L at Leipzig/Halle Airport. The incident occurred at 17:54 local time (16:54Z) after an unstable landing attempt in crosswind conditions.

After the initial touchdown and a subsequent bounce, the aircraft banked to the right before both pilots initiated a go-around. During the maneuver, the aircraft’s tail contacted the runway, causing substantial damage to the lower fuselage and runway surface. The aircraft climbed out safely and landed without further incident on runway 26R about 20 minutes later. No injuries were reported.

Aircraft Details

• Type: Airbus A300-600 Freighter (A300F4-622R)

• Registration: D-AZMO

• Operator: EAT Leipzig (European Air Transport)

• Engines: 2x General Electric CF6

Sequence of Events

1. Outbound Flight:

• The aircraft departed Leipzig early on February 9 for a cargo flight to Tel Aviv, where it landed and was unloaded and reloaded.

2. Inbound Approach:

• The crew performed an ILS approach to Leipzig’s runway 26L in manual mode, with manual control of thrust levers.

• At 1,000 feet, the co-pilot (Pilot Flying) confirmed the approach as stabilized, and the landing checklist was completed.

3. Unstable Landing and Go Around:

• During the flare, the co-pilot attempted to align the aircraft with the runway in crosswind conditions.

• The aircraft touched down briefly at 17:54:31 but became airborne again, rolled to the right, and touched down a second time.

• Both pilots called “go-around” at 17:54:37, and the captain took over control, initiating a go-around with increasing thrust.

• During the maneuver, the tail struck the runway, damaging the aft fuselage and scratching the runway surface.

4. Safe Landing:

• The captain conducted a second approach and landed the aircraft safely on runway 26R at 18:12.

Initial Findings

• The approach was stabilized at 1,000 feet and continued under manual control.

• Crosswind conditions and alignment adjustments during the flare contributed to the instability.

• The tail strike occurred during the go-around sequence after the aircraft’s aft fuselage contacted the runway surface.

Safety Risks Identified

1. Crosswind Approach Challenges:

• Handling crosswinds during manual flare alignment posed a significant challenge.

2. Tail Strike Damage:

• Tail strikes can lead to structural damage and potential safety hazards in subsequent operations.

3. Runway Surface Damage:

• The incident resulted in physical damage to the runway, requiring repair.

Recommendations

1. Enhanced Training:

• Improve pilot training for crosswind landings and go-around procedures in manual flight conditions.

2. Stabilized Approach Criteria:

• Reinforce adherence to stabilized approach criteria, with stricter go-around policies for unstable landings.

3. Incident Review:

• Conduct a thorough review of operational procedures to identify and mitigate contributing factors to tail strikes.

4. Runway Repairs:

• Ensure timely repair of runway surfaces damaged during incidents.

Conclusion

This accident highlights the challenges of crosswind landings and the importance of precise handling during go-around maneuvers. The incident underscores the need for rigorous training and procedural reviews to prevent tail strikes and ensure operational safety.

Disclaimer

If you are the rightful owner of the photo and wish it to be taken down, please email takedown@cockpitking.com.

Our investigation reports are based on all the evidence and facts we have at the time of writing and posting. We apologise if any details are missed or are not fully accurate.

RELATED ARTICLES

Most Popular