I like how Boeing made my jet. Above 80K it only makes the "bad things happening sounds" for things I should reject for. Bad things I need to think about have their audibles inhibited above 80k. I just listen and don't look above 80K. Swerve, bang, or bell above 80k is all I need to worry about unless it doesn't fly for some reason. If it comes to that you're pretty much screwed anyways.
That is how the other Boeings, McBoeings, Canadairs, Embraers, and the Buses work as well.
But not how all the Falcons, Gulfstreams, Citations, Lears and Hawkers work.
If V1 is say, 140 knots, my hand is usually off the thrust lever by about 130 (-ish) knots.
I do the exact same thing. Tends to vary with rate of acceleration.
Doing a risk assessment at 135 knots is a recipe for a runway excursion.
Does Delta not callout V1 at V1-5 kts precisely for what you are implying? I thought almost everyone had made that switch.
Or worse. There is a reason the 80kts call is there.
Yup. "Fire, (engine) failure, fear, or windshear (if it's deemed by the ca safer to stop)" are the only reasons we abort above 80 knots. Other than that, it's go.
I do believe in the V1-5kt call and do it part 91. However, if I remember correctly, startle factor is built into certification with regards to V1. Some one correct me if I'm wrong.Does Delta not callout V1 at V1-5 kts precisely for what you are implying? I thought almost everyone had made that switch.
Edit: I take issue with that because there are a few rare set of circumstances that dictate otherwise, like it won't rotate, but I'm paid to do it one way, so I do it that way. If the sucker won't rotate, I'm going to have to hold hands while I call out the failure I guess, get on the brakes and deal with it later.
It is vitally important that all pilots, but especially 121 FOs, understand the difference between company policy and good airmanship. Blindly following company policy is not always the same as good airmanship.
You're completely right to be following company policy, but also remembering that when your pink butt is on the line, it is simultaneously your responsibility to exercise good judgment (and sometimes that conflicts with company policy).
And that's where things get really really muddy. 99.999% of company policy is the way it is for good reason, even the RTO decision is a good one because they are so dangerous. But I remember a recent Allegiant RTO above V1, on a long runway because of an elevator issue. Had that been on a short runway, the FO flying and "it won't fly!!!" what would have happened?
And that's where things get really really muddy. 99.999% of company policy is the way it is for good reason, even the RTO decision is a good one because they are so dangerous. But I remember a recent Allegiant RTO above V1, on a long runway because of an elevator issue. Had that been on a short runway, the FO flying and "it won't fly!!!" what would have happened?
Every airline I've seen has "it won't fly" as the one reason to abort above V1.
I think you missed the point though. Common sense, besides what the feds or any airline says, if it won't fly, and you're past V1, you either drive on Highway 40 to the destination, or you abort. But it may take a few seconds to mutter "it won't rotate...IT WON'T ROATATE!"
Then, the left seat says, "uhh, what?" Scans the instruments....2000ft remaining... Looks at you perplexed....scans the instruments....trying to figure out why the FO hasn't taken us flying yet....trys for himself to get it flying....1000ft remaining.....initiates abort, well above Vr now.....500ft remaining, and into the dirt (if you're lucky enough to have that) you go.
IMO, there should be a set of circumstances, as narrow as they might be where the FO can, and should, call "ABORT-ABORT-ABORT".
Especially at my shop. There are a few guys, and gals, who I, as an FO, feel like I babysit for 3-4 days at a time.