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 start from a scheduled flight, be typed in directly, or be imported from a CSV or DJI flight records.

Logging a flight

Section titled “Logging a flight”

Open Log flight (on the Flight logs page, the Fleet page, or as the dashboard’s quick action) to start the wizard:

  1. Aircraft — pick from your fleet.
  2. Details — start and end date/time, and location. Under location, Pick on map opens a map: tap the spot to fill in the latitude and longitude. Without a pointer, move the map until the crosshair is on the spot and choose Use map centre. You can also type the coordinates.
  3. Crew — who was Pilot in Command, plus any additional crew.
  4. Review — check everything before it becomes a record. (An end time is optional on a draft.)

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.

The map on a flight log

Section titled “The map on a flight log”

Open a flight log to see where it happened. A log with coordinates shows a small map with its location. A log imported from a DJI flight record into a new draft also shows the GPS track as a line from take-off to landing; the track is simplified (the shape of the flight, not every fix), and the page says so. Most older logs have no coordinates and no track, and the map area says that instead of showing an empty box.

When the terrain data covers the launch area, the log also shows an estimated max height above ground (from USGS 3DEP terrain data), or says why there is no estimate. It is an estimate from the aircraft’s height above take-off, shown separately from the max altitude AGL you record yourself. If the estimate differs from the aircraft’s own height above take-off by more than 50 ft, the log asks you to check it: the ground under the flight may be higher or lower than at take-off, or the terrain data may be off. If you record the flight’s altitude as measured from a structure, the estimate is not shown, because it measures from the ground at take-off. See Map.

Correcting a filed log

Section titled “Correcting a filed log”

Once a log is filed, fixing something in it goes through an amendment rather than a silent edit (only the current version of a filed log can be amended): 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 flights

Section titled “Importing flights”

Import flights opens a dialog with two choices: a CSV export (Aloft, AirData, DJI or your own spreadsheet) or DJI flight records (DJIFlightRecord files from a controller or phone). The result panel shows counts: imported, matched to existing (a scheduled or event flight whose actual times were updated), skipped, and failed. Importing the same file again says it was already imported.

New flights arrive as drafts. Check the pilot and purpose, then file them from the Drafts tab (or Review imported flights); hours count once a flight is filed.

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

Section titled “What’s next”