GUIDELINES FOR ELECTRONIC

QUALIFICATION TEST GUIDE

ARINC REPORT 436-1

PUBLISHED: September 20, 2010

AN DOCUMENT
Prepared by FSEMC
Published by
AERONAUTICAL RADIO, INC.
2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401-7435
 DISCLAIMER

THIS DOCUMENT IS BASED ON MATERIAL SUBMITTED BY VARIOUS PARTICIPANTS

DURING THE DRAFTING PROCESS. NEITHER AEEC, AMC, FSEMC NOR ARINC HAS
MADE ANY DETERMINATION WHETHER THESE MATERIALS COULD BE SUBJECT TO
VALID CLAI MS OF P ATENT, COPYRIG HT OR OT HER PRO PRIETARY RIGHTS BY
THIRD PARTIES, A ND NO RE PRESENTATION OR WARRANTY, E XPRESS O R
IMPLIED, IS MADE IN THIS REGARD.

ARINC I NDUSTRY ACT IVITIES US ES RE ASONABLE E FFORTS TO DEVELOP A ND

MAINTAIN THESE DOCUMENTS. HOWEV ER, NO CERTIFICATION OR WARRANTY IS
MADE AS TO THE TECHNICAL ACCURACY OR SUFFICIENCY OF THE DOCUMENTS,
THE ADEQ UACY, MERCHANT ABILITY, FITNESS FOR INT ENDED PURPOSE OR
SAFETY OF A NY PRODUCTS, CO MPONENTS, OR S YSTEMS DE SIGNED, T ESTED,
RATED, I NSTALLED O R OP ERATED IN A CCORDANCE WITH ANY ASPECT OF T HIS
DOCUMENT OR T HE ABS ENCE OF RI SK OR HAZA RD AS SOCIATED WIT H SUCH
PRODUCTS, COMPO NENTS, OR S YSTEMS. T HE USER OF T HIS DO CUMENT
ACKNOWLEDGES THAT IT SHALL BE SOLELY RESPONSIBLE FOR ANY LOSS, CLAIM
OR DAMAGE THAT IT MAY INCUR IN CONNECTION WITH ITS USE OF OR RELIANCE
ON T HIS DOCUMENT, AN D S HALL HOLD A RINC, AEEC, AM C, F SEMC A ND A NY
PARTY T HAT PA RTICIPATED I N T HE DRAFTING OF THE DOCUM ENT HA RMLESS
AGAINST ANY CLAIM ARISING FROM ITS USE OF THE STANDARD.

THE US E I N T HIS DOCUMENT OF AN Y T ERM, S UCH AS S HALL O R MUST, IS NOT

INTENDED T O AFFECT THE ST ATUS OF T HIS DOCUME NT AS A VOLUNT ARY
STANDARD OR IN ANY WAY T O MODI FY T HE ABOVE DIS CLAIMER. NOT HING
HEREIN SHA LL BE DE EMED T O REQUIRE A NY P ROVIDER OF EQUIP MENT TO
INCORPORATE A NY ELEMENT OF T HIS S TANDARD IN I TS PRODUCT . HOW EVER,
VENDORS W HICH REPRESENT T HAT T HEIR P RODUCTS A RE COMPLI ANT WI TH
THIS ST ANDARD SHALL B E DEE MED A LSO T O HAVE REPRESENTED T HAT THEIR
PRODUCTS CONTAIN OR CONFORM TO THE FEATURES THAT ARE DES CRIBED AS
MUST OR SHALL IN THE STANDARD.

ANY USE O F OR RE LIANCE ON T HIS DO CUMENT SHALL CONSTITUTE A N

ACCEPTANCE THEREOF “AS IS” AND BE SUBJECT TO THIS DISCLAIMER.

This document is published information as defined by 15 CFR Section 734.7 of the Export Administration Regulations (EAR). As publicly available technology under 15 CFR 74.3(b)(3), it is not
subject to the EAR and does not have an ECCN. It may be exported without an export license.
 ©2010 BY
