SC-04: Geofence Breach
| Field | Value |
|---|---|
| Scenario ID | PER-002-SC-04 |
| Context / Trigger | The pre-approved aerial photography drone (the one Jason correlated in Scenario 2) deviates from its authorized volume. It was authorized to operate south of the stadium at 200ft AGL. It has crossed north, directly over the stadium seating area, at 250ft AGL and climbing. The FAS detects the geofence breach and generates a Critical severity event. |
Narrative
Jason’s tablet emits a high-priority audible alert — a distinct tone that cuts through the ambient concert noise. The COP display highlights the non-conforming track in red with a pulsing boundary showing the authorized volume it has exited [UERQ-SYS-1838(a), UERQ-SYS-1839(f)].
The alert banner displays on a single screen without requiring Jason to navigate: event type (“Aircraft outside approved area”), track position (over stadium, 250ft, climbing), deviation (50ft above authorized ceiling, 400m north of authorized area), trend (deviation increasing — heading further north, still climbing), trust score (0.82 — high-confidence track) [UERQ-SYS-1839, UERQ-SYS-1840(a)].
Jason assesses the situation in 10 seconds: this is a known track that has left its authorized volume and is now over 40,000 people. The deviation is increasing. He taps “Escalate to TOC” — the escalation attaches the track ID, the non-conformance event details, and his field assessment: “Track [ID] non-conforming over occupied stadium. Deviation increasing. Recommend TOC action.”
Jessica Cooper at the TOC receives the escalation simultaneously with her own COP-generated non-conformance alert. She has the authorization-level visibility that Jason does not: she can see the operator identity, the authorization details, and she has the authority to issue a rescind notification [UERQ-SYS-1419]. Jessica issues the rescind. The operator receives the notification and begins return-to-home.
Jason maintains visual contact and confirms the drone is descending and heading south, back toward its authorized area. He updates the escalation: “Track returning to authorized volume. Visual confirmed.” Total time from alert to escalation: 20 seconds. Total time from alert to drone returning: approximately 90 seconds.
Traceability
| Linked End Goals | Receive non-conformance alerts within 5 seconds of event detection. Assess severity without switching screens. Escalate with one tap. |
| Linked Capabilities | Incident Notification Latency (UERQ-SYS-1841), Operational Event Types (UERQ-SYS-1838), Event Notification Content (UERQ-SYS-1839), Event Severity Levels (UERQ-SYS-1840), Incident Notification Channels (UERQ-SYS-1842), Incident Monitor Audit Trail (UERQ-SYS-1844). |
| Safety Relevance | Critical: a drone over 40,000 people is an immediate safety concern. Jason’s field-level awareness — visual confirmation of the drone’s position and behavior — complements the TOC’s system-level view. The combination of field and system awareness enables a faster and better-informed response than either alone. The 5-second notification latency [UERQ-SYS-1841] for Critical events is a safety-relevant performance requirement that this scenario validates. |