Edit a past usage log

Fix a mistake in a saved usage log: a wrong meter reading, a wrong flight or ground-run choice, an incorrect touch-and-gos count, or a typo in the notes.

Before you start

You must be the log’s author, or an admin of the syndicate.
The booking must still be in confirmed status. Once a booking has been finalised (status completed), its logs are locked to ordinary editing. After finalisation only an admin can correct a log, via the audited Correct flight action. Ask your admin if you spot a problem on a completed booking.
Every edit is stamped with who made it and when, for audit. The only user-visible sign is an “(edited)” marker on the log entry; there is no browsable history view.

Steps

Open the booking containing the log. From the calendar, tap the booking; from the Bookings tab, pick it.
Scroll to the Usage logs section. Each log shows its date, route, and readings.
Tap the pencil icon on the log you want to edit. (The tooltip reads Edit usage log.)
The Log Flight screen opens in Edit Flight mode with the existing values pre-filled.
Change the fields you need to. The full field list is the same as when creating a log; see Usage log fields.
Tap Update Usage at the bottom of the form.

You’ll see a success snackbar and the updated log appears in the booking.

What editing does

Each populated time has an × (Clear) button; clearing it removes only that time and its date. Ground run: no takeoff hides the airborne fields and excludes them when saving; switching back to Flight before saving restores the entered times.
Keeps recorded times and missing values as they were until you edit them. Changing one time does not fill another using the taxi default. Recorded timing spans remain available even if the syndicate no longer captures that span. A meter-only flight with a single recorded departure keeps that single departure; it does not acquire a block-time span.
Overwrites the previous values with the new ones. The prior values are not kept separately; only the audit stamp (who edited and when) is recorded.
Updates the charge preview. Whenever the inputs are complete, the preview reflects the new values.
Tells the booking’s owner when an admin changes the hours or price of a flight they neither flew nor own the booking for: they get a Flight corrected notification with the hours before and after and the new price. A change to the notes or the route alone tells nobody.
Does not apply to a completed booking. Completed bookings are closed to ordinary editing; an admin corrects the flight via Correct flight, which fixes the log and posts no money; the booking then offers Apply the new charge for any difference.

Delete a log

A log entered twice, or against the wrong booking, can be removed instead. The same people can delete as can edit, on a booking that is still confirmed, except that a log which reported a defect can be deleted only by an admin.

In the Usage logs section, tap the bin icon on the log. (The tooltip reads Delete usage log.)
The Delete Usage Log? dialog says it will remove the log from the booking. Nothing has been charged yet: a log can only be deleted before its booking is finalised. Tap Delete to remove it, or Cancel to back out and change nothing.

You’ll see Usage log deleted.

If it goes wrong

The pencil icon isn’t there: you are not the log’s author and not an admin, or the booking has been finalised (status is completed) and you are not an admin. An admin sees the pencil on a finalised booking as Correct flight; see Correct a finalised booking.
“End value must be greater than the start value”: the same validation that applies to new logs applies to edits. Fix the reading before saving.
Cannot save while offline: edits queue and sync when you reconnect. If the queue doesn’t drain, check your connection.