SC-03: Field Sighting Correlation
| Field | Value |
|---|---|
| Scenario ID | PER-006-SC-03 |
| Context / Trigger | Jason Trask (PER-002) radios in a visual drone sighting from the stadium security perimeter during a major public event: “Drone observed, approximately 200 feet AGL, heading south over the north parking structure, no markings visible.” Rafael must determine whether this sighting corresponds to an existing COP track or represents a new, unidentified vehicle. |
Narrative
Rafael receives Jason’s radio report and simultaneously checks the COP for tracks near the stadium north parking structure. He finds two tracks within 0.5nm of Jason’s reported position.
Track 1: AUTH-2026-05992, “SkyView Media,” correlated with a valid authorization for aerial event photography. Position: directly over the parking structure at 210 feet AGL, heading south. This matches Jason’s description.
Track 2: AUTH-2026-05998, “Metro PD Aviation,” the department’s own surveillance drone operating at 350 feet AGL, 0.3nm east. Not a match (different altitude and position).
Rafael assesses: Track 1 matches Jason’s sighting in position, altitude, and heading. He radios back: “Field-05, COP confirms: track matches AUTH-2026-05992, SkyView Media, authorized event photography. Altitude 210 feet, heading south. Track is conforming.”
Jason acknowledges. Rafael logs the field correlation in the shift record: sighting timestamp, Jason’s report, matched track ID, and his classification decision. He also updates Track 1’s classification with a “field-corroborated” flag, which increases the track’s confidence in the system.
Rafael notes: if no matching track had existed, this would have escalated to a non-cooperative vehicle response. The speed of his correlation (48 seconds from Jason’s report to confirmed response) directly determined whether law enforcement escalation was triggered.
Traceability
| Linked End Goals | Classify every track within 60 seconds. Correlate field reports with COP tracks. |
| Linked Capabilities | Track Matching (UERQ-SYS-1641), Track Query Interface (UERQ-SYS-1816), Fused Track Output (UERQ-SYS-1813), Classification Tags (UERQ-SYS-1649), In-Field Device Data Feed (UERQ-SYS-1730). |
| Safety Relevance | Yes: a false-negative correlation (declaring no match when one exists) would trigger an unnecessary non-cooperative vehicle response during a major public event. A false-positive correlation (matching to the wrong track) would mask a genuine unidentified vehicle. |