System anatomy · 08

Launch, recovery and maintenance

Design the people, equipment, weather window, retrieval plan and post-mission inspection as part of every mission.

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

FUURAA thesis

A platform that cannot be launched, recovered and returned to a known condition is not an operational system.

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

Launch

Bound handling loads, deck or site hazards, checks and go/no-go authority.

02

Recovery

Plan rendezvous, landing, surfacing, failed retrieval and personnel safety.

03

Turnaround

Inspect damage, batteries, sealing, corrosion, calibration and software state.

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

    What makes launch unsafe?

  2. 02

    How is a disabled vehicle retrieved?

  3. 03

    What evidence releases it for the next mission?

  4. 04

    Are support-vessel and crew risks counted?

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

    Launch and recovery risk assessment

  2. 02

    Evidence package 2

    Failed-retrieval and salvage plan

  3. 03

    Evidence package 3

    Post-mission inspection and release 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.