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 and owners 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 the syndicate’s time capture mode 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 today (UTC). You can back-date — the booking must cover the date. |
| Notes | Free text | No | Anything the pilot wants recorded. Plain text only. |
Meter readings (engine-meter and both modes)
Section titled “Meter readings (engine-meter and both modes)”| Field | Type | Required | Notes |
|---|---|---|---|
| <Meter> Start | Number | Yes | Labelled with the syndicate’s meter label — “Hobbs Start”, “Tacho Start”, etc. Label comes from engineMeterLabel. |
| <Meter> End | Number | Yes | Must be ≥ Start. |
The difference (End − Start) is the meter delta. The billable hours value depends on the billing basis — see Time capture modes.
Clock times (clock-time and both modes)
Section titled “Clock times (clock-time and both modes)”| Field | Type | Required | Notes |
|---|---|---|---|
| Off Blocks | Time (HH:MM) | Yes | Brakes released / start of taxi. |
| On Blocks | Time (HH:MM) | Yes | Brakes on / parked. |
Block time = On Blocks − Off Blocks. Airborne time = block time − taxi minutes (see Taxi minutes).
Aircraft-specific fields
Section titled “Aircraft-specific fields”| Field | Type | Required | Notes |
|---|---|---|---|
| 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) | No | E.g. EGMC. |
| Arrival | ICAO code (free text) | No | Used to decide whether landing fees apply — see Behaviour rules. |
| 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 | Tick box | No | Defaults to unticked. Tick for an engine run that didn’t leave the ground — hides the landings, touch-and-gos, and block-time fields, and stops airframe hours from advancing. The engine meter still updates. See Log a ground run or ferry flight. |
Attribution (maintenance and ferry flights)
Section titled “Attribution (maintenance and ferry flights)”| Field | Type | Required | Notes |
|---|---|---|---|
| Used by (member) | Member picker | Yes — one of these two | Which syndicate member operated the asset. Defaults to the current user. The asset’s tech log reads this field — not the booker — to answer “who operated this asset on this day.” |
| Used by (name) | Free text | Yes — one of these two | A free-text name for a non-member operator (for example, a workshop pilot or an external mechanic). A free-text name records attribution without creating a user record. |
Exactly one of Used by (member) or Used by (name) must be set — the form clears the other when one is filled. For most flights, the default (current user as the member) 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.
- Required fields depend on billing basis:
engineMeterbasis — Start and End are required; clock times are not.blockbasis — Off Blocks and On Blocks are required; meter readings are also captured if the mode isboth.airbornebasis — same as block; taxi minutes are subtracted to produce airborne hours.
- Landing fees only apply when the arrival matches the asset’s base airfield. If Arrival is blank, the system assumes home. If Arrival is a different ICAO code, landings and touch-and-gos do not incur event fees for that log.
- Charge preview appears in-screen while you fill the form and updates as you type. 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
edited_byandedited_at; the original values are not kept separately but the edit is visible in the log history.
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.