ATC Error Leads To Close Call At Washington National Airport

There was a very close call this morning at Washington National Airport (DCA), and I’m sure this will be investigated closely…

Southwest Boeing 737 & JetBlue Embraer E190 incident at DCA

This incident happened today (Thursday, April 18, 2024), and involves two flights that were departing Washington National Airport. Specifically, this involves:

  • A Southwest Boeing 737 MAX 8 with the registration code N8710M that was scheduled to fly to Orlando (MCO) as flight WN2937
  • A JetBlue Embraer E190 with the registration code N323JB that was scheduled to fly to Boston (BOS) as flight B61554

VASAviation has an excellent video describing what happened, including both an airport diagram and the air traffic control audio. To summarize:

  • The JetBlue Embraer E190 was cleared to taxi into position and hold on Runway 4 by the tower controller
  • The Southwest Boeing 737 was then cleared to taxi to Runway 1 by the ground controller, and those instructions included being cleared to cross Runway 4, which is where the JetBlue aircraft was awaiting takeoff clearance
  • The JetBlue Embraer E190 was then cleared for takeoff by the tower controller, just shortly before the Southwest Boeing 737 was preparing to cross the runway
  • The JetBlue Embraer E190 and Southwest Boeing 737 were then both promptly told to stop, by both a ground and tower controller
  • Based on ADS-B data, when the planes stopped, the Southwest Boeing 737 was about 60 meters past the hold short line for the runway, and around 20 meters from the edge of the runway
  • The planes stopped at a distance of around 90 meters from one another; for context, a Boeing 737 is around 34 meters long

Following this incident, the Southwest Boeing 737 proceeded to the departure runway and took off. Meanwhile the JetBlue Embraer E190 ended up returning to the gate, and the flight ended up being delayed by hours.

I’m curious what an investigation reveals

This will no doubt be investigated, as this was a pretty close call that could have had a different outcome.

Air traffic controllers have really tough jobs, and they have to be right 100% of the time, or else there could be potentially fatal consequences. Add in how overworked they are, and I can’t help but feel bad for the profession.

As you can hear with the audio, different controllers gave the instructions to the two pilots, and obviously coordination was lacking, leading to this error. Fault lies with the controllers, as the pilots were simply following instructions.

I’m a little confused why the ground controller already cleared the Southwest jet to cross the runway so far in advance, given what a busy airport Washington National is. Is that standard policy at the airport, or did the air traffic controller misspeak, and forgot to say that clearance would be needed to cross the runway?

Here’s another thing I’m curious about, and I’d love to hear from pilots who have a more realistic sense of what you see in the cockpit. Pilots are obviously supposed to be vigilant, especially during ground operations, given how much can go wrong.

The Southwest 737 was crossing the runway around 1,000 feet from the end, where the JetBlue E190 was lined up. With decent visibility, would the Southwest pilots not have seen the JetBlue aircraft starting the takeoff roll, as they prepared to cross the runway? Or due to the angle plus how slowly planes start their takeoff roll, would they not have seen it in that way?

Kudos to all parties involved for their situational awareness, or else this could have had a different ending.

Bottom line

There was a close call at Washington National Airport this morning, as a JetBlue aircraft was cleared for takeoff at the same time that a Southwest aircraft was cleared to cross the same runway. Fortunately the error was caught just in time, and both planes managed to stop. I’m curious what an investigation reveals about how this happened…

What do you make of this incident at DCA?

Conversations (31)
The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.
Comment as a member

Membership is free and takes no more information than commenting as a guest. Earn status points for good contributions, and see fewer ads as your status grows.

Type your response here.

If you'd like to participate in the discussion, please adhere to our commenting guidelines. Anyone can comment, and your email address will not be published. Register to save your unique username and earn special OMAAT reputation perks!

  1. Loading comments…
Recent Comments
The latest from the OMAAT community.

The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.

Mary Guest

I assume the Jet Blue flight had to cool down but just curious how long that takes?

0
‼ 0
Elux Troxl Guest

Thanks for calling it Washington National.

1
‼ 0
Eilon Tal Guest

Without referring to a specific incident crossing an active runway should happen on Tower/local controller frequency. I believe it will get looked into. Also there are ground safety systems that alert ATC about such safety threats so they can immediate corrective measures. I wonder if those systems are working at Washington National.

0
‼ 0
Submarine Guest

I am genuinely disturbed by these comments and their focus and support for aviation safety. The FCC, per their official website, is focused on diversity candidates inclusive of “people with intellectual disabilities.” That is a far more noble and virtuous goal than your tired, old-fashioned emphasis on customer safety.

0
‼ 0
Anon Guest

"Is it policy at the airport". The "airport" doesn't dictate policy. Ground Controllers can coordinate runway crossings at any point. In slow periods, the Local (tower) Controller might even give up control of a runway to the ground controller for blanket crossings. Myriad of possibilities could've led to this... positions being split, controller change, etc... but most likely is that the local controller forgot they had coordinated. (Less likely is that the ground controller gave instructions to cross without coordinating) Our job is to prevent a collision. They did the job. Ideally it wouldn't have come to what happened. But this is ultimately a nothingburger that is just going to rile up people who don't know anything about the job. These articles and the publicity are going to make things worse, not better (actually, they already have made things worse). Overworked and underpaid.

2
‼ 0

Save posts to read later

Saving posts is a member feature. Become an OMAAT member to build a reading list you can come back to from any device.

Become a member
Meet Ben Schlappig, OMAAT Founder
5,883,136 Miles Traveled

43,914,800 Words Written

47,187 Posts Published