Falken Avionics Expands iPad-Based EFIS Lineup 

We have an updated version of the FlightBox Pro - also "v3" - which you can install in the Stinson. Because it's a re-design we're having to re-do the NORSEE approval, so it will be several months before it's available. An experimental version will be available in August.

Our map database - updated monthly and free for US users - includes airports, runways, frequencies, navigation aids, obstacles, special use airspace, and controlled (B, C, D) airspace. Our base maps include water (lakes, rivers, etc.), geographic boundaries, terrain hill-shading (at high zoom levels), and a full street map (hidden by default). Together the base maps and the database are used to populate a complete aeronautical vector map. Sectionals, IFR low and high raster charts, and other tile-based chart elements will be available from a third party partner in the near future.

@@falkenavionics5392 Thank you. I’ll be watching you for a future project then.

We are planning on selling both a connector kit and pre-made harnesses. The connector kit will include two DB9s (one for the power / CAN connector and one for the EMS) and a DB37 connector, mil-spec pins, and back-shells as well as three PEX quick connects for the Pitot, static, and AoA inputs. I'm estimating $55 for the kit, but that could change. The pre-built harnesses will be available in "stock" configuration and also custom. We're still working on the pricing for those.

There is a contact form on the "Contact Us" page: www.falkenavionics.com/contact/ as well as an email address.

Serious aviation app developers do invest in compatibility assurance. Besides Falken, ForeFlight, Garmin Pilot, major airline EFBs run on iPads.

@@KitplanesMagazine I manage 12,000 iPads at Southwest Airlines for Pilot EFBs and have done so since 2012. They have worked perfectly and Apple is VERY involved in EFB work to ensure the product works well.

We opted to use the iPad as the display platform for several reasons. EFB applications have made iPads almost a standard in the aviation space, so there's less of a learning curve. There are only three major form factors (mini, 10", and 12.9") to support. They are extremely well field-tested, with over 600,000,000 having been sold over the last 13 years. Yes, Apple can and does change the underlying platform, but we test each new iOS release and thus far (since 2019) we've only run into one breaking change, which was easily addressed. Compare that to our other option: source our own LCD panel, capacitive touch layer, drivers, and other low-level components to build a bespoke display in at what is low volume for the electronics industry. Pair that with a custom computer running Linux or perhaps the Android Open Source Project (AOSP). Layer on some kind of graphical "widget" layer (Qt or GTK). This kind of project is a major undertaking for a large company. It's well beyond what we could fund, and the resulting product would have been far less appealing that what we get by building on a well-established platform. If, at some point in the future, Apple decides to make changes that break our app or our business model we could and probably would pivot to another platform. For now, iOS is the best option for FlightView.

@@falkenavionics5392maybe I’m missing some relevant consideration but I think if I were using this as my avionics, I would not perform mainstream iPad firmware updates. Would only update if Falken recommended. Of course I’d keep these iPads off the internet.

@@KitplanesMagazine OK... how? Apple simple doesn't care sometimes. One example that comes to mind is DOD. Apple literally locked them out after an update, and there was thousands of dead pieces of hardware. I don't have a problem of software, as the developer... as long as they are supporting the hardware... they can continue to update the software.