NTSB Issues Preliminary Report on Midway Near-Collision

The National Transportation Safety Board (NTSB) has posted its Preliminary Report on the runway incursion and near-collision involving a Flexjet Challenger 350 and a Southwest Airlines Boeing 737-800 at Chicago Midway Airport (KMDW). The February 25 incident saw Southwest Flight 2504 (SWA2504) on final approach execute a last-minute go-around from just above the surface as the Challenger taxied across Runway 31C directly in its path. On climbout from the maneuver, the Boeing passed approximately 200 feet behind the tail of the Challenger after it had crossed the runway and was directed to hold its position by ground control.


This is a companion discussion topic for the original entry at https://www.avweb.com/aviation-news/report-expores-last-second-go-around-at-chicago-midway-airport

Does anyone know of FlexJet uses an electronic checklist? The CL30’s Proline 21 avionics displays a full screen, geo-referenced Jeppesen airport diagram with a green depiction of one’s position on the airport. Using the built/in electronic checklist removes the airport diagram from the screen, replacing it with the checklist. Doing so is a huge loss of situational awareness, and why some operators prohibit the use of the electronic checklist. By utilizing that geo-referenced diagram, there is no question regarding one’s relative position on the airport surface. And if one doesn’t understand the taxi instructions, stop, and request clarification.

Perhaps the pilot never heard of requesting progressive taxi? I’ve requested it many times. Especially at unfamiliar airports I’ve gone to.

The 10-9 chart is up and in view prior to contacting ground. The projected taxi route is briefed, including threats. Then contact ground. But what was the root cause of this near tragic incident? Poor company training. Poor intra company NOTAMs for special airports, airspace, navigation? Poor crew coordination, CRM, Cockpit Disciplines? Great for SMS for the company to jump on to prevent future incidences. On another note, reference to the fact the crew was blinded by the sun and unable to see Yellow/Black RWY Hold Lines and White on Red RWY Identifier Signs? I’ll leave it there… However those involved are entitled to their day before the investigation board and the administrator for due process.

I hope the FAA and NTSB are as critical about themselves as they are about the FJ crew.

3 years ago a Skywest RJ came face-to-face with a snow plow at KAPN TWO DAYS IN A ROW!!!. You would have thought the airline and airport operator would have learned a valuable lesson after the first day. Both flights were as close to the plow, on the emergency go around, as Southwest was to FlexJet at MDW. Both flights would have been fatal had the RJ not gone around. But in the end no one cared about little ole KAPN. After 6 months of investigation the FAA swept both incidences under the rug because there were “no violations” of any regs. Apparently deaths can only happen if regulations are broken.

Did you know that an employee must have drug screening in order to dump a toilet on a commercial aircraft, yet no drug screening is required of those driving or managing snow plows, on our main runways!

Maybe the FAA could improve safety at MDW by allowing half the air traffic to be on UHF while the other half is on VHF. Seems to have worked well a DCA.

Does MDW have RWSL ( Runway Status Lights) installed? If not, why not?

When was the hold short line for 31C painted on rwy 4L? Google earth doesn’t show that.

  • No Punitive Action:

The FAA will not use ASRS reports for disciplinary or other adverse action, as long as the reported violation was inadvertent.

The crew probably filed NASA reports.

Your mention of other incidents is irrelevant in this situation. All surfaces are clearly marked and indicated by signs along the assigned route.

Look at the FR24 satellite view.

This topic was automatically closed after 7 days. New replies are no longer allowed.