Seggy
Well-Known Member
He may not have flown many airplanes that don't expect to get shot at....
Once again, he didn't say that.
He may not have flown many airplanes that don't expect to get shot at....
Didn't know you upgraded...
![]()
That's funny, I too have several type ratings, and I believe we share the A320.The four aircraft I have type ratings for don't have anything like this.
That's funny, I too have several type ratings, and I believe we share the A320.
There is an expanded checklist for tail strike.
Did you say something about required to think outside the box, because that's what is expected of an aviator?
Why does everyone keep saying tail strike? These guys took off from a runway that was too short and plowed through some approach lights, could have hit the gear, mid part of the belly, the tail. Who knows but it's not a damn tail strike in the traditional sense and a stupid EICAS message shouldn't dictate how you continue, it's not really applicable here.
Why does everyone keep saying tail strike?
And SKW pilots as late as 2015*.XJT pilots were running their own takeoff performance numbers and spinning a wiz wheel as late as 2010.
Do you guys have a whiz wheel in the Ejet?And SKW pilots as late as 2015*.
* yes, I know nobody cares how we did it on the Brasilia. But it was sort of cool being involved with the process, because when a plainly and obviously incorrect result was arrived at, you went "um," and threw the manifest away and started over.
No.Do you guys have a whiz wheel in the Ejet?
I assumed it was a tail strike just like how @Seggy assumed it was fatigue induced because of no Union protection.Why does everyone keep saying tail strike? These guys took off from a runway that was too short and plowed through some approach lights, could have hit the gear, mid part of the belly, the tail. Who knows but it's not a damn tail strike in the traditional sense and a stupid EICAS message shouldn't dictate how you continue, it's not really applicable here.
That's not what he said and you know it. You know that having another set of eyes and ears looking out for you and your pilot group is better for the overall safety culture. It is very easy to Monday morning quarterback and that's why @Seggy is making his statements regarding unions.I assumed it was a tail strike just like how @Seggy assumed it was fatigue induced because of no Union protection.
The four aircraft I have type ratings for don't have anything like this.
From my understanding, you can't tail strike a 777 normally. They didn't tail strike it as well it seems like....
They hit the lights and continued on. Wonder if the nonunion, lack of a safety culture contributed to this...
Let us talk about that some more. The pilot of that flight, slept what, about 3 or 4 hours 24 hours prior to the accident? This of course, after flying 99 hours the previous month. Have the scheduling practices at Emirates changed since then? Wouldn't pilots be prone to procedural errors being so fatigued? Looks like there may have been more!
http://www.news.com.au/travel/trave...-highly-probable/story-e6frfq80-1225707342621
Wouldn't a company with a just safety culture have kept them on and look at the system that caused the mistakes? Wait a second, Emirates DID change some procedures after the incident in Melbourne, didn't they? So why didn't they keep the pilots on then?
The QF32 guys did a controllability check before the approach, which likely contributed to their safe and successful arrival. The Brasilia QRH specified that one be done under certain circumstances.
Incidentally, all I've ever gotten from MOC over the air was "follow the QRH," @MikeD.