CorrelationAmbiguityData

AIRM Conformant
False

This class is present when the automatic correlation process failed because it was unable to identify a unique relationship between a single SFPL and a single system track via the SSR code assigned to the SFPL. This would occur under the following circumstances:

ONESFPL_MANYTRACKS - multiple tracks within the SFPL's correlation search volume are squawking the SSR code assigned to the SFPL.
MANYSFPL_ONETRACK - A track update is received whose received SSR code is assigned to multiple SFPLs that meet the correlation criteria.
MANYSFPL_MANYTRACKS - there are multiple SFPLS and tracks that meet the correlation criteria, i.e. the SFPLs are assigned the same code and multiple tracks are squawking that same code in the region where

If there are multiple tracks that meet the correlation criteria for an SFPL then the relevant track identifiers are provided in the correlation ambiguousTrackData.

If there are multiple flights that meet the correlation criteria for an SFPL then the relevant flight identifiers are provided in the correlation ambiguousFlightData.

Ambiguous correlation issues usually require manual intervention by a controller. For example, the ONESFPL_MANYTRACKS case means that at least one aircraft is squawking the wrong code. This may be a transient situation because the transponder of an aircraft was not put into Standby mode when changing codes or simply that an aircraft has entered the wrong code. In the former case it may resolve itself but in the latter case a controller will have to identify the aircraft involved and resolve the situation manually.