Hard Landing of Embraer E170 at Warsaw Chopin Airport

Casualties unknown • EPWA, PL

An Embraer E170 experienced a hard landing at Warsaw Chopin Airport, which subsequently went undocumented, leading to several subsequent flights without required technical inspections.

What happened

On February 15, 2012, an Embraer E170-200 was operating a scheduled flight from Brussels to Warsaw (EPWA). During the approach to runway 11, the aircraft was configured with flaps 6, operating in conditions with a 1,000-meter visibility and a 13-knot wind from 150 degrees.

Flight data recorder analysis revealed that while all flight parameters were normal until the flare, the crew performed the flare too late. This resulted in a hard touchdown with a vertical load of 1.89g, followed by the aircraft bouncing off the runway for approximately one second before a second touchdown occurred, generating a vertical load of 2.29g. Following the landing, the captain verbally informed a mechanic of the suspected hard landing and requested that the aircraft not be released for flight until the Digital Voice Data Recorder (DVDR) was reviewed. However, the crew failed to make the required entry in the aircraft technical log (LDP 60) or file an Air Safety Report (ASR).

The investigation

The investigation established that the aircraft continued operations for several subsequent flights, including routes to Sofia and Helsinki, before any technical inspection was initiated. Although flight parameter data was read by the Flight Parameter Analysis Department shortly after the aircraft arrived from Brussels, the processed files were not uploaded to the server until 10:19 UTC, and an email notifying technical services of the hard landing was not distributed until 17:49 UTC.

By the time the technical inspection process began at 23:15 UTC on February 15, the aircraft had already completed four additional landings. The first phase of the special inspection was not completed until the early hours of February 16, and the second phase of the inspection was not performed until February 20, at which point the aircraft was cleared for normal service.

Findings

  • The primary cause of the hard landing was the late execution of the flare and improper control of the aircraft following the initial bounce.
  • The delay in performing required special inspections was caused by the failure to record the event in the technical log and the delayed communication of flight parameter data by technical services.
  • Atmospheric conditions at Warsaw Chopin Airport acted as a contributing factor to the landing event.
  • The delay in notifying technical services was exacerbated by a significant lag in the distribution of DVDR analysis results, which took over eight hours to reach the relevant departments.

Probable cause

The hard landing was caused by a late flare and improper recovery from a bounce, while the failure to conduct timely inspections resulted from inadequate documentation by the crew and delayed data processing by technical services.

Frequently asked questions

What happened in the 2012-02-15 Embraer E170-200 accident near EPWA, PL?

An Embraer E170 experienced a hard landing at Warsaw Chopin Airport, which subsequently went undocumented, leading to several subsequent flights without required technical inspections.

What aircraft was involved and where did it happen?

The accident on 2012-02-15 involved a Embraer E170-200, at EPWA, PL.

What was the probable cause of the accident?

The hard landing was caused by a late flare and improper recovery from a bounce, while the failure to conduct timely inspections resulted from inadequate documentation by the crew and delayed data processing by technical services.

Investigation report by the Polish State Commission on Aircraft Accidents Investigation (PKBWL). Original record: https://pkbwl.gov.pl/raporty/2012-0130/. This page is a structured re-presentation; facts and quotes are in the Panstwowa Komisja Badania Wypadkow Lotniczych (PKBWL), Poland.

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 40,000+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.