Drone/UAV Flight Log & Maintenance Tracker

Principal workflows

• Log: Each 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.
• Track: Every aircraft, battery and serialized component carries its own counters, and the tracker compares them with the intervals in your maintenance program.
• Maintain: Write-ups and scheduled tasks become work orders. Maintainers record the work and parts, and a qualified inspector checks it before the aircraft is released.
• Report: Readiness, utilization and maintenance history are available to commanders, program managers and inspectors from the same records the maintainers use.

Who uses it

• 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

Reporting

• Fleet readiness with the reason behind each status
• Maintenance coming due and overdue
• Battery cycles and retirement
• Utilization by aircraft and unit
• Component failures and removals
• Complete aircraft histories for inspections

Features

• 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.

Integrations

• 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.

Deployment

• 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.

Security and privacy

• 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.

Limitations

• 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.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/drone-uav-flight-log-and-maintenance-tracker. Purchasing routes and company information: www.moraph.com/how-to-buy.