AERONAUTICAL RADIO, INC.
2551 RIVA ROAD ANNAPOLIS, MARYLAND
21401-7435 USA

ARINC REPORT 436-1

GUIDELINES FOR ELECTRONIC QUALIFICATION TEST GUIDE

Published: September 20, 2010

Prepared by the FSEMC

Specification 436 Adopted by the FSEMC Steering Committee April 1, 2005
Summary of Document Supplements
Supplement Adoption Date Published
Specification 436-1 July 21, 2010 September 20, 2010
A description of the changes introduced by each supplement is included at the end of this document.
 FOREWORD

Aeronautical Radio, Inc., the FSEMC, and ARINC Standards

ARINC organizes aviation industry committees and participates in related industry activities that
benefit aviation at large by providing technical leadership and guidance. These activities directly
support aviation industry goals: promote safety, efficiency, regularity, and cost-effectiveness in
aircraft operations.

ARINC Industry Activities organizes and provides the secretariat for international aviation
organizations (AEEC, AMC, FSEMC) which coordinate the work of aviation industry technical
professionals and lead the development of technical standards for airborne electronic
equipment, aircraft maintenance equipment and practices and flight simulator equipment and
used in commercial, military, and business aviation. The AEEC, AMC, and FSEMC develop
consensus-based, voluntary standards that are published by ARINC and are known as ARINC
Standards. The use of ARINC Standards results in substantial benefits to the aviation industry
by allowing avionics interchangeability and commonality and reducing avionics cost by
promoting competition.

There are three classes of ARINC Standards:

a) ARINC Characteristics – Define the form, fit, function, and interfaces of avionics and
other airline electronic equipment. ARINC Characteristics indicate to prospective
manufacturers of airline electronic equipment the considered and coordinated
opinion of the airline technical community concerning the requisites of new
equipment including standardized physical and electrical characteristics to foster
interchangeability and competition.

b) ARINC Specifications – Are principally used to define either the physical packaging
or mounting of avionics equipment, data communication standards, or a high-level
computer language.

c) ARINC Reports – Provide guidelines or general information found by the airlines to

be good practices, often related to avionics maintenance and support.

The release of an ARINC Standard does not obligate any organization or ARINC to purchase
equipment so described, nor does it establish or indicate recognition or the existence of an
operational requirement for such equipment, nor does it constitute endorsement of any
manufacturer’s product designed or built to meet the ARINC Standard.

In order to facilitate the continuous product improvement of this ARINC Standard, two items are
included in the back of this volume:

An Errata Report solicits any corrections to the text or diagrams in this ARINC Standard.

An ARINC IA Project Initiation/Modification (APIM) form solicits any recommendations for

addition of substantive material to this volume which would be the subject of a new Supplement.

ii
 ARINC REPORT 436
TABLE OF CONTENTS

1.0 INTRODUCTION ...........................................................................................................1

