Duplicate glider on CCAS VFRnav?

VFRnav Support
1

Hello,

How can we explain the duplication of this glider?

  • Did the owner tinker with an Arduino/FLARM/Stratux setup?
  • A CCAS fault?
  • A VFRnav fault?

CCAS_VFRnav
CCAS_VFRnav1146×539 188 KB

This also raises the question of being able to quickly silence the audible alarm, since these 36 aircraft do not exist… except for one.

I also had a case of an in-flight collision alert on the CCAS radar while I didn’t see the aircraft… I turned back to look for it and saw it a minute away (very far). This effect seems due to information latency.

Is it fair to conclude that there is no precise, time-coordinated temporal information tied to position in CAS systems?

Also, aircraft that appear to be arriving from afar may already be very close, and those that should be approaching us may have already passed?

Thanks for your input.

Daniel.

2

Hi Daniel,

Thanks for your observation and description. :+1:

  • ..that could certainly be, but I don’t see it as the root cause of what you’re describing

  • @H655 I don’t think it’s a direct error, maybe cache management.

  • @H655

  • How did you connect CCAS to VFRnav?

    • TCP/2000
    • UDP/4000

  • What does CCAS show on its own? Surely not a thousandfold? Or?

  • Have you paired a Stratux or Flarm to CCAS?

  • What do the received traffic data in VFRnav show? Correct there?

In general, I observe a different behavior with solutions like CCAS or Safesky etc. than when you have your own reception system (that’s what I’ll call it) on board.

Thanks again for the info, this will be clarified.

Pilot greetings,

Karsten

3

Hi Daniel,

tanks for the heads-up.
The points Karsten has already written would be great for further troubleshooting :+1:

Clear skies
Hermann

  • @H655 I don’t think it’s a direct error, maybe cache management.

yep, that’s what I assume too. I’ll take a look as soon as I have more info.

4

I’m paired with an UPD4000.

No Flarm or Stratux on board, just a test in the living room.

I didn’t look at the CCAS screen. :worried:

I’ve already noticed duplicate aircraft in the VFRnav traffic list, which have different codes but are the same aircraft several times. Same altitude, same location.

Here the location and the altitude vary. But there’s no movement. It’s only a succession of positions, without erasing the previous position. It doesn’t display an aircraft code, just the altitude.

For this particular case I think I remember it being reported dozens of times in the VFRnav list with a different specific code. I’m not entirely sure.

One possibility would be that it loses the network, and each time it reconnects it’s considered new?

That’s unfortunately all I can say. It was version 4.24

Other times I don’t have any problem.

Have a good flight.

5

I just saw that he’s back!

The base data has indeed already been duplicated in CCAS.

I’ll attach screenshots later.

Edit. I reached them by phone; it’s a FLARM that’s causing this mess…

6

I’ll take a look, thanks for the info :flexed_biceps: :+1:

7

Here are the saboteur’s traces! :wink:

The club involved will try to find the culprit. They suspect a motor glider whose FLARM seems to be malfunctioning.

See you

Screenshot_20260421_151044(1)
Screenshot_20260421_151044(1)1152×720 292 KB

Screenshot_20260421_152642_VFRnav(1)
Screenshot_20260421_152642_VFRnav(1)1152×720 213 KB

Screenshot_20260421_151607_VFRnav(1)
Screenshot_20260421_151607_VFRnav(1)1152×720 192 KB

8

I received their response.

It’s not a FLARM nor a motor glider. Nor a model aircraft.

That leaves only the hypothesis of a SafeSky or a CCAS on a UL.

We’re back to the basic problem of cheap CAS on phones, or perhaps of the processing center? In any case, you can clearly see dozens of messages coming from the same device with a multitude of different identifiers.

Hope this helps.