372 

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

Pt. 60, App. C 

data collected from specific helicopter flight 
tests or other flights the required design 
model or data changes necessary to support 
an acceptable Proof of Match (POM) should 
be generated by the helicopter manufacturer. 

(2) For proper validation of the two sets of 

data, the helicopter manufacturer should 
compare their simulation model responses 
against the flight test data, when driven by 
the same control inputs and subjected to the 
same atmospheric conditions as recorded in 
the flight test. The model responses should 
result from a simulation where the following 
systems are run in an integrated fashion and 
are consistent with the design data released 
to the flight simulator manufacturer: 

(a) Propulsion. 
(b) Aerodynamics. 
(c) Mass properties. 
(d) Flight controls. 
(e) Stability augmentation. 
(f) Brakes/landing gear. 
i. A qualified test pilot should be used to 

assess handling qualities and performance 
evaluations for the qualification of flight 
simulators of new helicopter types. 

E

ND

I

NFORMATION

 

lllllllllllllllllllllll

B

EGIN

QPS R

EQUIREMENT

 

9. E

NGINEERING

S

IMULATOR

—V

ALIDATION

 

D

ATA

 

a. When a fully validated simulation (i.e., 

validated with flight test results) is modified 
due to changes to the simulated helicopter 
configuration, the helicopter manufacturer 
or other acceptable data supplier must co-
ordinate with the NSPM to supply validation 
data from an ‘‘audited’’ engineering simu-
lator/simulation to selectively supplement 
flight test data. The NSPM must be provided 
an opportunity to audit the use of the engi-
neering simulation or the engineering simu-
lator during the acquisition of the data that 
will be used as validation data. Audited data 
may be used for changes that are incre-
mental in nature. Manufacturers or other 
data suppliers must be able to demonstrate 
that the predicted changes in helicopter per-
formance are based on acceptable aero-
nautical principles with proven success his-
tory and valid outcomes. This must include 
comparisons of predicted and flight test vali-
dated data. 

b. Helicopter manufacturers or other ac-

ceptable data suppliers seeking to use an en-
gineering simulator for simulation valida-
tion data as an alternative to flight-test de-
rived validation data, must contact the 
NSPM and provide the following: 

(1) A description of the proposed aircraft 

changes, a description of the proposed sim-
ulation model changes, and the use of an in-
tegral configuration management process, 
including an audit of the actual simulation 

model modifications that includes a step-by- 
step description leading from the original 
model(s) to the current model(s). 

(2) A schedule for review by the NSPM of 

the proposed plan and the subsequent valida-
tion data to establish acceptability of the 
proposal. 

(3) Validation data from an audited engi-

neering simulator/simulation to supplement 
specific segments of the flight test data. 

c. To be qualified to supply engineering 

simulator validation data, for aerodynamic, 
engine, flight control, or ground handling 
models, a helicopter manufacturer or other 
acceptable data supplier must: 

(1) Be able to verify their ability to: 
(a) Develop and implement high fidelity 

simulation models; and 

(b) Predict the handling and performance 

characteristics of a helicopter with suffi-
cient accuracy to avoid additional flight test 
activities for those handling and perform-
ance characteristics. 

(2) Have an engineering simulator that: 
(a) Is a physical entity, complete with a 

flight deck representative of the simulated 
class of helicopter; 

(b) Has controls sufficient for manual 

flight; 

(c) Has models that run in an integrated 

manner; 

(d) Had fully flight-test validated simula-

tion models as the original or baseline sim-
ulation models; 

(e) Has an out-of-the-flight deck visual sys-

tem; 

(f) Has actual avionics boxes interchange-

able with the equivalent software simula-
tions to support validation of released soft-
ware; 

(g) Uses the same models as released to the 

training community (which are also used to 
produce stand-alone proof-of-match and 
checkout documents); 

(h) Is used to support helicopter develop-

ment and certification; and 

(i) Has been found to be a high fidelity rep-

resentation of the helicopter by the manu-
facturer’s pilots (or other acceptable data 
supplier), certificate holders, and the NSPM. 

(3) Use the engineering simulator to 

produce a representative set of integrated 
proof-of-match cases. 

(4) Use a configuration control system cov-

ering hardware and software for the oper-
ating components of the engineering simu-
lator. 

(5) Demonstrate that the predicted effects 

of the change(s) are within the provisions of 
sub-paragraph ‘‘a’’ of this section, and con-
firm that additional flight test data are not 
required. 

d. Additional Requirements for Validation 

Data 

(1) When used to provide validation data, 

an engineering simulator must meet the sim-
ulator standards currently applicable to 

VerDate Sep<11>2014 

16:30 Jun 25, 2019

Jkt 247047

PO 00000

Frm 00382

Fmt 8010

Sfmt 8002

Q:\14\14V2.TXT

PC31

kpayne on VMOFRWIN702 with $$_JOB