Tukuk-OS📏 Boston to Las Vegas
| Great-circle (haversine, R = 6371.0088 km) | 3,813.1 km |
| Miles (international) | 2,369.4 mi |
| Nautical miles | 2,058.9 nmi |
| Initial true bearing | 274.6° W |
| Flight at 900 km/h (no climb, taxi or wind) | 254 min |
| Drive at 80 km/h, non-stop | 47.7 h |
| Latitude change | -6.1900° |
| Longitude change | -44.0800° |
ℹ️ What this tool does & how it works
The air line between the two is 3,813 km (2,369 statute miles, 2,059 nautical miles). It comes from the haversine formula on the two coordinate pairs the page carries — Boston at 42.3600° N, -71.0600° W and Las Vegas at 36.1700° N, -115.1400° W — using the IUGG mean Earth radius of 6371.0088 km. Leaving Boston toward Las Vegas you start on a true bearing of 274.6° (W); because the Earth curves, that heading drifts as you go.
How the Boston and Las Vegas distance is worked out
Two points on a sphere are separated by the shorter arc of the great circle that passes through both of them, and the haversine formula is the numerically stable way to get its length: it converts the latitude difference and the longitude difference into a single chord ratio, takes its square root, and multiplies by twice the radius. Written that way it stays accurate even for pairs a few kilometres apart, which is why it is still the standard in navigation code. The radius used here is 6371.0088 km, the IUGG mean radius; on the true WGS84 ellipsoid the same Boston–Las Vegas arc differs by a few tenths of a per cent depending on the route's orientation, which is well inside the error of a city-centre coordinate.
What that number means for an actual trip
It is the distance a bird flies. A 3,813 km line becomes roughly 4,957 km of road once hills, borders, river crossings and bypasses are counted — the 1.2 to 1.4 multiplier is the usual empirical range, and this page does not pretend to know the road you would take. Air distance is closer to the figure above, though airline routings, wind and holding add time to the 254 minutes a perfect 900 km/h cruise would take. Rail sits between the two. The latitude and longitude changes in the table show why the line is not simply "north" or "east": a 6.19° shift in latitude is about 688 km, while the same number of degrees in longitude shrinks with the cosine of the latitude.
Both positions, exactly
Boston, United States (Americas): 42° 21′ 36.0″ N, 71° 03′ 36.0″ W — decimal 42.36, -71.06, GeoHash drt2yzrsv. Las Vegas, United States (Americas): 36° 10′ 12.0″ N, 115° 08′ 24.0″ W — decimal 36.17, -115.14, GeoHash 9qqjgbt9e. Those two pairs are all this page needs, and everything above is derived from them; nothing is fetched, and the coordinates you can edit in the form are recalculated by your own browser, so a different pair costs nothing and stays on your device.