A declaration from Online Aviation Library
Aviation is losing its memory.
Thousands of vintage aircraft still fly. Warbirds, trainers, liaison aircraft, classic airliners — airframes that survived wars, decades of neglect, and the slow erosion of time.
But the aircraft is only half the story.
The other half — the technical knowledge required to understand, maintain, and restore them — is disappearing faster than the machines themselves.
Today, critical information exists in fragments:
Scattered across ageing PDFs. Buried in handwritten maintenance logs. Locked inside the memory of mechanics who learned on these aircraft fifty years ago and are no longer here to ask. Undocumented modifications. Disconnected photographs. Obsolete manuals with no cross-reference, no index, no continuity.
The aircraft may survive. The knowledge often does not.
This is the problem we are choosing to address.
At Online Aviation Library, we have spent years assembling, digitizing, and distributing historical aviation documentation. Manuals. Blueprints. Technical orders. Engine overhaul instructions. Flight handbooks.
We know what exists. We also know what is missing.
And we have come to a conclusion:
Digitization alone is not enough.
Scanning a manual and selling it as a PDF preserves the document. It does not preserve the knowledge. The information remains static, disconnected, unsearchable, and impossible to build upon.
What vintage aviation needs is not an archive. It needs a technical memory.
What we mean by Computable Aviation Heritage
Inspired by modular data principles used in modern aerospace — standards such as S1000D and ATA chapter architecture — we are developing a methodology to transform historical aviation documentation into structured, navigable, machine-readable technical knowledge.
Not enterprise bureaucracy. Not a government programme.
Something modular. Scalable. Incremental. Built one aircraft at a time.
The goal is a digital technical twin of the aircraft's historical knowledge — a living environment where manuals, components, revisions, photographs, and maintenance history are linked, organized by system, and searchable across time.
Where the configuration history of an aircraft can be traced.
Where a future restorer inherits organized intelligence instead of a box of disconnected paper.
Where the knowledge becomes computable.
Why now. Why vintage aircraft.
Legacy aircraft offer a unique window of opportunity.
Their systems are understandable. Their documentation is finite. Their engineering logic is still visible. The people who worked on them are still — some of them — reachable.
Unlike modern aerospace platforms, vintage aircraft still allow complete system-level understanding by a small, dedicated team.
This makes them ideal candidates for structured heritage preservation before the window closes permanently.
What comes next
We are beginning with a single aircraft.
A proof of concept. A first structured archive. A demonstration that this methodology works at human scale, with real documentation, for a real machine.
We will share the process as we go.
If you own, restore, or care for a vintage aircraft — and you recognize this problem — we would like to hear from you.
The knowledge is still recoverable. But not indefinitely.
Online Aviation Library — onlineaviationlibrary.com
Technical documentation for aviation history, preservation, and research.
Step 2 — S1000D and the Vintage Aircraft Question
We are often asked: why not simply apply S1000D? It is, after all, the international standard. The answer is honest, and worth stating clearly.
S1000D — the international XML specification for technical publications — is theoretically applicable to any aircraft. And in mechanical terms, it works. But applying it to vintage aircraft and warbirds requires an honest evaluation of its practicality and real implementation costs. At OAL, we have done that evaluation. Here is what we found.
Where S1000D genuinely helps
- Asset Tracking & Reuse: S1000D breaks manuals down into granular, reusable Data Modules. If a warbird shares a common engine or hydraulic pump with a modern fleet, maintenance procedures for that specific component can be reused without rewriting the entire document. This is genuinely powerful — and it is the principle we are borrowing.
- Regulatory Traceability: It provides the strict governance and audit trail expected by aviation authorities such as the FAA and EASA — essential for any operator seeking continued airworthiness certification on a heritage type.
Where it breaks down for vintage fleets
- High Implementation Costs: S1000D relies on a Common Source Database (CSDB). Restructuring ageing, paper-based legacy manuals into S1000D-compliant XML is a massive and expensive undertaking — one that is simply not justified for most heritage operators working with finite budgets and finite fleets.
- Overkill for Low-Volume Operations: S1000D was designed to manage fleets of hundreds of complex military or commercial aircraft where parts are constantly modified and configurations diverge continuously. It is cost-effective at that scale. For a privately owned P-51 Mustang or Spitfire, it is over-engineered by an order of magnitude.
- Non-Standard & Obsolete Parts: Vintage warbirds frequently feature obsolete or custom-manufactured components with no surviving OEM support. S1000D is optimized for assets where every part carries a unique, trackable identification code. When that traceability chain is broken — as it almost always is with vintage types — the specification loses much of its structural value.
What the industry actually does
Many operators of mixed or historical fleets bypass S1000D entirely for older airframes. They rely instead on legacy standards such as ATA iSpec 2200, or they use documentation management software capable of handling multiple standards within a single system. Organizations managing heritage fleets should evaluate legacy data conversion services — companies such as ONEIL offer structured assessments of whether transitioning to an XML-based specification is justified by a fleet's long-term maintenance strategy.
The OAL position
We are not implementing S1000D. We are learning from it.
The modular logic. The data module concept. The principle that technical knowledge should be structured, reusable, and traceable — not locked inside a single monolithic document.
We are applying those principles at human scale, using tools and workflows that a small, dedicated team can actually sustain. The goal is not compliance with a specification. The goal is knowledge that survives.
S1000D asks: how do we manage technical publications at enterprise scale?
We ask: how do we preserve technical knowledge before it disappears entirely?
The questions are related. The answers are different.
Online Aviation Library — onlineaviationlibrary.com
Technical documentation for aviation history, preservation, and research.