SC-03: Unidentified Track
| Field | Value |
|---|---|
| Scenario ID | PER-004-SC-03 |
| Context / Trigger | At 1:45 PM, the Traffic Service detects a new track via a ground-based MLAT sensor [UERQ-SYS-1795] near a county airport’s approach path. The track has no matching authorization in the FAS — no Remote ID broadcast, no activated flight plan. It is classified as an unidentified/non-cooperative vehicle. The system generates a “missing track” alert (inverse of UERQ-SYS-1411: a track exists with no authorization, rather than an authorization with no track). |
Narrative
The COP displays the unidentified track with a distinct icon (yellow triangle — unidentified) and an audible alert: “UNIDENTIFIED TRACK — No matching authorization — Airport proximity zone.”
Jessica’s event feed shows: track ID TRK-88401, data source: MLAT sensor M-07, trust score: 0.72 [UERQ-SYS-1638], altitude: 280ft AGL, speed: 22 knots, heading: 195°, position: 0.6nm north of Runway 28 extended centerline.
Jessica assesses: the track is real (trust score above threshold), in a safety-critical location (airport approach path), and has no authorization. This is her highest-risk scenario.
She checks for possible data correlation errors: could this be an authorized flight whose track wasn’t matched? She queries the authorization database for active/activated flights within 1nm of the track’s position. Result: one activated authorization (AUTH-2026-04201, operator “SkyView Media”) has an authorized volume 0.4nm east. But that flight’s track is separately displayed on the COP with a green conformance indicator — it is accounted for.
The unidentified track is not a correlation error. Jessica escalates: she selects the track and initiates the “Non-Cooperative Vehicle” workflow. The system logs the detection event [UERQ-SYS-1844] and generates a structured alert package for the airport authority, including: track position, altitude, speed, heading, estimated time to runway centerline intercept, and data source.
Jessica simultaneously calls the airport tower supervisor on the direct line to provide verbal notification. She also alerts her county-level counterpart (David Okafor’s office) to check whether they have any off-system authorization or waiver for the area. County reports negative.
The airport tower issues a NOTAM advisory to inbound manned aircraft. Jessica monitors the unidentified track on the COP. After 6 minutes, the track descends below sensor coverage and disappears.
She logs the full incident: detection time, assessment, escalation actions, and resolution. The incident is flagged for the quarterly state audit and post-incident review.
Traceability
| Linked End Goals | Correlate every active track with a valid authorization and immediately flag unmatched tracks. |
| Linked Capabilities | Track Matching (UERQ-SYS-1641), Missing Track Alert (UERQ-SYS-1411), Fused Track Output with trust score (UERQ-SYS-1813), MLAT Data Ingestion (UERQ-SYS-1795), Trust Scoring (UERQ-SYS-1638), Classification Tags (UERQ-SYS-1649), Cross-Authority Event Visibility (UERQ-SYS-1846), Incident Monitor Audit Trail (UERQ-SYS-1844). |
| Safety Relevance | Critical: an unidentified drone in an airport approach path is the highest-risk scenario in UAS traffic management. The system’s ability to detect, classify, and surface the track immediately — and Jessica’s ability to assess and escalate within minutes — is the core safety function of the Airspace Manager role. |