Casualties unknown

Piper PA-31 Incident at Mielec (EPML): Landing on Taxiway (SP-FPK)

Mielec (EPML), PL

On December 27, 2017, a Piper PA-31 (registration SP-FPK) was involved in an aviation accident near Mielec (EPML), PL. Investigators recorded the probable cause as: Błędna decyzja pilota o lądowaniu na drodze kołowania, spowodowana trudnością w identyfikacji miejsca lądowania. This summary draws on records from the Polish State Commission on Aircraft Accidents Investigation (PKBWL); 8 related events involving the same aircraft type or operator are linked below.

Sourcesthe Polish State Commission on Aircraft Accidents Investigation (PKBWL)Primary reportUpdated 2026-09-13Data APIEditorial standards

On December 27, 2017, a Piper PA-31 landed on a taxiway at Mielec (EPML) due to smoke obscuring the runway. The pilot made an incorrect decision under visual constraints, resulting in an incident with no injuries.

Incident Overview

On December 27, 2017, a Piper PA-31 aircraft was involved in an aviation incident at Mielec Airport (EPML). The flight was a repositioning mission intended to hangar the aircraft for the winter season. The arrival had been previously coordinated with the hangar owner. Upon leaving controlled airspace, the pilot contacted the Automatic Flight Information Service (AFIS) and declared intentions to land.

Operational Context

The AFIS provided meteorological data and traffic information. Although operations were primarily on Runway 18 due to wind direction, the informant noted that Runway 09/27 was also available for landing. The pilot elected to approach Runway 18 and was instructed to enter a left-hand traffic pattern.

Contributing Factors

During the base leg of the traffic pattern, the pilot observed smoke from a factory located on the airport's southeastern boundary being blown by a wind from 170°. This smoke significantly obscured the view of Runway 18. The pilot could see most of the airfield, including both ends of Runway 09/27, and estimated the location of Runway 18 based on this visual reference. The pilot decided to continue the approach, planning to abort if necessary and land on Runway 09/27 with a crosswind.

Landing Sequence

Approximately 1.5 km from the airport, the pilot identified a paved road perpendicular to the axis of Runway 09/27 and aligned for landing. Due to sun glare during the final approach, the pilot's attention was focused on maintaining the glide path. On the short final, the pilot realized the selected surface lacked runway markings. Assessing the length, width, wind conditions, and terrain obstacles, the pilot determined there was insufficient time to locate Runway 18 or correct the approach. The pilot concluded that continuing the landing on the taxiway was safer than going around for a second circuit.

Conditions and Outcome

The landing occurred at 10:29 UTC. Conditions included a wind from 170° at 18 knots, a temperature of 8°C, and an aircraft landing weight of 5,250 lbs. The required landing distance was calculated at 1,150 ft (350 m), while the available taxiway length was approximately 450 m. No injuries were reported.

Investigation Findings

The investigation concluded that the incident was caused by the pilot's incorrect decision to land on a taxiway, driven by difficulties in identifying the intended landing site due to visual obstructions. The operator subsequently expanded pilot training modules to include uncontrolled airport procedures, runway identification, and decision-making processes for go-arounds.

Probable cause

Błędna decyzja pilota o lądowaniu na drodze kołowania, spowodowana trudnością w identyfikacji miejsca lądowania.

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