Same. Making sure not to let complacency creep in with switching to another frequency or something else.I have been thinking about these incidents on my 4 day trip a lot. Lots of crossing runways this trip and although we are always normally vigilant while crossing, I placed a lot of extra focus on it. Sadly it is starting to look like this is where our next accident will be.
Yep! Likely sooner than later. LAS has been seeing a lot more of these as well as an increase in go arounds due to ground traffic.Anyone get the feeling we’re eventually going to run out of luck with these incidents? It seems like they’re becoming an almost daily thing.
Yep! Likely sooner than later. LAS has been seeing a lot more of these as well as an increase in go arounds due to ground traffic.
I have been thinking about these incidents on my 4 day trip a lot. Lots of crossing runways this trip and although we are always normally vigilant while crossing, I placed a lot of extra focus on it. Sadly it is starting to look like this is where our next accident will be.
Anyone get the feeling we’re eventually going to run out of luck with these incidents? It seems like they’re becoming an almost daily thing.
It seems like an awful lot of these incidents happened simultaneously to the point where something systemic may be going on with the NAS. I didn’t mean to be critical of the controller (we’re all one mistake away from a YouTube video being made about us) and I think it’s way too oversimplified to be like “*shrug* guess ATC sucks all the sudden”, because coordinating runways crossings is a regular thing that’s been done safely and consistently for decades. I’m more inclined to think that a lot of links in the chain happen to be lining up (coordination procedures, controller fatigue rules changes, new controller workforce with less experience and not enough trainers, chronic understaffing, etc) and I hope the FAA is doing some frantic internal root cause investigation and reflecting on what they need to change (spoiler: they’re probably not).
All the more reason to keep asking for any shortcutsControllers are overworked, understaffed, and dealing with more traffic than ever before.
Had that "feeling" for quite some time now. It's an "every man for himself" world these days, lads... This zeitgeist applies not only to economic issues, but to every part of our "society". Act accordingly. Remain vigilant.Anyone get the feeling we’re eventually going to run out of luck with these incidents? It seems like they’re becoming an almost daily thing.
Incidentally, LAS is getting a new airport.
Decades in the making, the new airport south of Las Vegas is back on track
There's a new airport on the way south of the Las Vegas Valley.knpr.org
It's hard to really know. It's only recently that people are somehow hearing these incursions and posting them same day. Any statistics I've seen do not show a drastic increase... Obviously the data for this year will be interesting to check.I’m glad to hear you guys are reflecting on this stuff and being careful. What was especially crazy to me about this incident over the others was that frontier was the only ones who noticed something was wrong, and everybody else (both controller and other pilots) carried on business as usual.
It seems like an awful lot of these incidents happened simultaneously to the point where something systemic may be going on with the NAS. I didn’t mean to be critical of the controller (we’re all one mistake away from a YouTube video being made about us) and I think it’s way too oversimplified to be like “*shrug* guess ATC sucks all the sudden”, because coordinating runways crossings is a regular thing that’s been done safely and consistently for decades. I’m more inclined to think that a lot of links in the chain happen to be lining up (coordination procedures, controller fatigue rules changes, new controller workforce with less experience and not enough trainers, chronic understaffing, etc) and I hope the FAA is doing some frantic internal root cause investigation and reflecting on what they need to change (spoiler: they’re probably not).
But barring that, you guys all be careful out there because it does feel like we’re on the precipice of luck running out. Keep monitoring the radio and trying to build the mental SA picture, and keep trusting the little voice in your head if something seems wrong or your spidey senses are tingling. You can always set the brakes.
"There is no authority except facts. Facts are obtained by accurate observation."I’m glad to hear you guys are reflecting on this stuff and being careful. What was especially crazy to me about this incident over the others was that frontier was the only ones who noticed something was wrong, and everybody else (both controller and other pilots) carried on business as usual.
It seems like an awful lot of these incidents happened simultaneously to the point where something systemic may be going on with the NAS. I didn’t mean to be critical of the controller (we’re all one mistake away from a YouTube video being made about us) and I think it’s way too oversimplified to be like “*shrug* guess ATC sucks all the sudden”, because coordinating runways crossings is a regular thing that’s been done safely and consistently for decades. I’m more inclined to think that a lot of links in the chain happen to be lining up (coordination procedures, controller fatigue rules changes, new controller workforce with less experience and not enough trainers, chronic understaffing, etc) and I hope the FAA is doing some frantic internal root cause investigation and reflecting on what they need to change (spoiler: they’re probably not).
But barring that, you guys all be careful out there because it does feel like we’re on the precipice of luck running out. Keep monitoring the radio and trying to build the mental SA picture, and keep trusting the little voice in your head if something seems wrong or your spidey senses are tingling. You can always set the brakes.
I have been thinking about these incidents on my 4 day trip a lot. Lots of crossing runways this trip and although we are always normally vigilant while crossing, I placed a lot of extra focus on it. Sadly it is starting to look like this is where our next accident will be.
Maybe I'm wrong, but when tower clears us to cross and switch to ground, I don't ever do the switch until we are very obviously either clearing the runway or nothing is lined up on the active we are crossing. I'd much rather be up on primary freq if something weird happened, rather than relying on guard (which by then we probably aren't monitoring anymore).
For many years, takeoffs were “cleared for takeoff, change to departure”; so the takeoff would be on departure freq. Not sure if the USN did similar for the tac jets.