ATA Spec2300 2017.1 FINAL

ATA Spec 2300
Data Exchange Standard for
2300 Flight Operations

Revision 2017.1
Use of this document is subject to the warranty provisions and license agreement contained on pages i, ii, and iii.
PRODUCT LICENSE AGREEMENT
AIR TRANSPORT ASSOCIATION OF AMERICA, INC. ("ATA") PRODUCT LICENSE

AGREEMENT
IMPORTANT -- PLEASE READ THIS ENTIRE AGREEMENT CAREFULLY
BEFORE USING THIS DOCUMENT
YOU AGREE TO BE BOUND BY THE TERMS OF, AND BECOME PARTY TO, THIS AGREEMENT. THIS
AGREEMENT IS APPLICABLE TO THE ACCOMPANYING MERCHANDISE (THE "MERCHANDISE"),
THE INFORMATION RESIDING THEREON OR ON INTERNET WEB SITES ACCESSIBLE EXCLUSIVELY
VIA LINKS FROM THE MERCHANDISE (THE "CONTENT") AND THE RELATED SOFTWARE
(COLLECTIVELY, THE "LICENSED PRODUCT"). IF YOU DO NOT AGREE TO BE BOUND BY THE
TERMS OF AND BECOME PARTY TO, THIS AGREEMENT, YOU CANNOT USE ANY PART OF THIS
DOCUMENT AND CANNOT SHARE IT WITH OR FORWARD IT TO ANY OTHER PERSON OR ENTITY.
IMPORTANT INFORMATION
The Licensed Product contains specifications, practices and other information relating to the covered topics. ATA
does not mandate the use of all or any part of the Licensed Product and your decision to use the Licensed Product
is entirely voluntary, your decision and at your own risk. You may choose to use the Content in whole, in part, or
not at all.
There may be practices, standards and/or governmental requirements applicable to your operations that exceed, or
vary from, the Licensed Product. You are solely responsible for determining if such practices, standards or
regulatory requirements exist and whether they apply to your activities, and for complying with those that are
applicable. Such practices, standards and regulatory requirements can change significantly over time. Unless ATA
expressly states otherwise in writing, nothing in this Agreement shall be interpreted as requiring ATA to provide
you with updates, revisions, or information about any development or action affecting the Licensed Product.
The Licensed Product has been compiled by ATA and/or its licensors. ATA and/or its licensors reserve title to
and ownership of the Licensed Product and all copyrights and any other intellectual property rights in it.
DESCRIPTION OF LICENSE
Upon your acceptance of this Agreement, you will be permitted to access the information for which you have
obtained the license described and limited below.
The extent of permissible access to the Licensed Product to you and within your company depends on the type of
Licensed Product that ATA has provided to you. Access is as follows:
1. If you purchased the Licensed Product for individual use ("single-user"), access to the Licensed Product
shall be limited to employees in your company, not to any third parties, and only one concurrent user.
2. If you purchased the Licensed Product for multiple person use ("multi-user") or you are a member of the
ATA E-Business Program, you can allow access to the Licensed Product to employees within your
company, not to any third parties, and have multiple concurrent users. Such employees shall be bound by
all the provisions of this Agreement.
3. Single user and multi-user employees may use the Licensed Product for the internal business purposes of
your company, and each may print a single copy of any Licensed Product for purposes of designing,
structuring or modifying any of your company's products or services as authorized below.
The license that this Agreement provides you is subject to any applicable payment and is non-exclusive, non-
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page i
transferable and worldwide. ATA can terminate this license if you materially fail to comply with the terms of this
Agreement.
This Agreement does not authorize you to, and you shall not:
1. Alter, modify, translate, adapt or create derivative works based on the Licensed Product or any related
software. Notwithstanding the foregoing prohibition, you may include or apply elements of the Licensed
Product in a work that you exclusively produce.
2. Use the Licensed Product on any unsecured network or permit any third party to access or use the Licensed
Product except as expressly permitted in this Agreement or in a separate agreement.
3. Use the Licensed Product or any part thereof in any manner that infringes the intellectual property or other
rights of another entity or person, including ATA.
4. Sublicense or assign this Agreement.
5. Indicate that ATA endorses, approves, or certifies your application of the Licensed Product, including,
without limiting the generality of the foregoing prohibition, your use of specifications contained in the
Licensed Product.
ATA CREDIT
If the Licensed Product is used to design, structure or modify any of your or your company's products or services,
you must reference, in a commercially reasonable location, the fact that the Licensed Product has been so used.
LIMITED WARRANTY
ATA warrants that at the time of delivery, THE LICENSED PRODUCT will be free from defects in materials and
workmanship. In the event of a breach of the foregoing warranty, as your sole and exclusive remedy and ATA's
sole liability, ATA will replace any LICENSED PRODUCT having defects in materials or workmanship at no
charge, provided you inform ATA within 30 days after your receipt of the Product.
WARRANTY DISCLAIMER
EXCEPT AS EXPRESSLY STATED ABOVE, THE LICENSED PRODUCT IS PROVIDED "AS IS" AND ATA
HEREBY EXPRESSLY DISCLAIMS, ON BEHALF OF ITSELF AND ALL PERSONS WHO CONTRIBUTED
TO THE CREATION, PUBLICATION, REVISION AND/OR MAINTENANCE OF THE LICENSED
PRODUCT, ALL OTHER WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-
INFRINGEMENT. NEITHER ATA NOR ANY PERSON WHO CONTRIBUTED TO THE CREATION,
PUBLICATION, REVISION OR MAINTENANCE OF THE LICENSED PRODUCT WARRANTS THAT THE
LICENSED PRODUCT WILL MEET YOUR REQUIREMENTS, THAT THE OPERATION OF THE
LICENSED PRODUCT WILL BE ERROR FREE, OR THAT IT IS ACCURATE, COMPLETE, CURRENT OR
RELIABLE.
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page ii
LIMITATION OF LIABILITY
IN NO EVENT WILL ATA OR ANY PERSON WHO CONTRIBUTED TO THE CREATION, PUBLICATION,
REVISION, OR MAINTENANCE OF THE LICENSED PRODUCT BE LIABLE FOR INDIRECT, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE, OR THE INABILITY TO
USE, THE LICENSED PRODUCT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES;
WITHOUT LIMITING THE GENERALITY OF THE FOREGOING LIMITATIONS OF LIABILITY, NEITHER
ATA NOR ANY PERSON WHO CONTRIBUTED TO THE CREATION, PUBLICATION, REVISION, OR
MAINTENANCE OF THE LICENSED PRODUCT IS RESPONSIBLE FOR LOST PROFITS OR REVENUE,
LOSS OF THE USE OF THE LICENSED PRODUCT, LOSS OF DATA, OR THE COST OF ANY SUBSTITUTE
PRODUCT. IN NO CASE SHALL THE AGGREGATE LIABILITY OF ATA AND ALL PERSONS WHO
CONTRIBUTED TO THE CREATION, PUBLICATION, REVISION, OR MAINTENANCE OF THE LICENSED
PRODUCT EXCEED EITHER (1) THE AMOUNT OF THE ANNUAL E-BUSINESS PROGRAM
MEMBERSHIP FEE YOU PAID FOR THE YEAR IN WHICH SUCH LIABILITY AROSE, IF YOU ARE AN E-
BUSINESS PROGRAM MEMBER, OR, IF YOU ARE NOT SUCH A MEMBER, (2) THE PRICE YOU PAID TO
PURCHASE THE LICENSED PRODUCT FROM ATA. IN ADDITION, THE THIRD-PARTY PUBLISHER OF
THE LICENSED PRODUCT WILL NOT BE LIABLE FOR ANY DAMAGE OR LOSS OF ANY KIND
ARISING OUT OF OR RESULTING FROM YOUR POSSESSION OR USE OF THE LICENSED PRODUCT
(INCLUDING DATA LOSS OR CORRUPTION), REGARDLESS OF WHETHER SUCH LIABILITY IS BASED
IN TORT, CONTRACT OR OTHERWISE.
This Agreement shall be governed in its interpretation and enforcement by the laws of the District of
Columbia, without regard to its choice of law principles.
This is the entire agreement between the parties about the subject matter of this Agreement. Any change to this
Agreement must be in writing and agreed to by both parties.
Comments about or suggested changes to the Licensed Product should be sent to:
ATA e-Business Department Air Transport Association of America, Inc. 1275 Pennsylvania Avenue, NW, Suite
1300 Washington, DC 20004-1707 USA
Or
admin@ataebiz.org
YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT, UNDERSTAND IT AND AGREE TO
IT, AND THAT YOU HAVE THE AUTHORITY TO AGREE TO IT ON BEHALF OF YOUR COMPANY. IF
YOU DO NOT AGREE TO BE BOUND BY THE TERMS OF, AND BECOME PARTY TO THIS AGREEMENT,
YOU CANNOT USE ANY PART OF THIS DOCUMENT AND CANNOT SHARE IT WITH OR FORWARD IT
TO ANY OTHER PERSON OR ENTITY.
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page iii
Table of Contents
Chapter 1. INTRODUCTION .................................................................................................. 1
1-1. Purpose............................................................................................................................ 1
1-2. Intended Audience .......................................................................................................... 1
1-3. Scope Of This Document ................................................................................................ 2
1-4. Anticipated Benefits........................................................................................................ 3
1-4-1. Standardization ....................................................................................................... 3
1-4-2. Use of Structured Information ................................................................................ 3
1-4-3. Additional Benefits ................................................................................................. 4
1-5. XML Implementation ..................................................................................................... 4
1-6. Flight Operations Markup Language .............................................................................. 5
1-6-1. General .................................................................................................................... 5
1-6-2. Schemas .................................................................................................................. 5
1-6-3. Sample Data ............................................................................................................ 6
1-7. Tailoring Spec 2300 for a Specific Project ..................................................................... 6
Chapter 2. DATA MODULE MANAGEMENT ..................................................................... 7
2-1. Data Management Concepts ........................................................................................... 7
2-2. Data module types........................................................................................................... 7
2-3. Data Module Identification ............................................................................................. 8
2-3-1. Data Module Code .................................................................................................. 8
1. Data Module Code Structure .................................................................................... 10
2-3-2. Language ............................................................................................................... 13
2-3-3. Data module code extension ................................................................................. 13
2-3-4. Issue information .................................................................................................. 14
2-4. Temporary Data Modules ............................................................................................. 14
2-5. Data module content and metadata organization .......................................................... 14
2-5-1. Data module global content .................................................................................. 14
2-5-2. Content fragment .................................................................................................. 15
2-5-3. Metadata: DM Status fragment ............................................................................. 15
1. DM Status Schema Mapping .................................................................................... 16
2-5-4. DM Status and DM Content association ............................................................... 16
2-5-5. Addressing mechanism ......................................................................................... 16
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page iv
1. Path to Nodes ............................................................................................................ 16
2. Contexts .................................................................................................................... 17
2-5-6. Extended path for part of content.......................................................................... 18
Chapter 3. FLIGHT OPERATIONS INFORMATION ......................................................... 19
3-1. Introduction ................................................................................................................... 19
3-2. General Structures ......................................................................................................... 19
3-2-1. Information Layers................................................................................................ 19
3-2-2. Phase of Flight ...................................................................................................... 20
3-2-3. Crew qualification ................................................................................................. 20
3-2-4. Policy references ................................................................................................... 20
3-2-5. Data owner ............................................................................................................ 21
3-2-6. References Management ....................................................................................... 21
1. General ...................................................................................................................... 21
2. Data Module Reference ............................................................................................ 21
3. Internal Reference ..................................................................................................... 21
4. External Reference .................................................................................................... 22
5. External Application Reference ................................................................................ 22
3-3. Data Management ......................................................................................................... 22
3-3-1. Applicability management .................................................................................... 22
1. General ...................................................................................................................... 22
2. Cross reference tables ............................................................................................... 23
3. Applicability annotations and formula...................................................................... 27
3-3-2. Revision Management .......................................................................................... 31
1. General ...................................................................................................................... 31
2. Revision data............................................................................................................. 31
3-3-3. Container and Alternate Data Modules................................................................. 40
3-3-4. Information Repositories ...................................................................................... 44
1. General ...................................................................................................................... 45
2. Repository types........................................................................................................ 45
3. Repository Schema Mapping .................................................................................... 46
4. Repository Mechanism ............................................................................................. 46
3-3-5. Software Parameters ............................................................................................. 50
3-3-6. Additional Parameters ........................................................................................... 52
3-4. Flight Operations Technical Content ............................................................................ 52
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page v
3-4-1. Common Data ....................................................................................................... 52
1. General ...................................................................................................................... 52
2. Content Guidelines.................................................................................................... 53
3-4-2. Approval Data ....................................................................................................... 53
1. General ...................................................................................................................... 53
2. Approval Data Modules ............................................................................................ 53
3. Approval DM and Schema Mapping ........................................................................ 54
3-4-3. Dispatch Data ........................................................................................................ 54
1. General ...................................................................................................................... 54
2. Dispatch Data Modules ............................................................................................. 55
3. Dispatch Data DM and Schema Mapping ................................................................ 57
4. Dispatch Content Guidelines .................................................................................... 57
3-4-4. Front Matter Data .................................................................................................. 58
1. General ...................................................................................................................... 58
2. Front Matter Data Modules ....................................................................................... 58
3. Front Matter DM and Schema Mapping ................................................................... 59
3-4-5. Limitations Data.................................................................................................... 59
1. General ...................................................................................................................... 59
2. Limitations Data Modules......................................................................................... 60
3. Limitations DM and Schema Mapping ..................................................................... 60
3-4-6. Performance Data.................................................................................................. 60
1. General ...................................................................................................................... 60
2. Performance tables .................................................................................................... 61
3. Performance Data Modules....................................................................................... 62
4. Performance DM and Schema Mapping ................................................................... 63
3-4-7. Procedures Data .................................................................................................... 64
1. General ...................................................................................................................... 64
2. Procedures Data Modules ......................................................................................... 65
3. Procedure DM and Schema Mapping ....................................................................... 69
4. Procedure Content Guidelines .................................................................................. 70
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page vi
3-4-8. Substantiation Data ............................................................................................... 72
1. General ...................................................................................................................... 72
2. Substantiation data module ....................................................................................... 72
3. Substantiation DM and Schema Mapping ................................................................ 72
3-4-9. Systems Description Data ..................................................................................... 72
1. General ...................................................................................................................... 72
2. Systems Description Data Modules .......................................................................... 73
3. Systems Description DM and Schema Mapping ...................................................... 76
4. Systems Description Content Guidelines.................................................................. 77
3-5. Graphics and Multimedia .............................................................................................. 79
3-5-1. Graphics standards ................................................................................................ 79
1. Graphic Format ......................................................................................................... 79
2. Intelligent graphics.................................................................................................... 79
3. Graphic Display ........................................................................................................ 79
3-5-2. Multimedia files standards .................................................................................... 80
3-5-3. Information Control Number ................................................................................ 80
1. Model Identification Code ........................................................................................ 81
2. System Difference Code ........................................................................................... 82
3. Standard Numbering System .................................................................................... 82
4. Responsible Partner Company Code ........................................................................ 82
5. Originator Code ........................................................................................................ 82
6. Unique Identifier ....................................................................................................... 82
7. Variant Code ............................................................................................................. 82
8. Issue Number ............................................................................................................ 82
9. Security Classification .............................................................................................. 83
3-5-4. Information Control Number Extension ............................................................... 83
Chapter 4. DATA PACKAGING AND DELIVERY ............................................................ 84
4-1. Introduction ................................................................................................................... 84
4-2. Publication Module ....................................................................................................... 85
4-2-1. Assembly for publication ...................................................................................... 85
4-2-2. PM Identification .................................................................................................. 85
1. Publication Module Code ......................................................................................... 85
2. Language ................................................................................................................... 86
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page vii
3. Publication Module Code extension ......................................................................... 86
4. Issue information ...................................................................................................... 86
4-2-3. Content and metadata organization of publication modules ................................. 87
1. Metadata : PM Status fragment................................................................................. 87
2. Publication structure: PM Content fragment ............................................................ 89
4-2-4. Publication Module Schemas ................................................................................ 91
1. PM Schema Mapping ................................................................................................ 91
4-2-5. Non-linear data module concept ........................................................................... 91
4-2-6. PM Entry revision dates for open and closed applicability .................................. 91
4-3. Data Delivery ................................................................................................................ 92
4-3-1. Project rules .......................................................................................................... 93
4-3-2. Project rules using structured format .................................................................... 93
4-3-3. Delivery scope ...................................................................................................... 94
4-3-4. DM Status and DM Content life cycles ................................................................ 94
4-3-5. PM Status and PM Content life cycles ................................................................. 94
4-3-6. Exchange Package ................................................................................................ 94
4-3-7. Package Organization Description ........................................................................ 95
1. General ...................................................................................................................... 95
2. Package Organization Description file ..................................................................... 97
3. Package Organization Description Schema ............................................................. 97
4-3-8. Exchange Package Status List .............................................................................. 97
1. Exchange Package Status List Identification ............................................................ 99
2. Issue information ...................................................................................................... 99
4-3-9. Exchange Package Status List Schema ................................................................. 99
4-3-10. Major Event .......................................................................................................... 99
4-3-11. Subsets .................................................................................................................. 99
4-4. Data Set Status List ..................................................................................................... 100
4-4-1. General ................................................................................................................ 100
4-4-2. DSSL (Data Set Status List) ............................................................................... 101
4-4-3. Data Set Status List Schema ............................................................................... 102
Chapter 5. FLIGHT OPERATIONS INFORMATION STANDARDS .............................. 103
5-1. Phase Of Flight Specification ..................................................................................... 103
5-1-1. Identification ....................................................................................................... 103
5-1-2. Transition Relationships ..................................................................................... 103
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page viii
1. Transition Relationships for Airplane Operations .................................................. 103
2. Transition Relationships for Helicopter Operations ............................................... 105
3. Transition Relationships for Spacecraft Operations ............................................... 107
5-1-3. Definitions........................................................................................................... 109
1. Flight Planning (FLP) ............................................................................................. 109
2. Pre-flight (PRF) ...................................................................................................... 109
3. Engine Start/Depart (ESD) ..................................................................................... 109
4. Taxi-out (TXO) ....................................................................................................... 109
5. Take-off (TOF) ....................................................................................................... 110
6. Rejected Take-off (RTO) ........................................................................................ 110
7. Climb (CLB) ........................................................................................................... 110
8. Separation (SEP) ..................................................................................................... 111
9. Boost (BST) ............................................................................................................ 111
10. In Space (SPC) .................................................................................................... 111
11. Cruise (CRZ) ....................................................................................................... 111
12. Descent (DST) .................................................................................................... 111
13. Re-Entry (REN) .................................................................................................. 112
14. Hover Out of Ground Effect (OGE) ................................................................... 112
15. Approach (APR) ................................................................................................. 112
16. Go-Around (GOA) .............................................................................................. 113
17. Landing (LND) ................................................................................................... 113
18. Taxi-in (TXI) ...................................................................................................... 113
19. Tow-in (TOW) .................................................................................................... 114
20. Arrival/Engine Shutdown (AES) ........................................................................ 114
21. Post-flight (PSF) ................................................................................................. 114
22. Flight Close (FLC) .............................................................................................. 114
23. Ground Servicing (GDS) .................................................................................... 114
5-2. ATA Flight Operations Standard Numbering System ................................................ 115
5-3. Data Module Information Codes ................................................................................ 141
5-3-1. Information Codes for content DMs ................................................................... 141
5-3-2. Information Codes For Data Management DMs ................................................ 144
APPENDICES ............................................................................................................................ 145
Appendix 1. Unit of Measure Code ..................................................................................... 145
Appendix 2. Backward Compatibility ................................................................................. 154
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page ix
Appendix 3. References ....................................................................................................... 155
Appendix 4. Data Dictionary ............................................................................................... 156
A4-1. Description of Information ................................................................................. 156
1. Entry Info ................................................................................................................ 156
2. Definitions............................................................................................................... 156
3. Application in Specifications .................................................................................. 157
4. Permitted Values ..................................................................................................... 161
A4-2. Spec 2300 Entries ............................................................................................... 161
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page x
Important Information About This Document
Read Before Using This Document
This document contains recommended specifications that have been developed for the covered
topics. ATA does not mandate their use. You must decide whether or not to use the
recommendations in this document. You may choose to use them in whole, in part, or not at
all.
There may be practices, standards and/or regulatory requirements applicable to your operations
that exceed the recommendations in this document. You are solely responsible for determining
if such practices, standards or requirements exist and whether they apply to your activities, and
for complying with those that are applicable. Such practices, standards and requirements can
change significantly over time.
ATA does not guarantee, promise or warrant that the specifications in this document will meet
the needs of your operations. This is a determination that you must make and for which ATA
is not responsible.
IMPORTANT NOTICE: This document is intended to be used only in an electronic

environment. ATA accepts no responsibility or liability for any material
printed from this document.
For Additional Information

For more information or to order additional publications, refer to the Airlines for America
(A4A) Publications website at http://www.airlines.org/publications, e-mail pubs@airlines.org,
or call +1 202-626-4000.
For Technical Information and Change Submissions

Errata information for ATA Publications is available at the A4A Publications Web page.
For technical information or to recommend an alteration or amendment to this specification,
please submit the recommendation and any supporting documentation to ATA:
ATA Change Request (CR) Process and Forms:
http://www.ataebiz.org/specifications/Change_Requests/
E-mail: admin@ataebiz.org
Phone: +1 202-626-4062
Fax: +1 202-626-4181
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page xi
Highlights
Release History
Revision 2017.1 – October 2017
Revision 2016.1 – November 2016
Revision 2015.1 – November 2015
Revision 2014.1 – June 2014
Revision 2013.1 – April 2013
Revision 2011.2 – December 2011
Revision 2011.1 – April 2011
Revision 2009.1 – October 2009
Draft version 0.2 – May 2009
Draft version 0.1 – May 2008
Revision: 2017.1
Location in
Change Description
Specification
Multiple locations Added Sample Data Keyword references to facilitate searching for specific topics within
the sample data XML files. Corresponding keywords were added to multiple sample data
XML files.
CR-2017-09_SampleDataKeywords
1-6-3 Added new section to describe the Sample XML data files provided with the specification,
and the use of Sample Data Keywords to facilitate searches.
CR-2017-09_SampleDataKeywords
2-4 Updated the description of Temporary Data Modules to provide more clarification.
CR-2017-10_TDM
Appendix 1 Added Units of Measure to support Rotorcraft requirements.

CR-2017-08_UnitsOfMeasure
FailureConsequences.xsd Updated the inopItemsGroup element definition to allow recursive use of this structure.
schema Added a new optional element "title" to inopItemsGroup.
CR-2017-05_InopItemsGroup
DispatchItem.xsd schema Added a new optional attribute, "removable on dispatchItem "to identify non-essential
dispatch items that can be removed under Operator process and responsibility.
CR-2017-06_Removable
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page xii
Location in
Change Description
Specification
Approval.xsd schema Changed the properties of attributes "issueNumber" and "subsetIssueNumber" to allow
SubSetHeader.xsd schema string values.
Pm.xsd schema Added a new optional attribute "minorIssueNumber" to approbationIdentification,
DmStatus.xsd schema productIssueInfo, and subset elements.
CR-2017-07_RevisionNumbering
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page xiii
Chapter 1. INTRODUCTION
1-1. Purpose
The purpose of this specification is to provide a concise set of information standards and
guidelines for the management, configuration and interchange of flight operations technical
content for fixed-wing and rotorcraft. This Specification is focused on a data-centric approach,
addressing the aircraft operator’s current and planned future operational / business
requirements of these data. A corner stone of this specification is that these data are stored
once, reusable without rework, and the interchange mechanisms will be non-proprietary,
software / hardware independent, integrity checked, secure and self-verifying.
This specification is designed to enable the cost-effective and efficient exchange of digital data
between information providers and information users for Flight Operations. The primary
goals, features, and objectives are:
• Exchange of information based on non-proprietary standards.
• A standard architecture that is data-centric as opposed to document-centric, and relies

on modular, reusable components.
• Information from multiple manufacturers is received by operators in a single, consistent

manner.
• Facilitate identification of changes to the data.
• Facilitate modification or re-authoring of information.
• Separate presentation of information from the content of the information, enabling

output to multiple formats.
• Enable identification of information based on its applicability to specific aircraft or

fleets.
• Facilitate re-use of content for different audiences, e.g., Crew Use During Flight, In-
House Training, Engineering, Computer-Based Training (CBT).
Spec 2300 is not intended to address unique operational needs or specific implementations, but
rather to provide an industry standard framework from which such implementations could be
developed.
1-2. Intended Audience

This specification provides business and technical requirements and guidelines to enable data
providers, data receivers, and technology solution providers to exchange digital flight
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page 1
operations data in an efficient, cost-effective manner. Specifically, the roles in those
organizations that should use this specification include:
• Content authors
• Engineers
• System analysts
• Database engineers
• Programmers
• Aircraft configuration and data managers
1-3. Scope Of This Document

This revision of the specification describes the requirements and standards for exchange of the
following types of digital content pertaining to flight and cabin crew operations and training:
Approval: Data used to record or display the regulatory approval of flight operations data and
documents.
Dispatch: Data to inform flight crews of the allowable minimum equipment and configuration
required for departure of a flight
Front Matter: Contains general or introductory information for flight operations documents
or topic.
Limitations: Data that define the envelope within which the aircraft and systems are designed
to safely operate.
Performance: Data used to calculate the aircraft and engine performance for flight operations,
including normal and certain non-normal configurations. Data can include items such
as takeoff and landing distance, climb rates, fuel burn, holding, etc. For certain aircraft models
this section may be a User Guide for Performance Software.
Procedures: Describes the operational procedures that must or may be conducted by flight or
cabin crews before, during, and after a flight.
Publication Module: The collection of Spec 2300 data modules that constitute a given flight
operations publication
Substantiation: Data used to document the historical background for the creation and
modification to Master Minimum Equipment List (MMEL), Airplane Flight Manual (AFM)
and other information. This data is generally exchanged between Original Equipment
Manufacturers (OEMs), regulatory agencies and lead airlines.
Systems Description: Flight and cabin crew-oriented functional aircraft systems and sub-
systems descriptive data designed to support aircraft procedural instructions.
Weight and Balance: Data pertaining to aircraft center of gravity, fuel and water loading,
cargo loading, etc.
1-4. Anticipated Benefits

There are several benefits to the use of digital technologies for the exchange of flight operations
data.
1-4-1. Standardization
Across-fleet standardization can be achieved at several levels, from operational philosophy
through procedures, to the use of common formats and terms in the different fleets.
An operator's style manual can promote the document designer’s use of standard names for
common items and actions. A style manual should have a glossary of terms, acronyms and
their standard definition. Such a glossary should be developed and updated on a regular basis.
1-4-2. Use of Structured Information

Information can be structured in such a way as to improve overall crew performance. In the
design of larger documents, such as operations manuals, information should be structured and
sequenced such that it can be accessed quickly by flight crews. The structure should be clearly
stated, easy to understand, appropriate for the information documented and clearly identified
through headings and other formatting devices. Structuring guidelines address the higher level
issues that generally apply at the document level. Format and typography issues can be used at
a lower level to facilitate information access, and apply at the page or display level.
This technology should help by meeting the following business needs:
• Data should be stored only once and referenced (may be addressed in a later phase to
avoid discrepancy in information)
• Data should be exchanged in commonly agreed standards (e.g., text, graphics, transport
media, revision and applicability [aka, effectivity] models)
• Revision tracking metadata allows for identification of changes, e.g., what data has
changed, when it changed and who has changed it
• Information can be released either as a complete package or as an interim release with

only the changed content included
• This data interchange should allow operators to simplify their workflow, further
reducing unnecessary steps while having customized output that can be referenced back
to the manufacturer’s data.
1-4-3. Additional Benefits
Airlines will be able to source publication solutions that will help them to realize the maximum
efficiency in their publishing work flow, while increasing the diversity of their output media.
Content reuse can become a reality. For example, a fuel policy can be developed for a whole
airline yet appears at the appropriate place in each fleet’s manual. Its owner can be confident
that if he changes the policy all users of the information will get the latest information.
The scope of Spec 2300 is on the exchange of flight operations data. The diagram below
depicts one example of how this data may be processed by the operator.
Figure 1-1 Electronic Data Framework
Data in
Spec 2300
Format
Manufacturer A
Data in Internet Operator Content

Spec 2300 Management System
Format
Manufacturer B Operator Server
Operator
Data
Data in
Spec 2300
Format
Manufacturer C
Data Transformation /
Multi-Channel
Publishing
Computer
Performance
?
Based Training
Calculations
Paper Workstation Smartphone EFB
1-5. XML Implementation

This specification employs the use of the eXtensible Markup Language (XML) as the standard
format for exchange of flight operations data.
XML is the predominant technology for data interchange. XML has superior features to enable
consistency in how information is described, a critical requirement for interoperability and
system integration. As a result, XML is supported by many of the leading software
applications, tools, and vendors.
The primary XML component of this specification is a set of XML Schemas. A schema is a
model for the content and structure of an XML document. It describes the data that are used
for a given type of information (e.g., System Description), as well as their data types, whether
they are mandatory or optional, number of occurrences, and more. A system can validate if
the XML it receives is compliant with the corresponding schema; thereby facilitating correct
interpretation of the contents of the XML. This capability makes it possible to automate
processing of the data.
1-6. Flight Operations Markup Language

1-6-1. General
Flight Operations Markup Language (FOML) is the industry-standard format for the content
and structure of digital flight operations data. FOML is designed to meet the unique
requirements for civil aviation flight operations data. It consists of a series of self-contained
XML schema modules, based on the W3C XML Schema Language. Each schema module
defines element(s) and/or attribute(s) that describe the unique data types and definitions for
that schema. Where applicable, FOML has drawn on existing industry standards and best
practices (e.g., S1000D®, MathML, CALS, etc.)
1-6-2. Schemas
The diagram below depicts the FOML schema modules.
Note: All Spec 2300 XML Schemas are provided in the accompanying folders.
Figure 1-2 FOML - XML Schemas Layout
Data Management
Schemas
Publication
Technical
Technical Content
Content Schemas
Schemas ApplicCross
Module
RefTable
(Pm)
Dispatch Schemas General Schema
Dispatch CDL Supplemental CondCross
Front Matter PmStatus
Item Item Content RefTable
Dispatch System
Exchange
Procedure Fault Limitations Schema Approval Schemas ProductCross
Package
RefTable
StatusList
Dispatch SubSet
Limitation Approval
Locator Header
DmStatus Container
Procedures Schemas
Normal NonNormal Failure Performances Schema
Glossary Qualifier
Procedure Procedure Consequences Repository Repository
Performance
CabinEquip
Malfunction
Link Target Package
Repository Organization
Systems Schemas Substantiation Schema
System Substantiation Data Set
Annunciation Project Rules
Description Status List
Additional
Parameters
1-6-3. Sample Data
Sample XML data are provided to illustrate the intended application of the standard for certain
data structures described in this specification. These samples can be used by implementers to
aid in development of software to support this specification.
The sample XML fragments pertain to the FCOM, QRH, and DDG Data Module types defined
in Spec 2300. These XML samples are provided solely to illustrate intended application of the
specification and are not intended for operational use, nor do they represent a comprehensive
implementation of the specification. The data provided is for a fictitious aircraft model and
does not represent any specific aircraft design type in operation today.
Note: Sample data XML files are provided in the accompanying folders.
Throughout this specification, references to data sample keywords are provided to highlight
concepts for which sample data exist. This allows the reader to search for those keywords in
the sample data library to find the XML samples which illustrate the concept.
Example of a keyword reference in this specification:
Sample Data keyword: "kwd:ProjectRules"
Example of a keyword in a sample data XML file:

1-7. Tailoring Spec 2300 for a Specific Project

To support the broadest reasonable range of business scenarios and data requirements, Spec
2300 contains some degree of variability in the type of data which can be provided and the
manner in how those data are structured. However, for a given data provider/receiver
relationship, this variability can be constrained by specifying which optional elements are to
be used and how certain types of information are to be provided by using Project Rules [Section
4-3-1 Project rules].
Project rules must be coordinated between the parties and can be conveyed using a structured
format (i.e., XML) to facilitate Spec 2300 implementation and data validation [Section 4-3-2
Project rules using structured format].
Chapter 2. DATA MODULE MANAGEMENT
2-1. Data Management Concepts

This specification uses a modular, data-centric approach for organizing and exchanging
information. This approach overcomes the traditional paper-oriented packaging in manuals and
allows information to be provided in a format and manner that is more consistent with the way the
information is used in the end user’s business processes.
This approach utilizes Data Modules, which are complete, meaningful, collections of data. A Data
Module is the minimum information object for exchange.
For example, in a manual-centric process, if the description of an Indicator is changed, then each
manual or document with a reference to that Indicator must be updated and transmitted. The data
receiver must import each transmission and integrate the results. Because of possible differences
in revision dates for these various documents, the Indicator information can be inconsistent. The
data-centric process defined in this specification eliminates this problem by transmitting an
updated Indicator data module. This transmission has only one instance of the changed Indicator
so inconsistency is not possible. There is also no requirement for the information receiver to
integrate separate deliverables. The information receiver may then use the single updated Indicator
data to generate whatever documents are required.
In order to be able to build a manual (a given organization of Data Modules), Publication Modules
are used to organize the data modules into a hierarchy.
In any component, elements have optional ID attributes. Values must be unique and persistent.
2-2. Data module types

Two categories of data modules can be found:
• Flight operations technical content
• Data management
Flight operations technical content data modules provide the effective content of different
information types such as System Descriptions, Dispatch Data, Procedures, Limitations,
Performance and Weight and Balance. Refer to [Section 3-4, Flight Operations Technical
Content].
Related to the set of flight operations technical content data modules, a set of special data modules
are provided for management of the data. The following are Data Management type modules:
Cross-reference tables: Applicability cross-reference table, Condition cross-reference table and
Product cross-reference table. Refer to [Section 3-3-1, Applicability management].
Container data modules: Allow the association of several data modules representing the same
data but with different applicability. Refer to [Section 3-3-3, Container and Alternate Data
Modules].
Information repository data modules: Allow the delivery of factorized and shared data (i.e.,
qualifier repositories, glossary repository, link target repository) that are referenced in other data
modules. Refer to [Section 3-3-4, Information Repositories].
Additional Parameters: Allow the delivery of additional values for software parameters that are
not found in any other Data Module Content. Refer to [Section 3-3-6, Additional Parameters].
All data modules (for technical content and for data management) use a common standardized
identification and follow a physical organization for content and metadata.
2-3. Data Module Identification

Each data module has a unique identification composed of:
• Data Module Code
• Language
• Optional data module code extension
Additionally, issue information is provided.
2-3-1. Data Module Code

The Data Module Code (DMC) is the standardized and structured identifier for a data module. The
DMC may range from 17 to 50 characters in length with 11 components per the following:
Component Required Range Minimum Maximum

Digits Digits
Model Required NATO NSPA Model 2 14
Identification Code Identification - ASD
(MI) S2000M
System Difference Required alphanumeric 1 4

Code (SDC)
Standard Required Refer to [Section 5-2 ATA 6 8

Numbering System Flight Operations
(SNS) Standard Numbering
System], except for
dispatch data, which uses
iSpec 2200 SNS.
Disassembly Code Required alphanumeric 2 2

(DC)
Component Required Range Minimum Maximum
Digits Digits
Disassembly Code Required alphanumeric 1 3
Variant (DCV)
Information Code Required Refer to [Section 5-3 Data 3 3

(IC) Module Information
Codes]
Information Code Required "A" 1 1

Variant (ICV)
Item Location Code Required "A" or "T" 1 1

(ILC)
Total Required Required - 17 36
Learn Code (LC) Optional "T00", "T01", "T02", 3 3

"T03", "T04"
Learn Event Code Optional and "C" 1 1

(LEC) Conditioned to LC
Total without Optional - 21 40

Dispatch Extension
Code
Dispatch Extension Optional and alphanumeric 10 10

Code conditioned to DM
Type
Total with Dispatch Optional - 31 50

Extension Code
The following diagrams show the structure of the DMC at the minimum and maximum sizes.
If presented as a single string, the DMC must be presented with hyphens [-] in the positions as
shown in the figures and without spaces in between. The hyphens separate the contents of the
codes, as shown, but are not included within the population of the DMC attributes.
1. Data Module Code Structure
Figure 2-1 Data Module Code structure
DMC 17+10 Characters (minimum)
DMC 40+10 Characters (maximum)
YYYYYYYYYYYYYY - YYYY – YY-YY-YYYY - YY YYY - YYY Y - Y – YYY Y - YYY-YYYY-YYY
Model identification code

System difference code
Standard numbering system
Disassembly Code
Disassembly Code Variant
Information Code
Information Code Variant
Item Location Code
Learn Code
Learn Event Code
Dispatch Item Extension Code
1.1. Model Identification Code

The Model Identification (MI) Code identifies the Product to which the data applies and is the
point of reference for all applicability information. The MI includes all related model variants. MI
Codes must be in accordance with NATO NSPA Model Identification - ASD S2000M - Model
Identification Codes (MI).
1.2. System Difference Code
The System Difference Code (SDC) indicates alternative versions of the system and subsystem by
the SNS without affecting the type, model or variant identity. SDC can also be used to differentiate
DMs which pertain to the same subject but for different equipment variations installed on the
aircraft.
1.3. Standard Numbering System
The Standard Numbering System (SNS) describes the aircraft System and Subsystem breakdown
to which the information in the data module applies. The Flight Operations Standard Numbering
System uses the Chapter level designations from the ATA SNS as defined in this specification,
except for dispatch data. Refer to [Section 5-2 ATA Flight Operations Standard Numbering
System]. Dispatch data uses iSpec 2200 SNS at System and SubSystem level (first 3 digits only),
optionally extended by the Dispatch Item extension code.
The SNS consists of three groups of characters: System, Subsystem/Sub-Subsystem and
Assembly. The Flight Operations SNS allows 6 or 9 alphanumeric characters. The system
represents the general systems and the basic structure of the product. The system is identified in
the Data Module Code by the first two or three alphanumeric characters. Subsystem/sub-subsystem
and assembly describe the further breakdown of system. The subsystem is identified in the Data
Module Code by the third alphanumeric character and the sub-subsystem by the fourth
alphanumeric character. The assembly code is the final division to provide identification of a
specific item within a system/subsystem/sub-subsystem and is identified by the last two or four
alphanumeric characters.
Figure 2-2 Standard Numbering System structure
min 6 characters YY - Y Y - YY
max 8 characters YY - Y Y - YYYY
System
Subsystem
Sub-subsystem
Assembly
1.4. Disassembly Code

The Disassembly Code (DC) identifies the breakdown condition of an assembly to which
information applies. The disassembly code (DC) can also be used to provide additional project-
defined numbering to the DMC, for any purpose. Use "00" as the default value if DC is not
applicable. The use of alphanumeric characters in both positions is permitted, establishing a range
from 00 – ZZ.
1.5. Disassembly Code Variant
The Disassembly Code Variant (DCV) designates alternative items of equipment or components
differing slightly in design, but not enough to warrant a change of the system difference code.
The use of one to three alphanumeric characters is permitted. Characters range from 0 – ZZZ.
When DCV is not required to differentiate DMs, then the value "A", "AA", or "AAA" must be
used. For container DMs, the value "Z", "ZZ", or "ZZZ" must be used. Other values may be used
to differentiate the DMs inside a container.
1.6. Information Code
The Information Code (IC) is used to describe the type of information contained in the data
module.
The relationships between data modules and XML Schemas are provided in Chapter 4 of this
specification.
Flight operations data use the Information Codes listed in Chapter 5. Refer to [Section 5-3, Data
Module Information Codes].
1.7. Information Code Variant
The Information Code Variant (ICV) fixed value is "A".
1.8. Item Location Code
The Item Location Code (ILC) default value is "A". If the DM pertains to training information,
there are two options available:
- Use the value "T" in ILC; or
- Use either value "A" or "T" in ILC and provide Learn Code.
1.9. Learn Code
The Learn Code (LC) is an optional code that is applied to training data modules. Each LC
represents a category of training information.
The following codes are available:
o T00 – Generic Training
o T01- In Flight Training
o T02 - Simulator Training
o T03 – On Ground Training
o T04 - Test Flight
1.10. Learn Event Code
The Learn Event Code (LEC) is an optional one-character, alpha code that may be applied only if
the Learn Code (LC) is used. If used, the value "C" (training content) is required.
1.11. Dispatch Item Extension Code
The Standard Numbering System (SNS), used by Dispatch data modules (CDL Item, Dispatch
Item, Dispatch Locator, System Fault, M Procedure, M Note, O Procedure, O Note), based on the
ATA iSpec 2200 SNS, can be optionally extended using the Dispatch item extension code as part
of the DMC.
The Dispatch Item Extension Code is a 10-character alphanumeric string, based on the following
scheme:
YYY-YYYY-YYY
Note: Data providers may populate the Dispatch Item Extension Code with any values,
provided it conforms to the above scheme.
2-3-2. Language
The Language in which the data module is written is part of the data module identification.
It is composed of:
• The ISO Language Code: Generally coded by using the two alpha characters from
International Standards Organization (ISO) 639. Simplified languages are coded by
using additional codes similar to, and not in conflict with, ISO 639 codes.
• The ISO Country Code: Coded by using the two alpha characters from ISO 3166 to
denote the country where the language is spoken.
2-3-3. Data module code extension

An optional Data Module Code Extension may be provided. This gives the additional parameters
needed to establish a unique identification of a data module in those cases when data module code,
issue information and the language and country are insufficient to form a universally unique
identity for a Data Module.
It is composed of:
• The extension producer: Contains the CAGE/NCAGE code of the producer of the
data module instance and forms part of the universally unique identifier of a data
module instance.
• The extension code: Typically, but not necessarily, contains customer related content
(e.g., customer CAGE appended with a sequence number). the value of which is
decided by the data module producer.
2-3-4. Issue information
Issue information for a data module contains the issue date of the data module, composed year,
month, day, hour and minute properties, a decimal-valued second property, and a Boolean time-
zoned property.
Optionally, issue information may contain an additional in-work number, composed of a numeric
value. This additional number, if presented, indicates that the document is still being revised and
is not yet at its final version. It will be sequentially increased with each in-work version, starting
at 0.
Following the physical organization of data modules, the following issue information is provided:
• issue information for content part of the data module (DM Content), and
• issue information for metadata (DM Status) part of the data module.
2-4. Temporary Data Modules

A Temporary Data Module (TDM) is a data module that is temporarily applicable for operational
reasons and which may replace another DM.
For example, this is used when a defect in a system has an impact on the operation. The aircraft
manufacturer sends a TDM to temporarily replace the DM or to provide temporary new
information. When the defect is fixed, the TDM is cancelled and the original DM becomes
applicable again.
The TDM is distinguished from the DM by the tdmInfo element structure in DM Status. The
content may provide a reference to the impacted DM using a dmRef element. When the TDM is
temporarily replacing a DM, the disassyCode and/or disassyCodeVariant is to be used to ensure
uniqueness in the DMC.
When the TDM is processed as part of a future revision it is either revised, cancelled and removed,
or absorbed into the dataset.
2-5. Data module content and metadata organization

2-5-1. Data module global content
A data module is composed of two parts:
• DM Content: The technical content of a Data Module
• DM Status: The related metadata, including applicability annotation, revision data and
data for some business concepts
Using the unique data module identification, the DM Content and the DM Status parts of data
modules are physically provided with two separate XML fragments. Refer to [Section 2-3, Data
Module Identification]. Each of the fragments can be delivered separately in the exchange package,
and has its own issue information.
Following the revision mechanism described in this specification, the two XML fragments of a
data module each have their own life cycle. Refer to [Section 3-3-2, Revision Management]. For
example, if only the applicability of a data module is changed but the technical content is not
changed, then only the DM Status XML fragment of the data module is delivered.
2-5-2. Content fragment

The DM Content XML fragment follows a regular structure for Flight Operations technical content
data modules and data modules for management (such as the applicability cross-reference table
and container data modules). The structure of the DM content fragment is common to all data
modules and includes:
• The data module identification. Refer to [Section 2-3, Data Module Identification].
• The DM content issue information, containing the issue information of the DM Content
fragment.
• The technical content depending on the data module type and schema.
2-5-3. Metadata: DM Status fragment

The DM Status XML fragment follows the same model for all types of data modules:
• Associated properties (attributes) giving status information. Refer to [Section 3-3-2,
Revision Management].
• The data module identification. Refer to [Section 2-3, Data Module Identification].
• The DM status issue information containing the issue date of the DM Status fragment.
• The DM content issue information, containing the issue date of the DM Content
fragment. It allows identification of the DM Content fragment to which the provided
metadata applies.
• Data for some business concepts.
• Approval information, providing data on the approval status of the DM; given when
approval is required.
• Applicability annotations. Refer to [Section 3-3-1, Applicability management].
• Revision data pertaining to metadata and technical content. Refer to [Section 3-3-2,
1. DM Status Schema Mapping
DM Status XML fragments use the DmStatus.xsd schema.
2-5-4. DM Status and DM Content association

Because the two parts of a data module are provided in two separate XML fragments and can be
delivered separately, the following mechanism is used to make the association between the DM
Content XML fragment and the DM Status XML fragment:
• DM identification for both XML fragments is identical
• The DM content issue information for both XML fragments is identical

Figure 2-3 Data Module Status and Content Association
2-5-5. Addressing mechanism

1. Path to Nodes
The DM Status XML fragment provides metadata (such as revision marks or applicability) related
to:
• Flight operations technical content provided in the DM Content XML fragment
• Other metadata provided in the current DM Status XML fragment
To address specific elements or attributes from the DM Status XML fragment, a shared mechanism
is applied, based on the W3C XML Path Language (XPath) 2.0.
This specification uses only the XPath functionality pertaining to Path Expressions, which is used
to locate nodes within trees.
2. Contexts
An Xpath expression evaluation must give one or more nodes (elements or attributes). The
evaluation contexts are:
• Root of XML document DM Status for path addressing metadata.
• Root of XML document DM Content for path addressing content.

Figure 2-4 Data Module Addressing Mechanism
The use of persistent element IDs is preferred in XPath expressions.

Using this path mechanism, any element of a DM Content XML fragment or DM Status XML
fragment can be addressed. The path mechanism is used to:
• Address an inline applicability for elements in DM Content
• Address revision marks for elements and attributes in DM and PM Content
• Address revision marks for applicability in DM Status.
• Address a data owner for elements in DM Content
• Address an avionic context for elements in DM Content
• Address a dispatch qualifier for specific elements (dispatch condition, proviso) in

Dispatch Item DM Content
2-5-6. Extended path for part of content

To address a part of element or attribute content, for inline revision marks (Refer to [Section 3-3-
2 Revision Management]), the XPath mechanism is extended with two optional properties to
address a range of characters:
• Start position: Contains a positive integer, giving the starting position of the selected
range in the content. Start position begins at 1.
• End position: Contains a positive integer, giving the ending position of the selected
range in the content.
The following rules apply:

• Both positions are inclusive.
• If start position is provided, end position is required.
• End position must be greater than start position.
• End position must be less than or equal to the content length.
• In case of mixed content, the Start and End positions are based on the concatenated text
content of the base Node (i.e., nested tags are ignored).
• The extended path mechanism is not relevant to address elements in mixed content.
Examples:
Chapter 3. FLIGHT OPERATIONS INFORMATION
3-1. Introduction
This chapter provides technical guidelines for Flight Operations information. Where
applicable, business rules and specific XML markup may be provided to illustrate and further
clarify data usage. This chapter is divided into three major sections, General Structures, Data
Management and Flight Operations Technical Content.
General Structures specifies common data concepts and structures that can be used by one or
more areas in the technical content. The Data Management section specifies metadata that are
used to manage data configuration, publishing revision and unique data repositories. The
Flight Operations Technical Content section describes all the data module types and how they
may be used to represent the core technical content for each of the data domains such as
Systems Description, Procedures, Dispatch, Limitations, etc.
3-2. General Structures

This section describes all common data concepts and structures that are applicable for one or
more data elements and/or data modules. Their usage is generally the same regardless of XML
schema or where they are being implemented.
3-2-1. Information Layers

Sample Data keyword: "kwd:InformationLayers"
Operational documentation, and particularly the FCOM, has many varied uses. Basically, ﬂight
crews use the FCOM to perform their daily tasks. However, the FCOM is also commonly used
by airlines for training purposes and by their operations and scheduling personnel.
The FCOM can also be used as a reference document for the creation of an Airline Operations
Manual (AOM). As such, it can be used as is, or complemented, or even reworked and
customized with specific airline material (e.g. airline policy, training philosophy, national
requirements, etc.)
To support these varying needs, up to three layers of information are available and allow
filtering of information in accordance with a user’s needs and the level of detail required.
The three layers are:
• Layer 1 provides "need to know" information: This is the minimum amount of
information considered necessary for the flight crew to safely operate the aircraft.
• Layer 2 provides "nice to know" information: This information can be used as

reference for pilots to fully understand the logic of the aircraft-pilot interface.
• Layer 3 provides "expert knowledge": This information is not likely to be used in
flight, but is intended to provide a greater level of detail that can be used at the
operator's discretion.
A layer can be used for a content element or for a whole data module.
If a nested element does not have a layer value, the parent element’s layer applies. If there is
no layer information associated to an element and to any parent elements, then the current
element will be considered as Layer 1.
When an element has an information layer, its child elements must not have lower layers (i.e.
they are at least as much detailed as their parents). If some child elements are figures, this rule
also applies to their graphics.
3-2-2. Phase of Flight

Sample Data keyword: "kwd:PhaseOfFlight"
Phase of flight information can be assigned to the operational documentation. This is
particularly the case for normal procedures.
The ATA phases of flight are defined in [Section 5-1 Phase of Flight Specification].
The phase of flight concept specifies which phase of flight is assigned to a data module.
3-2-3. Crew qualification

Some procedures require the crew to have one or more special qualifications, such as Low
Visibility Procedures (LVP). The crew qualification attribute is used in procedure data modules
to indicate that special crew qualifications are required to perform the procedure.
3-2-4. Policy references

Information that is included in the operational documentation can be associated with external
references.
Typical references can be:
• a regulation or guidelines, as FAA, EASA, ICAO
• a company policy, as airline policy documentation
The policy reference concept identifies a data module that is associated with a reference.
The policy reference concept provides the source of the reference and the title of the reference.
This title of the reference can be the name of the reference document, such as "EU-OPS" or a
specific requirement, such as "IOSA Standards Manual FLT 1.11.4".
3-2-5. Data owner
Information that is included in the operational documentation can be based on external sources,
such as certification basis, or sub-contractor documentation. Therefore, any update of this
information may not be allowed without agreement by the source of the data.
The data owner can be assigned to a complete DM or elements within a DM.
3-2-6. References Management

Sample Data keyword: "kwd:References"
1. General
References Management provides mechanisms to support references between the sources and
their intended targets, which allow the receiving systems or applications to handle the
references more appropriately and in different ways. The references are categorized into four
types; data module, internal, external and external application.
2. Data Module Reference
Sample Data keyword: "kwd:References.DM"
A data module reference is a direct reference from a source data module to a target data module.
The reference can occur anywhere in the source data module. While the target generally refers
to the entire referenced data module, it may be specific to a specific element in the target data
module. This reference is also used to gather the data modules into a publication module.
Refer to [Section 4-2, Publication Module].
The referencing mechanism is specified by the dmRef element. The dmRef element carries
the exact replica of the target data module identification (dmRefIdent) which includes the data
module code (dmCode) for the target DM. The optional referredFragment attribute is used if
the target is a specific element in the data module.
A data module reference may also provide additional descriptive content and/or behavior
attributes to facilitate how the reference should be handled.
3. Internal Reference
Sample Data keyword: "kwd:References.Internal"
Internal references are used when the source and target of the reference are within the same
data module. The internal reference mechanism is specified by an internalRef element. The
internarial attribute is used to specify the target location, such as an element id in the data
module. The element id may be a figure; in this case the reference points to the graphic.
4. External Reference
Sample Data keyword: "kwd:References.External"
External references are used when the source is within an ATA Spec 2300 data module, and
the target is not within the scope of ATA Spec 2300 data (e.g., AMM, regulatory guidance,
etc.). The external reference mechanism is specified by the externalRef element with the main
target-reference-id attribute (targetRefId). Because the referencing is external, it includes an
extensive list of optional metadata or attributes to provide more information about the target.
These attributes include product owner, model, serial, name, data format, data spec, etc. In
addition, a general text description can be provided with this reference.
5. External Application Reference
Sample Data keyword: "kwd:References.ExternalApp"
A reference to an electronic application can be anchored in DM content, providing a way to
launch the application from an electronic consultation tool. The application is identified by its
name and the reference would contain dedicated parameters.
Different applications can be supported depending on the need; in some cases, only specific
business applications (such as performance applications) are managed, in other cases general
applications could be supported.
An external application reference will contain alternative descriptive content in case the
referenced application is not supported.
3-3. Data Management

The Data Management section describes metadata concepts and markup mechanisms to handle
the configuration, changes, life cycle, and qualifications of the technical content. It includes
applicability management, revision management, container DM concept, unique qualifiers and
common data repositories.
3-3-1. Applicability management

Sample Data keyword: "kwd:Applicability"
1. General
Applicability provides the mechanism to identify the context for which a data module or parts
of a data module are valid for one or more configurations.
The applicability mechanism is supported by the applicability annotations and formula within
data modules (in DM Status XML fragment) and by three specific data module types:
• the Applicability Cross-reference Table (ACT) data module
• the Conditions Cross-reference Table (CCT) data module
• the Products Cross-reference Table (PCT) data module
• The ACT, CCT and PCT data modules are supported by the ApplicCrossRefTable.xsd,
CondCrossRefTable.xsd and ProductCrossRefTable.xsd schemas respectively.
2. Cross reference tables

2.1. ACT: Applicability Cross-reference Table
Sample Data keyword: "kwd:Applicability.ACT"
The Applicability Cross-reference Table (ACT) data module is used to declare product
attributes. A product attribute is a property of the Product that affects the applicability of
technical content. Product attributes are properties of the Product that are typically set at the
time of manufacture of a product instance and will usually not change throughout the service
life of a product instance. Examples of product attributes are model, series, and serial number.
The ACT data module serves as the central point of reference for applicability declarations. It
provides references to the Conditions Cross-reference Table (CCT) and Products Cross-
reference Table (PCT) data modules. By referencing the ACT data module in the DM Status
fragment, all other data modules will be able to access all declarations of product attributes
and conditions as well as actual values for product instances.
Figure 3-1 Applicability cross-reference table
The ACT data module contains the following data:

• mandatory definition of product attributes
• optional reference to the Conditions Cross-reference Table (CCT) data module
• optional reference to the Products Cross-reference Table (PCT) data module
This combination provides access to all applicability definitions and product instance values
from a single data module.
The definition of a product attribute in the ACT data module includes a mandatory unique
identifier, name and description as well as optional display name, enumeration and pattern.
The unique identifier is used to reference this product attribute from other data modules. The
name and description provide help in identifying the product attribute. The display name can
be used when generating a human readable applicability annotation. The enumeration and
pattern together define the allowable values for a product attribute.
2.1.1. Standard Product Attributes
The following table lists the standard product attributes that have been defined as part of the
ATA 2300 Specification. These product attributes are not mandatory to be in a product
deliverable. However, if any of them are applicable to the product, these standard attributes
should be used.
Product
Product Attribute Name Product Attribute Definition
Attribute ID
The registration identity assigned to an aircraft by the
acn Aircraft Registration Number cognizant international authority. The registration
number is unique to operator, country, and time.
Aircraft Basic Engineering A number assigned by the manufacturer to identify the

benbr
Number basic configuration for the aircraft design definition.
A 3 to 4-character code selected by the airline to identify

cec Customer Effectivity Code
the aircraft in the customized document.
A five-digit code assigned to identify the manufacturer of

mfr Manufacturer Code the product, normally the Commercial And Government
Entity (CAGE) code.
Identifies engine or aircraft model designation. May

model Model
include a model dash number (e.g. 747-400).
modtype Model Type Identifies an aircraft/engine model or model group.
The number assigned to identify the specific aircraft

msnbr Manufacturing Serial Number
during the production/manufacturing process.
A code which identifies the entity responsible for the

operator Operator
operations of the aircraft.
2.2. CCT: Conditions Cross-reference Table

Sample Data keyword: "kwd:Applicability.CCT"
The Conditions Cross-reference Table (CCT) data module is used to declare any condition that
can affect applicability of data. Conditions can be technical, operational, environmental, or any
other type that can affect technical content. Technical conditions are typically tied to the
configuration of the Product, such as service bulletins or modifications.
The CCT data module is divided into three sections; a definition of common types of
conditions, a definition of specific conditions, and an optional incorporation status list for
technical conditions.
Conditions in the CCT data module are defined with a two-step process. First, a general
condition type must be defined, and then a specific condition must be defined of that type. For
example, a generic service bulletin type can be defined with allowable values of "pre" and
"post", then a specific service bulletin condition can be defined for whether a service bulletin
has been incorporated ("post") or not ("pre").
The definition of a condition type in the CCT data module includes a mandatory unique
identifier, name, description and enumeration as well as an optional pattern. The unique
identifier is used to reference this condition type when defining a specific condition. The name
and description provide help in identifying the condition type. The enumeration and pattern
together define the allowable values for a product attribute.
The definition of a condition in the CCT data module includes a mandatory unique identifier,
condition type reference, name and description as well as an optional display name and
references. The unique identifier is used to reference this condition from other data modules
and from the incorporation list of this data module. The name and description provide help in
identifying the condition. The display name can be used when generating a human readable
applicability annotation. The references are used if there is additional information associated
with this condition. A common use of this is to refer to service bulletin documentation for a
service bulletin condition.
The optional incorporation status list of the CCT data module is used to document which
technical conditions have been incorporated into the associated data modules for the relevant
product instances.
2.2.1. Standard Condition Values
The following table lists standard condition values that have been defined and applicable for
all ATA 2300 products. These standard condition values must be used if they are applicable
to the product deliverable.
Condition Condition Name Enumerations Condition Definition

ID
authority Authority Specifies the regulatory authority to whose
requirements a set of flight crew data conforms.
coc Customer Originated Customer requested data to be added or removed

Change from the operator's manual. Customer-specific
data is supplied to the manufacturer for
incorporation.
mod Modification A number assigned by the manufacturer to

identify design changes to the aircraft.
sb Service Bulletin PRE The identifier of a Service Bulletin referenced

in an applicability statement.
POST
Rejected
Scheduled
Embodied
NotReported
2.3. PCT: Products cross-reference table
Sample Data keyword: "kwd:Applicability.PCT"
The Products Cross-reference Table (PCT) data module is a repository for defining product
instances and associating values to product attributes and conditions for each product instance.
It is a formal method for defining product instances and the configuration of each product
instance.
The definition of a product instance in the PCT data module includes a list of assignments of
actual values to product attributes and conditions for the product instance. Each assignment
must include the following information:
• a reference to the product attribute or condition
• an indicator whether this is a product attribute or condition
• the actual value
3. Applicability annotations and formula

3.1. Physical organization
The applicability data for a data module is delivered in the DM Status XML fragment. It is
composed of:
• An optional reference to the Applicability cross-reference table (ACT) that applies to
the data module.
• The applicability annotation of the data module
• An optional logical formula of the data module applicability
• An optional set of inline applicability annotations, for specific content elements.
3.2. Applicability annotation of the data module

Sample Data keyword: "kwd:Applicability.Annotation"
The applicability annotation of the data module provides the configuration characteristics of
the whole data module, to be able to apply a filtering mechanism.
Using the Applicability cross-reference table data module, the applicability annotation
provides resolved configuration data by giving the related products (aircraft defined within the
PCT data module) and conditions (such SB "pre" and "post" conditions defined in the CCT
data module).
The data module applicability annotation has two logical branches which are used for separate
purposes:
• A human readable applicability annotation ("displayText") which provides human
readable applicability information. This branch can be used in conjunction with the
other branch as required.
• A computable applicability annotation ("assert" and "evaluate") which provides

applicability information in a computable format which can be used to support dynamic
filtering of the annotated content.
The computable applicability annotation branch is constructed with a set of individual tests
which are grouped together to form a computable expression. Each individual test is
represented with an "assert" which specifies the product attribute or condition to test and the
values to test against. Each grouping is represented with an "evaluate" which associates the
enclosed expressions together along with a logical operation to perform, either an "and" or an
"or" operation. Groupings can contain other groupings and individual tests, thus allowing
construction of very complicated expressions where needed.
An "assert" provides for a single test for the computable branch of the applicability annotation.
The assert annotation specifies the product attribute or condition to test and a set of values
and/or ranges to test against. The result of evaluating an assert annotation will be a Boolean
value of "true" or "false".
In the case where an assert cannot be evaluated due to lack of a value to test against or the case
where only a textual annotation is provided (not referencing a product attribute or condition)
then the result must be considered the Boolean value "true".
An "assert" is composed of:
• An "applicPropertyIdent" for the identifier of either the product attribute (from the ACT
data module) or condition (from the CCT data module) to test.
• An "applicPropertyType" which indicates whether the "applicPropertyIdent" value

references a product attribute or a condition.
• An "applicPropertyValues" for the values and/or ranges to test against.
• An optional "applicDisplayClass" provides a style for formatting. The style can be used
by publication systems when generating text in a readable applicability annotation
("displayText").
An "evaluate" is used to group tests together and provide the logical operation to apply to the
test results. An "evaluate" must be used whenever more than one "assert" is required. An
"evaluate" can contain other "evaluate" and is therefore recursive. This allows for very
complicated applicability annotations to be represented with a simple structure consisting of
only two element types.
To process an "evaluate", all included "asserts" and "evaluates" are evaluated each providing
a Boolean value of "true" or "false". Then a logical "and" or "or" operation is performed on the
results, providing a single Boolean result. A result of the value, "true" means the associated
content is valid and a result of the value, "false" means the associated content is not valid.
Example:
"evaluate"
{
"assert"
applicPropertyType: product attribute
applicPropertyIdent: MSN
applicPropertyValues: 0033~0040
and
"assert"
applicPropertyType: condition
applicPropertyIdent: SB 28-1000
applicPropertyValues: post
}
It expresses that the data module is valid for aircraft with MSN include in range 0033 to 0040,
when the SB 28-1000 is embodied.
This applicability annotation, for the whole data module, always applies to all parts of the
content. Within the DM content section, it is often necessary to indicate inline applicability at
a more granular level than for the data module as a whole. Refer to [Section 3-3-1.3.4, Inline
applicability annotations]. Any inline applicability annotations addressing an element in the
DM content fragment must be covered by the applicability given at the data module level.
3.3. Logical formula of a data module applicability
In addition to the data module applicability annotation, a logical formula of data module
applicability is optionally provided. Whereas the applicability annotation of the data module
is composed of resolved configuration data (such as aircraft identification and conditions such
as SB) for filtering, the logical formula applicability provides the related logical representation
of the aircraft configuration applicable to the data module. The logical formula does not aim
at filtering, but provides the formula of technical and operational criteria that the aircraft
complies with.
The way to express a logical formula applicability is the same as the applicability annotation
of the data module. It is composed of "asserts" and "evaluates" using product attributes and
conditions defined in the cross-reference tables. Refer to [Section 3-3-1.3, Applicability
annotations and formula].
Example:
Applicability annotation:
"evaluate"
{
"assert"
applicPropertyIdent: MSN
applicPropertyValues: 0033~0040
and
"assert"
applicPropertyIdent: SB 28-1000
applicPropertyValues: post
}
Associated logical formula

"evaluate"
{
"evaluate"
{
"evaluate"
{
"assert"
applicPropertyIdent: ACModel
applicPropertyValues: 380-841
or
"assert"
}
or
"assert"
}
and
"assert"
applicPropertyIdent: MOD
applicPropertyValues: 66251
}
Results in the following applicability for the data module:

Applicable to: POST SB 28-1000 on MSN 0033~0040
Criteria: ((380-841 or 380-842 or 380-861) and 66251)
3.4. Inline applicability annotations

Sample Data keyword: "kwd:Applicability.Inline"
In case of applicability that applies to elements in the DM Content, a set of inline applicability
annotations is provided.
Each inline applicability statement is composed of:
• An applicability annotation with the same structure as the applicability annotation of
the data module. Refer to [Section 3-3-1.3, Applicability annotations and formula].
• A path (using the mechanism described in [Section 2-5-5, Addressing mechanism] to

address an element in the DM Content XML fragment.
3-3-2. Revision Management

Sample Data keyword: "kwd:RevMgmt"
1. General
Revision Management describes how changes are handled in the data and metadata at all levels.
The change mechanism includes markup for data elements, attributes, data modules, data
module status, publication modules, etc. to facilitate the life cycle of the data and its
publication.
Note: Spec 2300 uses the same revision management mechanisms for Data Modules
(DMs) and Publication Modules (PMs). For more information about DMs, refer to
[Chapter 2 DATA MODULE MANAGEMENT]. For more information about
PMs, refer to [Section 4-2 Publication Module].
Revision data in an exchange package pertain to the differences between the current and
previous deliveries.
2. Revision data
In a Flight Operation exchange package, the following revision data are provided:
• Status information
• Reasons for update
• Revision marks
Revision data are provided in the DM or PM Status XML fragment.

2.1. Status
Sample Data keyword: "kwd:RevMgmt.Status"
For each delivered data module (DM Status and/or DM Content) and each publication module
(PM Status and/or PM Content), an issue type gives the general issue status of the data module.
Possible values are:
• New: The data/publication module is newly delivered.
Sample Data keyword: "kwd:RevMgmt.Status.New"
• Changed: The content alone, or (for DM only) both content and applicability, is
changed.
Sample Data keyword: "kwd:RevMgmt.Status.Changed"
• Applicability Changed: Only the applicability is changed (applies to DM only).

Sample Data keyword: "kwd:RevMgmt.Status.ApplicChanged"
• Unchanged: No change in DM/PM Status and DM/PM Content XML fragments.
For each delivered XML fragment, the issue date (issue info) of the current fragment is
provided.
In case of a data/publication module delivered in the previous delivery, the previous issue date
is provided. It contains the issue date of the previous DM/PM Status XML fragment and allows
checking that the current revision data is consistent with the previous data/publication module
issue (the current package is related to the previous delivered package).
For each delivered data module (DM Status and/or DM Content), a DM Status entry is provided
in the Exchange Package Status List. For each delivered publication module (PM Status and/or
PM Content) a PM Status entry is provided in the Exchange Package Status List. (Refer to
[Section 4-3-8, Exchange Package Status List].
For each deleted data/publication module, a DM/PM Status entry in the Exchange Package
Status List is provided with the status set to "deleted". Deleted data/publication modules are
not delivered.
2.2. Reason for update
Sample Data keyword: "kwd:RevMgmt.RFU"
For each delivered data/publication module, reason for update (RFU) contains short
explanations of the reasons for updating the data/publication module.
Different types of RFU are:
• Technical: The change is technical.
• Editorial: The change is only editorial but no technical changes are detected.
• Other: Typically, automatic change detection of structures.
An RFU may describe one of the following content actions:
• Deleted: Gives the path of a deleted element or attribute. Refer to [Section 2-5-5,
Addressing mechanism].
• Moved: Gives the identification of an element or attribute moved from one location to
another within a data module.
• Textual content: Textual explanations.
An RFU is identified and can be global to a data/publication module or referenced by one or

more revision marks.
2.3. Revision marks
For each delivered data module, two optional separate sets of revision marks giving local
modification addresses and types are provided: revision marks of content changes, revision
marks of applicability changes.
For a delivered publication module, a set of revision marks for content changes is provided.
A revision mark is composed of:
• A change type with possible values:
o add
o modify
o move
o moveAndModify
o changeComment
▪ Used to indicate new or revised reason for update with no change to the
content
• A path to the changed node using path (for element and attributes) or extended path for
inline changes. Refer to [Section 2-5-5, Addressing mechanism].
• One or more references to reason for update giving related explanations
2.4. Change use cases

2.4.1. New data module
Case: The data module does not exist in the previous delivery.
Note: The data module may have been delivered in an earlier delivery but has been deleted.
If the data module is referenced in a publication module, it impacts a PM
content change.
Required delivered data:

• DM Status XML fragment
• DM Content XML fragment
• A DM Status entry in the Exchange Package Status List
Status:
• DM Status issue type : new (in DM Status XML fragment)
• Issue info for DM Content (in DM Status and DM Content XML fragments)
• Issue info for DM Status (in DM Status XML fragment)
• DM Status entry in the Exchange Package Status List: new
• no previous issue date
RFU:
• optional RFUs (in DM Status XML fragment)
Revision marks
• none
2.4.2. Deleted data module

Case: The data module is deleted.
Note: Deleted data are not delivered. If the data module was referenced in a publication
module, it requires a PM content change.

Status:
• DM Status entry in Exchange Package Status List: deleted
RFD:
• optional Reason For Deletion (in Exchange Package Status List)
Revision marks
• none
2.4.3. DM Content changed

Case: The content of the data module changes.
Note: Applicable to data modules for both flight operations data and data modules for
management.

Status:
• DM Status issue type : changed (in DM Status XML fragment)
• Issue info for DM Content updated (in DM Status and DM Content XML fragments)
• Issue info for DM Status updated (in DM Status XML fragment)
• DM Status entry in the Exchange Package Status List: changed
• Previous issue date (in DM Status XML fragment)
RFU:
Revision marks
• Revision marks for content that has changed in the DM Content XML fragment (in DM
Status XML fragment)
2.4.4. Applicability-only changes

Case: Only the applicability changes.
Note: For revised-only deliveries, the DM content XML fragment is not delivered. Refer
to [Section 4-3-3, Delivery scope].
Status:
• DM Status issue type : applicability changed (in DM Status XML fragment)
• Issue info for related DM Content not updated (in DM Status)
• DM Status entry in the Exchange Package Status List: applicability changed
RFU:
Revision marks
• Revision marks for applicability that has changed in the DM Status XML fragment (in
DM Status XML fragment)
2.4.5. Applicability and content changed

Case: The applicability and the content of the data module changes.
Status:
• DM Status issue type : changed (in DM Status XML fragment)
• Issue info for DM Content updated (in DM Status and DM Content XML fragments)
• DM Status entry in the Exchange Package Status List: change
RFU:
Revision marks
• Revision marks for content that has changed in the DM Content XML fragment (in DM
• Revision marks for applicability that has changed in the DM Status XML fragment (in
DM Status XML fragment)
2.4.6. Data module unchanged

Case: The data module is unchanged, but has been delivered in the previous delivery with
revision data.
Note: Revision marks and RFU of previous delivery must be removed. The DM Status
XML fragment is delivered for this reason.

Status:
• DM Status issue type : unchanged (in DM Status XML fragment)
• Issue info for DM Content not updated (in DM Status XML fragment)
• Issue info for DM Status updated
• DM Status entry in the Exchange Package Status List: unchanged
• Previous issue date updated (in DM Status XML fragment)
RFU:
• none
Revision marks
• none
2.4.7. Graphic and multimedia changes
Note: Graphic and multimedia changes are considered as content changes. Revision marks
are provided on the referencing elements in the DM Content XML fragment.
2.4.8. New publication module

Case: The publication module does not exist in the previous delivery.
Note: The publication module may have been delivered in an earlier delivery but has been
deleted.

• PM Status XML fragment
• PM Content XML fragment
• A PM Status entry in the Exchange Package Status List
Status:
• PM Status issue type : new (in PM Status XML fragment)
• Issue info for PM Content (in PM Status and PM Content XML fragments)
• Issue info for PM Status (in PM Status XML fragment)
• PM Status entry in the Exchange Package Status List: new
• no previous issue date
RFU:
• optional RFUs (in PM Status XML fragment)
Revision marks
• none
2.4.9. Deleted publication module

Case: The publication module is deleted.
Note: Deleted data are not delivered.

Status:
• PM Status entry in Exchange Package Status List: deleted
RFD:
• optional Reason For Deletion (in Exchange Package Status List)
Revision marks
• none
2.4.10. PM Content changed

Case: The content of the publication module changes.
• PM Content XML fragment
Status:
• PM Status issue type : changed (in PM Status XML fragment)
• Issue info for PM Content updated (in PM Status and PM Content XML fragments)
• Issue info for PM Status updated (in PM Status XML fragment)
• PM Status entry in the Exchange Package Status List: changed
• Previous issue date (in PM Status XML fragment)
RFU:
• optional RFUs (in PM Status XML fragment)
Revision marks
• Revision marks for content that has changed in the PM Content XML fragment (in PM
2.4.11. Publication module unchanged

Case: The publication module is unchanged, but has been delivered in the previous delivery
with revision data.
Note: Revision marks and RFU of previous delivery must be removed. The PM Status
XML fragment is delivered for this reason.

Status:
• PM Status issue type : unchanged (in PM Status XML fragment)
• Issue info for PM Content not updated (in PM Status XML fragment)
• Issue info for PM Status updated
• PM Status entry in the Exchange Package Status List: unchanged
• Previous issue date updated (in PM Status XML fragment)
RFU:
• none
Revision marks
• none
2.4.12. Changes to Metadata only

Case: The data module content is unchanged, but there has been a change to one or more
metadata items (other than applicability). For example, approval data, subset data or reason for
update.
Note: For revised-only deliveries, the DM content XML fragment is not delivered. Refer
to [Section 4-3-3, Delivery scope].
Status:
• DM Status issue type: metadataChanged (in DM Status XML fragment)
• Issue info for related DM Content not updated (in DM Status)
• DM Status entry in the Exchange Package Status List: Metadata only has changed
RFU:
Revision marks
• Revision marks for metadata that has changed in the DM Status XML fragment (in DM
3-3-3. Container and Alternate Data Modules

Sample Data keywords: "kwd:ContainerAlternateDM"
The Container Data Module is a production management mechanism to associate several data
modules representing the same data. The grouping of data modules can be used when several
data modules achieve the same goal, but the detailed content differs due to aircraft
configuration.
A container data module is considered as a configuration independent interface for a group of
data modules (called alternates).
Figure 3-2 Container and alternate DMs
For example, a container data module can be used to associate two data modules giving the
description of a control-indicator with different content depending on the data module
applicability. To define this, a container data module (using the Container schema) is delivered
including the references to the two ControlIndicator DMs called alternate data modules. It
allows clearly identifying that the two alternate ControlIndicator DMs deal with the same
subject (description of a specific control-indicator) but for two different aircraft configurations
(and different applicabilities).
A container DM is identified by the Disassembly Code Variant (refer to [Section 2-3-1.1.5,
Disassembly Code Variant] for specific details) and uses the same SNS and information code
as the referenced alternate DMs. In each of the referenced alternate DMs, aircraft configuration
differences can be identified by using the Disassembly Code Variant (DCV). System
differences (e.g., engine manufacturer) between alternate DMs can be identified by using the
System Difference Code (SDC).
Figure 3-3 Container and Alternate Identification Example
Using a container data module also allows making links independent of

configuration/applicability.
When not using a container data module, if a data module includes a link to other data modules
with different configurations, specific links to each target data module must be provided.
For example, if a ControlIndicatorArrangement DM gives a link to a control-indicator
description provided by two different ControlIndicator data modules for different
applicabilities, two different direct links are provided. Using a container data module to group
the two ControlIndicator data modules allows making a single link to the container DM,
independent of source and target configurations.
The actual link target is then dynamically resolved by a data processing application, providing
the effective alternate target DM for a given applicability.
Figure 3-4 Container DM Example
As the container is configuration independent, referencing a Container Data Module has

several benefits for data management and referencing purposes:
• Reduction of configuration dependencies between data modules
A container data module limits the impact of evolutions linked to configuration.
For example, if a data module directly links to another data module, a configuration
change (on source or target data module), may require that the link be updated. When
using a container data module as the target of a link, a configuration change has no
impact on the link definition.
Figure 3-5 Container DM links
• Consistency of links
The container data module helps to maintain the consistency of links by centralizing
the link management and providing the capability to define the linking at the source
instead of at the point of usage.
• Configuration consistency checks
The configuration consistency between various alternate data modules can be

maintained. At a given moment in time (i.e., for a given aircraft configuration and under
a given operational condition), only one alternate data module is applicable for a
container data module. The applicability of one referenced data module within a
container must not overlap the applicability of any other referenced data module within
the same container.
3-3-4. Information Repositories

Sample Data keyword: "kwd:Repository"
1. General
Data repositories are data module types that provide data (such glossary or data qualifiers) as
factorized in a single data module and referenced from the content or status parts of other data
modules. In other words, data repositories are not technical content data modules but a kind of
reservoir of data used by other data modules.
Typically, in the content of a technical repository, if an abbreviation is set in a paragraph, the
abbreviation definition by itself is not embedded in the content but is available in the Glossary
repository. This repository contains all definitions that are referenced by all other data modules.
A Data Repository DM has its own life cycle and is independent of the other data modules
which reference it.
2. Repository types
2.1. Glossary Repository
Sample Data keyword: "kwd:Repository.Glossary"
Glossary Repository contains the terms and definitions of acronyms and abbreviations that are
used in the technical content for a given data exchange package. The acronym or abbreviation
in the content contain no terms or definitions, but a reference to an applicable item in the
Glossary repository to obtain the information.
2.2. Dispatch Qualifier Repository
Sample Data keyword: "kwd:Repository.DispatchQualifier"
Dispatch Qualifier Repository provides dispatch qualifications that are used in dispatch items.
Some dispatch conditions in a dispatch item of the MMEL have an impact on the operation of
the aircraft.
Typical impacts can be:
• On the performance of the aircraft, such as takeoff weight penalties or increased fuel
consumption
• On the operational envelope of the aircraft, such as ceiling limitation
• On the use of the aircraft, such as limitations on ETOPS flights
The dispatch qualification concept provides the ability to identify a dispatch condition or a
proviso that impacts the operation of the aircraft, and can provide the associated impacts.
2.3. Avionics Qualifier Repository
Avionics Qualifier Repository provides avionic contexts used for avionics qualifiers. When
an Electronic Flight Bag (EFB) is connected to the avionics system of the aircraft, the
electronic documentation module can receive data from the aircraft avionics systems.
This is known as contextual access which provides the flight crew an easy and rapid way of
accessing information without needing to know the manual’s structure and/or where to look
for relevant information.
The avionics qualifiers concept specifies data received from the avionics system that is
associated with a data module or part of a data module.
2.4. Link Target Repository
Link Target Repository identifies DM references that are not delivered as part of the exchange
package in the current deliverable. A link is defined from one source data module to another
target data module in the context of a Publication Module. The summary data for each link is
composed of:
• Source data module identifier in which the link can be found
• Target information: target data module identifier, title, product code of the publication
module in which the target is found, and a textual description of the location of a link
target within a PM.
3. Repository Schema Mapping

The following table lists the Repository Data Modules and the corresponding XML Schemas
used for each DM:
DM Type Schema
Avionics Qualifier
QualifierRepository.xsd
Dispatch Qualifier
Glossary GlossaryRepository.xsd
Link Target LinkTargetRepository.xsd
4. Repository Mechanism
4.1. Reference between data and repository
When a data module (content or metadata) uses data from a data repository, the data is not
embedded in the content or status part of the DM, it is just referenced, using the data identifier.
Figure 3-6 Reference to a data repository
For example, in the technical content module content of DM x, a paragraph contains the
abbreviation "FMS". The mechanism is:
• The Glossary repository contains a data "glossary item" with an ID [id=n], that gives
the definition of FMS ("Flight Management System"). This definition is provided only
once, in the data repository.
• The paragraph in DM x content contains a reference to the glossary item [id=n] using
a specific element "abbreviation". The term and the definition of the abbreviation are
not embedded in the DM x content but only referenced.
• The glossary item [id=n] can be referenced by any other element abbreviation in the
content of any other data modules.
In this way, the resolution is dynamic. A process (such as publication process) uses the
reference to the data repository to get the effective value of the data referenced from any data
module.
Data that is included in data repositories is defined once, and is usable in any data module, by
using specific elements to reference it.
4.2. Qualifier Repository addressing
To define the possible qualifier definitions, data repository data modules called Avionics
Qualifier Repository and Dispatch Qualifier Repository are provided. A common mechanism
is used to define the qualifiers and address qualifiers for a data module.
Qualifiers are defined by using a recursive structure in the data repository. The definition of a
qualifier uses the following rules:
• A qualifier represents a category or a sub-category (recursively) or a property
o identified by an ID (allowing to be referenced)
o with an optional display Name used for a user-friendly display
o the qualifier name provides a category name or a property value
o an optional description of qualifier is provided
• A qualifier can have sub-categories or properties
o qualifiers are defined recursively in a qualifier
• In case of non-discrete value
o A "local value" specifies that the qualifier has no specified value. It means that the
value should be defined by the reference (i.e. locally)
o Optionally, a value pattern (using regular expression) gives constraints on local

values
o Optionally a set of enumerations gives values or ranges of values for the locally
defined value.
For example, the following case:

Figure 3-7 Dispatch qualifier repository, Example
It defines the following dispatch qualifiers:
• Performance impacts, with sub qualifiers:
o Impact on the POF (Phase Of Flight) "Take-off", "En-route"
o Impact on the FL (Flight Level) 250 and 420
o Impact on speed, locally defined value, expressed with 1 or more digit.
• Maintenance "flight conducted unpressurized"
When a data module is associated to qualifier, a reference is given in its DM Status using a
"qualification" containing the definition ID. It can be completed, if required by a locally
defined value.
When a content element is impacted, the "qualification" in the DM status uses an XPATH to
address the related element in the DM Content. Refer to [Section 2-5-5, Addressing
mechanism].
For example, when a dispatch condition is qualified by a Dispatch qualifier, the qualifier ID is
set in a qualification in the DM Status allowing reference to a qualifier defined in the data
repository. If needed, a local value can be defined, following the value pattern or the set of
enumerations defined in the repository. The DM Status qualifications use XPATH to address
dispatch condition elements in the DM Content to make the association of qualification and
content element.
Figure 3-8 Reference to dispatch qualifier for dispatch conditions
In this case, the first dispatch condition is qualified as "Performance impacts". The label "A",
defined as display name in the qualifier definition of the data repository can be displayed. The
second dispatch condition is qualified as "Performance impacts, FL = 250". Finally, the third
dispatch condition is qualified as "Performance impacts, Speed" set to a local value "300".
3-3-5. Software Parameters

In the electronic paradigm, electronic data is generally consumed by software applications.
Inevitably, certain data contain values that can be parsed as input into an application. For
example, Weight and Balance data provided through the WBM can feed an application to
compute a Load & Trim Sheet. Spec 2300 provides a mechanism for defining software
parameters for one or more software applications, allowing them to retrieve parameter values
from the data set.
Declarations in the DM Status XML fragment define software parameters. An XPATH address
is used to locate the elements in the DM content that contain the parameter values. Refer to
[Section 2-5-5, Addressing mechanism].
Software parameters may target a single element or a full table column (i.e., simple or table
parameter). A supplementary context structure can be applied to parameter definitions to allow
a software application to provide context driven results.
Figure 3-9 Software parameter addressing mechanism
DM Status DM Content
Measurement of the fuel properties is necessary to ensure the aircraft systems
Simple Parameter use accurate data for fuel quantity measurement, fuel system management,
Name=FUELDENSITY xpath and fuel quantity indication.
Fuel properties sensors mounted on the aircraft transmit Permittivity (or
Label=”Density” Dielectric), Density and Temperature signals to the Fuel Quantity Management
System (FQMS) computers, for use in the aircraft system.
The fuel quantities and units used in the manual are based on the following:
- fuel quantities are shown in liters and us gallons.

- metric fuel weights are based on a fuel density of 0.785 kg/l
Simple Parameter
Name=FWDCANTHARM
Label=”H-arm” xpath
Context
Name=FWDCANTER
Label=”Frame” This chapter contains the maximum cumulative load per
Value=”46" loading zone for the forward fuselage area in front of frame
46H-ARM=31.496m (1240.00 in) and in the aft fuselage area
aft of frame 56 H-ARM=38.100m (1500.00 in).
Simple Parameter
Name=AFTCANTHARM
Label=”H-arm”
Context xpath
Name=AFTCANTER
Label=”Frame”
Value=”56"
Table Parameter
xpath col1 col3 col5
Context ColumnParam
Name=TABFUEL ColName=”col1"
Label=”Table” Name=FUELSAVOL
Value=”Quantity" Label=”Quantity”
Context ColumnParam
Name=FUELTYPE ColName=”col3"
Label=”Fuel Type” Name=FUELUSAHARM
Value=”Usable" Label=”H-arm”
Context ColumnParam
Name=FUELUSATANK ColName=”col5"
Label=”Tank name” Name=FUELUSAYARM
Value=”Outer tank" Label=”Y-arm”
Context
Name=FUELUSAPOS
Label=”Tank position”
Value=”RH"
In addition to targeting an entire table column, the table parameter structure can be used to
target specific elements within the table.
Figure 3-10 Simple parameters within a table parameter structure
Table Parameter
xpath
col1 col2 col3
Context ColumnParam
Name=TABLIM ColName=”col1"
Label=”Table” Name=WVDESIG
Value=”Design Weight" Label=”Designation”
Context ColumnParam
Name=WVNUM ColName=”col2"
Label=”Weight Variant” Name=WVCG
Value=”000" Label=”Aircraft CG”
ColumnParam
ColName=”col3"
Name=WVMAXWEIGHT
Label=”Maximum weight”
Simple Parameter
Name=WVMTW xpath
Label=”MTW”
Simple Parameter
Name=WVMTOW xpath
Label=”MTOW”
Simple Parameter
Name=WVMLW
Label=”MLW” xpath
3-3-6. Additional Parameters
Additional Parameters are extra input parameters that are needed by a software application,
but are not included in the DM Content of a publication. In other words, they’re not referenced
by the PM but can be delivered in an exchange package. The additional Parameters DM uses
a specific XML schema to specify its content with a dedicated info-code, but uses the same
mechanism as the software parameter to reference between the DM Status and its Content.
3-4. Flight Operations Technical Content

3-4-1. Common Data
1. General
This section provides usage rules for common data elements that are applicable to more than
one Flight Operations information domain. The common data elements are below the data
module level and their associated schemas. Thus, this section contains no data module
definition and schema mapping guide.
2. Content Guidelines
Data Element XML Location in

Usage Rules
Tag Type Schema
Although this element is in the DMC, and
dispatchItemExtension Element Available in all
therefore is found in all Data Module schemas,
Code schemas dispatchItemExtensionCode shall be used only in
the Dispatch schemas (see [Section 3-4-3.3
Dispatch Data DM and Schema Mapping]).
electronicMessage Element Available in all An electronic message may contain a leading
schemas system name.
If the system name is specified in the
systemName element under the
electronicMessage element, then the content in
the systemName is concatenated with the
content in the message element to become a
complete electronic message.
If the system name is not specified, the content
of the message element is the only content for
the electronic message.
figure Element equation Used only to provide a graphical representation

of the equation.
measureBlock Element Available in all measureBlock consists of exactly two measure

schemas elements. The two measure elements must
convey the same type of measurement category
and subcategory from two different
measurement systems.
For category and subcategory values, reference
the Appendix 1 at the end of the specification.
3-4-2. Approval Data

1. General
Approval Data is one of the information domains in the Flight Operations documentation. It
is specific to document and/or information in a document that a Regulatory Agency or an
Organization must approve (e.g. AFM, MMEL). Approval data may be applicable to one or
more data modules, a publication module, revision cycle, or subset (e.g., a bulletin or
temporary add-on).
2. Approval Data Modules
Sample Data keyword: "kwd:ApprovalDM"
Approval Data Modules accompany the product or dataset that the approval information is
applicable to in a data exchange package. They contain the approval information such as
regulatory standard, approval agency, signature block, approver, approver title, date, etc.
including references to external approval information or documents.
Following are the Approval data modules and their descriptions:
• Initial Approval DM: The Initial Approval DM contains the first-time approval
information for a publication as defined by a Publication Module and associated Data
Modules.
• Revision Approval DM: The Revision Approval DM contains the approval

information for a revision of a publication as defined by a Publication Module and
associated Data Modules.
• Temporary Add-on Approval DM: The Temporary Add-on Approval DM contains

the approval information for one or more Data Modules that are provided
independently of a revision cycle, managed as a subset.
• SubSetHeader DM: The Subset Header DM contains the identification and approval
information of a subset and its applicability to the product.
3. Approval DM and Schema Mapping

The following table lists the Approval Data Modules and the corresponding XML Schema
used for each DM:
DM Type Schema
Initial Approval
Approval.xsd
Revision Approval
Temporary Add-on Approval

SubSetHeader.xsd
SubSetHeader
There are no specific usage rules for this content. Refer to [Appendix 4, Data Dictionary] for
element and attribute definitions.
3-4-3. Dispatch Data

Sample Data keyword: "kwd:DispatchData"
1. General
Dispatch Data is one of the information domains in the Flight Operations documentation.
Dispatch information is used to describe aircraft systems or components that may be
inoperative or missing without affecting the safe operation of the aircraft. Dispatch Data
provided by an aircraft manufacturer (OEMs) contains a copy of the Regulatory-approved
Master Minimum Equipment List (MMEL) or Configuration Deviation List (CDL). This data
is used by airlines as the basis for their aircraft Minimum Equipment List (MEL).
Dispatch information is categorized by the ATA Standard Numbering System as described in
iSpec 2200, plus an optional Dispatch Item Code Extension.
The Dispatch Item provides the information needed by the crew to safely operate the aircraft
with a given fault or inoperative system. Each dispatch item is contained in one Dispatch Item
DM. The Dispatch Item may also contain one or more dispatch conditions. Dispatch
conditions may contain one or more qualifiers for those conditions. Dispatch conditions may
require specific maintenance and/or operational procedures which must be accomplished as a
condition for safe dispatch. These maintenance and operational procedures are described in
their own data modules.
2. Dispatch Data Modules
Following are the Dispatch data modules and their descriptions:
• CDL Item DM: Each CDL Item DM contains information related to a single aircraft
component that may be missing for dispatch as allowed by the approved Configuration
Deviation List (CDL).
Sample Data keyword: "kwd:DispatchData.CDL"
• Dispatch Item (LRU) DM: Each Dispatch Item (LRU) DM contains information
related to a single system or component which may be inoperative for aircraft dispatch
as allowed by an approved Master Minimum Equipment List (MMEL). The DM
contains information such as dispatch conditions (one or more), equipment location
and description. It also provides implicit references to any applicable maintenance and
operational procedures.
Sample Data keyword: "kwd:DispatchData.DispatchItem"
• Dispatch Item (Message Oriented) DM: Each Dispatch Item (Message Oriented)
DM contains information related to a single system or component which may be
inoperative for aircraft dispatch as allowed by an approved Master Minimum
Equipment List (MMEL). The DM contains information such as dispatch conditions
(one or more), equipment location and description. It also provides implicit references
to any applicable maintenance and operational procedures.
Sample Data keyword: "kwd:DispatchData.DispatchItem"
• Dispatch Locator DM: Each Dispatch Locator DM contains an intelligent graphic

with hotspots and/or textual architecture description typically depicting where
Dispatch/CDL items are located and is composed to allow for interactive and direct
navigation to another Data Modules or an internal/external reference.
Sample Data keyword: "kwd:DispatchData.DispatchLocator"
• M Note DM: Each M Note DM contains maintenance information which is not

required by an approved MMEL or CDL item but typically advises the operator of
interrelated systems effects. The DM may contain the same type of content as an
mProcedure DM.
• M Procedure DM: Each M Procedure DM describes a specific maintenance procedure

which must be accomplished when operating with the listed item inoperative or
missing. The DM contains a procedure title, general description of the procedure and
procedural steps (including multiple sub levels), actions and other types of maintenance
content.
Sample Data keyword: "kwd:DispatchData.DispatchProcedure.MProcedure"
• O Note DM: Each O Note DM describes operational information which is not required
by an approved MMEL or CDL item but typically advises the operator of interrelated
systems effects. The DM may contain the same type of content as an oProcedure DM.
Sample Data keyword: "kwd:DispatchData.DispatchProcedure.ONote"
• O Procedure DM: Each O Procedure DM describes a specific operational procedure

which must be accomplished when operating with the listed item inoperative or
missing. The DM contains a procedure title, general description of the procedure and
procedural steps (including multiple sub levels), actions and other types of operational
content.
Sample Data keyword: "kwd:DispatchData.DispatchProcedure.OProcedure"
• System Fault and Dispatch Cross Reference DM: The System Fault and Dispatch
Cross Reference DM contains fault information related to a single cockpit/flight deck
electronic display (ECAM/EICAS) message or any other malfunction (crew
observation, local warning, etc.). Each single cockpit/flight deck display message or
other malfunction can have one or several triggering causes. For each cockpit/flight
deck display message or other malfunction, the System Fault and Dispatch Cross
Reference DM may include a description of the triggering causes and/or actions to
perform for differentiating the triggering causes. The intent is to identify the triggering
cause and direct the user to the appropriate Dispatch Item DM(s).
Sample Data keyword: "kwd:DispatchData.SystemFault"
3. Dispatch Data DM and Schema Mapping
The following table lists the Dispatch Data Modules and the corresponding XML Schemas
used for each DM:
DM Type Schema
CDL Item CdlItem.xsd
Dispatch Item (LRU)

DispatchItem.xsd
Dispatch Item (Message Oriented)
Dispatch Locator DispatchLocator.xsd
M Procedure
M Note
DispatchProcedure.xsd
O Procedure
O Note
System Fault and Dispatch Cross

SystemFault.xsd
Reference
4. Dispatch Content Guidelines

This section provides business rules and markup guidelines that are applicable to the Dispatch
data module types. If there is no specific rule or guideline for a data module, then that data
module is not included in this section.
4.1. CDL Item
Data Element XML

Location in Schema Usage Rules
Tag Type
placard Element cdlItem The use of placard is exclusive. It may be
used at the cdlItem level or
cdlItem/dispatchCondition
normalDispatchCondition level but not
/normalDispatchCondition
both.
4.2. Dispatch Item
XML
Data Element Tag Location in Schema Usage Rules
Type
title Element dispatchItem Can contain the name of the LRU
(Information Code = 12B) or electronic
message (message-oriented dispatch,
Information Code = 12C).
placard Element dispatchItem The use of placard is exclusive. It may be

used at the dispatchItem level or
normalDispatchCondition level but not both.
numberInstalled Attribut dispatchItem Use "N/A" if this is a message-oriented

e dispatch item (Information Code = 12C)
numberRequired Attribut dispatchCondition/ Use "N/A" if this is a message-oriented

e normalDispatchCondition dispatch item (Information Code = 12C)
4.3. Dispatch Locator
XML
Type
figure Elemen dispatchLocator Used to provide visual guidance about the
t location of the dispatch item.
3-4-4. Front Matter Data

Sample Data keyword: "kwd:FrontMatterData"
1. General
Front Matter Data is one of the information domains in the Flight Operations documentation.
The Front Matter is used to introduce the information contained in each of the Flight
Operations Data sets. It is a generic data module that can be adapted to present many different
sections, such as MMEL Preamble, CDL Preamble, General Introduction, Local Introduction,
and Transmittal Letter.
2. Front Matter Data Modules
Following are the Front Matter data modules and their descriptions:
• CDL Preamble DM: The CDL Preamble DM introduces the Configuration Deviation
List (CDL).
• Definition DM: Each Definition DM contains complete and fully descriptive

information about a nomenclature or unique phrase.
• General Introduction DM: The General Introduction DM introduces an entire data
set.
• Local Introduction DM: Each Local Introduction DM introduces a section of a data

set.
• MMEL Preamble DM: The MMEL Preamble DM introduces the Master Minimum
Equipment List (MMEL).
• Transmittal Letter DM: The Transmittal Letter DM describes the contents of an

exchange package.
• Supplementary Content DM: The Supplementary Content DM provides references

to additional materials that are delivered in a non-Spec 2300 format. The Aircraft
Weighing Report is an example of this type of data.
3. Front Matter DM and Schema Mapping

The following table lists the Front Matter Data Modules and the corresponding XML Schemas
used for each DM:
DM Type Schema
CDL Preamble
Definition
General Introduction
FrontMatter.xsd
Local Introduction
MMEL Preamble
Transmittal Letter
Supplementary Content SupplementalContent.xsd
3-4-5. Limitations Data

Sample Data keyword: "kwd:LimitationsData"
1. General
Limitations Data is one of the information domains in the Flight Operations documentation.
For flight crew operations data, Limitations are used to define the envelope within which the
aircraft must be operated to ensure safe operation. The data are related to the operational and
performance parameters or restrictions. For weight and balance data, Limitations pertain to
allowable or certificated weight limits.
2. Limitations Data Modules
Following are the Limitations data modules and their descriptions:
• Limitations DM: The Limitations DM is used to provide information that is
specifically required by a regulatory authority, and may not be changed without
approval. The Limitations DM may also be used to provide information that is
identified by the airline, OEM, or associated regulatory authority and not otherwise
provided.
• Operational Capabilities DM: The Operational Capabilities DM is used to provide

information about an aircraft’s enhanced capabilities to operate and which require
separate approval from a regulatory authority, e.g., RNP, ETOPS, etc.
3. Limitations DM and Schema Mapping

The following table lists the Limitations Data Modules and the corresponding XML Schemas
used for each DM:
DM Type Schema
Limitations
Limitation.xsd
Operational Capabilities
3-4-6. Performance Data

Sample Data keyword: "kwd:PerformanceData"
1. General
Performance data is one of the information domains in the Flight Operations documentation.
Performance data specifies aircraft performance for different operational environments or
conditions. Performance data aids the flight crew with safe operation of the aircraft in standard
and some non-standard configurations. In the publication form, it’s usually expressed in a very
complex table structure. In the digital aircraft environment, a performance application would
provide precise calculation and parameters of any given operational environments or
conditions.
2. Performance tables
Performance tables are specifically designed to convey aircraft performance data and use a
more complex data structure than a standard table.
Typically, a table can contain:
• Header rows and columns
• Table body
• Footer rows.
Some Performance tables can contain additional elements, such as:

• Common conditions: Values of parameters that apply for the whole table body (e.g.
thrust setting, anti-icing conditions, type of engine, …)
• Value legends: Definitions of the parameters stored in table body cell.
• Split definitions: Definitions of splits applied in the table body, in the case of cells in
the table body that are linked with different conditions
• Correction type: Types of corrections that are linked with parameters that have an
influence on the performance values
• Corrections value: Name and value of the parameters, and values of the corrections to
be applied
The two examples below show performance tables:
Figure 3-11 Performance Table examples
TAKE OFF THRUST

ENG XXX
Common conditions
AIR CONDITIONING ON
PRESSURE ALTITUDE (FT)
OAT (C) Column definitions
-2000 0 2000 4000 6000 8000 10000
10 98.1 97.8 97.6 97.4 97.2 96.8 96.6
15 98.1 97.8 97.6 97.4 97.2 96.6 96.2
Row
20 98.1 97.8 97.6 97.4 97.2 96.4 96.2 Table body
Values
25 98.1 97.8 97.6 97.3 97.1 96.3 96.0
30 98.1 97.8 97.6 97.2 96.9 96.2 95.8
OAT < CORNER POINT OAT > CORNER POINT Split definition
OAT < CORNER OAT > CORNER

THR CORRECTION FOR BLEED Correction types
POINT POINT
AIR CONDITIONING OFF THR = 100.0
ENG ANTI ICE ON 0.0 -1.7 Correction values
ENG AND WING ANTI ICE ON 0.0 -1.7
CRUISE – M.80
Common MAX CRUISE THRUST LIMIT ISA N1 (%) MACH
NORMAL AIR CONDITIONING CG = 37.0% KG/H/ENG IAS (KT) Value legends
conditions
ANTI-ICING OFF NM/1000KG TAS (KT)
header
FLIGHT LEVEL
WEIGHT
Column definitions
(1000KG) FL290 FL310 FL330 FL350 FL370 FL390 FL410
88.4 .800 88.3 .800 88.3 .800 88.3 .800 88.8 .800 90 .800 91.3 .800
130 2867 311 2672 297 2491 281 2330 272 2203 260 2108 248 2033 237
82.6 473 87.6 469 93.1 465 98.9 461 104.1 459 108.8 459 112.8 459
Table body
88.8 .800 88.8 .800 88.8 .800 88.9 .800 89.6 .800 90.9 .800 92.3 .800
140 2916 311 2722 297 2546 281 2395 272 2274 260 2189 248 2127 237
81.2 473 86.2 469 91.1 465 96.3 461 100.9 459 101.8 459 107.9 459
PACK FLOW HI
ENGINE ANTI ICE TOTAL ANTI ICE Correction types
PACK FLOW LO OR/ AND CARGO
footer ON ON
COOL ON
FUEL=0.5% FUEL=+1% FUEL=+1.5% FUEL=+3% Correction values
3. Performance Data Modules

Following are the Performance data modules and their descriptions:
• Performance DM: The Performance DM contains the performance data in text, tables
or graphics.
Sample Data keyword: "kwd:PerformanceData.PerformanceDM"
• Performance Application User Guide DM: The Performance Application User
Guide DM is used to provide instructions on using performance data or/and
performance software.
Sample Data keyword: "kwd:PerformanceData.AppUserGuide"
• Performance How-To Instruction DM: The Performance How-To Instruction DM

is used to provide instructions on how to read, interpret or perform calculations from
the values that are specified in a performance table or a set of performance tables.
• Summary Performance DM: Each Summary Performance DM contains aircraft

performance information specifically related to a non-normal aircraft configuration that
results from aircraft system malfunction and the accomplishment of the appropriate
non-normal/abnormal/emergency checklists or procedures.
Sample Data keyword: "kwd:PerformanceData.PerformanceDM"
4. Performance DM and Schema Mapping

The following table lists the Performance Data Modules and the corresponding XML Schemas
used for each DM:
DM Type Schema
Performance
Performance.xsd
Summary Performance
Performance How-To
Instruction
SystemDescription.xsd
Performance Application User
Guide
Data Element XML Location in

Usage Rules
Tag Type Schema
<commonCondition> may not be empty. It
commonCondition Element performance//*
must contain at least one child element.
techLabel Element performance/perfoConten Use <techLabel> to set the performance

t/digitalPerformanceInfo/ database reference per the following
perfoDatabaseVersion/ifI example:
nstalled
<techLabel
type="perfoDatabaseRef">ABBE861A04</
techLabel>
3-4-7. Procedures Data

Sample Data keyword: "kwd:ProceduresData"
1. General
Procedures Data is one of the information domains in the Flight Operations documentation.
The Procedures information is used to safely operate the aircraft systems through all phases of
flight, under normal and non-normal conditions. Procedures can be presented in both checklist
format and expanded procedures formats. Checklists contain only crew actions. Expanded
procedures contain both crew actions and expanded information about system responses, limits
and aircraft performance data.
Procedures data can be divided into:
• Normal Procedures
• Supplementary Normal Procedures
• Special Operations Normal Procedures
• Abnormal/Non-Normal Procedures
• Emergency Procedures
• Supplementary Non-Normal Procedures
• Special Operations Non-Normal Procedures
• Cabin Equipment Malfunction Procedures
• Cabin Equipment Malfunction Decision Tree
Normal Procedures are used by the flight and cabin crews on every flight. Flight crew normal
procedures follow a hierarchy of actions and comments based on a scan-flow of the flight-
deck/cockpit physical arrangement. The aircraft is prepared for each subsequent phase of flight
by positioning controls and monitoring responses, as needed before moving to the next phase
of flight. Normal Procedures can be presented as a series of actions based on scan flow or in
a task-sharing table.
Normal Checklists are Normal Procedure DMs that contain only the required flight crew
actions to verify that the aircraft has been safely prepared for the next Phase of Flight.
Supplementary Normal Procedures and Special Operations Normal Procedures are used by
flight crews for normal operations under non-standard configurations and special situations.
Special Operations Normal Procedures and Supplementary Procedures use the Normal
Procedures DM.
Abnormal/Non-Normal Procedures and Emergency Procedures are used by flight crews to
manage non-normal, abnormal and emergency situations. All checklists have a condition
statement. The conditions statement briefly describes the situation being encountered by the
flight crew. Additional information, such as a representation of flight deck lights and other
indicators may also be included. This information is contained in an Annunciations Data
Module. A series of flight crew actions to correct the situation follows. If needed, information
for planning the rest of the flight is presented. Some checklists will have an objective
statement. The objectives statement briefly describes the expected result from doing the
checklist. The objective statement and crew actions and information are contained in a Non-
Normal Procedures Data Module. Some checklists have additional information presented at
the end of the checklist. This type of information can include Associated Procedures,
Inoperative Systems, Deferred Normal Checklists, System Restrictions, Redundancy Losses,
etc. Additional information is contained in the Failure Consequences data module.
Supplementary Non-Normal Procedures and Special Operations Non-Normal Procedures are
used by flight crews for non-normal operations under non-standard configurations and special
situations. Special Operations Non-Normal Procedures and Supplementary Non-Normal
Procedures use the same DMs as the Abnormal/Non-Normal and
Emergency Procedures.
Normal and Non-Normal Procedure and Checklist DMs can also be created for cabin crew
operations. Cabin Equipment Malfunction Procedures and Cabin Equipment Malfunction
Decision Tree are used by cabin crews to perform or make decision in case an equipment used
in the cabin is malfunction.
2. Procedures Data Modules
Following are the Procedures data modules and their descriptions:
• Cabin Equipment Malfunction Decision Tree DM: Each Cabin Equipment
Malfunction Decision Tree DM contains yes/no-type questions and answers for cabin
crews to diagnose an equipment malfunction by narrowing down the symptoms to
reach a final resolution.
• Cabin Equipment Malfunction Procedure DM: Each Cabin Equipment Malfunction

Procedure DM contains procedural and descriptive information to assist cabin crews to
understand and resolve an equipment malfunction.
• Failure Consequences DM: Each Failure Consequences DM contains detailed

information on the consequences of the failure associated to a non-normal procedure.
Information provided can include associated procedures, secondary failures, system
restrictions, deferred procedures, inoperative items, status information, redundancy
losses, additional descriptive information or information from the memo page of a
cockpit/flight deck electronic display (ECAM/EICAS).
Sample Data keyword: "kwd:ProceduresData.FailureConsequences"
• Flight Profile DM: Each Flight Profile DM contains a graphical depiction of a flight
crew procedure. Flight Profile DMs are provided for some all-engine and engine
inoperative situations. Flight Profile illustrations do not contain all procedural items,
but show required or recommended configuration changes, thrust changes, Mode
Control Panel (MCP) changes, pitch mode and roll mode changes and checklist calls.
• Non-Normal Maneuver DM: Each Non-Normal Maneuver DM contains information

about flight crew actions needed to be accomplished during non-normal and abnormal
flight conditions, such as Rejected Takeoff, Terrain Avoidance, Traffic Avoidance or
Windshear.
Sample Data keyword: "kwd:ProceduresData.NonNormalManeuver"
• Non-Normal Procedure DM: Each Non-Normal Procedure DM contains information

about flight crew actions needed to manage non-normal/abnormal and emergency
aircraft system responses. It contains a Title and optional Objective Statement,
followed by a series of flight crew actions and information about the aircraft system
responses, limitations and performance. Internal and external references can be
included to assist in flight crew navigation of complex procedures. Information in the
data module can be arranged in sub-levels to further assist in flight crew navigation of
the procedure. For situations that involve a cockpit/flight deck electronic display
(EICAS/ECAM) message, this DM can also reference the Annunciations DM. Crew
awareness procedures, where no actions are provided, can also be identified by a non-
normal procedure DM,
Sample Data keyword: "kwd:ProceduresData.NonNormalProc"
• Non-Normal Non-ECAM/EICAS Procedure DM: Non-Normal Non-ECAM/EICAS
Procedures relate to non-normal situations that are not monitored by an electronic
warning system and may not be related to aircraft systems, such as Pilot Incapacitation.
The procedures do not automatically appear on the cockpit/flight deck display.
• Non-Normal Sensed Procedure DM: Each Sensed Non-Normal Procedure is

associated with an indication from the aircraft to the flight crew. Sensed Non-Normal
Procedures may automatically appear on the cockpit/flight deck electronic display
when a system failure is detected.
• Non-Normal Not-Sensed Procedure DM: Not-Sensed Non-Normal Procedures do

not automatically appear on the cockpit/flight deck display.
• Non-Normal Procedure Description DM: Each Non-Normal Procedure Description

DM contains information that is used to introduce a Non-Normal procedure.
Sample Data keyword: "kwd:ProceduresData.NonNormalProcDesc"
• Normal Checklist DM: Each Normal Checklist DM contains information used by the
crews following a Normal Procedure to verify that the critical actions have been
completed correctly. This data module generally contains a series of crew actions and
CRM information, if needed.
Sample Data keyword: "kwd:ProceduresData.NormalChecklist"
• Normal Procedure DM: Each Normal Procedure DM contains the information and
crew actions needed to prepare the aircraft for various phases of flight. It can include
information used to develop "what-if" scenarios to assist the crew in the event of
unexpected system responses. Accommodations are available to provide descriptive
information to the crewmembers about the given procedure. Crew actions can be
organized in sub-levels to allow the building of complex procedures.
Sample Data keyword: "kwd:ProceduresData.NormalProc"
• Normal Procedure Description DM: Each Normal Procedure Description DM

contains information that is used to introduce a Normal procedure.
• Special Non-Normal Operations DM: Each Special Non-Normal Operations DM

contains information about flight crew actions needed to manage non-normal/abnormal
and emergency aircraft system responses under special situations. It contains a Title
and optional Objective Statement, followed by a series of flight crew actions and
information about the aircraft system responses, limitations and performance. Internal
and external references can be included to assist in flight crew navigation of complex
procedures. Information in the data module can be arranged in sub-levels to further
assist in flight crew navigation of the procedure.
• Special Normal Operations Procedure DM: Each Special Normal Procedure DM

contains the information and crew actions needed to prepare the aircraft for various
phases of flight under special situations. It can include information used to develop
"what-if" scenarios to assist crewmembers in the event of unexpected system
responses. Accommodations are available to provide descriptive information to the
crew about the given procedure. Crew actions can be organized in sub-levels to allow
the building of complex procedures.
• Summary Item DM: Each Summary Item DM contains summary information about
aircraft systems in non-normal/abnormal configurations. The Summary Item DM can
be consulted after the completion of required ECAM/EICAS/ECL checklists or
procedures. Information provided can include flight crew actions, conditions, landing
capabilities, system limitations and information, and non-electronic status information.
• Supplementary Non-Normal Procedure DM: Each Supplementary Non-Normal

Procedure DM contains information about flight crew actions needed to manage non-
normal/abnormal and emergency aircraft system responses under special circumstances
and non-standard configurations. It contains a Title and optional Objective Statement,
followed by a series of flight crew actions and information about the aircraft system
responses, limitations and performance. Internal and external references can be
included to assist in flight crew navigation of complex procedures. Information in the
data module can be arranged in sub-levels to further assist in flight crew navigation of
the procedure. For situations that involve a cockpit/flight deck electronic display
(EICAS/ECAM) message, this DM can also reference the Annunciations DM.
• Supplementary Normal Procedure DM: Each Supplementary Normal Procedure

DM contains the information and flight crew actions needed to prepare the aircraft for
various phases of flight under special circumstances and non-standard configurations.
These procedures are accomplished as required, rather than routinely performed on
each flight. It can include information used to develop "what-if" scenarios to assist a
flight crew in the event of unexpected system responses. Accommodations are
available to provide descriptive information to the flight crew about the given
procedure. Flight crew actions can be organized in sub-levels to allow the building of
complex procedures.
Sample Data keyword: "kwd:ProceduresData.NormalProc"
• Synthesis Item DM: Each Synthesis Item DM provides information to the crew to
assist them in quickly assessing which subsystems remain operative in the case of a
major failure.
Sample Data keyword: "kwd:ProceduresData.SynthesisItem"
• Task Sharing Normal Procedure DM: Each Task Sharing Normal Procedure DM
contains information needed to build task-sharing procedures. These procedures are
usually presented in a table which displays a column for each crew member. Individual
actions are presented in the crewmember column. Generally, each crewmember will
have independent actions. When both crew members accomplish the same action
simultaneously, the action can span both columns. If actions are limited to only one
crewmember, the opposite crewmember cell will be empty.
Sample Data keyword: "kwd:ProceduresData.TaskSharing"
3. Procedure DM and Schema Mapping

The following table lists the Flight Crew Procedure Data Modules (described in Chapter 3)
and the corresponding XML Schemas used for each DM:
DM Type Schema
Cabin Equipment Malfunction

CabinEquipMalfunction.xsd
Decision Tree
Failure Consequences
FailureConsequences.xsd
Synthesis Item
DM Type Schema
Cabin Equipment Malfunction

Procedure
Maneuver Procedure
Non-Normal Procedure
Non-Normal Non-
ECAM/EICAS Procedure
Non-Normal Sensed Procedure
Non-Normal Not-Sensed NonNormalProcedure.xsd

Procedure
Non-Normal Procedure
Description
Special Operations Non-Normal

Procedure
Summary Item
Supplementary Non-Normal
Procedure
Normal Checklist
Normal Procedure
Normal Procedure Description
Special Operations Normal

Procedure NormalProcedure.xsd
Supplementary Normal
Procedure
Flight Profile
Task-Sharing Normal Procedure
4. Procedure Content Guidelines

This section provides business rules and markup guidelines that are applicable to the Procedure
data module types. If there are no specific rules or guidelines for a data module, then that data
module is not included in this section.
4.1. NonNormal Procedure
Data Element XML

Tag Type
landingCapability Element nonNormalProcedure Used only when the NonNormalProcedure
schema is used for a Summary Item DM
nonElectronicStatusInf Element procContent Used only when the NonNormalProcedure

o schema is used for a Summary Item DM
simultaneousStep Element procContent/simultaneous The crm attribute is set on the

Actions simultaneousStep element. Individual actions
and actionBlocks must not have a crm
attribute. The "both" attribute identifies a
single step that is done by both crewmembers.
When the "both" attribute is set to true, only
one simultaneousStep is allowed.
crewAwareness attribute nonNormalProcedure When noProcContent element used,

crewAwareness attribute must be set to "true"
4.2. Normal Procedure
XML
Type
silent Attribute normalProcedure Used only for checklists. Used to identify if
a checklist is silent.
omit Attribute normalProcedure Used only for checklists. Used to identify if

a checklist can be omitted under certain
conditions
checkListItemStatus Attribute procContent/action Used only for checklists.
4.3. Task Sharing Normal Procedure
Data Element XML

Tag Type
simultaneousStep Element normalProcedure/procCon The crm attribute is set on the
tent/simultaneousActions simultaneousStep element. Individual
actions and actionBlocks must not have a
crm attribute. The "both" attribute identifies
a single step that is done by both
crewmembers. When the "both" attribute is
set to true, only one simultaneousStep is
allowed.
3-4-8. Substantiation Data
1. General
Substantiation data is one of the information domains in the Flight Operations documentation.
Substantiation data provides the rationale for approval, consequences of a failure, history of
changes to associated data, system background, and any other information helpful to justify
the reason for the approval. The substantiation is usually restricted to exchange between
OEMs, regulatory authorities and lead airlines. The substantiation information is often used
to justify the review and approval of the MMEL item.
2. Substantiation data module
Following is the Substantiation data module and its description:
• Substantiation DM: The Substantiation DM is used to provide the supporting
information and rationale for allowing an aircraft to operate with an inoperative item.
3. Substantiation DM and Schema Mapping

The following table lists the Substantiation Data Module and the corresponding XML
Schemas used:
DM Type Schema
Substantiation Substantiation.xsd
3-4-9. Systems Description Data

Sample Data keyword: "kwd:SystemDesc"
1. General
Systems Description Data is one of the information domains in the Flight Operations
documentation. The Systems Description information is used to describe the aircraft systems
that are necessary for the operation of the aircraft by the flight crews.
Systems Description information is categorized by the aircraft systems as defined in the ATA
Flight Operations Standard Numbering System. Refer to [Section 5-2 ATA Flight Operations
Standard Numbering System]. It follows the system hierarchy of sub-system and sub-sub-
system for hardware systems, or of function and sub-function for software systems.
Information about each system, subsystem or function is contained in its own data module
(DM) and implicit references are used to establish the relationship between them
Additionally, Subsystems may also reference Component data modules to further describe the
subsystem components. For software systems, functions may refer to Mode data modules, to
explain the different modes that are applicable to the function.
Each Subsystem, Function, Component or Mode DM may have operational instructions based
on one of three operational conditions such as normal, non-normal or "how-to". The
operational instructions of each condition are provided in their own data modules. Each
Control, Indicator or combined Control and Indicator is represented by its own
ControlIndicator DM and may be referenced by any Subsystem, Function, Component or
Mode DM. For electronic messages, however, as annunciated by an onboard computing
system like the ECAM or EICAS system, each message is represented by its own Annunciation
DM. Finally, each system or subsystem may also have specific information about the electrical
supply used by the subsystem. The information is stored in its own ElectricalSupply DM and
implicitly referenced by its own System or Subsystem DM.
Furthermore, the SystemArchitecture and ControlIndicatorArrangement data modules have
been introduced to represent the graphical layout views to allow for advanced navigation and
graphical aids like intelligent graphics with hotspots. Each System or Subsystem may have a
SystemArchitecture DM. Using the intelligent graphic(s) and/or text with references, the
SystemArchitecture DM illustrates the composition of a subsystem and components to
facilitate the interactive navigation to those related data modules. The
ControlIndicatorArrangement DM works in a similar way; it illustrates the cascading views of
the cockpit and panels to allow for direct navigation to any related Control and/or Indicator
data modules.
2. Systems Description Data Modules
Following are the Systems Description data modules and their descriptions:
• Center of Gravity DM: Each Center of Gravity DM contains information on the effect
on the center of gravity of the aircraft due to fuel, fluid, fuel loading and other weight
related configuration.
• Complementary Description DM: Each Complementary Description DM contains

detailed descriptive information in addition to the general description for Subsystem,
Function, and Mode DMs.
• Component DM: Each Component DM describes a unique or self-contained

component or part of the subsystem. It also provides implicit references to all
applicable controls and indicators.
Sample Data keyword: "kwd:SystemDesc.SystemDescription"
• Control DM: Each Control DM contains information about a specific control device
and how it is operated. It also provides references to any affected indicators, affected
or affecting systems.
• Control-Indicator DM: Each Control-Indicator DM contains information about a

single device that operates as both a control and indicator, and can’t logically be
separated. The information contained in the Control-Indicator DM is similar to that in
the Control DM, but Annunciations are associated with each setting of the device.
• ControlIndicatorArrangement DM: The ControlIndicatorArrangement DM may

contain intelligent graphics with hotspots and/or textual description and references to
describe how the control and/or indicator are arranged to facilitate the direct
navigations and view of the control and/or indicator devices. A typical interactive view
follows the cascading style from the cockpit, panel to the control or indicator.
• DataEntryFormat DM: Each DataEntryFormat DM contains specific input data to

be performed by the flight crew into a ControlIndicator device through the device's
application interface.
• ElectricalSupply DM: Each system or subsystem may have an ElectricalSupply DM

to describe the electrical supply information that is specific to the operation of that
system or subsystem.
• Electronic Annunciation DM: Each Electronic Annunciation DM contains

information corresponding to a single electronic message provided by an onboard
computing system. These messages are typically generated from a cockpit/flight deck
electronic display system, such as ECAM or EICAS.
Sample Data keyword: "kwd:SystemDesc.Annunciation"
• Function DM: The Function DM contains general descriptions of a function of a

software system.
• How-To Operation DM: The How-To Operation DM contains the operational

instructions to describe how a user interacts with a system.
• Indicator DM: Each Indicator DM contains information about a specific indicator

device that conveys information about the state of the system. It also provides
references to any applicable controls, components and annunciations.
• Mode DM: The Mode DM describes various contexts that can change a function
behavior of a software system.
• Non-Electronic Annunciation DM: Each Non-Electronic Annunciation DM contains

information corresponding to a flight deck annunciation that is not generated by an on-
board computer system. These annunciations alert the crew of a system malfunction
or other non-normal condition that is not monitored by the cockpit/flight deck
electronic display system.
Sample Data keyword: "kwd:SystemDesc.Annunciation"
• Non-Normal Operation DM: The Non-Normal Operation DM contains the

operational instructions for the flight crew to perform for a given system or subsystem
under non-normal operating conditions.
• Normal Operation DM: The Normal Operation DM contains the operational

instructions for the flight crew to perform for a given system or subsystem under
normal operating conditions.
• Panel and Display DM: The Panel and Display DM contains graphics, a callout list
and other information used to describe the items on the panel or display.
• Subsystem DM: Each Subsystem DM describes a subordinate system known as a

Subsystem or Sub-Subsystem. Each Subsystem DM describes a major functional
portion of a system. It also provides implicit references to its own subordinate systems
(if applicable), components, controls, indicators, affected and affecting systems.
• System DM: Each System DM describes a high-level System and provides references
to all the subordinate, affected or affecting systems. There is exactly one System DM
for each ATA System.
• SystemArchitecture DM: Each system or subsystem may have a SystemArchitecture

DM that can contain an intelligent graphic with hotspots and/or textual architecture
description typically depicting how the System or Subsystem is composed to allow for
interactive and direct navigation to any related Subsystem and Component DM.
3. Systems Description DM and Schema Mapping
The following table lists the System Description Data Modules and the corresponding XML
Schemas used for each DM:
DM Type Schema
Additional Parameters
Center of Gravity
Complementary Description
Component
Control
Control-Indicator
Control-Indicator Arrangement
Data-Entry Format
Electrical
Function
SystemDescription.xsd
How-to Operation
Indicator
Mode
Non-Normal Operation
Normal Operation
Panel and Display
Subsystem
Supply
System
System Architecture
Electronic Annunciation
Annunciation.xsd
Non-Electronic Annunciation
4. Systems Description Content Guidelines
This section provides business rules and markup guidelines that are applicable to the Systems
Description data module types. If there is no specific rule or guideline for a data module, then
that data module is not included in this section.
4.1. Annunciation
Data Element XML

Tag Type
auralWarning Element annunciation/indications Used to provide either an audio file that
corresponds to a warning, a textual
description of the warning, or both.
category Attribute annunciation Used only if conveyance is set to

message
code Attribute annunciation/inhibitConditions/in Contains the Spec 2300 Phase of Flight

hibitCondition code per Appendix 6-1, as defined for
each aircraft flight warning system.
display Attribute annunciation Used only if conveyance is set to

message
figure Element annunciation/inhibitConditions The graphic inside the figure is used to

illustrate the conditions (e.g. flight
phases) when the electronic message is
inhibited.
localLight Element annunciation/indications/localLig Can contain illustrations, and/or

hts reference to indicator or controlIndicator
data module that deals with this local
light.
multimediaType Attribute annunciation/indications/auralWa Audio, as linked to an aural alert.

rning/multimediaObject
priorityRanking Attribute annunciation Use only manufacturer-specific

established standard terminology (e.g.,
time critical, normal, info, etc.). Not
used to convey priority level (i.e.,
warning, caution, advisory)
title Element annunciation Include systemName (if any), the

content of the electronic messages and
submessage (if any) that is generated.
type Attribute annunciation/indications/masterLi Type of the masterlight (warning or

ght caution).
Type of auralWarning. (e.g. Single
annunciation/indications/auralWa
Chime or Continuous Repetitive Chime).
rning
4.2. ControlIndicatorArrangement
Data Element XML

Tag Type
figure Element systemDescription/description Should contain hotspots to provide links
to the ControlIndicatorArrangement or
ControlIndicator data modules of the
(sub)system.
title Element systemDescription Should contain the name of the panel if

the figure shows a specific panel of the
cockpit.
4.3. Panel and Display
XML
Type
figure Element systemDescription/description At least one graphic is required.
calloutList Element systemDescription/description At least one callout list is required.
4.4. System Architecture
XML
Type
description Element systemDescription Should contain, if necessary,
supplementary information about the
structure of the (sub) system.
title Element systemDescription Should include the name of the

system/subsystem.
figure Element systemDescription/description Hotspot references must refer to the

associated subsystems/components data
modules.
4.5. System Description
XML
Type
title Element systemDescription Used to provide the name of the information
type corresponding to the Information Code
(IC) (e.g., if IC = 04A, then title is used to
provide the name of the System)
XML
Type
description Element systemDescription Used to provide a description of the
information type corresponding to the
Information Code (IC) (e.g., if IC = 04E, then
description is used to provide a description of
the Mode of the software system)
affectedSystemList Element systemDescription Used only if the SystemDescription schema

is used for System or Subsystem data
modules (i.e. IC=04A or 04B)
affectingSystemList Element systemDescription Used only if the SystemDescription schema

is used for System or Subsystem data
modules (i.e. IC=04A or 04B)
dmRef Element systemDescription/affected Must be used to reference a System DM

SystemList/systemRef
systemDescription/affectin
gSystemList/systemRef
inhibitConditions Element annunciation <inhibitConditions> may not be empty. It

must contain at least one child element.
3-5. Graphics and Multimedia

3-5-1. Graphics standards
1. Graphic Format
ATA Spec 2300 makes no recommendation on any specific graphic format. Any recognized
MIME type is acceptable.
2. Intelligent graphics
An intelligent graphic contains an illustration and hotspots.
Hotspots are interactive areas on an illustration that enable navigation between graphical
objects or between graphical objects and text.
The target of a hotspot is established by using the reference management mechanism specified
in [Section 3-2-6, References Management].
A hotspot can also be a target from text in the same or another data module.
3. Graphic Display
The display of a graphic is specified by the anchor and display modes:
• Inline anchor mode: The graphic is fully displayed in the content of the data module
on the consultation application.
• Thumbnail anchor mode: An icon is displayed in the content of the data module with
a link to the graphic.
• Linktext anchor mode: Text is displayed as an active zone with a link to the graphic
• Unanchored mode: The figure contains more than one graphic not anchored in the
text flow of the data module. The first graphic is displayed, and contains hotspots that
enable display of another graphic instead of the first one, to create a sequence (with
steps) of graphics. This can be used to simulate a user-controlled animated sequence
showing how an interface behaves when used.
3-5-2. Multimedia files standards

Some multimedia files may be included in the documentation, e.g. to show the operation of a
system, or to enable the user to hear an aural warning.
They are considered as external data, and they are called by using an external reference to the
multimedia file.
An alternative content element must be provided for all multimedia content for cases when it
is not possible to call an application for viewing or hearing the external data.
The format of the multimedia files can also depend on the formats that the consultation
application accepts.
3-5-3. Information Control Number

The Information Control Number (ICN) is the standardized and structured identifier for an
illustration, graphic, or multimedia file.
The Information Control Number may range from 27 to 45 characters in length and contains 9
components described below. The identifier must be unique for each object. An optional
Information Control Number Extension may also be provided to ensure uniqueness.
Figure 3-12 Information Control Number structure – min length
Information control number – min 29 characters:
ICN - YY - Y - YYYYYY - Y - YYYYY - YYYYY - A - XXX - XX
Prefix
Responsible partner company code
Originator code (NCAGE code)
Unique Identifier
Variant code
Issue number
Security classification
Figure 3-13 Information Control Number structure – max length

Information control number – max 46 characters:
ICN - YYYYYYYYYYYYYY - YYYY - YYYYYYYY - Y - YYYYY - YYYYY - A - XXX - XX
Prefix
Responsible partner company code
Originator code (NCAGE code)
Unique Identifier
Variant code
Issue number
Security classification
1. Model Identification Code

point of reference for all applicability information. The MI includes all related model variants.
MI Codes must be in accordance with NATO NSPA Model Identification - ASD S2000M -
Model Identification Codes (MI).
2. System Difference Code
The System Difference Code (SDC) indicates alternative versions of the system and
subsystem/ by the SNS without affecting the type, model or variant identity.
3. Standard Numbering System
The Standard Numbering System (SNS) describes the aircraft System and Subsystem
breakdown to which the information in the data module applies. The Flight Operations
Standard Numbering System is based on the ATA SNS as defined in iSpec 2200, but
customized at the Subsystem level to apply specifically to flight operations data. Refer to
[Section 5-2 ATA Flight Operations Standard Numbering System].
Dispatch data uses the iSpec 2200 SNS (at System and SubSystem level), optionally extended
by the Dispatch Item extension code. Refer to [Section 2-3-1.1.11 Dispatch Item Extension
Code]. For this reason, any illustration, graphic, or multimedia referenced from a dispatch data
module uses the iSpec 2200 SNS.
4. Responsible Partner Company Code
The Responsible Partner Company Code identifies the company or organization responsible
for the illustration or multimedia object independent of its use in data modules.
5. Originator Code
The Originator Code (OC) identifies the originator of an illustration or a multimedia object. It
consists of 5 alphanumeric characters. The code is the originator’s NCAGE/CAGE code.
6. Unique Identifier
The Unique Identifier is used to help provide uniqueness to the identifier of the object. It
consists of five alphanumeric characters.
7. Variant Code
The Variant Code (VC) is a single alpha character, which identifies the variants of a basic
illustration or multimedia object. The variant code "A" identifies a basic illustration or
multimedia object and "B" identifies the first variant. A variant is a supplemented, scaled,
cropped, rotated, mirrored and/or annotated basic illustration or multimedia object.
Variant Code is not used to identify configuration-based differences in illustrations.
8. Issue Number
The Issue Number (IN) is a 3-digit sequential numerical value. It starts from 001 for each basic
illustration or multimedia object, or variant thereof, and is incremented each time the
illustration or multimedia object is updated.
9. Security Classification
The Security Classification (SC) is a 2-digitnumerical character that identifies the security
classification of the illustration or the multimedia object. Data providers are responsible for
defining their own security classification codes. Lower numbers should represent a lower level
of security and progress higher as the level of security increases.
3-5-4. Information Control Number Extension

The Information Control Number Extension gives the additional parameters needed to
establish a unique identification of a graphic or multimedia object in those cases when ICN is
insufficient to form a universally unique identity.
It is composed of:
• The extension producer: Contains the CAGE/NCAGE code of the producer of the
graphic or multimedia object and forms part of the universally unique identifier of the
object.
• The extension code: Typically, but not necessarily, contains customer related content
(e.g., customer CAGE appended with a sequence number) the value of which is decided
by the graphic or multimedia object producer.
Chapter 4. DATA PACKAGING AND DELIVERY
4-1. Introduction
Data are delivered using the concept of the exchange package. An exchange package contains
the delivered resources:
• XML documents for data modules: DM Status and DM Content. Refer to [Section 2-
5-1, Data module global content].
• External objects (graphics, multimedia). Refer to [Section 3-5, Graphics and

Multimedia].
• XML documents to manage the publication organization. Refer to [Section 4-2,

Publication Module].
• Additional resources can be added in exchange packages, such as ATA FOML XML
Schemas, project specific rules resources and any supporting documentation/resources
determined by agreement between data provider and data receiver. Refer to [Section 0,
• Sample Data keyword: "kwd:DataDelivery"
• Project rules].
The scope of the delivery package can be any of the following (refer to [Section 4-3-3, Delivery
scope] for descriptions):
• Complete
• Revised resources
• Partial.
As part of the exchange package some DMs can be marked as included in a subset to identify
them as pertaining to a bulletin or temporary add-on (refer to [Section 4-3-11, Subsets]), or to
be considered with highest priority in case of a major event. Refer to [Section 4-3-10, Major
Event].
An Exchange Package Status List (managed as an XML document) is included in the package
to provide the status of each delivered resource. Refer to [Section 4-3-8, Exchange Package
Status List].
The package organization is described using a package organization description XML
document to provide the physical ways the data are delivered. Refer to [Section 4-3-7, Package
Organization Description].
In addition, a specific Data Set Status List XML document can be exchanged, independently
of an exchange package, to provide the expected data set after a (complete, revised only or
partial) delivery, listing all the resources and the related status. Refer to [Section 4-4, Data Set
Status List].
4-2. Publication Module

Sample Data keyword: "kwd:PublicationModule"
4-2-1. Assembly for publication

A publication module defines an assembly of data modules, typically to manage a manual
structure such FCOM or MMEL.
It allows building a recursive structure of chapters/sub-chapters with a reference to data
modules.
Referenced data modules can be container DMs and/or content DMs. Refer to [Section 3-3-3,
Container and Alternate Data Modules].
One or more publication modules can be delivered in an exchange package using the same
revision management and revision mark mechanisms as a DM. Refer to [Section 3-3-2,
4-2-2. PM Identification
Each publication module has a unique identification composed of:
• Publication Module Code
• Optional language
• Optional publication module code extension
In addition to the publication module identification, issue information is provided.

1. Publication Module Code
The Publication Module Code (PMC) is the standardized and structured identifier for a
publication module.
It is composed of the Model Identification Code, the publication module issuer, the publication
module number and volume.
1.1. Model Identification Code
MI Codes must be registered with the NATO Support Agency (NSPA).
1.2. PM Issuer
The publication module issuer contains the NCAGE/CAGE code of the publication module
issuing company.
1.3. PM Number
The publication module number is an alphanumeric identifier unique to the Model
Identification Code and the PM Issuer.
1.4. PM Volume
The publication module volume contains the volume number of the publication module (in
case of multiple volumes in the publication) or is set to "00" if only one volume exists.
2. Language
When all the data modules referenced from the publication module are provided in a single
language, that language may be optionally identified within the publication module
identification.
It is composed of:
• The language ISO Code: Generally coded by using the two alpha characters from
International Standards Organization (ISO) 639. Simplified languages are coded by
using additional codes similar to, and not in conflict with, ISO 639 codes.
• The country ISO Code: Coded by using the two alpha characters from ISO 3166 to
denote the country where the language is spoken.
3. Publication Module Code extension

Related to the publication module code, an extension is optionally provided. The publication
module identification extension gives the additional parameters needed to establish a unique
identification of a publication in those cases when other identification data are insufficient to
form a universally unique identity.
It is composed of:
• The extension producer: The publication module producer, the value of which forms
part of the universally unique identifier of a publication module instance and contains
the NCAGE/CAGE code of the producer of the publication module instance.
• The extension code: The value of the publication module extension code is decided by
the publication module producer. Typically, it will contain customer related content,
e.g. customer NCAGE/CAGE code appended with a sequence number.
4. Issue information
Issue information for a publication module is composed of the issue date of the publication
module and an optional issue number. If issue number is used, an optional minor issue number
may also be provided.
Following the physical organization of publication modules (refer to [Section 4-2-3, Content
and metadata organization of publication modules]), two separate issue dates and numbers are
provided: issue date and number for the content portion of the publication module (PM
Content) and issue date and number for the metadata (PM Status) portion of the publication
module.
4-2-3. Content and metadata organization of publication modules

Following the same philosophy as data module organization (refer to [Section 2-5, Data
module content and metadata organization]), publication modules are physically delivered by
two separate XML fragments:
• PM Content: The publication structure giving the data modules assembly
• PM Status: The related metadata
Each exchange package may contain one or both fragments and each fragment has its own
issue information.
Figure 4-1 Publication module content and status association
Following the revision mechanism (refer to [Section 3-3-2, Revision Management]), the two
XML fragments of a publication module have their own life cycle.
1. Metadata : PM Status fragment
The publication module status is an XML fragment containing the metadata related to a
publication module:
• Associated properties (attributes) giving status information . Refer to [Section 3-3-2,
• The publication module identification. Refer to [Section 4-2-2, PM Identification].
• The issue information composed of:
o The PM status issue information containing the issue date and number of the PM
Status fragment
o The PM content issue information, containing the issue date and number of the PM
Content fragment. It allows identification of the PM Content fragment to which the
provided metadata applies. Refer to [Section 4-2-2.4, Issue information].
• Receiver code and name
• Product code (such as FCOM, MMEL), product number, publication scope, publication
type and optionally the norm applicable to the publication. Publication scope can be
one of the following:
o ALL: Generic data that does not pertain to a particular aircraft, model or fleet (used
for company manuals)
o ENVMOD: Non-customized data for an Envelope Model that may consists to one
or more aircraft models
o FLEET: Customized data for one or more aircraft of one or more aircraft models
o FLEET+COC: FLEET data embedding also some COC
o MSN: Customized data for one particular aircraft
o MSN+COC: MSN data embedding also some COC
Publication type can be one of the following:
o NR: Normal revision
o TR: Temporary revision
o CP: Certification package
o OSD: Operational Suitability Data – data required by an operator to develop its own
publications
• An optional label to specify some restriction of use of the publication (e.g. a PM can
be produced and delivered for specific reasons, such as an advance copy or a specific
release for training or the specific issue for A/C delivery).
• Major and minor model code, model designation and market designator. This structure
may be repeated to target several aircraft models.
• Approval information providing data on the approval status of the PM; given when
approval is required
• Revision data of the publication module content. Refer to [Section 3-3-2, Revision
Management].
• PM Entry Revdates. Refer to [Section 4-2-6, PM Entry revision dates for open and
closed applicability].
2. Publication structure: PM Content fragment

A publication module defines the assembly of data modules for a publication.
The high-level structure is commonly called Chapter, Section, etc. in a typical publication.
Using a publication module, all high-level structures are defined using a generic recursive level
called PM Entry. A PM entry is composed of a PM Entry title (title of the current level of
structure), a type and a code (to allow forcing the numbering of the level).
In a PM Entry, the following can be found:
• Sub levels, represented by:
o Included PM entries
o References to other Publication modules
or
• References to data modules (terminal level of the PM tree): data modules can be
grouped or not.
o Data modules are referenced using explicit references; the referenced data module
can be either a container data module (refer to [Section 3-3-3, Container and
Alternate Data Modules]) to reference a set of data modules with configuration
variants, or a flight operations technical content data module;
o Referenced data modules can be grouped in a GDM (Group of DMs). It specifies

that the included data modules should be published in a single publication unit. A
GDM is composed of a title and a list of data module explicit references.
Figure 4-2 Example of a publication module content fragment
Figure 4-3 Example of a Publication Module reference to other Publication Modules
This publication module gives the data modules assembly and the high-level structure of an
FCOM.
It uses PM Entry for defining the organization of the manual (Aircraft systems, Procedures,
Limitations…). For each top level (such as Aircraft systems), the included PM entry gives a
business oriented organization (in this case organized by ATA Systems).
The recursive structure concludes with references to data modules (DM Ref) or groups of data
modules (GDM) including a list of DM Refs.
4-2-4. Publication Module Schemas

Each publication that is being exchanged must have a PM Content and PM Status XML
instance using the following XML Schemas:
• Pm.xsd – A schema to specify the publication organization, its sequence, hierarchy and
references to content data modules (PM Content).
• PmStatus.xsd – A schema to provide metadata to the PM instance (PM Status).
1. PM Schema Mapping
PM Status XML fragments use the PmStatus.xsd schema.
PM Content XML fragments use the Pm.xsd schema.
4-2-5. Non-linear data module concept

A publication module can contain data modules that are only available for consultation after
some specific actions and not during a normal linear mode of consultation.
Non-linear data modules are contextually-based DMs. If the context requirements are
satisfied, then the DM would be available. Non-linear DMs can also be accessed as the result
of a search. Example: In the event of an engine failure, the linear consultation would provide
a display of the ENGINE FAILURE checklist. In addition, there are separate non-linear DMs
for ENG 1 FAIL, ENG 2 FAIL, etc. that can be displayed depending on sensed aircraft
condition or configuration.
4-2-6. PM Entry revision dates for open and closed applicability

The concept of open and closed applicability revision dates should be used to better identify
the type of revision of a PM entry (refer to [Section 4-2-3.2, Publication structure: PM Content
fragment]) and to define if it can be considered as revised or not.
Closed applicability is the list of aircraft applicable to a data module.
Open applicability is the list of aircraft applicable to a data module in the context of the
complete list of aircraft applicable for the publication module.
Example 1:
List of applicable aircraft: 001, 002, 003, 006, 007
DM applicability: 001, 002, 003, 006
DM Closed range applicability: 001-003, 006
DM Open range applicability: 001-006 (indeed 004, 005 are not part of the list of
aircraft)
Having a different PM entry revision date for closed and open range allows identification of
the modifications applied to the closed and open applicability of data modules.
For instance, inserting a new aircraft in the list of aircraft does not have the same impact for
the closed and for the open applicability.
Example 2:
List of applicable aircraft: 001, 002, 003, 004, 006, 007
DM applicability: 001, 002, 003, 004, 006
DM Closed range applicability: 001-004, 006
DM Open range applicability: 001-006 (indeed 005 is not part of the list of aircraft)
In the example 2, with the insertion of aircraft 004, the closed applicability has been changed
compared to example 1, but not the open applicability.
That means that the PM entry revision date for the closed applicability should reflect this
change whereas the PM entry revision date for the open applicability should reflect that the
open applicability has not evolved.
Further in this example, if adding this new aircraft has not impacted any enclosed DM content,
it’s possible to consider:
• The PM entry as revised, if we consider the PM entry revision date for closed
applicability; or
• The PM entry as not revised, if we consider the PM entry revision date for open
applicability.
These revision dates are provided in the PM Status fragment using the path mechanism to
address the PM entries in the PM content fragment. Refer to [Section 2-5-5, Addressing
mechanism].
4-3. Data Delivery

Sample Data keyword: "kwd:DataDelivery"
4-3-1. Project rules
Project rules communicate specific Spec 2300 implementation decisions for a project.
For example,
• Specify if optional attributes or elements are required for a project or not allowed for a
project.
• Allowed or not allowed attribute or element values
• Relevant spec revision
A project defines a set of rules identified by a Project Identifier (that could be specified for a
specific data delivery in the Package Organization Description file).
4-3-2. Project rules using structured format

Sample Data keyword: "kwd:DataDelivery.ProjectRules"
ATA Spec 2300 includes an option for providing project rules in a structured format (i.e., XML
Schema). This can make it easier for parties to automatically validate that delivered data
complies with the defined rules.
The Project Rules schema can be used to provide the following:
• Common information: Allows the data producer to share textual general information.
• Rules on SNS: To describe one or more SNS systems as described in Spec 2300
(including SNS sub-hierarchy) that are applicable to the concerned project.
SubSubSytem and Assembly levels are not specified in Spec 2300 and project rules
may also be expressed to declare their use.
• Contextual rules: To express rules which can be related to a particular schema/context
or particular element/attribute in the schema structure. For each defined rule:
o one part will indicate which element/attribute/content must be considered for
verification (using standard Xpath mechanism).
o one optional part may give a textual explanation of the constraint or of the non-
conformity.
o one optional part may provide the list of allowed values.
• Non-contextual rules: To express rules which cannot be related to a particular
schema/context/element/attribute, in a textual form.
4-3-3. Delivery scope
Sample Data keyword: "kwd:DataDelivery.Scope"
Data can be delivered in one of the following ways:
• Complete: all XML content and external objects are provided in the exchange package.
Sample Data keyword: "kwd:DataDelivery.Scope.Complete"
• Revised only: only revised XML content and external objects are provided in the
exchange package.
Sample Data keyword: "kwd:DataDelivery.Scope.RevisedOnly"
• Partial: all XML content and only revised external objects are provided in the
exchange package.
The delivery scope is specified in the Exchange Package Status List XML document. Refer to
[Section 4-3-8, Exchange Package Status List].
4-3-4. DM Status and DM Content life cycles

DM Status and DM Content XML fragments each have their own life cycle / issue information
and can be provided independently or together. For example, if only the applicability of a data
module changes; only the DM Status XML fragment would be delivered. In any case there is
a mechanism to associate the DM Status XML fragment to its related DM Content XML
fragment. Refer to [Section 2-5, Data module content and metadata organization].
4-3-5. PM Status and PM Content life cycles

Life cycles of publication modules are managed in the same way as data modules: PM Status
and PM Content fragments are associated to each other but can be delivered independently or
together. For example, if only the content of a Data Module changes, the Publication Module
content does not need to change, but must be re-approved by sending a revised PM Status
fragment.
4-3-6. Exchange Package

An exchange package is composed of:
• The Package Organization Description: The Package Organization Description is
an XML file that describes the physical organization of the exchange package
(locations of resources, naming conventions). Refer to [Section 4-3-7.2, Package
Organization Description file].
• The Exchange Package Status List: The Exchange Package Status List is an XML
document providing the list of all delivered data modules and publication modules
with their related revision status. It also includes a list of deleted data modules, deleted
publication modules and deleted external objects (graphics, multimedia). It can be
considered as the logical entry point of an exchange package. Refer to [Section 4-3-7,
Package Organization Description].
• A set of Data Modules: The exchange package contains a set of data modules as XML
fragments following the data module organization (refer to [Section 2-5, Data module
content and metadata organization]), including data modules for flight operations
technical content and data modules for management, such as applicability cross
reference tables (refer to [Section 3-3-1, Applicability management]), data repositories
(refer to [Section 3-3-4, Information Repositories), and containers (refer to [Section 3-
3-1, Applicability management]).
• Optionally, one or more Publication Modules: Publication modules to organize data

modules for publication are delivered as XML fragments (PM Content and PM Status).
Refer to [Section 4-2, Publication Module].
• Optionally, graphics and multimedia files: all external files referenced by data
modules. Refer to [Section 3-5, Graphics and Multimedia].
4-3-7. Package Organization Description

Sample Data keyword: "kwd:DataDelivery.PackageOrganization"
1. General
As the entry point of an exchange package, the Package Organization Description is an XML
file that describes how the resources are physically organized in an exchange package.
The Package Organization Description document provides the organization for each ATA 2300
compliant data (i.e., Exchange Package Status List, Data Modules Content/Status, Publication
Modules Content/Status, Graphics, Multimedia and XML Schema). It can also be used to
provide project rules (refer to [Section 0,
Sample Data keyword: "kwd:DataDelivery"
Project rules]) and to describe how additional custom data, considered as a particular resource
group (custom with a specific custom data group name) are delivered.
The Package Organization Description document provides:
• Project Identifier: if the delivered data use specific project rules, the related project
identifier can be provided.
• Package Base location: the base URI to find the exchange package resources. Using
this base location, every group of resources can be located relatively.
• Exchange Package Status List location: the location (URI, absolute or relative to the
Package Base Location) of the Exchange Package Status List.
• Resource Groups: Resources are organized in the following groups: DM Content, DM

Status, PM Content, PM Status, Graphic objects, Multimedia objects, XML Schema,
Custom (any additional resources), Project (project rules resources).
Note: In this context, the term "groups" implies a virtual organization of resources. It does
not mean that there must be a corresponding physical folder for each "group".
• The following is provided for each group:
o Default Location: the location of the folder where resources that are part of the
group are found by default. The location is provided as a URI that can be absolute
or relative to the Package Base Location.
If necessary, the naming rule is provided using an XPath expression (returning a

string) that should be evaluated to find the name of the resource.
o Conditional Locations: for resources that are not located in the Default Location,
Conditional Locations can provide specific locations and naming rules.
A Conditional Location is specified with a condition statement (XPath expression

returning a Boolean value) followed by a location (URI, absolute or relative to the
Package Base Location) and if necessary the naming rule to compute the name of
the resource.
Figure 4-4 Package Organization Description Example
2. Package Organization Description file

The Package Organization Description document is provided as an XML document, in a file
using the following file naming scheme:
• ata2300exchangepackage_datetime.xml
with datetime filled with an ISO standard data/time stamp.

3. Package Organization Description Schema
PackageOrganization.xsd – A schema to provide the physical organization of resources in an
exchange package,
4-3-8. Exchange Package Status List

Sample Data keyword: "kwd:DataDelivery.ExchangePackageStatusList"
The Exchange Package Status List contains references to:
• All delivered data modules and publication modules: All data modules and
publication modules included in the exchange package are referenced in the Exchange
Package Status List. For each referenced data or publication module, its status is
specified: changed, new, applicability changed (for DM only), unchanged.
• All deleted data modules and publication modules: All data/publication modules
that have been deleted since the previous delivery are not included in the exchange
package (refer to [Section 3-3-2, Revision Management]) but are listed in the
Exchange Package Status List with the status set to "deleted". It is used for Revised
Only deliveries.
• Deleted External Objects: in case of an incremental delivery (delivery scope set to

Revised Only or Partial, (refer to [Section 4-3-3, Delivery scope]), the list of external
objects (graphics and multimedia resources) that have been deleted since the previous
delivery.
Figure 4-5 Exchange Package
An entry for a DM in the Exchange Package Status List is called a DM Status entry. An entry
for a PM is called a PM Status entry.
1. Exchange Package Status List Identification
The Exchange Package Status List has an identification composed of:
• The Data Module List Code
• An optional Extension Code
1.1. Data Module List Code

The Data Module List Code is the standardized and structured identifier for an Exchange
Package List.
It is composed of the Model Identification Code and the Sender Identification (NCAGE/CAGE
Code).
1.1.1. Model Identification Code
MI Codes must be in accordance with NATO Support Agency (NSPA) Model Identification
Codes.
1.2. Extension Code:
The value of the Data Module List Extension Code is decided by the sender. Typically, it will
contain customer related content, e.g. customer NCAGE/CAGE code appended with a
sequence number.
2. Issue information
Issue information for an Exchange Package Status List is composed of the issue date.
4-3-9. Exchange Package Status List Schema

• ExchangePackageStatusList.xsd – A schema to provide a list of references to all DMs
and PMs for a given exchange package,
4-3-10. Major Event

In some cases, manufacturers must quickly transmit new or updated information to the
operators.
The major event concept identifies exchange packages, and data modules in an exchange
package, that are considered to be high priority.
4-3-11. Subsets
Sample Data keyword: "kwd:DataDelivery.Subset"
A Subset groups DMs that have content that is linked and must be released together.
There are several types of subsets, such as:
• An Operations Engineering Bulletin (OEB) is issued to rapidly inform operators of any
deviations from initial design objectives that have a significant operational impact. An
OEB provides the operators with technical information and temporary operational
procedures that address these deviations.
• An FCOM bulletin provides complementary technical/operational explanations related

to the information included in the FCOM. They are periodically issued to address one
or several subjects and include supplementary explanations concerning procedures,
systems, performance or regulations.
• A Cabin Crew Bulletin (CCB) is issued to rapidly inform operators of any deviations
from initial design objectives that have a significant impact on cabin operations. A CCB
provides the operators with technical information and temporary operational
procedures that address these deviations.
• A Temporary Add-On pertains to amendments to be quickly approved and introduced

in a manual.
A subset header data module is provided with a subset giving some general information, i.e.,
reason, criteria, cancel conditions, comments, approval references, and internal approval
responsible.
To identify a Data Module as part of a Subset, the following metadata are provided in the DM
Status fragment:
• Subset Type: provides the type of Subset (OEB, FCB, CCB…)
• Subset Identifier: provides the unique identifier of the subset.
• If relevant, the Subset Issue Number, the Subset Importance and Subset Impact (an
indicator of whether or not the Subset impacts a ECAM/EICAS system).
Each DM in a Subset, including the Subset header DM, shares the same set of metadata.
4-4. Data Set Status List

Sample Data keyword: "kwd:DataDelivery.DataSetStatusList"
4-4-1. General
At any time, the data receiver may need to check the status of its own data set to verify that its
data set is up-to-date with all the deliveries sent by the data producer. This check may be
particularly relevant in case of partial deliveries. Refer to [Section 4-3-3, Delivery scope]. For
example, when a "revised only" exchange package is received, the data receiver should update
its data set. Any mistake in an update process could produce a data set that is not consistent
with the expected data set (i.e., exactly the same as the complete data set).
Figure 4-6 check of updated data set
Revised only
Complete
Data Set
Revised only
+ Update
Data Set
???
Updated
Data Set
= Complete
Data Set
4-4-2. DSSL (Data Set Status List)

To check the status of a data set, the data producer can deliver a specific XML document named
"Data Set Status List" to the data receiver that lists all the expected resources in a data set, with
the related status (issue information) for each resource:
• Each DM with the issue info:
o DM identifier with related issue type
o DM Status issue info (date and optional in-work number)
o DM Content issue info (date and optional in-work number)
• Each PM with the issue info:
o PM identifier with related issue type
o PM Status issue info (date, optional issue number and minor issue number)
o PM Content issue info (date, optional issue number and minor issue number)
• Each graphic and multimedia object
o Object identifier
Using the Data Set Status List, the data receiver can verify if its updated data set is compliant
with the expected content.
Figure 4-7 Use of Data Set Status List
Status List
• DMCx, issue t1
Check • DMCy, issue t2
Updated • DMCz, issue t3
Data Set
?or?
X
DMCz, issue t3
missing
4-4-3. Data Set Status List Schema

• DataSetStatusList.xsd – A schema to provide a list of expected DM, PM, graphics
and multimedia objects in a data set
Chapter 5. FLIGHT OPERATIONS INFORMATION
STANDARDS
5-1. Phase of Flight Specification

Sample Data keyword: "kwd:PhaseOfFlight"
5-1-1. Identification
ATA Phases of Flight (POF) shall be explicitly identified for all flight operations data. The
identification of phases of flight and their transitions should be broad enough to allow the
capture of phase of flight- related elements in systems descriptive information, aircraft and
systems limitations, normal / non-normal procedures, supplementary procedures and
techniques, dispatch deviation /configuration deviation information, and performance data etc.
5-1-2. Transition Relationships

Summary information for phase transition relationships are as given in the following table and
graphic.
1. Transition Relationships for Airplane Operations
Phase Subsequent Phase Subsequent Phase if Abort

Flight Planning Pre-flight Flight Close
Pre-flight Engine Start/Depart Post-flight
Engine Start/Depart Taxi-out Arrival/Engine Shutdown
Taxi-out Take-off Taxi-in
Take-off Initial Climb Rejected Take-off
Rejected Take-off Taxi-in Arrival/Engine Shutdown (possibly

associated to emergency)
Initial Climb En Route Climb Approach
En Route Climb Cruise Descent
Cruise Descent En Route Climb
Descent Approach Cruise or En Route Climb
Approach Landing Go-around or Initial Climb
Go-around Approach Initial Climb
Landing Taxi-in Go-around
Taxi-in Arrival/Engine Shutdown Taxi-out
Arrival/Engine Shutdown Post-flight Engine Start/Depart
Post-flight Flight Close Engine Start/Depart
Flight Close Ground Servicing Flight Planning
Ground Servicing Flight Planning Pre-flight
Figure 5-1 Transition Relationships for Airplane Operations
Cruise (CRZ)
En Route Climb
Descent (DST)
(ECL)
Initial Climb
Approach (APR)
(ICL)
Rejected Take- Go-around

off (RTO) (GOA)
Take-off (TOF) Landing (LND)
Taxi-out (TXO) Taxi-in (TXI)
Arrival / Eng
Eng Start /
Shutdown (AES)
Depart (ESD)
Pre-flight (PRF) Post-flight (PSF)
Flight Planning Flight Close

(FLP) (FLC)
Ground
Servicing (GDS)
2. Transition Relationships for Helicopter Operations

Engine StartDepart Hover In Ground Effect or Taxi-out Arrival/Engine Shutdown
Hover In Ground Effect Taxi-out Arrival/Engine Shutdown
Taxi-out Hover In Ground Effect or Take-off Taxi-in
Take-off Climb Rejected Take-off
Rejected Take-off Taxi-in Arrival/Engine Shutdown (possibly

associated to emergency)
Climb Cruise, Descent, or Hover Out of Descent or Approach

Ground Effect
Cruise Hover Out of Ground Effect or Descent

Descent
Hover Out of Ground Effect Climb, Cruise or Descent Descent, Cruise or Climb
Descent Approach or Hover Out of Ground Cruise or Climb

Effect
Approach Landing Go-around or Climb
Go-around Approach Climb
Landing Taxi-in or Hover In Ground Effect Go-around
Taxi-in Hover In Ground Effect or Taxi-out

Arrival/Engine Shutdown
Hover In Ground Effect Taxi In or Arrival / Engine Shutdown Arrival/Engine Shutdown
Arrival/Engine Shutdown Post-flight Engine Start/Depart
Figure 5-2 Transition Relationships for Helicopter Operations
Cruise (CRZ)
Hover out of
Ground Effect
(OGE)
Climb
Descent (DST)
(CLB)
Approach
(APR)
Rejected Take- Go-around
off (RTO) (GOA)
Take-off (TOF) Landing (LND)
Taxi-out (TXO) Taxi-in (TXI)
Hover in
Ground Effect
(IGE)
Arrival / Eng
Eng Start /
Shutdown
Depart (ESD)
(AES)
Pre-flight Post-flight
(PRF) (PSF)
Flight Planning Flight Close

(FLP) (FLC)
Ground
Servicing
(GDS)
3. Transition Relationships for Spacecraft Operations

Engine Start/Depart (Applies to Taxi-out Arrival/Engine Shutdown

Mothership)
Taxi-out (Applies to Mothership) Take-off Taxi-in
Take-off (Applies to Mothership) Initial Climb Rejected Take-off
Rejected Take-off (Applies to Taxi-in Arrival/Engine Shutdown (possibly

Mothership) associated to emergency)
Climb (Applies to Mothership) En Route Climb Approach
En Route Climb (Applies to Cruise Descent

Mothership)
Separation (Applies to Spacecraft) Engine Start / Depart Descent
Engine Start/Depart (Applies to Boost Descent

Spacecraft)
Boost (Applies to Spacecraft) In Space N/A
In Space (Applies to Spacecraft) Re-Entry N/A
Cruise (Applies to Mothership) Descent En Route Climb
Re-entry (Applies to Spacecraft) Descent N/A
Descent (Applies to Mothership) Approach Cruise or En Route Climb
Descent (Applies to Spacecraft) Approach N/A
Approach (Applies to Mothership) Landing Go-around or Initial Climb
Approach (Applies to Spacecraft) Landing N/A
Go-around (Applies to Mothership) Approach Initial Climb
Landing (Applies to Mothership) Taxi-in Go-around
Landing (Applies to Spacecraft) Tow-in (Spacecraft) N/A
Taxi-in (Applies to Mothership) Arrival/Engine Shutdown Taxi-out
Tow-In (Applies to Spacecraft) Post-Flight N/A
Arrival/Engine Shutdown (Applies Post-flight Engine Start/Depart

to Mothership)
NOTE: The Transition Relationship Diagram for Spacecraft Operations assumes that
the spacecraft is carried by a mothership to an altitude where it can be released
("separated") for flight under its own power. Therefore, the diagram covers
phases of flight for both the mothership and the spacecraft. The relationship
diagram does not cover spacecraft that is launched from a ground-based stand
under its own power.
Figure 5-3 Transition Relationships for Spacecraft Operations
In Space
(SPC)
Boost Re-Entry
(BST) (REN)
Engine Start/ Descent

Depart (ESD) (DST)
Separation Approach
(SEP) (APR)
Cruise
Landing
(CRZ)
(LND)
En Route Descent
Climb (ECL) (DST)
Tow-In
Initial Climb Approach (TOW)
(ICL) (APR)
Rejected
Go-around
Take-off
(GOA)
(RTO)
Take-off Landing
(TOF) (LND)
Taxi-out
Taxi-in (TXI)
(TXO)
Arrival / Eng
Eng Start /
Shutdown
Depart (ESD)
(AES)
Pre-flight Post-flight
(PRF) (PSF)
Flight
Flight Close
Planning
(FLC)
(FLP)
Ground
Spacecraft Servicing
(GDS)
Mothership
Both
5-1-3. Definitions
1. Flight Planning (FLP)
The Flight Planning phase begins when the flight crew initiates the use of flight planning
information facilities and becomes dedicated to a flight based upon a route and aircraft. This
phase ends when the crew arrives at the aircraft for the purpose of the planned flight or the
crew initiates a "Flight Close" phase.
2. Pre-flight (PRF)
The Pre-flight phase begins with the arrival of the flight crew at an aircraft for the purpose of
flight. This phase ends when a dedication is made to depart the parking position and/or start
the engine(s). This phase may also end by the crew initiating a "Post-flight" phase.
NOTE: The Pre-flight phase assumes the aircraft is sitting at the point at which the
aircraft will be loaded or boarded, with the primary engine(s) not operating.
If boarding occurs in this phase, it is done without any engines operating.
Boarding with any engine operating is covered under Engine Start/Depart.
3. Engine Start/Depart (ESD)

The Engine Start/Depart phase begins when the flight crew takes action to have the aircraft
moved from the parked position and/or take switch action to energize the engine(s). This phase
ends when the aircraft begins to move forward under its own power or is ready for hover, or
the crew initiates an "Arrival/Engine Shutdown" phase.
NOTE: The Engine Start/Depart phase includes: the aircraft engine(s) start-up
whether assisted or not and whether the aircraft is stationary with more than
one engine shutdown prior to Taxi-out, i.e., boarding of persons or baggage
with engines running. It includes all actions of power back for the purpose of
positioning the aircraft for Taxi-out.
4. Taxi-out (TXO)
The Taxi-out phase begins when the crew moves the aircraft forward under its own power.
This phase ends when thrust is increased for the purpose of Take-off or the crew initiates a
"Taxi-in" phase.
4.1. Taxi to Runway (TXR)
The Taxi to Runway sub-phase occurs when the crew moves the aircraft under its own power,
and ends just prior to the aircraft entering the designated active runway.
4.2. Taxi to Take-off Position (TXP)
The Taxi to Take-off Position sub-phase occurs upon entering the designated active runway
until reaching the take-off position.
4.3. Hover in Ground Effect (IGE)
The Hover in Ground Effect sub-phase begins when the helicopter leaves the ground to hover
at low height. The Hover In Ground Effect phase ends when reaching a forward ground speed
to join the take-off phase, when reaching the point where a rolling taxi is initiated, or when
reaching the parking position.
5. Take-off (TOF)
The Take-off phase begins when the crew increases the thrust for the purpose of lift-off. This
phase ends when an Initial Climb is established or the crew initiates a "Rejected Take-off"
phase.
6. Rejected Take-off (RTO)
For airplane operations, the Rejected Take-off phase begins when the crew reduces thrust for
the purpose of stopping the aircraft prior to the end of the Take-off phase. This phase ends
when the aircraft is taxied off the runway for a "Taxi-in" phase or when the aircraft is stopped
and engines shutdown.
For helicopter operations, the Rejected Take-off phase begins when the crew decides to reject
the takeoff in order to perform a landing. This phase ends when the helicopter has landed and
the Landing phase begins.
7. Climb (CLB)
The Climb phase begins when the crew establishes the aircraft at a defined speed and flight
condition that enables the aircraft to increase altitude for the purpose of cruise. This phase ends
with the aircraft established at a predetermined constant initial cruise altitude at a defined speed
or by the crew initiating the "Descent" phase.
7.1. Initial Climb (ICL)
The Initial Climb phase begins at 35 ft. above the runway elevation. This phase ends after the
speed and aircraft configuration are established at a defined maneuvering altitude or to
continue the climb for the purpose of cruise. This phase may also end by the crew initiating
an "Approach" phase.
NOTE: Maneuvering altitude is based upon such an altitude to safely maneuver the
aircraft after an engine failure occurs, or pre-defined as an obstacle clearance
altitude. Initial Climb includes such procedures applied to meet the
requirements of noise abatement climb, or best angle/rate of climb.
7.2. En Route Climb (ECL)

The En Route Climb phase begins when the crew establishes the aircraft at a defined speed
and configuration that enables the aircraft to increase altitude for the purpose of cruise. This
phase ends with the aircraft established at a predetermined constant initial cruise altitude at a
defined speed or by the crew initiating the "Descent" phase.
7.3. Top of Climb (TOC)
The Top of Climb sub-phase occurs at the point that the En Route Climb phase ends and the
Cruise phase begins.
8. Separation (SEP)
For spacecraft operations, the Separation phase begins when the mothership reaches a defined
altitude for the purpose of releasing a spacecraft for flight under its own power. This phase
ends when the spacecraft has separated from the mothership.
9. Boost (BST)
For spacecraft operations, the Boost phase begins at successful rocket motor ignition and ends
at rocket motor shutdown
10. In Space (SPC)
For spacecraft, this phase begins after the boost stage and ends at the beginning of the re-entry
phase. This phase includes the glide to apogee and the portion of flight that is exo-atmospheric.
11. Cruise (CRZ)
For airplane operations, the Cruise phase begins when the crew establishes the aircraft at a
defined speed and predetermined constant initial cruise altitude and proceeds in the direction
of a destination. This phase ends with the beginning of Descent for the purpose of an approach
or by the crew initiating an "En Route Climb" phase.
For helicopter operations, the Cruise phase begins when the crew establishes the aircraft at a
defined speed and altitude. This phase ends with the beginning of Descent, or by the crew
initiating a Hover Out of Ground Effect (HOG).
11.1. Cruise Climb (CRC)
The Cruise Climb sub-phase occurs at a change of altitude after a cruise altitude has been
established in order to re-establish cruise flight at a higher altitude.
11.2. Cruise Descent (CRD)
The Cruise Descent sub-phase occurs at a change of altitude after a cruise altitude has been
established in order to re-establish cruise flight at a lower altitude.
12. Descent (DST)
For airplane operations, the Descent phase begins when the crew departs the cruise altitude for
the purpose of an approach at a particular destination. This phase ends when the crew initiates
changes in aircraft configuration and/or speeds to facilitate a landing on a particular runway.
This phase may also end by the crew initiating an "En Route Climb" or "Cruise" phase.
For helicopter operations, the Descent phase begins when the aircraft leaves the Cruise, Hover
Out of Ground Effect or Climb phase for purposes of decreasing altitude. The Descent phase
ends when the aircraft enters a Hover Out of Ground Effect, Climb, Cruise, or Approach phase.
For spacecraft, this phase begins after the vehicle has reentered Earth’s atmosphere. This phase
would begin at the completion of the reentry phase and would end at the beginning of the
approach phase. During this phase of flight, the spacecraft has sufficiently re-entered the
atmosphere to have aerodynamic flight control of the vehicle
12.1. Top of Descent (TOD)
The Top of Descent sub-phase occurs at the point at which the Cruise phase ends and the
Descent phase begins.
13. Re-Entry (REN)
The reentry phase begins at the end of the In Space phase and ends at the beginning of the
Descent phase. During this phase of flight, the spacecraft has passed apogee and is configured
for reentry into the atmosphere and is not yet capable of atmospheric aerodynamic control.
14. Hover Out of Ground Effect (OGE)
The Hover Out of Ground Effect phase occurs when the aircraft is maintained in stationary
flight at the appropriate power setting at a constant height at least 2.5 times the rotor diameter
above ground level.
15. Approach (APR)
For aircraft and helicopter operations, the Approach phase begins when the crew initiates
changes in aircraft configuration and/or speeds enabling the aircraft to maneuver for the
purpose of landing on a particular runway. This phase ends when the aircraft is in the landing
configuration and the crew is dedicated to land on a specific runway. This phase may also end
by the crew initiating an "Initial Climb" or "Go-around" phase.
For spacecraft, this phase begins at the end of the Descent phase and ends at the beginning of
the Landing phase. There is no option for Initial Climb or Go-Around for spacecraft.
15.1. Initial Approach (IFR)
The Initial Approach sub-phase occurs during IFR flight, within the initial approach fix (IAF)
to the final approach fix (FAF) period.
15.2. Final Approach (IFR)
The Final Approach sub-phase occurs during IFR flight, from the FAF to the point in which a
dedication to landing is made or a go-around is initiated.
15.3. Circuit Pattern (VFR)
The Circuit Pattern sub-phase occurs during circuit pattern / VFR flight. A flight path normally
1,000 ft. above the runway elevation, which commences abeam the departure end of the
runway and runs parallel to the runway in the direction opposite to landing, and is further
prescribed by a rectangular pattern commonly known as cross wind, downwind, base and final.
16. Go-Around (GOA)
For airplane operations, the Go-Around phase begins when the crew aborts the descent to the
planned landing runway during the Approach phase. This phase ends after speed and
configuration are established at a defined maneuvering altitude or to continue the climb for the
purpose of cruise. (Same as end of "Initial Climb".)
For helicopter operations, the Go-Around phase begins when the crew aborts the descent to a
planned landing point. The phase ends after speed and flight conditions are established for the
new flight phase (e.g. new Approach).
17. Landing (LND)
For airplane operations, the Landing phase begins when the aircraft is in the landing
configuration and the crew is dedicated to touch down on a specific runway. This phase ends
when the speed permits the aircraft to be maneuvered by means of taxiing for the purpose of
arriving at a parking area. This phase may also end by the crew initiating the "Go-around"
phase.
For helicopter operations, the Landing phase begins when the aircraft is in the landing
configuration and the crew is dedicated to touch down on a specific runway. This phase ends
with touch-down, or when the Hover In Ground Effect or Go Around phases begin.
For spacecraft, this phase begins at the end of the Descent phase and ends at the beginning of
the Landing phase. There is no option for Initial Climb or Go-Around for spacecraft.
17.1. Flare (LNF)
The Flare sub-phase occurs during the pitch up to a higher nose up attitude maneuver, in order
to reduce vertical speed just before landing until touchdown.
17.2. Landing Roll (LNR)
The Landing Roll sub-phase occurs from touchdown until the aircraft is stopped or the speed
permits the aircraft to be maneuvered by means of taxiing
18. Taxi-in (TXI)
The Taxi-in phase begins when the crew begins to maneuver the aircraft under its own power
to an arrival area for the purpose of parking; it ends when the aircraft is committed to moving
into a parked position. This phase may also end by the crew initiating a "Taxi-out" phase.
19. Tow-in (TOW)
The Tow-in phase begins when an aircraft is moved by ground equipment to an arrival area for
the purpose of parking; it ends when the aircraft is in a parked position.
20. Arrival/Engine Shutdown (AES)
The Arrival / Engine Shutdown phase begins when the crew begins to maneuver the aircraft
into a parking position, under its own power or under tow. This phase ends with the aircraft in
a parked position with the engine(s) shut down with a dedication to shutting down ancillary
systems for the purpose of securing the aircraft. This phase may also end by the crew initiating
an "Engine Start / Depart" phase.
NOTE: The Arrival/Engine Shutdown phase includes actions required during a time
when the aircraft is stationary with one or more engines operating while
ground servicing may be taking place, i.e., deplaning persons or baggage with
engine(s) running, and/or refueling with engine(s) running.
21. Post-flight (PSF)

The Post Flight phase begins when the crew commences the shutdown of ancillary systems of
the aircraft for the purpose of leaving the flight deck. This phase ends when the cockpit and
cabin crew leaves the aircraft. This phase may also end by the crew initiating a "Pre-flight"
phase.
22. Flight Close (FLC)
The Flight Close phase begins when the crew initiates a message to the flight-following
authorities that the aircraft is secure, and the crew is finished with the duties of the past flight.
This phase ends when the crew has completed these duties or begins to plan for another flight
by initiating a "Flight Planning" phase.
23. Ground Servicing (GDS)
The Ground Servicing phase begins when the aircraft is stopped and available to be safely
approached by ground personnel for the purpose of securing the aircraft and performing the
duties applicable to the arrival of the aircraft, aircraft maintenance, etc. This phase ends with
completion of the duties applicable to the departure of the aircraft or when the aircraft is no
longer safe to approach for the purpose of ground servicing, e.g., prior to crew initiating the
"Taxi-out" phase.
NOTE: This phase was identified by the need of information that may not directly
require the input of cockpit or cabin crew. It is acknowledged as an entity to
allow placement of the tasks required of personnel assigned to service the
aircraft.
5-2. ATA Flight Operations Standard Numbering System
The ATA Flight Operation Standard Numbering System (SNS) is used to facilitate
organization and identification of flight operations data modules. It is based on the System
level of the ATA SNS as described in ATA iSpec 2200, but has been optimized at the
Subsystem level for flight operations data.
Note: The Dispatch Data types described in this specification do not use this SNS, but
instead use the Standard Numbering System described in ATA iSpec 2200
(first 3 digits).
SYSTEM SUBSYSTEM TITLE DEFINITION
0 Non-System Specific Used for information that does not pertain to a

Information specific system, or pertains to multiple systems
and that is not specific to crew (e.g. Information
related to a list of abbreviations, etc.).
1 *Reserved for Airline Use
5 TIME LIMITS/ Not applicable for Flight Crew Operations

MAINTENANCE CHECKS Applications
6 DIMENSIONS AND AREAS Those charts, diagrams, and text which show the
area, dimensions, stations, access doors/zoning
and physical locations, of the major structural
members of the aircraft. Includes an explanation
of the system of zoning and measurement used.
7 LIFTING & SHORING Not applicable for Flight Crew Operations

Applications
8 WEIGHT AND BALANCE All weight and balance data specifically related to
a group of aircraft, including volume, maximum
weight, and recommended nominal balance
arm(s).
-00 General
-20 Fuel Weight and balance data pertaining to fuel

management and loading.
-30 Fluids Weight and balance data pertaining to

management and loading of fluids (other than
fuel).
-40 Interior Arrangement Weight and balance data pertaining to aircraft

interior configuration and personnel (i.e., crew
members, passengers, and supernumeraries).
-60 Cargo Weight and balance data pertaining to cargo

(and baggage) compartments and associated
partitions.
-80 Ground Operations Weight and balance data pertaining to ground

operations, including jacking, towing, weighing,
and loading.
-90 Examples Examples such as completed work sheets and

calculations used. Provided to clarify the use of
data contained in the WBM.
9 TOWING & TAXIING Those instructions necessary to tow and taxi the
aircraft
10 PARKING, MOORING, Not applicable for Flight Crew Operations

STORAGE & RETURN TO Applications
SERVICE
11 PLACARDS AND MARKINGS Not applicable for Flight Crew Operations

Applications
12 SERVICING Not applicable for Flight Crew Operations

Applications
13 *Unassigned
14 *Unassigned
15 .. Crew Procedure Specific information given to crew members for

performing the designated missions of the
aircraft that does not pertain to a specific system
16 *Unassigned
17 *Unassigned
18 VIBRATION AND NOISE Not applicable for Flight Crew Operations

ANALYSIS (HELICOPTER Applications
ONLY)
19 *Unassigned
20 STANDARD PRACTICES- Not applicable for Flight Crew Operations

AIRFRAME Applications
21 ENVIRONMENTAL CONTROL Those units and components which furnish a

means of pressurizing, heating, cooling, moisture
controlling, filtering and treating the air used to
ventilate the areas of the fuselage within the
pressure seals. Includes cabin supercharger,
equipment cooling, heater, heater fuel system,
expansion turbine, valves, scoops, ducts, etc.
-00 General
-20 Distribution That portion of the system used to induct and

distribute air. Includes equipment rack cooling
systems and items such as blowers, scoops,
ducting, inlets, check valves, wiring, etc. Does
not include valves which are part of
pressurization and temperature control.
-30 Pressurization Control That portion of the system used to control the
pressure within the fuselage. Includes items
such as control valves, relief valves, indicators,
switches, amplifiers, wiring, etc.
-60 Temperature Control That portion of the system used to control the
temperature of the air. Includes items such as
control valves, thermal sensing devices, switches,
indicators, amplifiers, wiring, etc.
-70 Moisture/Air Contaminant That portion of the system used to control

Control moisture in the air, to control ozone
concentrations, to filter radioactive debris from
conditioned air, and to treat the air with
deodorizers, insecticides, etc.
22 AUTO FLIGHT Those units and components which furnish a

means of automatically controlling the flight of
the aircraft. Includes those units and
components which control direction, heading,
attitude, altitude and speed.
-00 General
-10 Autopilot / Flight Director That portion of the system that uses radio/radar
signals, directional and vertical references, air
data pitot-static, computed flight path data, or
manually induced inputs to the system to
automatically control the flight path of the
aircraft through adjustment to the pitch/roll/yaw
axis or wing lift characteristics and provide visual
cues for flight path guidance, i.e.: Integrated
Flight Director. This includes power source
devices, interlocking devices and amplifying,
computing, integrating, controlling, actuating,
indicating and warning devices such as
computers, servos, control panels, indicators,
warning lights, etc.
-20 Speed-Attitude Correction That portion of the system that automatically

/ Automatic Envelope maintains safe flight conditions by correcting for
Protection effects of speed and out-of-trim conditions by
such means as automatic trim, mach trim or
speed stability and mach feel. This includes
sensing, computing, actuating, indicating,
internal monitoring, and warning devices, etc.
-30 Autothrottle / Autothrust That portion of the system that automatically

controls the position of the throttles / thrust
levers and/or engine thrust to properly manage
engine power during all phases of flight/attitude.
This includes engaging, sensing, computing,
amplifying, controlling, actuating and warning
devices such as amplifiers, computers, servos,
limit switches, clutches, gear boxes, warning
lights, etc.
-40 Flight Management System That portion of the system which combines
navigational data to compute or manage the
aircraft's geographical position or theoretical
flight path. Includes items such as course
computers, flight management computers,
performance data computers, and associated
control display units, warning annunciators, etc.
-50 Automatic Flight Operations That portion of the system that describes the
integration of the various components of the
automatic flight system (autopilot, autothrottle,
flight director, FMC/FMS, etc.) and how they
control the movement of the aircraft through
different phases of flight including Takeoff and
Climb out, Enroute, Approach and Landing, and
Go-around.
23 COMMUNICATIONS Those units and components which furnish a

means of communicating from one part of the
aircraft to another and between the aircraft and
another aircraft or ground stations. Includes
voice, data, C-W communicating components,
reproducers, all transmitting/receiving
equipment, associated antennas, etc.
-00 General
-10 Speech Communications That portion of the system which utilizes voice
modulated electromagnetic waves to transmit
and/or receive messages from air to air, or air to
ground installations. Includes H.F., VHF., UHF.,
etc., inflight telephone, communication
transmitting & receiving equipment. Passenger
air-to-ground communications now in [Chapter
(System) 44-30]
-15 SATCOM That portion of the system which utilizes satellite

communication systems (SATCOM).
-20 Data Transmission and That portion of the system which presents
Automatic Calling information derived from pulse coded
transmissions. Includes Teleprinter, Selcal,
Calsel, ACARS, etc.
-30 Passenger Address That portion of the system used to make

announcements to passengers. Includes items
such as speakers, handsets, control panels, etc.
-40 Interphone That portion of the system which is used by

flight, cabin, and ground personnel to
communicate between areas on the aircraft.
Includes items such as amplifier, handset, etc.
-50 Audio Integrating That portion of the system which controls the
output of the communications and navigation
receivers into the flight crew headphones and
speakers and the output of the flight crew
microphones into the communications
transmitters. Also includes the flight to ground
personnel communications. Includes items such
as audio selector control panel, micro-phones,
headphones, cockpit loudspeakers, etc.
-60 Static Discharging That portion of the system which is used to

dissipate static electricity.
-70 Emergency communication That portion of the system that enables

emergency communication. Includes ELT.
24 ELECTRICAL POWER Those electrical units and components which

generate, control and supply AC and/or DC
electrical power for other systems, including
generators and relays, inverters, batteries, etc.,
through the secondary buses. Also includes
common electrical items such as wiring,
switches, connectors, etc.
-00 General
-20 AC Power That portion of the systems used to generate and

regulate AC electrical power. Includes items
such as inverters, AC generators/ alternators,
control and regulating components, indicating
systems, etc., all wiring to but not including main
buses. Also includes load shedding/monitoring
systems.
-30 DC Power That portion of the systems used to generate and

regulate DC electrical power. Includes items
such as generators/ alternators, transformers,
rectifiers, batteries, control and regulating
components, indicating systems, etc., all wiring
to but not including main buses.
-40 External Power That portion of the system within the aircraft
which connects external electrical power to the
aircraft's electrical system. Includes items such
as receptacles, relays, switches, wiring, warning
lights, etc.
-50 AC Electrical Load That portion of the system which provides for
Distribution connection of AC power to using systems.
Includes items such as AC main and secondary
buses, main system circuit breakers, power
system devices, etc.
-60 DC Electrical Load That portion of the system which provides for
Distribution connection of DC power to using systems.
Includes items such as DC main and secondary
buses, main system circuit breakers, power
system devices, etc.
-70 Standby Power That part of the system used to supply electrical
power, to include emergency power generation
(e.g. RAT, static inverters, backup batteries) in
the event of loss of all Engine Driven Generators
and/or external power.
25 EQUIPMENT/FURNISHINGS Those removable items of equipment and

furnishings contained in the flight and passenger
compartments. Includes emergency, galley and
lavatory equipment. Does not include structures
or equipment assigned specifically to other
chapters.
-00 General
-10 Flight Compartment The compartment above the floor and between
the forward passenger partition and the forward
pressure dome. Includes items such as flight
crew seats, tables, pilot check lists and food
containers, wardrobes, curtains, manuals,
electronic equipment rack, spare bulbs, fuses,
etc. Does not include cargo compartments.
-20 Passenger Compartment The areas in which the passengers are seated.
Includes lounges but not dressing rooms.
Includes items such as seats, berths, overhead
storage compartments, curtains, wall coverings,
carpets, magazine racks, wardrobes, movable
partitions, wall-type thermometers, spare bulbs,
fuses, etc.
-30 Galley The areas in which food and beverages are

stored and prepared. Includes items such as
removable and fixed cabinets, ovens,
refrigerators, garbage containers, dish racks,
coffee maker and dispensers, containers,
electrical outlets, wiring, etc.
-40 Lavatories The toilet and dressing room areas containing

wash basins, dressing tables, and water closet.
Includes items such as mirrors, seats, cabinets,
dispensing equipment, electrical outlets, wiring,
etc. Wash basins and water closets are included
in [Chapter (System) 38].
-50 Crew Compartments Those additional compartments for the use of

crew. Includes such compartments as crew rest
compartments, sleeping compartments etc.
-60 Emergency Those items of equipment carried for use in

emergency procedures. Includes items such as
evacuation equipment, life rafts, jackets,
emergency locator transmitters, underwater
locator devices, first aid kit, incubators, oxygen
tents, medical stretchers, landing and signal
flares, drag parachutes, evacuation signaling
systems, etc. Does not include fire extinguishers,
oxygen equipment or masks.
26 FIRE PROTECTION Those fixed and portable units and components

which detect and indicate fire or smoke and
store and distribute fire extinguishing agent to all
protected areas of the aircraft; including bottles,
valves, tubing, etc.
-00 General
-10 Detection That portion of the system which is used to sense

and indicate the presence of overheat, smoke, or
fire.
-20 Extinguishing That portion of those fixed or portable systems

which is used to extinguish fire.
27 FLIGHT CONTROLS Those units and components which furnish a

means of controlling the flight attitude
characteristics of the aircraft, including items
such as hydraulic boost system, rudder pedals,
controls, mounting brackets, etc. Also includes
the functioning and maintenance aspects of the
flaps, spoilers and other control surfaces, but
does not include the structure which is covered
in the Structures Chapters. Does not include
rotorcraft rotor controls which are covered in
[Chapter (System) 65].
-00 General
-10 Roll Control The control surfaces and control systems which
provide the movement around the roll axis.
-20 Yaw Control The control surfaces and control systems which
provide the movement around the yaw axis.
-30 Pitch Control The control surfaces and control systems which
provide the movement around the pitch axis.
-50 Flaps and Slats Leading edge and trailing edge flaps, slats and
devices. Includes specific functions such as,
Speed Lock function, Cruise Baulk Function, ARS
and AES functions.
-60 Speedbrakes, Spoiler, Drag That portion of the systems which controls the
Devices and Variable position and movement of the speedbrakes,
Aerodynamic Fairings spoilers, drag devices and variable aerodynamic
fairings. Includes fairings. Includes items such as
control handles, cables, warning systems,
linkages, spoilers, drag devices, position
indicators, etc.
-70 Aerodynamic Load The system or portion of the system that

Alleviating automatically corrects/provides for gust
loading/upset, aerodynamic
augmentation/alleviation/suppression, ride
control, etc. This includes sensing, computing,
actuating, indicating internal monitoring,
warning devices, etc.
-80 Flight Control Computers The computers that control the position and
movement of the flight control surfaces,
including the normal flight control laws,
alternate law, and/or reconfiguration laws.
Includes load alleviation function.
28 FUEL Those units and components which store and

deliver fuel to the engine. Includes engine driven
fuel pumps for reciprocating engines, includes
tanks (bladder), valves, boost pumps, etc., and
those components which furnish a means of
dumping fuel overboard. Includes integral and
tip fuel tank leak detection and sealing. Does not
include the structure of integral or tip fuel tanks
and the fuel cell backing boards which are
covered in the Structures Chapters, and does not
include fuel flow rate sensing, transmitting
and/or indicating, which are covered in [Chapter
(System) 73].
-00 General
-10 Storage That portion of the system which stores fuel.

Includes tank sealing, bladder type cells,
ventilating system, cell and tank inter-
connectors, over wing filler necks and caps, etc.
Also includes reservoir feed pumping systems
and reservoirs within the tanks which are not
part of the distribution system.
-20 Distribution & That portion of the system which is used to

Management distribute fuel from the filler connector to the
storage system and from the storage system to
and including the power plant fuel quick
disconnect. Includes items such as plumbing,
pumps, valves, controls, crossfeed, imbalance,
etc.
29 HYDRAULIC POWER Those units and components which furnish

hydraulic fluid under pressure (includes pumps,
regulators, lines, valves, etc.) to a common point
(manifold) for redistribution to other defined
systems.
-00 General
-10 Main That portion of the system which is used to store

and deliver hydraulic fluid to using systems.
Includes items such as tanks, accumulators,
valves, pumps, levers, switches, cables,
plumbing, wiring, external connectors, etc. Does
not include the supply valves to the using
systems.
-20 Auxiliary That portion of the system which is classified as

auxiliary, emergency or standby, and which is
used to supplement or take the place of the main
hydraulic system. Includes items such as tanks
and accumulators which are separate from the
main system, hand pumps, auxiliary pumps,
valves, plumbing, wiring, etc.
30 ICE AND RAIN PROTECTION Those units and components which provide a
means of preventing or disposing of formation of
ice and rain on various parts of the aircraft.
Includes alcohol pump, valves, tanks,
propeller/rotor anti-icing system, wing heaters,
water line heaters, pitot heaters, scoop heaters,
windshield wipers and the electrical and heated
air portion of windshield ice control. Does not
include the basic windshield panel.
For turbine type power plants using air as the

anti-icing medium, engine anti-icing is contained
under Air System.
-00 General
-10 Airfoil That portion of the system which is used to

eliminate or prevent the formation of ice on all
airfoil surfaces. Includes wings, airfoil sections of
the empennage, and pylons.
-20 Engine Cowl and Air Intakes That portion of the system which is used to
eliminate or prevent the formation of ice in or
around air intakes. Includes power plant cowling
anti-icing.
-30 Probes and Sensors That portion of the system which is used to
eliminate or prevent the formation of ice on the
pitot and static probes and sensors.
-40 Windows, Windshields and That portion of the system which is used to
Doors eliminate or prevent the formation of ice, frost
or rain on the Windows, windshields and doors.
-50 Antennas and Radomes That portion of the system which is used to
eliminate or prevent the formation of ice on
antennas and radomes.
-60 Propellers/Rotors That portion of the system which is used to

eliminate or prevent the formation of ice on
propellers or rotors. Includes all components up
to but not including rotating assembly.
-70 Water Lines That portion of the system which is used to

prevent the formation of ice in water supply and
drain lines.
-80 Detection That portion of the system which is used to

detect and indicate the formation of ice.
31 INDICATING/RECORDING Pictorial coverage of all instruments, instrument

SYSTEMS panels and controls.
Procedural coverage of those systems which give

visual or aural warning of conditions in unrelated
systems. Units which record, store or compute
data from unrelated systems. Includes
systems/units which integrate indicating
instruments into a central display system and
instruments not related to any specific system.
-00 General
-10 Primary Flight Instruments Those systems and components which give visual
and Displays display of conditions in unrelated systems. i.e.
How the PFD/ND and MFD work together,
display switching (auto and manual) etc.
Includes Primary Flight Instruments,
Central/Common Display Systems (CDS),
Electronic Flight Instrument System (EFIS), and
Head Up Display / Head Up Guidance System
(HUD/HGS).
-20 Standby/Independent Coverage of those instruments that display basic

Instruments flight information to the pilots and are
independent of the primary flight and navigation
displays. i.e. standby instruments, clocks, timers
etc.
-30 Flight Recorders Those systems and components used for

recording data not related to specific systems.
Includes items such as flight recorders,
performance or maintenance recorders, VG
recorders, etc.
-40 Central Computers Those systems and components used for

computing data from a number of different
sources without a preponderance of functions in
any one system. Includes items such as stored
check list, emergency procedures, Cursor
Control Devices (CCD), keyboards, etc., for call up
on a display.
-50 Central Warning Systems Those systems and components which give
audible or visual warning of conditions in
unrelated systems. Includes items such as
master warning or flight warning systems,
central instrument warning, or caution and
warning systems, tone generators, annunciators,
etc.
-60 Central Display Those systems and components which give visual
Systems/ECAM/EICAS display of conditions in unrelated systems.
-70 Automatic Data Reporting Those systems and components used for
Systems collating and computing data from unrelated
systems and transmitting same automatically.
Includes ASDAR systems and components.
-80 Audio & Video Monitoring Those installations that record, or monitor crew
conversation or movement, or provide external
monitoring, for security or safety purposes.
Includes externally mounted cameras, voice
and/or video recorders, etc., used for aircraft
operations.
32 LANDING GEAR Those units and components which furnish a

means of supporting and steering the aircraft on
the ground or water, and make it possible to
retract and store the landing gear in flight.
Includes tail skid assembly, brakes, wheels,
floats, skids, skis, doors, shock struts, tires,
linkages, position indicating and warning
systems. Also includes the functioning and
maintenance aspects of the landing gear doors
but does not include the structure which is
covered in [Chapter (System) 52].
-00 General
-10 Main Gear and Doors That portion of the system which provides the
major support for the aircraft while on the
ground. Includes items such as shock struts,
bogie axles, drag struts, doors, linkages, attach
bolts, etc.
-20 Nose Gear and Doors That portion of the system which supports the
nose of the aircraft while the aircraft is on the
ground. Includes items such as shock struts, drag
struts, doors, linkages, attach bolts, etc.
-30 Extension and Retraction That portion of the system which is used to
extend and retract the landing gear and open
and close the landing gear doors. Includes items
such as actuating mechanisms, bogie trim,
bungees, up and down latches, operating
controls, valves and motors, cables, wiring,
plumbing, etc.
-40 Wheels and Brakes That portion of the system which provides for
rolling and stopping the aircraft while on the
ground and stopping wheel rotation after
retraction. Includes items such as bearings, tires,
valves, de-boosters, swivel glands, anti-skid
devices, pressure indicators, plumbing, etc.
-50 Steering That portion of the system which is used to

control the direction of movement of the aircraft
on the ground. Includes items such as actuating
cylinders, controls, bogie swivel unlock, etc.
-60 Position and Warning That portion of the system which is used to
indicate and warn of the position of the landing
gear/doors. Includes items such as switches,
relays, lights, indicators, horns, wiring, etc.
-70 Supplementary Gear Devices used to stabilize the aircraft while on the
ground and prevent damage by ground contact.
Includes items such as shock strut, skid block,
wheels, etc.
33 LIGHTS Those units and components (electrically

powered) which provide for external and internal
illumination such as landing lights, taxi lights,
position lights, rotating lights, ice lights, master
warning lights, passenger reading and cabin
dome lights, etc. Includes light fixtures, switches
and wiring. Does not include warning lights for
individual systems or self-illuminating signs (see
[Chapter (System) 11]).
-00 General
-10 Flight Compartment The lighting sub-systems in the compartment

above the floor and between the forward
passenger partition and the forward pressure
dome. Does not include cargo compartment.
Includes direct and indirect illumination of work
areas, panels, and instruments. Includes master
warning light and warning light dimming
systems, where not integrated with a central
audio or visual system under 31-50.
-20 Passenger Compartment The lighting sub-systems in the areas in which

the passengers are seated and in buffet/galley,
lavatories, lounges and coat rooms. Includes
items such as direct and indirect illumination,
passenger call system, lighted signs, etc.
-30 Cargo and Service The lighting sub-systems in the compartments

Compartments for stowage of cargo and the housing of various
components of accessories.
-40 Exterior The lighting sub-systems used to provide

illumination outside of the aircraft. Includes
lights such as landing, navigation, position
indicating, wing illumination, rotating, courtesy,
taxi, etc.
-50 Emergency Lighting The separate and independent sub-system used

to provide illumination in case of primary
electrical power failure. Includes items such as
inertia flashlights, lanterns, etc.
34 NAVIGATION Those units and components which provide

aircraft navigational information. Includes VOR,
pitot, static, ILS, flight director, compasses,
indicators, etc.
-00 General
-10 Flight Environment Data That portion of the system which senses
environmental conditions and uses the data to
influence navigation. Includes such items as
Central Air Data Computers, pitot/static systems,
air temperature, rate-of-climb, airspeed, high
speed warning, altitude, altitude reporting,
altimeter correction system, air disturbance
detection system, etc.
-20 Attitude & Direction The portion of the system which uses magnetic
or inertia forces to sense and display the
direction or attitude of the aircraft. This includes
sensing, computing, indicating and warning
devices such as magnetic compasses, vertical and
directional references, magnetic heading
systems, attitude director systems, symbol
generators, turn and bank, rate of turn,
amplifiers, indicators, etc. Includes Flight
Director when it is not integral with the auto
pilot computation.
-30 Landing and Taxiing Aids That portion of the system which provides
guidance during approach, landing and taxiing.
Includes items such as localizer, glide slope, ILS,
markers, paravisual director ground guidance
systems, etc.
-40 Independent Position That portion of the system which provides

Determining information to determine position and is mainly
independent of ground installations or orbital
satellites. Includes items such as inertial
guidance systems, etc.
-50 Dependent Position That portion of the system which provides

Determining information to determine position and is mainly
dependent on ground installations or orbital
satellites. Includes items such as DME, radio
compass, LORAN, VOR, ADF, GLOBAL
POSITIONING, etc.
-60 Surveillance That portion of the system which provides

ground proximity warning, weather, wind shear
and turbulence information, detects, displays
surrounding aircraft, calculates possible collision
threats and triggers orders, and reports aircraft
position to ATC.
35 OXYGEN Those units and components which store,

regulate, and deliver oxygen to the passengers
and crew, including bottles, relief valves, shut-off
valves, outlets, regulators, masks, walk-around
bottles, etc.
-00 General
-10 Crew That portion of the system which furnishes

oxygen to the crew.
-20 Passenger That portion of the system which furnishes

oxygen to the passengers.
-30 Portable That portion of the system which has an

independent oxygen supply and which can be
transported about the aircraft.
36 PNEUMATIC Those units and components (Ducts and Valves)

which deliver large volumes of compressed air
from a power source to connecting points for
such other systems as air conditioning,
pressurization, deicing, etc.
0 General
-10 Distribution That portion of the system which is used to

distribute high or low-pressure air to using
systems. Includes items such as ducts, valves,
actuators, heat exchangers, controls, etc. Does
not include the supply valves to the using
systems. Includes temperature and pressure
warning systems.
-30 Leak Detection That portion of the system which is used to

detect bleed air leaks.
-40 Bleed Air That portion of the system and its controls which
supplies compressed air. Includes items such as
controls and indicating systems related to the
compressors, wiring, etc. Does not include the
pressure control and indicating system for the
cabin pressurization.
37 VACUUM Not applicable for Flight Crew Operations

Applications
38 WATER/WASTE Those fixed units and components which store

and deliver for use, fresh water, and those fixed
components which store and furnish a means of
removal of water and waste. Includes wash
basins, toilet assemblies, tanks, valves, etc.
-00 General
-10 Potable That portion of the system which is used to store

and deliver fresh drinking water. Includes wash
water system if the potable water is also used for
washing.
-20 Wash That portion of the system which is used to store

and deliver wash water which is not potable.
-30 Waste Disposal That portion of the system which is used for
disposal of water and waste. Includes items such
as wash basins, water closets, flushing systems,
etc.
-40 Air Supply That portion of the system common to more

than one sub-system which is used for
pressurizing supply tanks to insure fluid flow.
39 *Unassigned
40 *Unassigned
41 WATER BALLAST Not applicable for Flight Crew Operations

Applications
42 INTEGRATED MODULAR Generalize computing devices that can host

AVIONICS software applications for system functions that
had traditionally been implemented in dedicated
hardware. The actual system functions are
covered in their respective ATA chapters.
-00 General
-10 Shared Avionic Resources The resources, which provide processing, I/O,
network and power supply conditioning
capabilities necessary to host system functions.
This sub-chapter describes the resources, the
means of communication between these
resources and their installation.
-20 Core System Contains information about the main computing

devices of the system.
-30 Communication Network The data communication network used for

operational communication between systems.
This network may also be used for
communication within systems and for data
loading. This sub-chapter describes all
components of the network and their installation
in the aircraft.
-40 Remote Shared Resources The resources installed remotely from the main
avionics that may be used by more than one
system, e.g. Remote Data Concentrator (RDC).
43 *Unassigned
44 CABIN SYSTEMS Those units and components which furnish a

means of entertaining the passengers and
providing communications within the aircraft and
between the aircraft cabin and ground stations.
Includes voice, data, music and video
transmissions. It does not include SATCOM, HF,
VHF UHF and all transmitting/receiving
equipment, antennas, etc. which are covered in
Systems 23 or System 46.
-00 General
-10 Cabin Core System That portion of the system used to accomplish
the integrated functional control, operation,
testing and monitoring of cabin systems and to
increase cabin comfort (such as active noise
control). Includes items such as controllers, cabin
control panels, handsets, signs, loudspeakers,
etc.
-20 Inflight Entertainment That portion of the system used to entertain the
System passengers with music, video, information,
games, etc. Includes items such as controllers,
cabin control panels, audio and video
equipment, etc.
-30 External Communication That portion of the system used by passengers

System and cabin crew to transmit and/or receive
data/messages from air to air or from air to
ground installations. Includes items such as
telephones, telefaxes, modems, AM/FM radio
units, etc.
-40 Cabin Mass memory System That portion of the system used to store and
process cabin related data, such as systems
configuration data, multimedia programs, etc.
Includes items such as controllers, terminals,
keyboards, disk drives, printers, modems, etc.
-50 Cabin Monitoring System The portion of the system used to monitor parts
of the cabin area. Includes items such as
surveillance cameras, monitors, etc. Does not
include external anti-hijack devices or external
video monitoring which are covered in System
23.
-60 Miscellaneous Cabin System That portion of the system used to support
miscellaneous cabin functions
45 CENTRAL MAINTENANCE Those units, components and associated system

SYSTEM (CMS) which interfaces with multiple aircraft systems.
Contains checkout and fault isolation procedures
using a central computer complex and/or
standard fault isolation procedures to locate a
single system or component malfunction.
-00 General
-5 thru -19 CMS/Aircraft General Central Maintenance System interfaces with

General Aircraft systems and identification of
maintenance functions related to Aircraft
General.
-20 thru -49 CMS/Airframe Systems Central Maintenance System interfaces with
Airframe Systems, and identification of
maintenance functions related to Airframe
Systems.
-45 Central Maintenance That portion of the system which interfaces with
System other aircraft systems, flight line mechanics, and
radio communications. Includes computers,
storage devices, control and display devices.
-50 thru -59 CMS/Structures Central Maintenance System interfaces with

Structures, and identification of maintenance
functions related to Structures.
-60 thru -69 CMS/Propellers Central Maintenance System interfaces with

Propeller, and identification of maintenance
functions related to Propellers.
-70 thru -89 CMS/Power Plant Central Maintenance System interfaces with
Power Plant, and identification of maintenance
functions related to Power Plant.
46 INFORMATION SYSTEMS Those units and components which furnish a

means of storing, updating, and retrieving digital
information traditionally provided on paper,
microfilm, or microfiche. Includes units that are
dedicated to the information storage and
retrieval function such as the Electronic Library
mass storage and controller. Does not include
units or components installed for other uses and
shared with other systems, such as flight deck
printer or general use display.
-00 General
-20 Flight Deck Information That portion of the onboard information system
Systems that supports the flight deck systems, flight deck
crew, flight operations, Electronic Flight Bag
(EFB) and ATC datalink (FANS).
-30 Maintenance Information That portion of the onboard flight information

Systems system that supports all onboard maintenance
system functions, maintenance technicians, and
any ground based maintenance activity.
-40 Passenger Cabin That portion of the onboard information system

Information Systems that supports the passenger cabin, cabin
operations, and flight attendants.
47 INERT GAS SYSTEM Those units and components used to generate,

store, deliver and regulate inert gas. Includes
regulators, lines, manifolds, etc.
0 General
-10 Generation/Storage That portion of the system which generates

and/or stores inert gas. Includes tanks, cells,
reservoirs, accumulators, etc. Does not include
plumbing, pumps, valves, controls, etc.
-20 Distribution That portion of the system which is used to

distribute inert gas to the using systems. Includes
plumbing, pumps, valves, regulators, etc.
48 *Unassigned
49 AIRBORNE AUXILIARY Those airborne power plants (engines) which are

POWER installed on the aircraft for the purpose of
generating and supplying a single type or
combination of auxiliary electric, hydraulic,
pneumatic or other power. Includes power and
drive section, fuel, ignition and control systems;
also wiring, indicators, plumbing, valves, and
ducts up to the power unit.
-00 General
50 CARGO COMPARTMENTS Those compartments for storage of cargo.

Includes those systems used to load/unload
cargo and other cargo related systems. Does not
include aircraft structure which is in [Chapter
(System) 53]
-00 General
-10 Cargo Compartments Those compartments for storage of cargo.
-20 Cargo Loading Systems Those systems which have components which
are or can be mounted on the aircraft and used
to load/unload, restrain, guide or service cargo.
Includes drive systems, rollers, latches, restraint
nets etc.
-30 Cargo Related Systems Those systems which are related to

loading/unloading of cargo. Includes aircraft
levelling, loader alignment systems etc. Does not
include Cargo Loading Systems.
51 STANDARD PRACTICES AND Not applicable for Flight Crew Operations

STRUCTURES - GENERAL Applications
52 DOORS Removable units used for entrance or exit, and

for enclosing other structure contained within
the fuselage. Includes passenger and crew
doors, cargo doors, emergency exits, etc.
Electrical and hydraulic systems associated with
door control are included as appropriate.
-00 General
-10 Passenger/Crew Doors used for entrance and exit of the

passengers and crew to and from the aircraft.
Includes items such as structure, latching
mechanisms, locking units, handles, insulation,
lining, controls, integral steps, ramps, handrails,
attach/attached fittings, etc.
-20 Emergency Exit Exit doors used to facilitate evacuation that are
not normally used for exit. Includes items such
as structure, latching mechanisms, locking units,
handles, insulation, lining, controls,
attach/attached fittings, etc.
-30 Cargo Exterior doors used primarily to gain access to

cargo compartments. Includes items such as
structure, latching mechanisms, motors, handles,
insulation, lining, controls, integral steps, ramps,
handrails, attach/attached fittings, etc.
-40 Service and Miscellaneous Exterior doors used primarily to gain access for
servicing aircraft systems and equipment and
miscellaneous exterior doors used to fulfill
system functions. Includes items such as
structure, latching mechanisms, handles,
insulation, lining, controls, integral steps,
handrails, attach/attached fittings, etc.
-50 Fixed Interior Doors inside the fuselage installed in fixed

partitions. Includes items such as structure,
latching mechanisms, handles, lining,
attach/attached fittings, etc. Does not include
doors installed in movable partitions which are
covered in [Chapter (System) 25].
-60 Entrance Stairs Stairs which operate in conjunction with but are
not an integral part of entrance doors. Stairs
whose primary structure is a door shall be
covered under the appropriate topic. Includes
items such as structure, actuating mechanisms
and controls, handrails, attach/attached fittings,
etc.
-80 Landing Gear Structure of the doors used to enclose the

landing gear compartments. Includes items such
as structure, latching mechanisms, handles,
insulation, lining, controls, attach/attached
fittings, etc.
53 FUSELAGE Not applicable for Flight Crew Operations

Applications
54 NACELLES/PYLONS Not applicable for Flight Crew Operations

Applications
55 STABILIZERS Not applicable for Flight Crew Operations

Applications
56 WINDOWS Crew compartment windows and windshield.
-00 General
-10 Flight Compartment Compartment above the floor and between the
forward passenger partition and the forward
pressure dome. Includes items such as the
transparent material and its frame of sliding and
fixed windows and windshields, handles, latching
mechanisms, etc. Does not include door or
inspection/observation windows.
57 WINGS Not applicable for Flight Crew Operations

Applications
58 *Unassigned
60 STANDARD PRACTICES - Not applicable for Flight Crew Operations

PROPELLER/ROTOR Applications
61 PROPELLERS/PROPULSION The complete mechanical or electrical propeller,

pumps, motors, governor, alternators, and those
units and components external to or integral
with the engine used to control the propeller
blade angle. Includes propeller spinner
synchronizers. Also includes propulsor duct
assemblies, including aerodynamic fairing of
mechanical components, stators, vectoring
systems, etc.
-00 General
-10 Propeller Assembly That portion of the system which rotates except
the engine propeller shaft. Includes items such
as blades, dome, hub, spinner, slip ring, deicer
boot, distributor valve, etc.
-20 Controlling That portion of the system which controls the

pitch of the propeller blades. Includes items
such as governor synchronizers, switches, wiring,
cables, levers, etc. Does not include any parts
which rotate with the propeller assembly. Also
includes all those units and components
provided for the propulsor vector drive system.
Includes flight deck control, drive motors,
gearboxes, drive shafts, synchronizing shafts, etc.
-30 Braking That portion of the system which is used to

decrease run-down time or stop propeller
rotation during engine power-off conditions.
Includes brake mechanisms, levers, pulleys,
cables, switches, wiring, plumbing, etc.
-50 Propulsor Duct The complete duct assembly including vector

drive attachment, fairings, stators, gearbox
covers, etc.
62 ROTOR(S) Not applicable for Flight Crew Operations

Applications
63 ROTOR DRIVE(S) Not applicable for Flight Crew Operations

Applications
64 TAIL ROTOR Not applicable for Flight Crew Operations

Applications
65 TAIL ROTOR DRIVE Not applicable for Flight Crew Operations

Applications
66 FOLDING BLADES/PYLON Not applicable for Flight Crew Operations

Applications
67 ROTORS FLIGHT CONTROL Not applicable for Flight Crew Operations

Applications
68 *Unassigned
69 *Unassigned
70 STANDARD PRACTICES -
ENGINES
71 POWER PLANT The overall power package inclusive of engine,

air intake, mount, cowling, scoops, cowl flaps.
-00 General
-10 Engine Those units and components of the Engine,

Turbine/Turbo Prop, or Ducted Fan/Unducted
Fan.
-20 Fuel and Control Those units and components and associated
mechanical systems or electrical circuits which
furnish or control fuel to the engine beyond the
main fuel quick disconnect; and thrust
augmenter, fuel flow rate sensing, transmitting
and/or indicating units whether the units are
before or beyond the quick disconnect.
-30 Ignition and Starting Those units and components which generate,
control, furnish, or distribute an electrical
current to ignite the fuel air mixture in the
cylinders of reciprocating engines or in the
combustion chambers or thrust augmenters of
turbine engines. Includes induction vibrators,
magnetos, switches, lead filters, distributors,
harnesses, plugs, ignition relays, exciters, and the
electrical portion of spark advance.
In addition, those units, components and
associated systems used for starting the engine.
Includes electrical, inertia air or other starter
systems.
-40 Air Those external units and components and

integral basic engine parts which go together to
conduct air to various portions of the engine and
to the extension shaft and torquemeter
assembly, if any. Includes compressor bleed
systems used to control flow of air through the
engine, cooling air systems and heated air
systems for engine anti-icing. Does not include
aircraft anti-icing, engine starting systems, nor
exhaust supplementary air systems.
-50 Engine Control That portion of the system which governs

operation of the engine. Includes
digital/electronic engine control systems like
FADEC and EEC. Includes units and components
which are interconnected for emergency
shutdown. For turbo-prop engines, includes
linkages and controls to the coordinator or
equivalent to the propeller governor, fuel control
unit or other units being controlled. For
reciprocating engines, includes controls for
blowers. Does not include units or components
which are specifically included in other chapters.
-60 Oil Those units and components external to the

engine concerned with storing and delivering
lubricating oil to and from the engine. Covers all
units and components from the lubricating oil
engine outlet to the inlet, including the inlet and
outlet fittings, tank, radiator, by-pass valve, etc.,
and auxiliary oil systems.
-70 Thrust Reverser Those units and components associated with

reverse thrust systems used to assist aircraft
stopping.
72 ENGINE TURBINE/TURBO Not applicable for Flight Crew Operations

PROP DUCTED Applications
FAN/UNDUCTED FAN
73 ENGINE FUEL AND Not applicable for Flight Crew Operations

CONTROL Applications
74 IGNITION Not applicable for Flight Crew Operations

Applications
75 AIR Not applicable for Flight Crew Operations

Applications
76 ENGINE CONTROLS Not applicable for Flight Crew Operations

Applications
77 ENGINE INDICATING Not applicable for Flight Crew Operations

Applications
78 EXHAUST Not applicable for Flight Crew Operations

Applications
79 OIL Not applicable for Flight Crew Operations

Applications
80 STARTING Not applicable for Flight Crew Operations

Applications
81 TURBINES Not applicable for Flight Crew Operations

Applications
82 WATER INJECTION Not applicable for Flight Crew Operations

Applications
83 ACCESSORY GEAR-BOXES Not applicable for Flight Crew Operations

Applications
84 PROPULSION Not applicable for Flight Crew Operations

AUGMENTATION Applications
85 *Unassigned
86 *Unassigned
87 *Unassigned
88 *Unassigned
89 *Unassigned
90 *Unassigned
91 CHARTS Not applicable for Flight Crew Operations

Applications
92 *Unassigned
93 *Unassigned
94 *Unassigned
99 *Unassigned
100 *Do not use
101 *Do not use
102 *Do not use
103 *Do not use
104 *Do not use
105 *Do not use
106 *Do not use
107 *Do not use
108 *Do not use
109 *Do not use
110 *Do not use
111 *Do not use
112 *Do not use
113 *Do not use
114 *Do not use
115 FLIGHT SIMULATOR Not applicable for Flight Crew Operations

SYSTEMS Applications
116 For FLIGHT SIMULATOR CUING Not applicable for Flight Crew Operations
subsystem/section SYSTEMS Applications
assignments and
descriptions, Ref.
IATA Simulator
Documentation
Requirements
5-3. Data Module Information Codes

5-3-1. Information Codes for content DMs
Note: The letters I and O are intentionally omitted.
Information Data Module

Code
01A Transmittal Letter DM
01B General Introduction DM
01C Local Introduction DM
01D MMEL Preamble DM
Code
01E CDL Preamble DM
01F Subset Header DM
01G Initial Approval DM
01H Revision Approval DM
01J Temporary Add-on Approval DM
01K Definition DM
03B Performance DM
03C Performance Application User Guide DM
03D Summary Performance DM
03E Performance How To DM
04A System DM
04B Subsystem DM
04C Component DM
04D Function DM
04E Mode DM
04F Complementary Description DM
04G System Architecture DM
04H Electrical Supply DM
04J Normal Operation DM
04K Non-Normal Operation DM
04L How-To Operation DM
04M Limitations DM
04N Operational Capabilities DM
09A Data Entry Format DM
11A Control DM
11B Indicator DM
11C Control Indicator DM
Code
11D Control Indicator Arrangement DM
11E Electronic Annunciation DM
11F Non-Electronic Annunciation DM
11G Panel and Display DM
12A CDL Item DM
12B Dispatch Item (LRU) DM
12C Dispatch Item (Message Oriented) DM
12D Dispatch Locator DM
12E System Fault and Dispatch Cross Reference DM
12F M Procedure DM
12G M Note DM
12H O Procedure DM
12J O Note DM
12K Substantiation DM
13A Normal Procedure DM
13B Supplementary Normal Procedure DM
13C Special Normal Operations Procedure DM
13D Task-Sharing Normal Procedure DM
13E Normal Procedure Description DM
13F Normal Checklist DM
14A Non-Normal Procedure DM
14B Non-Normal Non-ECAM/EICAS Procedure DM
14C Supplementary Non-Normal Procedure DM
14D Special Non-Normal Operations Procedure DM
14E Non-Normal Sensed Procedure DM
14F Non-Normal Not-Sensed Procedure DM
14G Non-Normal Procedure Description DM
Code
14H Failure Consequences DM
14J Summary Item DM
14K Synthesis Item DM
14L Maneuver Procedure DM
14M Flight Profile DM
14N Cabin Equipment Malfunction Decision Tree DM
14P Cabin Equipment Malfunction Procedure DM
16A Center of Gravity DM
16B Supplemental Content DM
16C Weight Report DM
16D Weighing Form DM
16E Equipment List DM
16F Control Surface Balance Record DM
022 Project Rules DM
90A Additional Parameters DM
5-3-2. Information Codes for Data Management DMs

Code
00P Product Cross-reference Table DM
00Q Conditions Cross-reference Table DM
00W Applicability Cross-reference Table DM
03A Avionics Qualifier Repository DM
0AA Glossary Repository DM
0AB Link Target Repository DM
0AC Dispatch Qualifier Repository DM
APPENDICES
Appendix 1. Unit of Measure Code

Units of Measure may be expressed in Flight Operations data in accordance with any of the
following systems:
• US - US Customary Units
• SI - International System of Units – (includes named units derived from SI base units)
• Other - Used to maintain backward compatibility for legacy data
The following table contains the accepted Spec 2300 Unit of Measure Codes:
Example Measurement System

Unit Categories Units
SubCategories US SI Other
acceleration
m/s2 Meter per second

squared
ft/s2 Feet per second squared
kt/s Knot per second
g Gravity Acceleration (G-

Load)
angle
rad Radian
deg Degree
% Percentage
angularVelocity
deg/s Degree per second
rad/s Radian per second
rpm Revolutions per minute
% Percentage
area
m2 Square meter
cm2 Square centimeter
mm2 Square millimeter
km2 Square kilometer
ft2 Square feet
in2 Square inch
yd2 Square yard
nm2 Square nautical mile
cost costPerUnit, Use ISO 4217 Currency

consumptionCost Codes
USD/USgal United States Dollar per

Gallon
density
kg/l Kilogram per liter
kg/m3 Kilogram per cubic

meter
g/cm3 Gram per cubic

centimeter
g/m3 Gram per cubic meter
mg/l Milligram per liter
lb/US Gal Pound per US gallon
lb/ft3 Pound per cubic feet
lb/in3 Pound per cubic inch
electricity charge,
current
Ah Ampere hour
KVA Kilo volt-ampere
V Volt
A Ampere
W Watt
VDC Direct Current Voltage
VAC Alternating Current

Voltage
kV Kilovolt
kW Kilowatt
MW Megawatt
energy
J Joule
MJ Megajoule
flow
kg/h Kilogram per hour
kg/min Kilogram per minute
t/h Metric Ton per hour
t/min Metric Ton per minute
ton/h US Ton per hour
ton/min US Ton per minute
l/min Litre per minute
lb/min Pound per minute
lb/h Pound per hour
gal/min Gallons/Minute
cc/h Cubic centimeters per

hour
oz/h Ounces per hour
qt/h Quarts per hour
force
N Newton
daN Decanewton
lb Pound force
oz Ounce force
kg Kilogram force
forceLength
N/m Newton per meter
kg/m Kilogram force per

meter
oz/m Ounce force per meter
lb/in Pound force per inch
lb/ft Pound-force per feet
forceVolume
MN/m3 Mega Newton per cubic

meter
frequency
Hz Hertz
kHz Kilohertz
MHz Megahertz
GHz Gigahertz
rpm Revolutions per minute
geographicLocation latitude,
longitude,
latitudeLongitude
deg Degrees
degmin Degrees Minutes
degminsec Degrees Minutes

Seconds
length depth,
width,
distance,
range,
circumference
m Meter
cm Centimeter
ft Feet
in Inch
km Kilometer
yd Yard
mi Mile
nm Nautical Mile
sm Statute Mile
mm Millimeter
%RC Referenced chord
nm/lb Nautical Mile per Pound
linearVelocity
m/s Meter per second
KIAS Knots Indicated Air

Speed
m/min Meter per minute
KTAS Knots True Airspeed
km/h Kilometer per hour
M Mach
kt Knot
mph Mile per hour
ft/s Feet per second
ft/min Feet per minute
KCAS Knots Calibrated
Airspeed
in/s Inches per Second
noise
dB Decibel
dBA A-Weighted Decibel
EPNdB Effective Perceived

Noise Decibel
percentage
% Percentage
pressure atmosphericPressure
hPa Hecto-pascal
inHg Inches of mercury
bar Bar
mbar Millibar
Pa Pascal
kPa Kilopascal
kg/m2 Kilogram force per

square meter
psi Pound force per square

inch
lb/ft2 Pound force per square

foot
psid pound-force per square-

inch differential
psia Pounds per square inch

absolute
kg/in2 Kilogram per Square

Inch
psig Pound per Square Inch
Gauge
temperature
degC Degree Celsius
degF Degree Fahrenheit
K Kelvin
time
h Hour
min Minute
s Second
ms Millisecond
day Day
mon Month
yr Year
torque moment
N.m Newton meter
daN.m Decanewton meter
N.mm Newton millimeter
kg.m Kilogram force meter
lb.in Pound force inch
lb.ft Pound force feet
oz.in Ounce force inch
oz.ft Ounce force feet
verticalDistance altitude,
height,
elevation,
dimension
m Meter
ft Feet
FL Flight Level
cm Centimeter
in Inches
volume capacity
l Liter
ml Millilitre
USgal US Gallon
qt Quart
UKgal Imperial Gallon
m3 Cubic meter
cm3 Cubic centimeter
mm3 Cubic millimeter
ft3 Cubic feet
in3 Cubic inch
yd3 Cubic yard
weight
ton US Ton
t Metric Ton
kg Kilogram
g Gram
mg Milligram
oz Ounce
lb Pound
klb Kilopound
Appendix 2. Backward Compatibility
The following table indicates changes in Revision 2017.1 that could result in backward
incompatibility to revision 2016.1. Backward incompatibility is defined as, "XML instances
that are valid in accordance with revision 2016.1 of ATA Spec 2300 may not validate to
revision 2017.1 schemas."
In some cases, the reason for the incompatibility described below is not a result of Schema
changes, but because the specification imposes new restrictions on the data which could result
in incompatibility with data generated under an earlier revision of Spec 2300 (e.g., use of the
standard Unit of Measure Codes specified in Appendix 1).
Note: Spec 2300 Revision 2017.1 is fully compatible with revision 2016.1.
Object
Type Reason Schema Context
Name
N/A N/A N/A N/A N/A
Appendix 3. References
ATA iSpec 2200 ATA Specification 2200. Information Standards for Aviation Maintenance.
ATA e-Business Program
(www.ataebiz.org)
IANA Media Media Types

Types Internet Assigned Numbers Authority
(http://www.iana.org/assignments/media-types/media-types.xhtml)
Model NATO Support Agency (NSPA)

Identification (http://www.nspa.nato.int/en/organization/logistics/LogServ/asds2000m.htm)
(MI) Codes
NCAGE/CAGE NATO Support Agency (NSPA)

Codes (https://eportal.nspa.nato.int/ac135public/)
S1000D International Specification for Technical Publications

Aerospace and Defence Industries Association of Europe (www.asd-
europe.org) (www.s1000d.org)
W3C XML World Wide Web Consortium (http://www.w3.org/XML/Schema)

Schema 1.0
W3C XML Path World Wide Web Consortium (http://www.w3.org/TR/xpath20/)

Language
(XPath) 2.0
W3C MathML World Wide Web Consortium

3.0 (http://www.w3.org/Math/)
Appendix 4. Data Dictionary
This appendix contains descriptions of terms and definitions used in this specification that have
been extracted from the ATA Common Support Data Dictionary (CSDD). For more
information, or to obtain the complete CSDD, please contact the ATA e-Business Program at
admin@ataebiz.org.
A4-1. Description of Information

1. Entry Info
1.1. Name
This is the airline industry label used in the specifications for concepts or objects represented
by the CSDD entry.
When two or more airline industry terms have identical names but different conceptual
meanings, there will be two entries with the same name. In that case, a "variant" number is
assigned, and appended to the name (in parentheses).
A given CSDD entry may also be known by several names; in that case, there will be one or
more additional names listed under the label, ALSO KNOWN AS. These may be
abbreviations, acronyms, or full names.
Naming conventions follow specific guidelines, but since they are collected from the ATA e-
Business Program Specifications, there are some differences.
1.2. Mod
This is the date the CSDD entry was last modified.
Note: The earliest date reflected in the CSDD is 10/2001 due to the restructuring of
the CSDD in 2001 where all entries were implicitly altered as a result of the
schema changes.
2. Definitions
This table includes the conceptual meaning of the term, as well as one or more optional
meanings in specific contexts. There are three columns: Class, Definition, and Source.
2.1. Class
Either Concept or Specific. A conceptual definition is one that provides the general meaning
of the CSDD Entry as it applies to the airline industry. A Specific definition is specification
and, sometimes, usage dependent.
2.2. Definition
An explanation of the concept, or the usage-specific definition.
2.3. Sources
This is the list of specifications to which the definition applies. The abbreviations are as
follows:
Specification Name Abbreviation

ATA Data Model ATA Online Data Model ODM
ATA Spec 42 Aviation Industry Standards for Digital 42

Information Security
ATA Spec 103 Standard for Jet Fuel Quality Control at 103
Airports
ATA Spec 106 Sources & Approved Parts Qualification 106

Guidelines
ATA Spec 109 No Fault Found Process 109
ATA Spec 300 Specification for Packaging of Airline 300

Supplies
ATA SPEC 2000 E-Business Specification for Materiels 2000

Management
ATA iSpec 2200 ATA Specification 2200. Information 2200

Standards for Aviation Maintenance.
ATA Spec 2300 Data Exchange Standards for Flight 2300

Operations
Airline Handbook Airline Handbook Airline Handbook
ATA MSG-3 Operator/Manufacturer Scheduled MSG3

Maintenance Development
WATOG World Airlines Technical Operations WATOG

Glossary
3. Application in Specifications
A CSDD entry is said to have an application in a specification when it is used to represent data
(e.g., in a DTD, a data model or schema, or a component of a message). Each application is
differentiated by a source-context-key tuple, which uniquely identifies the application (the
primary key).
For purposes of exposition below, the application of an entry is called the Entry Application.
3.1. Source
This field identifies the specification in which the CSDD Entry is implemented.
3.2. Context
Denotes the type of application in the specification. For example, the CSDD Entry could be
implemented in Markup Language (ML), such as a DTD for SGML or XML; or it could be
implemented using an XML Schema (XSD); or it may represent the semantics of a data
element which can be implemented in a message (MSG) or as a field in a data file (File) or
both (MSG & File).
The list of valid identifiers of contexts are defined in the table below:
Context Explanation
DM Data Model Class or Attribute.
Field A portion of a record of a file or a printed report.
File A field or component of a file-based data source, where a file is a set of related data (or
program) records that are similarly structured and are stored with a single name. (Many fields
make up one record; many records make up one file.)
ML Markup language Element or Attribute, as defined by markup languages such as DTDs for
SGML or XML.
MSG A field or component of a message based data source.
MSG & File A field or component of a both a message and file based data source.
Term A term applied in the specification which may differ from the underlying conceptual term
XSD An entry representing an application in an XML Schema
3.3. Key (e.g., Tag or Type)

Denotes the name (external key) for this entry as used in this context.
3.4. Type
Denotes the type of application of the concept for the CSDD entry. This is really a subdivision
of the context, where appropriate.
Valid Types are given below:
Type Explanation
Attribute An attribute or property of data, as used for an attribute of an element for SGML and
XML, or an attribute of a data element of a data model or schema.
Class A data object consisting of a set of attributes and relationships, as used in the
terminology of the Unified Modeling Language (UML) and the ATA Data Model
Type Explanation
Data Element A basic data object in general used to represent a data field in structures in data files
or messages, as well as in the specific terminology of a data model or schema.
Data Set Group A group of interdependent data elements identified by a single Text Element
Identifier Code.
Doctype A document type identifier, as used in the terminology of SGML and XML
Element A basic data object as used in the terminology of SGML and XML
Entity An entity, as more specifically defined by the SGML/XML context.
Notation A notation in the SGML or XML sense, i.e., that specifies the character or bitwise
coding scheme.
N/A A technical implementation for which there are no types defined
3.5. Properties
Denotes a number of data properties for the CSDD entry and begins with free-form remarks
describing the application. This is followed by several labeled properties, as described in the
following text.
3.5.1. Data Type
Denotes the data type for the CSDD entry.
3.5.1.1. Data Types for the Context: XSD
CSDD entries of the Context "XSD" use the Built-In XML datatypes as defined in the World
Wide Web Consortium (W3C) Recommendation XML Schema Part 2: Datatypes. In
accordance with accepted conventions, and for consistency with ATA XML Schemas, the
notations for these datatypes in the CSDD are prefixed with "xs:".
Examples:
xs:integer
xs:boolean
xs:string
3.5.2. Properties
The following table describes the properties which can be found listed in the Application table
of each entry.
Property Context Description
Case Sensitive Boolean (Yes/No) field indicates whether or not the data must be in
a specific case (e.g., upper, lower, mixed, etc.).
Chapter The Chapter of [ATA SPEC 2000] where this Entry Application can
be found.
Class The Unified Modeling Language (UML) Class to which an Entry

applies in the ATA Data Model
Cobol Picture Cobol picture or range specifying the format of the data.
Command Code This indicates specific command codes, which may be associated
with the Entry Application. For example, the command codes used
in [ATA SPEC 2000] messages.
Decimals The common practice decimal places for a numeric value.
Domain The sub-domain of the data: a range or set of values which further
restricts the data type
External Std This identifies one or more external standards which reference this
Entry Application.
Group Name This identifies an Entry Application, which represents a group,

whose identifier is typically the same as the CSDD Entry Name. For
applications which are groups, the "Type" of the Entry Application
(see above) will indicate the group type (e.g., "Data Set Group").
Groups Containing This This identifies an Entry Application as a member of one or more
Entry groups. The list of groups for which the entry is a member (per the
application) is provided, with links to the entry information for the
group.
Group Members This identifies the Entry Application as a group, containing the list
of members specified.
Group Type This identifies the type of group for the Entry Application.
Included in DTDs This lists the DTDs that are used by the Entry Application.
Note: If more than one Entry Application in an Entry uses the same
external reference identifier (e.g., element or attribute name), each
will list all the DTDs, even if the actual context is more limited.
Max Length Integer value of the minimum allowable length for the data.
Min Length Integer value of the minimum allowable length for the data.
Perm. Val. List This is the identifier for the list of permitted values. If there are
more than one permitted value sets, this will identify which table
applies to this Entry Application.
Property Context Description
Record Type Code This indicates specific record type codes from [ATA SPEC 2000]
which may be associated with the Entry Application.
Schema The schema which includes this Entry Application.
Structure Details Specification of the layout or format of the data.
4. Permitted Values
This table provides the set of allowable values for a CSDD entry. Following are the details
available in the Permitted Values table:
Value The actual code, number, text, or other value represented by the CSDD entry.
Description A narrative description of the Value.
Default Indicates if a permitted value should be used as the default value for a CSDD
entry.
A4-2. Spec 2300 Entries

The following pages contain the CSDD extract for entries used in Spec 2300.
Name Abbreviation Mod 2014
DEFINITIONS
Class Definition Source
Concept A shortened form of word or phrase 2300,
APPLICATION IN SPECIFICATIONS
Source Context Key (e.g., Type Properties
Tag or TEI)
2300 XSD abbreviation Element Data Type: xs:string
Usages:
Schema AdditionalParameters, Annunciation,
Approval, CabinEquipMalfunction,
CdlItem, DispatchItem, DispatchLocator,
DispatchProcedure, FrontMatter,
GlossaryRepository, Limitation,
LinkTargetRepository,
NonNormalProcedure,
NormalProcedure, Pm,
QualifierRepository, Substantiation,
SupplementalContent,
SystemDescription, SystemFault
Name Abnormal and Emergency Procedures Mod 2010
DEFINITIONS
Specific The top-level content element of the NonNormalProcedures schema which describes 2300,
abnormal, non-normal, and emergency procedures and checklists.
Specific Identifies the Flight Crew Operating Manual (FCOM) abnormal, non-normal, and 2200,
emergency procedures and checklists.
Tag or TEI)
2200 ML abnemer Element The structure of this element is currently not industry
standardized; i.e., the content is manufacturer defined.
Usages:
DTD fcom
2300 XSD nonNormalPr Element
ocedure
Usages:
Schema NonNormalProcedure
Name Acronym or Abbreviation Mod 2010
DEFINITIONS
Specific Specifies if a Spec 2300 glossary item is an acronym or abbreviation. 2300,
Tag or TEI)
2300 XSD acronymOrAb Attribute Data Type: xs:string
breviation
Permitted Value List: AcronymOrAbbreviation
Usages:
Schema GlossaryRepository
PERMITTED VALUES List Name: AcronymOrAbbreviation

Permitted Value Default Value Description
abbreviation Glossary item is an Abbreviation
acronym Glossary item is an Acronym
Name Action Mod 2015
DEFINITIONS
Concept A single act performed or commanded as part of one's duties. DM,
Specific Describes a command or challenge/response to be performed. 2300,
Specific The basic component of an action/result table (ART) or checklist. Each ACTION describes 2200,
an elementary action that the user of the document is to do. This action is followed by
the results (zero or more) that can be expected.
Tag or TEI)
2200 ML action Element
Usages:
DTD amm, cmm, frmfim
ODM DM Action Class Data Type: Character (20)
Attributes: Action Checklist, Action Memory Item,

Action Type
2300 XSD action Element
Usages:
Schema CabinEquipMalfunction, CdlItem,
DispatchProcedure,
FailureConsequences,
NonNormalProcedure,
NormalProcedure, SystemFault
2300 XSD challengeRes Element
ponse
Usages:
DispatchProcedure,
NonNormalProcedure,
2300 XSD command Element
Usages:
DispatchProcedure,
NonNormalProcedure,
2300 XSD simultaneous Element In a task sharing table, identifies an action completed
Actions by one or both crewmembers, or separate actions
completed by each crewmember at the same time.
Usages:
Schema FailureConsequences,
NonNormalProcedure, NormalProcedure
2300 XSD simultaneous Element A set of actions done by one or two crew members
Step
Usages:
2300 XSD timeActionFla Attribute Flag an action as a time action (e.g. "wait 30 seconds")
g
Data Type: xs:boolean
Usages:
Schema NonNormalProcedure, NormalProcedure
Name Action Block Mod 2010
DEFINITIONS
Specific In a dispatch assessment, describes complementary actions to be performed. 2300,
Specific Two or more linked sequential actions. 2300,
Tag or TEI)
2300 XSD actionBlock Element
Usages:
Schema CdlItem, DispatchProcedure,
NonNormalProcedure,
2300 XSD complementa Element
ryActions
Usages:
Schema SystemFault
Name Action Instruction Mod 2015
DEFINITIONS
Specific Used to provide instructions on how to perform an action (e.g. without delay) 2300,
Tag or TEI)
2300 XSD actionInstructi Element
on
Usages:
Schema DispatchProcedure,
Name Action Memory Item Mod 2010
DEFINITIONS
Concept Indicates that the action must be recalled from memory 2300, DM,
Tag or TEI)
ODM DM Action Attribute Data Type: Answers - Yes No
Memory Item
Permitted Value List: Answers - Yes No
Class Name: Action
2300 XSD memory Attribute Data Type: xs:boolean
Usages:
NonNormalProcedure
PERMITTED VALUES List Name: Answers - Yes No

No The character string 'No' indicating an negative answer to the question.
Yes The character string 'Yes' indicating an affirmative answer to the question.
Name Action Timing Indicator Mod 2011
DEFINITIONS
Specific Indicates that an action is only required to be performed on certain flights within a 2300,
flight day.
Tag or TEI)
2300 XSD timing Attribute
Permitted Value List: Action Timing Codes
Usages:
Schema NormalProcedure
PERMITTED VALUES List Name: Action Timing Codes

firstFlight First flight of the day
lastFlight Last flight of the day
transit Any flight that is not the first or last flight of the day
Name Additional Fault Information Mod 2015
DEFINITIONS
Concept Additional information provided about a system fault other than the fault description, 2300,
e.g., "System remains operative".
Tag or TEI)
2300 XSD additionalFau Element
ltInfo
Usages:
Schema SystemFault
Name Additional Parameters Mod 2014
DEFINITIONS
Specific The root element for the AdditionalParameters schema which provide additional values 2300,
for software parameters that are not found in any other DM content.
Tag or TEI)
2300 XSD additionalPar Element
ameters
Usages:
Schema AddtionalParameters
Name Affected System List Mod 2009
DEFINITIONS
Specific References to systems that are affected by a given system but are not in themselves 2300,
subordinate to the given system.
Tag or TEI)
2300 XSD affectedSyste Element
mList
Usages:
Schema SystemDescription
Name Affecting System List Mod 2009
DEFINITIONS
Specific References to systems that affect a given system but are not in themselves subordinate 2300,
to the given system.
Tag or TEI)
2300 XSD affectingSyst Element
emList
Usages:
Name Aircraft Applicability Change List Mod 2013
DEFINITIONS
Specific A list of aircraft identifiers that are added to or deleted from an applicability statement. 2300,
Tag or TEI)
2300 XSD aircraftAdd Element Data Type: xs:string
Usages:
Schema DmStatus
2300 XSD aircraftDel Element Data Type: xs:string
Usages:
Schema DmStatus
Name Aircraft Model Identifier Mod 2015
DEFINITIONS
Concept Uniquely identifies aircraft by model type. This code is assigned by the manufacturer 2000, 2300,
and registered with the airworthiness authorities.
Tag or TEI)
2000 XSD AMC Element Data Type: xs:string
Min Length: 1
Max Length: 20
Usages:
Chapter 11, 15
Schema AircraftEvent,
AircraftHoursAndLandings,
AircraftOutOfService,
AircraftStatusChange,
DeliveredAircraftTransferPartList,
Logbook, LRU_Removal,
QuantityPerAircraft,
ScheduledMaintenance, ServiceBulletin,
ShopFindings, SummaryData
2300 XSD modelIdentCo Attribute
de
Usages:
Schema Annunciation, ApplicCrossRefTable,
CondCrossRefTable, Container,
DataSetStatusList, DmStatus,
ExchangePackageStatusList, Pm,
ProductCrossRefTable,
SystemDescription
2300 XSD majorModelC Attribute Data Type: xs:string
ode
Usages:
Schema Approval, PmStatus
2300 XSD minorModelC Attribute Data Type: xs:string
ode
Usages:
2300 XSD modelIdent Element
Usages:
2300 XSD modelDesign Attribute Data Type: xs:string
ation
Usages:
2300 XSD modelMarket Attribute Data Type: xs:string
Designator
Permitted Value List: ModelMarketDesignatorList
Usages:
PERMITTED VALUES List Name: ModelMarketDesignatorList

business
cargo
civil
military
Name Aircraft Registration Number Mod 2014
ALSO KNOWN AS: Aircraft Fully Qualified Registration Number
DEFINITIONS
Concept The registration identity assigned to each individual aircraft by the cognizant national DM,
authority.
Concept The registration identity assigned to each individual aircraft by the cognizant national 2000, 2200, 2300,
authority. The registration number is unique to an operator, country, and time.
Tag or TEI)
2000 MSG ACN Data Element Data Type: AN
Min Length: 3
Max Length: 10
Cobol Picture: X(03) to X(05)
Decimals: 0
Usages:
Chapter 3, 5, 7
Command R1CPOXMT, R1CUSSHP, R1SPLSHP,
S1BOOKED
External UN/EDIFACT, X12
2000 XSD ACN Element Data Type: xs:string
Min Length: 3
Max Length: 10
Usages:
Chapter 3, 5, 7
Record Type 22, 26
Schema ATA_SparesOrder,
ATA_SparesOrderBookback
2200 ML acn Element
Usages:
DTD aipc, amm, frmfim, mpd, sds, srm, wm
ODM DM Aircraft Attribute Data Type: Character (5)
Registration
Number
Class Name: Registration
Name Aircraft Status Information Mod 2011
DEFINITIONS
Specific Used to provide status information that may or may not be displayed on an electronic 2300,
monitoring device.
Tag or TEI)
2300 XSD nonElectronic Element
StatusInfo
Usages:
2300 XSD statusInfo Element
Usages:
NonNormalProcedure
Name Alert Level Mod 2010
DEFINITIONS
Specific Indicates whether a failure affects a single system or equipment items, or causes the 2300,
loss of other systems, or equipment items.
Tag or TEI)
2300 XSD level Attribute Data Type: xs:string
Permitted Value List: AlertLevelList

Usages:
Schema FailureConsequences
PERMITTED VALUES List Name: AlertLevelList

independent A failure that affects an isolated system, or an equipment item, but does not degrade
the performance of other aircraft systems
primary A failure that affects a system, or an equipment item, and causes the loss of other
systems, or equipment items
Name Alternative Content Mod 2014
DEFINITIONS
Specific Content to display in the event that a multimedia object cannot be displayed. 2300,
Tag or TEI)
2300 XSD alternative Element
Usages:
CabinEquipMalfunction, CdlItem,
DispatchItem, DispatchLocator,
Limitation, NonNormalProcedure,
NormalProcedure, QualifierRepository,
Name Annunciation Mod 2013
ALSO KNOWN AS: Indication
DEFINITIONS
Concept System generated visual, audible or tactile notification of an aircraft condition. DM,
Specific Contains information about system generated visual, audible or tactile notification of an 2300,
aircraft condition.
Tag or TEI)
ODM DM Annunciation Class
Attributes: Annunciation Conveyance, Annunciation
Title, Annunciation Type
2300 XSD indications Element
Usages:
Schema Annunciation
2300 XSD message Element
Usages:
Schema Annunciation
2300 XSD subMessage Element
Usages:
Schema Annunciation
2300 XSD textualIndicati Element
on
Usages:
Schema Annunciation
Name Annunciation Conveyance Mod 2015
DEFINITIONS
Concept Identifies the means by which the annunciation is conveyed. e.g. Sensory Conveyance DM,
Specific Means by which an annunciation is expressed (e.g., light, message, aural, tactile). 2300,
Tag or TEI)
2300 XSD conveyance Attribute Data Type: xs:NMTOKEN
Permitted Value List: ConveyanceTypes

Usages:
Schema Annunciation
ODM DM Annunciation Attribute Data Type: Character (50)
Conveyance
Class Name: Annunciation

2300 XSD masterLight Element
Usages:
Schema Annunciation
2300 XSD auralWarning Element
Usages:
Schema Annunciation
2300 XSD localLight Element
Usages:
Schema Annunciation
2300 XSD otherDisplays Element One or more display units, other than masterlight,
auralwarning, locallights, and that provide information
linked to an alarm.
Usages:
Schema Annunciation
2300 XSD type Attribute Used to convey a sub-conveyance for aural warning
electronic annunciations.
Data Type: xs:string
Usages:
Schema Annunciation
2300 XSD localLights Element
Usages:
Schema Annunciation
2300 XSD auralWarning Element
s
Usages:
Schema Annunciation
PERMITTED VALUES List Name: ConveyanceTypes

aural
light
message
other
tactile
visual
Name Annunciation Priority Ranking Mod 2009
DEFINITIONS
Specific Describes additional information to clarify the priority level of an annunciation. 2300,
Tag or TEI)
2300 XSD priorityRankin Attribute Data Type: xs:string
g
Usages:
Schema Annunciation
Name Annunciation Type Mod 2009
DEFINITIONS
Concept Classification of the annunciation based on level of urgency e.g. Warning, Caution, DM,
advisory, Status, Change of mode etc.
Specific Describes the type of electronic message being conveyed. 2300,
Specific Classification of the annunciation based on level of urgency. 2300,
Name Annunciation Type Mod 2009
Tag or TEI)
2300 XSD priorityLevel Attribute Data Type: xs:NMTOKEN
Permitted Value List: AnnunciationTypes

Usages:
Schema Annunciation
ODM DM Annunciation Attribute Data Type: Character (20)
Type
Permitted Value List: AnnunciationTypes
Class Name: Annunciation
2300 XSD type Attribute Data Type: xs:string
Permitted Value List: Master Light Types

Usages:
Schema Annunciation
2300 XSD category Attribute
Permitted Value List: ElectronicAnnunciationCategori
es
Usages:
Schema Annunciation
PERMITTED VALUES List Name: AnnunciationTypes

advisory
caution
warning
PERMITTED VALUES List Name: ElectronicAnnunciationCategories

alert
communication
dispatch
memo
message
status
PERMITTED VALUES List Name: Master Light Types

caution
warning
Name Applicability Annotation Mod 2009
DEFINITIONS
Specific Applicability annotation of a data module 2300,
Tag or TEI)
2300 XSD applic Element
Usages:
Schema DmStatus
2300 XSD inlineApplic Element
Usages:
Schema DmStatus
Name Applicability Cross Reference Table Mod 2010
DEFINITIONS
Specific The top-level content element of the Applicability Cross-reference Table (ACT) data 2300,
module, used to declare product attributes.
Tag or TEI)
2300 XSD applicCrossR Element
efTable
Usages:
Schema ApplicCrossRefTable
Name Applicability Formula Mod 2013
DEFINITIONS
Specific Describes a conditional formula for determining applicability using logical operators. 2300,
Tag or TEI)
2300 XSD applicFormul Element
a
Usages:
Schema DmStatus
2300 XSD definitionMeth Attribute Identifies the method used to calculate the
od applicability formula.
Usages:
Schema DmStatus
Name Applicability Property Type Mod 2009
DEFINITIONS
Specific Indicates if the attribute applicPropertyIdent references a product attribute or a 2300,
condition
Tag or TEI)
2300 XSD applicPropert Attribute
yType Permitted Value List: ApplicabilityPropertyTypes
Usages:
Schema ProductCrossRefTable
PERMITTED VALUES List Name: ApplicabilityPropertyTypes

condition The applicPropertyIdent attribute refers to a condition
prodattr The applicPropertyIdent attribute refers to a product attribute
Name Applicability Property Value Mod 2009
DEFINITIONS
Specific Indicates the values and/or ranges in an applicability group. 2300,
Tag or TEI)
yValues
Usages:
Schema ApplicCrossRefTable, DmStatus,
ProductCrossRefTable
Name Application Structure Identification Mod 2009
DEFINITIONS
Specific Corresponds to the CGM APS parameter "apsid" and defines a relationship between the 2300,
hotspot and the graphical object in the illustration.
Tag or TEI)
2300 XSD applicationStr Attribute Definition and properties as per S1000D.
uctureIdent
Usages:
Schema Annunciation, SystemDescription
Name Application Structure Name Mod 2009
DEFINITIONS
Specific Corresponds to the CGM APS attribute "name" and defines an alternate relationship 2300,
between the hotspot and the graphical object in the illustration.
Tag or TEI)
2300 XSD applicationStr Attribute Definition and properties as per S1000D.
uctureName
Usages:
Name Approval Authority Mod 2011
DEFINITIONS
Specific The organization or agency responsible for approving data. 2300,
Tag or TEI)
2300 XSD authority Element
Usages:
Schema Approval, DmStatus, PmStatus
Name Approval Data Mod 2011
DEFINITIONS
Specific The set of data related to the approval status of a Data Module or Publication Module. 2300,
Specific The complete set of data conveying approval information. 2300,
Specific The top-level content element of the Approval schema which describes initial or 2300,
revision approval data.
Tag or TEI)
2300 XSD approval Element
Usages:
Schema Approval
2300 XSD approvalData Element
Usages:
Schema Approval, SubSetHeader
2300 XSD approvalInfo Element
Usages:
Schema DmStatus, PmStatus
Name Approval Date Mod 2011
DEFINITIONS
Specific The date of record upon which an authority indicates approval of a set of data. 2300,
Tag or TEI)
2300 XSD approvalDate Element Data Type: xs:dateTime
Usages:
Schema Approval, DmStatus, PmStatus
Name Approval Required Indicator Mod 2011
DEFINITIONS
Specific Identifies if all or part of a data Data Module contains approved data. 2300,
Tag or TEI)
2300 XSD approvalRequ Attribute Data Type: xs:string
ired
Permitted Value List: ApprovalRequiredIndicatorList
Usages:
PERMITTED VALUES List Name: ApprovalRequiredIndicatorList

no There is no approved data in the Data Module
partial Some of the data in the Data Module is approved
yes The entire Data module contains approved data
Name Approval Statement Mod 2011
DEFINITIONS
Specific Used if DM contains any approved data. It contains a statement like “EASA Approved” 2300,
or "A/R Related".
Tag or TEI)
2300 XSD approvalState Element
ment
Usages:
Name Approver Mod 2011
DEFINITIONS
Specific Used to describe the individual authorized to approve data. 2300,
Tag or TEI)
2300 XSD approvedBy Element
Usages:
Schema Approval
2300 XSD name Element
Usages:
Schema Approval
Name Approver Signature Mod 2011
DEFINITIONS
Specific An image or facsimile of the handwritten signature of the person approving data. 2300,
Tag or TEI)
2300 XSD signature Element
Usages:
Schema Approval
Name As Required by Regulations Mod 2010
DEFINITIONS
Specific Provided by a manufacturer to indicate a dispatch condition that is determined by local 2300,
regulatory requirements.
Tag or TEI)
2300 XSD asRequiredB Element
yRegulations
Usages:
Schema DispatchItem
Name Associated Procedures Mod 2010
DEFINITIONS
Specific In a given procedure, provides a reference to additional or alternative procedures to be 2300,
completed based on certain circumstances.
Tag or TEI)
2300 XSD associatedPr Element
ocedure
Usages:
NonNormalProcedure
2300 XSD associatedPr Element
ocedures
Usages:
NonNormalProcedure
Name Associated Subset Mod 2010
DEFINITIONS
Specific Contains references to other Subsets 2300,
Tag or TEI)
2300 XSD associatedSu Element
bSet
Usages:
Schema DmStatus
Name Auto Play Mod 2009
DEFINITIONS
Specific Defines whether or not a multimedia object is played on load (i.e., wait for user action). 2300,
Tag or TEI)
2300 XSD autoPlay Attribute Data Type: xs:Boolean
Usages:
Name Avionic Contexts Mod 2010
DEFINITIONS
Specific Used to denote that all or part of a Data Module is associated with data provided by an 2300,
Avionics system.
Tag or TEI)
2300 XSD avionicConte Element
xts
Usages:
Schema DmStatus
Name Background Color Mod 2012
DEFINITIONS
Specific Specifies the background color that should be displayed behind textual data. 2300,
Tag or TEI)
2300 XSD bgColor Attribute Use CSS Color Module Level 3 standard
Usages:
Schema Annunciation, Approval, CdlItem,
DispatchProcedure,
FailureConsequences, FrontMatter,
NormalProcedure, Performance,
Name Basic Engineering Number Mod 2016
DEFINITIONS
Specific A number assigned by the manufacturer to identify the basic configuration for the 2200, 2300,
aircraft design definition.
Tag or TEI)
2200 ML benbr Element
Usages:
Name Bold Mod 2009
DEFINITIONS
Specific Specifies whether or not textual data should be displayed in a boldface font. 2300,
Tag or TEI)
2300 XSD bold Attribute Data Type: xs:boolean
Usages:
Name Boolean Operator Code Mod 2013
DEFINITIONS
Concept A form of logic used to express the interaction between expressions. 2300, DM,
Tag or TEI)
ODM DM Boolean Attribute Data Type: Boolean
Operator
Code
Permitted Value List: LogicalOperatorCodes
Class Name: Effectivity Segment
Usages:
Schema CdlItem, DispatchItem,
DispatchProcedure,
ODM DM Boolean Attribute Data Type: Boolean
Operator
Code
Class Name: Operational Condition
2300 XSD logicalOperat Attribute
or Permitted Value List: LogicalOperatorCodes
Usages:
Schema CdlItem, DispatchItem,
DispatchProcedure,
NonNormalProcedure,
PERMITTED VALUES List Name: LogicalOperatorCodes

AND
NOT
OR
Name Cabin Equipment Malfunction Mod 2013
DEFINITIONS
Specific The root element of the CabinEquipMalfunction schema which provides a guideline to 2300,
isolate and eliminate equipment malfunctions in the cabin.
Tag or TEI)
2300 XSD cabinEquipM Element
alfunctino
Usages:
Schema CabinEquipMalfunction
Name Cabin Malfunction Elimination Procedure Mod 2013
DEFINITIONS
Specific A set of actions to be performed by the cabin crew to eliminate an equipment 2300,
malfunction in the cabin.
Tag or TEI)
2300 XSD elimProc Element
Usages:
2300 XSD malfunctionEl Element One or more action(s) to be performed in order to
iminate eliminate some failure causes or to solve the
malfunction.
Usages:
Name Cabin Malfunction Isolation Procedure Mod 2013
DEFINITIONS
Specific A question to be answered by the cabin crew to identify and isolate the source of an 2300,
equipment malfunction in the cabin.
Tag or TEI)
2300 XSD malfunctionIs Element
olate
Usages:
Name Cabin Malfunction Procedure Mod 2013
DEFINITIONS
Specific A set of steps performed by the cabin crew to isolate and eliminate an equipment 2300,
malfunction in the cabin.
Tag or TEI)
2300 XSD malfunctionPr Element
oc
Usages:
2300 XSD question Element
Usages:
2300 XSD yes Element
Usages:
2300 XSD no Element
Usages:
Name Cabin Malfunction Symptom Mod 2013
DEFINITIONS
Specific A Symptom of a malfunction observed by the cabin crew. 2300,
Tag or TEI)
2300 XSD symptom Element
Usages:
Name Callout Item Mod 2015
DEFINITIONS
Specific Describes an item called out on a control panel or flight deck display. 2300,
Tag or TEI)
2300 XSD calloutItem Element
Usages:
2300 XSD designator Element Callout item designator, as identified on the panel
graphical view.
Usages:
Name Callout List Mod 2012
DEFINITIONS
Specific A list of specific types of controls or indicators; such as switches, lights, bar, etc. on a 2300,
display panel.
Tag or TEI)
2300 XSD calloutList Element
Usages:
Name Case Mod 2009
DEFINITIONS
Specific Specifies whether or not textual data should be displayed in an uppercase or lowercase 2300,
font.
Tag or TEI)
2300 XSD case Attribute Data Type: xs:string
Permitted Value List: Text Cases

Usages:
PERMITTED VALUES List Name: Text Cases

lower Text is to be displayed in lower case
upper Text is to be displayed in upper case
Name Caution Mod 2014
DEFINITIONS
Specific Call attention to the use of materials, processes, methods, procedures, or limits, which 2200, 2300,
must be followed precisely to avoid damage to equipment.
Tag or TEI)
2200 ML caution Element Statement that expresses the need for heightened
awareness to conditions that can cause damage to
equipment.
Usages:
DTD amm, cmm, cpm, eipc, em, frmfim,
mpd, sb, sds, srm, teman, wm
2300 XSD caution Element
Usages:
Substantiation, SupplementalContent,
2300 XSD cautionProc Element Procedural content that may result in damage to
equipment if not followed
Usages:
Name CDL Item Mod 2010
DEFINITIONS
Specific The top-level content element of the cdlItem schema which describes permissable 2300,
deviations from standard aircraft configuration.
Tag or TEI)
2300 XSD cdlItem Element
Usages:
Schema CdlItem
Name Challenge Mod 2013
DEFINITIONS
Specific The first part of a two-part flight crew action that identifies a control to be checked or 2300,
manipulated.
Tag or TEI)
2300 XSD challenge Element Data Type: xs:string
Usages:
DispatchProcedure,
NonNormalProcedure,
Name Change Type Mod 2016
DEFINITIONS
Concept Identifies which document type or authority defines the source of a modification to the 2200,
configuration of an aircraft.
Specific Indicates the type of description for a change to technical documentation. 2200,
Specific Specifies the nature of a change to a Data Module or Publication Module. 2300,
Tag or TEI)
2200 ML chgtype Attribute The type of change identified in the element to which
this attribute belongs.
Permitted Value List: chgtype

Usages:
DTD aipc
2300 XSD changeType Attribute
Permitted Value List: ChangeTypes
Usages:
2200 ML chgdtype Attribute
Permitted Value List: ChangeDescriptionTypes
Usages:
DTD aipc, amm, cmm, cpm, eipc, em, frmfim,
mpd, msg3, sb, sds, srm, tem, wm
2200 ML chgtyp Element
Usages:
DTD cmm
PERMITTED VALUES List Name: ChangeDescriptionTypes

edit Editorial change - authored/technical content changed, but technically changes are
deemed insignificant.
effect Effectivity change - only the Effectivity has changed
sgml Markup change - changes are solely related to SGML markup
tech Technical change - authored/technical content has changed, changes are significant and
should be reviewed
PERMITTED VALUES List Name: ChangeTypes

add
changeComment
modify
move
moveAndModify
PERMITTED VALUES List Name: chgtype

as Alert Service Bulletin
cb Conversion Service Bulletin
coc Customer Originated Changes
mr Manufacturer Revision
rr Rapid Revision
sb Service Bulletin
sl Service Letter
Name Checklist Interruption Mod 2010
DEFINITIONS
Specific Indicates that crew may interrupt a Checklist and perform the rest of the check later. 2300,
Tag or TEI)
2300 XSD interruption Element
Usages:
Name Checklist Item Status Mod 2010
DEFINITIONS
Specific Indicates whether or not a checklist items has been completed. Those that are sensed 2300,
by the aircraft are automatically marked as completed, while others must be manually
completed by the crew.
Tag or TEI)
2300 XSD checkListItem Attribute An attribute of the Action element
Status
Permitted Value List: Checklist Item Status
Usages:
PERMITTED VALUES List Name: Checklist Item Status

detected Checklist item is sensed by the aircraft
nonDetected Checklist item is not sensed by the aircraft and must be selected by the crew
Name Checklist Navigation Item Mod 2010
DEFINITIONS
Specific Used to direct the crew to a step or other information within the same or different 2300,
procedure or checklist.
Tag or TEI)
2300 XSD navigationIte Element
m
Usages:
Name Checklist Objective Mod 2010
DEFINITIONS
Specific The expected outcome of accomplishment of a checklist or procedure. 2300,
Tag or TEI)
2300 XSD objective Element
Usages:
Name Comment Mod 2013
DEFINITIONS
Concept A general statement or observation forming supplementary information. 2200, 2300,
Specific A statement given by publisher for the benefit of the approver or end user 2300,
Specific A comment provided by the data approver. 2300,
Name Comment Mod 2013
Tag or TEI)
2200 ML comment Element A COMMENT is used in an Action Result List (ARLIST)
Action. It contains one elementary explanation of the
result of the corresponding ACTION and RESULT.
Usages:
DTD cmm
2200 Field Comment N/A Free form comments
Data Type: AN
Decimals: 0
2300 XSD comment Element

Usages:
Schema Approval, CabinEquipMalfunction,
CdlItem, DispatchProcedure,
NonNormalProcedure,
NormalProcedure, SubSetHeader,
SystemFault
2300 XSD direct Attribute Indicates if a comment should be published inline with
the corresponding text.
Usages:
DispatchProcedure,
2300 XSD approvalCom Element
ment
Usages:
Schema Approval
Name Company Department Mod 2011
DEFINITIONS
Specific The name of the data approver's department or division within a company. 2300,
Tag or TEI)
2300 XSD department Element
Usages:
Schema Approval
Name Condition Mod 2014
DEFINITIONS
Concept Describes the conditions under which information is applicable. 2300,
Specific A set of conditions that can initiate different navigation events within a procedure. 2300,
Specific For publication purposes, indicates if a condition and the resulting conditional content 2300,
should be published in a single paragraph.
Specific Describes the conditions under which different electrical supplies are used depending 2300,
on where equipment is installed.
Specific A set of conditions that can initiate different navigation events during a conditional 2200,
reference in intelligent graphics.
Tag or TEI)
2200 ML condition Attribute
Usages:
DTD igsheet
2300 XSD condition Element
Usages:
2300 XSD caseCond Element
Usages:
2300 XSD case Element
Usages:
2300 XSD caseCondBlo Element A group of dispatch conditions
ck
Usages:
Schema AdditionalParameters,
DispatchProcedure,
NonNormalProcedure,
NormalProcedure, SupplementalContent
2300 XSD exclusiveCon Element
ditions
Usages:
Schema CdlItem, DispatchProcedure
2300 XSD ifCondition Element
Usages:
2300 XSD whatIf Element

Usages:
2300 XSD infoCondition Element
Usages:
NonNormalProcedure
2300 XSD inopCondition Element
Usages:
NonNormalProcedure
2300 XSD commonCond Element Values of parameters that apply to one or more
ition Performance tables.
Usages:
Schema Performance
2300 XSD exclusiveCas Element
es
Usages:
Name Condition Applicability Flag Mod 2010
DEFINITIONS
Specific Indicates if a condition is applicable at any time during the course of a procedure. 2300,
Tag or TEI)
2300 XSD atAnyTime Attribute Data Type: xs:boolean
Usages:
Name Condition Cross Reference Table Mod 2010
DEFINITIONS
Specific The top-level content element for the Conditions Cross-reference Table (CCT) data 2300,
module, which is used to declare any condition that can affect applicability of data.
Tag or TEI)
2300 XSD condCrossRe Element
fTable
Usages:
Schema CondCrossRefTable
Name Condition Incorporation Mod 2009
DEFINITIONS
Specific Represents a technical condition that has or is planned to be incorporated into the 2300,
technical data.
Tag or TEI)
2300 XSD condIncorpor Element
ation
Usages:
2300 XSD incorporation Element
Usages:
Name Condition Issue Number Mod 2013
DEFINITIONS
Specific An identifier to indicate a release or issue of an airplane configuration modification, e.g. 2300,
service bulletin.
Tag or TEI)
2300 XSD condIssueNu Attribute Data Type: xs:string
mber
Usages:
Name Conditional Location Mod 2013
DEFINITIONS
Specific The location of one or more resources or sub-group of resources that are not in the 2300,
default location.
Tag or TEI)
2300 XSD conditionalLo Element Data Type: xs:string
cation
Usages:
Schema PackageOrganization
Name Conditional Location Criteria Mod 2013
DEFINITIONS
Specific The criteria for why a resource is in a location other than the default location. 2300,
Tag or TEI)
2300 XSD conditionalLo Element
cationCriteria
Usages:
Name Consequence Mod 2011
DEFINITIONS
Specific Describes how the operation of the airplane is affected by the next most critical failure 2300,
of an associated or interrelated system to the first failure after dispatch.
Specific Describes how the operation of the airplane is affected by a failure; the consequence of 2300,
flying in the MEL configuration.
Specific The operational impact of an inoperative system. 2300,
Tag or TEI)
2300 XSD consequence Element
Usages:
NonNormalProcedure
OfFailure
Usages:
Schema Substantiation
OfNextCritical
Failure Usages:
Name Container Mod 2010
DEFINITIONS
Specific The top-level content element for the Container data module. 2300,
Tag or TEI)
2300 XSD container Element
Usages:
Schema Container
Name Crew Action Confirmation Flag Mod 2010
DEFINITIONS
Specific Indicates whether an action to be performed must be confirmed by both crew 2300,
members.
Tag or TEI)
2300 XSD confirm Attribute An attribute of the challengeResponse element
Usages:
NonNormalProcedure
Name Crew Awareness Information Mod 2015
DEFINITIONS
Specific Identifies a crew awareness procedure. 2300,
Specific Provides the crew additional information about aircraft status for planning the rest of a 2300,
flight following a system failure.
Tag or TEI)
2300 XSD additionalInfo Element
rmation
Usages:
NonNormalProcedure
2300 XSD crewAwarene Attribute Data Type: xs:boolean
ss
Usages:
Name Crew Qualification Mod 2010
DEFINITIONS
Specific Identifies any special qualifications that are required for a flight crew member to 2300,
complete a procedure.
Tag or TEI)
2300 XSD crewQualifica Attribute
tion
Usages:
Name Crew Resource Management Mod 2016
DEFINITIONS
Specific Identifies which crew member(s) are responsible for commanding, responding, or taking 2300,
an action.
Tag or TEI)
2300 XSD crm Attribute An attribute of the Action element
Usages:
Schema CabinEquipMalfunction,
2300 XSD both Attribute
Usages:
2300 XSD challenger Attribute Crew member responsible for verbalizing the action.
Usages:
2300 XSD responder Attribute Crew member responsible for responding to the action.
Usages:
Name Customer Code Mod 2010
DEFINITIONS
Concept The ICAO alphanumeric code identifying the customer airline receiving or transmitting 2000, 2200,
data.
Specific The ICAO alphanumeric code identifying the customer receiving data. 2300,
Tag or TEI)
2200 ML cus Element In the Effectivity Cross Reference list it is only used
when the manual is produced for a consortium of
operators who may use the same fleet numbers for
different aircraft in the (consortiums) fleet.
Usages:
DTD aipc, amm, frmfim, mpd, sb, sbi, sds,
srm, wm
2200 ML cus Attribute The ICAO customer code.
Usages:
DTD aipc, amm, cpm, eipc, em, frmfim, lap,
lea, msg3, sds, srm, teman, wm
2200 Field Customer N/A Data Type: AN
Code
Min Length: 3
Max Length: 3
Decimals: 0
2000 MSG CUS Data Element Refer to Customer Identification Code (CIC) for other
applications in Procurement Planning, Order
Administration, and Repair Administration.
Data Type: AN
Min Length: 3
Max Length: 5
Cobol Picture: X(03) to X(05)
Decimals: 0
Usages:
Chapter 12, 3, 4, 6, 7
Command A1CNTACT, A1QUOTES, A1SEARCH,
A1STOCKS, P1ADVISE, PURCHASE,
R1ADVISE, R1CNTACT, R1CUSSHP,
R1DSPACK, R1DSPXMT, R1EXCACK,
R1EXCXMT, R1INVACK, R1INVXMT,
R1MATRCP, R1SPLSHP, R1TDNXMT,
S1BOOKBK, S1CMDACK, S1CNTACT,
S1INVEXC, S1NVOICE, S1ORDEXC,
S1SHIPPD
2000 File CUS Data Element Refer to Customer Identification Code (CIC) for other
Procurement Planning, Order Administration, and
Repair Administration applications.
Refer to Inquirer Identification Code (IIC) for
P1PDINQY, R1CDBINQ, and R1CDBRSP Command Code
applications.
Refer to Owner Code (ONR) for other Surplus
Procedure applications.
For provisioning applications, a three character code,
agreed upon between trading partners, must be used.
The tape recipient code for an airline receiving a
procurement data tape is the three character
Customer Code.
Non-airline companies which do not qualify for
ATA/IATA Codes but wish to function as customers for
Procurement Planning should use their Supplier Code
(POS 01-05).
Data Type: AN
Min Length: 3
Max Length: 3
Cobol Picture: X(03)
Pos. 01-02 IATA Airline Designator X(02)

Pos. 03 Office Code X(01)
Pos. 04-05 Internal Routing Code X(02)
(As agreed between trading partners)
Usages:
Chapter 1, 5
Record Type 01, 11, 21, 23, 26, 28
2300 XSD receiverCode Attribute Data Type: xs:string
Usages:
Schema ExchangePackageStatusList, PmStatus
Name Customer Effectivity Code Mod 2016
DEFINITIONS
Specific A three to four character code selected by the airline to identify the aircraft in the 2200, 2300,
customized document.
Tag or TEI)
2200 ML cec Element
Usages:
Name Customer Identification Mod 2015
DEFINITIONS
Specific Contains information to identify the data receiver. 2300,
Tag or TEI)
2300 XSD receiverIdent Element
Usages:
Schema DataSetStatusList,
ExchangePackageStatusList, PmStatus
Name Customer Name Mod 2010
DEFINITIONS
Concept Legal identifier of an operator, manufacturer, or supplier. 2200,
Specific The name of the customer receiving data. 2300,
Tag or TEI)
2200 ML cusname Attribute
Usages:
DTD aipc, amm, cpm, eipc, em, faammel,
frmfim, lap, lea, msg3, sds, srm, teman,
wm
2200 ML custname Element
Usages:
DTD sb
2200 Field Customer Data Element Data Type: AN
Name
Max Length: 40
Decimals: 0
2300 XSD receiverName Attribute Data Type: xs:string
Usages:
Schema ExchangePackageStatusList, PmStatus
Name Customer Originated Change Mod 2016
ALSO KNOWN AS: COC
DEFINITIONS
Concept Customer requested data to be added or removed from the operator's manual. 2200, 2300,
Customer specific data is supplied to the manufacturer for incorporation.
Tag or TEI)
2200 ML cocend Element The Customer Originated End tag marks the end of
customer revised data started by the tag COCST.
Usages:
DTD aipc, amm, eipc, em, fcom, frmfim, sds,
wm
2200 ML cocst Element Customer Originated Change Start Tag identifies that
all data following the tag, until the tag COCEND is
reached, is information provided by the customer for
whom the data is effective. Note: The REVST - REVEND
tags must be used in conjunction with the COCST -
COCEND tags to indicate changes in the COC data.
Usages:
DTD aipc, amm, eipc, em, fcom, frmfim, sds,
wm
Name Data Format Mod 2010
DEFINITIONS
Concept Specifies the format of data. 2300,
Tag or TEI)
2300 XSD productRefDa Attribute Data Type: xs:string
taFormat
Usages:
Schema Annunciation, CdlItem, DispatchItem,
DispatchLocator, DispatchProcedure,
FrontMatter, QualifierRepository,
Name Data Group Mod 2015
DEFINITIONS
Specific Identifier to categorize the type of content in an exchange package. 2300,
Tag or TEI)
2300 XSD dataGroup Attribute Data Type: xs:string
Permitted Value List: dataGroupList

Usages:
2300 XSD customDataG Attribute Provides the data group name for custom resources
roup
Usages:
2300 XSD objectType Attribute Data Type: xs:string
Permitted Value List: ObjectTypes

Usages:
ExchangePackageStatus List
PERMITTED VALUES List Name: dataGroupList

custom
dmContent
dmStatus
graphic
multimedia
pmContent
pmStatus
xmlSchema
PERMITTED VALUES List Name: ObjectTypes

graphic
multimedia
Name Data Group Location Mod 2013
DEFINITIONS
Specific Used to identify the location of a data group. 2300,
Tag or TEI)
2300 XSD dataGroupLo Element A wrapper element to associate a data group with its
cation location.
Usages:
2300 XSD defaultLocatio Element The main location for a data group.
n
Usages:
2300 XSD location Element The URL for a folder/collection where data of the
group are located. The location can be relative to the
base URI of the package or absolute.
Data Type: xs:anyURI
Usages:
Name Data Module Mod 2015
DEFINITIONS
Specific The root element of a Data Module schema. 2300,
Tag or TEI)
2300 XSD dmodule Element
Usages:
CdlItem, CondCrossRefTable, Container,
ProductCrossRefTable, ProjectRules,
QualifierRepository, SystemDescription,
SystemFault
Name Data Module Content Mod 2015
DEFINITIONS
Specific Contains the substantive information pertinent to a data module. 2300,
Tag or TEI)
2300 XSD content Element
Usages:
ApplicCrossRefTable,
QualifierRepository,
Name Data Module Entry Code Mod 2011
DEFINITIONS
Specific A code used in a Publication Module for organization of data modules for publication. 2300,
Tag or TEI)
2300 XSD dmEntryCode Attribute Data Type: xs:string
Usages:
Schema Pm
Name Data Module Identification Mod 2015
DEFINITIONS
Concept A unique identifier for a Spec 2300 data module or publication module. 2300,
Tag or TEI)
2300 XSD dmIdent Element
Usages:
DispatchProcedure, DmStatus,
NonNormalProcedure,
NormalProcedure, ProjectRules,
ProjectRules, QualifierRepository,
2300 XSD dmCode Element Data Type: xs:string
Attributes and structure of dmCode are defined in ATA

Spec 2300.
Usages:
ApplicCrossRefTable, Approval,
CondCrossRefTable, DispatchItem,
DmStatus, FrontMatter,
2300 XSD dmRefIdent Element
Usages:
Schema ExchangePackageStatusList
2300 XSD impactedDm Element
Usages:
Schema DmStatus
2300 XSD pmCode Element
Usages:
Schema Pm, PmStatus
2300 XSD pmIdent Element
Usages:
Schema Pm, PmStatus
2300 XSD pmRefIdent Element
Usages:
Schema Pm
Name Data Module Reference Group Mod 2010
DEFINITIONS
Specific A group of references to Data Modules intended to be published together, e.g., Non 2300,
Normal Procedures.
Tag or TEI)
2300 XSD dmRefGroup Element
Usages:
Schema Pm
Name Data Module Status Mod 2015
DEFINITIONS
Specific The top-level content element of the dmStatus data module. 2300,
Specific Describes the revision status of a data module. 2300,
Tag or TEI)
2300 XSD dmStatusEntr Attribute
yCode Permitted Value List: DM Entry Types
Usages:
ExchangePackageStatusList
2300 XSD dmStatus Element
Usages:
Schema DmStatus
2300 XSD issueType Attribute
Permitted Value List: DM Issue Types
Usages:
Schema DmStatus
PERMITTED VALUES List Name: DM Entry Types

a Applicabilty only has changed
c Changed
d Deleted
m Metadata only has changed
n New
u Unchanged
PERMITTED VALUES List Name: DM Issue Types

applicChanged
changed
metadataChanged
new
unchanged
Name Data Set Status Information Mod 2015
DEFINITIONS
Concept Used to provide a list of data set content with related issue information. 2300,
Tag or TEI)
2300 XSD dssl Element The top level element of the DataSetStatusList schema.
Usages:
Schema DataSetStatusList
2300 XSD dsslCode Element Used to identify content associated with a Data Set
Status List.
Usages:
2300 XSD dsslContent Element A list of data module and publication module entries,
with related dmEntryType or pmEntryType and
issueInfo, plus list of objects (graphic, multimedia).
Usages:
2300 XSD dsslIdent Element The identifier of the Data Set Status List.
Usages:
Name Data Source Mod 2015
ALSO KNOWN AS: Originating Company Name
DEFINITIONS
Specific Name or code to identify the data originator or source of a change to the data. 2300,
Specific Name of the company supplying the data 2200,
Tag or TEI)
2200 Field Data Source Data Type: AN
Max Length: 76
Decimals: 0
Permitted Value List: DataProducerList
2300 XSD senderIdent Attribute Data Type: xs:string
Usages:
2300 XSD productRefO Attribute Data Type: xs:string
wner
Usages:
2300 XSD dataProducer Attribute
Permitted Value List: DataProducerList
Usages:
Schema DmStatus
2300 XSD dataSupplier Element
Usages:
Schema Approval
2300 XSD changeProdu Attribute Data Type: xs:string
cer
Usages:
PERMITTED VALUES List Name: DataProducerList

OEM
Operator
Name Date Stamp Date Mod 2010
DEFINITIONS
Specific The date associated with a Reason for Update for revision of a Data Module or 2300,
Publication Module.
Specific Identifies the date on which a digital signature is applied to an electronic part 2000,
certification form.
Specific Identifies the date of listing or update in the AIRS Surplus file. This date is transmitted 2000,
on the output Master File and output update Master File.
Tag or TEI)
2000 File DAT Data Element Data Type: N
Min Length: 5
Max Length: 5
Decimals: 0
99 99 9 Day Month Year
2000 XSD DAT Element Data Type: xs:date
Date Format: YYYY-MM-DD
Usages:
Chapter 16
Schema ATA_PartCertificationForm
2300 XSD date Attribute Data Type: xs:dateTime
Usages:
Name Deferred Procedures Mod 2010
DEFINITIONS
Specific Procedure steps to be considered later during a flight. 2300,
Tag or TEI)
2300 XSD deferredProc Element
edures
Usages:
NonNormalProcedure
2300 XSD flightPhaseDe Element
ferredProc
Usages:
NonNormalProcedures
Name Definition Mod 2010
DEFINITIONS
Concept Provides the meaning of a term, symbol, or abbreviation within the context of one or 2200, 2300,
more usages.
Tag or TEI)
2200 ML def Element
Usages:
DTD aipc, amm, cmm, eipc, faammel, fcom,
frmfim, mpd, sds, srm, wm
2300 XSD definition Element
Usages:
Name Delete Mod 2010
DEFINITIONS
Concept Remove an item from a specific application. For technical data "Delete" indicates the WATOG,
removal of a paragraph, phrase, page,
Specific Identifies an element that has been deleted. 2300,
Tag or TEI)
2300 XSD del Element
Usages:
Name Delimiter Mod 2009
DEFINITIONS
Specific A character used as separator between the Left Part and the Right Part of a Paired Item 2300,
element.
Specific A special character for (1) designating the end of a Text Element Identifier (TEI) and (2) 2000,
separating individual fields within a multiple field TEI (Data Set Group).
Tag or TEI)
2000 MSG & File Delimiter Data Element 1) Space - Designates the end of each individual field
(excluding the last) in a field grouping within a Data Set
Group.
2) Slash - The slash (/) designates the end of a field
that contains a TEI and the value for a data element (or
end of Data Set Group).
Data Type: AN
Min Length: 1
Max Length: 1
Decimals: 0
2300 XSD sepChar Element

Usages:
Name Delimiter Position Mod 2009
DEFINITIONS
Specific The position of the separator character for bi-column text. Defined as a percent of 2300,
global width.
Tag or TEI)
2300 XSD width Attribute Data Type: xs:decimal
Usages:
Name Delivery Scope Mod 2013
DEFINITIONS
Specific Provides the scope of the delivery; Complete , Revised Only, or Partial. 2300,
Tag or TEI)
2300 XSD deliveryScop Attribute Data Type: xs:string
e
Permitted Value List: Delivery Scope List
Usages:
PERMITTED VALUES List Name: Delivery Scope List

complete The exchange package contains all resources
partial The complete XML is delivered; but only revised external objects (i.e.
graphics/multimedia) are delivered
revisedOnly Only revised resources are delivered
Name Description Mod 2010
ALSO KNOWN AS: Detailed Description
DEFINITIONS
Concept A brief textual characterization of the Fault Symptom DM,
Specific Provides information about a Data Module. 2300,
Specific A definition or exposition of attributes, features or details. 2200,
Tag or TEI)
2200 ML desc Element The content of this element describes the parent
element.
Usages:
DTD msg3, srm
2200 ML descdet Element Detailed description of an Element.
Usages:
DTD msg3
ODM DM Description Attribute Data Type: Character (200)
Class Name: Fault Symptom

2300 XSD description Element
Usages:
Schema CdlItem, DispatchItem, FrontMatter,
QualifierRepository, SystemDescription,
SystemFault
Name Description Sub Level Mod 2010
DEFINITIONS
Specific Used to group descriptive information in a hierarchical structure. 2300,
Tag or TEI)
2300 XSD subLevel Element
Usages:
Schema DispatchProcedure, FrontMatter,
NonNormalProcedure,
NormalProcedure, SystemDescription
Name Dispatch Assessment Mod 2010
DEFINITIONS
Specific In an electronic crew alerting system, associates an aircraft status with a corresponding 2300,
dispatch condition.
Tag or TEI)
2300 XSD assessment Element
Usages:
Schema SystemFault
2300 XSD dispatchAsse Element
ssment
Usages:
Schema SystemFault
Name Dispatch Condition Option Mod 2010
DEFINITIONS
Specific Used to indicate alternative scenarios affecting the dispatch condition for a given item. 2300,
Tag or TEI)
2300 XSD option Attribute Data Type: xs:string
Usages:
Schema CdlItem, DispatchItem
Name Dispatch Conditions Mod 2013
DEFINITIONS
Specific Describes the criteria in which the dispatchability is restricted or limited depending on 2300,
the equipment and/or regulatory requirements.
Specific The dispatch conditions include the category, number installed, number required for 2200,
dispatch, and remarks for each item, subitem1, subitem2, subitem3.
Tag or TEI)
2200 ML dispcond Element
Usages:
DTD faammel
2300 XSD dispatchCond Element
ition
Usages:
2300 XSD normalDispat Element
chCondition
Usages:
2300 XSD dispCondCod Attribute A code that identifies a dispatch condition for
e applications such as performance computation.
Usages:
Name Dispatch Item Mod 2011
DEFINITIONS
Specific The top-level content element of the dispatchItem schema which describes permissible 2300,
deviations from standard aircraft configuration.
Tag or TEI)
2300 XSD dispatchItem Element
Usages:
Schema DispatchItem
Name Dispatch Item Extension Code Mod 2010
DEFINITIONS
Specific Optional extension to the SNS number for dispatch items. 2300,
Tag or TEI)
2300 XSD dispatchItem Attribute Data Type: xs:string
ExtensionCod
e
Usages:
Schema DispatchItem
Name Dispatch Locator Mod 2010
DEFINITIONS
Specific The top-level content element of the dispatchLocator data module, which provides 2300,
graphical references to the locations of dispatch or CDL items.
Tag or TEI)
2300 XSD dispatchLocat Element
or
Usages:
Schema DispatchLocator
Name Dispatch Qualifier Value Mod 2011
DEFINITIONS
Specific A specific value provided in the case that a local qualifier is referenced. 2300,
Tag or TEI)
2300 XSD value Element
Usages:
Schema DmStatus
Name Dispatch Qualifiers Mod 2010
DEFINITIONS
Specific Used to denote categories or properties associated with a dispatch condition or proviso. 2300,
Tag or TEI)
2300 XSD dispatchQuali Element
fiers
Usages:
Schema DmStatus
Name Display Name Mod 2010
DEFINITIONS
Specific Human-readable text or symbol to identify a specific dispatch qualifier. 2300,
Specific Name of the display where an electronic message appears. 2300,
Tag or TEI)
2300 XSD display Attribute Data Type: xs:string
Usages:
Schema Annunciation, FailureConsequences,
NonNormalProcedure
2300 XSD displayName Element
Usages:
Schema QualifierRepository
Name Display Object Height Mod 2009
DEFINITIONS
Specific Indicates the presentation height of a graphical object. 2300,
Specific Defines the display height of a multimedia object at run time, if not full screen 2300,
Tag or TEI)
2300 XSD multimediaOb Attribute Data Type: xs:string
jectHeight
Usages:
2300 XSD reproduction Attribute Data Type: xs:string
Height
Usages:
Name Display Object Scale Mod 2009
DEFINITIONS
Specific Indicates the percentage or ratio of the original size of a graphical object for 2300,
presentation.
Tag or TEI)
2300 XSD reproductionS Attribute Data Type: xs:string
cale
Usages:
Name Display Object Width Mod 2009
DEFINITIONS
Specific Indicates the presentation width of a graphical object. 2300,
Specific Defines the display width of a multimedia object at run time, if not full screen. 2300,
Tag or TEI)
2300 XSD multimediaOb Attribute Data Type: xs:string
jectWidth
Usages:
2300 XSD reproduction Attribute Data Type: xs:string
Width
Usages:
Name Do Not Accomplish Mod 2010
DEFINITIONS
Specific A list of checklists that should not be accomplished based on a non-normal airplane 2300,
configuration.
Tag or TEI)
2300 XSD doNotAccom Element
plish
Usages:
NonNormalProcedure
Name Document Incorporation Mod 2009
DEFINITIONS
Specific Used to list the data modules and publications that are affected by a technical 2300,
condition.
Tag or TEI)
2300 XSD documentInc Element
orporation
Usages:
Name Document Number Mod 2012
ALSO KNOWN AS: Document Identification Number
DEFINITIONS
Concept Document identification code given by the manufacturer to a document. 2000, 2200, 2300,
Specific A unique alphanumeric identifier based on the model identification code and the 2300,
issuing authority.
Name Document Number Mod 2012
Tag or TEI)
2200 ML docnbr Attribute In an instance top level element, it represents the
identification code of the current document.
Within an external reference, it represents the
identification code of the document being referenced.
Usages:
igsheet, lap, lea, mpd, msg3, sb, sbi, sds,
srm, teman, v4sheet, wm
2000 XSD DIN Element Data Type: xs:string
Min Length: 1
Max Length: 32
Usages:
Chapter 11, 14, 15, 16
Schema ATA_PartCertificationForm,
ATA_WarrantyClaim,
ScheduledMaintenance
2300 XSD pmNumber Attribute Data Type: xs:string
Usages:
Schema Pm, PmStatus
2300 XSD productNumb Attribute Data Type: xs:string
er
Usages:
Schema PmStatus
2000 XSD DocumentNu Element Use if the document can't be parsed according to
mber elements within the Document Type group.
Max Length: 100
Usages:
Chapter 17
Schema ATA_DSE_Logbook
Name Electronic Annunciation Mod 2016
DEFINITIONS
Specific Specifies information about electronic messages generated by an onboard computing 2300,
system (e.g., EICAS, ECAM, FMS, etc.)
Tag or TEI)
2300 XSD electronicMes Element
sage
Usages:
DataSetStatusList, DispatchItem,
DmStatus, ExchangePackageStatusList,
NonNormalProcedure,
NormalProcedure, Performance, Pm,
PmStatus, QualifierRepository,
SubSetHeader, Substantiation,
2300 XSD memoConditi Element An electronic message displayed only under certain
on conditions
Usages:
NonNormalProcedure
2300 XSD memoPage Element
Usages:
NonNormalProcedure
2300 XSD memosGroup Element
Usages:
NonNormalProcedure
2300 XSD displayStatus Attribute

Permitted Value List: Display Status Types
Usages:
NonNormalProcedure,
2300 XSD dynamicBeha Element Provides a dynamic display of a message (blinking or
vior steady)
Permitted Value List: Dynamic Display Types

Usages:
NonNormalProcedure,
2300 XSD electronicMes Element A grouping of electronic messages.

sageBlock
Usages:
NonNormalProcedure,
PERMITTED VALUES List Name: Display Status Types

acknowledged
off
triggered
PERMITTED VALUES List Name: Dynamic Display Types

blinking
steady
Name Electronic Message Not Applicable Mod 2011
DEFINITIONS
Specific An electronic crew alerting system message that has no reference to a dispatch item 2300,
Tag or TEI)
2300 XSD notApplicable Element
Usages:
Schema SystemFault
Name Emphasis Mod 2014
DEFINITIONS
Specific Indicates if a procedure should be displayed with a larger font size or other means to 2300,
improve readability.
Specific Describes specific display formats for textual data. 2300,
Tag or TEI)
2300 XSD emphasis Element
Usages:
Schema AddtionalParameters, Annunciation,
DispatchProcedure,
NonNormalProcedure,
2300 XSD enhancedRea Attribute
dability Date Format: xs:boolean
Usages:
Name Employee Title Mod 2011
DEFINITIONS
Specific Specifies the job title of the person responsible for an activity, e.g. signing a document 2000, 2300,
Tag or TEI)
2000 XSD EPT Element Data Type: xs:string
Min Length: 1
Max Length: 50
Usages:
Chapter 11
Schema AircraftStatusChange, ServiceBulletin
2300 XSD jobTitle Element
Usages:
Schema Approval, SubSetHeader
Name End of Procedure Mod 2013
DEFINITIONS
Specific Used to indicate when an entire procedure or procedure branch is completed. 2300,
Tag or TEI)
2300 XSD endOfProc Element
Usages:
DispatchProcedure
Name Enumeration Mod 2011
DEFINITIONS
Specific Used to identify allowable values for a dispatch qualifier. 2300,
Tag or TEI)
2300 XSD enumeration Element
Usages:
Name Equation Mod 2014
DEFINITIONS
Specific Identifies a statement of mathematical or logical expressions 2200, 2300,
Tag or TEI)
2200 ML equ Element This tag identifies an equation.
Usages:
DTD amm, cmm, cpm, em, frmfim, mpd,
msg3, sb, sds, teman
2300 XSD equation Element Imported from mathML namespace
Usages:
Limitation, LinkTargetRepository,
Name Equipment Data Mod 2010
DEFINITIONS
Specific A specific occurrence of a subsystem or component. 2300,
Specific Data associated to a piece of equipment in a list of equipment. 2200,
Tag or TEI)
2200 ML equdata Element
Usages:
DTD amm
2300 XSD dispatchEqui Element
pment
Usages:
Name Example Data Mod 2013
DEFINITIONS
Specific A block of sample data of data provided for clarification 2300,
Tag or TEI)
2300 XSD example Element
Usages:
Schema Annunciation, Approval,
DispatchProcedure,
Limitations, NonNormalProcedure,
Name Exchange Package Status List Mod 2010
DEFINITIONS
Specific The root element of the ExchangePackageStatusList data module. 2300,
Tag or TEI)
2300 XSD dml Element
Usages:
Name Exchange Package Status List Information Mod 2015
DEFINITIONS
Specific Provides a list of data module and publication module entries, including deleted 2300,
data/publication modules and data/publication modules included in the current
delivery, with the related dmEntryType or pmEntryType.
Tag or TEI)
2300 XSD linkText Element
Usages:
Schema Annunciation, Pm, SystemDescription
2300 XSD dmStatusEntr Element
y
Usages:
2300 XSD dmlContent Element
Usages:
2300 XSD dmlIdent Element
Usages:
2300 XSD dmlCode Element
Usages:
2300 XSD pmStatusEntr Element
y
Usages:
Name Exchange Package Status List Location Mod 2013
DEFINITIONS
Specific The location of the exchange package status list XML fragment. This can be an absolute 2300,
address or relative to the base URI.
Tag or TEI)
2300 XSD exchangePac Element Data Type: xs:anyURI
kageStatusLi
stLocation
Usages:
Name External Application Mod 2013
DEFINITIONS
Specific Used to launch an external application from within a data module. 2300,
Tag or TEI)
2300 XSD extApplication Element
Usages:
Schema Annunciation, CabinEquipMalfunction,
Substantiation, SystemDescription,
SystemFault
Name External Object Mod 2015
DEFINITIONS
Concept Identifies external graphics and multimedia objects that are part of the data set. 2300,
Specific An external object (graphic, multimedia) that is deleted in the current exchange 2300,
package.
Tag or TEI)
2300 XSD deletedObject Element
Usages:
2300 XSD object Element
Usages:
Name Failure Consequences Mod 2010
DEFINITIONS
Specific The top-level content element of the FailureConsequences schema which describes the 2300,
consequences of a failure to a non-normal procedure.
Tag or TEI)
2300 XSD failureConseq Element
uences
Usages:
Schema FailureConsequences
Name Fault Mod 2010
DEFINITIONS
Concept An identifiable condition in which one element of a redundant system has failed (no 2200, MSG-3,
longer available) without impact on the required function output of the system
Maintenance Significant Item (MSI). At the system level, a fault is not considered a
functional failure.
Specific An identifiable condition in which one element of a system has failed (no longer 2300,
available).
Tag or TEI)
2300 XSD faultItem Element
Usages:
Schema SystemFault
Name Fault Code Mod 2014
DEFINITIONS
Concept A computer generated alphanumeric code which uniquely identifies an aircraft system DM,
fault which can be cross referenced in the aircraft FRM and FIM.
Specific Specifies a computer generated alphanumeric code which uniquely identifies an aircraft 2000, 2200, 2300,
system fault which can be cross referenced in the aircraft FRM and FIM.
Tag or TEI)
2200 ML faltcode Element
Usages:
DTD frmfim
2000 XSD FLT Element Data Type: xs:string
Min Length: 1
Max Length: 20
Usages:
Chapter 11
Schema AircraftEvent, AircraftOutOfService,
Logbook, LRU_Removal
2000 XSD FaultCode Element Data Type: xs:string
Max Length: 20
Usages:
Chapter 17
ODM DM Fault Code Attribute Data Type: Character (20)
Class Name: Maintenance Message

2300 XSD impactedFaul Attribute Data Type: xs:NMTokens
tCodes
Usages:
Schema CdlItem, SystemFault
Name Fault Detection Conveyance Mod 2010
DEFINITIONS
Specific Identifies the manner of conveyance of a fault to the crew (e.g., EICAS/ECAM alert, crew 2300,
observation, etc.)
Tag or TEI)
2300 XSD faultDetection Attribute Data Type: xs:string
Usages:
Schema SystemFault
Name Figure Mod 2014
DEFINITIONS
Concept A grouping of elements that provide detailed information about a graphical object. 2300,
Specific A container for the Parts Data in the Illustrated Parts List. It consists of Graphics and 2200,
Text.
Tag or TEI)
2200 ML figure Element
Usages:
DTD aipc, cmm, eipc, srm
2300 XSD figure Element
Usages:
DispatchProcedure,
Name Full Screen Mod 2009
DEFINITIONS
Specific Used to specify whether or not a multimedia will be viewed/played in full screen mode. 2300,
Tag or TEI)
2300 XSD fullScreen Attribute Data Type: xs:Boolean
Usages:
Name Function Mod 2013
DEFINITIONS
Concept Function describes the role a manufacturer part will perform when fitted in functional DM,
positions on an assembly.
Concept The normal characteristic actions of an item. MSG-3,
Specific Identifies a specific mode or purpose for a given system or component. 2300,
Tag or TEI)
ODM DM Function Class
Attributes: Function Description Text, Function
Identifier, Manufacturer Code
2300 XSD function Element
Usages:
NonNormalProcedure
Name Glossary Data Mod 2010
DEFINITIONS
Specific The body of the glossary comprised of a term and its definition. 2200, 2300,
Tag or TEI)
2200 ML glosdata Element
Usages:
DTD aipc, amm, eipc, fcom, frmfim, mpd, sds,
srm, wm
2300 XSD glossaryItem Element
Usages:
Name Glossary Repository Mod 2010
DEFINITIONS
Specific The top-level content element of the glossaryRepository schema which is a collection of 2300,
acronyms and abbreviations and their definitions.
Tag or TEI)
2300 XSD glossaryRepo Element
sitory
Usages:
Name Graphic Mod 2014
ALSO KNOWN AS: Drawing

Illustration
DEFINITIONS
Concept A collection of Graphical Objects. DM,
Concept A collection of Illustrations. 2200,
Specific A collection of information about graphical objects. 2300,
Tag or TEI)
2200 ML graphic Element Graphic - A place holder for a set of graphic images
(normally in the form of Sheet elements).
Usages:
mpd, msg3, sb, sds, srm, teman, wm
2200 ML cptype Attribute The type of Consummable Product represented in the
Graphic.
Usages:
DTD cpm
ODM DM Graphic Class
Attributes: Graphic Number, Graphic Type, Graphic
Type Description
2300 XSD graphic Element
Usages:
Limitation, QualifierRepository,
Name Graphic and Multimedia Type Mod 2016
DEFINITIONS
Specific Describes the category of a graphic or multimedia object (e.g., figure, audio, video, etc.) 2300,
Tag or TEI)
2300 XSD mimeType Attribute
Usages:
FrontMatter, Limitation,
NonNormalProcedure,
Substantiation, SystemDescription,
SystemFault
Name Graphical Object Anchor Mode Mod 2009
DEFINITIONS
Specific Describes how a graphical object behaves 2300,
Tag or TEI)
2300 XSD anchorMode Attribute Data Type: xs:string
Permitted Value List: Anchor Modes

Usages:
PERMITTED VALUES List Name: Anchor Modes

inline the graphic is fully displayed in the content of the data module on the consultation
application.
linkText text is displayed as an active zone with a link to the graphic
thumbnail an icon is displayed in the content of the data module with a link to the graphic.
unanchored the figure contains more than one graphic that are not anchored in the text flow of the
data module. The first graphic is displayed, and contains hotspots that enable display of
another graphic instead of the first one, in order to create a sequence (with steps) of
graphics.
Name Graphical Object Coordinates Mod 2009
DEFINITIONS
Specific Used to provide the coordinates of the overlay region of a graphical object, as a closed 2300,
polygon, separated by commas in the form “x1, y1.....xn, yn” where each (x,y) pair
defines a vertex point of the closed region in absolute pixel coordinates.
Tag or TEI)
2300 XSD objectCoordin Attribute Definition and properties as per S1000D.
ates
Usages:
Name Graphical Object Descriptive Text Mod 2009
DEFINITIONS
Concept Text conveying information about a graphical object. This text would be in addition to DM,
any text included as part of the graphical object.
Concept Information about graphical objects including text and references. 2300,
Tag or TEI)
ODM DM Graphical Attribute
Object Class Name: Graphical Object
Descriptive
Text
2300 XSD objectDescr Attribute Properties as per S1000D.
Usages:
Name Graphical Object Display Mode Mod 2016
DEFINITIONS
Specific Describes how a graphical object is presented. 2300,
Tag or TEI)
2300 XSD displayMode Attribute Data Type: xs:string
Permitted Value List: Display Modes

Usages:
2300 XSD displayInstruc Element Provides display instructions for a target display
tions device/format
Usages:
CabinEquipmentMalfunction, CdlItem,
DispatchProcedure,
2300 XSD rotation Attribute Data Type: xs:string
Permitted Value List: RotationList

Usages:
2300 XSD spread Attribute Data Type: xs:boolean
Usages:
2300 XSD zoomMode Attribute Data Type: xs:Integer
Usages:
2300 XSD gColor Attribute Indicates if the graphic must be rendered in color.
Usages:
CabinEquipmentMalfunction, CdlItem,
DispatchProcedure,
PERMITTED VALUES List Name: Display Modes

frameHorizontal the screen is cut horizontally with the graphic on the top and the text on the bottom
frameVertical the screen is cut vertically with the graphic on the right and the text on the left
inlineCenter center alignment
inlineLeft left alignment
inlineRight right alignment
PERMITTED VALUES List Name: RotationList

antiClockwise
clockwise
Name Graphical Object Visibility Mod 2009
DEFINITIONS
Specific Used to identify graphical regions that should not be displayed for the current use of a 2300,
graphic. Otherwise the value is assumed to be "visible"
Tag or TEI)
2300 XSD visibility Attribute Definition and properties as per S1000D.
Permitted Value List: Object Visibility Types

Usages:
PERMITTED VALUES List Name: Object Visibility Types

hidden
visible Yes
Name Hotlink Mod 2014
ALSO KNOWN AS: Hotspot
DEFINITIONS
Concept Contains the definition of graphical regions in an illustration and contains information 2300,
needed to navigate between graphical objects or between graphical objects and text.
Specific Only for use by retrieval engines, is not to be used in interchange SGML document 2200,
instances. During data prep by a retrieval software vendor, the cross links between
references in a document instance must be coded for that particular software and set of
documents. This element allows a target (where the reference is to) and source (where
the reference is from) to be encoded in whatever format is necessary for that software.
Because it is an inclusion at the manual level, it can be used to code all implicit as well
as explicit references. Its exact use and positioning is entirely dependent on the
retrieval engine's requirements and so is not defined in this document.
Tag or TEI)
2200 ML hotlink Element
Usages:
DTD aipc, amm, cmm, cpm, eipc, em,
faammel, fcom, frmfim, mpd, msg3, sb,
sds, teman, wm
2300 XSD hotspot Element
Usages:
Name Hotspot Type Mod 2009
DEFINITIONS
Specific Used to classify a graphical object (e.g., callout, detail, etc.) 2300,
Tag or TEI)
2300 XSD hotspotType Attribute Definition and properties as per S1000D.
Usages:
Name Identification Extension Mod 2015
DEFINITIONS
Specific Gives the additional parameters needed to establish a unique identification of a Spec 2300,
2300 object in those cases when the existing identification attributes are insufficient to
form a universally unique identity.
Tag or TEI)
2300 XSD identExtensio Element Gives the additional parameters needed to establish a
n unique identification of a data module in those cases
when data module code, issue information together
with the language and country are insufficient to form
a universally unique identity.
Usages:
ExchangePackageStatusList,
FrontMatter, GlossaryRepository,
2300 XSD extensionCod Attribute Data Type: xs:string
e
Usages:
SystemDescription
Name Identification Number Mod 2015
DEFINITIONS
Specific An alphanumeric string to uniquely and persistently identify an element 2300,
Specific The identifier of either a product attribute (element productAttribute attribute id from 2300,
the ACT data module) or condition (element cond attribute id from the CCT data
module.
Specific An alphanumeric string to uniquely identify text, multimedia or graphical data. 2200, 2300,
Tag or TEI)
2200 ML id Attribute Unique number to allow direct SGML cross-referencing
to be performed from the REFID attribute.
Usages:
igsheet, mpd, msg3, sb, sds, srm, teman,
v4sheet, wm
2300 XSD parameterIde Attribute Data Type: xs:string
nt
Usages:
yIdent
Usages:
2300 XSD id Attribute Data Type: xs:id
Usages:
2300 XSD subSetIdent Attribute A unique identifier for a subset.
Usages:
Schema DmStatus
2300 XSD projectId Attribute The identifier of a project representing a unique set of
rules, whether it applies to a specific aircraft,
publication or whatever is defined by the data
producer.
Data Type: xs:id
Usages:
Schema PackageOrganization, ProjectRules
Name Incorporation Date Mod 2009
DEFINITIONS
Specific The date on which a technical condition is incorporated. 2300,
Specific The date on which a Service Bulletin was completely embodied on all applicable aircraft 2200,
or engines.
Tag or TEI)
2200 ML icdate Element
Usages:
DTD aipc, amm, wm
2300 XSD day Attribute
Usages:
2300 XSD month Attribute
Usages:
2300 XSD year Attribute
Usages:
Name Incorporation Status Mod 2009
DEFINITIONS
Specific Describes the status of incorporation of technical conditions. 2300,
Specific Identifies the status (incorporation date or a text string - normally "INCORP" or "No 2200,
effect") of Service Bulletins or Customer Originated Modifications submitted for
incorporation in the document instance. This status appears in the Service Bulletins and
Modification List.
Tag or TEI)
2200 ML ics Element
Usages:
DTD aipc, amm, cmm, eipc, em, frmfim, sds,
srm, wm
2300 XSD incorporation Attribute
Status Permitted Value List: Incorporation Status
Usages:
2300 XSD incorporation Element
Status
Usages:
PERMITTED VALUES List Name: Incorporation Status

incorporated a technical condition which is completely incorporated into the data module or
publication content
inprogress a technical condition which is partially incorporated into the data module or publication
content
noeffect a technical condition which has no impact on the data module or publication content
Name Indicator Mod 2011
DEFINITIONS
Concept A device that conveys information about a system's state. 2300,
Tag or TEI)
2300 XSD otherDisplay Element
Usages:
Schema Annunciation
Name Inform Mod 2013
DEFINITIONS
Specific Descriptive information provided inside of procedural content. 2300,
Tag or TEI)
2300 XSD inform Element
Usages:
DispatchProcedure
2300 XSD electronicInfo Element
rm
Usages:
NonNormalProcedure
Name Information Object Identifier Mod 2015
ALSO KNOWN AS: Multimedia Object Identifier

Graphical Object Identifier
Graphical Object ID
DEFINITIONS
Concept A code that uniquely identifies a Graphical Object. 2200,
Specific A unique identifier for a set of information about one or more graphical or multimedia 2300,
objects (i.e., Information Control Number [ICN]).
Tag or TEI)
2300 XSD infoIdent Attribute Data Type: xs:string
Usages:
Schema Annunciation, DataSetStatusList,
SystemDescription
Name Inhibiting/Enabling Logic Mod 2011
DEFINITIONS
Concept Conditions under which an annunciation will be inhibited or enabled. 2300,
Tag or TEI)
2300 XSD inhibitConditi Element
ons
Usages:
Schema Annunciation
2300 XSD inhibitConditi Element
on
Usages:
Schema Annunciation
2300 XSD code Attribute Code identifying an avionic phase of flight
Usages:
Schema Annunciation
Name Inoperative Item Mod 2015
DEFINITIONS
Specific A system that no longer functions as designed due to completion of a procedure or 2300,
failure of another system.
Specific A system, component, or function that no longer functions as designed due to 2300,
completion of a procedure or failure of another system, component, or function.
Tag or TEI)
2300 XSD inoperativeIte Element
ms
Usages:
NonNormalProcedures
2300 XSD flightPhaseIn Element
opSys
Usages:
NonNormalProcedures
2300 XSD inopItem Element
Usages:
NonNormalProcedures
2300 XSD inoperativeSy Element
stems
Usages:
NonNormalProcedure
2300 XSD notAvailFunct Element
ions
Usages:
NonNormalProcedure
2300 XSD criticalImpact Attribute Used to set the critical impact level (caution or
advisory) of the included inoperative items.
Permitted Value List: Critical Impact Levels

Usages:
NonNormalProcedure
PERMITTED VALUES List Name: Critical Impact Levels

advisory
caution
Name Interactive Targets Mod 2015
DEFINITIONS
Specific Specifies display devices, electronic consultation tools or applications, where a 2300,
procedure is interactive (tickable).
Tag or TEI)
2300 XSD interactiveTar Attribute Data Type: xs:NMToken
gets
Usages:
2300 XSD targetName Attribute Data Type: xs:string
Usages:
Name Internal Reference Target Type Mod 2015
DEFINITIONS
Specific Describes the type of information/object to which a reference points. Used to 2300,
autogenerate a caption.
Tag or TEI)
2300 XSD internalRefTa Attribute Definition and properties as per S1000D.
rgetType
Permitted Value List: InternalRefTargetList

Usages:
PERMITTED VALUES List Name: InternalRefTargetList

figure
graphic
hotspot
multimedia
multimediaObject
other
paragraph
table
Name Introduction Mod 2016
ALSO KNOWN AS: Front Matter

Introduction Text
DEFINITIONS
Specific Identifies introductory information about an exchange package, publication, dataset or 2300,
a major data structure.
Specific The top-level content element of the frontMatter schema which describes introductory 2300,
information about the complete document or a major document structure.
Specific Identifies introductory information about the complete document or a major document 2200, 2300,
structure.
Name Introduction Mod 2016
Tag or TEI)
2200 ML intro Element
Usages:
DTD aipc, amm, cpm, eipc, em, fcom, mpd,
msg3, sbi, sds, srm, teman, wm
2200 ML fimintro Element
Usages:
DTD frmfim
2200 ML frmintro Element
Usages:
DTD frmfim
2300 XSD frontMatter Element
Usages:
Schema FrontMatter
2300 XSD intro Element
Usages:
Schema CdlItem, DispatchItem, SystemFault
2300 XSD dmlIntro Element
Usages:
2300 XSD elementIntrod Element Used in the Front Matter to introduce the presentation
uction of data elements that may be presented elsewhere in
the publication.
Usages:
Schema FrontMatter
Name Invalid Configuration Mod 2014
DEFINITIONS
Specific Used to indicate that a table cell is empty by design because the combination of row 2300,
and column values is not valid.
Tag or TEI)
2300 XSD invalidConfig Element
Usages:
DispatchProcedure,
Name Issue Date Mod 2015
DEFINITIONS
Specific The issue date of a data module or subset. 2300,
Specific Day, month, year of the issue date associated with a document, temporary revision or a 2200,
Service Bulletin. Must be given in ANSI standard format of 'YYYYMMDD'
Name Issue Date Mod 2015
Tag or TEI)
2200 ML issdate Attribute
Usages:
DTD aipc, amm, cmm, eipc, em, frmfim, mpd,
sds, srm, wm
2200 ML issdate Element
Usages:
DTD cmm, eipc, em, sbi
2300 XSD dmContentIss Element
ueInfo
Usages:
Schema DataSetStatusList, DmStatus
2300 XSD issueDate Attribute Data Type: xs:dateTime
Usages:
GlossaryRepository,
NonNormalProcedure,
NormalProcedure, Pm, PmStatus,
QualifierRepository, SubSetHeader,
2300 XSD prevIssueDat Attribute Data Type: xs:dateTime
e
Usages:
2300 XSD date Element
Usages:
Schema SubSetHeader
Name Issue Information Mod 2015
DEFINITIONS
Specific Contains information about a data module or publication module issue. 2300,
Tag or TEI)
2300 XSD issueInfo Element
Usages:
NonNormalProcedure,
NormalProcedure, Pm, PmStatus,
2300 XSD PmContentIs Element
sueInfo
Usages:
Schema DataSetStatusList, PmStatus
2300 XSD productIssueI Element
nfo
Usages:
Schema SubSetHeader
2300 XSD dmStatusIssu Element
eInfo
Usages:
2300 XSD inWork Attribute
Usages:
DmStatus, FailureConsequences,
NonNormalProcedure,
2300 XSD PmStatusIssu Element
eInfo
Usages:
Name Italic Mod 2009
DEFINITIONS
Specific Specifies whether or not textual data should be displayed in an italic font. 2300,
Tag or TEI)
2300 XSD italic Attribute Data Type: xs:boolean
Usages:
Name Language Mod 2015
DEFINITIONS
Specific Identifies the language in which the data is being transmitted. 2300,
Specific Language in which the data is being transmitted. The format for language coding is as 2200,
defined in ISO 639. Some examples are: "EN" English, "FR" French, "DE" German, "IT"
Italian, "NL" Dutch, and "JA" Japanese. Values CDATA.
Tag or TEI)
2200 ML lang Attribute
Usages:
faammel, frmfim, lap, lea, mpd, msg3,
sb, sbi, sds, srm, teman, wm
2300 XSD language Element
Usages:
Name Layer Mod 2014
DEFINITIONS
Specific Describes the level of detail provided in a Flight Operations XML file based on the 2300,
importance of the data to the flight crew.
Tag or TEI)
2300 XSD layer Attribute Data Type: xs:string
Permitted Value List: Layers

Usages:
Schema Annunciation, Approval,
PERMITTED VALUES List Name: Layers

1 Provides “need to know” information. Typically this is the minimum amount of
information necessary for the flight crew in operations and basically corresponds to
information they need to know for their initial. Computer Based Training (CBT) contains
almost the same level of information.
2 Provides “nice to know” information. This can be used as reference for the flight crew to
fully understand the logic of the aircraft-pilot interface.
3 Provides “detailed information.” This is not likely to be used in flight, but provides more
expertise, rationale and explanation with clarification and amplification material that can
be used at an airline’s discretion.
Name Left Column Mod 2014
DEFINITIONS
Specific In bi-column text, the information in the left column of a paired item. 2300,
Tag or TEI)
2300 XSD leftPart Element
Usages:
Name Limitation Mod 2011
DEFINITIONS
Concept Limitation is a restriction or threshold which defines the boundary of the aircraft 2300, DM,
operation.
Specific Describes restrictions on aircraft operation due to missing or inoperative equipment. 2300,
Tag or TEI)
ODM DM Limitation Class
Attributes: Limit Title, Limit Type
2300 XSD cdlLimit Element
Usages:
Schema CdlItem
2300 XSD limit Element
Usages:
FailureConsequences, Limitation,
NonNormalProcedures
2300 XSD systemRestri Element
ctions
Usages:
NonNormalProcedures
2300 XSD flightPhaseRe Element
strictions
Usages:
NonNormalProcedures
2300 XSD limitCondition Element limits depending on a condition
Usages:
NonNormalProcedure
2300 XSD systemRestri Element
ctionsGroup
Usages:
NonNormalProcedure
Name Link Behavior Mod 2009
DEFINITIONS
Specific Describes the manner in which an application will respond when a hyperlink is selected 2300,
by a user or otherwise encountered by the application.
Tag or TEI)
2300 XSD behavior Element
Permitted Value List: Link Show Types
Usages:
2300 XSD linkShow Attribute Data Type: xs:string
Permitted Value List: Link Show Types

Usages:
2300 XSD linkActuate Attribute Data Type: xs:string
Permitted Value List: Link Actuate Types

Usages:
PERMITTED VALUES List Name: Link Actuate Types

onLoad Will cause the referenced data to be automatically displayed with no action by the user
onRequest Requires user to indicate that they want to view the referenced data
PERMITTED VALUES List Name: Link Show Types

embedInContent Displays the linked data inline at the point where the data module reference occurs
newPane Will open in another window for the referenced data
replaceAndNoReturn Replaces the current screen of data with the referenced data
replaceAndReturnToSourc Replaces the current screen of data with the referenced data, and then returns tue user
e to the origin.
Name Link Summary Mod 2011
DEFINITIONS
Specific Provides information about the source Data Module and target Data Module of a link. 2300,
Tag or TEI)
2300 XSD linkSummary Element
Usages:
Schema LinkTargetRepository
Name Link Target Location Mod 2011
DEFINITIONS
Specific A textual description of the location of a link target within a Publication Module. 2300,
Tag or TEI)
2300 XSD linkTargetLoc Element Data Type: xs:string
ation
Usages:
Name Link Target Repository Mod 2011
DEFINITIONS
Specific The top-level content element of the LinkTargetRepository schema which provides 2300,
complementary information for links to data modules that are not delivered as part of
the exchange package in the current deliverable.
Tag or TEI)
2300 XSD linkTargetRep Element
ository
Usages:
Name Link Text Mod 2009
DEFINITIONS
Specific The display text to which a hyperlink is applied. 2300,
Name List Association Type Mod 2015
DEFINITIONS
Specific Used to indicate if a list is inclusive or exclusive. 2300,
Tag or TEI)
2300 XSD associationTy Attribute
pe
Usages:
Name List Item Mod 2015
DEFINITIONS
Concept A name, word or other item written, printed or transmitted as part of a list. DM,
Concept A name, word or other item written, printed or transmitted as part of a list. 2300,
Specific A set of elements that describe the names, words or other items transmitted as part of 2300,
a list.
Tag or TEI)
2300 XSD listItem Element
Usages:
Limitation, Performance,
ODM DM List Item Class
Name List Style Mod 2015
DEFINITIONS
Concept Describes the format for the type of bullet used in random lists, and the type of 2300,
numbers used in sequential lists.
Tag or TEI)
2300 XSD listStyle Attribute
Usages:
Schema CdlItem, DispatchItem, DispatchLocator,
Name List Title Mod 2014
DEFINITIONS
Specific A description of the purpose of a list. Normally only used to differentiate between 2200, 2300,
consecutive repetitions of a list structure unseparated by a higher level list item.
Tag or TEI)
2200 ML ltitle Element
Usages:
DTD amm, cmm, frmfim, sds
2300 XSD listTitle Element Data Type: xs:string
Usages:
Name Location Mod 2010
DEFINITIONS
Concept Identifies a position or area of an aircraft. 2300, DM,
Specific Description of the area where the job is to be performed. 2200,
Specific The physical position of a part in the airplane described by Station, Water and Buttock 2200,
lines, or by Zone.
Tag or TEI)
2200 ML location Element
Usages:
DTD srm, wm
ODM DM Location Class
Name Maintenance Procedure Note Mod 2010
DEFINITIONS
Specific Maintenance related information that is recommended, usually by the OEM, but is not 2300,
mandated, and may be incorporated into an actual procedure at a later date.
Tag or TEI)
2300 XSD mNoteRef Element
Usages:
Schema DispatchItem
Name Maintenance Procedures Mod 2010
DEFINITIONS
Concept Data or information that describe how to do the maintenance work. 2200, 2300,
Specific Procedural information that is unique to the dispatch domain or may be a summary of 2300,
one or more AMM maintenance procedures
Tag or TEI)
2300 XSD mProcedureR Element
ef
Usages:
Name Major Event Indicator Mod 2010
DEFINITIONS
Specific Indicates whether or not an event pertains to an emergency situation or other high 2300,
priority.
Tag or TEI)
2300 XSD majorEvent Attribute Data Type: xs:boolean
Usages:
Schema DmStatus, ExchangePackageStatusList
Name Manual Code Mod 2011
DEFINITIONS
Concept Abreviation identifying manual type being delivered in digital format. 2200, 2300,
Tag or TEI)
2200 Field Manual Code N/A Data Type: AN
Max Length: 4
Decimals: 0
2300 XSD productCode Attribute Data Type: xs:string
Usages:
Schema LinkTargetRepository, PmStatus
Name Manufacturer Cage Code Mod 2015
DEFINITIONS
Specific A unique identifer for the producer of the data. 2300,
Specific The unique identifier for the manufacturer as defined by the Defense Logistics 2200,
Information Service.
Tag or TEI)
2200 ML cagecode Attribute
Usages:
DTD mpd, msg3
2200 ML cagecode Element
Usages:
DTD mpd
2300 XSD extensionPro Attribute Data Type: xs:string
ducer
Usages:
SystemDescription
Name Manufacturer Code Mod 2016
DEFINITIONS
Concept Identifies the manufacturer, government agency or other organization controlling the DM,
design, production and part number assignment of the subject part.
Specific A five digit code assigned to identify the manufacturer of the product, normally the 2300,
Commercial And Government Entity (CAGE) code.
Specific A five digit code assigned to identify the manufacturer of the part, normally the 2200,
Commercial And Government Entity (CAGE) code. Can be a local code.
Specific Identifies the manufacturer, government agency or other organization controlling the 2000,
design, production and part number assignment of the subject part.
Tag or TEI)
2000 MSG & File MFR Data Element Reference Information for CAGE/NCAGE:
Use the five position alphanumeric code specified in
Cataloging Handbook H4/H8: Sections A and B,
Commercial and Government Entity (CAGE) Codes
(United States and Canada only) and Sections C and D,
NATO Supply Codes for Manufacturer(NCAGE)
(excluding United States and Canada).
Data Type: AN
Min Length: 5
Max Length: 5
Decimals: 0
For standard parts (Standard/Attaching Part Codes 3, 4,
and 6) the following part number types will be
identified by the referenced Manufacturer Code (CAGE
Code/NCAGE Code).
<FF1>
TYPE / CAGE CODE
AC / 88041
AF / 99238
AMS / 81343
AN / 88044
AND / 99237
JAN / 81350
MIL / 81349
MS / 96906
NAS / 80205
NAF / 80020
NASA / 88006
SAE / 81343
USA / 81351
USN / 88827
TYPE / NCAGE (NATO/NSCM)

A / K7766
AFNOR / F0110
AGS / U1653
AS / U1653
BNA / F0112
BNAE / F0111
CCTU / F0115
DIN / D8286
EN / I9005
AECMA / I9005
LN / D8442</FF1>
Usages:
Chapter 1, 12, 2, 3, 5, 7, 8, 9
Command A1ADDPRT, A1CHANGE, A1QTYDEC,
A1QTYINC, A1QUOTES, A1STOCKS,
A1UPDATE, P1PDINQY, P1UPDATE,
R1CDBACK, R1CDBINQ, R1CDBRSP,
R1CDBUPD, R1CPOXMT, R1CUSSHP,
R1DSPXMT, R1QTNINT, R1QTNREQ,
R1QTNXMT, R1SPLSHP, R1TDNXMT,
S1BOOKED, S1ORDEXC, S1PNSTAT,
S1POSTAT, S1QUOTES, S1SHIPPD,
S1STOCKS
Record Type 02, 03, 04, 05, 07, 12, 17, 21, 24, 27, 29,
32
2200 ML mfr Element
Usages:
DTD aipc, amm, cmm, cpm, eipc, srm, teman,
wm
2200 ML amfr Attribute An attribute which identifies if the part is built by the
airframe manufacturer
Usages:
DTD aipc
2200 ML manufact Attribute
Usages:
DTD msg3
2000 XSD MFR Element Data Type: xs:string

Min Length: 5
Max Length: 5
Usages:
Chapter 11, 13, 14, 15, 16, 3
Schema AircraftEvent,
AircraftHoursAndLandings,
AircraftOutOfService,
AircraftStatusChange,
ATA_MetricsPartsDetail,
ATA_PartCertificationForm,
ATA_SparesOrderExc,
ATA_SparesOrderStatusResponse,
ATA_SparesQuoteFinal,
ATA_SparesQuoteInterim,
ATA_SparesQuoteRequest,
ATA_SparesStockInquiry,
ATA_SparesStockResponse,
ATA_SparesSupplierShipNotice,
ATA_WarrantyClaim,
Logbook, LRU_Removal, PieceParts,
QuantityPerAircraft,
ScheduledMaintenance, ServiceBulletin,
ShopFindings, SummaryData
2000 XSD PartManufact Element Data Type: xs:string
urerCode
Min Length: 5
Max Length: 5
Usages:
Chapter 17
ODM DM Manufacturer Attribute Data Type: Character (5)
Code
Class Name: Function
Name Manufacturing Serial Number Mod 2016
DEFINITIONS
Specific A number assigned to identify the specific aircraft during the production/manufacturing 2200, 2300,
process.
Tag or TEI)
2200 ML msnbr Element
Usages:
DTD aipc, amm, frmfim, mpd, sb, sbi, sds,
srm, wm
Name Measurement Boundary Mod 2012
DEFINITIONS
Concept Indicates if a measurement value is the minimum or maximum allowable value. 2300,
Tag or TEI)
2300 XSD bound Attribute Data Type: xs:string
Permitted Value List: MeasurementBoundaryList

Usages:
DispatchProcedure,
NonNormalProcedure,
PERMITTED VALUES List Name: MeasurementBoundaryList

max Maximum value
min Minimum value
minMax Both miniumum and maximum value
Name Measurement Category Mod 2015
DEFINITIONS
Concept Describes the type of measurement (e.g., length, velocity, volume, etc.) 2300,
Tag or TEI)
2300 XSD category Attribute Data Type: xs:string
Usages:
NonNormalProcedure,
2300 XSD subCategory Attribute
Usages:
NonNormalProcedure,
Name Measurement System Mod 2015
DEFINITIONS
Specific Describes the measurement standard (e.g., US, SI, etc.) 2300,
Tag or TEI)
2300 XSD measurement Attribute Data Type: xs:string
System
Permitted Value List: Measurement Systems
Usages:
NonNormalProcedure,
PERMITTED VALUES List Name: Measurement Systems

other
si International System of Units
us United States customary units
Name Measurement Unit Indicator Mod 2009
DEFINITIONS
Concept Indicates whether or not a unit of measure label is generated during publication. 2300,
Tag or TEI)
2300 XSD showUnit Attribute Data Type: xs:boolean
Usages:
Name Measurement Value Mod 2015
DEFINITIONS
Concept Used to provide specific values of measurement and corresponding attributes (e.g., unit 2300,
of measure).
Concept The measurement taken to identify the specific and exact geographic position or DM,
location.
Name Measurement Value Mod 2015
Tag or TEI)
ODM DM Measurement Attribute
Value Class Name: Geographic Location
2300 XSD measure Element
Usages:
NonNormalProcedure,
2300 XSD measureBloc Element
k
Usages:
NonNormalProcedure,
Name Model Mod 2012
DEFINITIONS
Concept Identifies engine or aircraft model designation. May include a model dash number (e.g. 2000, 2200, 2300,
747-400).
Tag or TEI)
2200 Field Model Data Element Max Length = 19 if using extended field lengths
Data Type: AN
Max Length: 12
Decimals: 0
2200 ML model Attribute

Usages:
faammel, frmfim, lap, lea, sb, sbi, sds,
srm, teman, wm
2000 XSD MOL Element Data Type: xs:string
Min Length: 1
Max Length: 64
Usages:
Chapter 14, 16
ATA_WarrantyClaim
2300 XSD productRefM Attribute Data Type: xs:string
odel
Usages:
2000 XSD Model Element Data Type: xs:string
Max Length: 20
Usages:
Chapter 17
Name Model Type Mod 2009
DEFINITIONS
Concept Identifies an aircraft/engine model or model group 2300,
Specific Model/Type in Airplane Effectivity Cross Reference Table. Identifies the model or type 2200,
of aircraft covered by the document instance.
Tag or TEI)
2200 ML modtype Element
Usages:
Name Modification Number Mod 2016
DEFINITIONS
Specific A number assigned by the manufacturer to identify design changes to the aircraft. 2200, 2300,
Tag or TEI)
2200 ML mdnbr Element
Usages:
DTD aipc, amm, cmm, frmfim, sb, sbi, sds,
srm, wm
Name Moved Data Mod 2010
DEFINITIONS
Specific Indicates moved data within a Data Module 2300,
Tag or TEI)
2300 XSD move Element
Usages:
Name Moved From Mod 2010
DEFINITIONS
Specific Previous location of moved data within a Data Module. 2300,
Tag or TEI)
2300 XSD from Element
Usages:
Name Moved To Mod 2010
DEFINITIONS
Specific New location of moved data within a Data Module. 2300,
Tag or TEI)
2300 XSD to Element
Usages:
Name Multimedia Mod 2014
DEFINITIONS
Specific A grouping of elements containing information about multimedia objects. 2300,
Tag or TEI)
2300 XSD multimedia Element
Usages:
Name Multimedia Object Mod 2014
DEFINITIONS
Specific Describes information about a multimedia object. 2300,
Tag or TEI)
2300 XSD multimediaOb Element
ject
Usages:
Name Multimedia Run Time Duration Mod 2009
DEFINITIONS
Specific Specifies the length of time for a multimedia object to run. 2300,
Tag or TEI)
2300 XSD runTimeDurat Attribute Data Type: xs:integer
ion
Usages:
Name Naming Convention Mod 2013
DEFINITIONS
Specific The naming convention for the resources of a data group. 2300,
Tag or TEI)
2300 XSD resourceNami Element
ng Contains an XPATH expression that must return a
string. XPATH expression evaluated in the context of /
for an XML document (DM Content, DM Status, PM
Content, PM Status), of 'graphic' element for a
graphicresource, of 'multimediaObject' for a
multimedia resource.
Usages:
Name No Dispatch Mod 2010
DEFINITIONS
Specific Indicates that dispatch with an inoperative item is not allowed. 2300,
Tag or TEI)
2300 XSD noDispatch Element
Usages:
Schema DispatchItem, SystemFault
Name No Remark Mod 2010
DEFINITIONS
Specific Indicates that there are no restrictions relevant to a dispatch condition. 2300,
Tag or TEI)
2300 XSD noRemark Element
Usages:
Name Nomenclature Mod 2015
DEFINITIONS
Concept The name of a given part. For example, 'SERVICE UNIT, ASSY-PASS DM,
(Equipment/Furnishings ONLY)
Concept A common name that can be used for identification purposes or navigation events. 2300,
Specific The full name for an acronym or abbreviation 2300,
Specific A descriptive label for a sublevel within an XML Schema. 2300,
Specific The name of a given part. 2200,
Tag or TEI)
2200 ML nom Element
Usages:
DTD cmm, eipc, srm
2300 XSD name Element Data Type: xs:string
Usages:
ODM DM Nomenclature Attribute Data Type: Character (50)
Class Name: Manufacturer Part

2300 XSD title Element Data Type: xs:string
Usages:
DispatchProcedure,
NonNormalProcedure,
NormalProcedure, Pm, Substantiation,
2300 XSD fullName Attribute Data Type: xs:string
Usages:
2300 XSD origin Attribute The name of the the alerting system that manages the
annunciation / electronic message, e.g., EICAS, ECAM,
etc.
Usages:
NonNormalProcedure,
2300 XSD systemName Element Data Type: xs:string
Usages:
NonNormalProcedure,
Name Non Linear Content Flag Mod 2011
DEFINITIONS
Specific Used to indicate a data module that should not appear during a linear consultation of 2300,
the documentation.
Tag or TEI)
2300 XSD nonLinear Attribute Data Type: xs:boolean
Usages:
Schema DmStatus
Name Non-normal Landing or Flight Instruction Mod 2015
DEFINITIONS
Concept A specific recommendation for landing or continuing flight in a non-normal situation. 2300,
Tag or TEI)
2300 XSD land Element
Usages:
NonNormalProcedure
2300 XSD when Attribute Data Type: xs:string
Permitted Value List: LandWhenList

Usages:
NonNormalProcedure
2300 XSD continueFlight Element
Usages:
NonNormalProcedure
PERMITTED VALUES List Name: LandWhenList

ansa
asap
immediately
Name Note Mod 2014
DEFINITIONS
Concept Descriptive information used to provide recommendations or additional information, DM,
but not directly required for the accomplishment of a procedrue.
Specific Descriptive information used to provide recommendations or additional information, 2300,
but not directly required for the accomplishment of a procedure.
Specific Call attention to methods that make the job easier. 2200,
Tag or TEI)
2200 ML note Element Notes follow the text to which they relate and are
located directly under and vertically in line with the
text to which they apply.
Used to highlight or emphasize important points when

necessary. Notes are explanatory comments.
Usages:
faammel, frmfim, mpd, msg3, sb, sbi,
sds, srm, teman, wm
2300 XSD note Element
Usages:
ODM DM Note Class
Attributes: Note Text, Note Type Code, text
2300 XSD noteProc Element Pprocedural content considered essential to
emphasize. Information contained in notes may also
be safety related.
Usages:
Name Number Installed Mod 2010
DEFINITIONS
Specific Indicates, for a given dispatch item, the quantity of equipment, components, systems or 2300,
functions, installed on the airplane.
Specific The number (quantity) of items, subitem1, subitem2, subitem3 normally installed in the 2200,
aircreaft.
Tag or TEI)
2200 ML nbrins Element
2300 XSD numberInstall Attribute Data Type: xs:string
ed
Usages:
Name Number Required for Dispatch Mod 2010
DEFINITIONS
Specific Indicates, for a given dispatch item, the minimum quantity of equipment, components, 2300,
systems or functions which must be operative for dispatch, under the given condition.
Specific The minimum number (quantity) of items, subitem1, subitem2, subitem3 required for 2200,
operations provided the remarks are met.
Tag or TEI)
2200 ML nbrreq Element
2300 XSD numberRequi Attribute Data Type: xs:string
red
Usages:
Name Numbered List Mod 2015
ALSO KNOWN AS: Sequential List

Ordered List
DEFINITIONS
Concept A set items of text in which the sequence of the items listed is significant. 2300,
Concept A set of ordered items of text. 2200,
Tag or TEI)
2200 ML numlist Element Unlike the List structures elswhere in the DTD, the data
in this list may contain the required numbering if no
automatic numbering is defined by the NUMTYPE
attribute.
Usages:
sds, srm, teman, wm
2200 ML numlitem Element Numbered List Item - This tag identifies an item of a
NUMLIST.
Usages:
sds, srm, teman, wm
2200 ML numtype Attribute An attribute of NUMLIST which indicates the
numbering system to be used (alpha, numeric, other).
It also indicates any parentheses, full stops or
underscores that are necessary to indicate level. See
the ATA-TEXT-TECHREQ for the coding table. The
numbering is done by the receiver of the data. If this
attribute is not present the numbering must be
included in the text of the NUMLITEMs.
Permitted Value List: Numbered List Type

Usages:
srm, teman, wm
2300 XSD seqList Element
Usages:
PERMITTED VALUES List Name: Numbered List Type

ALB Alpha; lower case; both right and left parentheses
ALR Alpha; lower case; right parenthesis
AUP Alpha: Upper case; period
AUR Alpha; upper case; right parenthesis
NNB Number; no case; both right and left parentheses
NNP Number: no case; period
NNR Number; no case; right parenthesis
NNS Number; no case; underscore
RLP Roman numeral; lower case; period
RLR Roman numeral; lower case; right parenthesis
RUP Roman numeral; upper case; period
RUR Roman numeral; upper case; right parenthesis
Name Operations Procedure Note Mod 2010
DEFINITIONS
Specific Flight operations related information that is recommended, usually by the OEM, but is 2300,
not mandated, and may be incorporated into an actual procedure at a later date.
Tag or TEI)
2300 XSD oNoteRef Element
Usages:
Schema DispatchItem
Name Operations Procedures Mod 2010
DEFINITIONS
Specific Used to reference a specific operational procedure which must be accomplished when 2300,
operating with the listed item inoperative. Can reference an (o)procedure or an external
procedure (in the operating manual).
Tag or TEI)
2300 XSD oProcedureR Element
ef
Usages:
Name Operator Mod 2016
DEFINITIONS
Concept Aircraft Operator full designation. 2200,
Specific A code which identifies the entity responsible for the operations of the aircraft. 2300,
Tag or TEI)
2200 ML operator Element
Usages:
DTD aipc, amm, srm, wm
Name Optional Equipment Mod 2016
DEFINITIONS
Concept Aircraft equipment which is not required for a particular context or use. 2200,
Specific Indicates whether or not the given equipment is installed on the aircraft and, if so, then 2300,
conditions for dispatch must be met.
Tag or TEI)
2200 ML opteqp Attribute This attribute indicates whether or not the item,
subitem1, subitem2, or subitem3 are optional
equipment. An optional item, subitem1,subitem2,
subitem3 are indicated by three stars, "***".
Usages:
DTD faammel
2300 XSD optionalConfi Attribute Data Type: xs:boolean
gurationIndic
ator
Usages:
Schema Dispatchitem
2300 XSD ifInstalled Element
Usages:
2300 XSD ifOperated Element
Usages:
2300 XSD ifOperative Element
Usages:
Name Overline Mod 2009
DEFINITIONS
Specific Specifies whether or not textual data should be displayed in an overlined font. 2300,
Tag or TEI)
2300 XSD overline Attribute Data Type: xs:boolean
Usages:
Name Package Organization Mod 2013
DEFINITIONS
Specific The root element of the PackageOrganization schema which describes the content and 2300,
physical organization of an exchange package.
Tag or TEI)
2300 XSD packageOrga Element
nization
Usages:
Name Paired Item Mod 2014
DEFINITIONS
Specific Used to describe bi-column text. The columns are separated by a separator character 2300,
that is positioned relatively to the page width.
Tag or TEI)
2300 XSD pairedItem Element
Usages:
Name Paragraph Mod 2015
DEFINITIONS
Concept A subdivision of text that consists of one or more sentences, deals with one point or 2200, 2300,
gives the words of one speaker.
Specific General purpose container for textual information and other structured data. 2300,
Tag or TEI)
2200 ML content Attribute Copy of textual content of a paragraph within an
intelligent graphics application structure
Usages:
DTD igsheet, v4sheet
2200 ML para Element Identifies a piece of text, composed of a set of
sentences or graphical text elements which are to be
presented as a block separated in some way from its
neighbors. This element is the basic one which is
found almost every time when creating instances. It is
a mix of #PCDATA and the special text elements
identifying Tools, Circuit Breakers etc.
Usages:
faammel, fcom, frmfim, igsheet, mpd,
msg3, sb, sbi, sds, srm, teman, v4sheet,
wm
2200 ML subpara Element Subdivision Paragraph - A subdivision of a paragraph
into one or more subparagraphs
Usages:
DTD v4sheet
2200 ML parablock Attribute A rectangular region defining the intended area for
graphical placement of a text block.
Usages:
DTD v4sheet
2300 XSD para Element
Usages:
2300 XSD simplePara Element
Usages:
Schema DmStatus, ProjectRules
Name Parameter Mod 2013
DEFINITIONS
Specific Used as a container for attributes for passing parameters to objects within the 2300,
multimedia scene.
Tag or TEI)
2300 XSD parameter Element
Usages:
Schema Annunciation, CabinEquipMalfunction,
SystemDescription
Name Parameter Name Mod 2014
DEFINITIONS
Specific Used to identify a parameter that is provided to a software application. 2300,
Specific A non-unique descriptive text used to identify a multimedia object or group of 2300,
multimedia objects as a means of passing values to objects with the same name within
the multimedia scene.
Tag or TEI)
2300 XSD parameterNa Attribute Data Type: xs:string
me
Usages:
2300 XSD name Element
Usages:
Schema DmStatus
2300 XSD label Element The human readable display name for a parameter
Usages:
Schema DmStatus
Name Parameter Value Mod 2014
DEFINITIONS
Specific An assigned value used to pass a value to a multimedia object or software application. 2300,
Tag or TEI)
2300 XSD parameterVal Attribute Data Type: xs:string
ue
Usages:
2300 XSD value Element Data Type: xs:string
Usages:
Schema DmStatus
Name Performance Mod 2011
DEFINITIONS
Concept Data that provides the operating characteristics (weight, altitude, temperature, wind 2300, DM,
speed, aircraft speed, etc) of an aircraft in a given environment.Note: the operating
characteristic of a system is not considered as a Performance but as a System Limitation.
Tag or TEI)
2300 XSD perfoContent Element
Usages:
Schema Performance
ODM DM Performance Class
Attributes: Performance Criteria, Performance Title,
Performance Type
Name Performance Corrections Mod 2011
DEFINITIONS
Specific Adjustments to performance data based on airplane or environmental conditions. 2300,
Tag or TEI)
2300 XSD correctionTyp Element The name of the airplane or environmental condition
e under consideration.
Usages:
Schema Performance
2300 XSD correctionVal Element The amount by which data in the Performance table is
ue adjusted for a given condition.
Usages:
Schema Performance
Name Performance Data Mod 2015
DEFINITIONS
Specific A graphical or tabular representation of performance Data. 2300,
Tag or TEI)
2300 XSD perfoOutput Element
Usages:
Schema Performance
2300 XSD rowTitle Element
Usages:
Schema Performance
2300 XSD rowValue Element Data Type: xs:string
Usages:
Schema Performance
2300 XSD splitArea Attribute Used to define the split area of output data in the
performance table
Usages:
Schema Performance
2300 XSD splitDefinition Element Used to provide the context for cells included within a
split area of a Performance Table.
Usages:
Schema Performance
2300 XSD valueLegend Element Description of the parameters that are stored in each
of the Performance table Body cells
Usages:
Schema Performance
2300 XSD perfoData Element
Usages:
Schema Performance
2300 XSD colTitle Element
Usages:
Schema Performance
2300 XSD colValue Element Data Type: xs:string
Usages:
Schema Performance
Name Performance Database Mod 2011
DEFINITIONS
Specific A set of Performance data pertaining to a specific airframe/engine configuration, and 2300,
intended to be used in a Performance software application.
Tag or TEI)
2300 XSD perfoDatabas Element
eVersion
Usages:
Schema Performance
Name Performance Limitation Parameter Mod 2011
DEFINITIONS
Specific Conveys information about aircraft performance impacted by missing or inoperative 2300,
equipment.
Tag or TEI)
2300 XSD perform Element
Usages:
Schema Performance
2300 XSD perfValue Element
Usages:
Schema Cdlitem, DispatchProcedure,
Name Performance Limitation Parameter Name Mod 2011
DEFINITIONS
Specific A performance parameter related to a performance limitation. 2300,
Tag or TEI)
2300 XSD perf Element
Usages:
Name Performance Limitation Value Mod 2011
DEFINITIONS
Specific The value of a performance limitation corresponding to a given parameter. 2300,
Tag or TEI)
2300 XSD value Element
Usages:
Name Performance Restriction Mod 2010
DEFINITIONS
Specific Describes performance restrictions on aircraft operation due to missing or inoperative 2300,
equipment.
Tag or TEI)
2300 XSD cdlPerforman Element
ce
Usages:
Schema CdlItem
2300 XSD performance Element
Usages:
Schema CdlItem, dispatchProcedure,
Name Periodicity Mod 2011
DEFINITIONS
Concept Defines the accomplishment frequency for a Work Requirement. Periodicity data (limit, 2300, DM,
repetitive or specific accomplishment) must be defined and Operators must perform
the associated Work Requirement on or before the specified time(s).
Specific Scheduled Maintenance Task threshold and interval data. 2200,
Tag or TEI)
2200 ML periobox Element Periodicity Box - Scheduled Maintenance Task
periodicity data, limits data, and specific
accomplishment requirements.
Usages:
DTD mpd
2200 ML periodic Element The repetition of PERIODIC indicates a sequence of
threshold/interval statements (all have to be done).
The repetition of the structure within PERIODIC
indicates a choice between threshold/interval
statements (expressed in different units -> one has to
be done).
Usages:
DTD mpd, msg3
2200 ML periorel Attribute The repetition of periodic indicates a sequence of
periodicity statement. This attribute indicates whether
it is the first or the last in the sequence.
Usages:
DTD mpd
ODM DM Periodicity Class
Attributes: Effective Date, Limit Date, Periodicity ID,
Periodicity Justification, Periodicity Priority, Specific
Accomplishment
2300 XSD applicationInt Element
erval
Usages:
2300 XSD repairInterval Attribute
Permitted Value List: Repair Interval Codes
Usages:
2300 XSD repairLimit Element The limit to repair (composed of a number of
flight/calendar days, flight hours, flight cycles). Used
when repairInterval is set to A (value is set in a
remark).
Usages:
PERMITTED VALUES List Name: Repair Interval Codes

A Value is set in a remark
B 3 days
C 10 days
D 120 days
NA No repair interval
O To be defined by the operator
Name Periodicity Justification Mod 2011
DEFINITIONS
Concept A documented reason for the limit, repeat and/or threshold definitions for the Work 2300, DM,
Requirement.
Tag or TEI)
ODM DM Periodicity Attribute Data Type: Character (255)
Justification
Class Name: Periodicity

2300 XSD timeOfDispat Element
chRationale
Usages:
Name Phase of Flight Mod 2010
ALSO KNOWN AS: POF
DEFINITIONS
Concept A phase of flight (POF) is a segment of a mission for the purpose of operating an aircraft. 2300, DM,
Specific A division of the concept of a flight mission into smaller conceptual units. Each unit is a 2200,
particular phase of the mission.
Tag or TEI)
ODM DM Phase of Class
Flight Attributes: Phase of Flight Code, Phase of Flight Title
2300 XSD phaseOfFlight Element
Usages:
Schema DmStatus
2300 XSD phaseOfFlight Element
Contexts
Usages:
Schema DmStatus
Name Phase of Flight Code Mod 2012
DEFINITIONS
Concept Classification assigned to flight phase. 2300, DM,
Specific Indicates the particular Phase of Flight or point within a phase to which a particular 2000,
entry applies.
Tag or TEI)
2000 XSD POF Element See ATA Spec 2300 for more details.
Min Length: 3
Max Length: 3
Permitted Value List: POF Codes

Usages:
Chapter 11
Schema AircraftEvent, Logbook
2000 XSD FlightPhase Element See ATA Spec 2300 for more details.
Min Length: 3
Max Length: 3
Permitted Value List: POF Codes

Usages:
Chapter 17
2300 XSD phaseOfFlight Attribute Data Type: xs:NMTOKENS
Code
Usages:
Schema DmStatus, FailureConsequences,
NonNormalProcedure
PERMITTED VALUES List Name: POF Codes

AES Arrival/Engine Shutdown
APC Circuit Pattern
APF Final Approach
API Initial Approach
APR Approach
CRC Cruise Climb
CRD Cruise Descent
CRZ Cruise
DST Descent
ECL En Route Climb
ESD Engine Start/Depart
FLC Flight Close
FLP Flight Planning
GDS Ground Servicing
GOA Go-around
ICL Initial Climb
LND Landing
LNF Flare
LNR Landing Roll
PRF Pre-flight
PSF Post-flight
RTO Rejected Take-off
TOC Top of Climb (point between phases used for reliability analysis)
TOD Top of Descent (point between phases used for reliability analysis)
TOF Take-off
TXI Taxi-in
TXO Taxi-out
TXP Taxi to Take-off Position (sub-phase of Taxi-out)
TXR Taxi to Runway (sub-phase of Taxi-out)
Name Placard/Marker Content Data Mod 2011
DEFINITIONS
Concept A notice or plaque placed on equipment to provide important information to users. 2300,
Specific Identifies the text as it appears on a Placard or Marker. 2200,
Tag or TEI)
2200 ML pcd Element
Usages:
DTD aipc, cmm
2300 XSD placard Element
Usages:
Name Policy Originator Mod 2010
DEFINITIONS
Specific The regulatory agency or operator responsible for a regulation or operator policy. 2300,
Tag or TEI)
2300 XSD policyOriginat Element
or
Usages:
Schema DmStatus
Name Policy Reference Mod 2011
DEFINITIONS
Specific A reference to an operator or regulatory policy. 2300,
Tag or TEI)
2300 XSD policyRef Element
Usages:
Schema DmStatus
2300 XSD policyReferen Element
ces
Usages:
Schema DmStatus
2300 XSD reference Element
Usages:
Schema DmStatus
Name Precaution Mod 2010
DEFINITIONS
Specific Provides additional visibility to the flight crew about possible outcomes of an action. 2300,
Tag or TEI)
2300 XSD precaution Element
Usages:
NonNormalProcedures
Name Procedure Mod 2015
DEFINITIONS
Concept Identifies information or a list of ordered or conditioned steps to support aircraft 2200, 2300, DM,
operational requirements.
Specific Used to identify a crew awareness procedure that has no procedural content. 2300,
Name Procedure Mod 2015
Tag or TEI)
2200 ML proc Element
Usages:
DTD fcom
ODM DM Procedure Class
Attributes: Procedure Checklist, Procedure Memorized
Item, Procedure Title, Procedure Type
2300 XSD cdlProcedure Element
Usages:
Schema CdlItem
2300 XSD dispatchProc Element The top-level content element of the
edure dispatchProcedure data module, which describes a
series of actions to be taken in the event of deviations
from standard aircraft configuration.
Usages:
Schema DispatchProcedure
2300 XSD procContent Element
Usages:
DispatchProcedure,
2300 XSD normalProced Element The top-level content element of the NormalProcedure
ure schema which describes information about aircraft
systems, subsystems and components.
Usages:
2300 XSD nestedProced Element
ure
Usages:
Schema DispatchProcedure,
2300 XSD noProcConte Element
nt
Usages:
Name Procedure Context Mod 2016
DEFINITIONS
Specific Circumstances that define under which conditions a procedure is applied. 2300,
Tag or TEI)
2300 XSD context Element
Usages:
Name Procedure Description Mod 2013
DEFINITIONS
Specific The top-level content element of the ProcedureDescription schema which contains 2300,
information about a flight crew procedure.
Specific Introductory information about a procedure. 2300,
Specific A brief description of the steps required in accomplishing the Task. 2200,
Tag or TEI)
2200 ML procdesc Element Procedure Description - This was renamed from
Procedure (PROC).
Usages:
DTD msg3
2300 XSD procDescripti Element
on
Usages:
DispatchProcedure,
Name Procedure Omit Indicator Mod 2011
DEFINITIONS
Specific Indicates procedures that may be omitted under certain conditions. 2300,
Tag or TEI)
2300 XSD omit Attribute Data Type: xs:boolean
Usages:
Name Procedure Purpose Mod 2011
DEFINITIONS
Specific Describes the rationale for the M and O procedures included in the Dispatch Item. 2300,
Tag or TEI)
2300 XSD procedurePur Element
pose
Usages:
Name Product Mod 2009
DEFINITIONS
Specific Identifies an individual product instance in a Product Cross-Reference Table 2300,
Specific A product is an aircraft, aircraft engine, or propeller. 106,
Specific Unless indicated otherwise, it will mean jet fuel. 103,
Tag or TEI)
2300 XSD product Element
Usages:
Name Product Attributes Mod 2009
DEFINITIONS
Specific Provides descriptive information about a product that can be used as values for product 2300,
variables.
Tag or TEI)
2300 XSD productAttribu Element
teList
Usages:
2300 XSD productAttribu Element
te
Usages:
Name Product Condition Mod 2011
DEFINITIONS
Specific Describes conditions of a Product which will have an effect on the applicability of 2300,
technical data.
Tag or TEI)
2300 XSD condDescr Element A condition that is not defined in the CCT.
Usages:
2300 XSD cond Element
Usages:
2300 XSD condList Element
Usages:
2300 XSD condTypeList Element
Usages:
Name Product Cross Reference Association Mod 2009
DEFINITIONS
Specific Describes the association of a product instance in the Product Cross-Reference Table 2300,
with a product attribute or condition.
Tag or TEI)
2300 XSD assign Element
Usages:
Name Product Cross-Reference Table Mod 2010
DEFINITIONS
Concept A tabular listing that has the product identifiers that are applicable for a given 2200,
document. This is a generic term for the Effectivity Cross-Reference Table.
Specific The top-level content element of the productCrossRefTable Data Module, which is used 2300,
as a repository for defining product instances and associating values to product
attributes and conditions for each product instance.
Tag or TEI)
2300 XSD productCross Element
RefTable
Usages:
Name Product ID Mod 2013
DEFINITIONS
Specific Identifying number/code for a flight operations document or data set. 2300,
Specific Identifying number/code of product or service. 2000,
Tag or TEI)
2000 XSD ProductID Element Data Type: xs:string
Max Length: 15
Usages:
Chapter 17
2300 XSD productIdent Element
Usages:
Schema PmStatus, SubSetHeader
Name Project Rules Information Mod 2015
DEFINITIONS
Concept A set of project-specific rules for implementation of Spec 2300. 2300,
Tag or TEI)
2300 XSD commonInfo Element General descriptive information, e.g., project rule front
matter.
Usages:
Schema ProjectRules
2300 XSD snsRules Element Contains descriptions of one or several SNS systems
that apply to the project concerned.
Usages:
Schema ProjectRules
2300 XSD projectRules Element The top-level content element of the ProjectRules
schema which describes project-specific rules for Spec
2300 implementation.
Usages:
Schema ProjectRules
2300 XSD contextRules Element The set of project rules which can be related to a
particular schema/context or a particular elements and
attributes in the schema structures.
Usages:
Schema ProjectRules
2300 XSD nonContextR Element The set of project rules which cannot be related to any
ules particular schema/context or any particular elements
and attributes in the schema structures.
Usages:
Schema ProjectRules
2300 XSD snsDescr Element Provides a project-specific description of the complete
SNS breakdown.
Usages:
Schema ProjectRules
2300 XSD snsSystem Element The standard description of the System.
Usages:
Schema ProjectRules
2300 XSD snsSubSyste Element The standard description of the SubSystem.
m
Usages:
Schema ProjectRules
2300 XSD snsCode Element Contains a code used to define a component in an SNS
structure. The code concerned is represented as text
content. Depending on the context it can be either the
code of a system, a subsystem, a sub-subsystem or an
assembly.
Usages:
Schema ProjectRules
2300 XSD snsTitle Element Contains a title corresponding to a code used to define
a component in an SNS structure. The title is
represented as text content. Depending on the context
it can be either the title of a system, a subsystem, a
sub-subsystem or an assembly.
Usages:
Schema ProjectRules
2300 XSD snsSubSubS Element Contains the project-specific specification for each
ystem subsubsystem defined for the SNS subsystem
concerned.
Usages:
Schema ProjectRules
2300 XSD snsAssy Element Contains the project-specific specification of each
assembly defined for the SNS sub-subsystem
concerned.
Usages:
Schema ProjectRules
2300 XSD structureObje Element Specifies all rules about the project-specific use of
ctRuleGroup elements and attributes for all the various document
types (Schema) used within the project.
Usages:
Schema ProjectRules
2300 XSD structureObje Element Contains rules that apply to an element or an attribute,
ctRule which must be given when the intended use of that
object does not fully coincide with the specification,
for instance by being more restrictive.
Usages:
Schema ProjectRules
2300 XSD objectPath Element Contains an XPath address defining where an element
or attribute occurs in the Schema structure. This must
be identified for any element or attribute for which
rules are given.
Usages:
Schema ProjectRules
2300 XSD objectUse Element Contains a specific description and intended use for
each element, attribute, or notation that is recorded in
the projectRules data module. The description should
be a short narrative explanation of the use to the
extent that interpretation of the object is perfectly
clear.
Usages:
Schema ProjectRules
2300 XSD objectValue Element Contains the description of the intended meaning.
When relevant, each specific single value, range of
values, or pattern value that is applicable to an
element or attribute within a project or organization
must be given. In addition, there should be a short
description of each single value, value range, or
pattern value to explain the intended meaning of the
value. Since this element is repeatable, it is possible to
specify multiple and/or single values, ranges of values,
or pattern values for a specific element or attribute.
Usages:
Schema ProjectRules
2300 XSD nonContextR Element Contains a rule not related to any particular schema,
ule schema element or attribute.
Usages:
Schema ProjectRules
Name Proviso Mod 2010
DEFINITIONS
Specific A conditional provision or group of provisions for dispatchability. 2300,
Tag or TEI)
2300 XSD proviso Element
Usages:
2300 XSD provisoSet Element
Usages:
Name Publication Module Mod 2010
DEFINITIONS
Specific The top-level content element of the PublicationModule schema. 2300,
Tag or TEI)
2300 XSD pm Element
Usages:
Schema Pm
Name Publication Module Entry Mod 2010
DEFINITIONS
Concept The set of data that constitutes a publication. 2300,
Tag or TEI)
2300 XSD pmEntry Element
Usages:
Schema Pm
2300 XSD pmEntryCode Attribute Data Type: xs:string
Usages:
Schema Pm
2300 XSD pmEntryType Attribute Data Type: xs:string
Usages:
Schema Pm
Name Publication Module Issuer Mod 2010
DEFINITIONS
Specific The CAGE code of the publication module issuing company. 2300,
Tag or TEI)
2300 XSD pmIssuer Attribute
Usages:
Schema Pm, PmStatus
Name Publication Module Status Mod 2015
DEFINITIONS
Specific Describes the revision status of a publication module. 2300,
Specific The top-level content element of the PmStatus schema. 2300,
Tag or TEI)
2300 XSD pmStatus Element
Usages:
Schema PmStatus
2300 XSD pmStatusEntr Attribute
yCode Permitted Value List: PmStatusEntryCodeList
Usages:
2300 XSD restrictionUse Element A label providing some specific restriction of the use of
the publication.
Usages:
Schema PmStatus
PERMITTED VALUES List Name: PmStatusEntryCodeList

c Changed
d Deleted
n New
u Unchanged
Name Publication Scope Mod 2016
DEFINITIONS
Specific Scope of publication that a product is issued for (All, fleet, envelope model, single 2300,
aircraft, etc.)
Tag or TEI)
2300 XSD prodPubScop Attribute
e Permitted Value List: PublicationScope
Usages:
Schema PmStatus, SubSetHeader
PERMITTED VALUES List Name: PublicationScope

all Generic data that does not pertain to a particular aircraft, model or fleet (used for
company manuals)
envmod Non-customized data for an Envelope Model that may consists to one or more aircraft
models
fleet Customized data for one or more aircraft of one or more aircraft models
fleetCoc Fleet data embedding also some COC
msn Customized data for one particular aircraft
msnCoc MSN data embedding also some COC
Name Publication Type Mod 2016
DEFINITIONS
Specific Specifies the type of publication that a product is issued for (e.g. normal revision, 2300,
temporary revision, certification package, etc.)
Tag or TEI)
2300 XSD productPubTy Attribute Data Type: xs:string
pe
Permitted Value List: Product Publication Types
Usages:
Schema PmStatus
PERMITTED VALUES List Name: Product Publication Types

cp A PM for data pertaining to a Certification Package
nr A PM for data pertaining to a Normal Revision
osd A PM for Operational Suitability Data - data required by an operator to develop its own
publications
tr A PM for data pertaining to a Temporary Revision
Name Qualification Reference Mod 2011
DEFINITIONS
Specific Identifies the value of a qualification which is defined in the QualifierRepository data 2300,
module.
Tag or TEI)
2300 XSD qualification Element
Usages:
Schema DmStatus
2300 XSD qualifierIdent Attribute Data Type: xs:NCName
Usages:
Schema DmStatus
Name Qualifier Mod 2011
DEFINITIONS
Specific Used to describe categories or properties about dispatch conditions or avionics contexts. 2300,
Tag or TEI)
2300 XSD localValue Element Describes a local value used when there is no discrete
property values for the qualifier (example : speed).
Usages:
2300 XSD qualifier Element
Usages:
Name Qualifier Repository Mod 2010
DEFINITIONS
Specific The top-level content element of the qualifierRepository data module used to provide 2300,
qualifications of dispatch conditions or provisos or avionics contexts.
Tag or TEI)
2300 XSD qualifierRepo Element
sitory
Usages:
Name Reason For Change Mod 2011
DEFINITIONS
Concept A textual explanation of why a piece of information is different from previous versions. DM,
The Reason for Change is used by data receivers to determine, among other things,
whether the new information needs to be reviewed by engineering personnel.
Specific Specifies the type of change made. 2300,
Specific A summary of changes and/or the reasons for the changes made within a Data Module. 2300,
Tag or TEI)
ODM DM Reason For Class
Change Attributes: Reason for Change ID, Reason for Change
Status, Reason for Change Text
2300 XSD reasonForUp Element
date
Usages:
2300 XSD updateReaso Attribute
nType Permitted Value List: Update Reason Types
Usages:
2300 XSD historyAndRa Element A cumulative history of changes made to the Dispatch
tionale Item and why.
Usages:
PERMITTED VALUES List Name: Update Reason Types

editorial
other
technical
Name Reason for Data Release Mod 2015
DEFINITIONS
Specific Provides the reason for issuance of a Temporary Data Module or Bulletin. 2300,
Tag or TEI)
2300 XSD reasonForSu Element
bset
Usages:
Schema SubSetHeader
2300 XSD reasonForRe Element
vision
Usages:
Schema SubSetHeader
Name Reason for Deletion Mod 2010
DEFINITIONS
Concept Detailed textual explanation of why the task was deleted from the Maintenance 2200,
Planning Document.
Specific Explanation for why a Data Module has been deleted. 2300,
Tag or TEI)
2200 ML reasdel Element
Usages:
DTD mpd
2300 XSD reasonForDel Element
etion
Usages:
Name Redundancy Losses Mod 2010
DEFINITIONS
Specific In cases where there are mulitiple systems available for a given function, Redundancy 2300,
Losses conveys information to the flight crew in the event that one or more of those
systems fails.
Tag or TEI)
2300 XSD redundancyL Element
osses
Usages:
NonNormalProcedure
Name Reference Mod 2016
ALSO KNOWN AS: Data Module (DM) Reference

Non-graphic Media References
Graphic Reference
Cross-Reference
Internal Reference
External Reference
DEFINITIONS
Specific Identifies the exact target within a data module when a reference addresses a specific 2300,
location within another data module rather than the whole data module. The target
must be an element in the destination data module and the target identification is the
id attribute of the target element.
Specific A reference to a procedure in a location external to the current source. 2300,
Specific Data relating the current information to information at another location either internal 2000, 2200, 2300,
or external to the current source.
Tag or TEI)
2300 XSD perfoSoftware Element
Ref
Usages:
Schema Performance
2300 XSD condRef Element Identifies a single condition that is defined in the CCT
condition list
Usages:
2300 XSD condRefGrou Attribute Provides the type of relationship with another
pType condition
Usages:
2300 XSD condRefId Attribute Identifier of the referenced condition as defined in the
condition list
Data Type: xs:idRef
Usages:
2200 ML refaps Element A reference to another application structure
(intelligent graphics object) within the same manual
Usages:
DTD igsheet
2200 ML refcond Element An intelligent graphics navigation mechanism that is
initiated based on a choice of options
Usages:
DTD igsheet, v4sheet
2200 ML grphcref Element Identifies the text describing a reference to a graphic.
It is used at the beginning of an anchor when the
graphic is applicable to the whole anchor. This tag can
also used within the text.
Usages:
mpd, msg3, sb, sds, srm, teman,
2200 ML ref Entity When used as an entity, contains refext or refint.
Usages:
DTD faammel
2200 ML refmodel Attribute Model identifier associated with the manual being
referenced
Usages:
faammel, frmfim, igsheet, mpd, msg3,
sb, sbi, sds, srm, teman, v4sheet, wm
2200 ML shownow Attribute Indicator to determine whether the graphic should be
displayed upon navigation
Usages:
igsheet, mpd, msg3, sb, sds, srm, teman,
v4sheet, wm
2200 ML refext Element A reference to text or a structure in another manual.
Identifies a reference to another manual or document.

Contains the 'human readable' text explaining the
reference. The attributes give the information
necessary to allow the system to resolve the reference.
Usages:
2200 ML refint Element A reference to text within the same manual
Usages:
2200 ML refmedia Element A reference to a non-graphic media file (PDF, PNG,
JPEG, VRML, MPEG, MP3, etc.)
Contains the 'human readable' text explaining the
reference. The attributes give the information
necessary to allow the system to resolve the reference.
Usages:
mpd, msg3, sb, sds, srm, teman,
v4sheet, wm
2300 XSD internalRef Element Properties as per S1000D.
Usages:
2300 XSD internalRefId Attribute Data Type: xs:idref
Usages:
2300 XSD referredFrag Attribute For references to another Data Module, contains the
ment identification of an exact target within the data module
when the reference addresses a specific location
within another data module rather than the whole
data module. The target must be an element in the
destination data module and the target identification is
the id attribute of the target element.
Usages:
FrontMatter, Pm, QualifierRepository,
2300 XSD dmRef Element Definition and properties as per S1000D.
Usages:
CdlItem, DataSetStatusList,
2300 XSD systemRef Element
Usages:
2300 XSD condCrossRe Element
fTableRef
Usages:
2300 XSD productCross Element
RefTableRef
Usages:
2300 XSD condRefId Attribute Data Type: xs:IDREF
Usages:
2300 XSD condTypeRefI Attribute Data Type: xs:IDREF
d
Usages:
2300 XSD reasonForUp Attribute Data Type: xs:IDREFS

dateRefIds
Usages:
2300 XSD dispatchItems Element
Ref
Usages:
Schema SystemFault
2300 XSD dispatchRedir Element A reference to a different dispatch item to replace the
ect current one.
Usages:
Schema DispatchItem
2300 XSD extAction Element
Usages:
Schema SystemFault
2300 XSD externalRef Element
Usages:
GlossaryRepository,
NonNormalProcedure,
2300 XSD regulatoryRef Element
Usages:
Schema DispatchItem
2300 XSD pmRef Element
Usages:
Schema DataSetStatusList, Pm
2300 XSD systemPageR Element The reference to a system page where affected parts
ef of the failed system are indicated.
Usages:
NonNormalProcedure
2300 XSD approbationIn Attribute The supplier internal reference or number to track the
ternalReferen approbation
ce
Usages:
Schema Approval
2300 XSD approvalRefe Element A reference to the approval document or data.
rence
Usages:
Schema Approval
2000 XSD RML Element Model associated to manual being referenced

Min Length: 1
Max Length: 20
Usages:
Chapter 15
Schema DeliveredAircraftTransferPartList
2300 XSD subsequentT Element Reference to a previous annunciation (if any).
o
Usages:
Schema Annunciation
2300 XSD actionDepend Attribute Reference to another action, simultaneousAction or
encyRefID actionBlock upon which the subject is dependent.
Data Type: xs:IDREF
Usages:
2300 XSD productRefNb Attribute The product number in which the external reference is
r targeted.
Usages:
Name Referenced Location Mod 2012
DEFINITIONS
Concept Identifies the target location of a cross-reference or hyperlink. 2000, 2200, 2300,
Tag or TEI)
2200 ML refloc Attribute Referenced Location - Identifies a location in another
manual as defined by REFMAN and/or REFTYPE. This
attribute is analogous to the REFID of the REFINT
element, but because an external reference may not
be resolvable by the system it is not explicitly defined
as an SGML ID.
Usages:
2300 XSD path Attribute XPATH address
Usages:
2000 XSD RFL Element Data Type: xs:string
Min Length: 1
Max Length: 20
Usages:
Chapter 15
Schema DeliveredAircraftTransferPartList
Name Regulatory Authority Mod 2016
DEFINITIONS
Concept Groups all Government Agencies, for all countries, in charge of supervising and DM,
controlling the air transportation process in that particular country. For example FAA in
USA.
Specific Specifies the regulatory authority to whose requirements a set of flight crew data 2300,
conforms.
Specific Specifies the regulatory standard to which a set of flight crew data conforms (e.g., US, 2300,
EU, CAN, etc.).
Specific The National Aviation Authority / Approving Competent Authority with jurisdiction over 2000,
the organization issuing part certification or conformance data.
Tag or TEI)
2000 XSD NAA Element Data Type: xs:string
Min Length: 1
Max Length: 64
ODM DM Regulatory Class

Authority
2300 XSD norm Element Data Type: xs:string
Usages:
Schema Approval, PmStatus, SubSetHeader
Name Regulatory Directive Mod 2011
DEFINITIONS
Concept A directive issued by a regulatory agency providing information or instructions that 2300,
must be complied with.
Tag or TEI)
2300 XSD regulatoryDir Element
ective
Usages:
Schema Approval
Name Related Effects Mod 2009
DEFINITIONS
Specific A detailed statement that describes the effects that other systems have on a given 2300,
system; or a given system has on other systems.
Tag or TEI)
2300 XSD relatedEffects Element
Usages:
Name Remarks Mod 2011
DEFINITIONS
Concept Notation of any factors influencing the analyst during completion of the analysis or any DM,
conclusions not obviously supported by the analysis.
Specific Indicates that there are restrictions relevant to a dispatch condition. 2300,
Specific Includes the placard (*), maintenance (M), operations (O), and relief for an item, 2200,
subitem1, subitem2, subitem3. The relief is the data that includes a statement
prohibiting or permitting operation with a specific number of items inoperative,
provisos (conditions and limitations) for such operation, and appropriate notes.
Tag or TEI)
2200 ML remarks Element
Usages:
DTD msg3
2200 ML remark Element
Usages:
DTD faammel, msg3
ODM DM Remarks Attribute
Class Name: Zonal Analysis
2300 XSD remark Element
Usages:
Name Removable Item Indicator Mod 2017
DEFINITIONS
Specific Used to indicate items in the Master Minimum Equipment List which are non-essential 2300,
and may be removed under airline process and responsibility.
Tag or TEI)
2300 XSD removable Attribute Data Type: xs:boolean
Usages:
Schema DispatchItem
Name Repair Limit Number Mod 2011
DEFINITIONS
Specific Indicates the maximum number of hours, days, or cycles before a repair must be 2300,
completed.
Tag or TEI)
2300 XSD nbr Attribute Data Type: xs:positiveInteger
Usages:
Name Repair Limit Unit Mod 2011
DEFINITIONS
Specific Specifies the unit of measure corresponding to the maximum time before a repair is 2300,
required.
Tag or TEI)
2300 XSD unit Attribute Data Type: xs:string
Permitted Value List: RepairLimitUnits

Usages:
PERMITTED VALUES List Name: RepairLimitUnits

calendarDays
flightCycles
flightDays
flightHours
hours
Name Response Mod 2016
DEFINITIONS
Specific The flight crew action when no specific challenge is identified. 2300,
Specific The second part of a two-part flight crew action that identifies the setting of a control to 2300,
be checked or manipulated.
Tag or TEI)
2300 XSD response Element Data Type: xs:string
Usages:
DispatchProcedure,
NonNormalProcedure,
2300 XSD variableInput Element Indicates a displayed value that the pilot must confirm.
Usages:
NonNormalProcedure,
Name Revision Date Mod 2012
DEFINITIONS
Concept A date that can be used to establish a time order between different revisions of the 2300, DM,
same Information Set. Revision Date can also be used to establish which information set
is to be used as a baseline for incremental revision information.
Specific Year, Month, Day associated with a revision cycle for the data. 2000, 2200,
Tag or TEI)
ODM DM Revision Date Attribute Data Type: Date
Class Name: Transmittal Information

2300 XSD closedApplica Attribute Provides the revision date of the pmEntry, considered
bilityRevDate for closed applicability.
Data Type: xs:dateTime
Usages:
Schema PmStatus
2300 XSD openApplicab Attribute Provides the revision date of the pmEntry, considered
ilityRevDate for open applicability
Data Type: xs:dateTime
Usages:
Schema PmStatus
2200 ML revdate Attribute For initial issue of a document, before it is revised, the
REVDATE value shall be equal to the original issue date.
Date Format: YYYYMMDD
Usages:
faammel, fcom, frmfim, igsheet, lap, lea,
mpd, msg3, sb, sbi, sds, srm, teman,
v4sheet, wm
2200 Field Revision Date Data Element Data Type: AN
Max Length: 8
Decimals: 0
2200 ML revdate Element For initial issue of a document, before it is revised, the
REVDATE value shall be equal to the original issue date.
Usages:
DTD sb, sbi
2000 XSD RVD Element Data Type: xs:date
Date Format: YYYY-MM-DD
Usages:
Chapter 11, 15, 16
2300 XSD pmEntryRevD Element Used to provide revision dates for open and closed
ates applicability changes at a pmEntry level of the
Publication Module.
Usages:
Schema PmStatus
2000 XSD RevisionDate Element Data Type: xs:date
Usages:
Chapter 17
Name Revision End Mod 2010
DEFINITIONS
Specific Marks the end of data which has been revised. 2200, 2300,
Tag or TEI)
2200 ML revend Element Revision End - This tag identifies the end of revised
data started by the tag REVST.
Usages:
sds, srm, teman, wm
2300 XSD endPos Attribute Data Type: xs:positiveInteger
Usages:
Name Revision Markup Mod 2013
DEFINITIONS
Concept Describes changes to a Data Module or Publication Module. 2300,
Tag or TEI)
2300 XSD applicRevisio Element
ns
Usages:
Schema DmStatus
2300 XSD contentRevisi Element
ons
Usages:
2300 XSD change Element
Usages:
2300 XSD metadataRevi Element
sions
Usages:
Schema DmStatus
Name Revision Number Mod 2017
DEFINITIONS
Concept The unique number associated with a revision release. 2000, 2200, 2300,
Concept A number that uniquely identifies a particular revision of an Information Set. DM,
Tag or TEI)
ODM DM Revision Attribute
Number Class Name: Transmittal Information
2200 ML revnbr Element
Usages:
DTD sb
2200 ML revnbr Attribute A number assigned to the revision of the data.
Usages:
DTD mpd, msg3
2000 XSD REV Element Data Type: xs:string
Min Length: 1
Max Length: 6
Usages:
Chapter 11, 14, 15, 16
ATA_WarrantyClaim,
2300 XSD issueNumber Attribute Data Type: xs:string
Usages:
Schema Approval, DataSetStatusList, Pm,
PmStatus, SubSetHeader
2300 XSD subSetIssueN Attribute Data Type: xs:string
umber
Usages:
Schema DmStatus
2000 XSD RevisionNum Element Data Type: xs:string
Max Length: 12
Usages:
Chapter 17
2300 XSD minorIssueNu Attribute Data Type: xs:string
mber
Usages:
Schema Approval, DataSetStatusList, DmStatus,
Pm, PmStatus, SubSetHeader
Name Revision Start Mod 2010
DEFINITIONS
Specific Marks the start of data which has been revised. 2200, 2300,
Tag or TEI)
2200 ML revst Element This tag identifies that all data following the tag, until
the tag REVEND is reached is revised with information
from the manufacturer in this revision of the
Document Instance.
Usages:
sds, srm, teman, wm
2300 XSD startPos Attribute Data Type: xs:positiveInteger
Usages:
Name Right Column Mod 2014
DEFINITIONS
Specific In bi-column text, the information in the right column of a paired item. 2300,
Tag or TEI)
2300 XSD rightPart Element
Usages:
Name Roles Mod 2011
DEFINITIONS
Specific Indicates that specific maintenance personnel to be defined by the operator are 2300,
required to perform the referenced maintenance procedure.
Specific Specifies the airline functional areas responsible for completing an action. 2300,
Tag or TEI)
2300 XSD roles Attribute
Permitted Value List: Proviso Role List
Usages:
2300 XSD specificPerso Attribute Data Type: xs:string
nnelRequired
Usages:
Schema DispatchItem
PERMITTED VALUES List Name: Proviso Role List

Cabin
Cargo
Dispatch
Flight
GroundHandling
Maintenance
OperationalSecurity
Organization
Name Script Mod 2009
DEFINITIONS
Specific Specifies whether or not textual data should be displayed in superscript or subscript 2300,
typeface.
Tag or TEI)
2300 XSD script Attribute Data Type: xs:string
Permitted Value List: Typeface Scripts

Usages:
PERMITTED VALUES List Name: Typeface Scripts

sub Textual data should be displayed in subscript
super Textual data should be displayed in superscript
Name Secondary Failure Mod 2011
ALSO KNOWN AS: Failure, Secondary

Failure, Dependent
DEFINITIONS
Concept Failure of an item which is caused by the failure of an associated item(s). 2200, 2300, WATOG,
Tag or TEI)
2300 XSD secondaryFail Element
ures
Usages:
NonNormalProcedure
Name Serial Number Mod 2010
ALSO KNOWN AS: MSN

Manufacturer Serial Number
DEFINITIONS
Concept A Part Serial Number (SER) or Unique Component Identification Number (UCN), along DM,
with a code identifying the party assigning it, will uniquely identify the part throughout
its life, whether or not the Part Number changes.
Specific The serial number of a referenced item. 2300,
Specific The airframe or engine or component serial number(s). 2200,
Tag or TEI)
ODM DM Serial Attribute Data Type: Character (20)
Number
Class Name: Identifiable Item

2200 ML serial Element
Usages:
DTD mpd, msg3
2300 XSD productRefSe Attribute Data Type: xs:string
rial
Usages:
Name Service Bulletin Number Mod 2016
ALSO KNOWN AS: SB
DEFINITIONS
Concept The identifier of a Service Bulletin. This identifier must include information regarding 2200,
the aircraft or engine type, the model, the ATA number, and the sequence number
necessary to uniquely identify the Service Bulletin.
Specific The identifier of a Service Bulletin referenced in an applicability statement. 2300,
Specific Specifies the numeric identifier of a Service Bulletin. To uniquely identify a Service 2000,
Bulletin, the identifier must include information regarding aircraft or engine type,
model, ATA chapter/system number, and sequence number.
Tag or TEI)
2200 ML sbnbr Attribute
Usages:
DTD aipc, amm, eipc, em, frmfim, igsheet,
sds, srm, v4sheet, wm
2200 ML sbnbr Element
Usages:
DTD aipc, amm, cmm, eipc, em, frmfim, sb,
sbi, sds, srm, wm
2000 XSD SBN Element Data Type: xs:string
Min Length: 1
Max Length: 50
Usages:
Chapter 11, 16
Schema ATA_PartCertificationForm, Logbook,
ServiceBulletin, SummaryData
Name Show Plugin Controls Mod 2009
DEFINITIONS
Specific Used in an application to indicate whether or not third-party plugin controls should be 2300,
displayed.
Tag or TEI)
2300 XSD showPluginC Attribute Data Type: xs:string
ontrols
Permitted Value List: Show Plugin Controls
Usages:
PERMITTED VALUES List Name: Show Plugin Controls

hide Third-party controls should not be displayed
show Third-party controls should be displayed
Name Silent Checklist Mod 2011
DEFINITIONS
Specific Indicates that a checklist is accomplished by one crewmember without response or 2300,
verification from other crew member.
Tag or TEI)
2300 XSD silent Attribute Data Type: xs:boolean
Usages:
Name Software Data Mod 2011
DEFINITIONS
Specific Describes the properties of Performance software. 2300,
Specific Software equipment properties. 2200,
Tag or TEI)
2300 XSD digitalPerform Element
anceInfo
Usages:
Schema Performance
2300 XSD perfoSoftware Element
Version
Usages:
Schema Performance
2200 ML sftdata Element
Usages:
DTD amm
Name Software Parameter Mod 2014
DEFINITIONS
Specific Used to declare elements and attributes that contain values that can be passed to a 2300,
software application.
Tag or TEI)
2300 XSD columnParam Element
eter
Usages:
Schema DmStatus
2300 XSD simpleParam Element
eter
Usages:
Schema DmStatus
2300 XSD tableParamet Element
er
Usages:
Schema DmStatus
2300 XSD softwarePara Element
meters
Usages:
Schema DmStatus
2300 XSD paramContex Data Element Used to provide the context in which a parameter is
t used.
Usages:
Schema DmStatus
2300 XSD softwareNam Attribute
e
Usages:
Schema DmStatus
Name Source of Reference Mod 2011
DEFINITIONS
Specific Used to identify Data Modules where a link is located. 2300,
instances. Gives a unique, retrieval engine dependant code for the source or start point
for a cross reference. This can be used for explicit or implicit cross references.
Tag or TEI)
2200 ML targetrefid Attribute
Usages:
faammel, fcom, frmfim, mpd, sb, sds,
teman, wm
2300 XSD source Element
Usages:
Name Specification Reference Mod 2010
DEFINITIONS
Specific The designation for an industry specification/standard. 2300,
Tag or TEI)
2300 XSD productRefDa Attribute Data Type: xs:string
taSpec
Usages:
Name Status Message Mod 2010
ALSO KNOWN AS: Status Message List
DEFINITIONS
Specific An electronic message that provides information to the flight or maintenance crews 2200, 2300,
about the status of various aircraft systems. These messages have less urgency than
Alert Messages.
Tag or TEI)
2300 XSD aircraftStatus Element
Usages:
Schema SystemFault
Name Strikeout Mod 2009
DEFINITIONS
Specific Specifies whether or not textual data should be displayed in strikeout font. 2300,
Tag or TEI)
2300 XSD strikeout Attribute Data Type: xs:boolean
Usages:
Name Subset Mod 2011
DEFINITIONS
Specific Used to describe an anomoly with the airplane, or to provide data in advance of a 2300,
scheduled revision, e.g., FCOM Bulletin.
Tag or TEI)
2300 XSD subSet Element
Usages:
Schema DmStatus
Name Subset Approval Identifier Mod 2010
DEFINITIONS
Specific Provides an identifier for subset approval. 2300,
Tag or TEI)
2300 XSD approvalRefe Element
rence
Usages:
Schema SubSetHeader
Name Subset Approval Organization Mod 2011
DEFINITIONS
Specific Contains the name of the organization responsible for approving a subset (e.g., Flight 2300,
Crew Bulletin).
Tag or TEI)
2300 XSD subSetAppro Element
valOrganizati
on Usages:
Schema SubSetHeader
Name Subset Cancellation Criteria Mod 2010
DEFINITIONS
Specific Describes conditions or criteria that, once completed, allow a subset to be cancelled. 2300,
Tag or TEI)
2300 XSD cancelledBy Element
Usages:
Schema SubSetHeader
Name Subset Criteria Mod 2010
DEFINITIONS
Specific Describes the criteria for which a subset is applicable. 2300,
Tag or TEI)
2300 XSD applicableTo Element
Usages:
Schema SubSetHeader
Name SubSet Header Mod 2011
DEFINITIONS
Specific The top-level content element of the SubSetHeader schema which describes 2300,
information about anomolies with the aircraft or data preceding a scheduled revision.
Tag or TEI)
2300 XSD SubSetHeade Element
r
Usages:
Schema SubSetHeader
Name SubSet Impact Mod 2011
DEFINITIONS
Specific Indicates if content in the subset may impact information displayed on the ECAM/EICAS 2300,
system.
Tag or TEI)
2300 XSD subSetImpact Attribute Data Type: xs:boolean
Usages:
Schema DmStatus
Name SubSet Importance Mod 2011
DEFINITIONS
Specific Describes the criticality of the subset. 2300,
Tag or TEI)
2300 XSD subSetImport Attribute Data Type: xs:string
ance
Usages:
Schema DmStatus
Name SubSet Information Mod 2011
DEFINITIONS
Specific Provides the subsets applicable to the data module. 2300,
Tag or TEI)
2300 XSD subSetInfo Element
Usages:
Schema DmStatus
Name SubSet Type Mod 2011
DEFINITIONS
Specific Identifies the subset type (e.g., OEB, CCB, FCBUL, etc.) 2300,
Tag or TEI)
2300 XSD subSetType Attribute Data Type: xs:string
Usages:
Schema DmStatus
Name Substantiation Mod 2011
DEFINITIONS
Specific The top-level content element of the substantiation schema which describes the 2300,
background and rationale for allowing an aircraft to operate with an inoperative item.
Tag or TEI)
2300 XSD substantiation Element
Usages:
Name Substantiation Background Mod 2011
DEFINITIONS
Specific Provides general information, system description, test results, to support the rationale 2300,
to operate an aircraft with an inoperative item.
Tag or TEI)
2300 XSD systemBackG Element
round
Usages:
Name Supplemental Content Mod 2014
DEFINITIONS
Specific The root element for the SupplementalContent schema which references 2300,
supplementary multimedia information not contained in the DM.
Tag or TEI)
2300 XSD supplemental Element
Content
Usages:
Schema SupplementalContent
Name Symbol Mod 2014
DEFINITIONS
Specific A reference to a Graphical Icon used as a substitute for textual information. 2300,
Specific The name or description of a symbol preceeding the part number denoting a classified 2200,
part and/or the part status.
Tag or TEI)
2200 ML symbol Element
Usages:
DTD eipc
2300 XSD symbol Element
Usages:
NonNormalProcedure,
Name System Description Mod 2010
DEFINITIONS
Concept Text describing the ATA System. DM,
Specific The top-level content element of the SystemDescription schema which describes 2300,
information about aircraft systems, subsystems and components.
Tag or TEI)
ODM DM System Attribute Data Type: Character (50)
Description
Class Name: System

2300 XSD systemDescri Element
ption
Usages:
Name System Fault Mod 2011
DEFINITIONS
Specific The top-level content element of the SystemFault schema which relates information 2300,
from the EICAS/ECAM system to the MMEL Item.
Tag or TEI)
2300 XSD systemFault Element
Usages:
Schema SystemFault
Name Table (CALS) Mod 2014
ALSO KNOWN AS: Cellular Table

CALS Table
DEFINITIONS
Concept A markup representation of a table as standardized in the CALS (Continuous Acquisition 2200, 2300,
and Life-Cycle Support, previously known as Computer-aided Acquisition and Logistic
Support) initiative.
Specific A structured table composed (ultimately) of ENTRYs. The table used in this DTD is a 2200,
subset (with the exception of the ENTRY contents) of the CALS Table. For those tables
which are too complex to be represented in the CALS table structure, or when the table
is only available in illustration form, the contents of the table can be replaced with a
single graphic.
Tag or TEI)
2200 ML namest Attribute Defines the name of the column as defined with
colname, at which a spanspec definition or entry is to
begin.
Usages:
2200 ML table Element This tag identifies a structured table composed
(ultimately) of ENTRYs. The table used in this DTD is a
subset (with the exception of the ENTRY contents) of
the CALS Table. For those tables which are too complex
to be represented in the CALS table structure, or when
the table is only available in illustration form, the
contents of the table can be replaced with a single
graphic.
Usages:
2200 ML tbody Element Identifies the body (Table Body) of the information in a
table group.
Usages:
2200 ML tfoot Element Identifies the footer information (Table Footer) in a
table, displayed after the tbody and also at the bottom
of any tbody rows before a physical break.
Usages:
2200 ML tgroup Element Identifies a grouping of elements (Table Group) which
form a single logical table within a TABLE element.
Usages:
2200 ML thead Element Identifies the header information in a Table Body
Section.
Usages:
2200 ML tblitem Entity Used to include those elements which may appear
directly in a table cell as well as within a paragraph.
Usages:
DTD cpm, teman
2200 ML tabstyle Attribute Specifies a unique table style. Style matches to set
description per manual. It is based on CALS III.
Usages:
2200 ML colname Attribute Allows a specific column definition to be named. This
name is then used by the NAMEST and NAMEND
attributes to further define the appearance of the
table.
Usages:
2200 ML colnum Attribute The number of the displayed column counted from the
left.
Usages:
2200 ML colsep Attribute Logical indicator as to whether visible separators (i.e.
vertical lines) are intended to be displayed both sides
of a specific column or all columns in a table (Column
Separator). The default for the whole table is given at
the TABLE element. The value given at lower levels
supersedes that given at higher levels for that element
and its contained elements only.
Usages:
2200 ML colspec Attribute specify the intended presentation of a column.
2200 ML colspec Element specify the intended presentation of a column.
Usages:
2200 ML colwidth Attribute Gives the intended width of the column in terms of
column units (see COLS attribute).
Usages:
2200 ML cols Attribute The number of columns that are defined for that table
(see the colspec element). NOTE: because of the
spanning capabilities of columns this value may not be
that same as the apparent maximum number of
columns in any single row.
Usages:
2200 ML entry Element The basic component of a cellular table (TABLE). Each
ENTRY appears in one of the rows (ROW) of the table.
An ENTRY is a logical element which can contain
several lines (presentation is not forced in the SGML
text).
Usages:
2200 ML formal Attribute Specifies whether TABDAT or TABLE is formal or
informal. Formal is numbered (e.g. Table 801) and
informal is not numbered.
Permitted Value List: formal

Usages:
DTD cpm, em, teman
2200 ML frame Attribute Describes position of border siderules, as well as the
required top and bottom rules. Default="all".
Permitted Value List: frame

Usages:
2200 ML spanname Attribute Allows a specific span definition to be named. This
name may then be called in by the entry element to
further define the appearance of the table.
Usages:
2200 ML spanspec Element This tag is a placeholder element for attributes to
specify the intended presentation of a row.
Usages:
2200 ML row Element Used to define a set of cells (entry elements) which
together form a single logical line in the table. A logical
line may span more than one physical line depending
on the contents of each cell and the defined size of the
cells in the row.
Usages:
2200 ML valign Attribute Text vertical positioning within the entries. Declared
Value= top, middle (vertically centered), or bottom.
Default="top".
Permitted Value List: valign

Usages:
2200 ML align Attribute Indicates the intended 'text justification' of all the
contents of an element.
Permitted Value List: align

Usages:
2200 ML charoff Attribute For align="char", percent of the current width to the
left of the (left edge of) character. Default ="50".
Usages:
2200 ML char Attribute If align="char", the value is the single alignment
character on which the first to occur of this character
in the entry is aligned. If that character does not occur
in the entry, the entry aligns to the right of that
character offset. Default ="".
Usages:
2200 ML morerows Attribute Number of additional rows in a vertical straddle.
Usages:
2200 ML rowsep Attribute Logical indicator as to whether visible separators (i.e.

horizontal lines) are intended to be displayed above
and below a specific row or all rows in a TABLE. The
default for the whole table is given at the TABLE
element. The value given at lower levels supersedes
that given at higher levels for that element and its
contained elements only. NUMBER : 0 = no separators,
1 = separators
Usages:
2200 ML nameend Attribute Defines the name of the column as defined with
stop.
Usages:
2200 ML namest Attribute Defines the name of the column as defined with
begin.
Usages:
2200 ML rotate Attribute Content is either in the orientation of the table (value
is one or more zeros) or 90 degrees counter-clockwise
to table orientation (value is other than zeros).
Usages:
2200 ML orient Attribute Gives a logical indication of the intended orientation of
the table (i.e. in portrait or landscape format).
Permitted Value List: orient

Usages:
2200 ML pgwide Attribute If the value of PGWIDE is other than zeros, the table
runs across the page. If only zeros, the table runs
across just the (galley) width of the current column of
the page (regardless of orient). If the value is only
zeros, it has no meaning for orient=land.
Usages:
2200 ML entrycon Element Entry Container - A textual container that enables the
table cells identification.
The "entrycon" element is not part of the CALS table
Standard.
Usages:
DTD srm
2200 ML entconid Attribute Entry Container Identifier - The unique identifier of an
entry container.
The "entryconid" attribute is not part of the CALS table
standard.
Usages:
DTD srm
2300 XSD table Element
Usages:
DispatchProcedure,
PERMITTED VALUES List Name: align

center Center alignment
char Character alignment
justify Justify alignment
left Left alignment
right Right alignment
PERMITTED VALUES List Name: formal

F Formal
I Informal
PERMITTED VALUES List Name: frame

all Table borders on all sides
bottom Table border on bottom
none No table border
sides Table border on sides
top Table border on top
topbot Table border on top and bottom
PERMITTED VALUES List Name: orient

land Landscape (wide horizontal orientation)
port Portrait (tall vertical orientation)
PERMITTED VALUES List Name: valign

bottom Align bottom
middle Align middle
top Align top
Name Table Row Header Mod 2012
DEFINITIONS
Specific Indicates that the content of a table entry is the header for the row. 2300,
Tag or TEI)
2300 XSD rowHeader Attribute Data Type: xs:boolean
Usages:
DispatchProcedure,
Name Target of Reference Mod 2011
DEFINITIONS
Specific Used to provide information about the target of a link 2300,
Specific Unique identifier of an external object being referenced. 2300,
instances. Gives a unique, retrieval engine dependant code for the target or end point
for a cross reference. This can be used for explicit or implicit cross references.
Tag or TEI)
2200 ML targetid Attribute
Usages:
sds, teman, wm
2300 XSD targetRefId Attribute Data Type: xs:string
Usages:
GlossaryRepository,
NonNormalProcedure,
NormalProcedure, PmStatus,
2300 XSD target Element
Usages:
Name Target Title Mod 2011
ALSO KNOWN AS: Hotspot Title

Tooltip
DEFINITIONS
Specific Title of an external object being referenced. 2300,
Specific Used to provide a human-readable label for a link destination. 2300,
Specific Used to provide a content-dependent, human-readable label that can be displayed 2300,
when a cursor passes over a graphical object.
Tag or TEI)
2300 XSD hotspotTitle Attribute Definition and properties as per S1000D.
Usages:
2300 XSD targetTitle Attribute Definition and properties as per S1000D.
Usages:
2300 XSD targetRefTitle Attribute Data Type: xs:string
Usages:
GlossaryRepository,
NonNormalProcedure,
Name Technical Label Mod 2014
DEFINITIONS
Specific Used to identify significant data within a paragraph. 2300,
Tag or TEI)
2300 XSD techLabel Element
Usages:
LinkTargetRespository,
NonNormalProcedure,
Name Temporary Data Module Information Mod 2011
DEFINITIONS
Specific Used to indicate if a data module is a Temporary Data Module (TDM), and contains 2300,
information about the TDM.
Tag or TEI)
2300 XSD tdmInfo Element
Usages:
Schema DmStatus
Name Term Mod 2011
DEFINITIONS
Specific Identifies a term, acronym, or abbreviation. 2300,
Specific Identifies a term, symbol, or abbreviation. 2200,
Tag or TEI)
2200 ML sterm Element
Usages:
DTD faammel
2200 ML term Element
Usages:
DTD aipc, amm, cmm, eipc, faammel, fcom,
frmfim, mpd, sds, srm, wm
2300 XSD term Element
Usages:
Name Text Color Mod 2012
DEFINITIONS
Specific Specifies the color in which textual data should be displayed. 2300,
Tag or TEI)
2300 XSD color Attribute Use the CSS Color Module Level 3 standard.
Usages:
DispatchProcedure,
NonNormalProcedure,
Name Title Mod 2010
ALSO KNOWN AS: Service Bulletin Title

Manual Title
DEFINITIONS
Concept Brief title of the zonal analysis, is often based on the description of the zone covered by DM,
the analysis.
Specific A distinguishing name; the name of a document (e.g., Manual Title) or portion of a 2200, 2300,
document (e.g., Section Title)
Tag or TEI)
2200 ML sbtitle Element A descriptive label for a Service Bulletin. Used to aid in
the definition of an SB listed in the SBLIST in the
Manual Frontmatter.
Usages:
DTD amm, cmm, frmfim, sds, srm
2200 ML title Element
Usages:
sbi, sds, srm, teman, wm
ODM DM Title Attribute
Class Name: Zonal Analysis
ODM DM Title Attribute Data Type: Character (200)
Class Name: List

2300 XSD productRefNa Attribute Data Type: xs:string
me
Usages:
Name Triggered By Mod 2009
DEFINITIONS
Specific Indicates if an electronic message is the direct result of the flight crew action or not. 2300,
Tag or TEI)
2300 XSD triggeredBy Attribute
Permitted Value List: TriggeredByList
Usages:
Schema Annunciation
PERMITTED VALUES List Name: TriggeredByList

automatic
flightCrewAction
Name Triggering Conditions Mod 2009
DEFINITIONS
Specific Describes the conditions or events on an aircraft that may result in an electronic 2300,
annunciation.
Tag or TEI)
2300 XSD triggeringCon Element
ditions
Usages:
Schema Annunciation
Name Underline Mod 2009
DEFINITIONS
Specific Specifies whether or not textual data should be displayed in an underlined font. 2300,
Tag or TEI)
2300 XSD underline Attribute Data Type: xs:boolean
Usages:
Name Uniform Resource Identifier Mod 2013
ALSO KNOWN AS: URI
DEFINITIONS
Concept A string of characters to identif a computing name or resource. 2300,
Tag or TEI)
2300 XSD baseUri Attribute Provides the base URI for the exchange package
content. This allows use of relative addressing to
identify the locations of the resources in the exchange
package.
Data Type: xs:anyURI
Usages:
Name Unit of Measure Code Mod 2017
ALSO KNOWN AS: Unit of Measure
DEFINITIONS
Concept Specifies a type of count, measurement, container or form. 2300,
Concept The 2 character code for a unit of measure. Only applies to length, area, volume, DM,
weight, mass and miscellaneous general concepts like "piece", "packet" or "outfit"
which is defined as a collection of related items issued as a single item of supply.
Concept Used to define units of measure (ft = feet, cm = centimeters, lb = pounds, etc.). 2200,
Specific The unit of measure related to torque values. 2200,
Specific The specific unit of measure directly related to the Threshold, Interval or Limit for the 2200,
scheduled maintenance task presented.
Specific Specifies the type of count, measurement, container or form of the subject part or 300, 2000,
material.
Tag or TEI)
2000 MSG & File UNT Data Element Refer to Unit of Measure Clarification Text for a
nondefinitive Unit of Measure.
If not available, AIRS data base default is "EA".
Used in data set group Material Used Text (RMU) in
Warranty Claims (Chapter 14).
Applies to S and T files.
"* " denotes nondefinitive units.
Data Type: A
Min Length: 2
Max Length: 2
Cobol Picture: A(02)
Permitted Value List: Unit Of Measure Codes
Usages:
Chapter 1, 12, 2, 3, 4, 5, 7, 9
Command A1ADDPRT, A1CHANGE, A1QUOTES,
A1STOCKS, A1UPDATE, P1PDINQY,
P1UPDATE, R1CPOXMT, R1CUSSHP,
R1EXCXMT, R1INVXMT, R1QTNREQ,
R1QTNXMT, R1SPLSHP, R1TDNXMT,
S1BOOKED, S1NVOICE, S1ORDEXC,
S1PNSTAT, S1POSTAT, S1QUOTES,
S1SHIPPD, S1STOCKS
Record Type 02, 07, 12, 21, 29, 32
2200 ML unit Attribute
Permitted Value List: unit
Usages:
DTD aipc, amm, cpm, srm, teman, v4sheet,
wm
2200 ML unitcode Attribute
Usages:
DTD mpd, msg3
2000 XSD UNT Attribute Data Type: xs:string

Min Length: 2
Max Length: 2

Usages:
Chapter 11, 13, 15, 16, 17, 3, 4
Schema AircraftStatusChange,
ATA_DSE_Logbook,
ATA_MetricsPartsDetail,
ATA_PartCertificationForm,
ATA_SparesInvoice, ATA_SparesOrder,
ATA_SparesOrderBookback,
ATA_SparesOrderExc,
ATA_SparesOrderStatusResponse,
ATA_SparesQuoteFinal,
ATA_SparesQuoteRequest,
ATA_SparesStockResponse,
ATA_SparesSupplierShipNotice,
DeliveredAircraftTransferPartList
2000 TEI UNT Data Element Data Type: String
Min Length: 2
Max Length: 2

Usages:
Chapter 9
2300 XSD unit Attribute See Spec 2300 Appendix A-1 for permitted values.
Usages:
GlossaryRepository,
NonNormalProcedure,
PERMITTED VALUES List Name: unit

cm Centimeters
ft Feet
in Inches
lb-ft Pound Foot
lb-in Pound Inch
m Meters
m.daN Meter deca Newton
m.N Meter Newton
mm Millimeters
PERMITTED VALUES List Name: Unit Of Measure Codes

3F Kilograms per Liter
AA Two Hundred, Fifty -- 250 each of an item of supply.
AM Ampoule* -- A small glass or plastic tube sealed by fusion after filling.
AT Assortment -- A collection of various items falling into a common category or class and
packaged as a small unit constituting a single item of supply.
AX Twenty -- 20 each of an item of supply.
AY Assembly -- A collection of parts assembled to form a complete unit constituting a single
item of supply.
BA Bale* -- A shaped unit of compressed material bound with cord or metal ties and usually
wrapped, e.g., paper and cloth rags.
BB Bobbin* -- A cylindrical shaped reel or spool containing thread, yarn, wire.
BC Block* -- A piece of material such as wood, stone or metal usually with one or more
planed faces.
BF Board Foot -- A unit of measure for lumber equal to the volume of a board 12" X 12" X 1"
(144 cubic inches, or 2.360 cubic decimeters).
BG Bag* -- A flexible container of various sizes and shapes fabricated from materials as
paper, plastic or textiles. Includes "sack" and "pouch".
BK Book* -- A booklike package, as labels or tickets, fastened together along one edge,
usually between protective covers.
BL Barrel* -- A cylindrical container, metal or wood, usually with sides that bulge outward
and flat ends or heads of equal diameter.
Drum* -- A cylindrical container designed as an exterior pack for storing and shipping
bulk materials, e.g., fuels, chemicals, powders.
Keg* -- A small barrel shaped container.
BO Bolt* -- A flat fold of fabric having a stiff paper board core.
BR Bar* -- A solid piece or block of material having its length greater than its other
dimensions, e.g., solder. Not applicable to items as soap, beeswax, buffing compound.
BU Bushel -- A unit of dry measure equal to eight (8) gallons.
BX Box* -- A rigid three dimensional container of varying size and material. Includes "tray"
and "crate".
CA Can* -- A rigid receptacle made of fiber, metal, plastic. May be cylindrical or any
numbwe of shapes. Includes "cannister".
Pail -- A cylindrical container with a handle, as a bucket.
Tin* -- A box-like metal container with a flap or lid cover.
CB Carboy* -- A large, heavy duty, bottle-type container used for transportation and storage
of liquids. Usually encased in a rigid protective outer container for shipment.
CC Cubic Centimeter -- A metric unit of cubic measure equal to 0.000001 cubic meter, 1.0
milliliter or 0.061 cubic inch.
CE Degrees Celsius
CF Cubic Foot -- A unit of cubic measure equal to 0.037 cubic yard or 0.028 cubic meters.
CG Centigram -- A unit of metric weight equal to 0.01 gram or 0.000035 ounce.
CI Cubic Inch -- A unit of cubic measure equal to 0.00058 cubic feet or 16.387 cubic
centimeters.
CK Cake* -- A block of compacted or congealed matter. Applicable to such items as soap,
buffing compound.
CL Cylinder* -- A rigid, cylindrical, metal container designed for transportation and storage
of compressed gasses.
CM Centimeters -- A unit of metric length equal to 0.01 meter or 0.39 inch.
CN Carton* -- A container, usually of fibreboard or pasteboard, with fixed or collapsible
joints and self-locking or tuck-in flaps.
CO Container* -- A general term for a receptacle or covering for shipment of goods.
CP Capsule* -- A compact metallic or plastic container for liquids or solids.
CR Card* -- A flat piece of thick paper or pasteboard to which various items can be attached
or displayed.
CS Case* -- A container designed to hold one or more specific items in a fixed position by
virtue of conforming dimensions or attachments.
CT Hundred Feet -- A unit of linear measurement equal to 33.333 yards or 30.48 meters.
CW Hundred Pounds -- A unit of avoirdupois weight equal to 45.359 kilograms.
CY Cubic Yard -- Unit of cubic measure equal to 27 cubic feet or 0.765 cubic meter.
DC Cubic Decimeter -- A metric unit of cubic measure equal to 1.0 liter or 61.02 cubic inches.
DL Deciliter -- A unit of metric capacity equal to 0.1 liter, 100 cubic centimeters or 6.1 cubic
inches.
DM Decimeter -- A unit of metric length equal to 0.1 meter or 3.94 inches.
DR Dram -- A unit of avoirdupois weight equal to 1/16 (.0625) ounce or 1.771 grams.
DZ Dozen -- Twelve each of an item of supply.
EA Each -- One unit of an item of supply.
FA Degrees Fahrenheit
FM Fathom -- A unit of length equal to 6.0 feet or 1.829 meters.
FO Fluidounce (U.S.) -- A liquid unit of measure equal to 1/16 (.0625) pint (U.S.), 29.573
milliliters or 29.573 cubic centimeters.
FT Foot/Foot Run -- A unit of linear measurement equal to 12 inches or (Linear Foot)
30.480 centimeters.
FY Fifty -- Fifty (50) each of an item of supply.
FZ Fluidounce (Imperial) -- A liquid unit of measure equal to 1/20 (.05) pint (Imperial),
28.416 cubic centimeters or 28.416 milliliters.
GC Gill (Imperial) -- A unit of liquid or dry measure equal to 5 fluidounces, 8.669 cubic inches
or 142.066 cubic centimeters.
GE Pounds per Gallon
GI Gallon (Imperial) -- A unit of liquid or dry measure equal to 277.420 cubic inches, 4.545
liters or 1.201 gallons (U.S.).
GL Gallon (U.S.) -- A unit of liquid or dry measure equal to 231 cubic inches, 3.785 liters or
0.833 gallon (Imperial).
GM Gram -- A small unit of metric mass and weight equal to 0.000001 metric ton or 0.0353
ounce.
GN Grain -- A small unit of weight equal to 1/480 (.002083) troy ounce, or 0.0648 gram.
GP Group -- A collection of related items issued as a single unit of supply, e.g., test set group.
GR Gross -- 144 each of a unit of supply.

HC Hundred Cubic Meters -- A unit of metric volume equal to 131.0 cubic yards.
HG Hectogram -- A unit of metric mass and weight equal to 100 grams or 3.527 ounces.
HK Hundred Kilogram (Quintal) -- A unit of metric mass and weight equal to 0.1 metric ton
or 220.46 pounds.
HL Hundred Liters (Hectoliter) -- A unit of metric capacity equal to 3.53 cubic feet.
HM Hundred Meters (Hectometer) -- A unit of metric length equal to 109.36 yards or 0.062
mile.
HP Half Pint (U.S.) -- A unit of liquid measure equal to 14.4375 cubic inches or 0.2365
milliliter.
HS Hundred Square Feet -- A unit of area measurement equal to 11.1 square yards or 9.3
square meters.
HU Hundred -- 100 each of an item of supply.
HW Hundred Weight -- A unit of avoirdupois weight equal to 100 pounds or 45.359 kilograms
(short hundred weight); or 112 pounds or 50.802 kilograms (long hundred weight).
HY Hundred Yards -- A unit of linear measurement equal to 91.4 meters.

IN Inch -- A unit of linear measurement equal to 2.540 centimeters.
IU Unit* -- A standard or basic quantity into which an item of supply is dispensed or
distributed.
JR Jar* -- A rigid container having a wide mouth and often no neck, typically made of
earthen ware or glass.
Bottle* -- A glass, plastic or earthenware container of varying size, shape and finish with
a closure for retention of contents. excludes jars, ampoules, vials and carboys.
KC Kilograms per Cubic Meter
KG Kilogram -- A metric unit of weight equal to 1000 grams or 2.2046 pounds.
KM Kilometer -- A metric unit of length equal to 1000 meters or 0.62 mile.
KP Cop* -- A cylindrical or conical mass of thread, yarn, cable wound on a quill or tube.
KT Kit -- A collection of related items issued as a single unit of supply, such as tools,
instruments, repair parts, instruction sheets and often supplies typically carried in a box
or bag. Also includes selected collections of equipment components, tools and/or
materials for the repair, overhaul or modification of equipment.
LB Pound -- A unit a avoirdupois weight equal to 16 ounces or 0.453 kilogram.
LG Length* -- A unit of fixed or specific linear measurement.
LI Liter -- A unit of metric capacity equal to 1.0 cubic decimeter, 61.02 cubic inches, 1.06
quarts (U.S.) or 0.88 quart (Imperial).
LM Linear Meter -- A term used for measuring preformed piping, insulation.
LT Lot* -- A number of units of an item of supply offered as a single item.
MC Cubic Meter -- A metric unit of cubic measure equal to 1.0 kiloliter or 1.31 cubic yards.
ME Meter -- A metric unit of linear measurement equal to 39.37 inches.
MF Thousand Board Feet -- A unit of measure for lumber equal to the volume of 1000 board
foot units (12" X 12" X 1").
MG Milligram -- A metric unit of mass and weight equal to .001 gram.
ML Milliliter -- A metric unit of capacity equal to .001 liter, 0.061 cubic inch or 1 cubic
centimeter.
MM Millimeter -- A metric unit of length equal to .001 meter or 0.04 inch.

MN Square Millimeter -- A metric unit of area measurement equal to 0.000001 square meter
or 0.0016 square inch.
MT Thousand Feet -- A unit of linear measurement equal to 333.33 yards or 304.8 meters.
MX Thousand Cubic Feet -- A unit of volume equal to 37.04 cubic yards or 765 cubic meters.
OT Outfit -- A collection of related items issued as a single item of supply.
OZ Ounce -- A unit a avoirdupois weight equal to 1/16 (.0625) pound or 28.349 grams.
PB Pint (Imperial) -- A measure of liquid capacity equal to 1/8 (.125) gallon (Imperial),
34.678 cubic inches, 0.568 liter or 1.201 pints (U.S.).
PC Piece* -- A portion or quantity of an item, often a specific length.
PD Pad* -- Multiple sheets of paper that are stacked together and fastened at one end by
sealing.
PE Peck -- A unit of dry measure equal to 2 gallons.
PK Bundle* -- A quantity of an item tied together without compression.
Pack* -- A parcel or quantity of an item supplied as a wrapped or tied unit.
Package* -- A quantity of an item supplied in a protective wrapping.
PM Plate -- A flat piece of square or rectangular shaped metal of uniform thickness usually
1/4 inch or more.
PR Pair -- Two like, corresponding items as gloves, shoes, bearings; or single items
fabricated of two corresponding parts as shears, goggles, trousers.
PT Pint (U.S.) -- A measure of liquid capacity equal to 1/8 (.125) gallon (U.S.), 28.875 cubic
inches, 0.473 liter or 0.833 pint (Imperial).
PZ Packet* -- A container used for subsistence items.
QI Quart (Imperial) -- A unit of liquid capacity equal to 1/4 (.25) gallon (Imperial), 69.355
cubic inches, 1.136 liters or 1.201 quart (U.S.).
QK Quarter Kilogram -- A unit of metric weight equal to 250 grams.
QR Quire -- A measure of 24 sheets of paper.
QT Quart (U.S.) -- A unit of liquid capacity equal to 1/4 (.25) gallon (U.S.), 57.75 cubic inches,
0.946 liter or 0.833 quart (Imperial).
RA Ration* -- Amount of food or supplies allotted to an individual, usually for one day.
RL Roll* -- A cylindrical configuration of flexible material which has been rolled on itself as
textiles, tape, paper, film and may utilize a core with or without flanges.
Spool* -- A cylindrical form with a flange or rim at each end and an axial hole for a pin or
spindle on which material as thread or wire is wound.
Coil* -- An arrangement of material as wire, rope and tubing wound in a circular
shape.
Cone* -- A cone-shaped mass of material wound on itself as twine or thread wound on a
conical core.
RM Ream -- A quantity of paper varying from 480 to 516 sheets, depending upon grade.
SC Square Centimeter -- A metric unit of area measurement equal to 0.0001 square meter
or 0.155 square inch.
SD Square Decimeter -- A metric unit of area measurement equal to 0.01 square meter or
15.5 square inches.
SF Square Foot/Super Foot -- A unit of area measurement equal to 144 square inches or
0.093 square meter.
SH Sheet -- A flat piece of rectangular shaped material of uniform thickness that is very thin
in relation to its length and width, such as paper, metal and plywood.
SI Square Inch -- A unit of area measurement equal to 0.00694 square feet or 6.4516
square centimeters.
SK Stick* -- Material in a relatively long, slendor and often cylindrical form for ease of
application, e.g., abrasives.
SM Square Meter -- A metric unit of area measurement equal to 10.76 square feet.
SN Skein -- A loop of yarn, 120 yards in length, usually wound on a circular core.
SO Shot -- A unit of linear measure equal to 15 fathoms or 90 feet, usually applied to anchor
chain.
SP Strip* -- A relatively narrow, flat length of material, uniform in width, such as paper,
wood and metal.
ST Set -- A collection of matched or related items issued as a single item of supply, i.e., tool
set, matched set.
SY Square Yard -- A unit of area measurement equal to 1296 square inches, 9 square feet or
0.836 square meter.
TE Ten -- 10 each of an item of supply.
TH Thousand -- 1000 each of an item of supply.
TK Ton, Metric (Thousand Kilograms) -- A metric unit of weight equal to 2204.6 pounds.
TL Thousand Liter (Kiloliter) -- A metric unit of capacity equal to 1 cubic meter or 1.31 cubic
yards.
TN Ton, Short -- A unit of avoirdupois weight equal to 2000 pounds or 0.907 metric ton.
TO Troy Ounce -- A unit of troy weight, usually applied to precious metals, equal to 1/12
(.0833) troy pound or 0.373 kilogram.
TT Tablet* -- A compressed or molded block of solid material; a collection of sheet paper
glued together at one edge.
TU Tube* -- A squeeze-type container used in packaging commodities as
adhesives,toothpaste, pharmaceuticals.
TX Ton, Long -- A unit of avoirdupois weight equal to 2240 pounds or 1.016 metric tons.
VC Five Hundred -- Five hundred (500) each of an item of supply.
VI Vial* -- A small glass container, tubular in shape (generally less than one inch in
diameter) having a flat bottom and variety of neck shapes.
YD Yard -- A unit of length equal to 3 feet or 0.914 meter.
ZV Syphon* -- An aerated container from which liquid is forced by gas pressure.
Name Unnumbered List Mod 2015
ALSO KNOWN AS: Unordered List

Random List
List (Unnumbered)
DEFINITIONS
Concept A set of items of text in which the sequence of the items is not significant. 2300,
Concept A set of non-ordered items of text. 2200,
Name Unnumbered List Mod 2015
Tag or TEI)
2200 ML unlist Element
Usages:
sds, srm, teman, wm
2200 ML unlitem Element An unnumbered list item within an unnumbered list
Usages:
sds, srm, teman, wm
2200 ML bulltype Attribute An attribute of the un-numbered list which indicates
the type of dingbat (symbol) to be used to 'bullet' the
list items. The default value allows the receiving
system to assign the dingbat. See the ATA-TEXT-
TECHREQ for defined dingbat types.
Permitted Value List: Bullet Type

Usages:
sds, srm, teman, wm
2300 XSD randList Element
Usages:
PERMITTED VALUES List Name: Bullet Type

ASTERISK The ASCII character "*"
DELTA A triangular greek character
DIAMOND A rhombus-shaped figure usually oriented with the long diagonal vertical
MDASH A long dash (the width of the capital letter M)
NDASH A long dash (the width of the capital letter N)
NONE No bullet
SQUARE A rectangular character with four equal length sides
SYSTEM Yes A system specific character
Name Value Pattern Mod 2011
DEFINITIONS
Specific A regular expression for a constraint on a locally defined value. 2300,
Tag or TEI)
2300 XSD valuePattern Attribute Data Type: xs:string
Usages:
Schema ApplicCrossRefTable,
CondCrossRefTable, QualifierRepository
Name Volume Number Mod 2010
DEFINITIONS
Specific The volume number of a publication module. 2300,
Specific Identification number of a volume. 2200,
Tag or TEI)
2200 ML volnbr Attribute
Usages:
DTD fcom
2300 XSD pmVolume Attribute Set to "00" if only one volume.
Usages:
Schema Pm, PmStatus
Name Warning Mod 2014
DEFINITIONS
Specific Call attention to the use of materials, processes, methods, procedures, or limits, which 2200, 2300,
must be followed precisely to avoid injury to persons.
Tag or TEI)
2200 ML warning Element Warning - Used to give notice to or call one's attention
to beforehand especially of danger (such as a warning
to a Flight Crew person or a warning to a mechanic
before performing a dangerous task).
Usages:
mpd, sb, sds, srm, teman, wm
2300 XSD warning Element
Usages:
2300 XSD warningProc Element Procedural content that may result in personal injury
or loss of life if not followed.
Usages:

ATA Spec2300 2017.1 FINAL

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ATA Spec2300 2017.1 FINAL

Uploaded by

Copyright:

Available Formats

ATA Spec 2300

Data Exchange Standard for

2300 Flight Operations

AIR TRANSPORT ASSOCIATION OF AMERICA, INC. ("ATA") PRODUCT LICENSE

IMPORTANT NOTICE: This document is intended to be used only in an electronic

For Additional Information

For Technical Information and Change Submissions

Appendix 1 Added Units of Measure to support Rotorcraft requirements.

• A standard architecture that is data-centric as opposed to document-centric, and relies

• Information from multiple manufacturers is received by operators in a single, consistent

• Facilitate identification of changes to the data.

• Facilitate modification or re-authoring of information.

• Separate presentation of information from the content of the information, enabling

• Enable identification of information based on its applicability to specific aircraft or

1-2. Intended Audience

• Aircraft configuration and data managers

1-3. Scope Of This Document

1-4. Anticipated Benefits

1-4-2. Use of Structured Information

• Information can be released either as a complete package or as an interim release with

Figure 1-1 Electronic Data Framework

Data in Internet Operator Content

Manufacturer B Operator Server

Paper Workstation Smartphone EFB

1-5. XML Implementation

1-6. Flight Operations Markup Language

1-7. Tailoring Spec 2300 for a Specific Project

2-1. Data Management Concepts

2-2. Data module types

2-3. Data Module Identification

• Optional data module code extension

Additionally, issue information is provided.

2-3-1. Data Module Code

Component Required Range Minimum Maximum

System Difference Required alphanumeric 1 4

Standard Required Refer to [Section 5-2 ATA 6 8

Disassembly Code Required alphanumeric 2 2

Information Code Required Refer to [Section 5-3 Data 3 3

Information Code Required "A" 1 1

Item Location Code Required "A" or "T" 1 1

Total Required Required - 17 36

Learn Code (LC) Optional "T00", "T01", "T02", 3 3

Learn Event Code Optional and "C" 1 1

Total without Optional - 21 40

Dispatch Extension Optional and alphanumeric 10 10

Total with Dispatch Optional - 31 50

Figure 2-1 Data Module Code structure

DMC 17+10 Characters (minimum)

DMC 40+10 Characters (maximum)

YYYYYYYYYYYYYY - YYYY – YY-YY-YYYY - YY YYY - YYY Y - Y – YYY Y - YYY-YYYY-YYY

Model identification code

1.1. Model Identification Code

1.4. Disassembly Code

2-3-3. Data module code extension

2-4. Temporary Data Modules

2-5. Data module content and metadata organization

2-5-2. Content fragment

2-5-3. Metadata: DM Status fragment

• Data for some business concepts.

• Applicability annotations. Refer to [Section 3-3-1, Applicability management].

2-5-4. DM Status and DM Content association

• The DM content issue information for both XML fragments is identical