Flight price per mile calculator

Pricing for successful API calls is the published base of $0.002 per item; failed validation is not charged.

How flight cost per mile and per kilometer are calculated

Start from a concrete itinerary you can price and measure: a published ticket total and a great-circle or carrier-published route distance. The calculator first converts the input distance into both units using the exact international statute mile factor of 1.609344 kilometers per mile, the same constant used by standard length converters. Negative distances, negative ticket prices, missing fields, non-finite values such as NaN or Infinity, and unknown unit strings also fail early. When you have only airport codes, resolve the great-circle distance offline or with a separate geo tool and paste the number here—this capability deliberately does not call maps APIs so results stay reproducible and free of network variance. Enter ticket_price as a finite non-negative amount in major currency units such as dollars or euros—include taxes and mandatory fees when you want an all-in unit rate, or use base fare alone when you are comparing only the air portion across carriers. Enter distance as a positive number, and set distance_unit to mi for statute miles or km for kilometers. It then divides ticket_price by distance in miles to obtain price_per_mile, and by distance in kilometers to obtain price_per_km. Because both rates always appear in the response, a North American traveler who thinks in miles and a European traveler who thinks in kilometers can share one JSON object without a second conversion step. If distance is exactly zero the division is undefined, so the capability throws invalid_input with a message that price per mile cannot be computed when route distance is zero.

What you send and what you get back

Classic checks include a three-hundred-twenty dollar fare over two thousand four hundred fifty miles, which produces a clear cents-scale price per mile you can compare with another routing that is longer but cheaper on the headline fare. Wire the free browser form for one-off booking decisions, then call the identical contract from scripts when you score dozens of scraped fare-and-distance pairs into a bulk value table. Send three required fields. ticket_price is a finite number greater than or equal to zero in major currency units; aliases price, fare, and cost are accepted. distance is a finite number strictly greater than zero representing route length. distance_unit is the closed enum mi or km; friendly aliases such as mile, miles, kilometer, and kilometres are normalized, while anything else fails with invalid_input. JSON strings that parse as numbers are accepted the same way as numeric literals for the two numeric fields. Missing any field, empty strings, NaN, Infinity, negative price, zero or negative distance, and unrecognized units all fail with invalid_input and are not charged. On success the response echoes the cleaned ticket_price, distance, and distance_unit, the dual distances distance_mi and distance_km, the dual rates price_per_mile and price_per_km, the constant km_per_mi of 1.609344, the method label ticket_price_over_distance, and a human-readable formula string. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance. Downstream tools can threshold on price_per_mile alone, store the full object for audit, or map currency fields into multi-currency reports after converting major units with a separate FX step this capability deliberately does not perform.

Where flight price-per-mile calculators show up in real work

Leisure travelers comparing a nonstop and a one-stop often need more than the lowest listed fare: a slightly more expensive nonstop can still win on time, but a much longer multi-stop routing should look expensive per mile if the savings are tiny. Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.