Cessna 172N Overruns Runway at Aleksandrowice Airport

Casualties unknown • Bielsko-Biała Aleksandrowice (EPBA), PL

A pilot failed to abort a takeoff attempt in sufficiently early, leading a Cessna 172N to overshoot the runway and strike a perimeter fence.

What happened

On September 7, 2018, a pilot prepared a Cessna 172N for flight at Aleksandrowice Airport (EPBA). Following standard pre-flight procedures, including engine oil checks, fueling to 93 liters, and weight and balance calculations, the pilot taxied to the holding point for runway 09. After performing a engine run-up, the pilot set the flaps to a 10° takeoff position and applied full power.

During the initial phase of the takeoff roll, the pilot noted that the aircraft was accelerating more slowly than expected. Despite this observation, the takeoff attempt continued. Between the halfway and three-quarters mark of the runway, the aircraft failed to reach rotation speed, prompting the pilot to initiate an aborted takeoff. The pilot reduced power to idle and applied the brakes; however, the aircraft began to skid on the locked wheels. Due to the high remaining speed and the short distance left on the runway, the Cessna 172N overran the runway end, struck a field fence, and came to a stop on the uneven grass terrain adjacent to the airport perimeter road.

There were no injuries to the pilot or the passengers, and all occupants evacuated the aircraft independently.

The investigation

The investigation, conducted by the operator's commission, examined the aircraft's technical condition, the pilot's flight experience, and the sequence of events during the takeoff roll. The investigation confirmed that the aircraft was airworthy, properly insured, and that its technical state did not contribute to the incident. The investigation also reviewed the pilot's credentials, noting a total of 95 hours and 30 minutes of flight time, including 33 hours of solo flight.

Findings

  • The primary cause of the incident was pilot error involving a delayed decision to abort the takeoff.
  • The pilot failed to initiate an aborted takeoff during the initial phase of the roll when the slow acceleration on the grass runway was first identified.
  • The high speed of the aircraft at the end of the runway, combined with the limited remaining distance, prevented a successful stop within the runway boundaries.
  • The impact with the fence and the subsequent stop on uneven ground resulted in damage to the propeller spinner, both propeller blades, the nose landing gear strut, the left aileron, and the engine cowling.

Probable cause

The pilot's failure to abort the takeoff at the first sign of insufficient acceleration led to the aircraft overrunning the runway.

All Cessna 172 accidents →

Frequently asked questions

What happened in the 2018-09-07 Cessna 172 accident near Bielsko-Biała Aleksandrowice (EPBA), PL?

A pilot failed to abort a takeoff attempt in sufficiently early, leading a Cessna 172N to overshoot the runway and strike a perimeter fence.

What aircraft was involved and where did it happen?

The accident on 2018-09-07 involved a Cessna 172, registration SP-FCB, operated by Pilot samolotowy, at Bielsko-Biała Aleksandrowice (EPBA), PL.

What was the probable cause of the accident?

The pilot's failure to abort the takeoff at the first sign of insufficient acceleration led to the aircraft overrunning the runway.

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

Loading the flight search…