FltPlan Go not displaying TFRs

[Cap'n Jack]

I noticed this in the morning, they still aren't displaying as of this evening. I know there are a couple in the NYC area which show up on the FAA web page (https://tfr.faa.gov/tfr3/?page=map ). I noticed an impending one in Omaha too. The RADAR is updating correctly. This is both the iPad and Android versions. I reported it to their Tech support.

I learned to look for this sort of information on multiple independent sites. Also, there are some "permanent" TFRs that can be used to see if this layer is working on EFBs such as Disney or the DC no-fly zone.

 

[Cap'n Jack]

Update:

Garmin (owners of FltPlan) got back to me and indicated there is an issue with displaying TFRs with this app and apparently their web page.

 

[Flyxaos]

I flew with it last week. The World Cup soccer TFR's were all there in their red glory. They weren't last night but are showing on the app this morning.

 

[Cap'n Jack]

I flew with it last week. The World Cup soccer TFR's were all there in their red glory. They weren't last night but are showing on the app this morning.

Thanks for the update. The FltPlan TFRs look like those on the FAA graphical site now, although they didn't as of my posting this AM.

I almost said they were still broken because I was expecting a big red TFR around NYC for game 3 of the NBA playoffs, but both the app and FAA are showing smaller TFRs, probably for stadiums.

 

[Clip4]

Update:

Garmin (owners of FltPlan) got back to me and indicated there is an issue with displaying TFRs with this app and apparently their web page.

Didn’t you already know there was an issue displaying TFRs with that app?

 

[Cap'n Jack]

Didn’t you already know there was an issue displaying TFRs with that app?

I knew there was a problem but I didn't know if it was user error, such as turning the TFR layer off, or turning the opacity to zero, rendering the TFR invisible, or if that feature in the app simply stopped working.

Tech support closed the loop, as they should have, and indicated that it wasn't a user problem. One can reasonably infer that it wasn't an issue with the installed apps on iOS or Android because they mentioned that their web site wasn't displaying the TFRs.

I posted what I knew so that other people using the app were aware of the problem, and also so those who use the app knew that the problem wasn't the installed software.