A connected history of your drone fleet
See the aircraft and identified batteries behind your imported flight records. Flymetry links operational history to registered equipment, giving your team a clearer place to start a review.
Illustrative example · serials truncated
Connect flights by aircraft serial number
An aircraft name is convenient, but a serial number gives the matching process a specific identity. Flymetry matches the UAV serial in an imported record to the system register. Unknown aircraft can be presented for administrator review before they become registered systems.
Keep pilots, aircraft and components in context
Administrators register systems and assign pilots. Controller and battery observations can be checked against the register. A mismatch is a reason to review the record, not automatic proof of a fault or an unauthorised flight.
Follow a battery across aircraft
Where a physical battery is identified, its observed history can remain connected when it appears on more than one system. Unresolved battery indices stay separate until the identity is supported; not every multi-battery record identifies each physical pack.
Know the boundary of the record
Imported flight history is not a complete maintenance ledger. Current-register matching does not by itself establish who owned or used a component at every point in the past. Maintenance planning and historical component changes are not included in the current MVP.
Explore the relationships
Open the fleet demo, select an aircraft and follow its recorded flights and batteries. All demo equipment and activity are synthetic.