20
14 CFR Ch. I (1–1–14 Edition)
Pt. 60, App. A
(vi) All other information necessary to
recreate the flight test conditions in the
FFS.
(2) Appropriately qualified flight test per-
sonnel.
(3) An understanding of the accuracy of the
data to be gathered using appropriate alter-
native data sources, procedures, and instru-
mentation that is traceable to a recognized
standard as described in Attachment 2, Table
A2E of this appendix.
(4) Appropriate and sufficient data acquisi-
tion equipment or system(s), including ap-
propriate data reduction and analysis meth-
ods and techniques, as would be acceptable
to the FAA’s Aircraft Certification Service.
b. The data, regardless of source, must be
presented as follows:
(1) In a format that supports the FFS vali-
dation process.
(2) In a manner that is clearly readable and
annotated correctly and completely.
(3) With resolution sufficient to determine
compliance with the tolerances set forth in
Attachment 2, Table A2A of this appendix.
(4) With any necessary instructions or
other details provided, such as yaw damper
or throttle position.
(5) Without alteration, adjustments, or
bias. Data may be corrected to address
known data calibration errors provided that
an explanation of the methods used to cor-
rect the errors appears in the QTG. The cor-
rected data may be re-scaled, digitized, or
otherwise manipulated to fit the desired
presentation.
c. After completion of any additional flight
test, a flight test report must be submitted
in support of the validation data. The report
must contain sufficient data and rationale to
support qualification of the FFS at the level
requested.
d. As required by § 60.13(f), the sponsor
must notify the NSPM when it becomes
aware that an addition to, an amendment to,
or a revision of data that may relate to FFS
performance or handling characteristics is
available. The data referred to in this para-
graph is data used to validate the perform-
ance, handling qualities, or other character-
istics of the aircraft, including data related
to any relevant changes occurring after the
type certificate was issued. The sponsor
must—
(1) Within 10 calendar days, notify the
NSPM of the existence of this data; and
(2) Within 45 calendar days, notify the
NSPM of—
(a) The schedule to incorporate this data
into the FFS; or
(b) The reason for not incorporating this
data into the FFS.
e. In those cases where the objective test
results authorize a ‘‘snapshot test’’ or a ‘‘se-
ries of snapshot tests’’ results in lieu of a
time-history result, the sponsor or other
data provider must ensure that a steady
state condition exists at the instant of time
captured by the ‘‘snapshot.’’ The steady
state condition must exist from 4 seconds
prior to, through 1 second following, the in-
stant of time captured by the snapshot.
E
ND
QPS R
EQUIREMENTS
lllllllllllllllllllllll
B
EGIN
I
NFORMATION
f. The FFS sponsor is encouraged to main-
tain a liaison with the manufacturer of the
aircraft being simulated (or with the holder
of the aircraft type certificate for the air-
craft being simulated if the manufacturer is
no longer in business), and, if appropriate,
with the person having supplied the aircraft
data package for the FFS in order to facili-
tate the notification required by § 60.13(f).
g. It is the intent of the NSPM that for
new aircraft entering service, at a point well
in advance of preparation of the Qualifica-
tion Test Guide (QTG), the sponsor should
submit to the NSPM for approval, a descrip-
tive document (see Table A2C, Sample Vali-
dation Data Roadmap for Airplanes) con-
taining the plan for acquiring the validation
data, including data sources. This document
should clearly identify sources of data for all
required tests, a description of the validity
of these data for a specific engine type and
thrust rating configuration, and the revision
levels of all avionics affecting the perform-
ance or flying qualities of the aircraft. Addi-
tionally, this document should provide other
information, such as the rationale or expla-
nation for cases where data or data param-
eters are missing, instances where engineer-
ing simulation data are used or where flight
test methods require further explanations. It
should also provide a brief narrative describ-
ing the cause and effect of any deviation
from data requirements. The aircraft manu-
facturer may provide this document.
h. There is no requirement for any flight
test data supplier to submit a flight test
plan or program prior to gathering flight
test data. However, the NSPM notes that in-
experienced data gatherers often provide
data that is irrelevant, improperly marked,
or lacking adequate justification for selec-
tion. Other problems include inadequate in-
formation regarding initial conditions or
test maneuvers. The NSPM has been forced
to refuse these data submissions as valida-
tion data for an FFS evaluation. It is for this
reason that the NSPM recommends that any
data supplier not previously experienced in
this area review the data necessary for pro-
gramming and for validating the perform-
ance of the FFS, and discuss the flight test
plan anticipated for acquiring such data with
the NSPM well in advance of commencing
the flight tests.
i. The NSPM will consider, on a case-by-
case basis, whether to approve supplemental
VerDate Mar<15>2010
20:48 Jan 30, 2014
Jkt 232047
PO 00000
Frm 00030
Fmt 8010
Sfmt 8002
Q:\14\14V2.TXT
ofr150
PsN: PC150