Taxi minutes
What it is
Section titled “What it is”Taxi minutes are the minutes of ground movement subtracted from block time to compute airborne hours. They matter when the billing basis is airborne, or when the asset rate is quoted on airborne time rather than block time.
Airborne time, per log: block time − (2 × taxi minutes) — taxi is applied to both the start and end of the flight (depart, then arrive). If the result is negative, it is floored at zero.
Who can use it
Section titled “Who can use it”Any member submitting a usage log sees the effect indirectly — the airborne-time value used for billing is computed from their block times minus the configured taxi minutes. Only admins and owners can change the value.
Where to find it
Section titled “Where to find it”- Syndicate default: Syndicate settings → Billing (
/syndicates/:syndicateId/settings/billing). Stored assettings.default_billing.default_taxi_minutes. - Per-asset override: Asset billing settings (
/syndicates/:syndicateId/assets/:assetId/billing). Stored asasset_billing_config.default_taxi_minutes. Null means inherit.
Fields / options
Section titled “Fields / options”| Field | Type | Default | Notes |
|---|---|---|---|
| Default taxi minutes | Integer | 10 (per side) | One side of the flight. Symmetric application at start and end means the total subtracted per log is double this value (i.e. 20 minutes by default). Constrained to 0–30 by a database check. |
Behaviour rules
Section titled “Behaviour rules”- Only used when the billing basis is
airborne. When billing onengineMeterorblock, the configured taxi value has no effect on charges. - Symmetric application. The configured value is subtracted at departure and again at arrival — it represents a single one-way taxi, not the total.
- Floor at zero. If a flight’s block time is shorter than twice the taxi minutes, the airborne time is recorded as zero, not negative.
- Not editable at logging time. The log screen does not expose a per-log taxi override — the configured syndicate or per-asset value is applied as-is to every log. To change taxi for a single flight, an admin can edit the relevant asset or syndicate setting and accept that the change applies to subsequent logs only (it is not retrospective).
- Changes are not retrospective. Updating the taxi minutes setting changes how future logs compute airborne time; existing logs keep their saved values.