SC-03: Unidentified Drone
| Field | Value |
|---|---|
| Scenario ID | PER-002-SC-03 |
| Context / Trigger | Ninety minutes into the concert, a patrol officer on the north perimeter calls Jason on the radio: “I’ve got a small drone, looks like a consumer quad, about 150 feet up, hovering over the parking lot. It’s not one of ours.” Jason redirects to the north perimeter and confirms the visual sighting. He checks his tablet — there is no track within 500 meters of the reported position. |
Narrative
Jason performs a proximity query on his COP [UERQ-SYS-1816] centered on the parking lot. No tracks appear within the search radius. The data feed status indicator is green — the system is connected and receiving updates. This is a genuine gap: there is a drone in the sky that is not in the system.
Jason initiates a visual sighting report from the mobile interface. The streamlined submission form pre-populates his GPS position and timestamp. He enters: approximate drone position (taps the parking lot on the map), estimated altitude (150 feet), estimated heading (stationary/hovering), visual description (“small white quadcopter, consumer-type, no visible markings, approximately 12-inch span”). He optionally snaps a photo with the tablet’s camera and attaches it. He taps “Submit and Escalate.”
The system submits the visual sighting report to the Traffic Service as a field observation. Simultaneously, an escalation notification is sent to the TOC (Jessica Cooper’s team) with the sighting details and Jason’s assessment: “Unidentified UAS, no matching track, hovering over occupied parking lot adjacent to stadium. Requesting TOC assessment.”
The TOC acknowledges receipt. Jessica queries the FAS for any authorized operations in the parking lot area — none exist. She coordinates with the event security commander and Jason’s Unit Sergeant for law enforcement response. Jason maintains visual contact with the drone while his partner coordinates with the north perimeter patrol officers to establish a safe cordon. The drone departs to the east after approximately 4 minutes. Jason updates the sighting report with a departure time and direction.
Traceability
| Linked End Goals | Submit a visual sighting report for an unidentified drone in under 30 seconds. Escalate to the TOC with one tap. |
| Linked Capabilities | Track Query Interface (UERQ-SYS-1816), In-Field Device Data Feed (UERQ-SYS-1730), In-Band Status Flags (UERQ-SYS-1664), Incident Monitor role event escalation. |
| Safety Relevance | Critical: an unidentified drone hovering over an occupied area during a major public event is a potential security threat. The speed and accuracy of Jason’s sighting report directly affects the response timeline. If the report is delayed, inaccurate, or lost due to connectivity issues, the response is compromised. |