Runway Stop Bar Malfunction at Warsaw Chopin Airport

Casualties unknown • EPWA, PL

An Embraer 170 flight experienced an unnecessary delay at Warsaw Chopin Airport due to a runway stop bar remaining active after a change in lighting configuration.

What happened

On April 21, 2016, an Embraint 170 (E170) operating a scheduled airline flight was cleared to enter runway 29 at Warsaw Chopin Airport (EPWA). During the taxi process, the flight crew reported that a stop bar on taxiway E3 remained illuminated, despite the airport's lighting configuration having been switched from CAT II to CAT I.

This unexpected lighting state forced the aircraft to come to an unnecessary halt before the runway while the air traffic controller worked to resolve the issue. The incident was subsequently reported to the airport's Electrical Service.

The investigation

An analysis performed by the airport's Electrical Service examined the system monitoring logs. The investigation established that there were no hardware or software errors within the lighting control system itself.

Findings revealed that prior to the change in lighting scenario, the air traffic controller had manually deactivated the stop bar on taxiway E3 for a 25-second interval. During this 25-second countdown, the controller transitioned the lighting configuration from CAT II to CAT I. The investigation determined that the system's programmed algorithm does not cancel a pending command to reactivate a stop bar simply because a configuration change has occurred.

Findings

  • The primary cause was the timing of the lighting configuration change, which occurred while the system was in the middle of a programmed 25-second delay for the taxiway E3 stop bar.
  • The system functioned according to its programmed logic, which does not prioritize configuration changes over active countdowns for stop bar reactivation.

Safety action

  • The Polish Air Navigation Services Agency (PAŻP) confirmed that air traffic controllers operating the Touch Screen system have received training regarding the specific operational characteristics of the lighting control system.
  • The airport's Electrical Service is working to update the Touch Screen software to include operational counters, showing the remaining time until stop bars are scheduled to reactivate.

Probable cause

The incident was caused by changing the lighting configuration from CAT II to CAT I during a 25-second window when a stop bar reactivation command was already programmed to execute.

All Embraer ERJ-170 accidents →

Frequently asked questions

What happened in the 2016-04-21 Embraer 170 accident near EPWA, PL?

An Embraer 170 flight experienced an unnecessary delay at Warsaw Chopin Airport due to a runway stop bar remaining active after a change in lighting configuration.

What aircraft was involved and where did it happen?

The accident on 2016-04-21 involved a Embraer 170, at EPWA, PL.

What was the probable cause of the accident?

The incident was caused by changing the lighting configuration from CAT II to CAT I during a 25-second window when a stop bar reactivation command was already programmed to execute.

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