Aerospace Asset Identification: What a Tag Can’t Tell You

Between 2019 and 2023, a London-based supplier called AOG Technics sold over 60,000 aircraft engine parts accompanied by forged release certificates. The serial numbers on those parts were readable. The paperwork looked legitimate. The aerospace asset identification chain appeared intact. It wasn’t. The director received a four-year prison sentence in February 2026, following a GBP 39.3 million fraud. (See also: asset tracking dashboard.) (See also: asset tracking API.)

That case exposes what most identification programs quietly ignore: a readable tag is not a trusted identity. Whether you run MRO operations, manage airline supply chain quality, or oversee ground equipment across a dozen airports, identification only delivers value when it connects a physical mark to an authenticated, auditable record. Without that connection, the tag is decoration.

What follows maps the full territory: what aerospace asset identification covers, the technologies competing for it, the standards shaping it, and the operational gaps where money and safety disappear.

What Aerospace Asset Identification Actually Covers

Aerospace asset identification is the practice of assigning, marking, and maintaining unique identifiers on aircraft, components, ground equipment, drones, and spacecraft so each item can be traced through its operational life.

In practice, the term hides at least five distinct problems under one umbrella:

• Aircraft-level identity includes registration markings, broadcast addresses (ADS-B), and the documents tying an airframe to its operator.
• Component-level traceability covers serial numbers, Data Matrix codes, and RFID tags on parts that move between airframes, repair shops, and owners across years or decades.
• Ground support equipment (GSE) means tugs, belt loaders, ground power units, and service carts spread across airport ramps, often with no clear owner-operator visibility.
• Drone Remote ID is an in-flight broadcast of identification and position, required under FAA rules for unmanned aircraft operating in US airspace.
• Orbital object correlation involves matching a satellite or debris fragment to its observed track after launch, a problem that grows with every rideshare mission.

Each answers a different operational question. An MRO manager searching for a serialized turbine blade and an airport ops director locating a baggage tug are both doing “aerospace asset identification.” They share almost nothing in terms of regulation, technology, or stakes.

The common architecture across all five: identifier + physical carrier + observation + trusted record. Break any link in that chain, and identification degrades from knowledge to assumption.

The Identification Stack: Physical Marks to Connected IoT

US regulations under 14 CFR Part 45 require manufacturers to attach a secured, fireproof identification plate to each aircraft. Engines and propellers carry their own marking provisions. Critical parts need a unique serial number. Life-limited parts follow specific marking instructions or a documented exception. These physical marks predate every digital solution and remain legally required.

Digital identification builds on top of these physical foundations, not instead of them. Here’s how the layers compare:

The FAA issued operational guidance for onboard RFID through Advisory Circular 119-2A, which addresses ATA Spec 2000 Chapter 9 data standardization. A key provision: installed tags’ birth-record data should not be changeable by operators, although later maintenance information may need updating. The GS1 Global Individual Asset Identifier (GIAI) offers a separate framework, providing a structured key for individual vehicles, transport equipment, and spare parts designed for cross-organization interoperability.

For US defense procurement, the current DFARS clause covers delivered items with a unit acquisition cost of $5,000 or more, plus specified lower-value items and special equipment. The 2024 DoD IUID 2.0 instruction specifies manufacturer CAGE code, original part number, and serial number, with a central registry. Previously assigned identifiers continue without automatic remarking.

The pattern is cumulative. Digital methods supplement physical markings and regulatory records. They don’t replace them. And the stack keeps growing.

The Trust Gap That Tags Cannot Close

Here’s the uncomfortable reality I keep running into with aerospace clients: organizations invest in identification technology and stop at readability. If the scanner returns data, the job feels done.

AOG Technics proved otherwise. The UK Serious Fraud Office described altered genuine certificates and false documentation suggesting direct purchases from manufacturers including Safran. Parts entered the supply chain with correct-looking serial numbers and convincing release paperwork. Downstream operators had no reason to doubt what they scanned, because the scan confirmed exactly what the forged documents claimed.

FAA guidance on replacement parts is explicit about where responsibility sits. AC 20-62E addresses evidence of quality, eligibility, and traceability, placing the burden on installers to establish provenance, not simply accept what a label says. The Form 8130-3 FAQ states plainly that issuing the form does not constitute approval to install an article on a particular aircraft, engine, or propeller.

A tag tells you what something claims to be. A trusted record tells you what it actually is, where it’s been, who worked on it, and whether the custody chain holds up under scrutiny. The decision-ready test: can a technician move from this physical item to this authenticated history without an unexplained gap?

