Drone maintenance records for operator compliance: what to l

Records turn maintenance work into evidence

A repaired drone may be safe to fly, but the repair alone does not prove compliance. Inspectors need records that connect the fault, the work done and the aircraft returned to service.

1. DJI Agras T100 100 L
2. DJI Agras T70P 70 L
3. XAG P150 70 L
4. DJI Agras T55 50 L
5. XAG P100 Pro 50 L
6. DJI Agras T50 40 L

Spray tank capacity (L)

Model	Value
DJI Agras T100	100 L
DJI Agras T70P	70 L
XAG P150	70 L
DJI Agras T55	50 L
XAG P100 Pro	50 L
DJI Agras T50	40 L

Sources: ag.dji.com, ag.dji.com, xa.com, ag.dji.com, xa.com, ag.dji.com

This matters most when an operator must show how safety duties were met. The FAA’s proposed BVLOS framework places record keeping beside operational authorisations, aircraft duties, security and information reporting.

That framework is proposed, so operators should not present it as a current blanket rule. It still gives a clear view of the evidence the FAA expects more complex drone operations to produce.

The same distinction matters under Part 107. FAA material says the pilot is responsible for ensuring that a drone is safe before flight. However, the supplied primary material does not establish one standard maintenance logbook for every operator.

Records are therefore both a compliance tool and a safety control. They show whether staff found a defect, assessed it, fixed it and checked the result.

For agricultural fleets, maintenance records should also fit the wider operating system. Operators setting up commercial work can use the workflow in Running a drone spraying business alongside the maintenance checklist below. Australian operators should check the local framework covered in Agricultural drone rules in Australia (CASA) rather than applying FAA material by default.

Log the fault, the work and the return to service

A useful maintenance entry should answer a simple chain of questions. What was found, what happened next, who made the decision and why was the aircraft released?

The proposed FAA BVLOS framework expressly lists mechanical issues and maintenance and alteration inspections. Those fields give operators a sound base for joining flight and maintenance records.

Record field	What it should show	Why it helps
Aircraft identity	The registration number and the operator’s matching aircraft reference	Links the work to the correct aircraft
Fault or finding	The mechanical issue, inspection finding or reported symptom	Preserves the reason for the work
Source of finding	Preflight check, post-flight report, planned inspection or in-flight event	Shows when and how the issue arose
Aircraft status	Whether the aircraft was held from use or kept in service	Records the safety decision
Work done	Repair, adjustment, inspection or alteration	Shows the response to the finding
Parts or materials	The item fitted and its source records	Supports traceability
Person responsible	The person who did, checked or approved the work	Creates accountability
Return-to-service basis	The check or evidence used before further flight	Closes the maintenance chain
Linked evidence	Images, supplier papers, test output or related flight record	Keeps supporting proof with the entry

Use consistent terms for open and closed faults. Do not let an item vanish from the system merely because a later flight was successful. The record should show the action that closed it.

A flight record should also point back to any maintenance that affected that flight. Linking these records lets an inspector follow an issue from discovery to the next operation.

For spray aircraft, operational records may sit beside chemical and job files. The systems are different, but they should use the same aircraft identity. The guide to How agricultural drone spraying systems work explains why the spray system is part of the working aircraft rather than a separate office concern.

Parts need a traceable path into the aircraft

A maintenance log should not stop at “part replaced”. It should preserve enough evidence to identify what entered the fleet and where it came from.

FAA Advisory Circular AC 20-154A provides a useful model for this task. It covers receiving inspection systems for aircraft parts and materials. Its aim is to prevent unairworthy items from entering stock and to establish enough traceability to assess their accepted status.

The circular is guidance. It is not mandatory, does not create a regulation and presents one possible method rather than the only method. Operators should not claim that it imposes its full system on every agricultural drone.

Its core record design is still useful. AC 20-154A recommends written processes for buying, receiving and inspecting parts and materials.

A practical receiving record can capture:

• the aircraft or stock item linked to the part;
• the supplier and the papers received with it;
• the inspection carried out on receipt;
• any mismatch, damage or missing evidence;
• the person who accepted or rejected it;
• where the item went after acceptance; and
• the maintenance entry created when it was fitted.

Keep rejected items visible in the system. Otherwise, an operator may retain proof for accepted stock while losing the history of a suspect item.

AC 43-9C should be handled with care. The FAA page describes it as guidance on maintenance record-making and record-keeping under parts 43 and 91, but the circular is cancelled. It should not be quoted as current authority for a drone maintenance retention period.

