Turn radius from speed, bank angle, or turn rate
At 120 knots with a 25° bank, a coordinated turn needs a radius of 833.3860599903 m, or 2734.206233564 ft. Enter a speed and either the bank angle or the turn rate, and the other one is worked out for comparison. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Speed
- 120
- Speed unit
- Knots
- Bank angle deg
- 25
- Turn direction
- right
- Speed m s
- 61.7333333333
- Radius m
- 833.3860599903
- Radius km
- 0.83338606
This turn radius calculator converts speed plus either a coordinated bank angle or a measured turn rate into a practical radius. It supports metres per second, kilometres per hour, miles per hour, and knots, and reports the result in metres, kilometres, and feet. Signed angles and rates also preserve left or right turn direction. Use it for flight planning, vehicle path estimates, simulator checks, or a quick comparison of how speed and control input change the space required to turn.
Choose the input that matches the information you have
Start with a positive speed and select its actual unit. Then provide exactly one turning input. Use bank angle when planning a coordinated, level aircraft turn in still-air conditions, or when exploring how a chosen bank affects the ground-space estimate under a simplified model.
Use turn rate when you already know angular motion from an instrument, simulation, route requirement, or vehicle log. A positive bank angle or turn rate is reported as a right turn, while a negative value is reported as a left turn; the radius itself remains a positive distance. Do not enter both turning inputs, because they represent two different ways of defining the same motion and may conflict.
Zero bank and zero turn rate describe straight travel with an unbounded radius, so the calculator rejects them rather than returning a misleading finite value. Units matter: 120 knots is very different from 120 kilometres per hour, even though the numeric speed is identical. Check the selected unit before using the result in a route, safety margin, or map overlay.
Understand the formulas and assumptions
For the bank-angle method, the calculator applies the standard coordinated-turn relationship: radius equals speed squared divided by gravitational acceleration times the tangent of the absolute bank angle. Speed is converted to metres per second before calculation, and gravity defaults to standard gravitational acceleration. You may supply another positive gravity value when modelling a different assumption.
For the turn-rate method, radius equals linear speed divided by angular speed, with degrees per second converted to radians per second. The calculator also derives the complementary turn rate or bank angle so that results can be compared between methods. These equations describe ideal kinematics.
The coordinated-bank equation assumes level flight, balanced forces, constant speed, and no wind correction. It does not model climb angle, sideslip, tire friction, road superelevation, steering geometry, transient roll, or pilot reaction. The turn-rate equation is more general kinematically, but its accuracy still depends on the supplied rate and speed describing the same instant and reference frame.
Treat the output as a planning quantity, not as a substitute for certified performance data or operating procedures.
Interpret the radius and apply a suitable margin
The returned radius is measured from the centre of the circular path to the moving object's assumed reference point. Diameter is twice that value and is often easier to compare with available corridor width or map clearance. Results appear in metres, kilometres, and feet to reduce manual conversions, while the normalized speed in metres per second makes the calculation auditable.
Notice that the bank-angle formula contains speed squared: doubling speed at the same bank angle makes the radius four times larger. By contrast, radius at a fixed turn rate grows directly with speed. Those relationships make the calculator useful for sensitivity checks—run several realistic speeds and controls rather than relying on one nominal case.
Real operations need extra allowance for wind, tracking error, response delay, surface conditions, navigation tolerance, obstacle clearance, vehicle dimensions, and local rules. For aircraft, compare the estimate with the approved flight manual, operator guidance, airspace requirements, and actual conditions. For ground vehicles, account for the swept path of every body corner and trailer, not only the centreline radius.
What you can do with it
Estimate an aircraft turn footprint
Compare expected radii at several airspeeds and coordinated bank angles before laying out a training or simulation scenario.
Convert logged turn rate into path radius
Use speed and angular-rate telemetry to estimate the circular path represented by a steady portion of a flight or vehicle log.
Test route sensitivity to speed
Show how a planned turn expands as speed increases, then add operational clearance appropriate to the vehicle and environment.
FAQ
Should I provide bank angle and turn rate together?
No. Provide exactly one. Bank angle defines an ideal coordinated turn, while turn rate directly defines the angular motion.
Why are zero bank angle and zero turn rate rejected?
Either value describes straight motion rather than a finite circular turn, so the corresponding radius tends toward infinity.
Does wind affect the result?
The bank-angle calculation uses the supplied speed without a wind model. Use airspeed for the aerodynamic coordinated-turn estimate; a ground-track radius requires conditions and references appropriate to that task.
Can I use this as certified aircraft performance data?
No. It is an ideal planning calculation. Use approved aircraft documentation, procedures, regulations, and current operating conditions for operational decisions.
How do I tell the calculator it is a left turn?
Enter the bank angle or the turn rate as a negative number. Positive values are reported as a right turn and negative values as a left turn, while the radius always stays a positive distance.
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/geo/turn-radius \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"speed":120,"bank_angle_deg":25}'const res = await fetch("https://api.kit.forhosting.com/geo/turn-radius", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"speed": 120,
"bank_angle_deg": 25
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/geo/turn-radius",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"speed": 120,
"bank_angle_deg": 25
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/geo/turn-radius", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"speed":120,"bank_angle_deg":25}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"speed":120,"bank_angle_deg":25}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/geo/turn-radius", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"speed": 120,
"bank_angle_deg": 25
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "geo.turn_radius",
"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
Interpret the radius and apply a suitable margin
The API costs $0.002 per request, while the browser calculation is suited to quick interactive checks.
Technical questions
What does the API request cost?
Each API request costs $0.002. The interactive browser calculation can be used for quick checks.