EASA’s VIRTUA project evaluated blockchain and virtualized EASA Form 1 histories, including certificate genuineness and revocation, during a 2022-2024 research period. That work could make post-issuance changes more visible. But no digital layer makes a forged original document genuine. The real defense is layered: issuer verification, procurement controls, matching identities across records, discrepancy investigation, and a clear escalation path for suspected unapproved parts.

Interoperability: The Problem That Scale Creates

Even when identification is legitimate, scale introduces its own failure mode.

Delta TechOps presented its RFID program with numbers that look like a success story: 312,000 tags flying across 876 aircraft, 38 stations including MRO, and 3,150 users. The program delivered real gains in work volume and labor-hour efficiency.

But the same presentation carried a striking admission: some A350 RFID tags could not be found, read, or used within the program. Tag read range, material interference, environmental conditions, and cross-system compatibility were persistent constraints.

That’s not a Delta-specific bug. It’s structural. When an airline tags a component, the tag needs to be readable by that airline’s own MRO provider, by any third-party shop that touches the part, and potentially by another operator that acquires the component years later. Different readers, different software, different data formats. A tag can be physically present and operationally invisible.

On the supplier side, Tego reports that Airbus launched its Flyable Parts program around 2009, using passive UHF RFID on components moving through manufacturing and maintenance. In Tego’s case study, inspecting seats and life vests at final assembly fell from 14 hours to 26 minutes. A Delta oxygen-canister inspection reportedly dropped from four-to-eight hours to under a minute. The mechanism is credible: batch-reading a known tagged population against required configurations. But these are vendor-reported examples, not independently verified industry averages.

The practical takeaway: test cross-operator reading and data formats with actual assets before fleet-wide rollout. Start with inspection-intensive, high-volume equipment where local labor savings can be validated. Build interoperability testing into procurement, not post-deployment troubleshooting.

Standards Shaping Identification Today

Aerospace identification standards are evolving, but they’re not converging into a single universal system. That distinction matters for every implementation decision you make.

Notice the pattern. Physical marking requirements, digital data standards, radio protocols, acquisition contract clauses, and experimental provenance research all address different pieces of the identification puzzle. The GS1 Gen2 standard defines how a reader talks to a tag. It says nothing about whether the part behind that tag has a valid release certificate. The DoD IUID defines what goes into a serialized identifier. It doesn’t govern civil airline maintenance records.

For your implementation, that means knowing which regulatory regime applies to your specific assets, operations, and contracts. An airline’s rotable components live under different rules than a defense contractor’s delivered hardware, which lives under different rules than an airport’s GSE fleet. Treating all three the same is how compliance gaps form.

From Identification to Full Lifecycle Tracking

This is where I see the biggest disconnect in the field.

Most organizations treat identification as a point-in-time event. Tag it, scan it, move on. But an aircraft component doesn’t sit still. It gets installed on one airframe, removed at a maintenance event, sent to a repair shop, returned, installed on a different aircraft, removed again, and eventually retired. Each transition is a point where identity can be confirmed or lost. Each gap in visibility is a gap in the asset’s value.

The economics behind that gap are not abstract. Oliver Wyman estimates $136 billion in global commercial MRO demand in 2025, up 8% from the previous year, with the in-service fleet projected to grow from roughly 30,000 aircraft in 2026 to over 41,000 by 2036. IATA puts 2025 supply-chain disruption costs above $11 billion, driven by a 17,000-plus order backlog, delivery shortfalls, and an average fleet age of 15.1 years. More aircraft staying in service longer means more parts cycling through more hands, with more consequential recordkeeping at every step.

This is the distinction I push with every client. Shipment tracking tells you where something is until delivery. Asset tracking follows it through the entire cycle: installation, removal, repair, return, reinstallation, retirement. The first answers “where is my package?” The second answers “what is the complete, auditable story of this asset?”

In aerospace, the second question determines whether a part can be installed, whether a fleet audit passes, and whether you’re buying a replacement you already own but can’t locate.

Connected IoT trackers bring a layer that labels and passive RFID alone cannot: continuous, real-time visibility that persists across organizational boundaries. When a rotable component leaves your MRO facility, do you know where it sits for 47 days before the next shop touches it? That dwell time is invisible without active tracking, and turning those continuous reads into insight is where asset tracking data analytics proves its value. Connecting tags to authenticated records across these boundaries is the core challenge of asset tracking integration. For production environments, aerospace production asset monitoring extends this visibility upstream to manufacturing and assembly operations. For airfreight-approved applications, hardware like the Thingfox T2 (DO-160 certified) delivers position and condition data without disrupting existing certification frameworks.

