Recent ADS-B UAT issues

[takair]

Anybody else have recent issues with ADS-B UAT, primarily in class C and D airspace?  In the past two weeks I’ve had 3 reports from class D towers that my ADS-B was not reporting. In each case they had me ident and made a point of it. 
 

Here is the odd part. No issues in the class B I had flown through or approach control. FlightAware seems to have no issues either. The entire flights are captured almost to the ground. I recognize these networks are different, but….

Next odd part. I requested multiple FAA performance reports for the first two flights. They came back as not finding the flights…….BUT, when I enquirer with the FAA “report a problem” email, they told me they were having problems with the reporting system……BUT it should not have affected the feed to the tower. 
 
I had a similar thing happen last year. I chased it for a while, but the report at the time showed good in “rule airspace”, the FAA ADS-B problem folks said that means I’m good.  
 

Anybody run into similar situation?  I’m almost convinced “it’s not me, it’s them”.  That said, I installed this system relatively early and it’s a NavWorx system installed under AMOC. I have a strange suspicion that some towers are just coming on line with ADS-B capability and either aren’t seeing UAT or some issue with NavWorx comparability. 

[takair]

As a quick follow up…the FAA performance report for todays flight showed no failures. This makes me think even more that there is something going on with the way the towers are using ADS-B. 
 

[Marc_B]

Not specific to your xpndr, but I have a GTX330ES and I had two towers tell me they had issues with picking up my ads-b. The two things I could find was that my flight ID wasn’t set and my transponder was set to automatically go from ground to altitude reporting once airborne. 
I had my shop turn on flight ID (made sure my tail was listed) and I have it in continuous ALT. Now not a problem. 

Next time they mention an issue ask specifically what they aren’t picking up…ground signal, flight ID/tail number, no signal, what phase of flight…

[takair]

1 hour ago, Marc_B said:

Not specific to your xpndr, but I have a GTX330ES and I had two towers tell me they had issues with picking up my ads-b. The two things I could find was that my flight ID wasn’t set and my transponder was set to automatically go from ground to altitude reporting once airborne. 
I had my shop turn on flight ID (made sure my tail was listed) and I have it in continuous ALT. Now not a problem. 

Next time they mention an issue ask specifically what they aren’t picking up…ground signal, flight ID/tail number, no signal, what phase of flight…

Thanks.  I guess I can dig into the menu to be sure none of the software settings changed.  It sounds like I was completely invisible to them via ADS-B.  Once I would ident they would track me via mode C from the GTX-327.  Interestingly, in each case I had no problem with flight following…but they had dropped me prior to arrival vs doing a hand-off.  Wonder if that is just coincidence.

[takair]

So….the FAA got back to me.  Here is what they had to say:

“All 3 flights on 3/1 show ADS-B is working fine and reports are available.  Don't use ATC to check your ADS-B; use the report system.  All looks fine now.”

It is interesting that they say not to use ATC….but recall that it was ATC who told me in no uncertain terms that “your ADS-B does not work”.  

[Marc_B]

If they ever say that again, ask "what exactly could you not see?"  That may be telling.  At least FAA agrees with my avionics shop as well...they told me to just run the report and said it all looked squared away now.