1.1 Purpose/Goals ...............................................................................................................1
1.2 Background....................................................................................................................1
1.3 Legacy Systems.............................................................................................................1
1.4 Benefits of an eQTG System .........................................................................................2
1.5 Related Documents .......................................................................................................2
2.0 EQTG REQUIREMENTS ...............................................................................................3
2.1 Content .......................................................................................................................3
2.1.1 Regulatory Compliance .............................................................................................3
2.1.2 Identification of eQTG ...............................................................................................3
2.1.3 Supporting Material ...................................................................................................3
2.1.4 Source Data ..............................................................................................................3
2.1.5 Graphical Format.......................................................................................................3
2.1.6 Test Information Accessibility Requirements ............................................................4
2.1.7 Test Analysis .............................................................................................................4
2.1.8 Security .....................................................................................................................5
2.1.9 Document Archiving ..................................................................................................5
2.1.10 Configuration Control ................................................................................................5
2.1.11 MeQTG Update .........................................................................................................5
2.1.12 Hyperlinks and Bookmarks........................................................................................5
2.2 Viewing the eQTG..........................................................................................................5
2.2.1 Provision of Viewer....................................................................................................5
2.2.2 Encapsulation and Self-Containment ........................................................................6
2.2.3 Document Navigation ................................................................................................6
2.2.4 Viewer Operation.......................................................................................................6
2.2.5 Zoom .......................................................................................................................6
2.2.6 Printing ......................................................................................................................6
2.3 Annotation of Individual Copy ........................................................................................6
2.4 Annotation of Subsequent Releases..............................................................................7
2.5 Optional eQTG Features and Enhancements................................................................7
3.0 PROCESS FOR INITIAL AND RECURRENT QUALIFICATION USING AN EQTG .....8
3.1 Introduction ....................................................................................................................8
3.2 Items Required for Initial QTG Submittal .......................................................................8
3.3 eQTG Review Comments ..............................................................................................9
3.4 Initial Qualification..........................................................................................................9
3.5 Recurrent Qualification ..................................................................................................9
3.6 MeQTG Update..............................................................................................................9
4.0 SECURITY, ACCESS, AND PRIVACY GUIDELINES .................................................10
4.1 Introduction ..................................................................................................................10
4.2 Security .....................................................................................................................10
4.3 Access .....................................................................................................................10
4.4 Privacy .....................................................................................................................10

APPENDICIES
APPENDIX A GLOSSARY .................................................................................................11

iii
 ARINC REPORT 436 – Page 1

1.0 INTRODUCTION

1.0 INTRODUCTION

1.1 Purpose/Goals

The purpose of ARINC Report 436 is to provide Flight Simulation Training Device
(FSTD) users, suppliers and regulatory authorities a set of guidelines for Electronic
Qualification Test Guide (eQTG) systems. This document is intended to be
supplementary to existing regulatory authority requirements. This document is not
designed to direct the use of certain technologies or platforms, but to outline the
minimum requirements of an eQTG system. The choice of the technology used to
meet these requirements is left to the system’s designers and users.

A list of definitions and terms used throughout this document is contained in

Appendix A.

1.2 Background

The modern FSTD requires numerous binders to store its complete Qualification
Test Guide (QTG). An electronic system is becoming a regulatory requirement
which will eliminate the need for storing large volumes of paper and facilitate the
transfer and analysis of data. As both the number of FSTDs and the volume of
required qualification tests have grown, FSTD users and manufacturers have
developed electronic systems for storing, reviewing and analyzing FSTD test guide
data.

The production of the QTG, particularly the collation and indexing of the document’s
many parts, can be automated beyond the limits of that possible for a paper
document. With an automatically generated eQTG, the test results that constitute
the eQTG document could be automatically inspected to ensure that only the latest
results have been used, and that any necessary supplementary data has also been
included into the document.

This collation and checking task requires considerable effort, and should not be
underestimated, as a typical QTG may be the assembly of 500 separate articles.
Any automation in the production of the eQTG will be of great benefit during the
initial build and approval of the device, but the greatest benefit of automation will be
during the recurrent evaluations during the life of the device.

During the introduction of the eQTG, some operators and regulators may require a
traditional paper copy of the QTG, particularly during the initial approval. Clearly, it
would be impractical to have to produce two unique formats, hardcopy and
electronic, therefore the eQTG should also be the source of the hardcopy QTG. This
is an important consideration as it effectively limits the level of electronic interaction
that can be incorporated at this stage.

As more of these systems are developed, with different features and interfaces, the
need for an industry standard has emerged.

1.3 Legacy Systems

Subject to regulatory requirements, an electronic representation of the Master QTG

(MQTG) may be required. For legacy systems incapable of producing an eQTG, this
ARINC REPORT 436 – Page 2

1.0 INTRODUCTION

may be satisfied by scanning the existing paper MQTG producing an Electronic

MQTG (MeQTC). The resolution and readability of the electronic representation
should conform to Section 2.2.6.

