Nautical miles to miles converter
Bring a sea or air distance onto the road map: 1 nautical mile is 1.150779448024 statute miles, worked out from the 1852-meter nautical mile and the 1609.344-meter mile rather than the rough 1.15 rule. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Nmi
- 1
- Result
- 1.150779448 mi
- Converted
- 1.150779448
- Miles
- 1.150779448
- From unit
- nmi
A nautical-miles-to-miles converter turns marine, aviation, and chart distances into the statute mile value drivers, weather briefs, and land logistics teams still need on road maps, flight-planning summaries, and US-facing product copy. Approximate mental shortcuts such as multiply by one point one five are rejected in favour of the metre-based definitions, so homework checks and route exports match engineering tables.
Why nautical miles and statute miles still meet at 1852 ÷ 1609.344
Nautical miles are the standard length unit on marine charts, aviation flight plans, coastal weather products, and many maritime contracts because one international nautical mile is tied to the metre as exactly one thousand eight hundred fifty-two metres. Statute miles remain standard on many United States highway signs, vehicle odometers, inland logistics quotes, and consumer apps when set to imperial land distance.
The bridge between them is not a survey approximation or a rounded one point one five rule of thumb: divide the metre definition of the nautical mile by the metre definition of the international statute mile, one thousand six hundred nine point three four four metres from the nineteen fifty-nine yard and pound agreement, and you obtain an exact constant factor. That makes the conversion a single exact multiplication, miles equals nautical miles times one thousand eight hundred fifty-two over one thousand six hundred nine point three four four.
Teachers and navigators often still teach the rough rule of thumb multiply by one point one five, but that introduces a scale error that shows up immediately on a long coastal passage or a multi-leg flight plan.
Practical tips, checks, and related searches
Round-trip sanity checks are easy: convert one nautical mile and confirm you receive approximately one point one five zero seven seven nine four four eight statute miles after twelve-decimal rounding, or convert ten nautical miles and confirm the factor multiplies cleanly. When teaching navigation or unit analysis, pair the exact path with the mental one point one five shortcut so students see the drift on long hauls. Stay inside the absolute range so the multiplication cannot overflow into a non-finite result the solver must reject.
This landing targets people searching for nautical miles to miles, convert nmi to statute miles, or an exact one point one five zero seven seven nine calculator; it is not a general multi-unit travel hub, not a kilometres-to-miles primary form, not a knots-to-mph speed tool, and not an astronomical distance converter. Prefer this capability when the input is already in nautical miles and you only need statute miles for land-side reporting; if you must convert among many distance units in one call, use a broader travel distance unit converter instead.
What you can do with it
Marine and aviation planning summaries
Turn chart or flight-plan legs in nautical miles into statute miles for land-side briefings, weather narratives, and US-facing passenger copy with the same exact factor every leg.
Coastal logistics and SAR reporting
Search-and-rescue and coastal logistics teams convert nmi ranges to statute miles for road-support staging and public-facing distance statements.
FAQ
What formula converts nautical miles to statute miles?
Miles = nautical miles × (1852 / 1609.344). One international nautical mile is exactly 1852 metres; one international statute mile is exactly 1609.344 metres.
Is the factor exact or approximate?
Exact. This tool multiplies by 1852 ÷ 1609.344 from the international metre definitions, not a rough multiply-by-1.15 estimate or a survey-mile variant.
Can I convert statute miles back to nautical miles?
This capability is nautical miles → statute miles only. Divide miles by the same factor on your side, or use a bidirectional distance converter for other units.
Is the nautical miles to miles converter free?
The browser tool is free and runs locally.
Why is multiplying by 1.15 not good enough?
It drops the trailing decimals of 1.150779448024, and that small gap grows over a long coastal passage or a multi-leg flight plan. The exact ratio keeps land-side figures consistent with the chart.
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/conv/nautical-miles-to-miles \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"nmi":1}'const res = await fetch("https://api.kit.forhosting.com/conv/nautical-miles-to-miles", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"nmi": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/nautical-miles-to-miles",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"nmi": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/nautical-miles-to-miles", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"nmi":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"nmi":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/nautical-miles-to-miles", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"nmi": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.nautical_miles_to_miles",
"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
Invalid or missing input fails with a clear invalid_input error instead of inventing a number.
How to call the API and what comes back
Absolute values must stay within the published limit of one trillion. Prefer bare numbers when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without unit suffixes or thousand separators. Send a JSON body with one required finite number field named nmi. Aliases nautical_miles, nautical_mile, nm, value, length, and distance are accepted so SDK clients and form posts can use the name that fits the product. On success the response echoes rounded nmi, sets miles, result, and converted to the same rounded statute-mile magnitude, unit to the token mi, from_unit to nmi and to_unit to mi, factor to the rounded ratio one thousand eight hundred fifty-two over one thousand six hundred nine point three four four, meters_per_nmi to one thousand eight hundred fifty-two, meters_per_mile to one thousand six hundred nine point three four four, formula to the string miles equals nmi times that ratio, message to a short English summary, and steps to an ordered array of substitution lines. Failed validation—missing fields, non-finite numbers, bare plus or minus signs, non-numeric strings, values outside absolute limits, or a non-finite converted result—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item.
Practical tips, checks, and related searches
Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit nmi or pass text.
Integration use cases
Homework and unit-test fixtures
Students and engineers convert classroom nautical-mile readings to statute miles and pin golden JSON so browser and API arithmetic never drift.
Technical questions
What happens on missing or non-numeric input?
The API returns invalid_input naming the problem (for example a missing nmi field). Failed tasks are not charged.