Drone/UAV Flight Log & Maintenance Tracker

The Drone/UAV Flight Log & Maintenance Tracker keeps one record for every unmanned aircraft in your fleet: flight hours, battery cycles, components, inspections and open maintenance. It counts each aircraft and battery toward the intervals your maintenance program sets and shows what is coming due before it is overdue. Grounding and return to service stay with qualified people, and every log entry, sign-off and release is kept for inspectors and auditors.

The problem it solves

Many unmanned aircraft units still log flights on paper, in a ground control station's export or in a shared spreadsheet, and track maintenance somewhere else. Battery cycles are counted by hand, components move between airframes without the history following them, and nobody has a single view of which aircraft are mission capable today. When an aircraft fails or an inspector asks for its history, the record has to be rebuilt from several sources.

Who it’s for

• Unmanned aircraft units in the armed services and defense agencies
• UAS maintainers and maintenance supervisors
• Operations officers and commanders who need a current readiness picture
• Fleet and program managers who plan spares, batteries and replacements
• Safety officers, inspectors and auditors who review aircraft histories

1. LogEach flight is recorded against the aircraft, the batteries and the operator, either entered after landing or imported from the ground control station's flight log.
2. TrackEvery aircraft, battery and serialized component carries its own counters, and the tracker compares them with the intervals in your maintenance program.
3. MaintainWrite-ups and scheduled tasks become work orders. Maintainers record the work and parts, and a qualified inspector checks it before the aircraft is released.
4. ReportReadiness, utilization and maintenance history are available to commanders, program managers and inspectors from the same records the maintainers use.

Flight logbook

One log per sortie with the aircraft, operator, batteries, payload, times, landings and remarks, signed by the operator.

Ground control station import

Flight log files exported from supported ground control stations are imported and matched to the sortie, so times are not typed twice.

Battery cycle tracking

Each battery is serialized, with its cycles, recorded health checks and the aircraft it flew on, and is flagged when it reaches your retirement criteria.

Maintenance intervals

Inspections and component replacements scheduled by flight hours, cycles, calendar time or flights, following your maintenance program.

Component history

Motors, propellers, payloads and other serialized parts keep their hours and history when they move between airframes.

Readiness board

Each aircraft shown as ready, limited or down, with the open write-up, overdue item or missing part behind its status.

Work orders and sign-off

Write-ups become work orders with tasks, parts and labor, and a separate inspector signs off before return to service.

Operator currency

Each operator's recent flights and recorded qualifications shown against the currency requirements your unit sets.

Configuration and modification records

Software and firmware versions, approved modifications and payload configurations recorded for each aircraft.

Grounding and fleet holds

Ground a single aircraft or every aircraft with a given component or battery lot, and track which have been inspected and released.

Offline field use

Flight logs and work orders can be recorded on a device without a connection and synchronized when one is available, with conflicts shown for review.

Inspection-ready audit trail

Who logged, changed, signed or released what and when, for every aircraft, kept for inspectors and mishap investigations.

Operator

Logs flights, completes checklists and writes up discrepancies on the aircraft they fly

Maintainer

Works maintenance tasks, records parts and component swaps, and closes work orders for inspection

Inspector

Checks completed maintenance and signs it off; cannot inspect their own work

Operations officer

Sees readiness across the unit, grounds aircraft and authorizes return to service

Fleet manager

Maintains the maintenance program, intervals and fleet records, and plans spares and replacements

Auditor or inspector general (read-only)

Views aircraft histories, logs, work orders and the audit trail, with no ability to change them

Ground control station logs

Flight log files exported from the ground control stations you use are imported and matched to sorties. Supported formats are confirmed during implementation.

Supply and parts systems

Parts requests and consumption shared with your supply system by scheduled file or API, so maintenance and supply see the same demand.

Maintenance information systems

Where your service requires records in an official maintenance system, the tracker exports work orders and aircraft histories in an agreed format for your staff to load.

Training records

Operator qualifications from your training system, so currency is checked against what is recorded there.

Single sign-on

Staff sign in through your identity provider (SAML or OpenID Connect), including CAC or PIV where your provider supports it.

Work API

Fleet, readiness and maintenance data available to your data platform and reporting tools through the Moraph Work API.

Munitions Accountability & Audit Ledger

For units using both, payload and expendable records can be linked to the sortie that carried them.

Records kept in the United States

Hosted in the United States region only, for government clients.

Cleared support lane

Support tickets from federal and defense clients are handled only by US citizens with active security clearances.

Single sign-on and role-based access

Staff sign in through your identity provider, and what each person can see and do follows their role and unit.

Encryption under controlled keys

Client data is encrypted with keys Moraph staff cannot access without explicit, time-bound authorization.

Complete audit trail

Every log entry, sign-off, release, change and export is recorded with the person and time, and cannot be edited.

Controls mapped for your authorization

Moraph is SOC 2 Type II and ISO/IEC 27001 audited, maps the tracker's controls to NIST SP 800-171 and 800-53, and supports your own authorization process; it does not hold a DoD authorization of its own.

Moraph cloud, United States

Hosted and operated by Moraph in the United States region for unclassified data, with controls mapped to support your own authorization.

Dedicated environment

A single-tenant environment for organizations whose policies require isolation, scoped in the proposal.

Your environment

Installed in an environment you operate, including disconnected networks, where your authorizing official approves it and it runs under your authority.

With a managed service

Optionally run alongside a Moraph managed service for administration and integration support, delivered by US citizens with active clearances.

Fleet record setup

Aircraft, batteries and serialized components are loaded from your existing records, with current hours and cycles agreed with your maintainers.

Maintenance program

Your inspection intervals, task lists and battery retirement criteria are configured from your maintenance program and the manufacturer's data you hold, and approved by your airworthiness lead.

Flight log import

We confirm which ground control station log formats you use and test imports with sample files from your aircraft.

Workflow and roles

Checklists, write-up categories, sign-off steps, return-to-service authority and roles are configured to match your procedures.

Field devices

Devices for flight line and field use are registered, and offline synchronization tested in the conditions your units work in.

Training and go-live

Operators, maintainers, inspectors and officers are trained on their own tasks, and open work orders are moved across or finished in the old system by agreement.

• The tracker does not make airworthiness decisions. Grounding, inspection sign-off and return to service are made by qualified people at your organization.
• It does not replace the manufacturer's maintenance data or your service's maintenance program; it applies the intervals and tasks you configure from them.
• Counters are only as accurate as the flights and maintenance recorded. Flights that are not logged or imported are not counted.
• It does not control or connect to aircraft in flight, and is not a flight planning, airspace authorization or mission planning system.
• Ground control station imports depend on the formats your equipment exports; formats are confirmed during implementation.
• It is designed for unclassified records. Use on classified networks is possible only in an environment you operate and authorize.
• It is not your service's official maintenance information system of record unless your service approves it as one; where an official system is required, records are exported to it.
• Moraph does not hold a DoD authorization for the tracker; your authorizing official decides whether and where it may be used.

• Load a sample of your fleet and compare the tracker's due list with your current records
• Import ground control station logs from your own aircraft and check the matched times
• Follow a write-up from flight log to inspected repair and return to service
• Move a component between airframes and confirm its history follows it
• Test offline logging in the conditions your units work in
• Confirm separation of duties: who can sign off maintenance and who can release an aircraft