SC-04: Multi-Authority Emergency
| Field | Value |
|---|---|
| Scenario ID | PER-004-SC-04 |
| Context / Trigger | At 3:10 PM, a wildfire is reported in a rural area that spans two county jurisdictions. Both county authorities (including David Okafor’s county, PER-003) are activating blanket denial rules for their respective portions. Jessica, operating at the state level (root authority), must coordinate the unified response: verify that both county restrictions are active and consistent, ensure no conflicting authorizations remain in the affected area, and confirm that emergency services flights are exempted. |
Narrative
Jessica receives notifications from both county authorities that blanket denial rules are being activated. She opens the COP on her center monitor and sets a geographic filter to the fire area. The COP shows: 2 activated commercial flights within the proposed restriction zone, 1 accepted (not yet activated) flight, and the incoming fire department drone operations requesting high-priority authorization.
She checks the blanket denial status for both counties. County A (David’s) has activated their restriction — the system shows it enforcing on the COP as a red overlay. County B’s restriction is still in “scheduled” status — a 3-minute delay. Jessica calls her County B counterpart to confirm they are proceeding. County B confirms and activates. The COP updates: the restriction zone is now continuous across both county boundaries.
The FAS automatically revokes the 1 Accepted (non-activated) commercial authorization within the zone [UERQ-SYS-1476] and sends a notification to the affected operator. The 2 Activated commercial flights are protected from automatic preemption [UERQ-SYS-1477], but Jessica sends preemption conflict notifications requesting voluntary compliance [UERQ-SYS-1468]. Both operators acknowledge and begin return-to-home procedures.
Meanwhile, the fire department’s high-priority authorization request arrives in the manual review queue. The automated rules pass (emergency services category, high priority [UERQ-SYS-1472]). Jessica approves and the fire department’s drone activates. Within 15 minutes, the fire area is clear of commercial traffic and the firefighting drone is operational.
Jessica monitors the COP for the remainder of the incident, watching for any new non-cooperative tracks entering the restriction zone. She coordinates with both county authorities throughout, maintaining shared situational awareness through the authority dashboard’s cross-jurisdiction view [UERQ-SYS-1591].
Traceability
| Linked End Goals | Correlate every active track with a valid authorization. Identify non-conformance and respond within 30 seconds. |
| Linked Capabilities | Blanket Denials (UERQ-SYS-1595), High Priority Preemption of Accepted Authorization (UERQ-SYS-1476), Preemption Prohibited After Activation (UERQ-SYS-1477), Preemption Conflict Notification (UERQ-SYS-1468), Emergency Services Priority (UERQ-SYS-1472), Cross-Jurisdiction View (UERQ-SYS-1591), Authorization Processing Suspension (UERQ-SYS-1420), Cross-Authority Event Visibility (UERQ-SYS-1846). |
| Safety Relevance | Critical: commercial drones operating in an active firefighting zone endanger both manned aerial firefighting aircraft and ground crews. The coordinated multi-authority response, with Jessica providing state-level oversight, ensures no gaps in the restriction coverage and no commercial flights remain active in the danger zone. |