Comparison
ATA iSpec 2200 vs S1000D: What's Actually Different
The Short Answer
Documents vs a Database
ATA iSpec 2200 is a document-oriented specification: it defines maintenance manuals, illustrated parts catalogs, wiring data, and service bulletins as publications, organized by the ATA chapter numbering system the industry has used for decades. S1000D is database-oriented: content is authored once as data modules, held in a Common Source Database, and assembled into whatever publications a program owes — with configuration differences handled by a formal applicability model rather than by parallel documents.
Neither is “better” in the abstract. iSpec 2200 is what most operators' libraries, systems, and people are built around; S1000D is what new aircraft programs increasingly deliver. The practical question for most operations is not which one to choose — the fleet chooses for you — but how deliberately you run the years in which you have both.
Side by Side
The Structural Differences
| Dimension | ATA iSpec 2200 | S1000D |
|---|---|---|
| Unit of content | Manuals organized by ATA chapter, section, and subject — content lives inside a publication | The data module — a self-contained unit identified by a Data Module Code, independent of any publication |
| Source model | Document-oriented: the manual is the managed object | Database-oriented: all modules live in a Common Source Database (CSDB); publications are assemblies |
| Organizing scheme | The ATA chapter numbering system (21 Air Conditioning, 32 Landing Gear…) | The Standard Numbering System within the DMC — which, for civil aircraft, builds on the same ATA chapter logic |
| Configuration handling | Effectivity annotations within the content | A formal applicability model — content filtered by product configuration at publication or display time |
| Rule enforcement | Conformance checked editorially, against the specification text | Business rules can be captured in BREX and enforced by tooling at authoring time |
| Governance | Airlines for America (A4A) | ASD, AIA, and A4A jointly — with business rules layers (ATA Spec 1000BR, MIL-STD-3031) per industry |
| Where it dominates | In-service commercial fleets and their legacy libraries | New aircraft programs, defense, and coalition environments |
One continuity is worth underlining: the ATA chapter numbering outlives both specifications. S1000D's numbering for civil aircraft builds on the same chapter logic, and the chapters are embedded in maintenance planning, parts, and defect systems that no documentation migration touches. Moving specifications does not mean losing the map.
The Transition
Why Operators Run Both
The trigger is almost never a modernization initiative. It is an aircraft: a new type joins the fleet and its manufacturer delivers S1000D data, while every other type continues to revise its iSpec 2200 library. From that day the operation is running two specifications whether it planned to or not — two content models, two revision streams, and one workforce that has to work credibly in both.
The operations that handle this well make three decisions early. They keep a single delivery path, so a mechanic is not asked to care which specification a procedure was authored in. They keep revision control common, because proving which revision reached which person on which date is a continuing airworthiness obligation that does not pause for a migration. And they decide explicitly what happens to the legacy library — convert it, wrap it, or run it to fleet retirement — rather than letting the question drift. For the civil application of S1000D itself, ATA Spec 1000BR settles the choices that make airframer, supplier, and operator data actually interoperate.
When is conversion worth it? When the applicability machinery pays for itself — fleets with heavy configuration variation, content reused across types, or contractual delivery in S1000D. When is it not? A stable library on a mature fleet with a working toolchain is often best left where it is. We wrote more about the operational side of this in our aviation briefing.
FAQ
Questions We Hear
What is the difference between ATA iSpec 2200 and S1000D?
iSpec 2200 is a document-oriented specification: maintenance manuals, parts catalogs, and service bulletins organized by the ATA chapter numbering system. S1000D is database-oriented: content is authored as data modules held in a Common Source Database and assembled into publications, with a formal applicability model for configuration differences. iSpec 2200 dominates in-service commercial fleets; S1000D dominates new programs and defense.
Is S1000D replacing ATA iSpec 2200?
Slowly, and only at the front of the fleet. New aircraft increasingly arrive with S1000D data, but iSpec 2200 libraries remain in production on aircraft that will fly for decades, and the ATA chapter numbering both specifications lean on is embedded in maintenance planning and parts systems far beyond documentation. Replacement at the library level takes years; at the industry level, decades.
Can iSpec 2200 and S1000D coexist in one operation?
They usually have to. An operator taking delivery of a new type receives S1000D data while the rest of the fleet runs on iSpec 2200, and the realistic plan manages both streams deliberately — common delivery, common revision control, and a considered decision about what, if anything, gets converted.
How long does an iSpec 2200 to S1000D migration take?
The conversion itself is the smaller part. Agreeing the business rules, deciding the target issue, handling the exception structures in the legacy library, and standing up the CSDB and its workflow are what set the schedule — months for a scoped library with settled rules, years for a full operation. Migrating before those decisions are made is the expensive order of operations.
Get In Touch
Running Both?
Whether you are receiving your first S1000D delivery or deciding what to do with an iSpec 2200 library, the earliest conversation is the most valuable one.