← Back to Start
Getting startedDashboardUAV ManagementFlight LogsLog AnalyzerFlight ReportsImport & ExportUser Settings
Adding Flights

Adding Flights

Click the Add Flight button at the top of the Flight Logs page to open the flight record form. Fill in the mission details and click Save Flight to add it to your archive. The form validates required fields on the client side and provides clear error messages if anything is incomplete.

Required fields

The following fields must be filled to successfully save a flight:

  • Departure Place — The location where the flight started (e.g., "Meadow", "Airport A")
  • Date — The date the flight occurred
  • Departure Time — The takeoff time (HH:MM format)
  • Landing Time — The landing time (HH:MM format)
  • Landing Place — The location where the flight ended
  • UAV — The aircraft used for this flight (only active UAVs are available)

Form fields (all fields)

Essential Information

  • Departure Place (required) — Mission start location
  • Date (required) — Date picker; use consistent naming for easier filtering
  • Departure Time (required) — Takeoff time (HH:MM)
  • Landing Time (required) — Landing time (HH:MM)
  • Landing Place (required) — Mission end location

Duration

  • Flight Duration — Auto-calculated from departure and landing times. This field is read-only and updates automatically when you set the two time inputs. Overnight flights (landing time before departure time) are handled correctly.

Auto-calculation: The system calculates duration in minutes by computing the time difference. If your landing time is on the next day (e.g., departure 22:00, landing 02:00), the calculation accounts for midnight correctly.

Flight Operations

  • Takeoffs — Number of takeoff cycles (default: 1, minimum: 0)
  • Landings — Number of landing cycles (default: 1, minimum: 0)
  • Light Conditions — Choose "Day" or "Night" (default: Day)
  • OPS Conditions — Choose "VLOS" (Visual Line of Sight) or "BLOS" (Beyond Visual Line of Sight) (default: VLOS)
  • Pilot Type — Role during the flight: "PIC" (Pilot in Command), "Dual" (two pilots), or "Instruction" (training) (default: PIC)

Aircraft and Notes

  • UAV (required) — Select the aircraft that flew this mission. Only active UAVs appear in this dropdown. If you see a message saying "Inactive UAVs exist that match," those aircraft exist in your system but are marked as inactive and cannot be selected here. You must reactivate them in UAV Management if you need to use them.
  • Comments — Optional notes about the flight (equipment issues, weather, mission objectives, observations)

Validation and error handling

When you submit the form, all required fields are checked client-side:

  • If validation fails, inline red error messages appear below each missing or invalid field.
  • A yellow summary box lists all errors together for quick review.
  • Fix the errors and click Save Flight again.

Tips

  • Consistent location names: Use the same departure and landing place names across all flights for easier filtering and searching (e.g., always "Main Field" instead of "Main Field", "Field A", "The Field").
  • Time format: Times are in 24-hour format. Ensure both times are on the same date or the next day — the system handles overnight flights.
  • Pilot types: Choose the correct pilot type for regulatory compliance. "PIC" means you were the pilot in command, "Dual" indicates two pilots, and "Instruction" indicates a training scenario.
  • Current UAVs only: When adding a flight, only active UAVs are available. If the aircraft you want is inactive, activate it in UAV Management first.
  • Telemetry import: After saving the flight, you can open its detail page and import telemetry data from a CSV file to visualize the flight path and instrument data.

Next: Learn about Flight Details.

See Best Practices for guidelines on naming and organizing your flight records.