The electronic representation should be distributed in accordance with Section 3.2.

1.4 Benefits of an eQTG System

 Archiving
 Cost, time and space savings
 Ease of data review
 Portability
 Quick access to historical results
 Standardization
 Automated status reporting
1.5 Related Documents

In all instances of references, it is intended that the latest versions of each applies.

14 CFR Part 60: Flight Simulation Training Device Initial and Continuing
Qualification and Use

Joint Aviation Requirements JAR-STD 1A: Aeroplane Flight FSTDs Aeroplane

Flight Simulators (superseded by JAR-FSTD A)

Joint Aviation Requirements JAR-FSTD 1A: Aeroplane Flight

FSTDsSimulation Training Devices

ICAO 9625: Manual of Criteria for the Qualification of Flight Simulators

Bateman, Ian. The Electronically Published QTG. RAeS Flight Simulation

Conference Proceedings and Publications. 2003.

Aeroplane Flight Simulation Training Device Evaluation Handbook, Volume I,

Fourth Edition, 2009
 ARINC REPORT 436 – Page 3

2.0 EQTG REQUIREMENTS

2.0 EQTG REQUIREMENTS

2.1 Content

The eQTG should be presented in a form to allow for a quick and efficient review
and evaluation as defined below.

2.1.1 Regulatory Compliance

An eQTG must provide conformance to applicable regulatory QTG requirements

(e.g., 14 CFR Part 60, JAR-STD 1A (superseded), JAR-STD FSTD A, ICAO 9625).

2.1.2 Identification of eQTG

The eQTG should provide the user with the ability to uniquely identify a given
release, and provide adequate traceability of the results included therein. It is
recommended that this information include:
1. Operator and Regulatory FSTD ID(s)
2. Unique eQTG ID (e.g., date/time stamp, revision number)
2.1.3 Supporting Material

The supporting material should be included within the eQTG and be easily
accessible electronically while reviewing the associated test, and should include all
of the material required by the applicable regulatory authority (e.g., test
documentation, test description, clarifying notes, reference material, and rationale).

2.1.4 Source Data

The eQTG should include an electronic representation of the source of the

validation data, and it should be easily accessible while reviewing the associated
test (e.g., via hyperlinks).

2.1.5 Graphical Format

The eQTG test results should support color display. The following items, where
applicable, should be coded as follows:
1. Grid lines and axes Black
2. Background White
3. Validation data Blue solid line
4. FSTD results Green line
5. Out of tolerance FSTD results Red line
6. Master eQTG (MeQTG) FSTD results Gray line
The data lines should be wider than the grid lines, the individual traces must be
clearly identifiable, particularly when overlaid (e.g., line type, line width, symbols).
The following line types are suggested:
1. FSTD Results - short dashed
ARINC REPORT 436 – Page 4

2.0 EQTG REQUIREMENTS

2. Out of tolerance FSTD results - dotted

3. MeQTG FSTD results - long dashed
The eQTG should include a legend supporting these graphical line formats.

In the event that the eQTG is to be printed in a monochrome format, the individual
traces must be clearly identifiable (e.g., line type, line width, symbols).

Properly labeled axes should be used. Standard divisions on plot scales should be
used wherever possible. Scales should be sufficient to demonstrate trends, evaluate
tolerances and contain the plotted data of interest.

2.1.6 Test Information Accessibility Requirements

The documents referenced in Section 2.1.1 define minimum validation test

requirements all of which must be available within the eQTG.

The following should be displayed with the test results:

1. User’s FSTD ID
2. Test ID/Number
3. Test Name/Description
4. Manual/Automatic
5. Control Mode (for Computer Controlled Airplanes)
6. Run Date/Time
In addition, the following should be displayed or easily accessible (e.g., hyperlinks,
drop down list) when electronically viewing test results:
1. Manufacturer’s Name
2. User’s Name
3. Aircraft Model/Engine
4. FSTD/Software Configuration Load
5. Test Revision, if applicable
In the event that the eQTG is to be printed, it should also include:
1. Pagination
2.1.7 Test Analysis

