SC-01: Pre-Flight
| Field | Value |
|---|---|
| Scenario ID | PER-001-SC-01 |
| Context / Trigger | Julia arrives at a bridge inspection site at 7:00 AM. She has a pre-submitted flight authorization request for a 2-hour inspection window in controlled airspace near a regional airport. She needs to confirm authorization status, activate the flight, and launch. |
Narrative
Julia opens the ATOMx operator app on her tablet. The pre-flight compliance view shows her authorization in the Accepted state: green status indicator, authorized volume displayed on the map overlay, time window 7:15–9:15 AM, and one condition: altitude ceiling 300ft AGL. She taps the operator attribute panel to verify her credentials are current: Part 107 (valid), TSA clearance (valid), aircraft registration (current, NDAA-compliant).
At 7:10 AM, Julia taps “Activate Flight.” The system submits the activation request. Because the tenant has activation-time re-evaluation enabled (UERQ-SYS-1425), the FAS re-checks for conflicts with high-priority flights, weather minimums, and any authority vetoes since acceptance. All checks pass. The system confirms activation within 3 seconds and transitions the authorization to Activated state (UERQ-SYS-1434).
The FAS notifies the Conformance Monitoring Service, Traffic Information Service, and Network Identification Service (UERQ-SYS-1410). Julia sees the dashboard update: status changes to Activated, a countdown timer shows remaining authorized time, and her aircraft telemetry feed is connected and reporting to ATOMx.
Julia powers up the aircraft and begins the inspection. During the flight, the operator app displays her authorized volume boundary on the map with her live position. A proximity indicator shows how close she is to the volume boundary. The system operates without incident and Julia completes the inspection at 8:45 AM. She taps “End Flight” and the authorization transitions to Ended state.
Traceability
| Linked End Goals | Confirm authorization status on mobile device at launch site. Submit activation and receive confirmation before takeoff. |
| Linked Capabilities | Operator Application Interface (UERQ-SYS-1441), Activation Confirmation (UERQ-SYS-1434), Activation-Time Re-Evaluation (UERQ-SYS-1425), Activation Notification (UERQ-SYS-1410), Authorization Response — Approval (UERQ-SYS-1459). |
| Safety Relevance | Yes: Julia’s go/no-go decision depends on accurate authorization status display. Activation-time re-evaluation is a safety gate ensuring conditions haven’t changed since acceptance. |