TFR updates

[Seagull]

How does the Dynon panel receive TFR updates?
We had a fire TFR locally (4 mi radius), it was updated to a smaller (3 mi radius) last night. The change showed up on my EFB. This morning the TFR was removed and the EFB showed that it was removed, but the Dynon still showed the 4 mi radius, I flew for an hour and the Dynon never updated.

 

[Rhino]

They come over ADS-B In. Maybe the FAA is slow to update.

 

[Rhino]

I suppose it depends on your definition, but those aren't what I would call long-standing. The NOTAMs for them are expiring and being re-issued every few days. Foreflight gets TFRs from a different source than Skyview, so it does beg questions about update cycles or data filtering that could account for the difference in displayed information. Skyview does not process or display all NOTAMS. For instance, it does not process NOTAM-D data. It does process TFRs though, so there may be some sort of filtering involved that dictates what will be displayed, or when. But since Skyview gets all this from FIS-B data, and FIS-B is not considered an "official" source for NOTAMs by the FAA, I suspect this is something not going out over FIS-B in a timely manner. Probably only Dynon could give a definitive answer here.

 

[Rhino]

That brings up another interesting question. Seagull, do you have the 470 or 472 ADS-B receiver?

 

[swatson999]

That brings up another interesting question. Seagull, do you have the 470 or 470 ADS-B receiver?

I think you mean "470 or 472".

 

[Rhino]

I think you mean "470 or 472".

Yeah. Dang keyboard! LOL! That's my story and I'm sticking to it.

 

[Seagull]

I have the 472.
The TFR was taken down over a week ago. It still shows on my Dynon. I have flown 4 hours over the past 2 days, one would think it would have updated by now.
I also have a Garmin 696 with a GDL39 that is still showing the TFR.
My Ipad using IFly GPS does not show it. The TFR is 2/2508.

 

[Rhino]

The 696 gets NOTAMs over FIS-B, and I believe iFly gets them over the internet. If that's the case, this appears, at least on the face, to be more evidence for my guess the FAA just isn't updating the FIS-B data in a timely manner. However, there could also be an issue of data latency in the cockpit. The systems displaying the data might simply be caching it in memory after the FIS-B broadcast is no longer including it. That would presumably continue to display the TFRs until the cache resets. That's something Dynon and/or Garmin would have to answer.