When applicable, the following should be performed and included in the eQTG test
results:
1. Automatic identification of out of tolerance results
2. Calculation of parameters applicable to the analysis of the results (e.g.,
damping ratio, speed, time, period)
The methods used for calculations should be described.
 ARINC REPORT 436 – Page 5

2.0 EQTG REQUIREMENTS

2.1.8 Security

The eQTG should provide sufficient security to ensure the integrity of the original
contents. Specifically, the system should have the capability to lock or protect
specified sections while providing the ability to add electronic notes and electronic
approvals to the test results.

2.1.9 Document Archiving

The eQTG should be capable of being archived and allow quick retrieval and
viewing.

2.1.10 Configuration Control

The contents of the MeQTG should be defined, and an automated means within the
eQTG system provided to track the revision history.

2.1.11 MeQTG Update

The eQTG System should provide a method to update portions within the MeQTG
without affecting the remainder of the MeQTG. Chapter 3 describes in detail the
update process.

2.1.12 Hyperlinks and Bookmarks

If the eQTG makes use of hyperlinks to join each of the articles together, then every
article must be linked into the correct place, otherwise it may be inaccessible and
effectively missing from the eQTG. Manual checking of every link is tedious.
Therefore, the eQTG system should provide an automated collation process, which
should either faultlessly create or verify each and every one of the links in the
eQTG.

The eQTG should be usable as both an electronic and hardcopy document. When
printed, the hyperlinks should be visibly complete references, so that they can be
followed in the hardcopy result. This full expression should be as a complete and
traditional document reference and not as an internet URL (e.g., Document AB1234
- Revision G - Page 789).

2.2 Viewing the eQTG

2.2.1 Provision of Viewer

If needed, the author of the eQTG should provide the regulatory authorities the
software necessary to review the eQTG.

COMMENTARY

A possible format to create eQTGs is Portable Document Format

(PDF) since it can be easily seen and printed by users on a variety of
computer platforms.
ARINC REPORT 436 – Page 6

2.0 EQTG REQUIREMENTS

2.2.2 Encapsulation and Self-Containment

The eQTG should include all the information required to ensure that when viewed,
the on-screen appearance of the eQTG is independent of:
1. Application options
2. User profile
3. Installed fonts
4. Operating System and Computer platform
2.2.3 Document Navigation

The eQTG viewer should allow the user to easily review each test and navigate from
test to test in a sequential, logical manner consistent with the table of contents. It
should also have a method which will enable the user to jump to new sections of the
document easily. This capability can be similar, but is not limited to:
1. Bookmarks
2. Hyperlinks
2.2.4 Viewer Operation

The viewer should support standard keyboard operations (e.g., page down key
moves the document one page down) and standard mouse operations. The viewer
should also provide instructions as to its operation, including help facilities.

2.2.5 Zoom

The eQTG viewer should provide ability to zoom in/out.

2.2.6 Printing

The eQTG viewer should provide ability to print results, with the capability to support
correctly scaled output on the appropriate paper format. The resolution of the
recorded data should be sufficient to allow hard copy to be printed at a quality high
enough to allow appropriate manual evaluation of results.

2.3 Annotation of Individual Copy

1. Modifications to an individual copy are limited to the addition of temporary
notes and the addition of approval indications.
2. The eQTG viewer should provide capability to the user of adding temporary
notes to the eQTG. The temporary notes are unique to an individual copy of
the eQTG, and can be shared between other users of the eQTG. These
temporary notes exist for the life of a specific copy of the eQTG, but are not
automatically transferred to subsequent releases.
3. The eQTG should provide an adequate level of security to such
modifications.
4. The eQTG should provide the capability to identify the temporary notes
originator (reviewer or authorities).
5. The eQTG should provide the capability to prioritize temporary notes (e.g.,
color coding of notes, priority code).
6. Approval Indication
 ARINC REPORT 436 – Page 7

