9.3 Firmware, Braking Distance & Flyaway Causes

Closing the Flight-Performance Navigation Chapter

Sections 9.1 and 9.2 explained GNSS position and compass heading. This section ties those failure modes to firmware hygiene, braking distance (why speed caps save people), and the exam definition of a flyaway—then gives a practical Near People prevention checklist you can recite on paper and on site.

Together with mass/payload, batteries, and failsafe/RTH topics from the rest of the flight-performance domain, this is how the A2 candidate shows they understand UAS flight performance as ground-risk control, not as hobby gadget lore.

Keep Firmware Updated

Firmware is the software that runs on the aircraft, remote controller, and sometimes batteries or gimbals. Manufacturers issue updates to:

• Fix flight-control bugs that can contribute to instability or flyaways.
• Improve geo-awareness map data handling and zone alerts.
• Maintain Remote ID compliance behaviour where required for the class.
• Keep low-speed mode, braking logic, obstacle sensing, and failsafe state machines reliable.
• Patch security and connectivity issues that can affect link quality.

For A2 theory, the high-yield statement is simple: installing the latest manufacturer firmware safety updates is the pre-flight action that best keeps safety features current and free of known defects. Cleaning the lens, charging only the controller, or painting propellers does not update geo-awareness, low-speed mode, or failsafe code.

Firmware discipline for Near People ops

1. Update in a controlled environment before the job day—not in a windy car park five minutes before clients arrive, unless the manufacturer requires an urgent patch and you still have time to re-test.
2. After major updates, complete any required calibrations and a short hover test far from people.
3. Confirm geo-awareness databases are current (Chapter 5: stale maps are a failed technical mitigation).
4. Confirm low-speed mode still engages and limits speed as documented.
5. Confirm Remote ID still functions where the class requires it.
6. Read release notes for changes to RTH height, lost-link behaviour, and brake settings—misreading a new default is a classic failsafe misconfiguration path.

Exam trap: "Firmware is optional if the aircraft flew fine last year." Out-of-date software can leave known bugs and outdated geo data in place. For class-featured UK2 A2 work, treating firmware as optional undermines the technical mitigations the privilege assumes.

Braking Distance, Speed, Mass, and Low-Speed Mode

When someone steps into your buffer, or when you see the aircraft drifting toward a path, you need the aircraft to stop or reverse before it reaches them. Stopping is not instant.

Qualitative performance rules for the exam:

• Higher speed → longer stopping distance. The aircraft must cancel more kinetic energy and may need more metres to reverse horizontal velocity.
• Greater mass → harder to stop at the same speed (more momentum/energy; motors must work harder against inertia).
• Wind along the direction of travel can extend the distance needed to stop relative to the ground.
• Low-speed mode (commonly about 3 m/s on class-marked UK2/C2 types) caps maximum speed, which:
  • Cuts kinetic energy roughly with v² (Chapter 5).
  • Shortens braking/stopping distance so a pilot can protect the person bubble.
  • Is the technical key to the 5 m horizontal floor after weather, performance, and segregation evaluations—not informal "gentle sticks."

Stopping-distance thinking table

Link to separation rules: flying "slowly" without engaging manufacturer low-speed mode does not create the 5 m privilege and does not guarantee the same speed cap if a stick twitch or automation resumes higher speed. For Near People work, mode on + evaluations + legal floor is the package.

What a Flyaway Is

A flyaway is an uncommanded departure: the unmanned aircraft stops responding as intended and moves off uncontrolled (or so poorly controlled that the pilot cannot keep it on the planned path). It is not:

• A planned long-range autonomous mapping mission.
• A battery storage mode.
• A propeller type.

It is a serious safety event, especially in Open Near People environments where uninvolved persons, vehicles, and structures sit close to the operating volume.

Common Flyaway Causes (A2 Syllabus Map)

Exam stems often combine causes (steel bridge + wind + outdated firmware). Answer with the immediate safety action and the root performance issue, not with denial that flyaways exist on "modern" drones.

Failsafe Misconfiguration — A Special Exam Trap

