Launch
Bound handling loads, deck or site hazards, checks and go/no-go authority.
System anatomy · 08
Design the people, equipment, weather window, retrieval plan and post-mission inspection as part of every mission.
FUURAA thesis
Engineering map
Each layer states the boundary to establish and the evidence needed for the next decision.
Bound handling loads, deck or site hazards, checks and go/no-go authority.
Plan rendezvous, landing, surfacing, failed retrieval and personnel safety.
Inspect damage, batteries, sealing, corrosion, calibration and software state.
Verification questions
Each question needs an object, conditions, denominator, threshold and accountable decision owner.
What makes launch unsafe?
How is a disabled vehicle retrieved?
What evidence releases it for the next mission?
Are support-vessel and crew risks counted?
Evidence to preserve
A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.
Launch and recovery risk assessment
Failed-retrieval and salvage plan
Post-mission inspection and release record
Scope boundary
A successful autonomous phase can still depend on hazardous manual launch and recovery work.
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.
Describes untethered AUVs executing planned missions, storing payload data, surfacing for communications and requiring later recovery and processing.
Separates remote piloting from several autonomy levels and links supervision to traffic, hazards, weather, sensors, communications and recovery.
Explains Part 107 remote-pilot certification, recurrent knowledge, weather, loading, emergency, maintenance and night-operation requirements.