A 737 at 100 feet. A business jet on the runway.

Southwest 2504 at Midway: how a Challenger crossed the runway in front of a 737 on short final

A Flexjet Challenger read back "hold short of runway 31C" and then rolled straight across it, just as a Southwest 737 was about to touch down. Follow it on the airport scope, decode the Ground and Tower radio as it happens, and see what the NTSB found.

What happened

On Tuesday, February 25, 2025, at about 8:48 a.m. local time, Southwest 2504, a Boeing 737-800 from Omaha, was landing on runway 31C at Chicago Midway when Flexjet 560, a Bombardier Challenger 350 taxiing out for Knoxville, crossed that runway in front of it. The Challenger had been told to hold short of 31C and had read the instruction back correctly. The Southwest crew went around and, according to the NTSB, passed less than 200 feet behind the business jet as it cleared the runway. Nobody was hurt; the 737 landed about 14 minutes later, and the NTSB is investigating.

Incident facts
Date and timeTue 25 Feb 2025, about 14:48Z (08:48 CST)
AirportChicago Midway International (MDW), landing runway 31C, wind 310° at 8 kt, clear skies
Aircraft 1Southwest 2504 (SWA2504), Boeing 737-800 N8517F, Omaha to Midway, 142 aboard, landing 31C
Aircraft 2Flexjet 560 (LXJ560), Bombardier Challenger 350 N560FX, Midway to Knoxville, 3 aboard, taxiing for runway 22L
Closest pointLess than 200 ft sideways between GPS antennas (NTSB preliminary report, from FAA-certified ADS-B); the report's figure shows the 737 at about 175 ft above the ground at 08:48:23 CST. Flightradar24 has no Challenger positions during the crossing.
ControllersMidway Ground (Flexjet 560), Midway Tower (Southwest 2504)
OutcomeGo-around, no injuries or damage; possible pilot deviation notice to the Flexjet crew; NTSB investigation DCA25LA141
Southwest 2504Boeing 737-800 · landing runway 31C
Flexjet 560Challenger 350 · taxiing on runway 4L · grey dot on the scope while on the ground
Midway Ground & TowerGround works the taxiing jet, Tower the landing one
Scroll to run the clock
MIDWAY TWR · MDW14:46:50Z
CONTROLLER INSTINCTS0 / 2
14:46:50Z The setup

How Midway's crossing runways work

Midway sits inside one square mile of Chicago, so its runways are packed in a criss-cross. This morning the wind is from the northwest, and jets land on runway 31C, the long diagonal running toward the top left. Runway 4L cuts straight across it, and so does the narrow 31L just to its south.

Why it's tricky

A jet taxiing from the west ramp to the far end of the field has to cross runways to get there. Every crossing is a separate clearance, and every hold short line is a hard stop until a controller says otherwise.

Minutes earlier A confusing start

The Challenger is at the Signature ramp on the west side, heading for runway 22L at the far end of the field. Its first exchange with Ground doesn't go smoothly.

Ground · to Flexjet 560

"Flexjet 560, roger, taxi via Foxtrot and hold short of runway 2-2 right. Plan for runway 2-2 left."

Take taxiway F, stop before runway 22R. You'll depart from 22L.

Flexjet 560 · to Ground

"And Ground, Flexjet 560, just wanna confirm our taxi instructions for 2-2 left from Signature."

That didn't make sense from where we're parked. Can you say it again?

Ground asks where they are and reissues the route: taxiways A and F, hold short of 22R. The Flexjet crew later told the NTSB the first instructions "did not make sense to them."

14:47:40Z The clearance
Ground · to Flexjet 560

"Flexjet 560, turn left on runway 4 left, cross runway 3-1 left and hold short of runway 3-1 center."

Turn onto runway 4L, go across the small runway 31L, then stop before the big one, 31C.

Read the scope

On the ground the Challenger is a small grey dot. Its route runs up runway 4L toward the top right, across 31L and then 31C. The amber target at the bottom right is Southwest 2504, about a mile from the runway, cleared to land on 31C by Tower on a different frequency.

14:47:56Z The readback

Why controllers make you read back "hold short"

Flexjet 560 · to Ground

"Alright, left on 4 left, cross 2-2… 1-3 center, Flexjet 560."

