This Safety Notice contains information that is for guidance and/or awareness.
Applicability:
UAS Operators: All UAS Operators
Remote Pilots: All Remote Pilots
1 Introduction
1.1 The purpose of this safety notice is to highlight the responsibility of a UAS (Unmanned Aircraft Systems) operator and remote pilot to ensure that software and firmware updates are carried out to UAS when required by the manufacturer or by published maintenance procedures adopted and accepted by the operator.
2. Scope
2.1 The CAA are aware of loss-of-control events in which improper handling of software and/or firmware updates may have been a contributing factor to the event.
2.2 This Safety Notice recommends to UAS operators and remote pilots to flight test the unmanned aircraft after any update or modification.
3. Regulatory Requirements
3.1 Specific Category
3.1.1 Operators in the Specific Category are reminded of their responsibilities under UAS.SPEC.050 (1)(h)(i), “as a minimum, define maintenance instructions and employ adequately trained and *qualified maintenance staff.” Remote pilots in the Specific Category are reminded of their responsibilities under UAS.SPEC.060 (1)(c) - Responsibilities of the remote pilot. “be familiar with manufacturer’s instructions provided by the manufacturer of the UAS.”
3.2 Open Category
3.2.1 Remote pilots in the Open Category are reminded of their responsibilities under UAS.OPEN.060(2)(e) - Responsibilities of the remote pilot. “operate the UAS in accordance with manufacturer’s instructions provided by the manufacturer, including any applicable limitations.”
4. Queries
4.1 Any queries or requests for further guidance as a result of this communication should be addressed to UAVenquiries@caa.co.uk
5. Cancellation
5.1 This Safety Notice will remain in force until further notice.
I leave it a week or so after a release to make sure the new firmware doesnt cause anyone else any issues, then Il update with a bit of confidence. That makes me a lawbreaker in the eyes of the CAA
In case people (well Operational Authorisation holders specifically) find it helpful, this is what I’ve just updated our Operations Manual software section to:
General
• All new software and firmware must be thoroughly researched and assessed before installation.
• Updates are only installed if:
required by the manufacturer,
mandated by published maintenance procedures, or
deemed necessary for continued safe operation.
• Updates will be evaluated for:
Relevance to operations,
Reasons for release,
Known issues reported by the manufacturer or user communities (e.g., multi-rotor and UAS forums).
• The validity of each update must be confirmed before installation. If software or firmware is issued by the aircraft manufacturer, its suitability will be monitored on forums and social media; however, manufacturer instructions must still be followed where required.
Regulatory Compliance
• All operators and remote pilots must comply with the following:
UAS.SPEC.050(1)(h)(i) – Operators must define maintenance instructions and ensure qualified maintenance personnel are used.
UAS.SPEC.060(1)(c) – Remote pilots must be familiar with manufacturer instructions and ensure that software update procedures are followed.
• Only qualified personnel or appointed third-party providers may perform software or firmware updates.
Pre-Installation and Testing
• Record software version numbers and new functionality in the Aircraft Maintenance Logbook.
• Document any operational impact in the Operations Manual (OM)
• After each firmware or software update, a flight test is mandatory before the aircraft is used operationally.
• Testing must be conducted in a clear flight area by a qualified pilot.
Post-Update Performance Monitoring
• Any performance improvements or unexpected abnormalities must be recorded in both:
The Aircraft Operating Hours Log, and
The Aircraft Maintenance Log.
• If the pilot deems the update safe, this determination should be noted in the Aircraft Maintenance Logbook.
• If performance issues arise:
Attempt to restore the previous firmware version (if possible).
Conduct additional test flights to confirm safe operation.
• If firmware/software problems persist, immediately ground the aircraft until the issue is resolved or the manufacturer provides guidance.
Pilot Awareness and Training
• All pilots must be informed of any firmware or software updates.
• Each pilot must have the opportunity to test-fly the aircraft with the new configuration prior to operational flights.
Fortunately the CAA notice is only aimed at GVC holders and commercial UAS operators.
My amateur "ops manual " is carried in my head and the software recommendation is “don’t upgrade unless absolutely necessary, ;et some other poor sod take the hit of being an early adopter and borking his aircraft.”
Exactly what I was thinking earlier, although I used to be the ‘ Early Adopter ‘
Not anymore I’ll leave that to someone else, also ‘ If It Ain’t Broke Don’t Try And Fix It ‘ is what the CAA should be saying
Ensure software and firmware are up to date, hmmmmm. First thing I do when there’s an update, is look on YouTube/ forums etc and see what others who have updated say. Yep, perhaps takes a few hours to do this, but better to be safe than sorry. As others have already said “ If it ain’t broke, don’t try to fix it.”
Having said that, I do wish DJI would tell us what their updates are actually “fixing”, instead of simply saying “known issues”.
The lead paragraph of the notice lead me to believe that the intended audience is commercial operators:
This Safety Notice contains information that is for guidance and/or awareness.
Recipients are asked to ensure that this Information Notice is copied to all members of their staff who may have an interest in the information (including any ‘in-house’ or contracted maintenance
organisations and relevant outside contractors).
All firmware for all drones. It is basically saying that it is the reponsibility of the operator to ensure that their aircraft is/are updated with the respective manufacturers latest firmware.
