Federal Aviation Administration, DOT

Pt. 60, App. B

END INFORMATION
lllllllllllllllllllllll
BEGIN QPS REQUIREMENTS

kpayne on VMOFRWIN702 with $$_JOB

2. TEST REQUIREMENTS
a. The ground and flight tests required for
qualification are listed in Table B2A Objective Tests. Computer generated FTD test results must be provided for each test except
where an alternate test is specifically authorized by the NSPM. If a flight condition
or operating condition is required for the
test but does not apply to the airplane being
simulated or to the qualification level
sought, it may be disregarded (e.g., an engine
out missed approach for a single-engine airplane; a maneuver using reverse thrust for
an airplane without reverse thrust capability). Each test result is compared against
the validation data described in Section 60.13, and
in Appendix B. The results must be produced
on an appropriate recording device acceptable to the NSPM and must include FTD
number, date, time, conditions, tolerances,
and appropriate dependent variables portrayed in comparison to the validation data.
Time histories are required unless otherwise
indicated in Table B2A. All results must be
labeled using the tolerances and units given.
b. Table B2A in this attachment sets out
the test results required, including the parameters, tolerances, and flight conditions
for FTD validation. Tolerances are provided
for the listed tests because mathematical
modeling and acquisition and development of
reference data are often inexact. All tolerances listed in the following tables are applied to FTD performance. When two tolerance values are given for a parameter, 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 maximum 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 attachment must be supported with a SOC. In
Table B2A, requirements for SOCs are indicated in the  - Test Details -  column.
d. When operational or engineering judgment is used in making assessments for
flight test data applications for FTD validity, such judgment may 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 section. All relevant parameters related to a given maneuver or flight
condition must be provided to allow overall
interpretation. When it is difficult or impossible to match FTD 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 FTD
so that the mathematical modeling is correct only at the validation test points. Unless otherwise noted, FTD tests must represent airplane performance and handling
qualities at operating weights and centers of
gravity (CG) typical of normal operation.
FTD tests at extreme weight or CG conditions may be acceptable where required for
concurrent aircraft certification testing.
Tests of handling qualities must include 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
changes. For example, to show that control
force is within the parameters for a static
stability test, data to show the correct airspeed, power, thrust or torque, airplane configuration, altitude, and other appropriate
datum identification parameters must also
be given. If comparing short period dynamics, normal acceleration may be used to establish a match to the airplane, but airspeed,
altitude, control input, airplane configuration, and other appropriate data must also
be given. If comparing landing gear change
dynamics, pitch, airspeed, and altitude may
be used to establish a match to the airplane,
but landing gear position must also be provided. All airspeed values must be properly
annotated (e.g., indicated versus calibrated).
In addition, the same variables must be used
for comparison (e.g., compare inches to
inches rather than inches to centimeters).
g. The QTG provided by the sponsor must
clearly describe how the FTD will be set up
and operated for each test. Each FTD subsystem may be tested independently, but
overall integrated testing of the FTD must
be accomplished to assure that the total
FTD system meets the prescribed standards.
A manual test procedure with explicit and
detailed steps for completing each test must
also be provided.
h. For previously qualified FTDs, the tests
and tolerances of this attachment may be
used in subsequent continuing qualification
evaluations for any given test if the sponsor
has submitted a proposed MQTG revision to
the NSPM and has received NSPM approval.
i. FTDs are evaluated and qualified with an
engine model simulating the airplane data
supplier-s flight test engine. For qualification of alternative engine models (either
variations of the flight test engines or other
manufacturer-s engines) additional tests
with the alternative engine models may be
required. This attachment contains guidelines for alternative engines.
j. Testing Computer Controlled Aircraft
(CCA) simulators, or other highly augmented
airplane simulators, flight test data is required for the Normal (N) and/or Non-normal

223

VerDate Sep<11>2014

16:30 Jun 25, 2019

Jkt 247047

PO 00000

Frm 00233

Fmt 8010

Sfmt 8002

Q:\14\14V2.TXT

PC31