Southwest B738 at Chicago on Feb 25th 2025, near collision with business jet on runway
Last Update: March 18, 2025 / 18:23:47 GMT/Zulu time
Incident Facts
Date of incident
Feb 25, 2025
Classification
Incident
Airline
Southwest Airlines
Flight number
WN-2504
Departure
Omaha, United States
Destination
Chicago Midway, United States
Aircraft Registration
N8517F
Aircraft Type
Boeing 737-800
ICAO Type Designator
B738
Airport ICAO Code
KMDW
A Bombardier Challenger 35 was taxiing for departure from runway 22L and was tracking runway 04L crossing runway 31C.
Tower was just about to instruct the Boeing to go around when the crew already reported they were going around. Later the crew queried how that happened but was instructed to contact approach.
The Bombardier was in contact with ground and had been instructed to hold short of runway 31C. Following the occurrence ground again advised their holding instructions had been to hold short of runway 31C, the crew was given a phone number for pilot deviation.
According to ADS-B data WN-2405 was in the flare only a few feet above the runway surface about 500 meters/1600 feet short of the intersection with runway 04L, when the aircraft began to climb again crossing the intersection with runway 04L at 780 feet MSL (about 150 feet AGL, transponder altitude reading 900 feet corrected for ambient pressure to 780 feet) about 7 seconds later.
Later the day the NTSB announced: "NTSB is investigating Tuesday's runway incursion that occurred when a Southwest Airlines Boeing 737-800 initiated a go-around after a business jet entered the same runway at Chicago Midway International Airport."
On Mar 18th 2025 the NTSB released their preliminary report summarizing the taxi of the Challenger as follows:
They indicated that they called MDW ground control and asked for taxi instructions from the signature ramp at “whiskey”, however, the crew stated the response they received did not make sense to them. They were initially given a clearance to taxi to runway 22L via F taxiway and to hold short of 4L. After the flight crew requested ground control to clarify the taxi instructions, they were given a new taxi route of taxiway A to taxiway F with a hold short of runway 04L/22R (figure 3). When they were on Taxiway F, ground control instructed them to turn left onto runway 04L, cross runway 31L and then hold short of runway 31C. The flight crew initially read back the instructions incorrectly; however, the ground controller immediately reissued the instructions and received a correct readback.
According to postincident statements, the flight crew of LXJ560 indicated that as they turned left onto runway 4L/22R, the sun was impeding visibility from the right side of the aircraft, however they did not recall seeing any hold short line/pavement markings or any other signs for the 31L intersection as they taxied onto runway 04L/22R. They stated that taxiway F and runway 13R/31L were in close proximity to each other and by the time the nosewheel had straightened out, they were likely halfway across runway 13R/31L. They further stated that runway 13R/31L appeared to have a very similar width to taxiways and that they had not recognized it as a runway. The captain stated that as he approached runway 13C/31C he had thought it was runway 13R/31L. As they approached the runway intersection the crew stated they both looked to the left and to the right and did not observe the SWA airplane on final.
As LXJ560 approached the hold short line for runway 31C the ground controller instructed LXJ560 to hold short, but the transmission was not acknowledged.
As they were crossing/exiting runway 13C/31C, they were contacted by ground informing them to hold position. The captain continued to clear the runway intersection and subsequently stopped the airplane so the tail was not over any part of the runway. Ground control requested they taxi forward to clear the runway safety area and then hold short of taxiway “H.” Once the captain cleared the runway safety area, he stopped the airplane and ground control informed them that they had crossed 31C and provided a number to call for a possible pilot deviation.
After about 5 minutes the crew was issued taxi instructions to continue on runway 4L/22R, turn left on taxiway “N” to “N2,” and hold in the north triangle. The captain once in the triangle set the parking brake, transferred control to the first officer, and contacted the tower via the phone number provided. He subsequently contacted the operator to notify them of the possible pilot deviation, assessed their well being to continue the flight, and subsequently departed about 25 minutes after the runway incursion. The rest of their flight was uneventful.
Metars:
KMDW 251453Z 34011KT 10SM FEW250 09/03 A2981 RMK AO2 SLP096 T00890028 51021=
KMDW 251353Z 31008KT 10SM CLR 07/03 A2980 RMK AO2 SLP096 T00670028=
KMDW 251253Z 27003KT 10SM FEW100 03/01 A2977 RMK AO2 SLP085 T00330011=
Aircraft Registration Data
Incident Facts
Date of incident
Feb 25, 2025
Classification
Incident
Airline
Southwest Airlines
Flight number
WN-2504
Departure
Omaha, United States
Destination
Chicago Midway, United States
Aircraft Registration
N8517F
Aircraft Type
Boeing 737-800
ICAO Type Designator
B738
Airport ICAO Code
KMDW
This article is published under license from Avherald.com. © of text by Avherald.com.
Article source
You can read 2 more free articles without a subscription.
Subscribe now and continue reading without any limits!
Read unlimited articles and receive our daily update briefing. Gain better insights into what is happening in commercial aviation safety.
Send tip
Support AeroInside by sending a small tip amount.
Related articles
Fleet type match
Southwest B738 at Orlando on Mar 20th 2025, attempted to takeoff from taxiway
A Southwest Airlines Boeing 737-800, registration N8315C performing flight WN-3278 from Orlando,FL to Albany,NY (USA), was cleared for takeoff from…
Fleet type match
Southwest B737 at Sacramento on Feb 8th 2025, engine issue
A Southwest Airlines Boeing 737-700, registration N288WN performing flight WN-2301 from Sacramento,CA to Denver,CO (USA), was climbing out of…
Fleet type match
Southwest B737 at Fort Myers on Jan 17th 2025, foreign objects on landing runway
A Southwest Airlines Boeing 737-700, registration N236WN performing flight WN-3009 from Atlanta,GA to Fort Myers,FL (USA), landed on Fort Myers's…
Fleet type match
Southwest B737 at Los Angeles on Dec 11th 2024, burst tyre on landing
A Southwest Airlines Boeing 737-700, registration N7831B performing flight WN-1011 from Phoenix,AZ to Los Angeles,CA (USA), landed on Los Angeles'…
Fleet type match
Southwest B737 at Long Beach on Oct 19th 2024, landed on occupied runway, 857 feet horizontal between aircraft
A Southwest Airlines Boeing 737-700, registration N250WN performing flight WN-1671 from Oakland,CA to Long Beach,CA (USA), was cleared to land on…
Newest articles
Fleet type match
21 B762 near Omaha on Mar 24th 2025, cabin pressure problem
A 21 Air Boeing 767-200 freighter, registration N999YV performing flight 2I-805 from Cincinnati,KY to San Francisco,CA (USA), was enroute at FL360…
Fleet type match
United A320 at Santa Barbara on Mar 22nd 2025, multiple bird strikes
A United Airbus A320-200, registration N457UA performing flight UA-671 from Denver,CO to Santa Barbara,CA (USA) with 150 passengers and 6 crew,…
Subscribe today
Are you researching aviation incidents? Get access to AeroInside Insights, unlimited read access and receive the daily newsletter.
Pick your plan and subscribePartner
ELITE Simulation Solutions is a leading global provider of Flight Simulation Training Devices, IFR training software as well as flight controls and related services. Find out more.
SafetyScan Pro provides streamlined access to thousands of aviation accident reports. Tailored for your safety management efforts. Book your demo today
AeroInside Blog
Popular aircraft
Airbus A320Boeing 737-800
Boeing 737-800 MAX
Popular airlines
American AirlinesUnited
Delta
Air Canada
Lufthansa
British Airways