None of these speeds are read off a gauge and reacted to in the moment. All three are calculated on the ground, before brake release, for that specific takeoff — and by the time the aircraft is rolling, the decision they encode has already been made.
Every takeoff in a transport-category aircraft is bracketed by three calculated speeds — V1, VR, and V2 — and the whole point of calculating them in advance is to remove judgment from a part of the flight where there usually isn't time for any. Each one answers a different question about what the aircraft can safely do at that instant, assuming the worst plausible failure (typically an engine failure) happens right then. Mixing them up, or treating V1 as something a pilot simply "feels" in the moment, is one of the more persistent misunderstandings about how takeoff safety actually works. This explainer covers the sequence of speeds that governs the go/no-go decision itself — a related but distinct question from the airspeed-instrument topic covered in Indicated vs. True Airspeed.
V1 — takeoff decision speed.The maximum speed at which the crew can still decide to reject (abort) the takeoff and bring the aircraft to a full stop within the remaining runway. V1 is not the speed the aircraft "happens to be going" when a decision is made — it's computed beforehand, specifically for that flight's weight, runway length, runway condition, temperature, wind, and elevation, against a defined emergency scenario (almost always an engine failure). Below V1, rejecting is the safer choice. At or above V1, the takeoff must continue — a rejected takeoff initiated above V1 risks running off the far end of the runway before the aircraft can stop.
VR — rotation speed. The speed at which the pilot flying begins rotation: pulling back on the controls to raise the nose and initiate liftoff. VR is always at or above V1 — by definition, the aircraft can't begin rotating before it has passed the point where continuing the takeoff is already the committed, correct choice. VR is calculated to guarantee adequate control response and climb performance immediately after liftoff, including in the case of an engine failure occurring right around rotation.
V2 — takeoff safety speed. The minimum speed the aircraft must reach, and then maintain, by the time it is 35 feet above the runway. V2 is calculated specifically to deliver adequate climb performance and controllability with one engine inoperative — for a twin-engine aircraft, on the remaining single engine. If an engine fails at or after V1, V2 is the target climb-out speed: the speed the crew flies to guarantee the aircraft keeps climbing away from the ground on whatever thrust is left.
Takeoff performance planning computes V1, VR, and V2 from the aircraft's actual takeoff weight, the runway's length and surface condition, air temperature and pressure altitude, and wind — balancing the "accelerate-stop" distance (how far it takes to reach V1 and then brake to a full stop) against the "accelerate-go" distance (how far it takes to reach V1, lose an engine, and still complete the takeoff and climb to 35 feet at V2). Where those two distances are balanced against the available runway defines V1. The crew briefs all three numbers before every takeoff specifically so that if an engine fails, there's no decision left to make in real time — only a memorized action to execute against a number that was already computed on the ground.
No — and treating V1 as an in-the-moment judgment call is exactly backwards. V1 is precisely pre-calculated during takeoff performance planning, specific to that flight's weight, runway length, temperature, and other conditions, representing the last speed at which a rejected takeoff can still be completed safely within the remaining runway. It is not decided after the fact based on what feels safe in the moment — it's a number the crew computes and briefs before the aircraft ever begins its takeoff roll. The go/no-go rule — reject below V1, continue at or above V1 — is established in advance precisely because there usually isn't time for real judgment at these speeds. An engine failure near V1 leaves a crew a second or two to act, not to deliberate; the entire purpose of pre-calculating V1 is to turn that instant into a memorized, rehearsed response rather than a decision made under pressure.
Explains the three pre-calculated speeds that govern every transport-category takeoff — V1 (the takeoff decision speed, the last point a rejected takeoff can still stop safely on the runway), Vr (rotation speed, when the nose is raised for liftoff), and V2 (takeoff safety speed, the minimum climb speed guaranteed even with one engine inoperative) — and why all three are computed in advance for that specific flight rather than judged in the moment.
It is easy to picture V1 as a speed a pilot reacts to in real time — "the speed you were going when you decided to abort." In reality V1 is fixed by takeoff performance calculations completed before brake release, using that flight's actual weight, runway length and condition, temperature, pressure altitude, and wind. The go/no-go rule is briefed as a fixed number specifically so no real-time judgment is required at a speed where there usually isn't time for any.
V1 balances two computed distances: accelerate-stop (reach V1, then abort and brake to a stop) and accelerate-go (reach V1, lose an engine, and still complete the takeoff, reaching V2 by 35 feet). Where those distances fit within the available runway defines V1. Vr, the rotation speed, is always at or after V1 on the timeline — the aircraft cannot begin rotating before the point where continuing has already become the required action — and is set to ensure adequate control and initial climb performance even with an engine failure near rotation. V2 is the minimum speed that must be reached and held by 35 feet, sized to guarantee climb performance and controllability on the remaining engine(s) alone.
This sequence underlies every takeoff briefing on a multi-engine transport aircraft, and is recalculated for every departure since it depends on that day's weight, temperature, wind, and runway — it is never a fixed number for a given aircraft type. It is also one of the most frequently tested concepts in airline transport pilot and dispatcher training, and a common source of confusion for anyone assuming V1 is a real-time judgment rather than a pre-briefed performance limit.
No — V1 is capped by several limits simultaneously, including maximum brake energy speed, tire speed limits, and the runway-derived accelerate-stop and accelerate-go distances. The lowest of the applicable limits governs.
Yes, constantly. V1, Vr, and V2 are recalculated before every takeoff from that flight's actual takeoff weight, runway length and surface condition, temperature, pressure altitude, and wind. A heavier aircraft, a hotter day, or a shorter runway all shift these speeds — they are not fixed constants for an aircraft type.
V1 is defined so that this is treated as a continue case — the accelerate-go distance calculation already assumes a failure right at V1 and confirms the aircraft can still complete the takeoff and reach V2 by 35 feet on the remaining engine(s) within the available runway and clearway.
On some aircraft and configurations they can be very close or coincide, but Vr can never be lower than V1 — rotation cannot be initiated before the point at which continuing the takeoff has already become the required, committed choice.
35 feet above the runway is the certified screen height used in takeoff performance calculations (under regulations such as FAA 14 CFR Part 25 and equivalent standards) as the point by which the aircraft must have cleared obstacles and established the guaranteed one-engine-inoperative climb speed and gradient.
Try our Aerospace Engineering Studio
More calculators, simulators, and guides for this discipline.