You guys didn't rename it to "Takeoff Action Speed"?
Nope. (What?!)
You guys didn't rename it to "Takeoff Action Speed"?
In the 748, you don't call V1. V1 calls you.
Since an airliner has it, most of the corporate fleet has probably done this for decades.
We officially agree at The Tabernacle that the decision to stop must be made, and the thrust/power levers retarded to IDLE BEFORE V1. This is a subtle detail not often discussed, but you are going flying at or above V1 short of a @MikeD nightmare scenario realizing itself.Not ours. The school of thought at my company is that once you reach V1, the decision to take off has been made as in the "takeoff decision speed" is somewhat mislabeled.
@PeanuckleCRJ is an instructor so please feel free to steer me if need be.
V1-5 approximates the built-in delay between the recognition of the engine failure (or other event) and V1 itself. Calling V1-10 or V1-15 would be arbitrary, and not significant to anything in particular.
No need to muddy the water.
It is not 'muddy'.
In the book of the plane I fly, you are to call it out at V1-5 for the reasons mentioned. @dasleben mentioned it was a Boeing thing and I really have no idea. I forget what it was on the Airbus. @SmoothLanderJ what is it at your place? Calling V1-5 makes sense in the broader picture which no one has talked about in depth yet (not surprising).
After 100 knots you are in a go orientated mode and are only going to abort the takeoff for a fire, engine failure, wind shear or if the plane is unsafe or unable to fly. We brief those items every time there is a new Captain and First Officer pair. The V1-5 call reinforces this go orientated mode so it works in the bigger system of how the plane should be operated. Just got done with my recurrent and the plane flies just fine calling out V1-5 with engine failures.
This is really a silly discussion. The bigger concern (at least for me) and a much more practical scenario about take-off speeds is being able to figure out what to do because of a runway incursion in the high speed regime. Can you stop the plane in time when the lost 747 down the field enters the runway you are rumbling down at 120 knots (when V1 is 145) or do you under rotate by 25-30 knots as you can't stop in time??? We are more likely to face that situation which is A LOT more dangerous before we have to worry about the plane not flying if you call out V1-5.
Cool, sounds good. Meets the intent. Should call it the same thing then: V1. The same definition is being used for both techniques.
Some airlines renamed it to emphasize at V1 we are going now, we aren't "deciding". You made you're decision when that guy next to you started saying "veeeeeeee". Supposedly some other carriers did it and we were following suit.Nope. (What?!)
Some airlines renamed it to emphasize at V1 we are going now, we aren't "deciding". You made you're decision when that guy next to you started saying "veeeeeeee". Supposedly some other carriers did it and we were following suit.
Lies lies, and damn training departments.
Still missing the points.
It also isn't a technique as it is procedure at my place along with other operators.
Not missing anything. You're somewhat missing what I'm saying about technique/procedure. Your technique is your procedure there because that's the only method the company adopted. And that's fine. It's sound, it's safe, it works, it accomplishes what it's designed to accomplish. However other companies may use a different technique as their procedure. Both techniques accomplish the same overall objective in the big picture.
We officially agree at The Tabernacle that the decision to stop must be made, and the thrust/power levers retarded to IDLE BEFORE V1. This is a subtle detail not often discussed, but you are going flying at or above V1 short of a @MikeD nightmare scenario realizing itself.
(That is, not only must you decide to stop ["REJECT, MY CONTROLS"] but you need to start stopping!)
It is not 'muddy'.
In the book of the plane I fly, you are to call it out at V1-5 for the reasons mentioned. @dasleben mentioned it was a Boeing thing and I really have no idea. I forget what it was on the Airbus. @SmoothLanderJ what is it at your place? Calling V1-5 makes sense in the broader picture which no one has talked about in depth yet (not surprising).
After 100 knots you are in a go orientated mode and are only going to abort the takeoff for a fire, engine failure, wind shear or if the plane is unsafe or unable to fly. We brief those items every time there is a new Captain and First Officer pair. The V1-5 call reinforces this go orientated mode so it works in the bigger system of how the plane should be operated. Just got done with my recurrent and the plane flies just fine calling out V1-5 with engine failures.
This is really a silly discussion. The bigger concern (at least for me) and a much more practical scenario about take-off speeds is being able to figure out what to do because of a runway incursion in the high speed regime. Can you stop the plane in time when the lost 747 down the field enters the runway you are rumbling down at 120 knots (when V1 is 145) or do you under rotate by 25-30 knots as you can't stop in time???
Not ours. The school of thought at my company is that once you reach V1, the decision to take off has been made as in the "takeoff decision speed" is somewhat mislabeled.
@PeanuckleCRJ is an instructor so please feel free to steer me if need be.
Just curious the difference between V1-5 and "Most guys remove their hands from the thrust levers a couple knots before V1 since there's no time to make the decision at that point."Spot on. Most guys remove their hands from the thrust levers a couple knots before V1 since there's no time to make the decision at that point.
I don't like this V1-5 stuff... pretty dumb if you ask me.