The supplied rules do not prove one retention period

There is no authoritative, universal maintenance-record retention period in the supplied primary material. An operator should not turn a blog’s summary into a legal rule.

The research includes third-party claims that flight logs should be kept for at least 24 months and maintenance records for the life of the aircraft. Another third-party source gives a different flight-log period for UK operators. The supplied excerpts do not include the underlying regulatory text needed to verify those claims.

Retention statement in the research	Source type	Safe publishing treatment
Flight logs kept for at least 24 months	Third-party summary	Do not present as the universal FAA rule
Maintenance records kept for the life of the aircraft	Third-party summary	Treat as a policy claim until checked against primary law
A different minimum period for UK flight logs	Third-party summary	Verify against the applicable CAA text
Maintenance retention under FAA, EASA or CAA rules	Not established by the supplied primary excerpts	Check the exact rule, authorisation and operating category

AC 20-154A deals with receiving inspection and traceability, not a general drone maintenance retention period.

Set the retention rule only after identifying the legal basis for the operation. Check the governing regulation, permit, certificate, waiver, operational authorisation and any terms imposed by the authority. Contract and insurer terms may also need review, but none are supplied here.

Until that check is complete, preserve the records rather than deleting them on an assumed deadline. Mark the retention setting as awaiting legal confirmation. That is more defensible than attaching an unsupported period to the whole fleet.

Inspectors follow links, not tidy-looking folders

The supplied third-party research says inspectors carefully examine maintenance records during audits to check compliance and due care. Another summary says documentation is often the first material requested during an inspection or investigation.

These are not primary statements of a set inspection procedure. They do, however, point to the practical test for any record system: can the operator retrieve a complete chain without rebuilding it from memory?

An inspector reviewing maintenance evidence may need to connect several types of record:

Starting point	Records that should be easy to retrieve
A flight	Aircraft identity, assigned staff, open defects and relevant maintenance
A mechanical issue	Original report, safety decision, work done and closure
A fitted part	Supplier evidence, receiving check and installation record
An alteration	Description, inspection evidence and operating limits affected
A staff member	Assigned role and relevant training record
A BVLOS proposal	Authorised area, hazards, communications coverage and lost-link procedure

The proposed BVLOS framework makes those links especially important. Operators would identify operating boundaries, daily activity, take-off, landing and loading areas. They would also ensure communications coverage, prepare for a lost link and identify hazards.

Maintenance evidence should map to those controls where relevant. A communications fault, for example, should link to the lost-link procedure and the affected operation. A defect tied to an operating limit should point to the manual or approval that sets that limit.

Inspectors should not need a staff member’s private knowledge to decode the files. Use stable names, searchable aircraft references and clear status labels. Store supporting documents with the entry or provide a working link inside the record system.

A short audit drill exposes weak records

Audit readiness is a retrieval task. Test it with a sample aircraft and work backwards from a flight to the parts and checks that supported it.

Start with the flight record. Then check whether the aircraft had any unresolved mechanical issue at that point.

Next, select a closed fault. Retrieve the original report, the work entry, any part evidence, the person responsible and the basis for release. If one item cannot be found, the record chain is incomplete even if the aircraft flew without a problem.

Use the same drill for receiving inspection:

• choose an installed item;
• find its supplier evidence;
• find the receiving decision;
• link it to the maintenance entry;
• confirm which aircraft received it; and
• check that rejected or doubtful stock stayed out of use.

Review access as well as content. EASA’s privacy-by-design guidance says drone operators may be data controllers when their work processes personal data. Maintenance systems can also hold staff names and linked flight activity. Access controls should therefore protect the record without making authorised inspection impossible.

Finally, keep the operations manual aligned with the logs. A log that describes a process absent from the manual, or a manual step never shown in the logs, creates an obvious gap.

Manufacturer schedules need their own source

The supplied product data proves aircraft specifications, not maintenance instructions. It does not provide model-specific service intervals, replacement limits or required maintenance-log fields.

Do not derive a maintenance interval from payload, tank size, battery charge time or any other product specification. A specification describes the aircraft or system. It does not prove when a component must be inspected or replaced.

Before adding a model-specific field, obtain the relevant manufacturer maintenance document. Record its revision with the procedure used. If the manufacturer changes the instruction, keep enough history to show which procedure applied when the work was done.

The final checklist is simple: identify the aircraft, record the fault, trace the parts, name the responsible person and document the release. Then test whether another person can retrieve that chain. That is the point at which a maintenance log becomes compliance evidence.