Log a flight

Record a usage session against a booking — a flight for an aircraft, a leg of a charter for a boat, a trip for a vehicle. The instructions below are written for aircraft; the screen adapts to the asset type.

Before you start

You must be the booking’s author, or an admin or owner of the syndicate.
The booking must be confirmed. You can log usage during or after the booked time. Past completed bookings cannot have new logs added.
A booking can have more than one log — e.g. three flights in a week-long booking. Add one log per flight.

Log a flight from the booking

Open the booking. From the calendar, tap the booking. From the Bookings tab, pick it from the list.
Tap Log Usage at the bottom of the booking detail screen. (For an aircraft the screen that opens is titled Log Flight.)
Fill in the fields. Exactly which fields appear depends on the asset’s time capture mode and its configuration. Full field reference: Usage log fields.
Tap Log Usage at the bottom of the form to save.

You’ll see a “Usage logged successfully” snackbar and the log appears in the booking’s usage-logs section.

Key fields for a typical flight

Date — defaults to today. Back-date if the flight happened earlier within the booking.
<Meter> Start and <Meter> End — the asset’s meter reading at the start and end of the flight. The label reflects your syndicate’s meter: “Hobbs Start”, “Tacho Start”, and so on. End must be at least Start.
Off Blocks and On Blocks — when clock-time capture is configured. Off Blocks = brakes released, On Blocks = brakes on.
Departure and Arrival — ICAO codes, free text. Leave Arrival blank to indicate a return to base. Landing fees only apply when the arrival matches the asset’s home airfield.
Landings and Touch & Gos — counts. Both default to 0.
Pilot in Command and Pre-flight By — member pickers with free-text fallback.
Fuel Added and Oil Added — amounts, in the units configured on the asset.
Notes — free text for anything noteworthy.

Auto-fill meter readings with a photo

Both the Start and End meter fields have a camera button next to them.

Tap the camera icon.
Take a photo of the Hobbs or tacho meter.
On-device OCR reads the number and fills the field.
Check the filled number against the real meter. If it’s wrong, type over it — the field stays editable.

The End-meter photo is saved to the log as evidence. The Start-meter photo is held in memory to help you confirm your reading, but it isn’t saved. On web desktop the camera button produces no reading — use it on mobile.

Full detail: Hobbs and tacho photos.

Use Quick Capture on a flying day

If you’re about to fly and want a two-step workflow — capture the start readings on the ramp now, finish the log after you land — use I’m flying now instead.

On the booking detail screen, tap I’m flying now (shown on your own confirmed booking while it is still upcoming).
Enter the start-meter reading, take a start-meter photo, and tap Start Flight.
When you land, re-open the booking and continue — enter the end meter, end photo, landings, notes — and save. The log is created in the normal way.

Quick Capture is a convenience wrapper around the normal log-flight flow, not a separate log.

What happens after you save

The log is recorded against the booking.
For the booking’s author, the Log Usage button is replaced. The booking is now eligible for finalisation (see Finalisation rules).
auto-finalise (if enabled at syndicate level) may finalise the booking automatically; otherwise an admin finalises it later.

If it goes wrong

“Start value is required” / “End value is required” — the start or end meter field is empty.
“End value must be >= start value” — you typed an end reading below the start reading. Re-check the meter or typo.
“Enter a valid number” — the meter field must be numeric.
The Log Usage button is missing — the booking isn’t confirmed, or you aren’t the author and aren’t an admin. Viewers and non-owners cannot log usage against someone else’s booking.
OCR filled the wrong number — type over it. OCR is best-effort, and the drum boundary on some Hobbs meters reads as a slash.