There was a very close call this morning at Washington National Airport (DCA), and I’m sure this will be investigated closely…
In this post:
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?
I assume the Jet Blue flight had to cool down but just curious how long that takes?
Thanks for calling it Washington National.
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.
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.
Speaking of intellectual disabilities, your mention of the FCC here suggests you might have one.
Oh do sush. I’m so bored of people constantly bringing diversity into this when they have exactly zero idea of what happened. But sure, let’s use any excuse to kick minorities. The way some people go on, you’d think white men have never made any mistakes.
Check your privilege, boomer. We are today, you are yesterday.
FCC, hahahahaha. Stopped reading right there.
So the FCC won't let me be, let me be me so let me see, they tried to shut me down on MTV but it feels so empty without me.
Just wait until all these people screaming DEI find out that White Male Veterans Over 40 are included in those DEI initiatives.
"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...
"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.
Looking at the video my only guess is that someone thought the outbound Southwest was the one already across JetBlues path.
We’ve flow that B6 route to MCO like 6 times last year. And my wife left out of DCA on another WN flight this morning. I’ll just not mention this and go hyperventilate a little.
A surprising number of metres in this report.
Is Washington DC an island of metric measurements in the "imperial" USA?
Is OMAAT shifting to being more international-minded?
Or is it just that this was drafted by a non-American intern?
Probably taken from the illustrative video that's linked in the article.
Metric is the international Standard, as is English.
Is metric "woke?"
LOL!!!!!!!!!!
Meters is the ICAO standard for lateral measurement in aviation (runway lenghts, visibility etc) Feet for vertical (Height, altitude )
Assuming the SW jet was taking off from the South end of Runway 1 and flying Norith ( the cartoon picture shows that) and the JetBlue jet was on the West side of Runway 4 to travel East - SW would not be able to see the JetBlue Jet - terminals and other jets taxing from the terminal would block the view.
Incorrect. In fact the taxiing SW jet was angled in such a way they were more or less looking directly at the JetBlue aircaft with nothing in between (no buildings or other jets, DCA is a very small airport). Remember this involved the SW plane that was on the taxi and crossing runway 4, not the Southwest plane waiting for takeoff clearance on runway 1 (who also would have a clear view of Runway 4 aircraft as well)
Scary. Genuine question- why did B6 suffer such a long delay after the incident? Hot brakes?
Yes. The E190;has a setting called RTO. Rejected takeoff. It’s aggressive. Those brakes were showing amber on the gauge or possibly red. The B6 procedure requires the meter to be green for takeoff. It’s a checklist item at B6.
Also curious as to why the Jet Blue flight parked for 15 minutes and then decided to go back to the gate. Does the sudden braking do something to the plane?
Likely passengers wanted to get off. It’s traumatic for some. That’s an aggressive deceleration.
The correct terminology should be:
"Human Error".
Removing human error from the system is long overdue.
Off the shelf technology to replace these repetitive tasks are already available widely.
Hopefully that will work out better than the self-driving cars.
Why isn’t it mandatory to have indicators when a runway is active at all airports?? And sync with onboard controls?
Would prevent so many of these issues
thankful that there were two alert, skilled and fast acting sets of pilots.
It seems like there is one weak link in all of these near disastrous incidents but 2 links manage to save the situation.
I imagine if the pilots were alert, they would've stopped before they were told to (in spite of the controller error).
I do hear at least 3 different ATC voices involved in stopping the two aircraft.
Not to place any blame on the pilots, just refuting this weird take.
As Ben notes, there is plenty of reason to ask what the WN pilots saw... a plane taking off just a few thousand feet away should have drawn attention.
Let's see what the investigation shows but I suspect the FAA will find it hard to deflect blame from their own error.
From what I observe when a plane is ready to begin it's roll takeoff lights go on. If the JetBlue plane had it's lights on wouldn't that be warning to the Southwest pilots? As someone that flys 2-4 times a week delays seem to be getting worse and worse. I have no doubt airlines play games to make their delays look better (like changing a schedule by a few minutes and giving a new flight...
From what I observe when a plane is ready to begin it's roll takeoff lights go on. If the JetBlue plane had it's lights on wouldn't that be warning to the Southwest pilots? As someone that flys 2-4 times a week delays seem to be getting worse and worse. I have no doubt airlines play games to make their delays look better (like changing a schedule by a few minutes and giving a new flight number) because there's no way in hell AA is having an ontime rate of 80%, or any other airline. That has to weigh on crews constantly running behind and trying to make up some of the time. Many of those pilots feel for the hardship it causes passengers. But with 40-50 minute domestic turn times, packed planes and congested airports and skies it just becomes one big cluster.
DC has the busiest runway in the US, handling >800 movements per day. And that was last year, not sure what this year's numbers look like. We're (DC-area denizens) lucky that there hasn't been a major ground incident considering how tiny the airport is for the volume of traffic it handles (flights and pax).