SC-02: Track Correlation
| Field | Value |
|---|---|
| Scenario ID | PER-002-SC-02 |
| Context / Trigger | During the concert, Jason is at his observation post on the stadium’s south perimeter. He hears a faint buzzing and visually spots a small quadcopter approximately 200 feet AGL, 300 meters to the southeast, moving slowly northward toward the stadium. He needs to determine if this is a known, authorized operation or an unidentified aircraft. |
Narrative
Jason keeps his eyes on the drone while pulling up his tablet. The mobile COP shows his position and the area of interest boundary. He taps the approximate location on the map where he observes the drone — about 300 meters southeast of his position. The system executes a proximity query [UERQ-SYS-1816]: within a 200-meter radius of his tap point, there is one active track at approximately 180ft AGL, heading north-northwest at 8 knots.
The track has a green conformance indicator and a trust score of 0.85 [UERQ-SYS-1813(g)]. The track status shows it is correlated with a known authorization. Jason compares the system track’s position, altitude, and heading with what he sees visually. The track position is consistent: approximately the same direction from his position, roughly the right altitude, moving in the right direction.
He assesses this as the pre-approved aerial photography drone for the event. He notes the track ID and returns to full COP view. No escalation required. He radios his partner: “Drone visual confirmed — matches the event photographer’s track. Conforming.” Total time from sighting to classification: approximately 12 seconds.
Traceability
| Linked End Goals | Correlate a visually observed drone with a system track within 15 seconds. |
| Linked Capabilities | Track Query Interface (UERQ-SYS-1816), Fused Track Output Schema (UERQ-SYS-1813), In-Field Device Data Feed (UERQ-SYS-1730), TAK Protocol Support (UERQ-SYS-1662). |
| Safety Relevance | Yes: accurate visual-to-track correlation prevents both false escalations (wasting TOC resources and potentially causing an unnecessary rescind) and missed detections (failing to flag a genuinely unidentified drone). The correlation depends on track position accuracy, update rate [UERQ-SYS-1817: 1 Hz minimum], and trust score reliability. |