Overview
On January 2, 2025, a Wizz Air Airbus A321-200N, registration 9H-WBI, operating flight W6-2068 from Milan Malpensa (Italy) to Krakow (Poland), was cleared to land on Krakow’s runway 25. During the landing, it was discovered that the runway was occupied by a departing Jet2 Boeing 737-800, registration G-JZBA, operating flight LS-950 to Manchester, England.
Poland’s State Commission for Aircraft Accident Investigation (PKBWL) has classified the incident as a serious occurrence and launched a formal investigation.
Key Details
• Aircraft 1:
• Operator: Wizz Air
• Type: Airbus A321-200N
• Registration: 9H-WBI
• Flight Number: W6-2068
• Route: Milan Malpensa (Italy) → Krakow (Poland)
• Aircraft 2:
• Operator: Jet2
• Type: Boeing 737-800
• Registration: G-JZBA
• Flight Number: LS-950
• Route: Krakow (Poland) → Manchester (UK)
• Date of Incident: January 2, 2025
• Location: Krakow John Paul II International Airport (EPKK), Poland
• Runway Involved: Runway 25
Sequence of Events
1. Landing Clearance:
• Wizz Air flight W6-2068 was cleared to land on runway 25 by Krakow Air Traffic Control (ATC).
2. Runway Occupancy:
• Jet2 flight LS-950, a departing Boeing 737-800, was on the same runway preparing for takeoff.
3. Landing:
• Wizz Air’s A321 proceeded to land on runway 25, unaware of the occupied runway.
4. Investigation Initiation:
• Poland’s PKBWL classified the event as a serious incident and began investigating the circumstances leading to the simultaneous occupancy of the runway.
Investigation Focus Areas
1. Air Traffic Control (ATC) Procedures:
• Review of ATC communication and coordination, including sequencing and clearance protocols.
2. Pilot Actions:
• Examination of adherence to clearance instructions and situational awareness.
3. Runway Safety Protocols:
• Assessment of airport procedures to ensure runway occupancy is clear before landing clearances are issued.
4. Safety Systems:
• Analysis of available runway incursion and occupancy alert systems, such as ASDE-X or A-SMGCS.
Potential Hazards
• Risk of Collision:
• A simultaneous presence of two aircraft on the runway posed a significant safety risk.
• Human Error:
• Miscommunication or procedural lapses between ATC and flight crews could have contributed to the incident.
• Operational Disruption:
• Such incidents can lead to delays, increased workload for ATC, and operational inefficiencies.
Safety Recommendations
1. Enhanced ATC Protocols:
• Ensure stricter monitoring of runway occupancy before issuing landing or takeoff clearances.
2. Runway Incursion Prevention Systems:
• Implement or upgrade safety systems capable of alerting ATC to potential runway incursions.
3. Pilot-ATC Coordination Training:
• Conduct recurrent training for ATC and pilots focusing on coordination and communication during critical phases of flight.
4. Runway Occupancy Visibility:
• Increase the use of real-time runway occupancy displays and procedures to confirm runway clearance.
Current Status
The investigation by Poland’s PKBWL is ongoing. Further updates will be provided upon the release of official findings and safety recommendations.
Disclaimer
This report is based on preliminary information available as of January 13, 2025. If you are the rightful owner of any associated media and wish for it to be removed, please contact takedown@cockpitking.com.
