Environment
Bound wind, sea state, current, depth, temperature, visibility and precipitation.
Reading method · 03
Specify airspace or waters, traffic, weather, visibility, depth, communications and recovery access before approving a mission.
FUURAA thesis
Engineering map
Each layer states the boundary to establish and the evidence needed for the next decision.
Bound wind, sea state, current, depth, temperature, visibility and precipitation.
Map people, aircraft, vessels, fishing gear, obstacles and protected areas.
Bound navigation, communications, weather, launch and recovery dependencies.
Verification questions
Each question needs an object, conditions, denominator, threshold and accountable decision owner.
Which conditions are explicitly inside scope?
What forces delay, degradation or abort?
How is domain drift detected?
Which control depends on local infrastructure?
Evidence to preserve
A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.
Versioned operational-domain specification
Traffic, hazard and dependency map
Go/no-go and change-control record
Scope boundary
Evidence from one route, season, depth or jurisdiction cannot be silently transferred to another.
This is an engineering reading and decision framework; it does not replace application-specific risk assessment, conformity work, procurement acceptance or professional advice.
Sources and evidence status
Source dates and review status remain visible; external sources open in a new tab.
Specifies requirements for safe commercial UAS operations, including external safety-critical command-and-control services.
Establishes a goal-based framework for MASS design, operation and certification, including modes, operational limits, remote centres, cybersecurity and human oversight.
Separates remote piloting from several autonomy levels and links supervision to traffic, hazards, weather, sensors, communications and recovery.