Skip to content
Tobren Operations Docs

Flight logs

A flight log is the record of what actually happened — as opposed to the schedule, which is the plan. A log can come from completing a scheduled flight, from typing one in directly, or from importing a CSV.

Logging a flight

Open Log flight (from the Fleet page, or the dashboard’s Log flight quick action) to start the wizard:

  1. Aircraft — pick from your fleet.
  2. Details — start and end date/time, and location.
  3. Crew — who was Pilot in Command, plus any additional crew.
  4. Review — check everything before it becomes a record.

From Review you can Save as draft — every field stays editable, and a draft doesn’t count toward reports or currency calculations — or File log. Filing asks you to confirm first: it spells out that filing creates a permanent compliance record, since a filed log is no longer freely editable.

Correcting a filed log

Once a log is filed, fixing something in it goes through an amendment rather than a silent edit: the correction is a new version, and the original stays in the record with a note pointing to what superseded it. Nothing is ever quietly overwritten.

Importing from a CSV

Import CSV opens a dialog where you upload a file exported from a flight-tracking tool. The import always succeeds at the API level even when individual rows fail to parse — the result panel tells you what was imported, what matched an existing log, and what didn’t parse, so a large historical import doesn’t demand a row-by-row confirmation.

The accepted CSV shape, direct support for Aloft and AirData exports, and a guide for moving a full flight history over from another product → Imports & migration.

What’s next