Destination Point Calculator
Given a start point, bearing and distance, find the destination coordinates.
This page explains how the destination point calculator works, the data and formulas behind it, and how to interpret the result. Great-circle distances are the shortest path over the Earth's surface - the route aeroplanes actually follow. They are the baseline every other distance estimate starts from, and are accurate to ~0.3% of the more complex ellipsoidal (WGS84) distance. The tool is one of 329 free, open tools on JoseFitani for maps and geography. It runs in your browser with no sign-up needed. Use the search field or click the map to drop a pin - the tool uses the Haversine formula on a sphere of radius 6,371 km, plus mode-specific detour factors for driving, walking and flight-time estimates and returns the result in seconds. Below you'll find a step-by-step guide, real use cases, the methodology, FAQs, and data sources.
Formula: destination point from the spherical law of cosines on the WGS84 mean radius (6,371.0088 km) — accurate to a few metres for planning and education.
How to use this tool
Type your query, paste coordinates, or click on the map. The tool uses the Haversine formula on a sphere of radius 6,371 km, plus mode-specific detour factors for driving, walking and flight-time estimates to process your input locally in the browser.
The result appears instantly with the map showing your location. You can adjust by clicking elsewhere or searching a new place.
Click Copy to save to clipboard, or Share to send a direct link with the exact inputs.
What people use this tool for
Navigators who know their last confirmed position, the heading steered, and the distance run can compute where they should be now. This is the classic dead-reckoning step, done here with spherical math instead of a paper chart. It cross-checks GPS fixes and catches instrument errors before they compound.
Rescue coordinators can project outward from a last known position along likely travel bearings to generate search waypoints. Each projected point becomes a grid corner or a waypoint for a search team. Doing it computationally keeps every team working from identical coordinates instead of hand-drawn estimates.
Passage planners can build a route by projecting each leg from the previous waypoint using the planned course and leg distance. The resulting waypoint list drops straight into a chartplotter or autopilot. It is faster and less error-prone than measuring each leg off a paper chart with dividers.
Engineers sketching pipelines, power lines, or trails can project forward from a known point along a design bearing for a set distance. Each projected point becomes a candidate tower, valve, or marker location to verify on the ground. It turns a bearing-and-distance design into mappable coordinates in seconds.
How it's calculated
Uses the spherical Earth equations to project the destination along a great circle.
The calculation runs in your browser - no data is sent to our servers. Map tiles come from OpenStreetMap (ODbL license), geocoding uses Nominatim (1 request/second limit), and elevation uses the Open-Elevation API backed by SRTM data. All are free, open services.
All calculations use the WGS84 datum (EPSG:4326), the same as GPS. For other datums (NAD27, NAD83, ETRS89), a separate conversion is needed. The difference is typically under 1 metre - negligible for most uses but important for survey-grade work.
The formulas match those in professional GIS software (QGIS, ArcGIS, Global Mapper), just in a browser-friendly form. For sub-metre accuracy, use professional software with ellipsoidal calculations. Results are shown in multiple units: km and miles for distance, km²/m²/hectares/acres for area, metres and feet for elevation. Conversion factors are exact (1 mile = 1.609344 km), so the only error source is input precision.
Related tools and resources
Frequently asked questions
Does this account for Earth's oblateness?
No - this uses a spherical Earth model.
What inputs does the calculator need?
You provide a starting latitude and longitude, a bearing in degrees clockwise from true north, and a distance. The tool returns the latitude and longitude of the destination point. Make sure your distance unit matches what the tool expects — mixing kilometres and miles is the most common mistake.
How accurate is the destination over long distances?
The tool uses spherical Earth math, which is accurate to about 0.3% of the distance travelled — a few kilometres on a transoceanic leg. That is fine for planning waypoints and search grids. For survey-grade work, ellipsoidal geodesic libraries give tighter results.
What happens if my route crosses the antimeridian?
Crossing the 180° meridian is handled correctly: a route heading west past 180° longitude wraps around to −180° and continues. The destination longitude stays within the standard −180° to +180° range. Your chartplotter or map will interpret the wrapped value without any special handling.
Can the destination end up at the pole?
Yes, if you travel far enough toward a pole on the right bearing, the math correctly lands you at 90° latitude. Near the pole, tiny bearing changes swing the destination longitude wildly, which is mathematically correct but practically useless. Real polar navigation uses specialised techniques instead.
Is the bearing I enter the initial or final bearing?
It is the initial bearing — the heading you set out on from the start point. The tool projects along the great-circle path beginning with that heading. If you have a final bearing from the Bearing Calculator, convert it by adding or subtracting 180° before using it here.
Why doesn't my result match a flat-map measurement?
Flat maps distort distance and direction, especially east–west at high latitudes, so ruler measurements on them are unreliable. The calculator works on the sphere, where the true shortest path may arc away from what looks straight on screen. Trust the computed coordinates over the visual.
Can I chain multiple legs into a full route?
Yes — take the destination of one leg and use it as the start of the next, with the new leg's bearing and distance. This is exactly how passage planners build multi-leg routes. Keep a table of each leg so a typo in one step does not silently corrupt the rest.
Does it work offline?
The calculation runs entirely in your browser with no server calls, so it keeps working after the page loads even without a connection. Nothing you enter is transmitted anywhere. That makes it usable on a boat or in the field as long as the page was opened beforehand.
Data sources & methodology
- OpenStreetMap — Map tiles and address data.
- Open-Elevation API — Free elevation lookup.
- Nominatim — OpenStreetMap-based geocoding.
- WGS84 datum — Global reference datum used by GPS.