Shhhh! FlyQ EFB version 4.0 takes shape

Earlier today, I saw the first preliminary build of FlyQ EFB version 4.0.  Wow!  This is not just a new version.  Rather it’s an entirely new way to think about what an app aviation does.    The basic concept has been kicking around in my head for the past 2 years so it’s incredible to see it actually start to take shape.  Lots of work to go but the team is moving fast.  If you’re not already doing so, use the Follow feature of the blog system (right side of the page) to get notified about updates.

Like the Augmented Reality in FlyQ InSight and the Slingshot wireless data transfer system, we’re applying for a patent on it.  Unfortunately the patent isn’t done yet so I can’t say more but … wow is it great to see it materialize!  To be clear, version 4.0 is not just a new version with a feature or two 😉



13 thoughts on “Shhhh! FlyQ EFB version 4.0 takes shape

  1. Steve,

    I really think version 3.3 is FANTASTIC and personally I don’t see a need for more cool Gee Whiz stuff. Version 3.3 does everything I need it to do.

    I would prefer you guys fixing little issues that 3.3 might have instead. I think this is the best flight planning and flying app/EFB in the world, as it is.

    I agree with John above, “keep up the good work.”


    Liked by 1 person

    • Thanks Paul. As you probably noticed, we spend most of the last 3 release working on fixing bugs — large and small — and improving performance, battery life, and stability. In keeping, v 3.3.1 is being reviewed by Apple now and should be released by them this week. It includes:

      Version 3.3.1 (10/23/18)
      + FIXED: Problem downloading ChartData for some states
      + FIXED: Weather Gallery and Local/Regional/National radar does not load
      + FIXED: Two crashing bugs when downloading ChartData
      + FIXED: Navigational database does not function properly after a monthly update until the app is restarted.
      + FIXED: Crash when changing login email account

      Version 3.3 (10/12/18)
      + Animated radar
      + Substantially faster performance
      + 2X better battery life / lower device heat
      + Refinements to ADS-B traffic display
      + Minor fixes

      Version 3.2.1 (9/20/18)
      + ADS-B traffic tail numbers and detailed target info
      + Lots of bug fixes and stability improvements

      Version 3.2 (7/26/18)
      + Slingshot: Patent-pending wireless ChartData for in-panel systems like BendixKing xVue Touch
      + Appareo Stratus 3 support
      + Fix for Send to Avidyne
      + Fix for iOS 9 screen layout
      + Misc. fixes

      Version 3.1.1 (6/21/18)
      + Fix sporadic crash at startup with certain map layers
      + Fix weather briefings not refreshing for offline flight plans
      + Fix minor layout issue with METARs and TAFs
      + Fix problem where fuel stops were added in some cases even when not requested
      + Reduce memory pressure with the Grid layer

      Version 3.1 (5/31/18)
      + Tuned for iOS 11 and the iPhone X
      + Full Leidos support
      + Automatic fuel stop planning based on price
      + Shows recently cleared ATC routes for IFR flights
      + Restores Avidyne ADS-B and Flight Plan transfer features
      + Other flight planning improvements
      + Various fixes and improvements

      Version 3.0 (2/9/18)
      + iPhone version
      + Flight recorder
      + Augmented Reality
      + Helicopter and Gulf of Mexico charts
      + Maps and plates for Central America
      + Various fixes and improvements

      Liked by 1 person

  2. I would like to see W&B template added to new feature that we can customize for different planes (as many of us fly multiple rentals)! Thanks.


  3. Hi Steve:

    We are using FlyQ for IFR flights ………….

    Does Fly have capability that includes TEC Route planning between airports)?

    If not, do you see a FlyQ future improve IFR flight planning?

    Suggestions welcome…

    Keith Moore


  4. I wonder if it will have some sort of real time communications information, like indicating on the moving map whether or not a particular radio facility is within range. All of the data to determine that is already there, aircraft altitude, distance to the radio facility and elevation of any obstructions (e.g. the airport is on the other side of mountains or in a valley). For example, if a radio is in or out of range there is some indication on the map or in a list of radio frequencies for a facilities. That way I don’t waste time trying to call up the local weather (AWOS, etc.) at an en-route airport or trying to call an FBO at the destination when they aren’t in range. If they aren’t already planning that capability it would be nice to see it added.


    • I’m not sure why I’ve seen this question a few times — it’s been there for 6 months. When planning an IFR flight, the system asks Leidos what the recently cleared routes are. If one is a TEC route, you get a TEC route back. We do not try to do our own routing via TEC but I would think the actual Leidos routes are far more useful for such routing anyway.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s