2.0 EQTG REQUIREMENTS

a. The eQTG viewer should be capable of adding an indication, such as

electronic signature, of evaluator approval and evaluation date to the
eQTG (e.g., Quality Assurance approval). One or more approvals can be
applied to:
i. Individual tests
ii. The entire eQTG
2.4 Annotation of Subsequent Releases
1. The eQTG system should provide the ability to the author of adding
permanent notes to the eQTG (e.g., test data rationale, additional references
and clarifications), possibly introduced as an outcome of temporary notes
raised during the review of an earlier release. These permanent notes are
automatically transferred to subsequent releases.
2. The eQTG system should provide an adequate level of security to such
modifications.
2.5 Optional eQTG Features and Enhancements

These additional features are not required for an eQTG, but are presented as
options to assist in test analysis or reduce test review time.
1. Development mode to separate results from non-approved/development
simulation loads and the official results for the quarter
2. Automatic initial condition verification to confirm the required settings
3. The ability to simultaneously display multiple FSTD results of the same test
4. Plot multiple FSTD results on one plot with the validation data
5. Manual offsetting of the FSTD results, including clear annotation
6. Automatic display of (X, Y) value of cursor, including the ability to mark the
plot
7. Selectable viewing of plots chosen from a list of available parameters
8. Provide the user with options to alter the presentation of the data including
axis range (e.g., time slice) and scale, plot size and order
9. The capability to search an eQTG or eQTGs based on filtered values
ARINC REPORT 436 – Page 8

3.0 PROCESS FOR INITIAL AND RECURRENT QUALIFICATION USING AN EQTG

3.0 PROCESS FOR INITIAL AND RECURRENT QUALIFICATION USING AN EQTG

3.1 Introduction

The following sections describe in detail the eQTG process depicted below.

Figure 3-1 – eQTG Process

3.2 Items Required for Initial QTG Submittal

The following should be provided with the initial QTG submittal letter:
1. All eQTG components submitted on CD, DVD, or any other electronic media.
The electronic media used should be acceptable to the regulatory authority,
and may include:
a. Master QTG on CD, DVD or any other electronic media readable on a
standard PC
b. Web-based system accessible via the Internet
c. eQTG downloaded from a server via the Internet
2. eQTG tool, viewer, or access to the internet site required to review the
eQTG.
3. eQTG user manual or any relevant procedures to access eQTG information
on electronic media.
4. A statement of compliance to ARINC Report 436.
 ARINC REPORT 436 – Page 9

3.0 PROCESS FOR INITIAL AND RECURRENT QUALIFICATION USING AN EQTG

3.3 eQTG Review Comments

On receipt of the eQTG, the reviewer may wish to raise comments regarding the
QTG in the form of temporary notes using the features described in Section 2.3, and
return an annotated copy to the sender. The temporary notes may become
permanent notes.

3.4 Initial Qualification

During FSTD qualification, the MeQTG may be signed by the authorities using the
features described in Section 2.3, Item 6. The MeQTG should be retained by the
FSTD operator, and if required, a copy provided to the regulatory authorities on CD,
DVD, or other electronic media as described in Section 3.2, Item 1.

3.5 Recurrent Qualification

Prior to recurrent qualification, the eQTG should be made available on electronic

media as described in Section 3.2, Item 1. The recurrent results may be compared
with the validation data and MeQTG FSTD results using the features described in
Section 2.1.5. The regulatory authority may sign and approve the eQTG using the
features described in

Section 2.3, Item 6. The FSTD operator should archive the approved eQTG results
from the recurrent qualifications.

3.6 MeQTG Update

When the author updates the MeQTG, only the portions affected by the update are
included in the MeQTG and reflected in the revision history as specified in Section
2.1.10 and Section 2.1.11.

The regulatory authority may sign and approve the updated MeQTG using the
features described in Section 2.3, Item 6.
ARINC REPORT 436 – Page 10

