Timeline and Lessons Learned
It’s August, and that means it is time for another Atmos update!
This month, we’re covering Draco’s delivery timeline, new versions and configurations, changes coming to the website, and what we’re working on next.
First, let’s talk about Draco versions.
After returning from EAA AirVenture Oshkosh, we came home with a much clearer development vision and direction than we had before the show. Going into AirVenture, we thought, “Four- and six-cylinder engines are what we need to support.”
Wow, were we wrong—and that is a good thing. We enjoy being wrong when it helps us learn, improve, and build a better product.
So, what did we learn?
For starters, Draco has to—and will—support radial engines with up to nine cylinders using a single unit. Previously, a nine-cylinder installation would have required two Draco units because we did not realize how badly radial-engine pilots needed a reliable, full-featured engine monitor.
The standard Draco unit will now support up to nine cylinders. Customers will then be able to purchase the specific sensors they need or want through our website. More on that shortly.
Next up: Rotax engines equipped with an ECU.
This will likely become its own version of Draco. Because most of the engine information is already available digitally, this version can be smaller and will not require all of the analog sensor-input circuitry found in the standard Draco.
We would love to have this version available alongside the initial release, but we cannot promise that yet. We still need to dig into the details of the Rotax CAN bus and develop the software required to receive, interpret, and display that data.
That being said, if anyone knows someone at Rotax who may be interested in working with us, please reach out. The right technical support or documentation could greatly expedite the process.
Finally, we had a few people ask about more unusual applications, including jet engines and twin 18-cylinder engines like those found on aircraft such as the C-131.
We would absolutely love to build versions of Draco for those applications—because, honestly, that would be incredibly cool—but they are not part of the initial release timeline. Keep an eye out, but realistically, we would not expect those versions for at least a couple of years.
Website Changes
Currently, when purchasing Draco and its sensors through our website—and please do, that would be amazing—you are presented with three primary configurations and several additional options.
As described above, Draco’s mission is to support a wide variety of engine and sensor configurations. The way the online store is currently organized no longer aligns very well with that mission.
Here is the new plan:
Draco will be sold as a standalone unit capable of supporting engines with up to nine cylinders. We will then provide a detailed information page explaining which sensors and accessories are needed for customers starting with no existing sensors.
You will still be able to purchase all compatible sensors directly through us.
Purchasing sensors through Atmos guarantees that they have been tested and verified to work with Draco. Draco supports a broad range of sensor types, and we have yet to encounter one that cannot be made compatible. However, that does not mean incompatible sensors are not somewhere out there in the wild.
The new information page will include recommended sensor “packages” containing everything needed to get the most out of Draco. These packages will be divided into common four-, six-, seven-, and nine-cylinder configurations to make browsing and planning an installation easier.
Delivery Timeline
Our current roadmap remains on schedule.
Customers who place their orders by August 31, 2026, will be included in the first shipment wave beginning December 1, 2026.
After that initial shipment, we intend to keep Draco units in stock so customers ordering after December 1 should not experience a significant lead time. Orders placed after August 31 will be fulfilled in the order they are received, following the first December shipment wave.
What Comes Next?
For everyone who visited our booth at AirVenture: first, thank you. Second, we received an incredible amount of useful feedback from all of you, and that feedback has helped us realign some of our priorities following the Draco 1.0 release.
One request we heard repeatedly was for a dedicated, panel-mounted display. Some pilots prefer a permanent in-panel screen rather than using an iPad or Android device with the iFly EFB or Levil Aviation apps.
Roger that. A dedicated Draco display is now next on the list.
A dedicated display will also make future certification efforts easier, so this was always part of the long-term plan. Your feedback simply moved it much higher on our priority list.
However, this does not mean—and will never mean—that you must purchase an Atmos display for Draco to work. If you already fly with an iLevil or iFly EFB and don’t want a separate display, awesome keep doing that.
We greatly value our relationships with our industry partners, and we have no intention of creating a closed ecosystem like those found elsewhere in the industry. During AirVenture, we made more industry connections than we can count. We are simply waiting for everyone’s blessing before announcing anything, so keep your eyes peeled for more news soon.
As always, if you have any questions, comments, or concerns, please feel free to reach out and email me directly.
Thanks, everyone!
Dalton
Co-founder and Software Engineer
