background image


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

Pt. 60, App. B 

(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 


(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 

(2) Appropriately qualified flight test per-


(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 
B2F 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, acceptable to the FAA’s 
Aircraft Certification Service. 

b. The data, regardless of source, must be 


(1) In a format that supports the FTD 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 B2A, Appendix B; 

(4) With any necessary guidance informa-

tion provided; and 

(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 

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 FTD at the level 

d. As required by § 60.13(f), the sponsor 

must notify the NSPM when it becomes 
aware that an addition to or a revision of the 
flight related data or airplane systems re-
lated data is available if this data is used to 
program and operate a qualified FTD. The 
data referred to in this sub-section are those 
data that are 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 certification is issued. The sponsor 

(1) Within 10 calendar days, notify the 

NSPM of the existence of this data; and 

(2) Within 45 calendar days, notify the 

NSPM of— 

(i) The schedule to incorporate this data 

into the FTD; or 

(ii) The reason for not incorporating this 

data into the FTD. 

e. In those cases where the objective test 

results authorize a ‘‘snapshot test’’ or a ‘‘se-
ries of snapshot test 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 snap shot. 












f. The FTD 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 FTD in order to facili-
tate the notification described in this para-

g. It is the intent of the NSPM that for 

new aircraft entering service, at a point well 
in advance of preparation of the QTG, the 
sponsor should submit to the NSPM for ap-
proval, a descriptive document (see Appendix 
A, Table A2C, Sample Validation Data Road-
map for Airplanes) containing the plan for 
acquiring the validation data, including data 
sources. This document should clearly iden-
tify sources of data for all required tests, a 
description of the validity of these data for a 
specific engine type and thrust rating con-
figuration, and the revision levels of all avi-
onics affecting the performance or flying 
qualities of the aircraft. Additionally, this 
document should provide other information 
such as the rationale or explanation for 
cases where data or data parameters are 
missing, instances where engineering sim-
ulation 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 FTD evaluation. It is for 

VerDate Sep<11>2014 

16:30 Jun 25, 2019

Jkt 247047

PO 00000

Frm 00200

Fmt 8010

Sfmt 8002



kpayne on VMOFRWIN702 with $$_JOB