Matt Thurber, editor-in-chief at AIN Media Group, has been flying since 1975 and writing about aviation since 1978 and now has the best job in the world, running editorial operations for Aviation International News, Business Jet Traveler, and FutureFlight.aero. In addition to working as an A&amp;P mechanic on everything from Piper Cubs to turboprops, Matt taught flying at his father’s flight school in Plymouth, Mass., in the early 1980s, flew for an aircraft owner/pilot, and for two summer seasons hunted swordfish near the George’s Banks off the East Coast from a Piper Super Cub. An ATP certificated fixed-wing pilot and CFII and commercial helicopter pilot, Matt is type-rated in the Citation 500 and Gulfstream V/550. Based in the Pacific Northwest, Matt and his team cover the entire aviation scene including business aircraft, helicopters, avionics, safety, manufacturing, charter, fractionals, technology, air transport, advanced air mobility, defense, and other subjects of interest to AIN, BJT, and FutureFlight readers.

Editor-in-Chief

Matt Thurber

The NTSB has published a <a href="https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/199763/pdf">preliminary report</a> on the February 25 near-collision runway incursion involving a Flexjet Bombardier Challenger 350 and a Southwest Airlines (SWA) Boeing 737-800 at Chicago Midway International Airport (KMDW). The Aviation Investigation Preliminary Report noted that the “cockpit voice recorders for both airplanes were overwritten,” although the “SWA flight data recorder (FDR) and data from the Flexjet FDR were sent to the NTSB’s Vehicle Recorder Laboratory in Washington, D.C. for analysis.”
The incursion resulted in the SWA 737 crew aborting the landing on Runway 31C and performing a go-around after Flexjet Flight 560 (LXJ560) crossed the active runway in front of the 737. The 737 passed less than 200 feet behind the Challenger, according to the NTSB.
<figure role="group" class="caption caption-img">
<img alt="200 feet between each airplane" data-entity-type="file" data-entity-uuid="9d04ddf8-59a9-4afe-b766-63b7b834954d" src="/sites/default/files/inline-images/200%20feet%20between%20each%20airplane.jpg" width="1150" height="926" loading="lazy">
<figcaption>The NTSB calculated a lateral distance between each airplane's GPS antenna of about 200 feet.</figcaption>
</figure>

Clear weather prevailed as the SWA 737 crew flew the ILS approach to Runway 31C, with the captain as pilot flying and first officer (FO) in the pilot monitoring role. After shutting off the autopilot at about 500 feet, both pilots saw the Challenger “taxiing on a surface perpendicular to their runway and assumed it would be holding short of Runway 31C.” At 100 feet, when he heard the avionics call out the altitude, the FO “realized that the [Challenger] was not stopping and was going to cross onto Runway 31C. The FO stated that he called for a go-around and the captain executed it. The flight crew indicated that standard go-around procedures were applied, and the maneuver was executed smoothly and without incident.”
Parked at the Signature ramp on the west side of the airport, the Challenger crew had requested a taxi clearance and were given instructions that they later said were confusing, to taxi to Runway 22L via Foxtrot and to hold short of Runway 4L.&nbsp;
The airport diagram for KMDW shows that to get to Foxtrot, the Challenger would first need to taxi on Alpha, which is directly across from the Signature FBO. After requesting clarification, the ground controller cleared the Challenger to taxi on Alpha to Foxtrot then hold short of Runway 4L/22R.
<figure role="group" class="caption caption-img align-right">
<img alt="Blue line shows LXJ560's taxi route" data-entity-type="file" data-entity-uuid="55076e11-5034-4db8-a55a-e11562135bf7" src="/sites/default/files/inline-images/Blue%20line%20shows%20LXJ560%27s%20taxi%20route.jpg" width="596" height="566" loading="lazy">
<figcaption>The blue line shows the Challenger's taxi route.</figcaption>
</figure>

