Public ADS-B Performance Reports show Air-On-Ground failure on every flight. All other areas pass their tests. ADS-B Out installed 10-26-2015 using Garmin GNS530W and Garmin Transponder GTX330ES. Original installation passed Air-on-Ground after install. ADS-B In using Stratus 2 and iPad Mini 3. Corrective action so far:
1. Follow Garmin's direction to remain stationary after start until GPS position established, no ADS-B faults displayed, taxi at very slow taxi speed less than 12 knots. No help.
2. Check GTX330ES Set-up for Delay Time. Was set at 24 seconds. Changed to 02 seconds per avionics shop guidance from the STC. No help.
FAA ADS-B program office did preliminary and secondary performance reports. Secondary report clearly shows "the transponder was turned on just prior to takeoff and turned off just after landing." "The preferred method is to turn on the transponder prior to taxi and just leave it in ALT mode for the entirety of the flight and let the software in the transponder and the GPS information from the navigator do all the work."
As far as I can tell, the transponder was in ALT the entire time after the Avionics Master Switch was turned on. So, I am not manually turning the transponder On or Off. But the picture clearly shows ADS-B signals start on takeoff roll on the runway and stop as the aircraft slows on the landing runway just prior to runway exit. There is no signal during taxi out or in.
Other forum posts suggest transponder set-up problems are a leading reason for ADS-B errors. I have already changed the delay time to 2 seconds. Any other ideas?
1. Follow Garmin's direction to remain stationary after start until GPS position established, no ADS-B faults displayed, taxi at very slow taxi speed less than 12 knots. No help.
2. Check GTX330ES Set-up for Delay Time. Was set at 24 seconds. Changed to 02 seconds per avionics shop guidance from the STC. No help.
FAA ADS-B program office did preliminary and secondary performance reports. Secondary report clearly shows "the transponder was turned on just prior to takeoff and turned off just after landing." "The preferred method is to turn on the transponder prior to taxi and just leave it in ALT mode for the entirety of the flight and let the software in the transponder and the GPS information from the navigator do all the work."
As far as I can tell, the transponder was in ALT the entire time after the Avionics Master Switch was turned on. So, I am not manually turning the transponder On or Off. But the picture clearly shows ADS-B signals start on takeoff roll on the runway and stop as the aircraft slows on the landing runway just prior to runway exit. There is no signal during taxi out or in.
Other forum posts suggest transponder set-up problems are a leading reason for ADS-B errors. I have already changed the delay time to 2 seconds. Any other ideas?
