Pt. 60, App. C 14 CFR Ch. I (1-1-19 Edition) TABLE OF CONTENTS - Continued Paragraph No. Title 9. .............. Engineering Simulator - Validation Data. 10. ............ [Reserved] 11. ............ Validation Test Tolerances. 12. ............ Validation Data Roadmap. 13. ............ Acceptance Guidelines for Alternative Engines Data. 14. ............ Acceptance Guidelines for Alternative Avionics (Flight-Related Computers and Controllers). 15. ............ Transport Delay Testing. 16. ............ Continuing Qualification Evaluations - Validation Test Data Presentation. 17. ............ Alternative Data Sources, Procedures, and Instrumentation: Level A and Level B Simulators Only. 1. INTRODUCTION a. If relevant winds are present in the objective data, the wind vector (magnitude and direction) should be clearly noted as part of the data presentation, expressed in conventional terminology, and related to the runway being used for the test. b. The NSPM will not evaluate any simulator unless the required SOC indicates that the motion system is designed and manufactured to safely operate within the simulator-s maximum excursion, acceleration, and velocity capabilities (see Motion System in the following table). c. Table C2A addresses helicopter simulators at Levels B, C, and D because there are no Level A Helicopter simulators. 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 of C2A, FFS Objective Tests. Computer-generated simulator test results must be provided for each test except where an alternative 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 helicopter being simulated or to the qualification level sought, it may be disregarded (e.g., an engine out missed approach for a singleengine helicopter, or a hover test for a Level B simulator). Each test result is compared against the validation data described in Section 60.13 and in this appendix. Although use of a driver program designed to automatically accomplish the tests is encouraged for all simulators and required for Level C and Level D simulators, each test must be able to be accomplished manually while recording all appropriate parameters. The results must be produced on an appropriate recording device acceptable to the NSPM and must include simulator 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 C2A. All results must be labeled using the tolerances and units given. b. Table C2A sets out the test results required, including the parameters, tolerances, and flight conditions for simulator validation. Tolerances are provided for the listed tests because mathematical modeling and acquisition/development of reference data are often inexact. All tolerances listed in the following tables are applied to simulator performance. When two tolerance values are given for a parameter, the less restrictive value 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 an SOC. In Table C2A, 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 simulator 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 selection. 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 simulator to helicopter data throughout a time history, differences must be justified by providing a comparison of other related variables for the condition being assessed. e. The FFS may not be programmed so that the mathematical modeling is correct only at the validation test points. Unless noted otherwise, simulator tests must represent helicopter performance and handling qualities at operating weights and centers of gravity (CG) typical of normal operation. If a test is supported by helicopter data at one extreme weight or CG, another test supported by helicopter data at mid-conditions or as close as possible to the other extreme must be included. Certain tests that are relevant only at one extreme CG or weight condition need not be repeated at the other extreme. Tests of handling qualities must include validation of augmentation devices. 338 VerDate Sep<11>2014 16:30 Jun 25, 2019 Jkt 247047 PO 00000 Frm 00348 Fmt 8010 Sfmt 8002 Q:\14\14V2.TXT PC31