Drone Record Keeping Requirements in the UK: Flight Logs, Maintenance and Compliance Records

Why Record Keeping Matters for Drone Operators

Proper record keeping is not merely a regulatory box-ticking exercise. For commercial drone operators in the UK, well-maintained records serve multiple critical functions: they demonstrate compliance during CAA audits, provide evidence in the event of insurance claims, support Operational Authorisation renewals and protect you in the event of an incident investigation. Poor record keeping is one of the most common findings in CAA compliance reviews of drone operators.

Flight Logs: The Core Record

Every commercial drone flight should be recorded in a flight log. While ANO 2016 does not prescribe a specific format for flight logs, CAP 722 provides guidance on what information should be captured. A comprehensive flight log entry should include:

• Date and time: Start and end time of the operation (UTC or local time with timezone noted)
• Location: Grid reference or GPS coordinates of the take-off point, plus a description of the operating area
• Aircraft details: Drone make, model, serial number and registration (Operator ID)
• Remote pilot: Name and Flyer ID number of the pilot in command
• Type of operation: Category (Open/Specific), purpose of flight and any applicable Operational Authorisation reference
• Weather conditions: Wind speed and direction, visibility, cloud base, temperature and precipitation at the time of operation
• Flight duration: Total airborne time, number of flights conducted during the session
• Battery information: Battery serial numbers used, charge levels at take-off and landing, number of charge cycles
• Airspace status: Confirmation of airspace checks, any NOTAMs in effect and permissions obtained (such as Drone Assist app checks or ATC clearances)
• Risk assessment reference: Reference to the site-specific risk assessment conducted before the operation
• Incidents or observations: Any unusual events, near-misses, equipment issues or safety observations

Equipment and Maintenance Records

Maintaining accurate records of your drone fleet and its maintenance history is essential for both safety and compliance. Your equipment records should cover:

Aircraft Records

• Drone make, model, serial number and class marking (if applicable)
• Date of purchase and total flight hours accumulated
• Firmware version history and update dates
• Modifications or repairs carried out, including parts replaced
• Pre-flight and post-flight inspection checklists (completed for each operation)

Battery Management Records

Lithium polymer batteries are both the power source and one of the greatest risk factors in drone operations. Maintain detailed battery logs including:

• Battery serial number, purchase date and manufacturer
• Total charge cycle count
• Internal resistance readings (if measurable)
• Any instances of swelling, damage or abnormal behaviour
• Storage conditions and voltage when stored
• Retirement date and reason for disposal

Payload and Sensor Records

If your operations involve specialist payloads such as thermal cameras, LiDAR sensors or multispectral imaging equipment, maintain calibration records and service histories for each item.

Personnel Records

As an operator, you must keep records of all remote pilots authorised to fly under your Operator ID:

• Full name and contact details
• Flyer ID number and expiry date
• Additional qualifications (A2 CofC, GVC) with expiry dates
• Training history, including refresher training and competency assessments
• Medical fitness declarations (while not currently mandated for Open Category operations, many operators include these as part of their safety management approach)
• Flight hour totals by aircraft type

Mandatory Occurrence Reports (MORs)

The CAA requires drone operators to report certain occurrences through the Mandatory Occurrence Reporting system. You must maintain copies of all MORs filed, along with supporting documentation. Reportable occurrences include:

• Any accident resulting in serious injury or death
• Airprox events (near-misses with manned aircraft)
• Loss of control or flyaway incidents
• Damage to third-party property
• Any occurrence that endangers or could endanger the safety of the aircraft, its occupants, or any other person

MORs must be submitted to the CAA as soon as practicable after the occurrence, and no later than 72 hours. Keep records of the submission date, the CAA reference number assigned and any follow-up correspondence.

Insurance and Compliance Documentation

Maintain an organised file of all compliance-related documentation including:

• Current insurance certificates with coverage details and policy numbers
• Operator ID registration confirmation
• Operational Authorisation documents (if applicable)
• Operations Manual (current version and version history)
• Safety Management System documentation
• Risk assessment templates and completed assessments
• Standard operating procedures for each type of operation

Data Retention Periods

While UK regulations do not specify exact retention periods for most drone records, the following guidelines represent best practice:

• Flight logs: Minimum 2 years, recommended 5 years
• Maintenance records: For the lifetime of the aircraft plus 2 years after disposal
• Incident reports and MORs: Minimum 5 years
• Personnel records: For the duration of their association with your operation plus 3 years
• Insurance documentation: 6 years after policy expiry (aligned with statute of limitations for contractual claims)
• Risk assessments: Minimum 3 years or as required by your Operational Authorisation

Digital vs Paper Records

The CAA does not mandate a specific format for record keeping. Both digital and paper systems are acceptable, provided records are legible, complete, organised and available for inspection. Many operators now use digital flight logging applications that automatically capture GPS data, flight times and aircraft telemetry. If you use digital systems, ensure you maintain backups and that your data is stored securely in compliance with UK GDPR where personal data is involved.