Record flights and upload logs

Every flight needs a record. echoMike takes them three ways — a DJI log file you upload, a flight you pull straight from DJI, or one you type in by hand — and they all land in the same logbook and count the same way toward pilot currency.

Before you start

The job Logs tab needs the flight logs plan feature, plus either the Manage flight logs permission or organisation admin. Without the plan feature the tab is not shown at all, and opening a logs link falls back to the job overview.

Import from DJI additionally needs the DJI log integration enabled and an account linked. Without it, upload the file yourself.

Steps

1. Open the job Logs tab

   Open the job and select Logs. It has two sub-tabs: Flight and Vehicle.

2. Upload the log file

   Select Upload log. The dialog is titled Upload DJI Flight Log and takes .txt and .DAT files. A toast confirms Flight log uploaded — parsing… and the flight appears in the list as parsing finishes.

3. Link the aircraft

   Open the parsed flight and link it to an airframe from your fleet. If the drone is not in the fleet yet, create it from here — echoMike defaults the name to the model the log parsed as, and confirms Drone created and linked. Link the batteries used on the same screen.

4. Assign the pilot

   Set the pilot on the flight row. A flight with no pilot never becomes a logbook entry and never counts toward currency, so this is the step not to skip.

5. Check the telemetry

   Expand Telemetry evidence for the battery, signal, dynamics and route charts, and Track for the flown path on the map. Scrubbing the track switches the summary panel to a Live readout at that moment.

Options

Import from DJI instead

Import from DJI pulls flights from a linked DJI account without you handling files.

Record a flight by hand

Not every flight leaves a log file. Go to Logbooks, select Log a flight, and fill in Flight started, Flight ended, Operating location, Take-off location, Landing location, Operation mode, Day / night, Activity description, and the CAA identity fields — Operator name, Operator ID, Remote Pilot name and Flyer ID. The dialog marks which fields are still missing.

Import a batch of history

Import flight history (CSV) in the logbook’s overflow menu brings in flights flown before you started using echoMike.

Vehicle trips

The Vehicle sub-tab holds Vehicle logs — the trips driven to and from the job. Vehicle logs are only visible to admins.

What happens next

Screenshot pending

Job Logs tab, Flight sub-tab: the flight list with Upload log and Import from DJI buttons, a parsed flight row with aircraft and pilot assigned, and one row in a failed state so the failed filter chip is visible.

A parsed, pilot-assigned flight becomes an entry in the flight logbook, contributes its duration to the aircraft’s technical log, and counts toward the pilot’s rolling flight currency once it is approved and the aircraft sits in an equivalence group.

Troubleshooting

“Parse failed.” The flight row shows the parser’s error. Re-parse the flight from its detail panel — the toast reads Re-parsing flight — this usually takes a few seconds…. If it fails again the file is not a log echoMike can read; record the flight by hand instead.

Several rows failed. The list header shows a 3 failed chip. Select it to filter down to just those, and Clear filter to go back.

“You do not have permission to view flight logs.” You are missing the Manage flight logs permission. An organisation administrator grants it — see Why can’t I see this?.

“No flight logs yet. Upload a DJI log file or import one from DJI.” Nothing has been recorded against this job.

The flight is not counting toward currency. Check three things in order: the flight has a pilot, its aircraft is linked to a fleet airframe, and that airframe belongs to an aircraft equivalence group. The flight logbook’s Counting column names whichever is missing — No aircraft linked, Needs group or Drone not grouped.