iFly GPS Forum

This is another time a screenshot would be really helpful.  Any chance you could take a photo with your phone and post it here?

I don't usually have wind barbs on my map screen.  Actually, I couldn't find a setting that would show them except for "Show hi-res winds", which doesn't tie the wind barbs to specific airports.  I normally look at wind information by tapping the airport to bring up its QuickView pop up.  In that initial QV popup, iFly will present the preferred runway with a wind direction arrow overlaid on it.  From there you can tap the "Airport info" button, and in the resulting screen you'll get a North-up drawing of the runways with a wind barb.

When I tried looking at KWRI and KDOV on my Android tablet, iFly reported "No Metars on This Field" in their Airport Info screens.  However, I don't know why it says that, since they clearly do exist: 
KWRI METAR
KDOV METAR

Hmm.  I see some definite funny business going on here when I try to duplicate this on my 720:

- When I try to tap on KWRI to bring up the airport QuickView, I have to zoom in pretty tight before that works.  (This may just be a quirk of the 720; I don't really use it any more so am not so familiar with its normal behavior.)
- When I do successfully tap on KWRI and bring up its QuickView, if I tap on its WX tab, I don't get WRI weather, I get KVAY weather.  (NOTE:  When I do the same thing on my Android tablet, I get KNEL weather!)
- Now that you've pointed it out, I do see a color dot for the WRI weather just offshore, near the Lat/Lon 40/74 intersection.  If I tap that dot, I get the KWRI weather QuickView popup (same behavior on both the 720 and my Android tablet).  And if I then tap the APT tab on that QV window, I get JY35 ("Allen's", a seabase) and the QV circle jumps.about 3 nm to the WNW of the color dot, but there is nothing identified as an airport on the sectional in that location.  (Skyvector.com jumps to that same spot when you enter JY35, though, so maybe that's the correct location for it and it's just unmarked.)

So that sounds to me like a bug, or else some sort of FAA data integrity error that's leading to bad iFly behavior.  No way for a user to tell the difference.

...@Brolin?