Narrative:

Using foreflight performance plus and a stratus 2S; after departing approaching the 60 mile ring of the dca VOR; the area between the 30NM sfra boundary and outer 60NM ring displayed as a tfr on my foreflight map shaded in a light red color. No notams were issued regarding a tfr in that area. While on the ground prior to departure; no tfr was displayed. Due to the zoom scale of the foreflight map approximately 5 to 8 miles and the light shading I did not notice it until the 60 mile ring appeared on my map display in a dark red color. Just prior to crossing the 60 mile ring the tfr disappeared from my foreflight map. After landing I telephoned TRACON to ensure that I did not violate any tfr airspace and was assured by the TRACON that there was no tfr violation. I also telephoned our club president who in turn reported the event to the FSDO. I was asked to contact another FSDO representative which I did. I explained the above description to him. He saw no violation and suggested that I file this report.after researching this issue I found that it is a known problem with the FAA's data broadcast from certain ads-B towers. Since foreflight does not overwrite or change any of the FAA data broadcasted it appeared on my foreflight map display as a tfr even though no tfr existed at any point that day. As I proceeded west I apparently began receiving data from different towers and the tfr disappeared from my map display. In hindsight I wish I would have taken a few screenshots of the towers that my stratus was receiving so that I could give a more detailed description of the possible problem towers. In the interest of flight safety; this was a very unpleasant distraction that could possibly divert a pilot's attention from safe operation of the aircraft. I believe the FAA data broadcasted through the ads-B towers needs to be evaluated and a solution to this issue found. I would think that all of the adb-B towers would be broadcasting the same data without erroneous data (i.e.; a non-existent tfr). This could possibly be a hardware/software issue.

Related reports:

Google
 

Original NASA ASRS Text

Title: A Pilot reported their Foreflight displayed a TFR when there was no TFR in effect and that this is a known problem related to FAA ADSB signals.

Narrative: Using ForeFlight Performance Plus and a Stratus 2S; after departing approaching the 60 mile ring of the DCA VOR; the area between the 30NM SFRA boundary and outer 60NM ring displayed as a TFR on my ForeFlight map shaded in a light red color. No NOTAMs were issued regarding a TFR in that area. While on the ground prior to departure; no TFR was displayed. Due to the zoom scale of the ForeFlight map approximately 5 to 8 miles and the light shading I did not notice it until the 60 mile ring appeared on my map display in a dark red color. Just prior to crossing the 60 mile ring the TFR disappeared from my ForeFlight map. After landing I telephoned TRACON to ensure that I did not violate any TFR airspace and was assured by the TRACON that there was no TFR violation. I also telephoned our Club President who in turn reported the event to the FSDO. I was asked to contact another FSDO representative which I did. I explained the above description to him. He saw no violation and suggested that I file this report.After researching this issue I found that it is a known problem with the FAA's data broadcast from certain ADS-B towers. Since ForeFlight does not overwrite or change any of the FAA data broadcasted it appeared on my ForeFlight map display as a TFR even though no TFR existed at any point that day. As I proceeded west I apparently began receiving data from different towers and the TFR disappeared from my map display. In hindsight I wish I would have taken a few screenshots of the towers that my Stratus was receiving so that I could give a more detailed description of the possible problem towers. In the interest of flight safety; this was a very unpleasant distraction that could possibly divert a pilot's attention from safe operation of the aircraft. I believe the FAA data broadcasted through the ADS-B towers needs to be evaluated and a solution to this issue found. I would think that all of the ADB-B towers would be broadcasting the same data without erroneous data (i.e.; a non-existent TFR). This could possibly be a hardware/software issue.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.