ADS-B in radar airspace
Thread Starter
Join Date: Feb 2002
Location: Hongkers
Posts: 469
Likes: 0
Received 0 Likes
on
0 Posts
ADS-B in radar airspace
Not getting any bites on the ATC forum, so trying here.
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
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
ADS-B tracks being displaced aren't just rare, they're vanishingly so. I'm only aware of one such occurrence and that was outside radar coverage. There may have been others but it can't have been many.
As such we don't have any firm procedures but prudence would say treat it as real.
As such we don't have any firm procedures but prudence would say treat it as real.
Folks,
I am intrigued that this could happen on a C-145/146 GPS derived position, or is this some thing that is applicable to FMCS (by whatever name) derived position being broadcast.
Any ideas, please?
Tootle pip!!
I am intrigued that this could happen on a C-145/146 GPS derived position, or is this some thing that is applicable to FMCS (by whatever name) derived position being broadcast.
Any ideas, please?
Tootle pip!!
Thread Starter
Join Date: Feb 2002
Location: Hongkers
Posts: 469
Likes: 0
Received 0 Likes
on
0 Posts
ADS-B tracks being displaced aren't just rare, they're vanishingly so. I'm only aware of one such occurrence and that was outside radar coverage. There may have been others but it can't have been many.
As such we don't have any firm procedures but prudence would say treat it as real.
As such we don't have any firm procedures but prudence would say treat it as real.
Rare but we still notice the occasional one in non-radar. Now that we are moving to fused ADS-B/MRT in the TMA, the issue of how to deal with that in congested airspace is difficult.
As you say, you'd be a brave person to ignore it but trying to dodge the traffic in our TMA would be just about impossible.
Can't tell them to turn it off.
Can't blacklist immediately.
Pull ADS-B from the SDP?
Hmmmm.
Thanks for the reply anyway.
Have a feeling we may have worked together in Melbourne many moons ago. (?)
