Interactive walkthrough · 11 steps · 2–4 minutes

Walk through an initial attack dispatch.

Plan the mission, launch it, handle two exceptions, and close it with an after-action report.

• Part 135 rotor-wing, initial attack
• Planning through after-action

Start the walkthrough

What happens in the walkthrough.

One mission, from the resource order to the record it leaves behind.

1. 01 Start from a saved SOP The mission opens from a template that already carries the tasks, the timing and the rules. The procedure is applied the same way every time, by whoever is on shift.
2. 02 Set the mission variables Every list is already filtered to what is legal for this order: aircraft carded for the work, on a current contract, and crew inside duty and rest. What you can see is what you can actually launch.
3. 03 Review the task timeline Times are calculated from the order and the helibase rather than typed. Mission variables appear inline in the tasks that use them, so the SOP becomes a procedure with live hooks into records, feeds and the duty clock.
4. 04 Arm the notification rules Alerts on what matters, and the exceptions that need an action. Escalation is settled in planning rather than during the incident.
5. 05 Go live One button turns an agreed plan into a monitored operation, and the crew brief goes out on its own.
6. 06 Run it, and handle two exceptions A TFR is published over the incident and caught before the crew asks — one SOP path, no judgment call, so LiveSOP^™ drafts the action. Then a reassignment would break the 8-hour flight time limit: LiveSOP shows the impact and the options the SOP allows, and stops.
7. 07 Close it out Operational control is a human authority, so the system surfaces, computes and routes but does not decide. The authorization, its basis and its owner are captured as it happens rather than reconstructed a week later.

Bring the procedure you think will break it.