Boeing 767 takeoff speed is typically 140–160 KIAS at rotation. See how weight, flaps and runway conditions change V1, VR and V2.
The Boeing 767 has no single takeoff speed. In real-world aviation and accurate flight simulation, rotation speed (VR) is commonly about 140–160 KIAS, with lift-off following moments later. Exact V1, VR and V2 values depend on variant, weight, flap setting, thrust, runway, weather and pressure altitude.
Which Boeing 767 speed counts as takeoff speed?
For this question, takeoff speed normally means VR: the speed at which the pilot begins raising the nose. V1 and V2 are separate references used during the same takeoff.
| Reference | Meaning | How it is used |
|---|---|---|
| V1 | Takeoff decision speed | The continue-or-reject decision reference. It is at or below VR, not the normal cue to pull back. |
| VR | Rotation speed | Begin a smooth rotation. A typical 767 value is around 140–160 KIAS, although calculated values can fall outside this range. |
| V2 | Takeoff safety speed | The climb safety reference following an engine failure. It is not the rotation speed. |
Our plain-English explanation of V1, VR and V2 covers how these references fit together. The usual 140–160-knot VR band is roughly 161–184 mph or 259–296 km/h.
Is 767 takeoff speed indicated or ground speed?
The 767’s takeoff targets are indicated airspeeds shown in knots on the flight display, not groundspeeds. Do not wait for GPS or groundspeed to reach the calculated VR.
A headwind reduces groundspeed at a given indicated speed, while a tailwind increases it. At a hot, high airport, the same KIAS also corresponds to a higher true airspeed and groundspeed, contributing to a longer ground run.
Why does Boeing 767 rotation speed vary?
The calculated rotation speed changes with the aircraft, loading and selected takeoff configuration. The main inputs are:
- Takeoff weight: a heavier 767 generally needs a higher VR and more runway.
- Variant and engines: the 767-200, 767-300/ER and 767-400ER do not share one universal set of speeds.
- Flap setting: additional takeoff flap often reduces rotation speed, but adds drag and changes climb performance.
- Runway data: length, slope, surface condition and contamination affect the performance solution, especially V1 and allowable weight.
- Atmospheric conditions: temperature, pressure altitude and wind affect acceleration, runway distance and the permitted thrust setting.
- Thrust configuration: full-rated, derated or assumed-temperature takeoffs must use matching performance data.
A short runway does not justify choosing an arbitrary lower rotation speed. The solution may require another flap or thrust setting, a lower takeoff weight or a different runway. Our guide to Boeing 767 runway requirements explains that separate performance problem.
What speed should I use in a 767 flight simulator?
Use the V-speeds calculated for the loaded aircraft rather than entering 150 knots for every flight. A realistic setup follows this order:
- Identify the model. Confirm the exact 767 variant and engine option represented by the add-on.
- Finish loading. Set passengers, cargo and fuel, then check gross weight and centre of gravity. Confirm that pounds and kilograms have not been confused.
- Select the configuration. Enter the departure runway, takeoff flap, thrust setting and relevant weather or runway condition.
- Obtain the speeds. Use the add-on’s electronic flight bag, performance tool or approved documentation. Some flight management computers only store V-speeds supplied by another tool; blank values do not necessarily mean the FMC is broken.
- Cross-check the result. V1 should be at or below VR, with V2 above VR. Verify that the same values appear as speed markers on the primary flight display.
- Rotate at VR. Apply smooth nose-up input and follow the flight director or aircraft documentation. Do not wait until V2 to start rotating.
Our guide to entering performance data in an MSFS airliner FMC explains the usual workflow. If a simplified 767 model provides no calculator or documentation, about 150 KIAS is a reasonable simulator-only benchmark, but it is not valid operational data.
Why won’t the Boeing 767 rotate at VR?
If a simulated 767 will not rotate at the computed VR, the cause is usually configuration, loading or control input rather than a need for substantially more speed.
- VR begins the rotation: the wheels are not expected to leave the runway the instant the callout occurs.
- Incorrect stabiliser trim: set the calculated takeoff trim after entering the correct centre of gravity.
- Stale V-speeds: recalculate after changing fuel, payload, runway, flap or thrust settings.
- Wrong configuration: check the flaps, speedbrakes and brakes before starting the takeoff roll.
- Control problems: inspect elevator-axis assignment, calibration and dead zones if the virtual yoke moves less than the physical controller.
Do not compensate by yanking the nose up. An abrupt or early rotation can cause a tail strike, while excessive delay consumes runway and may lead to an overspeed during the initial climb.