Aircraft parts traceability means being able to follow a component's origin, use and maintenance through its records. GA Telesis proposes blockchain technology to help maintain that history, but a buyer still needs to establish who supplied the information and whether it belongs to the part being delivered.

For a quality manager choosing a system, the useful next step is a trial with real receiving questions. Can the team identify the issuer, detect an altered record, connect it to the physical part and resolve a missing answer? A platform description alone cannot answer those questions.

What GA Telesis has announced

GA Telesis provides aircraft parts and related maintenance, repair and overhaul services, often shortened to MRO. Its parts-traceability article was published on January 22, 2026 and updated on July 8. The company describes shared records, controlled access, document fingerprints and supplier checks. These are its proposed uses and expected benefits, not a regulatory requirement.

Its WILBUR platform predates that article. In July 2024, GA Telesis and Alitheon announced a partnership combining parts records with FeaturePrint, a system intended to identify physical items from images of their surface details.

In March 2026, GA Telesis announced WILBUR's public website. It described plans for summer 2026 beta testing, meaning trials before wider use, and anticipated broader adoption in 2027. That announcement does not establish that the trials finished or that their proposed benefits were achieved. No published trial results were identified in the company sources reviewed for this article on September 12.

Records and physical identity answer different questions

A blockchain is a shared record maintained across a network of computers. A document hash is a digital fingerprint calculated from a file. If the file changes, a comparison with a trusted earlier fingerprint can reveal the difference. Access to the record, corrections and the ability to inspect its history depend on the system's design. NIST's blockchain overview explains these distinctions and limitations.

That check does not establish that a document was truthful when entered. Nor does it identify the metal in the box. GA Telesis's proposed combination of records and optical identification addresses two separate questions: whether the record is unchanged, and whether the physical item matches its recorded identity. A buyer needs evidence for both.

Digital signatures and independently confirmed issuer records can also help verify documents. Supplier approval, inspection and the requirements for a specific installation still need attention, regardless of how the history is stored. The AOG Technics case gives a concrete example: checking with the real manufacturer helped uncover a false certificate.

The industry's recommendations leave the technology open

The Aviation Supply Chain Integrity Coalition's October 2024 report announcement recommends stronger supplier accreditation, meaning assessment against a defined supplier standard, alongside digital documents and signatures, receiving-inspector training, scrap control and information sharing. It explicitly allows different technologies to achieve these outcomes.

Its September 2025 update reports progress among respondents, including moves toward digital release certificates. It is evidence of work underway, not proof of universal adoption or a rule requiring a public blockchain.

The same care applies to cost claims. PwC's 2019 analysis projected potential annual MRO savings of about 5%, or $3.5 billion globally. That was a scenario for an industry, not a measured result for WILBUR or a forecast for your organization. GA Telesis's cited 5–10% range is broader than the original 5% estimate. It should not be treated as a harmless rounding or used as a guaranteed return.

A useful trial for a receiving team

Start with one document flow, such as accepting a used engine component's release certificate. That certificate describes its approved production or maintenance status. Agree with the supplier what evidence will be available and who will resolve an uncertain result. The following are proposed trial questions, not a certification scheme or an industry ranking:

  • Origin: can the receiver confirm the issuing organization and its authority for the document, using a channel independent of the broker?
  • Record: can the system distinguish an unchanged original, an altered copy and an authorized correction? Does a missing entry remain unresolved rather than become a claim that the part is counterfeit?
  • Part: can the team connect the record to the item's identifiers and physical inspection? If optical identification is proposed, test its limits on the kinds of parts the team actually receives.
  • Continuity: what can the team export, who can read it, and how will verification continue if the supplier's service is unavailable? Confirm how current status and access permissions are maintained.

In a fictional trial, the team receives an original release certificate, a copy with a changed serial number and a corrected version issued by the authorized shop. A useful system distinguishes all three and lets the reviewer trace the correction. If it merely returns an unexplained green badge, the team still lacks enough information to accept the records.

Measure the effort and unresolved cases during that trial, including integration, training and exception handling.

Make the purchasing requirement specific

Ask the supplier to show which records can be checked, by whom, with what dependencies and with what limits. Include the handling of personal and confidential information in that review. A hash-only design does not, by itself, establish compliance with every applicable privacy requirement.

The purchasing decision should follow the evidence from the trial and the team's obligations. For a closer look at what to retain, see our guide to exportable verification evidence. AeroCert's verification overview explains its document-focused approach.