Takeoff ground-roll calculator
Start from a 1,000 ft sea-level ground roll charted at a 2,400 lb reference weight and correct it for density altitude, actual weight, headwind and runway slope, with each factor shown. Built for dispatch checks and ground school. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Baseline distance
- 1,000
- Density altitude
- 0
- Weight
- 2,400
- Reference weight
- 2,400
- Liftoff speed
- 55
- Headwind
- 0
- Density ratio
- 1
- Density factor
- 1
- Weight factor
- 1
- Wind factor
- 1
Published takeoff charts almost always quote ground-roll distance at sea-level standard atmosphere, a reference takeoff weight, zero wind, and a level hard runway. Real departures rarely match that page: a high-elevation summer afternoon, extra fuel and bags, a tailwind component, or a slight upslope can stretch the roll far past the printed number. This takeoff ground-roll adjustment calculator starts from that baseline sea-level figure and applies deterministic density-altitude, weight, headwind, and runway-slope factors used in performance teaching and first-cut dispatch checks.
How density altitude, weight, wind, and slope stretch the roll
Takeoff ground roll is the distance from brake release to the point the main wheels leave the runway. Pilot operating handbook and AFM charts almost always publish that distance at sea-level International Standard Atmosphere, a listed reference weight, zero wind, and a paved level surface. Four first-order corrections turn that baseline into a departure-day estimate.
Density altitude enters through the ISA density ratio sigma: in the troposphere, theta equals one minus 6.875585586 times ten to the minus six, times density altitude in feet, and sigma equals theta raised to 4.2558797. Piston and turboprop ground roll scales about as one over sigma squared, because both true airspeed at a given indicated liftoff speed and net acceleration degrade with density. Jet thrust at low speed is closer to constant, so the density factor is one over sigma.
Weight scales the roll by the square of actual weight over the chart reference weight, because liftoff speed grows with the square root of weight while acceleration falls. A headwind lowers ground speed at liftoff; the wind factor is the square of liftoff true airspeed minus headwind, all over liftoff true airspeed, and a tailwind is simply a negative headwind.
Runway slope then uses the implied mean acceleration from that wind-adjusted roll: upslope subtracts g times the sine of the slope angle and stretches the remaining distance, while downslope shortens it. The product of the four factors multiplies the baseline. This is a planning identity, not a substitute for the AFM, a wet-runway analysis, or a rejected-takeoff calculation.
Who corrects ground roll before departure
Flight-school dispatch desks and club checkout sheets need a repeatable correction from the sea-level POH box when the AWOS reports a high density altitude or the airplane is under max weight. Type-rating and commercial-pilot ground schools use the same four factors to show why a hot high-elevation departure eats runway even when the indicated rotation speed looks familiar. Failed validation does not consume balance.
Always cross-check against the AFM or POH for the actual type, flap setting, and runway surface before you release brakes; this calculator is the correction arithmetic, not the certified chart.
What you can do with it
Hot-and-high club and school departures
Start from the sea-level POH ground-roll box and correct for today's density altitude and actual takeoff weight before a mountain or summer checkout.
Ground-school and LMS scoring
Mark performance-planning items with a deterministic oracle that rejects impossible tailwinds and upslopes instead of returning a silent empty distance.
FAQ
How is takeoff ground roll adjusted for density altitude?
Weight, wind, and slope factors are applied on top.
Does a heavier airplane always need more runway?
A ten percent weight increase lengthens the zero-wind roll by about twenty-one percent before wind and slope are applied.
How should I enter wind and runway slope?
Crosswind is ignored; resolve the along-runway component first.
Is this a substitute for the AFM or POH chart?
No. It is a first-order planning identity for teaching and dispatch estimates. Use the certified chart for the type, flap setting, surface, and obstacles, and add safety margins your operator requires.
Why do piston and jet aircraft get a different density correction?
Piston and turboprop ground roll grows roughly with one over the density ratio squared, because both liftoff true airspeed and acceleration suffer in thin air. Jet thrust at low speed stays closer to constant, so the factor is one over the density ratio.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/travel/takeoff-ground-roll \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"baseline_distance":860,"density_altitude":5000,"weight":2300,"reference_weight":2400,"liftoff_speed":55}'const res = await fetch("https://api.kit.forhosting.com/travel/takeoff-ground-roll", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"baseline_distance": 860,
"density_altitude": 5000,
"weight": 2300,
"reference_weight": 2400,
"liftoff_speed": 55
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/travel/takeoff-ground-roll",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"baseline_distance": 860,
"density_altitude": 5000,
"weight": 2300,
"reference_weight": 2400,
"liftoff_speed": 55
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/travel/takeoff-ground-roll", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"baseline_distance":860,"density_altitude":5000,"weight":2300,"reference_weight":2400,"liftoff_speed":55}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"baseline_distance":860,"density_altitude":5000,"weight":2300,"reference_weight":2400,"liftoff_speed":55}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/travel/takeoff-ground-roll", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"baseline_distance": 860,
"density_altitude": 5000,
"weight": 2300,
"reference_weight": 2400,
"liftoff_speed": 55
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "travel.takeoff_ground_roll",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
It returns the adjusted roll, each factor, implied liftoff true airspeed and ground speed, and a formula string so a briefing card, spreadsheet, or API client can show the same arithmetic. Missing or non-physical inputs fail with invalid_input instead of inventing a distance.
Input contract, response shape, and error behaviour
Optional headwind defaults to zero knots (positive shortens the roll, negative is a tailwind). Optional propulsion is piston or jet and defaults to piston. Density altitude must stay between minus two thousand and twenty-five thousand feet. The weight ratio must stay between 0.4 and 2.0 so mixed units are rejected. Headwind must not meet or exceed liftoff true airspeed, and an upslope that cancels implied acceleration is rejected. Example: an eight-hundred-sixty-foot sea-level chart, five thousand feet density altitude, twenty-three hundred against a twenty-four hundred reference, fifty-five knots liftoff, five knots of headwind and a half-percent upslope yields a longer adjusted roll with every factor visible. POST a JSON body with five required finite numbers: baseline_distance, the published sea-level zero-wind level-runway ground roll; density_altitude in feet; weight and reference_weight in the same mass unit; and liftoff_speed, the published indicated or calibrated liftoff or rotation speed in knots at the reference weight. Optional runway_slope defaults to zero percent (positive is uphill). Optional distance_unit is ft or m and defaults to ft. Each numeric field may arrive as a JSON number or as a numeric string; aliases such as da, vlof, chart_weight, and slope are accepted. Those validation failures return invalid_input and are not billed. On success the body echoes the inputs, returns density_ratio and the four factors, combined_factor, adjusted_distance and delta_distance, liftoff_ias, liftoff_tas, liftoff_ground_speed, implied_acceleration, plus formula, method, and a short message. Pair the number with AFM charts, surface condition, and obstacle data; this endpoint does not emit balanced-field length or screen-height distance.
Where a takeoff ground-roll API earns its keep
Charter and aerial-work planners batch a morning line of legs through one parse endpoint instead of re-deriving sigma and the weight-squared rule in a private spreadsheet that drifts between bases. Keep requests small, pin the rounded adjusted_distance in tests, and you get a reproducible first-cut roll for briefings, LMS items, and edge workers without standing up a performance-engineering stack.
Integration use cases
Wind and slope runway briefings
Fold a known headwind or tailwind and a published runway gradient into the same adjusted roll the free widget shows, for a consistent passenger or student brief.
Technical questions
What does the takeoff ground-roll calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.