Skip to content

Flight logs readout

The Flights page has two tabs:

  • Connected [model] - logs currently stored on the selected device.
  • Local files - flights imported into the application’s archive.

Counts may show a dash while data is loading.

Each row shows the source filename, device model, Imported, Device log, or Unreadable status, altitude, maximum velocity, duration when analysis is available, and device serial number when available.

For a readable log:

  • Open flight opens Mission replay directly from the device.
  • Import locally copies the flight into the local archive while leaving the device log in place.
  • Delete file removes the log from the device after confirmation.

An imported device log cannot be imported again, but it can still be opened from the device and managed in the local tab.

Unreadable logs show the read or analysis error and have no replay or import action. Invalid CSV content, missing or invalid timing data, unsupported values, or another read error can make a log unreadable.

Each local row shows the source filename, Nominal or the number of data-quality warnings, maximum altitude, maximum velocity, duration, source device serial number, sample count, and import date.

  • Open flight opens Mission replay from the local archive.
  • Export CSV opens a save dialog and writes a CSV copy. The dialog defaults to the source filename and filters for CSV files.
  • Delete removes the local archive entry after confirmation. It does not affect the original device log.

Local files tab with one imported flight showing altitude, maximum velocity, duration, warnings, and the Open flight, Export CSV and Delete actions

  • Local library is empty means no flight has been imported yet.
  • Connected flight computer unavailable means the device-log query failed; the local library remains usable.
  • No device flight logs means the selected computer exposes no logs.
  • A loading message appears while either source is being read.
  1. Open Flights and select Connected [model].
  2. Confirm that the log is readable.
  3. Select Import locally to preserve a copy.
  4. Open the local flight when offline review is needed.
  5. Use Mission replay to inspect telemetry and flight phases.
  6. Export CSV for external analysis when required.
  7. Delete the local copy only when it is no longer needed.