The founders of Atmos Avionics first saw the need for a different kind of avionics company while doing Part 145 repair station work. Too many avionics systems were locked into closed ecosystems, feature unlocks, and upgrade packages, forcing aircraft owners, installers, and pilots to work around product-line limitations and added costs instead of choosing the equipment that best fit the aircraft.

So, we got to work.

Atmos began with a simple monochrome EFIS concept originally intended for ultralight and experimental aircraft. Dalton, Software Engineer, and Richard “Auto,” Hardware Engineer, (yep, that is the entire team for now) brought that early EFIS prototype to AEA, where another industry partner encouraged us to show it to Levil Aviation as a possible fit for their ecosystem.

That conversation helped redirect the project. Levil was interested in what we were building, but they also saw a more immediate need: an engine monitor. The question was asked.

Could we build an engine monitor?

That question became Draco.

Draco grew from the same idea that started Atmos: avionics should be flexible, practical, and capable of integrating with the systems pilots already use, without artificially locking features behind unnecessary barriers. Our relationship with Levil helped shape Draco into a full-featured engine monitor built around broad sensor compatibility, adaptable engine configurations, and real avionics integration from the start.