Once flights are in the system, Flights is where you review them: one row per flight, a detail page with the path on a map, and a Missions view that rolls related flights into a single operation. This article covers finding a record, reading it, editing it, and the aircraft-level history built from those records.
Any signed-in pilot can view flights, but unless you are a global admin you see only your own unit's. Deleting a flight, changing its unit, and bulk mission assignment need supervisor or above.
Before you start. Flights only appear here after they are imported. If the list is empty, start with importing flight logs.
Finding a flight in the flights list
Open Flights from the sidebar. Charts sit at the top — flights and missions over time, plus a field/DFR split on DFR-enabled instances — and the table below has a Flights and a Missions tab.
The Flights tab shows one row per record: Date & Time, Unit, Address, Imported From, rPIC, Mission, Title, and a Checklist column that turns to a green check once a post-flight checklist is done. Narrow the list three ways:
- The All units dropdown in the toolbar filters to a single unit.
- The search box matches title, address, rPIC, unit, and mission name at once.
- Date & Time, Unit, rPIC, Mission, and Checklist are sortable — click the header.
The table pages 15 rows at a time. The eye icon on a row opens the flight; the trash icon deletes it.
What the flight detail page shows
The heading is the flight's title — click the pencil to set one, typically a case or incident number. Under it sit the date and time, the unit, the source the record came from, and a link that names the flight's mission or offers to add it to one. Export PDF builds and downloads a flight report. The body is a stack of cards:
| Card | What it holds |
|---|---|
| Flight Details | Address, aircraft, rPIC, unit, max altitude, max distance, max speed, distance traveled, air duration |
| Participants | Everyone on the flight and their role |
| Batteries | Takeoff and landing charge per battery |
| Flight Map | Takeoff point and flight path |
| Telemetry | Altitude, speed, and battery over the flight, when sample data exists |
| Weather & Airspace | Conditions at the flight's time and location, plus any TFRs it touched |
| Hazards | Hazard reports filed against this flight |
When the aircraft or a battery matches an item in Equipment, its name links straight to that record. Checklist blocks appear here too — at the top while one is outstanding, at the bottom once done. See post-flight checklists.
Working with the flight path map
The Flight Map card draws the takeoff point as a marker and the path as an orange track. The path comes from whichever source the record has: a path stored with the flight, the vendor's flight CSV, or telemetry samples captured when a standard-format log was imported. A flight with no takeoff coordinates says so instead of drawing an empty map.
Three switches sit above the map:
- Nearby TFRs — draws active temporary flight restrictions around the flight, with a badge for any within 3 miles. Click a TFR shape for its details and to zoom to it.
- UAS Facilities Map — overlays the FAA's UASFM grid for the current view.
- Satellite — swaps the basemap for imagery.
Mouse-wheel zoom is off here so the page still scrolls; use the +/− control. The chevron in the card header collapses the map, and the PDF export snapshots it fit to the full path.
For a program-wide view, Flight Map in the sidebar plots takeoff points for every flight in a date range. Pick the range, press Get Flights, and each marker opens a popup with the mission or title, crew, address, date, and a link into the record.
Crew and participant roles on a flight
The Participants card merges the participant data carried in the imported log with people added inside the app. Only the app-added rows can be edited or removed.
Press Manage participants. Supervisors and above get a picker searching pilots and managers across their units; pilots see an Add me button. The roles are:
| Role | Meaning |
|---|---|
| Pilot in Command | The remote PIC. One per flight; the flight's rPIC field tracks this person. |
| Pilot in Control | Flew the aircraft under the PIC. |
| Co-Pilot | Second pilot on the crew. |
| Support | General crew support. |
| Visual Observer | Kept eyes on the aircraft. |
| Instructor | Ran training on the flight. |
| Flight Supervisor | Supervised the operation. |
| Completed Checklist | Added automatically on checklist submission. |
Pilot in Command and Pilot in Control mean the person actually flew, so those are the roles that pull a flight into that pilot's currency and stats — which is why adding a second pilot after the fact matters. Pilots can remove themselves; supervisors and above can remove or re-role anyone but the checklist row.
A flight takes exactly one Pilot in Command: you cannot leave manage mode with two PIC rows, and setting the PIC rewrites the flight's rPIC so the two never disagree.
Grouping flights into missions
A mission is a named group of flights belonging to one operation — several aircraft on one incident, or one aircraft relaunched several times. It matters for two reasons: the charts count a mission as one event rather than several flights, and one post-flight checklist can cover the whole mission instead of each leg.
To group flights, tick them in the Flights tab and press Assign to mission. Pick an existing mission or type a new name; names match case-insensitively, so reusing a name reuses that mission instead of duplicating it. Remove from mission appears when a selected flight is already grouped. On a single flight, the mission link under the heading does the same job.
The Missions tab shows one row per mission with its flight count, date span, units, pilots, and checklist state. A mission missing a checklist shows a Fill checklist button with the number of flights still uncovered; one submission covers every flight without its own. Row actions drill into the mission's flights, rename it across every flight at once, or delete it — which ungroups the flights but keeps them.
A flight belongs to one mission at a time. Assigning a flight already in another mission is refused, and the error names that mission. Remove it from there first — no silent moves.
Select-all covers every page. The header checkbox selects every flight matching the current filter, not just the 15 rows on screen. The assign dialog warns you above 15 selected — cancel and clear if that was not what you meant.
Aircraft history and airframe hours
Flights are matched to an aircraft by drone ID or serial number, which is what makes aircraft-level history possible. Open Equipment, choose an aircraft, and its usage panel summarizes total flights, flight hours, pilots flown, and when it last flew — with a flight-activity chart, a usage-by-rPIC breakdown, and a searchable table of every flight on that airframe.
Airframe hours are computed from the logs by summing air duration across matching flights. Nobody types them. Maintenance entries capture hours as of their service date the same way, so a back-dated entry records the hours the aircraft actually had that day. If an aircraft has no serial number on its record, the panel says so and no flights match — add the serial to turn usage tracking on.
Editing and deleting flight records
Edits are deliberately narrow, because a flight log is evidence:
| Change | Who can make it | Effect |
|---|---|---|
| Title | Anyone with access to the flight | Marks the title hand-set so later enrichment never overwrites it |
| Mission | Anyone with access to the flight | Groups or ungroups that one flight |
| Unit | Supervisor and above | Changes who can see the flight; must name a real unit |
| Bulk mission assign, rename, delete | Supervisor and above | Own unit only, unless you are a global admin |
| Delete flight | Supervisor and above | Removes the record permanently |
Unit is the visibility scope, which is why changing it is restricted and why non-global users can only move a flight to their own unit. Viewing, editing, exporting, and deleting a flight all write to the audit log.
Deleting a flight cannot be undone. Everything derived from the record — airframe hours, pilot currency, mission counts — recalculates without it. Check your retention obligations first in the UAS recordkeeping and Remote ID audits guide.
Reporting a hazard from a flight
Where hazard reporting is enabled, the bottom of the detail page carries a Hazards card. Press Report hazard, give it a short title, pick a category (airspace, equipment, weather, crew, procedure, public, wildlife, or other) and a severity from low to critical, and add details. Filing notifies the responsible managers.
The card then lists the hazards filed against that flight with severity and status. Reports move from open to assigned to closed: a manager is assigned, works the hazard with a running work log, and closes it with a disposition — corrected, mitigated, risk accepted, no action needed, or referred out. Critical hazards go to agency level immediately; the rest stay with the unit unless escalated.
Frequently asked questions
Why does a flight show no path on the map?
The map draws whatever track the record carries. Some imports bring a full track, some bring only a takeoff point, and some bring neither. If the card says there is no location data, the record has no takeoff coordinates. A marker with no line means the source log had no per-point telemetry to import.
Can a flight belong to more than one mission?
No. A flight belongs to exactly one mission at a time, and an assignment that would move it out of the mission it is already in is refused. Remove it from that mission first, then assign it to the new one. This keeps mission counts honest and stops one flight being covered by two mission checklists.
Who can delete a flight record?
Supervisors and above, and only for flights in their own unit unless they are global admins. Deletion is permanent and removes the flight from every derived number, including airframe hours and pilot currency. The deletion is written to the audit log with the flight ID and title, so the removal stays traceable.
How do I make a flight count toward a pilot's currency?
Add them to the flight as a participant under a flying role. Pilot in Command and Pilot in Control are the two that mean the person actually flew, so those are what currency counts. Open the flight and press Manage participants. Pilots can add themselves with Add me; supervisors can add anyone.
Where do airframe hours come from?
Straight from the flight logs. The app matches flights to an aircraft by drone ID or serial number and sums their air duration; there is no field to type hours into. If an aircraft's hours look low, check that its equipment record carries the serial the flight logs use.
Next steps
If flights are missing or landing in the wrong unit, see importing flight logs. To close out the records you just reviewed, see post-flight checklists. To get this data out — for a records request, a monthly summary, or an audit — see reports and exports.