Originally Posted by
Squawk7700
The issue with displaying traffic via the internet is control and latency. There’s extra hops and latency between the two that can’t be controlled. For example, if an EFB took a feed from a 3rd party ADSB receiver network, what controls are around that data, what is the link latency and where is the data hosted (country)?
The best method is via an ADSB-in device, because the data can be controlled directly from the EFB, so they can decide what it shown and what isn’t. Have you ever noticed how FR24 or similar “estimate” where the other aircraft may be when signal is lost? Imagine if the feed from there was relied upon but was an estimate and the aircraft was not where the other pilot expected it to be!.
in relation to your comment about there being no controls in place about latency etc or the reliability of the 4G network, but really the limited traffic displayed on the device from other devices running the same app suffers similar limitations.
I agree that it is not a perfect solution and shouldn't be relied upon for separation but regarding your comment about an aircraft not being where the pilot expects it to be, isn't this the same problem with TCAS and all the other cheaper GA installations that try and display Mode C/S transponder returns on a map?