#range

Aircraft fuel-planning maths as an API, computed locally and deterministically — the endurance, range and fuel-required numbers a pilot, dispatcher or flight-sim developer plans a flight with, all honouring a reserve. The endurance endpoint gives how long you can fly = usable fuel ÷ burn rate, holding back a reserve (30 min day / 45 min night VFR, 45 min IFR is typical), so the usable endurance is the time you can actually plan to rather than the tanks-dry figure — 50 gallons at 10 gph is 5:00 total but 4:15 usable on a 45-minute reserve. The range endpoint turns that into distance = usable endurance × ground speed, so it lives or dies on the wind: a headwind cuts the ground speed and the range while burning the same fuel per hour, which is why you plan on the forecast ground speed, not the true airspeed. The fuel-required endpoint sizes the load for a leg = trip time × burn plus the reserve — 300 nm at 120 kt and 10 gph needs 25 gallons of trip fuel plus 7.5 reserve, 32.5 total — to which a real flight adds taxi and climb allowances. Everything is computed locally and deterministically, so it is instant and private. Ideal for flight-planning and EFB apps, dispatch and flight-school tools, flight-simulator utilities, and general-aviation calculators. Pure local computation — no key, no third-party service, instant. Add taxi/climb and a personal margin; confirm against tank capacity and weight-and-balance. 3 compute endpoints. For glide range use a glide-ratio API; for density altitude a density-altitude API.

api.oanor.com/fuelburn-api

Electric-vehicle charging maths as an API, computed locally and deterministically — the three numbers every EV driver and charging app actually needs. The charge-time endpoint gives how long a session takes: from the battery size and the gap between the starting and target state of charge it works out the energy to add and the time at a given charger power and efficiency — a 60 kWh battery from 20 % to 80 % on a 7.2 kW home charger at 90 % efficiency takes about 5.6 hours, and it reminds you that DC fast charging slows sharply above 80 % so road trips should be planned around the fast part of the curve. The range-added endpoint turns a charging session into miles: from the charger power, the minutes plugged in and the car's miles per kWh it gives the energy and range added, plus the handy "miles per hour of charging" figure — a 7 kW home charger adds roughly 22 mi/hr, a 150 kW DC station hundreds. The cost endpoint gives what a charge costs, correctly billing the energy drawn from the grid (the energy to the battery divided by the charging efficiency) times the price per kWh, with the effective cost per usable kWh — home overnight rates make EV miles very cheap while DC fast chargers cost several times more. Everything is computed locally and deterministically, so it is instant and private. Ideal for EV apps, route and trip planners, fleet and charging-station tools, charge-cost calculators and dashboards. Pure local computation — no key, no third-party service, instant. Estimates — real DC charging tapers above 80 % and cold weather cuts range. 3 compute endpoints. For battery runtime use a battery API; for generic energy cost use an energy-cost API.

api.oanor.com/evcharging-api