Cobra wrote:
FWIW, this has come up beforeI, and I will mention again that I think it's a bad idea for iFly to try to guess whether someone is flying VFR or IFR based on how the pilot is using iFly.
I have seen previous suggestions that iFly behave differently if an IFR flight plan was filed, or now based on what map mode the software is in. I don't think those are good ways to determine whether a pilot is flying IFR or VFR. I don't think there's *any* good way for iFly to detect whether it's being used for IFR or VFR flight.
Nearly 100% of my flights are IFR. I never use iFly to file my flight plan, and I also often have the map in sectional mode, since I'm often in VMC and use the map markings to cross check my location.
I don't know how common that is, but that's still a use case that iFly would fail if it tried to guess IFR vs. VFR.
Common enough. I do it and discussion with other pilots indicates many do it, regardless of which EFB hey are using. It's actually one of the great advantages of EFBs - being able to easily change the map used on the fly.
There are three safety issues with IFR "minimums" callouts. One is "minimums" not actually being the minimums due to differences in baro altitude and GPS altitude. The second is that iFly is not really equipped to know which minimums you are flying to on a particular approach. There are multiple choices. On an RNAV (GPS) approach for example, you've got LNAV, LNAV/VNAV, LP or LPV straight in and circling. Then add to that whether you are flying Category A, B, etc speeds which might change those as well. The third is integrity. Out certified panel mounts has all sorts of ways to tell us when they can't be relied on. An EFB might have some, but its not subjet to the same stanards.