Left on 4L, cross… 13C? (That's the runway they were told to stop short of.)

Ground · to Flexjet 560

"Flexjet 560, negative. Cross runway 3-1 left, hold short of runway 3-1 center."

No. Cross the small one. Stop before the big one.

Flexjet 560 · to Ground

"Cross 3-1 left, we'll hold short of 3-1 center, Flexjet 560."

The safety net worked

Pilots must read back every hold short instruction word for word, and the controller must listen. Here Ground caught the wrong readback instantly and got a correct one. On the radio, everything was now right.

Freeze frame

It's 14:48:06Z. The 737 is a few dozen feet above the runway, per the NTSB. Which airplane is about to be somewhere it shouldn't? Tap it on the scope or pick below.

According to the NTSB, as the Challenger neared the 31C hold short line, the ground controller told it again to hold short. That transmission was not acknowledged.

Your call

You're the Southwest first officer. The airplane calls out "100." The business jet you assumed would stop is still rolling toward your runway. What do you say?

14:48:14Z Going around

What is a go-around?

Tower · to Southwest

"Southwest twenty…"

Southwest 2504 · to Tower

"Southwest 2504, going around."

We're not landing. Full power, climbing away.

Tower · to Southwest

"Southwest 2504, roger that, climb and maintain 3,000."

Not an emergency

A go-around is a normal, trained maneuver: abandon the landing, add power, climb, come back for another try. Any pilot can call one, and when the runway isn't clear it's always the right answer.

What the data shows

ADS-B shows the 737 lowest at 14:48:16Z, at 725 ft on the pressure-altitude scale, at about 130 kt. ADS-B reports pressure altitude, not height: on this morning's altimeter (29.80) Midway's runway sits at roughly 730 on that scale (our estimate), so 725 means the jet was just about at runway height. The NTSB's figure puts it at about 25 ft.

14:48:23Z Over the top

How close did the planes get?

The NTSB says Southwest 2504 passed less than 200 feet behind the Challenger as it cleared runway 31C. That's measured sideways between the two airplanes' GPS antennas. The NTSB's figure shows the 737 about 175 feet above the ground at that moment, climbing.

About this replay

Flightradar24's ADS-B feed has no Challenger positions between 14:47:41Z and 14:58:45Z, so we can't measure the gap ourselves. From its last fix on taxiway F, its dot here runs along runway 4L at a steady taxi speed to where the NTSB's figure puts it at the closest point. Southwest's track is its own ADS-B data.

14:48:24Z Stop

What is a runway incursion?

Ground · to Flexjet 560

"Flexjet 560, hold your position there."

Flexjet 560 · to Ground

"Holding position, Flexjet 560."

Ground · to Flexjet 560

"Flexjet 560, continue across and hold short, hold short of Hotel."

Pull forward clear of the runway area, then stop before taxiway H.

A runway incursion is any aircraft, vehicle or person on a runway where they shouldn't be. The captain told the NTSB he stopped with the tail clear of the runway, and Ground then moved him forward clear of the runway safety area.

14:48:45Z On frequency
Tower · to Southwest

"Southwest 2504, when able, turn left heading 2-2-0."

Ground · to Flexjet 560

"Flexjet 560, your instructions were to hold short of runway 3-1 center."

Southwest 2504 · to Tower

"And Tower, Southwest 2504, how'd that happen?"

The question everyone on frequency was thinking.

Tower doesn't answer it on the radio. It sends Southwest to Chicago Approach on 128.2 for vectors back around for another landing.

14:49:11Z The phone number

What is a Brasher warning?

Ground · to Flexjet 560

"Flexjet 560, possible pilot deviation, advise you contact Midway Tower at a number when you're ready to copy."

This will be looked into. Write down this number and call us.

Pilots dread this one

That scripted line is a Brasher warning, named after an NTSB case. It tells the crew the FAA may follow up, so they can write down what happened while it's fresh. It is the controller's report, not a finding.

The investigation What the crew said

Who was at fault?

The NTSB hasn't said; its preliminary report describes what happened, not why. The FAA said the business jet "entered the runway without authorization." The Flexjet crew told investigators:

  • The sun was impeding their view from the right side as they turned onto 4L, and they didn't recall seeing the hold short markings or signs for 31L.
  • Runway 31L is only 60 feet wide (FAA airport data), and to them it looked about as wide as a taxiway. They hadn't recognized it as a runway. By the time they straightened out they were likely halfway across it.
  • The captain thought 31C was 31L, the runway they were cleared to cross. Both pilots looked left and right and didn't see the 737.

Southwest 2504 landed at 15:02:47Z. The Challenger left for Knoxville at 15:13:55Z, about 25 minutes after the incursion (Flightradar24).

Takeaways

What this one teaches

A correct readback, clear skies, and still an airplane on the runway. Three lessons from Midway.

Listen

A readback is not a picture

The crew said "hold short of 31C" correctly, then mistook 31C for the runway they'd been cleared across. Knowing which runway you're looking at matters as much as the words.

Count

Count the runways you cross

Midway's 31L is taxiway-narrow and sits right beside taxiway F. When two crossings come close together, each hold line is a fresh decision.

Act

Go around early, go around always

The Southwest crew had seen the jet and expected it to stop. The moment it didn't, they went, and that call is why this is a near miss.

SectorLive

Try your hand at air traffic control.

Sit at a real radar position in Southern California, with real runways, real procedures and live traffic, and AI controllers in every other seat. It runs in your browser, free.

  • Keep jets 3 miles or 1,000 feet apart
  • Climb departures and turn them onto their routes
  • Hand them off cleanly to the next controller
Play free in your browser
Questions

Chicago Midway near miss: common questions

How close did Southwest 2504 come to the Flexjet Challenger?

The NTSB preliminary report says Southwest 2504 passed less than 200 feet behind the Challenger as it cleared runway 31C, measured sideways between the two airplanes' GPS antennas. The report's figure shows the 737 about 175 feet above the ground at that moment, already climbing in its go-around.

Who was at fault for the Midway near miss?

The NTSB has not given a probable cause; its preliminary report is the latest it has published. The FAA said the business jet entered the runway without authorization, and the ground controller gave the Flexjet crew a possible pilot deviation notice. The Flexjet crew read back the hold short instruction correctly and later told the NTSB the sun impeded their view and they didn't recognize the narrow runway 31L as a runway, so the captain took 31C for 31L.

What is a runway incursion?

Any time an aircraft, vehicle or person is on a runway where they shouldn't be. Here the Challenger was cleared to cross runway 31L and hold short of 31C, but it rolled across 31C while Southwest 2504 was landing on it.

Why did the Southwest pilots go around?

The crew saw a business jet taxiing toward their runway and expected it to stop. After the airplane's automated 100-foot callout, the first officer realized it was not stopping and called for a go-around, and the captain flew it, according to the NTSB.

What does "possible pilot deviation" mean?

The controller believes a pilot did not follow a clearance. Saying it on frequency with a phone number to call is the scripted notice known as a Brasher warning. It tells the crew the FAA may follow up; it is not a finding.

Was anyone hurt?

No. The NTSB reports no injuries among the 142 people on the Southwest 737 or the 3 on the Challenger, and no damage to either airplane. Southwest 2504 landed about 14 minutes later and the Challenger left for Knoxville about 25 minutes after the incursion.

Full transcript

Every word on frequency

Midway Ground and Tower, about 14:46Z to 14:49:28Z
EarlierFlexjet 560Flexjet 560, Signature with Tango.
EarlierMidway GroundFlexjet 560, runway… actually, departure frequency is 119.35. Runway 22L. What taxiway are you coming out of?
EarlierFlexjet 560We're over at Whiskey, Flexjet 560.
EarlierMidway GroundFlexjet 560, roger, taxi via Foxtrot and hold short of runway 22R. Plan for runway 22L.
EarlierFlexjet 560Alright, planning for 22L. Foxtrot, Whiskey, Flexjet 560.
EarlierFlexjet 560And Ground, Flexjet 560, just wanna confirm our taxi instructions for 22L from Signature.
EarlierMidway GroundWhere on the ramp are you, sir?
EarlierFlexjet 560We're at Signature Aviation, at Alpha… Alpha taxi.
EarlierMidway GroundTaxi Alpha, Foxtrot, hold short of 22R.
EarlierFlexjet 560Alpha, Foxtrot, hold short of 22R, Flexjet 560.
14:47:40ZMidway GroundFlexjet 560, turn left on runway 4L, cross runway 31L and hold short of runway 31C.
14:47:48ZFlexjet 560Alright, left on 4L, cross 22… 13C, Flexjet 560.
14:47:56ZMidway GroundFlexjet 560, negative. Cross runway 31L, hold short of runway 31C.
14:48:01ZFlexjet 560Cross 31L, we'll hold short of 31C, Flexjet 560.
14:48:11ZMidway TowerSouthwest twenty… [cut off]
14:48:14ZSouthwest 2504Southwest 2504, going around.
14:48:16ZMidway TowerSouthwest 2504, roger that, climb and maintain 3,000.
14:48:21ZSouthwest 2504Southwest 2504, up to 3,000.
14:48:24ZMidway GroundFlexjet 560, hold your position there.
14:48:26ZFlexjet 560Holding position, Flexjet 560.
14:48:30ZMidway GroundFlexjet 560, continue across and hold short, hold short of Hotel.
14:48:33ZFlexjet 560Cross and hold short of Hotel, Flexjet 560.
14:48:37ZMidway TowerSouthwest 2504, when able, turn left heading 220.
14:48:41ZSouthwest 2504Left heading 220, Southwest 2504.
14:48:45ZMidway GroundFlexjet 560, your instructions were to hold short of runway 31C.
14:48:54ZSouthwest 2504And Tower, Southwest 2504, how'd that happen?
14:48:59ZMidway TowerSouthwest 2504, climbing 3,000, contact Chicago Approach 128.2.
14:49:07ZSouthwest 2504128.2, Southwest 2504.
14:49:11ZMidway GroundFlexjet 560, possible pilot deviation, advise you contact Midway Tower at a number when you're ready to copy.
14:49:17ZFlexjet 560Flexjet 560, we're ready to copy.
14:49:19ZMidway GroundFlexjet 560, at [phone number].
14:49:24ZFlexjet 560Flexjet 560, [phone number].
14:49:28ZMidway GroundFlexjet 560, readback correct.

Radio audio is from LiveATC.net, published by VASAviation, which combines Midway Ground and Midway Tower. Times are estimated from the airport webcam clock shown in that video and may be a few seconds off; the recording may skip quiet stretches, so the calls marked "Earlier" are shown in order without times. The NTSB also reports a hold short call from Ground, not acknowledged, as the Challenger approached 31C; it is not in this recording. Southwest 2504's positions are ADS-B data from Flightradar24. The scope above is our own drawing of that data. Transmissions may differ slightly from the audio.

Evidence and references

Sources

Official incident record

  • NTSB preliminary report, DCA25LA141 (PDF). The source for the closest point (less than 200 ft, between GPS antennas), the 737's height in the report's figures, the taxi clearances, both crews' statements, the weather and the injuries. It is preliminary and subject to change; as of November 17, 2026 it is the newest report the NTSB serves for this case, and it gives no probable cause.

Incident audio and flight data

  • VASAviation: NEAR DISASTER, Southwest and Flexjet at Chicago Midway!, published February 25, 2025. The LiveATC recording of Midway Ground and Tower used for our transcript. This is a third-party publication of the radio audio, not an FAA report.
  • ABC7 Chicago, February 26, 2025. Quotes the FAA's statement that the business jet entered the runway without authorization, and statements from Southwest and Flexjet.
  • Flightradar24. The replay uses ADS-B positions for Southwest 2504 and Flexjet 560 on February 25, 2025, plus their landing and takeoff times. Flightradar24 has no Challenger positions from 14:47:41Z to 14:58:45Z, so its dot during the crossing is our reconstruction along runway 4L toward the NTSB's closest-point position, not ADS-B. This provider link is not a permanent archive of those tracks; the replay and timings are our analysis, not an official finding.

Primary FAA procedure references

These FAA links explain procedures; they are not incident investigation records and do not establish cause or fault. This breakdown is an educational reconstruction from the NTSB preliminary report, the published audio and ADS-B data. The linked FAA pages are maintained online and may change; they show current editions, not necessarily the text in force on February 25, 2025.