iFly GPS Forum

I live in Colorado Springs but wanted to see the distance from the aiport in Kingman, Az to the airport in Mesa, AZ.   Using the Flight Planning button, I entered the two city airports (IGM, IWA).  I saved the flight plan and then went to the map screen.  On the upper right corner of the map screen, the Dist. Final box showed 474NM.  That did not seem correct so I pulled out an old WAC chart and it showed the distance to be just shy of 150NM. 

Can someone enlighten me as to what is going wrong, or what I am doing wrong??  Is there a configuration setting that I missed somewhere?  I looked in the User Manaul but nothing jumped out at me.

Thanks,

Steve

Thanks for your input.  I get the same result whether I am using my iPad or my desktop computer. There are only those two places in the flight plan.  Maybe since both devices connect to my wireless home network, it is getting the location and somehow incorporating that into the calculation.  Hopefully someone from Adventure Pilot can shed some light.

Steve

The distance-to-final instrument takes into account your current position, not just the points on your flight plan. 

If you are only interested in the distance covered by your flight plan, then open the FP and look at the total mileage indicated at the bottom of the plan.

That said, there does appear to be some sort of a bug in the distance-to-final instrument.  I performed this test and got (partially) unexpected results.  The DTF instrument only seems to update when I close iFly and re-open it.  Example:

1. I clear the flight plan and create a new one from T41 to DTN.  FP distance says 185nm.
2. I close the FP to return to the map screen.  Distance-to-Final (DTF) instrument reads a value in the thousands, corresponding to the flight plan I had loaded previously, which I deleted in favor of the T41-to-DTN plan.
3. I exit iFly and re-start it.  DTF now reads 191.5 nm, which is reasonable because I am at home, ~7 miles from the airport, and iFly is factoring in my current position when calculating DTF.
4. I open the FP page and insert ORD (Chicago O'Hare) as a waypoint between T41 and DTN.  FP page now says total route is 1446nm.
5. I close the FP to return to the map screen.  DTF instrument still reads 191.5nm, as it did before I added ORD to the FP.
6. I exit iFly and re-start it.  DTF now reads 1452nm (again, consistent with my current position at home vs. starting at T41).

I would have expected the DTF instrument to update immediately after I edited the FP, without having to exist/re-start iFly.  That behavior seems like a bug.

Edit:  I observed the above behavior performing those steps on my Win10 laptop last night.  This morning, I tried repeating those steps on my Android tablet, and while there was some delay between updating the FP and seeing the DTF instrument reflect the new distance when I returned to the map screen, it *did* update without me having to exit and restart iFly.  So the behavior is maybe not "perfect", but also maybe not "completely broken".