AAIB Record-only UAS investigations reviewed: February - March 2026
Published 14 May 2026
This section provides details of accidents and incidents which were not subject to a Field or full Correspondence Investigation. They are wholly, or largely, based on information provided by the aircraft commander at the time of reporting and in some cases additional information from other sources. The accuracy of the information provided cannot be assured.
| Event date | Aircraft Type | Location Name | Record Only Occurrence Text |
|---|---|---|---|
| 5 Feb 2026 | DJI M30T | Cwmllynfell, Neath Port Talbot | The UA struck overhead electrical cables immediately after takeoff and was destroyed. The flight was being conducted at night for operational requirements, and the cables had not been observed. The remote pilot was unaware that the mapping software highlighted the presence of cables if the appropriate mapping layer was selected. They said that this learning had been shared with the operator’s training team. |
| 3 Mar 2026 | MA Tiger Trainer OBL | Dewsbury, Yorkshire | The MA was being operated at a model flying club site located on the edge of an urban area when it experienced a failure of the electronic speed controller, becoming unresponsive to control inputs. This resulted in a flyaway event and the MA subsequently struck a pallet of goods in the grounds of a business unit, adjacent to the flying club site. |
| 18 Mar 2026 | Apellix B1 | City of Westminster, London | The UA was being used for window cleaning. Five minutes into the flight, the remote pilot noticed a warning light indicating a problem with the GPS lock. He stopped the cleaning operation and attempted to land the aircraft but it did not respond to the controller inputs. It collided with the building and fell to the ground within the safety cordon. |