Systems with identified issues to firmware or software should be grounded until the problem can be
rectified.
8.1. Software and Firmware Update Policy
All new software and firmware will be thoroughly assessed before installation. Particular attention
should be focused on relevance to operations, reason for release and any known issues. Multi-rotor and
UAS forums should be examined for any reported issues with the release and only when the validity of
the upgrade has been confirmed should the upgrade be considered.
In all circumstances the upgrade should only be performed by qualified Leicester Drones personnel or
appointed service providers. All upgrade information such as version numbers and new functions must be
recorded in the Aircraft Maintenance Logbook. All Leicester Drones pilots must be made aware that the
firmware or software has been upgraded before any flight is undertaken.
Any upgraded system must then have all functions thoroughly tested with a minimum of fifteen minutes
flight time by a qualified Leicester Drones pilot recording any abnormalities in the Aircraft Operating Hours
Logbook. If the Pilot-In-Command deems the aircraft safe then the Accountable Manager, Christian Smith
should sign the Aircraft Operating Hours Logbook as fit for operational use. If any doubts exist as to the new
upgrade then the aircraft should be downgraded to the previous firmware and the flight test procedure
repeated.
Systems with identified issues to firmware or software should be grounded until the problem can be
rectified.
9. Supervision of Remotely Piloted Aircraft System (RPAS)
When in-flight the Leicester Drones Pilot-In-Command on the day is responsible for supervising the
operation of the Leicester Drones SUAS.
10. Incident Investigation and Mandatory Occurrence Reporting
Any Incidents or Occurrences will be dealt with by Leicester Drones as follows:-
10.1. Incident Handling
In the event of any Incident, the severity must be assessed. The following lists should help to identify
Minor and Major Incidents:-
MINOR INCIDENTS
Any unusual or unexpected flight behaviour from the aircraft which does not result in damage or loss
Any failure of any aircraft system which does not result in damage or loss
MAJOR INCIDENTS
Any unusual or unexpected flight behaviour from the aircraft which results in damage or loss
Any significant damage to the aircraft caused by an aircraft system failure
Any significant danger or damage to persons, possessions or property during Flight Operations
Any public encroachments or aircraft incursions which required preventative measures to avoid
10.2. Incident Logging
All MINOR incidents should be logged in the Aircraft Operating Hours Logbook. Upon noting a minor
incident the logbook should be checked for similar occurrences. If a minor incident occurs three times