1) Unintentional BVLOS x3 (BMFA community)

• What happened: One EDF jet lost power from a poor solder joint after a user modification; two other flights went BVLOS when sea fog or thermal lift arrived faster than forecast.
• Legal frame (UK): The Drone and Model Aircraft Code requires direct VLOS and the ability to determine orientation at all times. If you cannot do that, the flight is non-compliant.
• Practical fix: Treat post-purchase alterations as airworthiness-significant and inspect them before each flight. Use BMFA’s SWEETS pre-flight. Adopt a simple “radial scan” habit: eyes out (aircraft and airspace) then quick glance down (controller or map) then eyes out again.

2) Nottingham Carnival injury (Mini 2)

• What happened: A minor pressed “land” while the supervising adult was distracted; the drone struck another child who was sitting on someone’s shoulders. Police confiscated the aircraft. No Operator ID was displayed and it was flown over a crowd.
• Legal frame (UK): Never fly over crowds or assemblies of people. Label the aircraft with a visible Operator ID. Where injury occurs, expect scrutiny under general endangerment provisions.
• Practical fix: Establish a safe TOLA (take-off and landing area) away from the crowd. Use aviation-style handover phraseology: “You have control” / “I have control”. Keep controller audio alerts audible. Supervision of minors must be active and informed by the Code.

3) “My app froze” (Mavic 4 Pro + RC2; 87-waypoint mission)

• What happened: Switching to Map View mid-mission froze the Fly app. The pilot used the hardware RTH button to recover the aircraft. Possible overload from running a large waypoint mission while screen-recording.
• Legal frame: You remain responsible for safe operation even when the UI hiccups. The defensible question is whether your procedures anticipated foreseeable failures, such as hardware RTH muscle memory, function checks, and reboot-on-the-ground policies.
• Practical fix: For long waypoint jobs, test the profile without screen-recording first. Pre-brief the hardware RTH action. Use a visual observer if you will be heads-down.

4) Fatigue and stress (power-line inspection)

• What happened: The pilot became disoriented, lost VLOS about 1,700 ft from home, hit 20 percent battery, and, unaware that “land at 20 percent” was set, descended into a tree despite pressing RTH.
• Practical fix: Know and brief your low-battery action (RTH vs auto-land vs hover) in the Operations Manual. Use two-crew where terrain or workload increases disorientation risk. Remember UK requirements to maintain VLOS and orientation at all times.

5) RTH vs powerlines (mapping mission)

• What happened: An automated flight went off-nominal. On RTH, the aircraft likely contacted an obstacle while climbing. CHIRP notes the perception trap of judging wire clearance at range and reminds that wires sag mid-span.
• Practical fix: Set RTH altitude locally before each flight, above towers, tree lines, cranes, and powerlines. Do not rely on obstacle avoidance to detect thin wires. Pre-flight, measure line heights relative to the home point and add margin for sag and wind.

BMFA SWEETS: a quick pre-flight check

• S — Sun: position now and later; glare; keep VLOS; avoid flying through the sun.
• W — Wind: direction/strength/turbulence; safe areas for forced or dead-stick landings.
• E — Environment: visibility (rain, mist, fog, fading light), people nearby, RF risks, space to fly a full circuit.
• E — Emergencies: plan what you will do if there is a malfunction or airspace incursion; confirm failsafes.
• T — Transmitter control: local Tx control and frequencies; correct model; trims/rates; Tx power/voltage.
• S — Site rules: club rules, local byelaws, no-fly zones, height and airspace limits.

Note: some older guides use “Eventualities” for the first E. Meaning is the same: think ahead about what could happen and how you will handle it.