20
14 CFR Ch. I (1–1–19 Edition)
Pt. 60, App. A
approved flight training programs for the
FFSs in the Chicago and Moscow centers) be-
cause—
(i) Each FFS in the Chicago center and
each FFS in the Moscow center is used at
least once each 12-month period by another
FAA certificate holder in that other certifi-
cate holder’s FAA-approved flight training
program for the airplane (as described in
§ 60.7(d)(1));
OR
(ii) A statement is obtained from a quali-
fied pilot (having flown the airplane, not the
subject FFS or another FFS, during the pre-
ceding 12-month period) stating that the per-
formance and handling qualities of each FFS
in the Chicago and Moscow centers rep-
resents the airplane (as described in
§ 60.7(d)(2)).
E
ND
I
NFORMATION
lllllllllllllllllllllll
7. A
DDITIONAL
R
ESPONSIBILITIES OF THE
S
PONSOR
(§ 60.9)
lllllllllllllllllllllll
B
EGIN
I
NFORMATION
The phrase ‘‘as soon as practicable’’ in
§ 60.9(a) means without unnecessarily dis-
rupting or delaying beyond a reasonable
time the training, evaluation, or experience
being conducted in the FFS.
E
ND
I
NFORMATION
lllllllllllllllllllllll
8. FFS U
SE
(§ 60.11)
lllllllllllllllllllllll
B
EGIN
I
NFORMATION
No additional regulatory or informational
material applies to § 60.11, Simulator Use.
E
ND
I
NFORMATION
lllllllllllllllllllllll
9. FFS O
BJECTIVE
D
ATA
R
EQUIREMENTS
(§ 60.13)
lllllllllllllllllllllll
B
EGIN
QPS R
EQUIREMENTS
a. Flight test data used to validate FFS
performance and handling qualities must
have been gathered in accordance with a
flight test program containing the following:
(1) A flight test plan consisting of:
(a) The maneuvers and procedures required
for aircraft certification and simulation pro-
gramming and validation.
(b) For each maneuver or procedure—
(i) The procedures and control input the
flight test pilot and/or engineer used.
(ii) The atmospheric and environmental
conditions.
(iii) The initial flight conditions.
(iv) The airplane configuration, including
weight and center of gravity.
(v) The data to be gathered.
(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.
VerDate Sep<11>2014
16:30 Jun 25, 2019
Jkt 247047
PO 00000
Frm 00030
Fmt 8010
Sfmt 8002
Q:\14\14V2.TXT
PC31
kpayne on VMOFRWIN702 with $$_JOB