Maintenance Oversight Error Leads to Exceeded Flight Hour Limit on Boeing 737 Flap Repair

Casualties unknown • EPWA baza techniczna, PL

A maintenance oversight involving data transfer errors between IT systems caused a Boeing 737 to exceed its authorized flight hour limit for a temporary flap repair.

What happened

On May 23, 2017, during a routine verification of technical logbook entries at the Warsaw (EPWA) maintenance base, it was discovered that a Boeing 737 operated by PLL LOT S.A. had exceeded its authorized flight hour limit for a permanent repair. The aircraft required a permanent repair to the right-hand inboard midflap following the discovery of a crack during a hangar inspection on May 6, 2017. The manufacturer had granted a temporary authorization for the aircraft to operate for a maximum of 100 flight hours (FH) following the initial discovery. However, by the time the discrepancy was identified, the aircraft had exceeded this limit by 14.51 flight hours.

The investigation

The investigation focused on how the flight hour limitation was not properly tracked within the airline's maintenance management systems. It was established that the maintenance organization used AMOS for defect logging, which then interfaced with the TRAX system (the airline's CAMO IT system). While the defect was correctly logged in AMOS, the specific technical authorization (ADD7038) regarding the flight hour limitation failed to transfer to the TRAX system.

During a manual verification of work package summaries on May 11, 2017, a maintenance employee incorrectly closed the defect in the TRAX system. This error occurred despite the fact that the information regarding the defect was present in the source system, leading to a lack of visibility regarding the expiring flight hour limit in the primary tracking system.

Probable cause

The primary cause was a failure in the data interface between the AMOS and TRAX maintenance systems, which prevented the transfer of specific flight hour limitations. This was compounded by human error during the manual verification of work packages, where a maintenance employee incorrectly closed the defect in the tracking system.

All Boeing 737-800 accidents →

Frequently asked questions

What happened in the 2017-05-23 Boeing 737 accident near EPWA baza techniczna, PL?

A maintenance oversight involving data transfer errors between IT systems caused a Boeing 737 to exceed its authorized flight hour limit for a temporary flap repair.

What aircraft was involved and where did it happen?

The accident on 2017-05-23 involved a Boeing 737, registration SP-LLE, at EPWA baza techniczna, PL.

What was the probable cause of the accident?

The primary cause was a failure in the data interface between the AMOS and TRAX maintenance systems, which prevented the transfer of specific flight hour limitations. This was compounded by human error during the manual verification of work packages, where a maintenance employee incorrectly closed the defect in the…

Investigation report by the Polish State Commission on Aircraft Accidents Investigation (PKBWL). Original record: https://pkbwl.gov.pl/raporty/2017-1018/. 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.