Logging sessions
Log simulator runs and real-world flights down to the second, bind gear, save the site, and keep the conditions worth remembering.
The Log page is your flight logbook. It keeps two timecards that never mix:
- Real World: the quads, batteries, and conditions you flew; and
- Simulator: VelociDrone, Liftoff, DRL, and other simulator practice.
Log a session
- Open Log and choose the Real World or Simulator tab.
- Select Log session.
- Enter the date and duration. Duration supports minutes plus optional seconds.
- Select Next for the details that make the record useful later.
- Bind the airframe, radio, goggles, battery set, packs, saved location, crashes, conditions, and notes when they apply.
- Save the session.
The session appears in your list immediately and feeds the dashboard.
| Field | Behavior |
|---|---|
| Date | Defaults to today, but can be changed. |
| Duration | Minutes with optional second-level precision. |
| Airframe | Bound drone for real-world sessions when available. |
| Simulator | Simulator name for simulator sessions. |
| Battery set / packs | Real-world pack context and battery totals. |
| Location | Optional saved personal site label; create one inline with New site. |
| Radio / goggles | Equipment context for rig stats and ledger views. |
| Crashes | Crash count used by reliability and failure analytics. |
| Conditions and notes | Weather, track, airspace reference, gates, and anything else worth retaining. |
A session can be saved without a location or without every gear binding. Bind the airframe whenever possible if you want rig-specific maintenance and forecasts.
Saved locations
The Location picker lists your personal saved sites. New site saves a name and selects it immediately. Locations are not shared with a squadron and are not GPS or LAANC records. See Saved flight locations.
Preflight context
Eligible operations can include a preflight briefing with weather and operational context. Weather is a convenience; review it yourself. Airspace and LAANC references are evidence fields, not an automated filing or verification service. If your organization requires a JHA, complete it before the protected flight workflow.
Import a vendor flight log
Commercial organizations can use Import log for supported DJI CSV exports, legacy DJI text, Autel CSV, or generic telemetry CSV formats. BeaconUAV parses supported records, helps resolve the airframe by serial or manual selection, and adds the accepted result to the real-world timecard.
Encrypted or unsupported binary formats must be exported to a supported format first. Imported records can include video links or browser-prepared uploads where the commercial workflow permits it. Flight logs remain internal to the operation; client portals expose deliverables, not raw telemetry.
Edit and delete
Every session can be edited or deleted. Deletion asks for confirmation and removes its contribution from derived totals immediately.
How sessions feed the rest of the app
- Dashboard: airtime, streak, heatmap, volume, sim/real split, and rig usage.
- Insights: reliability, failure context, cost, and service forecast.
- Batteries: pack counts and health context.
- Maintenance: bound hours and service decisions.
- Squadrons: roster activity and shared fleet statistics.
Simulator sessions do not consume battery packs, and real-world sessions do not use a simulator platform. Keeping those fields separate keeps the numbers accurate.