Usage log fields
What it is
Section titled “What it is”A usage log records one session of asset use against a booking. For aircraft, that is one flight (or one leg of a multi-leg booking). Multiple logs can exist on a single booking (e.g. three flights in a week-long booking).
Who can use it
Section titled “Who can use it”- Members can log their own usage against their own bookings.
- Admins can log usage on any booking in the syndicate.
Any member who can see the booking can view its logs in the booking detail. Photo visibility is gated separately; see Usage photo privacy.
Where to find it
Section titled “Where to find it”- Booking detail → Log Flight button.
- Route:
/bookings/:bookingId(or/syndicates/:syndicateId/bookings/:bookingId). - The log form is also reached from the flight entries in the per-asset Usage history.
Fields / options
Section titled “Fields / options”The form adapts to which measures the syndicate captures and to per-asset overrides. Not every field is shown in every configuration.
Always shown
Section titled “Always shown”| Field | Type | Required | Notes |
|---|---|---|---|
| Date | Date picker | Yes | Defaults to the booking start date in the pilot’s local timezone, capped at today. You can back-date (the booking must cover the date). |
| Notes | Free text | No | Anything the pilot wants recorded. Plain text only. |
Meter readings (shown when the engine meter is captured)
Section titled “Meter readings (shown when the engine meter is captured)”| Field | Type | Required | Notes |
|---|---|---|---|
| <Meter> Start | Number | Yes | Labelled with the syndicate’s engine-meter label: “Hobbs Start”, “Tacho Start”, etc. |
| <Meter> End | Number | Yes | Must be ≥ Start. |
The difference (End − Start) is the meter delta. Whether it drives the charge depends on the billed measure.
Clock times (shown when block time is captured)
Section titled “Clock times (shown when block time is captured)”| Field | Type | Required | Notes |
|---|---|---|---|
| Off Blocks | Time (HH:MM) | Yes | The start-of-taxi time. The label is configurable; the default is “Brakes off”. |
| On Blocks | Time (HH:MM) | Yes | The end-of-taxi time. The label is configurable; the default is “Brakes on”. |
Block time = On Blocks − Off Blocks. Airborne time is a separate, measured value: Landing − Takeoff when both wheels times are recorded, otherwise zero. It is never derived from block time, and taxi minutes only prefill the bracketing times.
Aircraft-specific fields
Section titled “Aircraft-specific fields”| Field | Type | Required | Notes |
|---|---|---|---|
| Takeoff | Time (HH:MM) | Yes, when airborne time is captured | Wheels up. Shown for aircraft. Captures the measured time aloft for airborne billing. |
| Landing | Time (HH:MM) | Yes, when airborne time is captured | Wheels down. Shown for aircraft. Airborne time is Landing − Takeoff; zero if either is missing. |
| Pilot in Command | Member picker + free text | No | Defaults to the current user. You can type a non-member name. |
| Pre-flight By | Member picker + free text | No | Defaults to the Pilot in Command. |
| Departure | ICAO code (free text) | Yes, for a flight | E.g. EGMC. Required for any flight that took off; exempt for a ground run (No takeoff ticked). |
| Arrival | ICAO code (free text) | Yes, for a flight | Required for any flight that took off. Decides whether event fees apply; see Behaviour rules. A blank arrival is never treated as “home”. |
| Landings | Integer | No | Full-stop landings. Defaults to 0. Hidden when No takeoff is ticked. |
| Touch & Gos | Integer | No | Defaults to 0. Hidden when No takeoff is ticked. |
| Fuel Added | Number + unit selector | No | Units configured on the asset (litres / US gallons / imperial gallons). |
| Oil Added | Number + unit selector | No | Units configured on the asset. |
| No takeoff | Switch | No | Shown when the syndicate does not capture airborne time. Switch on for an engine run that did not leave the ground. Hides landings and touch-and-gos; stops airframe hours from advancing. The engine meter still updates. The Off/On Blocks fields stay visible if the syndicate captures block time. When the syndicate does capture airborne time, this switch is replaced by a “Was there airborne time?” choice (“It flew” / “Ground run”): choosing “Ground run” has the same effect. See Log a ground run or ferry flight. |
| Any defects? | Choice (two options) | Yes, for aircraft flights that took off | Force-a-choice: No known defects or Report a defect. The pilot-in-command’s per-flight declaration, captured at the moment of logging. Hidden for ground runs (No takeoff ticked) and maintenance logs. Choosing “Report a defect” opens the squawk form after the log saves. |
Attribution
Section titled “Attribution”| Field | Type | Required | Notes |
|---|---|---|---|
| Used by | Member picker with free-text fallback | Yes | Shown on every log. Defaults to the current user. Pick a syndicate member or type a free-text name for a non-member operator (for example, a workshop pilot or an external mechanic). The asset’s tech log reads this field, not the booker, to answer “who operated this asset on this day.” |
For most flights, the default (current user) is correct. See Log a ground run or ferry flight for when to override it.
| Field | Type | Required | Notes |
|---|---|---|---|
| Meter photo (end) | Image | No | Attached to the log as evidence. See Hobbs photos. |
A start-meter photo can be captured as a user aid during logging but is not saved to the log.
Behaviour rules
Section titled “Behaviour rules”- Start ≤ End. The form blocks submission and shows an inline error when End < Start.
- Taxi-derived time prefill (aircraft). When taxi minutes is set, entering one of the four bracketing times fills its counterpart: Off Blocks ↔ Takeoff and Landing ↔ On Blocks, each offset by the taxi time (taxi-out is Off Blocks → Takeoff, taxi-in is Landing → On Blocks). You enter two of the four and the form derives the rest. A value you set by hand is never overwritten by derivation, and only the direct counterpart of the field you edit is touched.
- Required fields depend on which measures are captured:
- Engine meter captured: Start and End are required.
- Block time captured: Off Blocks and On Blocks are required.
- Airborne time captured: Takeoff and Landing are required (a flight that took off must record both, so airborne time is real rather than zero).
- A flight (one that took off) also requires Departure and Arrival; a ground run does not.
- Event fees are home-airfield fees. Landing and touch-and-go fees apply only when the flight’s Arrival matches the asset’s home airfield, resolved from the asset’s configured home airfield and falling back to a syndicate-wide default if one is set. If the arrival is a different airfield, or no home airfield is configured, no event fees are charged for that log (the time-based usage charge is unaffected). The comparison ignores case and surrounding spaces. Because every flight requires an arrival, a blank arrival is never treated as “home”.
- The defect declaration is mandatory for aircraft flights and immutable after save. An aircraft log where the flight took off cannot be saved until No known defects or Report a defect is chosen. The declaration is captured once, at the moment of logging; editing the log afterwards shows it read-only and never resends it. See Pilot-in-command responsibility.
- Charge preview is computed on the server and shown when you are online. The figure comes from the same calculation finalisation uses, requested as you fill the form, so the preview and the eventual charge agree. Offline, the form shows that an estimate is available online rather than calculating one on the device. It reflects the member’s effective rate at the time of logging.
- The saved log is not a financial record. The charge only becomes a ledger entry when the booking is finalised. See Finalisation rules.
- Edits create an audit trail. Editing a saved log stamps the editor’s identity and the moment of the edit; the original values are not kept separately. The only user-visible sign of an edit is an “(edited)” marker on the log entry in the booking detail.
See also
Section titled “See also”- Log your first flight: end-to-end walkthrough, from booking to saved log.
- Log a ground run or ferry flight against a maintenance booking: when the fields on this page are used from a maintenance booking.