Taxi minutes
What it is
Section titled “What it is”Taxi minutes is the estimated one-way taxi time used to prefill the bracketing times on the Log Flight screen. It is a data-entry convenience only: it lets a pilot enter two of the four bracketing times and have the form fill the rest.
Taxi minutes do not affect any charge. They do not feed billing, airborne hours, or airframe hours. Airborne time is the measured takeoff-to-landing interval; if no wheels times are captured it is zero. (Earlier versions computed airborne time as block time − (2 × taxi minutes); that derivation has been removed.)
Who can use it
Section titled “Who can use it”Members submitting a usage log see the prefill on the form when their syndicate captures both clock (block) time and airborne time: entering one bracketing time fills its counterpart, offset by the taxi value. On a syndicate that captures engine meter only, the value is stored but the pilot sees no prefill on the form. Only admins can change the configured value.
Where to find it
Section titled “Where to find it”- Syndicate default: Admin, then Usage capture. The taxi minutes field is part of the capture configuration for the syndicate.
- Per-asset override: the individual asset’s billing settings. A blank value means the asset inherits the syndicate default.
- At first setup: a syndicate that records both block and airborne times can accept the setup wizard’s offer to fill the airborne times in from the block times, which starts the syndicate on 5 minutes a side. Change it here at any time.
Fields / options
Section titled “Fields / options”| Field | Type | Default | Notes |
|---|---|---|---|
| Default taxi minutes | Integer | 0 | One side of the flight (taxi-out and taxi-in are prefilled symmetrically). Zero switches the prefill off entirely: nothing is written into the counterpart field, rather than a zero-length offset being applied. The form takes a whole number from 1 to 30. As you type, a value outside that range is marked Must be at least 1 or Must be at most 30, and Save Settings stays disabled until it is corrected. To switch the prefill off, clear the box: a blank saves as no value and resolves to zero. The database holds the syndicate default to the same bound as an asset’s own value, a whole number from 0 to 30 (or no value), so a value outside that range cannot be stored by any route, not only through this form. |
Behaviour rules
Section titled “Behaviour rules”- Prefill only, no billing effect. The configured value is never part of any charge, on any billed measure. It only influences what the form pre-populates.
- Symmetric prefill. Entering off-blocks fills takeoff offset by the taxi value (taxi-out), and entering landing fills on-blocks offset by the taxi value (taxi-in). The reverse directions also work.
- Never overwrites a hand-entered value. A time you type by hand is left untouched; only the empty counterpart of the field you edit is filled, and the filled value is a normal, editable timestamp.
- Fits inside known block times. A takeoff or landing estimate is left blank if the configured taxi allowance would leave no room for flight within the entered block times. Enter the actual times instead.
- Ground runs and recorded flights. Ground-run time edits do not prefill airborne times. Checking a Watch capture or editing a saved log keeps its recorded times and missing values. Editing one time changes only that field; the phone does not fill another using taxi defaults. Recorded spans remain available and are retained when saving even if the syndicate’s capture settings have since changed. Choosing Ground run: no takeoff hides and excludes airborne times; switching back to Flight before saving restores the entered values. The × (Clear) button removes only the chosen time and its date.
- Not editable at logging time. The log screen does not expose a per-log taxi override; the configured syndicate or per-asset value drives the prefill.