The invisible passenger on every commercial flight is the maintenance plan. It decides when an aircraft leaves service, which hangar receives it, whether the right mechanics are on shift, and how many revenue-producing hours remain before the work begins. Get the sequence wrong and the airline does not merely rearrange colored blocks on a calendar. It can strand capacity, waste a maintenance slot, push labor into overtime, or retire useful time on an expensive part.
Aerostrat built its business inside that unglamorous knot. Founded in Seattle in 2015 by airline and software veterans Elliot Margul, Cody Morris, and Frankie Angai, the company makes Aerros, a long-range heavy-maintenance planning platform. Its users are not travelers. They are the strategic planners, engineers, finance teams, hangar operators, and outside maintenance providers charged with keeping fleets legal, available, and economically useful.
A scheduling problem with wings
An airline maintenance planner may look five years ahead. Each aircraft carries requirements with limits measured in dates, flight hours, or cycles. Hangars have finite bays. Vendors have contracts and capability limits. Labor changes by skill and shift. Demand rises and falls by season. Some tasks should be bundled to avoid opening the same airplane twice; others must happen before a deadline. Every answer moves something else.
One plan, six arguments
Aerros turns those arguments into a working schedule. Planners can drag events, run auto-schedulers, model unlimited scenarios, preserve restore points, and see the operational consequences of a changed constraint. Once a scenario becomes the plan, it can be published as a live, read-only production schedule so operators, leaders, and vendors look at the same version. Capacity tools break demand down by technician skill, day, and shift. Reports can flow to business-intelligence software. APIs and integrations connect the plan to the systems that already hold maintenance and operating data.
The company sells Aerros as enterprise software by quote; public list pricing and standalone revenue are not disclosed. The subscription is only part of what the customer buys. Aerostrat configures the environment, helps move data, connects identity and reporting systems, trains users, and assigns a customer-success manager. Its support model advertises around-the-clock help, regular customer meetings, and frequent releases. For a mission-critical planning tool, that service layer is not decorative. A clever schedule is useless if the planning desk cannot reach anyone when the source data changes on a Sunday.
That last point is the commercial wedge. Aerostrat does not insist on becoming the airline’s new system of record. Aerros works above the existing maintenance ERP, whether that ERP belongs to Trax or somebody else. It concentrates on the decision layer where generic software and spreadsheets lose their grip.
The product was pulled into shape
The useful origin story is not a pristine product emerging from a whiteboard. When two FedEx Express employees encountered Aerostrat at its first MRO Americas exhibit, Aerros was, by the later case study’s own account, closer to a shell than the product customers know now. The conversation became a multi-year project. FedEx asked the software to serve not only as a modern planning tool but also as an interface to multiple legacy systems and, eventually, to feed broader business simulations.
The first thing that failed was compatibility. FedEx’s older systems did not expose usable APIs, while Aerros had hundreds of services that did not speak the carrier’s particular dialect. The teams met repeatedly and built microservices on both sides. The result was a real-time connection: an operational change in the carrier’s system could appear in Aerros instead of waiting for another spreadsheet export.
This is a customer-development story without the usual romance. A large enterprise customer stretched the small vendor. Integrations consumed development time. The original product boundary moved. Yet that strain created expertise competitors could not pick up by adding an “aviation” landing page. Aerostrat learned which data has to move in real time, which constraints planners actually debate, and where an automated answer still needs a human hand.
The operating culture followed the same logic. Aerostrat describes itself as customer-obsessed, quick-moving, and transparent; the more concrete evidence is in its routines. Customers could discuss features directly with developers, request additions without a separate feature fee, and meet a dedicated success manager at least every two weeks. The company says it builds the product internally and updates it monthly. Those choices are expensive for a small team, and they can become chaotic without a strong product boundary. In a narrow vertical, however, the support conversation doubles as market research. A request about a shift calendar or vendor allocation can reveal a pattern shared by several carriers.
What changed JetBlue’s mind
JetBlue arrived by a more painful route. The airline had started a planning-software development project with another provider. Two years and many bugs later, the system crashed. Lost time became a purchasing criterion. JetBlue did not want another promise trapped in development, but it also did not want a rigid product based on repeating maintenance methods that no longer matched how its team planned.
Aerostrat occupied the working middle. Aerros was far enough beyond development to implement immediately, yet the team was willing to absorb JetBlue’s previous work and discuss where the process should go. Research began in 2019, the airline decided to implement in early 2020, and pandemic disruption turned the rollout into a stress test. JetBlue briefly ran schedules in parallel until it trusted the new dataset and process, then moved forward with a new schedule in 2021.
The lesson is sharper than “listen to customers.” A buyer burned by failed development does not necessarily retreat to the oldest incumbent. It may seek a product with proof of operation and proof of flexibility at the same time. Aerostrat sold both.
The $15 million handoff
AAR bought Aerostrat on August 11, 2025. The base price was $15 million, with $3.1 million placed in escrow for indemnification and closing adjustments. The agreement added contingent consideration valued at $5 million: $1 million depended on launching a specified product offering by the end of 2026, while as much as $4 million depended on adjusted revenue targets through August 1, 2028.
The structure makes the sale less of an ending than a three-year operating exam. AAR wanted Aerros to expand Trax, the maintenance ERP and mobile-software business it had acquired in 2023. The products meet at a logical seam: Aerros handles the long horizon and heavy-check plan; Trax handles broader maintenance records and execution. Aerros remains available separately across ERP platforms, an important condition because AAR later reported that roughly two-thirds of Aerostrat revenue came from non-Trax customers.
The scale has continued to move. Aerros supported more than 5,000 aircraft when the deal was announced. AAR’s 2026 investor presentation put the figure above 5,500 and said annual recurring revenue had grown roughly 60 percent since inception. Its annual report said more than 90 percent of major U.S. carriers used Aerostrat. Publicly identified customers over time include FedEx Express, JetBlue, Alaska Airlines, Azul, Endeavor Air, Hawaiian Airlines, Horizon Air, Republic Airways, SkyWest, Southwest, and Virgin Australia. Thai Airways later selected Aerostrat with Trax for a digital MRO program.
What to steal - and when it fails
The copyable part is not the auto-scheduler. It is the market posture. Pick a workflow where mistakes cost far more than software. Sit beside the system of record instead of demanding a rip-and-replace. Give the specialist user power to model alternatives, then publish a simpler view for everyone else. Treat integrations and support as product, not post-sale cleanup. Let demanding customers pull the roadmap, but preserve a repeatable core.
Own the decision layer
Connect fragmented operational data, model constraints, and turn the answer into a shared plan.
Sell the working middle
Be deployed enough to reduce risk and flexible enough to respect how the buyer actually works.
The data stays dirty
Optimization cannot rescue inconsistent requirements, missing capacity, or owners who will not maintain inputs.
The workflow is too simple
A small, stable fleet with few constraints may not justify enterprise implementation or integration work.
It also fails when a customer wants automation to replace judgment. Aerostrat’s own later discussion of artificial intelligence was cautious: confident but wrong outputs are dangerous in maintenance. The product’s value is not a magic answer. It is a faster way for experienced people to see the consequences of their choices.
That restraint explains where Aerostrat fits in the market. Full maintenance suites such as AMOS, IFS Maintenix, Ramco, Veryon, OASES, and Trax cover broad records and execution. Homegrown tools and Excel offer familiarity. Aerros claims the narrower territory between them: long-range heavy-maintenance planning detailed enough for experts, legible enough for stakeholders, and connected enough to leave the rest of the stack standing.
A traveler will never applaud a clean capacity chart. They notice only when the aircraft is not there. Aerostrat’s business was built on that asymmetry. It made the planning work visible to the people responsible for it - and kept the resulting problems invisible to everyone else.