How to build an air assets management system? Retroactive and seaworthiness management of high-value components
An audit. Broke the "Happy Bill" illusion.
During a supplemental regulatory audit last year, gaps were found in the repair histories of both main landing gear assemblies on an eight-year-old narrow-body aircraft. One could only be traced back to its third-level repair, with no earlier records. We had two weeks to fill the gaps or risk the aircraft's airworthiness status. We scraped through by looking up paper files more than a decade old. The lesson was clear: aviation asset management cannot rely on ordinary inventory software. It needs to link full lifecycle data for high-value parts with airworthiness compliance requirements.
High-value components are traced back to more than one serial number.
High-value components on board the aircraft typically include engines, APU (Auxiliary Power Devices), landing gear, back-up thrusters, IDG (General Driver Generators), TRAS (Turkish Revoltors), radar masks, etc. There are two common features: one is expensive, single APU overhaul costs between $200,000 and $500,000, and engine retrofitting costs millions at a time; and the second has almost a clear time frame for use, exceeding the mandatory repair or end of life.
The time limit is three types: flight hours (FH), number of rises and drops (FC), calendar duration. The life cycle of a landing gear may be traced to tens of thousands, and the calendar period for the engine LLP (Life-Limited Parts) will need to be overhauled.
What exactly does it do to trace the matter? Each key piece binds a single serial number (S/N), with a P/N + Serial + Installation Main Index. An electronic CV card is then built for each component, including: the date of departure from the plant, the first time on board, the cumulative FH/FC, the last time of repair, the maintenance release certificate number (CCAR-145 in Form 1, FAA in 8130-3, EASA in Form 1). These fields look basic, but many companies only keep their billings on the "loader/dismantling machine" level, and the bottom repair history is broken -- once the situation is up, the gap is exposed.
Airworthiness management can't stop at "How many accounts are installed."
The core of airworthiness management is whether the parts per unit are compliant at the current node. This involves at least three layers of logic:
The first level is the seaworthiness command (AD) matching. Each AD sets out the scope of application -- what type, what package number, what serial number range is in effect. To determine whether to implement the system automatically according to the current unit number + serial number, which step to implement, is closed or still OPEN. By hand, a paper-based AD list is matched, and it is inefficient and easily missed.
The second level is service announcement (SB) execution tracking. There may be hundreds of SBs on board a service aircraft, and each configuration change could affect the applicability of the successor maintenance program. The system must record whether the current configuration of each component - "SB-XXXX has been implemented to Rev.C" or "not implemented" - supports retrofitting.
The third level is the traceability of maintenance release. After each check or retrogression, the component return to the machine is supported by a corresponding release certificate. At the time of audit, the authority pushes from an active data to a release certificate and from the certificate to a specific maintenance worksheet. If either ring breaks, the whole chain does not work.
The system is built around a few canals.
The first is the spread of data sources. The shipping library, the airway maintenance hours, the workshop repair records, and the flight operation data are often in four or five different systems, which are reconciled manually once a month. In an earlier study, Shanghai-based Chosenway found that it took almost two months for an airline to simply standardize the main data on components in each system, with differences mainly being found in the name code custom and the coding rules.
The second hurdle is digitizing legacy records. Older aircraft often have more than a decade of paper records. To capture all of them, either enter each record manually or scan them and use optical character recognition (OCR). OCR accuracy is limited, and key part numbers and signatures still need manual verification. That work is hard to avoid.
The third is multi-machine matching. If the same company operates both Boeing and Airbus series, the D and SB matching logic is to build separate banks, which will double the volume. It will also take into account the technical information systems of different engine manufacturers, such as CFM, Roiro, which have a single package number system.
There is also a point that can easily be ignored: audit trails. In addition to checking the data themselves, the Bureau audits check how, who and whether the data were modified and whether there was an approval flow. This means that the system will have an internal change log from the first day on line, not after.
What step do we start with?
If a company is prepared to build the system from zero, it is recommended that it be pushed in the following order:
The list of high-value components is first cleared. The engines, APUs and landing gear sets, each number of which is in service, in storage, and under repair. This appears to be the basis, but only if there is a list can we talk about it retroactively.
The main data standard for the component is then created. The name of the item number, how the serial number was generated, how the unit was coded and how the data returned by the supplier was matched - a non-uniform set of standards followed by an arctic attic.
Step three, run the time-delivering warning. FH and FC data are taken from flight operating systems, and the loop count is accumulated from maintenance worksheets to early warning before the limit. This step is the fastest-to-see, and most likely to get support from business -- after all, a major delay is real money.
When we do this kind of project, we usually have three steps above as the first target, running the core data link, and then gradually folding AD/SB matching and configurations. The main reason for all the modules in one-off is often to see a lot of non-useable features on the part of the business community, which is losing patience.
Back to the reflection after the first audit: the value of air asset management is not so much how many statements there are in the system, but whether it can pull a full chain in seconds when the regulator, the maintenance party, or either side of the shipping company, asks what exactly this item has gone through. It's not broken in every part of the chain, and each breakpoint is a potential compliance risk. Think about how the system is built, with what rhythm, and it's natural to come out.

Ms. Lei
Mr. Pang