As they were taxiing on Foxtrot, the ground controller instructed the Challenger crew to “turn left on Runway 4 Left, cross Runway 31 Left, and hold short of Runway 31 Center.”&nbsp;(LiveATC.net captured this and the language in the following paragraph; the NTSB has not yet released the transcript from ATC recordings.—Ed.)&nbsp;
The Challenger crew responded: “Right, left on two, 4 Left, cross two two, er, one three, uh, Center, Flexjet 560.” The controller indicated that the readback was incorrect and repeated the instruction: “Flexjet 560, negative. Cross Runway 31 Left, hold short Runway 31 Center.” The Challenger crew responded: “Cross 31 Left, hold short 31 Center, Flexjet 560.”
In the preliminary report, the NTSB said that the Challenger crew reported in post-accident statements “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.”
In the&nbsp;<a href="http://liveatc.net/">LiveATC.net</a>&nbsp;recording of the ground control frequency around the time of the go-around, after the controller made other calls to various aircraft, a garbled transmission, likely being stepped on by another transmission, can be heard that sounds like someone is saying, “Flexjet 560 hold short, Flexjet 560” but it is not clear where that transmission came from.
The preliminary report acknowledges that the ground controller told the Challenger crew to hold short but it does not mention anything about the radio call being garbled. “As LXJ560 approached the hold-short line for Runway 31C the ground controller instructed LXJ560 to hold short, but the transmission was not acknowledged,” according to the NTSB.
A few seconds after telling the crew to hold short, the ground controller instructed the Challenger to hold its position but the captain continued taxiing across the active runway and then stopped after making sure the airplane’s tail wasn’t over the runway. The controller then asked the Challenger crew to taxi forward and hold short of Hotel then after they stopped, informed the crew that they might have a possible pilot deviation and to write down and call a phone number.
After taxiing to the north triangle area and making the phone call, the captain “contacted the operator [Flexjet] 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.”
The NTSB’s operational factors group and a human performance specialist interviewed the Challenger crew on March 4 and the SWA crew on March 13. The FAA provided certified ADS-B data and audio recordings to the NTSB. Midway Airport supplied photos of the runway environment “showing the runway signs (vertical white-on-red signs erected on either side of the runway hold-short position markings) and the hold-short line for runway 13C/31C.” The hold-short line is painted on Runway 4L, the runway on which the Challenger was taxiing.
<figure role="group" class="caption caption-img">
<img alt="Photos of the hold-short line for Runway 13C/31C" data-entity-type="file" data-entity-uuid="cbca1c64-3f52-4abd-a339-1b9dd4d5d25e" src="/sites/default/files/inline-images/Photos%20of%20the%20hold-short%20line%20for%20Runway%2013C%3A31C..jpg" width="670" height="466" loading="lazy">
<figcaption>Photos of the hold-short line for Runway 13C/31C.</figcaption>
</figure>

&nbsp;

News about significant aircraft accidents and information from accident reports.

NTSB Releases Prelim Report on B737-Challenger 350 Near-collision at Midway

Report notes the both airplanes' cockpit voice recorders were overwritten

The incursion resulted in the Southwest Airlines 737 crew aborting the landing on Runway 31C and performing a go-around after Flexjet Flight 560 crossed the active runway in front of the 737. 

NTSB Releases Prelim on B737-Challenger Near-collision

2024 Corporate Aviation Leadership Summit

Amy Wilder

News and issues relating to business, corporate and private aviation, primarily regarding turbine-engine-powered airplanes and helicopters. Subjects include aircraft, engines, maintenance, operations, personnel, acquisitions, accidents, safety, security, and training.

Crew noted anomalies before and after departure, investigation ongoing

NTSB: Citation II Right-seat Pilot Not SIC-qualified

David Jack Kenny

Preliminary and final accident reports, February 2026

Business Aircraft Accident Reports: February 2026

News and issues relating to international air transport and cargo carriers, national airlines and regional airlines, including aircraft, engines, personnel, acquisitions, accidents, safety, security and training.

More In Accidents

NTSB: Citation II Right-seat Pilot Not SIC-qualified

Crew noted anomalies before and after departure, investigation ongoing

Business Aircraft Accident Reports: February 2026

Preliminary and final accident reports, February 2026

NTSB Probable Cause Cites FAA Lapses in DCA Collision

Hearing resulted in 50 recommendations to the FAA, U.S. Army, and other agencies

CL650 Accident Investigation Continues at Bangor Airport

The airport has been closed since Sunday night

Fatal Challenger 650 Crash in Maine Claims Six

The accident occurred in freezing, snowy conditions

Business Aviation Safety Suffers Worst Year since 2011

143 people were killed in 35 business aircraft accidents last year

Business Aircraft Accident Reports: January 2026

Preliminary and final accident reports, January 2026

Stall Test in Icing Cited in 2024 Hawker 900XP Accident

Training gaps cited by NTSB

AIN Products

SUBSCRIPTIONS

RESOURCES

ABOUT AIN