Skunkworks
Active Member
Sunday went out flying when suddenly the ADS-B rec?d information that there was an active TFR and it painted immeadiatly on my screen. As soon as I saw it I was looking around for the F-16 intercepting me because I was in the TFR when departing the airport. This did not look like a good situation, I turned to a tangent for quickest exit and landed at the closest airport to determine what was the status of this TFR I was totally unaware of. On Foreflight this was showing up in yellow as not active. I confirmed on the ground that in fact the TFR indicating being active was not, what a relief. The TFR in question is 5/3770 not due to be active until July 14, 2015 at 1630 UTC to July 14, 2015 at 2230 UTC
http://tfr.faa.gov/save_pages/detail_5_3770.html
Here is screen shot showing the incorrect status of the TFR 5/3770
I would expect this is a software bug in the FAA ADS-B system, have reported to Dynon Avionics and an FAA friend to get their take on this anomaly and where to report. This is a bad bug.
http://tfr.faa.gov/save_pages/detail_5_3770.html
Here is screen shot showing the incorrect status of the TFR 5/3770
I would expect this is a software bug in the FAA ADS-B system, have reported to Dynon Avionics and an FAA friend to get their take on this anomaly and where to report. This is a bad bug.