How are false tracks handled in the BCC?

• A. Delete all tracks automatically
• B. Ignore tracks that are uncertain
• C. Convert tracks into targets automatically
• D. Apply track quality filters, cross-check with corroborating sensors, and fade non-credible tracks

Answer: (D)

Managing false tracks relies on evaluating track quality and verifying them across multiple sensors. Instead of deleting everything at once or treating uncertain data as solid, a robust BCC approach filters tracks by quality metrics, checks them against corroborating sensor observations, and gradually reduces confidence for anything not well supported.

Applying track quality filters means the system assesses how well a track fits the data over time: consistency of position and velocity, sensor confidence, dwell time, and the coherence of observations. If a track isn’t meeting these criteria, its credibility is lowered. Cross-checking with corroborating sensors involves looking for supporting detections from other sources—like another radar, infrared, or electro-optical sensors—to confirm the target’s existence and movement. When corroboration is lacking or weak, the system fades the track, gradually reducing its prominence or removing it from consideration.

This combination helps prevent reacting to clutter or misdetections (false tracks) while preserving real targets that may be observed intermittently or by different sensor types.