SC-02: Non-Conformance Response
| Field | Value |
|---|---|
| Scenario ID | PER-004-SC-02 |
| Context / Trigger | At 10:22 AM, the COP displays a critical alert: an activated flight (commercial infrastructure inspection, authorization AUTH-2026-04187) has exited its authorized operational volume. The aircraft’s track shows it 120 meters outside the lateral boundary of its authorized polygon and continuing to diverge. The flight is operating 0.8nm from the boundary of a blanket denial zone protecting a military installation. |
Narrative
The COP audible alert fires — a distinct, priority-differentiated tone for Critical severity non-conformance [UERQ-SYS-1840(a)]. The alert banner on Jessica’s center monitor shows: “GEOFENCE BREACH — AUTH-2026-04187 — Lateral deviation 120m, increasing. Proximity to MIL-RESTRICT-07: 0.8nm.”
Jessica clicks the alert. The COP zooms to the affected area and displays: the aircraft’s current position (red icon indicating non-conforming), its authorized volume boundary (dashed blue polygon), the military restricted zone (solid red polygon), and a velocity vector showing the aircraft’s heading and speed. The deviation trend indicator shows the gap is widening at approximately 2 meters per second.
Jessica assesses: this is not a transient GPS error — the deviation is sustained and directional. She has 15–20 seconds before the aircraft could reach the military restricted zone boundary at its current trajectory.
She drills down to the authorization detail panel: operator is “Apex Infrastructure Services,” RPIC is “T. Morgan,” Part 107 verified, TSA cleared. Contact: operator’s dispatch phone number is displayed (per tenant privacy configuration: full disclosure mode). [UERQ-SYS-1845(a)]
Jessica makes the decision: issue a rescind notification. She selects the authorization on the COP and taps “Rescind.” The system presents a confirmation dialog with the authorization ID, operator name, and a required field for justification. Jessica types: “Sustained lateral geofence breach, trajectory toward MIL-RESTRICT-07, increasing deviation.” She confirms.
The FAS transitions the authorization to Rescinded state and sends a preemption notification to the operator’s app [UERQ-SYS-1474]. Delivery confirmation appears on Jessica’s event feed within 8 seconds: “Rescind notification delivered to Apex Infrastructure Services — T. Morgan. Delivery channel: in-app push + SMS.”
Jessica monitors the track. Within 90 seconds, the aircraft begins a return-to-home trajectory. The track re-enters the original authorized volume boundary and lands 4 minutes later. Jessica logs the incident summary in the event feed and notifies the military installation liaison that the incursion threat was contained. Total time from alert to rescind delivery: 38 seconds.
Traceability
| Linked End Goals | Identify a non-conformance event and assess its severity within 30 seconds. Issue a rescind notification and confirm delivery within 60 seconds. |
| Linked Capabilities | Operational Event Types (UERQ-SYS-1838(a): geofence breach), Event Notification Content (UERQ-SYS-1839), Event Severity Levels (UERQ-SYS-1840), Incident Notification Latency (UERQ-SYS-1841), Manual Authorization Withdrawal (UERQ-SYS-1419), Preemption Notification Sent (UERQ-SYS-1474), Fused Track Output (UERQ-SYS-1813), Trust Scoring (UERQ-SYS-1638). |
| Safety Relevance | Critical: the 38-second response time prevented an unauthorized incursion into military restricted airspace. A slower response — or a missed alert due to alert fatigue — could have resulted in a security incident and potential conflict with military operations. The severity-tiered alert system and one-click rescind workflow directly enabled Jessica’s response speed. |