Failsafes (lost-link RTH, hover, land, continue) are technical mitigations only if configured for this site:

• Home point recorded in a bad GNSS location may send RTH over a road full of people.
• RTH altitude set below obstacles or through a person-rich layer can create a forced fly-through.
• "RTH on everything" without thinking about assemblies of people or FRZ edges is not professional A2 practice.
• After firmware updates, defaults may change—re-verify.

Link this to Chapter 8-style failsafe learning if present in your pack: know what the aircraft will do if the link dies, and ensure that behaviour does not aim residual energy at uninvolved persons.

Prevention Checklist for Near People (A2) Ops

Use this as a single mental card before any 30 m / 5 m job:

A. Identity and rules

1. Valid Flyer ID and A2 CofC; Operator ID labelled as required.
2. Aircraft UK2/C2 (or eligible legacy) matches the distance rule you plan to use.
3. VLOS, height ≤ 120 m (unless another lawful structure applies), airspace/FRZ clear.

B. Technical integrity

1. Firmware and geo-awareness data current; Remote ID working if required.
2. Low-speed mode tested if you intend 5 m; props/airframe sound; mass within MTOM.
3. Compass calibrated in a clean magnetic environment; no metal-pad calibration.
4. GNSS quality good; home point verified visually and on the map.
5. Failsafes set for this site; RTH height and action make sense.

C. Performance and environment

1. Wind/gusts within manufacturer limits; no ATTI-only plan in gusts near people.
2. Battery healthy and adequate for the task plus contingency.
3. Site supports segregation; abort lines clear if people approach.

D. Human factors

1. Pilot ready for manual control if GNSS or compass degrades.
2. Eyes on aircraft and people bubble—not only the screen.
3. Go/no-go: if any of B or C fails, widen distance, relocate, or cancel—do not "save the shot."

This checklist is layered safety (Chapter 5): technical features + operational judgment + statutory floors.

If a Flyaway or Serious Degradation Starts

1. Eyes on the aircraft — establish orientation.
2. Attempt recovery with smooth, correct inputs if control remains; switch modes only if trained and the manual supports it (e.g., ATTI when GPS is corrupt—model-specific).
3. Steer residual flight path away from uninvolved persons if possible; avoid overflight.
4. Land in the first clear safe area when controllable.
5. If completely unresponsive, follow manufacturer emergency guidance; warn people on the ground if safe to do so; do not run under the aircraft.
6. After any flyaway event: do not relaunch for A2 work until cause is understood (compass, GNSS, RF, damage, config, wind).

Realistic Integrated Scenarios

Scenario A — outdated firmware, 5 m job. Low-speed mode flickers; geo map misses a temporary restriction. Correct approach: update and re-test before Near People closeness; do not rely on last year’s software.

Scenario B — fast normal-mode pass beside a path. Someone steps out; stopping distance exceeds the remaining gap. Lesson: speed and mass set braking needs; low-speed mode and larger buffers exist for this reason.

Scenario C — compass + stick panic. Toilet-bowling begins; pilot slams sticks watching FPV. Aircraft accelerates toward a pavement. Better path: VLOS, calm inputs, land, recalibrate away from steel.

Scenario D — mis-set RTH. Link glitch triggers RTH over a busy yard because home was set on multipath. Prevention: open-sky home, verify pin, understand failsafe path before take-off.

Memory Hooks for Section 9.3

1. Firmware currency = geo-awareness, RID, low-speed mode, failsafe reliability.
2. Stopping distance ↑ with speed and mass → low-speed mode near people.
3. Flyaway = uncommanded departure (interference, compass, GNSS, sticks, failsafe, RF, wind).
4. Prevention checklist before every A2 flight; abort when layers fail.
5. People safety first in recovery—never finish the shot over uninvolved persons.

With GNSS hold, compass discipline, firmware hygiene, braking awareness, and flyaway prevention memorised, you complete the navigation-and-control portion of A2 flight performance and are ready to connect these ideas to meteorology and operational ground-risk chapters in scenario questions.