Deployment evaluation · 15

Navigation integrity and conflict avoidance

Test detection, classification, rules, manoeuvre, uncertainty and recovery around real traffic and hazards.

Evidence statusCross-domain mission framework · vehicle, operation and jurisdiction validation requiredLast reviewed: 15 August 2026
15

FUURAA thesis

Avoidance is a closed interaction with other traffic, not an isolated obstacle-detection score.

Engineering map

Turn the title into engineering objects that can be observed, measured and reviewed.

Each layer states the boundary to establish and the evidence needed for the next decision.

01

See

Measure detection range and probability across size, aspect, weather and sensor failure.

02

Decide

Verify classification, right-of-way logic, uncertainty and human escalation.

03

Act

Measure manoeuvre timing, clearance, stability and return to mission.

Verification questions

Write the questions first, then decide whether a demo, test, pilot or operating record can answer them.

Each question needs an object, conditions, denominator, threshold and accountable decision owner.

  1. 01

    Which traffic is hard to detect?

  2. 02

    How are ambiguous rules escalated?

  3. 03

    Can the manoeuvre create a new conflict?

  4. 04

    Are near misses retained?

Evidence to preserve

Enable the next reader to reconstruct conditions, results, failures and the decision.

A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.

  1. 01

    Evidence package 1

    Traffic and hazard test catalogue

  2. 02

    Evidence package 2

    Unedited detect-decide-act traces

  3. 03

    Evidence package 3

    Near-miss and corrective-action record

Scope boundary

State what this evidence still cannot be generalised to.

Sources and evidence status

Read standards scope, measurement evidence and application conclusions separately.

Source dates and review status remain visible; external sources open in a new tab.