Plane Takes Off WHILE ANOTHER ONE is CLEARED TO CROSS the same runway at Las Vegas!
HTML-код
- Опубликовано: 8 апр 2024
- Your support is really important and appreciated to keep these videos coming! =)
-- / vasaviation
-- paypal.me/VASAviation
Become a VIP member of VASAviation! -- / @vasaviation
Flying Eyes 10% OFF: flyingeyesoptics.com/?ref=Vas...
Join VASAviation's Discord -- / discord
Twitter/Facebook/Instagram -- @VASAviation
Audio source: www.liveatc.net/
Please, give a big LIKE to support and for more videos like this!! :)
KUDOS to that Frontier Pilot for his on top situational awareness... "How is a guy being cleared for takeoff on 26R if I'm about to cross it."
1st reply
F9 did NOT follow instructions. But..to “error on the side of caution” is acceptable. Just not what ATC had planned or expected.
I just wish the pilot had identified “26” instead of mistakenly calling it “25”…still, great awareness. Very encouraging.
bit he also got told to HOLD SHORT ? so... yeah
Well, it was runway 25 until August 2017, maybe he's been flying in Vegas for a while.
Pilot in 2517 was Extremely professional.
First of all, he had situational awareness and reacted to the the conflict.
Second of all: He did not say anything(!) about this, until he was over and the most important communication was ended. Everything is recorded so no rush to point it out straight away and mess other important things up.
This. I think (I don't know, I am not involved with aviation) that it's crucial to get past any possible conflict before raising an issue that could have caused an immediate stress reaction in someone who is responsible for many lives. Get everyone on the same page, make sure immediate danger has passed, then when quieter say "hey, we need to raise an issue".
I do wonder what kind of disciplinary action is taken towards controllers?. This is your typical "Pilot Deviation Scenario" if it was the other way around.
+1!
But he was also covering his ass. ASAP report time....
@@diaphanoux Retraining.
Hey tower, this is frontier, say when ready to copy a number
Excellent work from the pilot on FFT2517. Situationally aware and took action when something didn't sound right. Potentially lots of lives saved. I suspect the controller thought he'd instructed them to hold-short instead of cross. Altogether seamlessly caught and fixed. Very well done and very professional way to bring it to the controller's attention.
Potentially that, although they did mention the aircraft holding in position. It's possible the controller got mixed up from the other aircraft calling ready at 26L. Or simply the fact that they're at opposite ends of a big runway and the controller simply forgot he told them to cross. It's amazing how quickly past information can leave your mind when you're in a fast-paced environment (and perhaps fatigued or not at your 100%).
But yes perfect job from 2517.
@@rabidtangerine yeah, that's a great theory too.
That or moving stuff around as quickly as possible, and thought FFT2517 would have crossed fast enough by that point (an assumption I wouldn't make but well, I'm not the controller either), considering the high speed exit taken, if I'm not wrong on that.
Too risky in my opinion, glad the crew in FFT2517 was thinking quickly there.
I was expecting him to say "Possible Tower deviation"
Ha ha! Never heard that one before.
Do you have a pen ready to write pilot’s number?😊
"When ready to copy, I have a number."
Tower needed more incoming telephone lines lately. 😅
Then followed by the number to Truck Masters😂
Classic LAX Nightmare Scenario...
Great Capture Victor!
LAS nightmare scenario, as it were ☝️
@@manifestgtrthis exact same scenario could play out in LAX, and is more likely there even though this was LAS
What's our vector, victor?
@@abowden5079
ROGER
@@JGB1990it could play out at ORD, ATL, CDG, anywhere that has pairs of parallel runways, like this. Not as likely at DEN, as the runways are laid out and used in a way that you don’t have to cross a runway on your way in. For instance, if two planes are landing on the 16s, the plane on 16R, would taxi down and around the opposite end of 16L. On the other side, landing on 35R, you taxi down and around the end of 35L. Sometimes you’ll have a plane land on 17R, and one take off on 17L, taxi for takeoff on 17L is just the opposite of landing on 35R, going around the end.
The pilot was clearly shaken. In fact, you can clearly hear him call the runway "25 R" instead of "26 R", twice. That suggests he's quite familiar with LAS because the current runway 26 R was indeed called 25 R until 2017.
26 and 25 are 10 degrees difference
@@cibularas3485 They probably changed the name due to the natural change of Earth's magnetic poles, which are used to number the runways. This suggests the pilot has been flying at that airport for a long time.
Likewise the old FAA terminology 'position and hold' when explaining the incident to the ground controller. We all revert back to instincts/basic training when under stress.
@@cibularas3485 26 and 25 can be as close as 1º difference only
@@cibularas3485 you round it to the nearest decade. Earth's magnetic field drifts with time, so periodically runway numbers have to be updated accordingly. Let's say that particular runway in 2016 was making an angle of 254.9 degrees with the magnetic nord. The closest decade is 250, so its number would have been 25. Now, in 2017 such angle might have increased to 255.0 deg which must be rounded up to 260, making the proper name 26.
That was perfection on the pilot’s part. Calling up to let them know they effed up without saying “you effed up” and actually even kind of posing it as a “did I hear everything correctly” inquiry. He likely knew exactly what was happening but that was a good, non-escalating way to frame it for the initial contact. No need to stir the pot on frequency…
This is why we don’t blindly cross active runways without checking. Just because a controller crosses you doesn’t mean it’s clear. I did a go-around years ago because an MD80 crossed my landing runway when I was about 300’ from touchdown. Kudos to the Frontier pilot.
Being an aviator is not unlike being a golfer. They self-report ( the honest ones ) their errors and hold other duffers accountable. I like it.
Good thing Frontier 2517 was still on tower freq even after being told to switch to ground, to hear the takeoff clearance and the last moment hold short. "Tower, I have a number for you to call." A lot of voices on here could be reading out the fine print advisories on ED commercials...
I believe that instruction usually meant cross runway THEN contact ground.
@@edNdr Yep....good job on the Frontier pilot - cross runway and contact ground...so he stayed on frequency until he was across the runway.,
@@edNdrHere in AMS it is always the instruction ‘after crossing contact’ … you never cross an active runway on ground freq.
Very well handled from the Frontier pilot, not only did he appreciate what was happening and stop, he waited until all the communications had died down before querying it, most importantly though he stayed on the tower frequency until he'd crossed the runway before switching to ground...
Las Vegas Tower hold, Hold, HOLD!!!!
I don’t understand why this happened
I’m a atc for reference, and controller here had no rush to depart the first aircraft as after its departure he lines up a 2nd one.
If there was a aircraft getting close on final I’d understand.
But I’d still prioritize “Frontier (callsign) cancel runway crossing clearance, hold short of rwy 26R” then give take-off clearance but as mentioned earlier this doesn’t seem to be the case
Good on Frontier Pilot listening out on the frequency
There may be traffic landing the crossing runway, 19R, behind Sun Country. We hear him ask them to exit at Y, which frees up 26R for Spirit to depart. Spirit would need to be through the 19R intersection before the next arrival crosses the threshold. I’m don’t mean to make excuses for the error; he obviously fell for the age-old “hit-the-gap” trap. But there’s obviously context that the clip is missing.
You're " a ATC" ??? right! 🤣
True. You obtain the hold short instruction first, then you clear the other guy for takeoff….
@@nickcarey4566 There was no "hitting the gap". He clears Frontier 2517 to cross 26R, clears the Spirit 396 for takeoff, then tells Frontier 2517 to hold short. After the Spirit 396 takes off and clears Frontier 2517 to cross 26R, he tells Spirit 2123 to line up and wait. Nowhere after he clears Spirit 396 for takeoff do you hear about any aircraft landing on the crossing runway, unless they trimmed the audio.
@@NICU_Guywell yes while we don’t hear a mention of inbound traffic, I find it interesting the “No delay” in take of clearance as usually in my tower use that only if we really need to depart someone. It could’ve been that the atc wanted to depart both of the Spirits prior to a arrival and for that to work the first had to expedite its departure
Buuuut it’s also America and some things are very different compared to the EU
I’m sure the controller got a discussion with the supervisor about that. It’s good thing he did stop the frontier or if he didn’t, spirit would have had to cancel take off clearance quickly.
Frontier already was stopping before being told to. He says this in the video you've just watched.
@@MarkPentlerno the controller told him to hold short once he cleared spirit to take off
@@carygutnick8284by that point the frontier had already stopped of its own accord. Listen to the pilot at the end again.
@@carygutnick8284 literally just watch the video and you'll first hear the takeoff clearance and then the hold-short instruction, then the pilot will repeat what happened to the ground.
The pilot at the end said that he had already breaked when he was told to hold short of runway @@marcellkovacs5452
Sometimes it is better not to hurry crossing runways.
Isn't it SOP to look both ways before crossing a runway?
@@JMcC64 Yes, but if traffic is lining up and holding on the runway while you start crossing, you can't just make your plane disappear when holding traffic gets a takeoff clearance.
Especially when your last command was to hold short, and your copilot acknowledged it.
Ideally and I do it but there’s a bad culture of folks that will give you a TON of grief for it. The FAA needs a revamp just like Boeing.
@@RetreadPhoto Frontier was only told to hold short *after* the other plane was cleared for takeoff. They had initially been told to cross the runway, then Spirit Wings 396 was cleared for takeoff on the same runway, and THEN the tower remembered Frontier was there and told them to hold short (which they'd already done on their own because they heard the takeoff clearance issued).
At this point they all know this will end up at this channel anyway 😂
ATC gets his "Fifteen minutes of fame"
In the past decades we saw nasty shit happening after saying "cross the runway and contact ground". That's why now we keep the tfc in contact on TWR frequency 'till he vacates the runway. Main EU airport ATC here.
Hey, maybe the Frontier x Spirit merger woulda happened anyway!
Oh shit
Damn lol. And this one would've technically been FAA approved!
Controller knew he messed up. He was trying to keep it under the radar hoping nobody would say anything.
Nope…ATC instructions to “keep it rolling,cross 26R, and contact ground …point 1=121.1 does NOT mean stop and hold short at the A6 Hold Short Line. 80% of the time, you HOLD SHORT right there with the Tower.
Done that EXACT Runway crossing 100s of times. F9 stopped when he should have “kept it rolling” and crossed 26R then contact LAS GRD in 121.1. No harm, no foul. ATC is very good in KLAS and keep ‘em rolling.” Classic “Expectation Bias”
@rodcoulter997 I don't know, if the pilot kept rolling but hadn't made it to the crossing runway yet and then heard a clearance for the other plane to takeoff, that's definitely worthy of stopping. Maybe he slow rolled it and threw off the cadence of the flow but whatever, it's been a S show out there lately (everywhere).
@@rodcoulter997I am not a pilot, but if a plane got permission to cross, not other plane should have permission for takeoff at the same time.
Sometimes, you get a landing clearance while another plane is on the runway, that is ok, because when you reach the runway, it will be clear (or your clearance will be revoked).
But takeoff clearance in this situation? I do not think, this was the correct way to do it...
@@rodcoulter997 Are you sure about that? FFT2517 pilot said he was about to cross the hold short line when the other aircraft was given takeoff clearance. What if he hadn't jumped on the brakes when he did and ATC had instructed him to hold short while he was halfway across?
@@jonesjones7057100% agree..80% of the time, end up stopping and HoldShort at A6 or A7 with the Tower. Better on the side of caution. Not faulting either ATC or the FlightCrew. “Expectation bias on both sides”…
Excellent job by the Frontier pilot listening out on the frequency for potential conflicts.
Low key they tried to sweep it under the rug. You can hear the controller issue a new holding clearance at 0:46. He messed it but fixed it later. Now if FFT2517's cap wouldn't have been proactive and would've actually followed the first instruction they would've been in the middle of the runway by the time they stopped. Kudos on those guys for monitoring tower and stomping on the brakes.
Pilot was right, he got cleared to cross 26r, then ATC told the other pilot to takeoff, and only THEN did ATC tell frontier to hold short (which it could have been too late to do). Good looking out pilot
It's even worse. He told him to hold short on a frequency he'd already told the pilot to leave (to cross over to ground)! This was so nearly an accident.
ATC did clear frontier to cross before clearing spirit to take off and changing frontier's instructions. Good job on the frontier crew catching that before spirit started rolling and avoiding a dangerous conflict.
By stark contrast to the recent New York incident of a similar nature, this is a perfect example of why all runway movements MUST be given on the same frequency. It allows one hole in the Swiss cheese to be closed when pilots can be situationally aware what is taking place.
Mistakes happen, we're all human. Allowing an opportunity for those mistakes to be spotted is vital, as demonstrated here by an extremely professional and observant flight crew. Kudos to them for the way they handled it.
100% on the tower, he told 2517 to cross 26R, then cleared the plane holding in position on 26R to take off, luckily 2517 was paying attention
Great situational awareness by that pilot 🎉
If unsure, hold short. Good awareness by frontier.
Really heads up awareness by that flight crew. It takes a village. Controllers can make mistakes too. Turn an avoided tragedy into a learning experience.
Yup. Nothing wrong with his ears.
Your vids are great. Thanks for all your hard work
Thank you for watching
ATC, formerly, rarely screwed up. Now it is a several times/day occurrence. Be on your A game at all times pilots! Only a matter of time until the chain breaks.
Why do you think this is happening? Dependence on tech? Training? Something else? Curious to get insights from someone who has done the job.
@@commerce-usa The standards are much lower than they used to be. I'll leave it at that.
I mean, with the FAA understaffing, mandatory over time, 6 day work weeks, ofc there are gonna be problems. Controllers aren’t able to take breaks like they used to, barely having any time to rest, especially in busier airspace. Until the problem is resolved you’re gonna see the evidence of the burnout. Unfortunately the FAA won’t care until people really get hurt.
@@icedandcorrectedchannel1236 This is it right here. Controllers are working 6 day weeks, sometimes all of them 10 hour days. Facilites are short staffed so breaks are short and don't come as often as they should. Because of the staffing issue some facilities are just "pushing" people through even though they may not be ready yet. The schedule they work isn't great, 9 hours between the quick turn shifts which realistically you might get 6-7 hours of sleep between. There are a lot of "issues" but the FAA/NATCA refuses to address them.
I also think you just didn't hear about it as often because no one had a channel like this dedicated to every little (or huge) mishap. 😊
He sure did. Pilot was correct and was great at being proactive!
The different voices for 2517 make this a bit tricky to understand. Sounds like maybe the first officer was handling the communications, 2517 did the right thing by holding short when instructed to "keep it rolling," then the captain called the tower to point out the conflict?
Definitely the Captain having that conversation with Ground
That's what I'm gathering. It's what I would've done. "Hey man... I got ATC for a second I want to ask him exactly what happened."
The controller realized he messed up and told the 2517 to hold short after letting the other plane roll, but dear lord. He just muttered out the hold short instruction and didn't seem to say it with any urgency whatsoever, like it was just another Tuesday for him. Quite shocking. Usually in situations like this, when controllers spot a conflict late, they'd at least raise their voice and yell at one of the crew to stop.
@@rinleezF9 had already stopped, urgency was 0, CYA was not 0.
@@qwerty112311 What the hell is CYA? F9 may have stopped, but you can't read minds and you don't know what they're gonna do next.
Listen to ALL communications!!! Those who do, like this crew who did, save lives!!
Frontier was 100% right!
Local controller for sure got in trouble for that one... Ouch. Good job on the pilot for active listening right there.
I once was cleared to land on 18 in a C152, 1 mile final. Then they cleared a Piper to land to 36. I called back and they confirmed my landing instructions. At a half mile out I saw the Piper Turbine Meridian exiting the runway! They had plenty of time to get that fast plane ahead of me.
One probable contributing factor to this is that LAS is overcrowded and gets very congested several times every day. It's entirely conceivable that the tower controller was trying to clear a backlog of 10+ departures while approach is handing him arrivals with minimum separation. Throw in the clearance referencing taxiway Y which indicates the crossing runways are also in use (and being worked by the same controller!) to further complicate things, and that's a lot of pressure to keep everyone moving.
Gotta do it right. Getting it done quickly is secondary and optional.
These are problems that managers and companies need to worry about. ATC needs to slow things down and not fold under pressure by suits.
this is why humans should be removed from the loop, controller computers should talk directly to aircraft autopilots
I was waiting for that pilot to say "Tower, Frontier 2517, standby to copy down a phone number". Very well handled by the Frontier crew!
I wonder if ATC screw-ups were always this common, and if it's only because of RUclips and VASAviation, etc. that we're finding out about scary situations like this.
Props to the Frontier pilot. Situational awareness
pilot: "tower, when you have a moment I have a number for you to call"
Kudos to the SPIRIT pilots to remain professional while passengers are relieving themselves in the aisles 😂
Well if the plane animation is correct that frontier pilot taxied slow AF. It’s called a high speed. Tower says keep going you keep going. Once tower found how how slow they were going he told them to just hold short. Freaking pay by the hour airline guys. Always freaking slow.
The animation being correct or not, the high-speed is the exit (to squeeze landing traffic behind) but not for the following taxiways. Mi aircraft, my taxi speeds. No way I am putting my aircraft in danger because ATC says "keep it rolling"
Wow some people here arguing just for arguing’s sake. Frontier was given a clearance by ATC to keep going and cross rwy 26R. Then ATC cleared the other flight for takeoff on rwy 26R without first telling the Frontier plane to hold. It was after the takeoff clearance was given that the Frontier plane was told to stop which is incredibly dangerous. The correct action was to tell Frontier to hold first and make sure they weren’t past the hold line before clearing the other plane for takeoff. Like the pilot said to ATC that was a conflict because for the time it took between the takeoff clearance and the hold short instruction there were two aircraft cleared to be on the same runway.
What that Frontier pilot did was maintained 'listening watch'.
He was the one who stopped short of the rwy (even before ATC told him to hold short) having heard ATC giving Spirit take off clearance.
Seems like ATC forgot that he told FFT to cross and quickly tried to correct it by telling him to hold short, after clearing Spirit for take off.
ATC should have ensured FFT was clear of rwy or give that hold short instruction prior to clearing spirit for takeoff.
Kudos to the FFT pilot.
Intelligent pilot.
Hopefully there won't be some sort of retribution against him by the feds in the future
Keep’n aircraft from sharing the same space at the same time in a high density environment with verbal communications is beyond its limit. Got’a figure out a better way sooner rather than later.
At some point in the future AI will definitely be involved. There will be a lot of kickback from people, but AI is more than capable of this, especially if it's just handling ground traffic and maybe tower. Obviously humans will still be involved but having a computer to say no, bad idea to think a like this would save a lot of incidents from happening.
Tower I have a number for you when you’re ready to copy.
Seems the controller forgot he cleared Frontier to cross 26R. Glad the pilot caught it! Sometimes two heads in the game are better than one.
Good job by that aviator..
When ATC says proceed without delay, they mean it.😊
So if the airplane delays for whatever reason, rethink your sequence or change instructions. But don't have 2 airplanes with clearance onto the runway
Well said
And it means don't delay, it doesn't mean taxi fast.
Kudos to 2517, saw the conflict, reacted to the conflict, verified his instructions AFTER critical events, didn't argue it excessively, to me, missed one important step - "Please Pull the Tapes" this tells them get a Super Involved because that was clearly an ATC Error.
Otherwise nice job
Yet when a pilot makes a mistake ATC cant wait to talk about it lengthy on frequency in a condescending way and finish with giving a telephone number
I would love to get a follow up on this.
It's only a matter of time...
that saying is always correct. it's functionally useless. ITs only a matter of time someone wins the lottery. It's only a matter of time until X event happens
Frontier should’ve given ATC a number to call, possible tower deviation
Well done to to the pilot, I was waiting for him to to tell the tower I have a phone number for you when your ready for possible tower deviation
Possible ATC deviation . Should have asked for the guy’s phone number .
hes expecting you to keep it rolling a bit faster
Pilot version of: Tower, I have a number for you to call!
I'm sure the CVR would be quite helpful in validating the pilot's claim. Kudos to the pilot of Frontier 2517 for being alert on the ground. At these airports out West nothing is routine.
We hebben een nummer voor de toren 😂
He should have said, "Possible ATC deviation, I got a number for you when you're ready.".
That's why you never leave tower until you are clear of ALL runways..
Sounds to me like the tower initially messed up but then caught their mistake by telling Frontier to hold instead? Unless the controller gave two conflicting instructions without realizing it?
Frontier, only fly me with this captain, please and thank you.
I was on the Frontier flight LMAO. I was wondering why we slammed on the brakes
Seems like twr could see they weren’t close to crossing so cleared the takeoff then said to hold short. Definitely not proper process for sure but it does seem like the twr was watching. They should have first said to hold short, waited for read back, then gave the takeoff clearance.
"Tower, I have a phone number for you when you are ready"
Yes, Tower we have a number for you to copy. Possible ATC deviation. Very heads up on the Frontier pilot.
This is how a pilot should be. Not emotional, just prepared and professional. Something that’s fading quickly away
Today's pilots have a better safety record than at any point in history.
"Hey ground, can you pass on a number over to tower? Thanks, 2517"
Was on Alaska #738 on 4/7 trying to land at LAS when we had to go around right before touching the ground due to a plane on the runway. Anybody got ATC on that?
Oh that was an insidious one! Yikes!!!!
Frontier pilot earned his pay. He should be given the controller's pay for that day too!
100% tower deviation
Delta 67 had to go to Paris not alnta takeoff from Rome now just landed in paris
I'm really counting the days until a pilot blurts out "possible tower deviation" and demands the tape be submitted for investigation.
And aviation is a team sport.
That was an incredibly dangerous mistake by the controller!
Tower did tell him hold short. Bad practice on the order there but he did tell him hold short
The Traffic Controller was backpedaling. He did cleared him to cross 26r and a takeoff 😳😳
Frontier vs Spirit: guaranteed brawl to ensue
"No further communication occured. The aircraft taxied to the gate"... I'm willing to bet there was more to say on the matter!
Sterile cockpit … a great concept of safety, that had to have contributed to this + outcome
Well he did stop when he heard the conflict developing and that was good. But he didn’t “keep it rolling” which might have avoided the whole thing
Keep it rolling doesn't mean anything to us pilots.
I have seen a genuinely terrifying number of new videos from this channel in the last week or so.
What is going on in avaition at the moment or is it just the algorithm?
Mainly algorithm stuff like this happens surprisingly often, well maybe not stuff like whats in the video but problems on aircrafts.
It feels like we're counting down the days until a major accident in the US, caused by poor ATC
that won't be the root cause
When white men are allowed to be hired again, and all the other riff raff is purged, then safety incidents will go down in frequency.
@@iain8837 still be waiting
Pilots should also be able to say "we got a number for you to call." :D
"Can I have a number to call?" "Yup, 911"
That’s why airplanes have two comms. Talk to ground while still listening to tower or vice versa.
Situational awareness at all times.
Is that what people do in commercial flights? I always use Comm 1 on the active frequency and Comm 2 on ATIS or whatever else. Even at Class C airports, listening to both tower and ground will be very disorienting as the traffic will be overwhelming at times not to mention a busy one like LAS where they have multiple ground and multiple tower frequencies. But I'm only private so I don't know how people do it there.
It's standard to use comm 1 exclusively for "controlling" frequencies like tower, ground, and clearance delivery and to only use comm 2 for all else like ramp, operations, ATIS etc. It is not common to listen to both ground and tower at the same time as the F/O was probably talking to ramp already to get cleared into the ramp on com 2.
So it is important to not flip to ground until you are either clear of the runway or at least halfway across it. In places like Atlanta ground will already be talking to you before you are fully across the runway without you having called them.
Awesome pilot work, poor ATC work here.
"Tower, I've got a number for you to call. Possible ATC deviation. Do you have a pen ready?"
I assume this the equivalent of a ATC possible deviation? When this happens do they get a warning or are they taken off the system for a while?
frontier was taking his sweet a** time though. I can see why the tower assumed he was instructed to hold short....
I had to make sure I wasn't the only one amidst the collective.
I didn't realize Frontier was told to hold, I was sure tower told him to keep it rolling.
Maybe tower should have told Frontier to expedite crossing but still seemed like Frontier was preoccupied.
@@SusanWSucks tower initially told frontier to keep it rolling cleared to cross. but he seems to stop for some reason....? and at that point I think the controller thought he instructed frontier to hold short....
The tower clearly made a mistake and Frontier 2517 did a good job waiting to be clear of everything to discuss the situation. However, I'm wondering if the tower expected 2517 to cross 26R much quicker than he was moving. Impossible to tell from the graphics, but it appeared 2517 was taking their time maybe?
This happens more often then you think. The only SAVE is by very observant Pilots. At the end of all my first leg of a trip Briefings
I add: " As far as ATC....They Work For Us at All Times...That Goes Double in South America!!!!" Many times I have had ATC try to
dig my grave!!!! And many times I Flatly REFUSED DIRECTION and Saved Myself!! If I am OK....Then all The PAX are OK !!! There
is a Magic Word in dealing with ATC. And that Magic Word is: "NO!!!!!" Followed by requesting a Time Check and Tel Number!!!!
I will post more of these if I find out more. This one was reported by a witness.
Eh. I didn’t know of this one. So at least 2 eerily similar close calls in two weeks. Ensuring ATC is rested is a good start but maybe there needs to be a system for Ground/Tower sync. Both incidents seem so similar: Ground has claimed runway with clearances, Tower appear completely unaware of Ground’s claim. This could be managed by bricks on a model if they sit physically next to each other; or some IT support system… these functions being unaware of each other’s clearances is insanely dangerous.
“Tower, I have a number for you to call when you get a second”
He had even switched them to ground before crossing the runway, if the pilot had done what they were instructed they might not even heard there was a conflict arriving?
- Tower, we would like a number to call, frontier 2517
Let me know when you can copy a phone number. Possible ATC deviation.
What’s good for the goose is good for the gander?