UK UAS RECORDS
UK UAS maintenance and configuration-control records
Operational claims remain credible only when the UAS configuration and technical condition used in flight match the evidence in the UK dossier.
Identify each controlled configuration
Record aircraft, payload, C2 equipment, software, firmware, safety functions and permitted combinations using unique identifiers and versions.
Manage maintenance and defects
Define inspections, scheduled tasks, defect reporting, grounding criteria, repair evidence and authorised release back to operation.
Assess changes before flight
Review firmware, component, payload and procedural changes against the ConOps, risk assessment and authorisation conditions before operational release.
Frequently asked questions
Are manufacturer records enough?
They are important inputs, but the operator also needs records showing how its own aircraft is configured, inspected, maintained and released.
Must every firmware update trigger a new application?
Not automatically, but each change must be assessed for impact on safety claims, procedures and authorisation conditions.