This could have been very very bad....
http://www.faa.gov/airports/runway_safe ... ation.html
Printable View
This could have been very very bad....
http://www.faa.gov/airports/runway_safe ... ation.html
It was 10 feet...what's the problem!?!
But sreiously, that's pretty nuts.
I like the controller's "oh s%&#, I'm fired" voice after the incident.
HOLY ****! WOW! Now to Monday morning quarter back it. I cannot fathom the controller's ability to back to back issue clearnces like that on the same runway. I mean, I could marginally understand a long delay between clearnces where someone doesnt get rolling but 5 seconds apart??? The pilots get a whole boat load of crap for this though too. Neither of them were using situational awareness. Situational awareness is most of the job. The fact that Bluestreak didnt abort sooner and that the PC12 pilot didnt notice what was happening strikes me. I dont know what the visibility conditions at the time were so I cant say why PSA didnt see it quicker or the PC12 crew didnt see those Zenon blue lights glaring down the runway like a cougar on the kill but that was scarey.
On furthur examination and reviewing I think what probably happened is the controller forgot that the PC12 was an intersection departure which would make sense. However, the visibility upon research was shown to be 9 miles which means I still have to ask..... WTF???? The PSA crew apparently began their abort about 1600 feet into the roll but apparently still had some speed to them at that point. Here is the AvHerald article on it. http://www.avherald.com/h?article=41a9b644&opt=0
I think the controller had to change her underpants after this one.
I can't believe how normal/calm the pilots sounded on the radio after...
They teach you that in pilot school :lol:Quote:
Originally Posted by Big Tim #70
They probably said OH ****. It wasnt on the radio. Both planes.Yea sure they sound calm but off that radio they were flipping. Its human nature.
Not acceptable. Excuse me while I pick my jaw up off the ground.