.png)
Why No One Has Built a New Aviation MRO ERP in 20 Years
"If the systems are so bad, why hasn't anyone built a new one?"
Fair question. The existing aviation maintenance ERPs have been around for decades. The interfaces look like they were designed in the late '90s, because they were. The underlying architecture is old. IBM AS400, Oracle, Delphi. TCP connections. No APIs.
I once tried to build a mobile application on top of one of these systems and was told I had to use something called FireMonkey. Great name, I know.
It touches everything. Literally everything from operations and engineering to maintenance execution. I even had to learn accounting at one point because we were integrating with financial systems.
To rebuild this from scratch, you need someone who understands how all of those departments interact: How stores will bottleneck everything if the purchasing logic is wrong. How a work order moves from creation to execution to sign-off and what regulatory trail it has to leave behind.
You rarely find that person. I got there by accident.
Over 17 years, I did almost every one of those jobs. CAMO engineering. Aircraft transitions. Line maintenance.
I chose the small company over Airbus specifically because I didn't want to be an expert in one thing, I wanted to see the full picture. And at small companies, "not my department" isn't an option. Everything is your department.
So when people say, "why hasn't anyone built this?" I knew the answer before I started AirNxt.
It's too complex for most teams. It requires domain knowledge that takes a decade to build. The regulatory layer adds a dimension that pure software people don't know how to handle.
And the sales cycles in aviation are brutal: deals done on dinner tables, management overruling their own evaluation teams because someone knew someone. Now you’re months from where you started and nothing has changed.
A team evaluates five products, agrees one is the best fit, presents the recommendation, and management picks a different vendor. Because a deal was already done before the evaluation started. Then I'd watch the implementation fail.
That is the industry AirNxt is in.
Trust me. We’re not pretending it's easy.
It's the hardest thing I've ever done and I've reverse-engineered databases without documentation on a three-month deadline.
If it were simple, someone would have built it already and the problem would be solved.
I’m proud of how far our team has come. We still have a long way to go but our progress has been incredible.
The aviation maintenance industry deserves software that was designed for how people actually work, not software that was designed in 1998 and patched for 25 years.
The operators know it. The technicians know it. The engineers know it. We know it.
We’re ready to break the status quo...
If you want to find out more about the next-gen aviation software Mahmoud and his team are building, go to https://airnxt.ai





