Our story
Built by an engineer who lived inside the problem.
Twenty-five years of airworthiness directives, maintenance records, and regulatory compliance — managed in spreadsheets, legacy systems, and institutional memory. Aviagent exists because that gap never stopped bothering me.
The long way round
My career in aviation began in India, at Hindustan Aeronautics Limited — one of Asia's largest aerospace manufacturers — where I first met the complexity of keeping aircraft airworthy at industrial scale. From the hangar floor to the engineering office, I learned that airworthiness is not paperwork. It is the invisible infrastructure that keeps aircraft safe, and the people responsible for it carry that weight every day.
I went on to Pratt & Whitney and GE Aviation — two of the most demanding engineering environments in the industry — where I saw how the engine side of compliance worked: meticulous, unforgiving, and built on data that was never quite where you needed it. A missed AD on a CFM56 is not an administrative inconvenience. It is a grounding event, and a regulatory finding.
Later, at SAS, I sat on the other side of the table. I was the operator. I was the CAMO. And I used the same tools the rest of the industry relies on: systems that need a trained specialist just to run a query, and that still could not tell you with confidence whether a specific directive applied to one tail number in its exact modification state.
Why now
The tools available to CAMOs and MROs have not fundamentally changed in decades. The incumbent systems have accumulated features the way old aircraft accumulate modifications: layered, inconsistent, and expensive to maintain. They keep their customers because switching costs are high.
What changed is the economics of doing the work properly. Reading thousands of directives, extracting their effectivity, and cross-referencing it against live registries is now viable at a price that makes sense for a small helicopter operator, not only a flag carrier. That was not true a few years ago.
Aviagent is the product I wanted when I was running compliance at SAS. It is not trying to be everything to everyone. It does one thing: give CAMO engineers, accountable managers, and quality teams an honest, continuously updated view of which directives apply to their fleet — and the evidence to defend it.
Where we started
We began with the Nordic registries, because that is where we know the operators. Norway, Sweden, and Finland run some of the most demanding aviation environments anywhere: offshore helicopter operations to North Sea platforms, scheduled services in Arctic conditions, a regional sector where margins are thin and regulatory tolerance is zero. Luftfartstilsynet. Transportstyrelsen. Traficom. We built for them first, and it made the product sharper.
It did not keep it there. Directives are global: the same EASA and FAA ADs apply whether an aircraft sits in Oslo, Nairobi, or São Paulo. Aviagent now covers 101 national registries alongside the US registry, and where a registry is not yet supported, aircraft details are entered directly for the same applicability result.
What it does
The compliance evidence layer for continuing airworthiness.
Aviagent is not a spreadsheet replacement. It sits above your CAMO operation and keeps the regulatory picture current, sourced, and ready to defend.
Applicability, per tail
Each aircraft is resolved to its type, TCDS, serial and configuration, and every directive is evaluated against that actual state — with the reason recorded on both sides, including the ones that do not apply.
Deduplicated across authorities
Where two authorities mandate the same corrective action, the comply-once relationship is linked, so one action is not tracked twice under two references.
Evidence you can defend
Every determination carries its authority source and the date it was synchronised, so an audit question can be answered by showing the chain rather than reconstructing it.
What we believe
We build for the people who carry the risk
Aviation safety is a discipline practised by real engineers, accountable managers, and CAMO teams who carry legal and moral responsibility for the aircraft they oversee. We build for those people — not for procurement committees or demo days.
Honest uncertainty beats a false green tick
Compliance data should be transparent about its own limits. Aviagent shows when confidence in an applicability determination is high and when it is not, and documents where its coverage stops. We would rather show an honest unknown than a confident answer that leads to a finding.
The judgement stays with your team
Aviagent is the documentation and evidence layer above your CAMO operation, not a replacement for any role in it. Software does the cross-referencing; applicability decisions, compliance-method selection, and sign-off remain with qualified personnel. Under EASA Part-CAMO that is not merely our preference — it is how the responsibility is required to sit.
Airworthy. Documented. Transferable.
Three words, in order. An aircraft is airworthy because someone determined it to be. It is documented because that determination was recorded with its evidence. It is transferable because the record holds up when someone else — a buyer, a lessor, an authority — comes to check it.
Talk to the founder.
If you run a CAMO, an MRO, or a leased fleet and want to see what this looks like against your own aircraft, reach out directly.