It seems to me that we're straining at a problem that's not really a problem. I think this comes from the fact that the team at AP is so efficient at adding in our suggestions. Since this has now been identified as a potential output of the system, why can't we simply issue a notification to all iFly owners that this can be expected when we attach an ADS-B "in" component to the iFly. That way, those of us who plan to buy either a SkyRadar or some other unit will expect it and know to compensate in our scan for that anomaly. I think that would be much easier than rewriting code for the unit, at least until the ADS-B system becomes more robust and reliable.
Sam