Reeks of being misconfigured how it determines air/ground mode switching or improper software versions.
Is this speculation or something you know causes this failure? With FAA's guidance that transponder should be set to ALT even when on the ground and Garmin's automatic mode switching based on ground speed, maybe this is something to look into.
I'd check to make sure it's sensing the phase of flight (taxi vs. flight) correctly. It either has to use a GPS speed signal or a switch of some kind (squat or airspeed). That data feed isn't happening IMHO.I can't answer that question for sure. I can say that the GTX345 passed all the other tests in the FAA's Airborne 1090 analysis.
Given that everything seems to be working fine, let's say the answer to your question is no. What would that mean?
In my case, it would have sensed the phase of flight just fine, had I allowed it to (my first clue was an "are you sure?" prompt when I switched to ALT); I'd eliminate pilot error before roping the avionics shop in.I'd check to make sure it's sensing the phase of flight (taxi vs. flight) correctly. It either has to use a GPS speed signal or a switch of some kind (squat or airspeed). That data feed isn't happening IMHO.
Everyone is cooperating trying to solve a problem that has everyone stumped. There's no need for confrontational posturing. I just thought that maybe someone had seen this issue before like GeorgeC has. Comments about contacting the attorney general or withholding payment aren't helpful or what I'm looking for. But thanks anyway.
It's not my transponder either. I have a GTX327 and a GDL88.
The 15kt rule seems to be moving from myth to reality. Flying above or outside the required airspace is not looking like an option either. What we really need from the FAA is for them to publish the specifications given to the programmer who wrote the algorithm that issues these PASS / FAIL notices. Given I got my results in 15 minuses on a Saturday afternoon there is no way they are being issued by a carbon based life form. I am going to bet the specs don't follow the rules, or the program doesn't follow the specs.
Ours passed when we kept the 345 in standby until takeoff.
Jim,
Can you be a bit more specific on when you went from standby to alt both on takeoff and landing?
Thanks
Don
I didn't fly the test flight,a friend did. He told me he turned the 345 on at the start of the takeoff roll. I don't know if he turned it off after landing.
At Bergstrom we have very long taxi runs, up to almost 10,000 feet if the wind is from the south, as it usually is.
I didn't fly the test flight,a friend did. He told me he turned the 345 on at the start of the takeoff roll. I don't know if he turned it off after landing.
At Bergstrom we have very long taxi runs, up to almost 10,000 feet if the wind is from the south, as it usually is.
I didn't fly the test flight,a friend did. He told me he turned the 345 on at the start of the takeoff roll. I don't know if he turned it off after landing.
At Bergstrom we have very long taxi runs, up to almost 10,000 feet if the wind is from the south, as it usually is.
Putting the GTX 345 in standby on startup, and then altitude after liftoff, then standby prior to landing and taxiing worked to pass the test required for the rebate.
I tried following the protocol suggested by Garmin which states taxiing at no faster than a brisk walk. This did not work for me on multiple tests. Garmin told me that there would be a fix for this problem in a subsequent update.
I passed the test on the second flight. What I did was to keep the transponder in standby until shortly after takeoff, then put the transponder in Mode "C" as I gained about 50 feet. Upon completion of the required 30 minutes in listed airspace, I switched the transponder back to standby just prior to landing. My report showed zero errors in everything and all green passes for the rebate. Thanks for the great ideas received here. Hope Garmin comes out with an update for the GTX-345 to stop it from showing in-flight while sitting on the ground and not moving.
ADS-B Air/Ground Assessment
Did you get an Air/Ground failure on your ADS-B Performance Report? You’re not alone. The FAA has detected numerous ADS-B equipped aircraft reporting airborne mode while stationary or taxiing. The installer can correct some issues, but other issues stem from decisions made by the avionics manufacturer. The FAA is working with avionics manufacturers to better understand the symptoms and next steps.
To clarify, the ADS-B avionics makes the Air/ Ground decision. The ADS-B Performance Report includes an assessment of the ADS-B avionics’ ability to determine airborne vs. ground mode. If you receive an Air/Ground failure, please work with your installer for guidance on appropriate corrective action. If the issue remains, reach out to your avionics manufacturer. If you’re still experiencing issues, email 9-AWA-AFS-300-ADSB-AvionicsCheck@faa. gov and request a review. Please attach the ADS-B Performance Report with Subject: “PAPR Review Request: Air/Ground Failure” in your email to help expedite a response.
There's a lengthy discussion about this over on MooneySpace. I just came back from my verification flight - passed everything EXCEPT the "Air on Ground" flag. With this many people having the exact same problem with different aircraft and different shops in different states, the shop is not the problem, Garmin is the problem.True. But this could be a case of fixing something that's not broken. Someone else here has already shown this to be the case. It could be purely procedural or not flying in the correct airspace.
The avionics shop is also several states away. My friend opted to leave before he had a satisfactory test result. I'm simply asking if anyone else has run into this. I know at the AOPA Prescott Fly-In, there were numerous folks stymied by the FAA's report trying to collect the $500 rebate.