Ground support equipment presents its own economics. In Australia, one project connected 5,000 GSE assets across 12 airports to improve utilization and allocation. In the UK, one telematics provider reported a 91% increase in monitored GSE vehicles from the first half of 2025 to the first half of 2026, with median daily active hours per monitored vehicle up 75.5%. The success metric here is different from component traceability: fewer unlocated vehicles, better utilization, less unnecessary capital expenditure. An airworthiness certificate isn’t the controlling document for a baggage tug, but the operational dollar impact is just as real.

What to Validate Before You Commit

Whether you’re evaluating RFID tags for component traceability, IoT trackers for ground equipment, or a software platform for lifecycle records, five questions separate a working identification program from an expensive pilot that stalls:

1. Can the identity be read by someone else’s system? Delta’s A350 experience proved that a tagged fleet is not automatically an interoperable fleet. Test with actual third-party readers, shops, and data formats before scaling.
2. Does the record survive a change of hands? A component’s identity matters most when it moves between operators, shops, or owners. If your system only tracks what’s inside your four walls, the transitions between organizations are exactly where provenance breaks.
3. Who is the authoritative issuer, and can you confirm them? AOG Technics forged certificates from real manufacturers. Scanning a serial number that matches a document is not verification. Confirming that the document’s issuer actually issued it: that is.
4. What operational outcome will you measure? “We tagged everything” is not a result. Reduced search time per component, fewer duplicate purchases, faster audit closure, shorter MRO turnaround: those are results. Define the metric before deployment.
5. Does the hardware match the asset’s environment? A passive UHF tag on a cabin seat operates differently than a connected tracker on a ground power unit in desert heat. DO-160 certification matters for airfreight. IP67 ratings matter for ramp equipment. Match the technology to the conditions.

If your asset pool feels invisible once components leave your facility, or if your GSE fleet has equipment you know you own but cannot locate, that’s the gap lifecycle-aware asset tracking closes. We build end-to-end tracking solutions for exactly this problem, connecting the physical identity of an asset to a living, location-aware record that persists through every transition. A capable asset tracking platform turns scattered reads into a unified history. Learn how to create an asset tracking system that addresses these challenges, or reach out to our team to discuss your specific requirements.

Frequently Asked Questions

What does “aerospace asset identification” mean?

It covers assigning and maintaining unique identifiers on aircraft, serialized components, ground equipment, drones, and spacecraft. The term spans multiple regulatory regimes and technologies: physical markings under FAA Part 45, RFID under ATA Spec 2000, DoD IUID for defense items, Remote ID for drones, and catalog correlation for orbital objects. The right approach depends entirely on the asset type and the decision the identifier needs to support.

Does RFID make an aircraft part airworthy?

No. RFID improves the speed and reliability of identification and certain inspections. FAA guidance addresses its installation and operational use. But the FAA explicitly states that even Form 8130-3 does not by itself approve installation on a particular aircraft. Airworthiness requires the correct approved part, complete maintenance records, proper configuration, and qualified technical judgment.

What are the US requirements for marking defense assets?

Under DFARS 252.211-7003, delivered items valued at $5,000 or more (plus specified exceptions) require compliant 2D Data Matrix marking. The DoD’s 2024 IUID 2.0 instruction defines the identifier using manufacturer CAGE code, original part number, and serial number, maintained through a central registry. Check the specific contract and item category rather than applying the dollar threshold as the only test.

How is drone Remote ID different from ADS-B?

Both broadcast identity during flight, but they serve different aircraft populations. Drone Remote ID (under FAA Part 89) can be built into a drone or provided by an add-on module; certain drones can also fly without it inside FAA-recognized identification areas. ADS-B serves crewed aircraft surveillance, including through satellite-based receivers. Neither system addresses serialized part provenance.

Why can a satellite have an identifier yet remain “unidentified”?

The operator knows which satellite it launched, but ground surveillance systems tracking multiple similar objects released close together cannot always determine which observed orbit belongs to which spacecraft. NASA documents cases where this assignment takes weeks or months, and some objects are never uniquely matched. Pre-launch coordination, deployment separation, and identifying aids like radio beacons or optical reflectors reduce the ambiguity.

What should I ask an identification technology provider to demonstrate?

Ask for a successful read or observation on the actual asset in its real environment. Ask who the authoritative issuer of the identity is. Ask how changes, custody transfers, and exceptions are recorded. Ask for interoperability evidence with other operators’ systems. And ask for a measurable operational outcome, not just a tag count. Delta’s 312,000 tags and unreadable A350 hardware show why volume alone is not evidence of capability.