Southwest jet narrowly avoids colliding with business jet at Chicago airport

3 Likes

Some confusion from the get go on the FlexJet crew reading back taxi instructions and it didn’t end well. They reached the last layer of defense. Luckily SWA was heads up and went around. Major catastrophe averted. :open_mouth: And that right there is why we practice balked landings with less than 50 ft to touchdown (in rare cases touching down).

4 Likes

Normally I see these things and the proximity and danger are grossly exaggerated. It gets laughable but for the fact that people believe the hype and fly in fear. But this? This 50/50 would have been a fireball had the crew not punched it. Good for them. The jet also at least had the wherewithal to accelerate. Had SWA not gone around, I think it would have been a miss–but only just by feet.

5 Likes

IMO at best case it would have been like the incident last year where the Hawker wing-tagged the tail of the Citation Mustang while taking off without a clearance. :open_mouth:

1 Like
2 Likes

The angle of the video makes it look closer.
There is about 650m from the aimpoint to the intersection. Now, that’s too close - of course, but it looks worse in the rear angled video.

2 Likes

I wanna hear the Tower Convo, cause this is just another in a big stack of ATC Fails already in just 2 months into 2025.

1 Like

VASAviation has already posted it.

Also, I don’t think this one is really on ATC, quite honestly.

2 Likes

Definitely not on ATC. Heck the DCA accident wasn’t either. Their job is to tell us what to do. Our job is to comply. They are supposed to monitor compliance but only as a secondary responsibility when workload permits.

5 Likes

Listening to that I think it’s 100% on the Flexjet pilot. Now WHY he seemed to be so confused all the time needs an investigation because when it comes to “preventable” accidents, a pilot whose focus isn’t 100% on taxiing around a busy airport and following ATC has to be top of the list.
To me it sounds like he was holding 2 conversations at once, like he was on a phone or someone else was talking to him in the cockpit and his attention was divided. I don’t know if that jet has a CVR or not, because that would be important to catch.

Here’s a question–if it was proven that the issue was a passenger or someone else who was NOT the copilot was trying to talk to the pilot and not going away, what is the recourse? It’s the pilot’s responsibility but not really “fault” per se. Can the NTSB/FAA go after a passenger/no fly list them for something like that?

3 Likes

Sterile cockpit is the rule whenever the airplane is moving under its own power and until the parking brake is set. Distractions are ALWAYS the pilot in command’s fault. If distracted by a passenger, snake, topless tug driver, whatever, their only action is to stop and set the brake. Having said that, I had a runway infraction of my own 10 years ago at West Palm. We weren’t distracted. We misunderstood the instructions. What saved my bacon was a very honest and thorough sole-sourced report AND the fact the PBI has an odd taxiway layout around the terminal that generates above average infractions. Mistakes happen.

3 Likes

We’ve already have what 15 major incidents of collisions and near misses.

Deconflicting and managing airspace,
Most of these incidents have been because of ill-advised, last second, without checking, changes to instructions by ATC, and pilot mistakes. If the ATC wasn’t understaffed, many of the changes likely wouldn’t have happened, or would have been veto’d by another controller citing route confliction, if they were actually there to over watch the routes


in the case of PAT25/CRJ, ultimately despite all the other factors and missed cues, systems being off, the main preventing factor would have simply been, they not been there, and they were not supposed to be. Don’t make changes and expect or rely on pilots to mitigate other issues, just don’t put them in that position in the first place.

The CRJ was instructed to change to that runway during final, when the aircraft ON that runway should have been held short on the taxi, allowing the CRJ to land, and the airspace remain conflict free. Being short staffed, no one was there to think ahead and hold the other aircraft off the runway, to keep from having to re-route CRJ to RW 33, to land, while the other plane was taking off from the intersecting runway. Most of the busy airfields are straight up directing traffic on the fly, hoping everyone is perfect and doesn’t make mistakes, hears every radio call, and flies like a computer, or get lucky. The amount of near misses from pilot deviations could have been straight up prevented with better ATC or Ground Controller Management.

Moving the CRJ to runway 33 conflicted the routes from the get go. not only with PAT25 but the Aircraft on the other intersecting runway. Having a short staffed Controller crew led to several missed communications after the change, let alone that the change conflicted the routes.

In the case of the FlexJet, again, they were told to hold short, yes, but they were put into that route confliction position by the ATC’s instructions, they should have just held on the taxiway and not told to make the left turn onto the runway to cross another runway. better yet, the taxiway north and around the runway was clear, so why they didn’t put the Flex going around the perimeter taxiway instead of THRU multiple runways is beyond me.

And that’s not even getting into the recent incidents from the last 48 hours with planes running over ground vehicles or colliding with them.

:roll_eyes:

@SkateZilla this happens ALL the time. And it always has. I’ve been switched at DCA a dozen times—including the very RW change combo in the accident. Try changing from 15 to 19 when asked over the Pentagon!* Happens. I’ve done it. With three intersecting runways, there’s not much choice. You are totally correct about staffing. THAT is kinda new—an enduring symptom of the pandemic. But the complex use of and changes of runways is normal. Professionals deal with it. What wasn’t normal was for the Blackhawk to be well east of, and above its assigned visual route and called “in sight”. Easy solution to that one. Don’t allow visual separation at night.

*Worth mentioning I haven’t been to DCA in at least eight years. The unique MO of that airport goes way back.

2 Likes

Did the Flexjet’s ground check-in come across as sloppy or distracted to anyone else? My only official experience with phraseology is a semester of ground school I was observing for some linguistics research, and the phraseology they taught for the ground check-in always included current parking position and intention/request, and Flexjet communicated neither at first. That was the thing that leapt out at me for some reason. Seemed like the Flexjet’s cockpit was distracted.

But that ground school was the primary phase where they were going to be flying DA-20s in Arizona. Is commercial and IFR phrasology different?

The phraseology is the same for all—the AIM is the guide for all. I haven’t heard or read the transcript but to answer the general question, some common-sense brevity is beneficial. Normally it’s “Who are you? Where are you? Where do you want to go?” But if, say, UPS has one ramp at the airport and just one outbound exit from that ramp then “Hello Ground. UPS 123. Information ‘Papa’” might be perfectly acceptable.

1 Like