Pilot here: I'd bet you 100 bucks the Citation had the Southwest 737 in sight the entire time while on the approach, and knew exactly what was going on. There was almost certainly little to no danger of a collision. When on a visual approach like this you are literally watching the runway the entire time.
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.
If the Citation pilot had the southwest plane in sight when they reached the decision height and kept going, rather than go around, wouldn’t that be an error on their part?
> The Federal Aviation Administration said in June that it would start mandatory monthly safety training sessions for air-traffic controllers across the U.S. after a spike in near misses.
> 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?
A few things related to this incident...
- The US allows landing clearance to be granted on occupied runways. It also allows landing clearance to planes who aren't next-to-land. This invites this sort of problem and, IIRC, isn't normal (or allowed?) in the EU.
- 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.
Not sure why this is being upvoted. ICAO doesn't expressly forbid line up and wait clearances with someone on final approach. In fact they're quite common in the EU. They're often conditional though (eg; "BEHIND the landing aircraft".) Pilots can mistake the aircraft being referred to, etc.
In general conditional type clearances have always been somewhat sketchy especially at busy airports where workloads are high.
You're correct, EASA allows conditional clearances ("clear to land after departing plane clears runway"). But the linked event was not a conditional clearance. The approaching jet was cleared to land, meanwhile the ATC got distracted and left the SWA jet on the active runway without clearance to take-off.
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 find it odd that you're basically reiterating my third point and yet you're the one getting downvotes, presumably because you actually used the "C" word. The level of denial about mass disablement (temporary, semi-temporary, or permanent) just gets more and more ridiculous.
Downvotes are sometimes given to short comments that don't add anything extra to the thread. That might be the case here as your original comment was quite clear.
Also seems that this is one of the easiest jobs to automate in the future. Keep planes from running into each other. How hard could that be? If a computer can drag a 9-dan Go champion up and down the board, it can do this.
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.
Ah yes I can't wait until some LLM instructs a plane to go to a runway that doesn't exist, and the pilot can't ask for clarification because the airport fired all the humans because "we don't need them"
Hmm, that doesn't sound like an optimal implementation. Can you think of any other approaches for handling air traffic (no pun intended) besides using AI language models?
In the video of the incident linked elsewhere there is a caption that basically says that an automated system is what notified the controller there was an issue and probably why she was able to correct it at the last second.
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.
Honestly, given that you're seeing labor shortages in just about every industry, I have to imagine that labor shortages probably play a role in ATC being overworked?
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.
Edit: missed the part about the tower controllers specifically, but the below still holds I think.
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.
The Forbes article suggests the problem began with the 2013 federal budget fight and resulting sequestration, which cut some programs and eliminated others.
They also have a mandatory retirement age (56) and afaik, a lot of the more seasoned ATCs are getting near that age. Article from 2014 that touches on this, and goes into more depth about some reasoning.
> 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?
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.
Since it’s government they can’t raise wages to attract talent so they keep going lower and lower down in standards until at some point they can’t even find people to meet the required minimum
The mean annual wage is $130,840 according to the BLS. That's two times the national mean of $61,900. There are very few occupations where the mean can compete with Air Traffic Control in terms of take home pay.
That’s not that much money anymore for high stress low quality of life work. UPS driver and railroad worker wages are in the same range And people don’t really want those jobs either
From UPS's website, the average package delivery driver earns $140k in total comp (incl. benefits). The average long-haul driver is $170k.
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.
Yep, that's what I meant by "it's not a walk in the park" - it's physically demanding labor. My friends are mid-40s, it will be interesting to see when they retire.
One job is sitting in a chair in an air-conditioned room using your brain to track detailed information.
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.
> there's a "proper" way to carry the keys to the truck
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.
I was referring to the "hold the keyring on the pinky finger" method but just read that UPS now has key fobs which the driver attaches to the belt, saving 2 seconds per stop...
Slightly unrelated, but my brother is working at UPS now and is making decent income. He went to a coding bootcamp 2 years ago and has had absolutely no luck finding a front end web dev position. I'm just glad he has a stable and well paying job for now, though I hope he finds his way to doing something else that's more sustainable for him, especially since he is beginning to have issues with his back. Maybe his best bet is finding a web dev job (or a dev job in general) within the company itself, since usually inside hires are preferred.
The underlying issue is public roles are heavily budget restricted. If the role pays well, administrators often have to reduce headcount as the trade off.
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?
I think the plan was for the Southwest to be given take off clearance quickly before the private jet arrived, but the controller got distracted by a route amendment for another flight that came in and they got their priorities wrong. In the US it's not uncommon for a 'Cleared to Land' to be given while something is then lining up and waiting for immediate Take Off clearance.
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.
Yea. The incoming jet was on a 5-mile final. Being a small jet it's "slow" so that 5-mile final is 3-5 minutes. You can see 19:04Z when the Southwest jet get's the "line up and wait". 19:07Z is the missed approach. If ATC has given them the departure clearance relatively quickly, there would have been no issue as Southwest would have hit the gas and been long gone... but ATC didn't.
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
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
They don't land planes at KSAN in the fog, because of the steep decent. So it would have ended very differently, because that Citation would have been diverted elsewhere.
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
That's true. But in this case no one was avoiding anyone, since neither knew the other one was there. And it's not exactly 3d when your both using the same runway. More like 1d...
From some of the calls I have listened to(engines failing, landing gears failing, close calls, etc...), it is incredible how composed the parties involved are! As much as some people point the finger at one person in the situation, the important thing is that these incidents are an opportunity to learn, and that is something the aviation industry seems to do very well.
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.