bekolblockage
27th Jul 2017, 13:55
Question for those who have implemented ADS-B fused with Radar in "complex" airspace.
In the rare case of a bad ADS-B track with good NUCp value being broadcast (lets say the track is offset consistently by 20NM) forming a separate track from the 'real' radar track, what procedures/guidance do your controllers have for;
1. Verifying which is the real track
2. Once confirmed that the ADS-B track is incorrect and assuming the pilot is unable to disable ADS-B, what actions taken against other traffic that are/will be in conflict with the rogue track?
Ignore it?
Watch STCA alerts go off and ignore them?
Pass traffic info to other aircraft in conflict with the false track and offer vectors to avoid, 'just in case'??
Would be interested to hear others experience.
Cheers
BB
In the rare case of a bad ADS-B track with good NUCp value being broadcast (lets say the track is offset consistently by 20NM) forming a separate track from the 'real' radar track, what procedures/guidance do your controllers have for;
1. Verifying which is the real track
2. Once confirmed that the ADS-B track is incorrect and assuming the pilot is unable to disable ADS-B, what actions taken against other traffic that are/will be in conflict with the rogue track?
Ignore it?
Watch STCA alerts go off and ignore them?
Pass traffic info to other aircraft in conflict with the false track and offer vectors to avoid, 'just in case'??
Would be interested to hear others experience.
Cheers
BB