4.0 SECURITY, ACCESS, AND PRIVACY GUIDELINES

4.0 SECURITY, ACCESS, AND PRIVACY GUIDELINES

4.1 Introduction

The following guidelines outline recommended procedures to protect the integrity of

the eQTG.

4.2 Security

Once the results are approved, either as the initial qualification or recurrent results,
they must be protected to prevent accidentally overwriting an approved eQTG.

4.3 Access

A method should be provided to control who has read only, read/write, or full access
to results. A method should be provided to record the time, date and author of each
modification.

4.4 Privacy

A method should be provided to prevent the inappropriate transfer of data or

software.
 ARINC REPORT 436 – Page 11

APPENDIX A
GLOSSARY

APPENDIX A GLOSSARY

Author
The person who creates or modifies an eQTG.

eMQTG
An electronic copy of a paper MQTG for legacy systems (e.g., scanned).

eQTG
Electronic Qualification Test Guide – a QTG produced by an eQTG System.

eQTG ID
A code identifying a release of the eQTG

eQTG System
Tools and processes to create, modify, and view an eQTG.

eQTG Viewer
An application that presents the eQTG to the user.

FSTD
Flight Simulation Training Device

FSTD ID
A code identifying an FSTD.

Legacy Systems
FSTDs that do not have an eQTG System.

MeQTG
Master Electronic Qualification Test Guide – an MQTG produced by an eQTG
System.
MQTG
Master Qualification Test Guide – the authority approved QTG which incorporates
the results of tests witnessed by the authority. The MQTG serves as the reference
for future evaluations.

PDF
Portable Document Format

Permanent Notes
Annotations within the eQTG that are automatically propagated from one eQTG
release to the next.

QTG
Qualification Test Guide – primary reference document used for evaluating an
aircraft FSTD. It contains test results, statements of compliance and capability, the
ARINC REPORT 436 – Page 12

APPENDIX A
GLOSSARY

configuration of the aircraft simulated and other information for the evaluator to
assess the FSTD against the applicable regulatory criteria.

Regulatory Authority
Qualifying agency (e.g., FAA, CAA, MOT)

Release
A uniquely identifiable version of the eQTG.

Supporting material
Additional information for a test (e.g., test documentation, test description, clarifying
notes, reference material, rationale)

Temporary Notes
Annotations to the current release of the eQTG that are not automatically
propagated to the next release.

Term
Definition

Validation data
Data used to prove that the FSTD performance corresponds to that of the aircraft.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 24101-7435

SUPPLEMENT 1
TO
ARINC REPORT 436

GUIDELINES FOR ELECTRONIC QUALIFICATION TEST GUIDE

Published: September 20, 2010

Prepared by the FSEMC

Adopted by the FSEMC Steering Committee: July 21, 2010

 SUPPLEMENT 1 TO ARINC REPORT 436 – Page a

A. PURPOSE OF THIS DOCUMENT

This Supplement provides updates to references to standards and regulations
related to the certification and compliance of flight training devices. As these other
standards have evolved and been updated, the need for ARINC Report 436 to
remain current has driven this supplement.

B. ORGANIZATION OF THIS SUPPLEMENT

In this document blue bold text is used to indicate those areas of text changed by
the current Supplement only.

C. CHANGES TO ARINC REPORT 436 INTRODUCED BY THIS SUPPLEMENT

This section presents a complete listing of the changes to the document introduced
by this Supplement. Each change is identified by the section number and the title as
it will appear in the complete document. Where necessary, a brief description of the
change is included.

1.5 Related Documents

Corrected the reference to 14 CFR Part 60 with correct title.
Corrected the reference to Joint Aviation Requirements JAR-STD 1A with correct
title, and noted that it has been superseded by JAR-STD FTSD A.
Added the reference of Joint Aviation Requirements JAR-STD FSTD A.
Added the reference to “Aeroplane Flight Simulation Training Device Evaluation
Handbook”.

2.1.1 Regulatory Compliance

