iFly GPS Forum

We have a new Forum!  Go here to get started: https://adventurepilot.community.forum.  
The new forum is easier to use and much more capable than the old, we hope you will join our community! 

Below is a copy of the old forum. This will remain available for a short period so you can access and review the information contained here. To continue a conversation, or start a new one, please register and create a post at our new forum location.
HomeHomeDiscussionsDiscussionsiFly GPS for An...iFly GPS for An...Late TFRLate TFR
Previous
 
Next
New Post
8/17/2018 6:37 PM
 

Today, while flying with my wingman I suggested we should take a different route back to our home airport. He said there is still a fire TFR on that route.

I did not see this on my tablet and we both have Samsung tablets that are WiFi only. I could see the Disneyland TFR which is always there, but not the large fire TFR.

I tried comparing all my alert settings with his and they all matched.

When we got to the airport we worked trying to get the TFR to show. I checked IFLY on my cell phone and it DID show the TFR. It is Internet available.

While in the air I updated NEXRAD and METAR/TAF via ADSB.

Finally, I made my cell phone a hot spot and let my tablet go to the WiFi from the phone and asked it to update via the Internet. It finally showed the TFR.

This could have been a bad situation if I couldn't see the TFR and flew into an active fire zone.

So my questions are:

Why didn't the ADSB update give the TFR info?

Why did I have to download from the Internet to get the TFR to show?

Probably something simple...right? 

John

 

 
New Post
8/17/2018 8:32 PM
 

John, thanks for posting.   I am not sure what went wrong today.   There is a way however to make iFly GPS capture the ADS-B raw GDL90 data so that I can replay the entire stream here at my desk, and find out if the TFR was missing from the data or if iFly simply failed to parse it, or present it.

Here is the method, for the next time you encounter something like this:

1. Select Menu => About => Connected Devices => Select Wireless Device => (scroll down) "Enable ADS-B Logger" (check the box) => Close .

Now all ADS-B data will be captured by iFly GPS.  Each time you restart iFly, it'll prompt you at startup to confirm if you want to keep this feature enabled or not -- just answer "Yes" to keep it enabled.

After duplicating the issue (i.e.. letting it run for a long time and no TFR shows up)... then shutdown iFly GPS and restart it.    Then select:

Menu => About => Send Bug Report => Select File => select the AdsbRaw.bin file with correct time stamp.

This'll send that file to me, where I can replay your entire ADS-B stream, and debug it.

 


Brian Knox, Sr Software Engineer
 
New Post
8/18/2018 8:19 AM
 

Brian

Thanks for the quick response. 

Roger WILCO on the suggestion for the next time the TFR doesn't show.

The strange part is that the permanent Disneyland TFR showed and most likely is now a permanent part of a printed chart.

It was lucky that my wingman could see the TFR so we didn't get in trouble as we merged with firefighting aircraft. 

John

 
New Post
8/18/2018 3:13 PM
 

Did flight service advise you of the TFR when you called them ?

 

 
New Post
8/18/2018 7:09 PM
 

I typically don't contact flight service when I fly 35 miles to breakfast.

 
Previous
 
Next
HomeHomeDiscussionsDiscussionsiFly GPS for An...iFly GPS for An...Late TFRLate TFR