March 9, 2015
One of the things always touted by the FAA regarding ADS-B is that we are supposed to receive TFR data via FIS-B from ADS-B. This is also cited on this web site as well. I've been flying with ADS-B in and out for over 2 years now (first the Skyguard send/recieve, then the Skyguard TWX), but I have never received TFR data via ADS-B. I live in an area that has frequent forest fires so often times have pop up TFRs. Why don't I ever get them from ADS-B? I only get TFR updates if I update my iFly GPS via WiFi, but never from ADS-B. Is this an issue from Skyguard? Or is this an issue with the FAA not providing the data via FIS-B?
I find that many times rather than seeing the "N" number displayed for another aircraft that is transmitting ADS-B out, I often times see either all zeros or the aircraft's ICAO number. This seems like it might be a data block issue with my unit as it is passing the data to my iFly GPS apparently in the incorrect block. This issue apparently started a year ago when I replaced my original Skyguard ADS-B unit with my current Skyguard TWX.
March 12, 2015
My guess is that if the TWX has not been updated to the latest software and has the wrong number set. The FAA agreed to use a different number so that Skyguard will still receive info. Read back topics for more details.
That is only my guess.
March 9, 2015
According to Don at the time, mine was one of the new units that already had the updated software as it was the version purchased for Experimental Aircraft in July 2015 I have verified (with the FAA that my unit has the appropriate SDA/SIL parameters. The FAA still replies to my unit with traffic, so it apparently does meet current requirements. I sent an email to Don yesterday, but assume he is still finding his way home from OSH or working a backlog from OSH week. Thanks for the reply.
I am curious as to whether others are receiving TFR updates via FIS-B on their ADS-B receivers, since I don't. The second issue is likely a data block issue I need to discuss with Don.
Thanks for the reply.
March 9, 2015
Heard back from Don on this.
Question #1: This is an issue with iFly development and should be addressed soon. Androids and iPads in the next release and the iFly units shortly after.
Question #2: We are still discussing, but essentially the receiver just passes along what it receives, so what I am seeing could be data getting scrambled anywhere along the line starting with other planes broadcasting from misconfigured ADS-B units, and there are a lot of them out there. In a multi-vendor environment starting with data from an anonymous source, the odds of figuring out the source of this very minor issue is likely to remain a mystery.
October 17, 2014
One of the "problems" with getting the correct "N" number and aircraft ID via ADSB-IN is that some manufacturers' units have a "stealth" mode which enters a "scrambled" fictitious registration and ICAO code so the FAA cannot identify the aircraft. From what has been reported to me (caveat emptor), this is not illegal as long as you are not using FAA services for separation of traffic. For example, flying strictly VFR and not talking to the FAA. But this is only scuttlebutt - I have never seen anything official from the FAA - however the FAA has "certified (TSO'd) these units with "stealth" mode capability. You could do the same thing with your Skyguard TWX by entering all zeros for your registration, etc. Not saying you should do that - just saying its possible to go "stealth" manually if YOU are so inclined. FWIW.
Most Users Ever Online: 19
Currently Browsing this Page:
Jim Logajan: 4
Guest Posters: 0
Newest Members:Manny, glen sullivan, Ben, Jim B, Swashplate, Bob, Joe, Dale_1, Dale, HenryLumma
Moderators: marsolgp: 0, leydsmanw: 0, Allensilberman: 0, Zane: 0, rshannon: 0, Brian_Neiman: 0, tmyers: 7, PAUL WESTCOTT: 0, jnmarshall: 8, rocpilot: 0, greghughes: 0
Administrators: Zane: 0, Don Houtz: 24