When the aircraft is newer than its paperwork

Modification state lives in service cards, amendment logs and a register that stopped being reconciled three years ago. Here is how to make the tail number the source of truth.

The situation

An airworthiness directive arrives. It applies to a component fitted to some of your fleet, and the question that decides your week is simple to ask and brutal to answer: which tail numbers actually carry it right now.

The register says one thing. The service cards say another, because a modification was embodied during a deep maintenance visit and the register entry was never propagated. The amendment log records the change but not which airframes it reached. Nobody is being careless; the record is just distributed across three systems and forty years.

Why it is hard

The register is a summary, not evidence

A fleet register records what should be true. The service card records what a technician actually did on a given date to a given airframe. When they disagree, only one of them is evidence.

Modification state is per-airframe, not per-fleet

Two aircraft delivered in the same batch can diverge within a year. Planning against the fleet average is how an AD gets applied to the wrong airframes and missed on the right ones.

The paperwork outlives the system that made it

Records span scanned cards, typed amendment logs and whatever the current maintenance system holds. Any approach that only reads the current system is reading the smallest part of the record.

How we approach it

Agentix indexes the service cards, amendment logs and register together and resolves them to the airframe rather than to the document. Asking which tail numbers carry a component returns an answer with the specific card, log entry and register row behind each one, including where those sources disagree.

The disagreements are the valuable output. A reconciliation that quietly picks a winner is worse than useless in an airworthiness context, so conflicting evidence is surfaced as a conflict for an engineer to adjudicate, with both sources side by side.

What changes

The answer to "which airframes" is traceable to the card that proves it
Register and service-card conflicts surface as conflicts rather than being silently resolved
Directive applicability is assessed per tail number, not per fleet
The reconciliation runs air gapped, with two person sign off on each adjudication

Is this your problem too?

Bring the version of it you actually have. We will tell you what it would take, including when the answer is that it is not worth doing.

Discuss your use case About Agentix