Airspace bug report - iFly GPS for Android - iFly EFB

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...Airspace bug reportAirspace bug report
Previous
 
Next
New Post
1/25/2019 11:29 AM
 

Interesting; that's what I figured, source data problem.  I see the other nuclear security areas in WA and SC match the data to the sectional.  In Oak Ridge, 3000AGL seems appropriate as the ground elevation is around 1300, making 1700 above that a little low.

Too bad the DOD DAFIF data got locked up...I can dig out my final copy from 2007 and check the restricted airspace issue there, since it must be a longstanding restriction.  Just need to think of which old hard drive has it!

 

 
New Post
1/25/2019 12:35 PM
 

Delete.

 
New Post
1/28/2019 2:44 PM
 

Restricted 5601-G was declared around 2015, 2006 DAFIF doesn't have it.

Hope the issue that prevented database auto-assimilation can be fixed.  Hate to miss restricted space while flying in vector mode...of course we should familiarize ourselves with all pertinent data sources before flight, but sometimes things get hectic and better practices get lost in favor of the expedient ones!

 

 
New Post
1/28/2019 3:43 PM
 

That's why I never use vector mode.  I just don't trust it.

 
Previous
 
Next
HomeHomeDiscussionsDiscussionsiFly GPS for An...iFly GPS for An...Airspace bug reportAirspace bug report