Updated the paragraph to reflect the superseded JAR-STD 1A.
Added the reference to JAR-STD FSTD A.
 ARINC Standard – Errata Report
1. Document Title
(Insert the number, supplement level, date of publication, and title of the document with the error)

2. Reference

Page Number: Section Number: Date of Submission:

3. Error
(Reproduce the material in error, as it appears in the standard.)

4. Recommended Correction
(Reproduce the correction as it would appear in the corrected version of the material.)

5. Reason for Correction (Optional)

(State why the correction is necessary.)

6. Submitter (Optional)
(Name, organization, contact information, e.g., phone, email address.)

Please return comments to fax +1 410-266-2047 or [email protected]

Note: Items 2-5 may be repeated for additional errata. All recommendations will be evaluated by the staff. Any
substantive changes will require submission to the relevant subcommittee for incorporation into a subsequent
Supplement.

[To be completed by IA Staff ]

Errata Report Identifier: Engineer Assigned:

Review Status:

ARINC Errata Form

11/24/2004
 ARINC IA Project Initiation/Modification (APIM)
Name of proposed project APIM #: _____
Name for proposed project.

Suggested Subcommittee assignment

Identify an existing group that has the expertise to successfully complete the
project. If no such group is known to exist, a recommendation to form a new
group may be made.

Project Scope
Describe the scope of the project clearly and concisely. The scope should
describe “what” will be done, i.e., the technical boundaries of the project.
Example: “This project will standardize a protocol for the control of printers.
The protocol will be independent of the underlying data stream or page
description language but will be usable by all classes of printers.”

Project Benefit
Describe the purpose and benefit of the project. This section should describe
“why” the project should be done. Describe how the new standard will improve
competition among vendors, giving airlines freedom of choice. This section
provides justification for the allocation of both IA and airline resources.
Example: “Currently each class of printers implements its own proprietary
protocol for the transfer of a print job. In order to provide access to the cockpit
printer from several different avionics sources, a single protocol is needed. The
protocol will permit automatic determination of printer type and configuration to
provide for growth and product differentiation.”

Airlines supporting effort

Name, airline, and contact information for proposed chairman, lead airline, list
of airlines expressing interest in working on the project (supporting airlines), and
list of airlines expressing interest but unable to support (sponsoring airlines). It
is important for airline support to be gained prior to submittal. Other
organizations, such as airframe manufacturers, avionics vendors, etc. supporting
the effort should also be listed.

Issues to be worked
Describe the major issues to be addressed by the proposed ARINC standard.

Recommended Coordination with other groups

Draft documents may have impact on the work of groups other than the
originating group. The APIM writer or, subsequently, The Committee may
identify other groups which must be given the opportunity to review and comment
upon mature draft documents.
 Projects/programs supported by work
If the timetable for this work is driven by a new airplane type, major avionics
overhaul, regulatory mandate, etc., that information should be placed in this
section. This information is a key factor in assessing the priority of this proposed
task against all other tasks competing for subcommittee meeting time and other
resources.

Timetable for projects/programs

Identify when the new ARINC standard is needed (month/year).

Documents to be produced and date of expected result

The name and number (if already assigned) of the proposed ARINC standard to
be either newly produced or modified.

Comments
Anything else deemed useful to the committees for prioritization of this work.

Meetings
The following table identifies the number of meetings and proposed meeting days
needed to produce the documents described above.

Activity Mtgs Mtg-Days

Document a # of mtgs # of mtg days
Document b # of mtgs # of mtg days

For IA Staff use

Date Received: IA Staff Assigned:
Potential impact:
(A. Safety B. Regulatory C. New aircraft/system D. Other)
Forward to committee(s) (AEEC, AMC, FSEMC): Date Forward:
Committee resolution:
(0 Withdrawn 1 Authorized 2 Deferred 3 More detail needed 4 Rejected)
Assigned Priority: Date of Resolution:
A. – High (execute first) B. – Normal (may be deferred for A.)
Assigned to SC/WG: