Private jet came ‘within 100 feet’ of colliding with Southwest plane, NTSB says
dallasnews.com
dallasnews.com
You can hear the Citation confirm and ask twice if they were still cleared to land, even after they were already cleared to land, so the Citation was gently nudging the controller that "hey, there's still an airplane on the runway."
It was a go around at the airport because of existing traffic on the runway. This happens all the time. Granted the controller got bogged down task wise, but the Citation knew it. I'd even bet you that the Alaska flight behind the Citation watched the whole thing go down with amusement.
> In the first two months of the year, eight incidents involving airliners on or near runways were rated by the FAA as a serious risk of a collision or prompted the NTSB to open an investigation. That’s almost double the annual average for the previous five years.
What's going on in control towers that's causing this? Did hiring standards for ATCs drop all of a sudden, or something like that?
- This particular ATC seems to be overloaded/distracted. She spend a lot of time providing adjusted altitudes to a waiting plane, while leave the SWA jet lined-up without clearance to take-off and a line of other planes on approach (two of which she had issued landing clearance).
Is this happening more often, or are recent events a random fluke? I don't know.
In general conditional type clearances have always been somewhat sketchy especially at busy airports where workloads are high.
IIRC, EASA requires the conditional to be explicit, with the condition named and read back, and both ATC and cleared plane to have visual on the conditional aircraft.
* Air traffic controller scabs during Reagan years are all retiring.
* Difficulty attracting and training new air traffic controllers, which takes years to do the training and is a high burnout job.
* Widespread effects of a virus that often causes cognitive damage, fatigue, and/or outright disability in many that's been circulating for almost 4 years.
I'm sure I'll be told differently any minute now, but... if I were a young person looking for a career, ATC is going to be very far down the list. Concerns about future automation will become a self-fulling prophecy once no humans are available to do the job.
It's a tough job that typically requires intense focus and rotation very very very regularly. Like 20mn to 2 hours "on frequency" at a time, depending on the airport and how busy it is. Working people long and hard, they are bound to make mistakes eventually.
Can anyone comment on this? It feels like a more believable explanation given they wouldn't be immune, especially given it's such a high stress job.
Partner is a FA, and can confirm that just about every department is understaffed and overworked. Unions can't strike due to Railway Labor Act and the current contracts under negotiations have been going for 2+ years...in which a lot has changed in the industry. There is little light at the end of the tunnel and my fear is that it will take one or more catastrophic incidents before something is actually done.
I haven't read it in full yet, the "What We Found" section seems to focus on training being paused during covid and a general lack of organization-wide tools and visibility around staffing.
I found that from this Forbes article: https://www.forbes.com/sites/suzannerowankelleher/2023/06/26...
The Forbes article suggests the problem began with the 2013 federal budget fight and resulting sequestration, which cut some programs and eliminated others.
https://www.cnbc.com/2014/12/15/blame-the-faa-for-air-traffi...
There was a fairly major change recently [1]. Before 2014, the FAA used to be biased towards recruits that had been already trained in a program on someone else's dime (military or university). Perhaps their on-the-job training isn't quite good enough to compensate for that change yet.
I'm surprised no one has mentioned it yet.
[1] https://en.wikipedia.org/wiki/Air_traffic_controller#2014_ch...
Starting pay is in the $43-$65,000 range (before location adjustments). In DC, that range is $57-$86,000.
Top of the range, non-management is $104-$161,000 (before location). In DC, that range is $138-$212,000.
Salary spreadsheet can be found here: https://www.faa.gov/jobs/working_here/benefits
Some high school friends drive for UPS (local package trucks). It's a solid income, but it's not a walk in the park either. They have quotas to meet. And late Fall through late Winter is a mad-house. That said, I believe they're union and both will be retiring well before me.
The UPS job is literally done by people in the top decile of physical fitness in the USA who are moving continuously and are so regimented that there's a "proper" way to carry the keys to the truck.
They're not really comparable in many ways.
That's a rule developed out of accident analysis, UPS drivers are trained to put the keys in their pocket as the first step of many procedures so that it becomes habit and they don't leave the truck running or create any possibility that someone will start it while the driver is away from the driver's seat.
It looks like the same ATC person lined up the southwest plane to take off and the private jet to land at the same time. Then realised and aborted at the last minute. Is that right?
The ATC should not have moved the south west plane onto the runway before the private jet landed. Correct?
(Edit: atrocious spelling)
In the EU / Canada this isn't allowed (landing clearance is only given if the runway is completely clear), but then the US pushes a lot more aircraft through its busy airspace this way. San Diego is a busy airport with just a single runway (due to the geography) near a couple of military bases and has a steep approach over the city - if there had been some ground fog like there often is at KSAN then this could have ended very differently.
Also, you can see in the video that due to the steep approach, the SWA was at the beginning of the runway, but the jet on approach would have landed further down, as the landing is offset there. This still would have be been dangerous but not a definite case of collision.
This is not uncommon for aircraft to get on the runway and take off while another aircraft is on final. If you want a good video of how this more typically works (and sometimes doesn't work), here's one from an incident at SFO about 2 months ago: https://www.youtube.com/watch?v=DrRGde5J8mo
And another from SFO: https://www.youtube.com/watch?v=E4cewwhcL5c
In both the SFO cases, they got the "go around" from ATC much earlier and no one got too close to each other. Keeping in mind that SFO is extremely busy and lands two parallel runways at the same time: https://www.youtube.com/watch?v=YsKhZm78DuY
This may be true overall, but San Diego is barely top-25 in the US in passenger traffic.
And Heathrow is busier (even measuring per runway, since it has 2). And both Gatwick and Mumbai handle more flights on a single runway.
Real error here was that SWA should have been told to hold short and then expedite as the SWA boys like to do after Citation was clear or to expedite from the getgo. Both would have worked just fine.
Also worth mentioning that while you can give landing clearance onto a runway that is not clear at the time, you still cannot have multiple aircraft on a given runway simultaneously, and there are very strict minimum separation requirements that vary depending on the airport which for KSAN is 5NM
https://www.youtube.com/watch?v=fWkYiJgaVFw
https://en.wikipedia.org/wiki/2002_%C3%9Cberlingen_mid-air_c...
https://www.youtube.com/watch?v=yiG3uiZWvUE for example.