On Oct 28, 9:19*pm, Andy wrote:

Also, to clarify, ADS-B does no path estimation of its own. That
function either would have to be added into an ADS-B unit by the OEM,
similar to the way Flarm does today - unlikely to be done in a glider-
specific way IMO - OR, it would have to be done by a separate external
device, perhaps a navigation computer/software like Oudie, WinPilot,
SN-10. For it to be effective manufacturers would all have to agree to
use the same algorithm, which also seems unlikely, unless they all
adopt the Flarm algorithm. That seems somewhat unlikely too, since I
don't think Flarm would want to start splintering how their algorithms
get used by splitting out the Flarm link technology from the collision
algorithm (which would have to be modified to accommodate the
differences in how path estimations get generated - with unpredictable
results). PLUS the external device OEM's would have to adapt to using
ADS-B inputs - another standards issue.

No matter how hard I try, it seems highly improbable that you will be
able to stitch together a satisfactory collision avoidance system for
gliders using ADS-B technology developed for general aviation. You'd
have to be satisfied with the simple functionality offered by ADS-B -
which would be fine if you generally come into conflict with GA and
airliners more often than other gliders, but there are a bunch of us
for whom the opposite is true. Then the problem becomes some gliders
using Flarm and others using ADS-B, you lose some of the Flarm
benefits of path estimation for the non-Flarm gliders.

9B

9B