Code of Federal Regulations - Title 14

14 CFR Ch. I (1–1–14 Edition)

Pt. 60, App. A

(6) Cruise—clean configuration at cruise

altitude and airspeed;

(7) Approach—gear up or down with flaps/

slats at any normal approach position as rec-
ommended by the airplane manufacturer;
and

(8) Landing—gear down with flaps/slats in

any certified landing position.

b. The format for numbering the objective

tests in Appendix A, Attachment 2, Table
A2A, and the objective tests in Appendix B,
Attachment 2, Table B2A, is identical. How-
ever, each test required for FFSs is not nec-
essarily required for FTDs. Also, each test
required for FTDs is not necessarily required
for FFSs. Therefore, when a test number (or
series of numbers) is not required, the term
‘‘Reserved’’ is used in the table at that loca-
tion. Following this numbering format pro-
vides a degree of commonality between the
two tables and substantially reduces the po-
tential for confusion when referring to objec-
tive test numbers for either FFSs or FTDs.

c. The reader is encouraged to review the

Airplane Flight Simulator Evaluation Hand-
book, Volumes I and II, published by the
Royal Aeronautical Society, London, UK,
and AC 25–7, as amended, Flight Test Guide
for Certification of Transport Category Air-
planes, and AC 23–8, as amended, Flight Test
Guide for Certification of Part 23 Airplanes,
for references and examples regarding flight
testing requirements and techniques.

d. If relevant winds are present in the ob-

jective data, the wind vector should be clear-
ly noted as part of the data presentation, ex-
pressed in conventional terminology, and re-
lated to the runway being used for the test.

NFORMATION

lllllllllllllllllllllll

EGIN

QPS R

EQUIREMENTS

2. T

EST

EQUIREMENTS

a. The ground and flight tests required for

qualification are listed in Table A2A, FFS
Objective Tests. Computer generated simu-
lator test results must be provided for each
test except where an alternative test is spe-
cifically authorized by the NSPM. If a flight
condition or operating condition is required
for the test but does not apply to the air-
plane being simulated or to the qualification
level sought, it may be disregarded (e.g., an
engine out missed approach for a single-en-
gine airplane or a maneuver using reverse
thrust for an airplane without reverse thrust
capability). Each test result is compared
against the validation data described in
§ 60.13 and in this appendix. Although use of
a driver program designed to automatically
accomplish the tests is encouraged for all
simulators and required for Level C and
Level D simulators, it must be possible to
conduct each test manually while recording
all appropriate parameters. The results must

be produced on an appropriate recording de-
vice acceptable to the NSPM and must in-
clude simulator number, date, time, condi-
tions, tolerances, and appropriate dependent
variables portrayed in comparison to the val-
idation data. Time histories are required un-
less otherwise indicated in Table A2A. All re-
sults must be labeled using the tolerances
and units given.

b. Table A2A in this attachment sets out

the test results required, including the pa-
rameters, tolerances, and flight conditions
for simulator validation. Tolerances are pro-
vided for the listed tests because mathe-
matical modeling and acquisition and devel-
opment of reference data are often inexact.
All tolerances listed in the following tables
are applied to simulator performance. When
two tolerance values are given for a param-
eter, the less restrictive may be used unless
otherwise indicated. In those cases where a
tolerance is expressed only as a percentage,
the tolerance percentage applies to the max-
imum value of that parameter within its
normal operating range as measured from
the neutral or zero position unless otherwise
indicated.

c. Certain tests included in this attach-

ment must be supported with an SOC. In
Table A2A, requirements for SOCs are indi-
cated in the ‘‘Test Details’’ column.

d. When operational or engineering judg-

ment is used in making assessments for
flight test data applications for simulator
validity, such judgment must not be limited
to a single parameter. For example, data
that exhibit rapid variations of the measured
parameters may require interpolations or a
‘‘best fit’’ data selection. All relevant param-
eters related to a given maneuver or flight
condition must be provided to allow overall
interpretation. When it is difficult or impos-
sible to match simulator to airplane data
throughout a time history, differences must
be justified by providing a comparison of
other related variables for the condition
being assessed.

e. It is not acceptable to program the FFS

so that the mathematical modeling is cor-
rect only at the validation test points. Un-
less otherwise noted, simulator tests must
represent airplane performance and handling
qualities at operating weights and centers of
gravity (CG) typical of normal operation. If
a test is supported by airplane data at one
extreme weight or CG, another test sup-
ported by airplane data at mid-conditions or
as close as possible to the other extreme
must be included. Certain tests that are rel-
evant only at one extreme CG or weight con-
dition need not be repeated at the other ex-
treme. Tests of handling qualities must in-
clude validation of augmentation devices.

f. When comparing the parameters listed to

those of the airplane, sufficient data must
also be provided to verify the correct flight
condition and airplane configuration

VerDate Mar<15>2010

20:48 Jan 30, 2014

Jkt 232047

PO 00000

Frm 00050

Fmt 8010

Sfmt 8002

Q:\14\14V2.TXT

ofr150

PsN: PC150