Appendix C to Part 60 Qualification Performance Standards for Helicopter Full Flight Simulators
This appendix establishes the standards for Helicopter FFS evaluation and qualification. The Flight Standards Service is responsible for the development, application, and implementation of the standards contained within this appendix. The procedures and criteria specified in this appendix will be used by the responsible Flight Standards office when conducting helicopter FFS evaluations.
1. Introduction.
2. Applicability (§ 60.1) and (§ 60.2).
3. Definitions (§ 60.3).
4. Qualification Performance Standards (§ 60.4).
5. Quality Management System (§ 60.5).
6. Sponsor Qualification Requirements (§ 60.7).
7. Additional Responsibilities of the Sponsor (§ 60.9).
8. FFS Use (§ 60.11).
9. FFS Objective Data Requirements (§ 60.13).
10. Special Equipment and Personnel Requirements for Qualification of the FFS (§ 60.14).
11. Initial (and Upgrade) Qualification Requirements (§ 60.15).
12. Additional Qualifications for a Currently Qualified FFS (§ 60.16).
13. Previously Qualified FFSs (§ 60.17).
14. Inspection, Continuing Qualification Evaluation, and Maintenance Requirements (§ 60.19).
15. Logging FFS Discrepancies (§ 60.20).
16. Interim Qualification of FFSs for New Helicopter Types or Models (§ 60.21).
17. Modifications to FFSs (§ 60.23).
18. Operations with Missing, Malfunctioning, or Inoperative Components (§ 60.25).
19. Automatic Loss of Qualification and Procedures for Restoration of Qualification (§ 60.27).
20. Other Losses of Qualification and Procedures for Restoration of Qualification (§ 60.29).
21. Record Keeping and Reporting (§ 60.31).
22. [Reserved]
23. [Reserved]
24. [Reserved]
25. FFS Qualification on the Basis of a Bilateral Aviation Safety Agreement (BASA) (§ 60.37).
Attachment 1 to Appendix C to Part 60—General Simulator Requirements.
Attachment 2 to Appendix C to Part 60—FFS Objective Tests.
Attachment 3 to Appendix C to Part 60—Simulator Subjective Evaluation.
Attachment 4 to Appendix C to Part 60—Sample Documents.
Attachment 5 to Appendix C to Part 60—FSTD Directives Applicable to Helicopter FFSs
a. This appendix contains background information as well as regulatory and informative material as described later in this section. To assist the reader in determining what areas are required and what areas are permissive, the text in this appendix is divided into two sections: “QPS Requirements” and “Information.” The QPS Requirements sections contain details regarding compliance with the part 60 rule language. These details are regulatory, but are found only in this appendix. The Information sections contain material that is advisory in nature, and designed to give the user general information about the regulation.
b. [Reserved]
c. The responsible Flight Standards office encourages the use of electronic media for all communication, including any record, report, request, test, or statement required by this appendix. The electronic media used must have adequate security provisions and be acceptable to the responsible Flight Standards office.
d. Related Reading References.
(1) 14 CFR part 60.
(2) 14 CFR part 61.
(3) 14 CFR part 63.
(4) 14 CFR part 119.
(5) 14 CFR part 121.
(6) 14 CFR part 125.
(7) 14 CFR part 135.
(8) 14 CFR part 141.
(9) 14 CFR part 142.
(10) AC 120-35, as amended, Flightcrew Member Line Operational Simulations: Line-Oriented Flight Training, Special Purpose Operational Training, Line Operational Evaluation.
(11) AC 120-57, as amended, Surface Movement Guidance and Control System (SMGCS).
(12) AC 120-63, as amended, Helicopter Simulator Qualification.
(13) AC 150/5300-13, as amended, Airport Design.
(14) AC 150/5340-1, as amended, Standards for Airport Markings.
(15) AC 150/5340-4, as amended, Installation Details for Runway Centerline Touchdown Zone Lighting Systems.
(16) AC 150/5340-19, as amended, Taxiway Centerline Lighting System.
(17) AC 150/5340-24, as amended, Runway and Taxiway Edge Lighting System.
(18) AC 150/5345-28, as amended, Precision Approach Path Indicator (PAPI) Systems
(19) AC 150/5390-2, as amended, Heliport Design
(20) International Air Transport Association document, “Flight Simulator Design and Performance Data Requirements,” as amended.
(21) AC 29-2, as amended, Flight Test Guide for Certification of Transport Category Rotorcraft.
(22) AC 27-1, as amended, Flight Test Guide for Certification of Normal Category Rotorcraft.
(23) International Civil Aviation Organization (ICAO) Manual of Criteria for the Qualification of Flight Simulators, as amended.
(24) Airplane Flight Simulator Evaluation Handbook, Volume I, as amended and Volume II, as amended, The Royal Aeronautical Society, London, UK.
(25) FAA Airman Certification Standards and Practical Test Standards for Airline Transport Pilot, Type Ratings, Commercial Pilot, and Instrument Ratings.
(26) The FAA Aeronautical Information Manual (AIM). An electronic version of the AIM is on the Internet at http://www.faa.gov/atpubs.
(27) Aeronautical Radio, Inc. (ARINC) document number 436, titled Guidelines For Electronic Qualification Test Guide (as amended).
(28) Aeronautical Radio, Inc. (ARINC) document 610, Guidance for Design and Integration of Aircraft Avionics Equipment in Simulators (as amended).
No additional regulatory or informational material applies to § 60.1, Applicability, or to § 60.2, Applicability of sponsor rules to person who are not sponsors and who are engaged in certain unauthorized activities.
See Appendix F of this part for a list of definitions and abbreviations from part 1 and part 60, including the appropriate appendices of part 60.
No additional regulatory or informational material applies to § 60.4, Qualification Performance Standards.
See Appendix E of this part for additional regulatory and informational material regarding Quality Management Systems.
a. The intent of the language in § 60.7(b) is to have a specific FFS, identified by the sponsor, used at least once in an FAA-approved flight training program for the helicopter simulated during the 12-month period described. The identification of the specific FFS may change from one 12-month period to the next 12-month period as long as that sponsor sponsors and uses at least one FFS at least once during the prescribed period. There is no minimum number of hours or minimum FFS periods required.
b. The following examples describe acceptable operational practices:
(1) Example One.
(a) A sponsor is sponsoring a single, specific FFS for its own use, in its own facility or elsewhere—this single FFS forms the basis for the sponsorship. The sponsor uses that FFS at least once in each 12-month period in that sponsor's FAA-approved flight training program for the helicopter simulated. This 12-month period is established according to the following schedule:
(i) If the FFS was qualified prior to May 30, 2008, the 12-month period begins on the date of the first continuing qualification evaluation conducted in accordance with § 60.19 after May 30, 2008, and continues for each subsequent 12-month period;
(ii) A device qualified on or after May 30, 2008, will be required to undergo an initial or upgrade evaluation in accordance with § 60.15. Once the initial or upgrade evaluation is complete, the first continuing qualification evaluation will be conducted within 6 months. The 12 month continuing qualification evaluation cycle begins on that date and continues for each subsequent 12-month period.
(b) There is no minimum number of hours of FFS use required.
(c) The identification of the specific FFS may change from one 12-month period to the next 12-month period as long as that sponsor sponsors and uses at least one FFS at least once during the prescribed period.
(2) Example Two.
(a) A sponsor sponsors an additional number of FFSs, in its facility or elsewhere. Each additionally sponsored FFS must be—
(i) Used by the sponsor in the sponsor's FAA-approved flight training program for the helicopter simulated (as described in § 60.7(d)(1)); or
(ii) Used by another FAA certificate holder in that other certificate holder's FAA-approved flight training program for the helicopter simulated (as described in § 60.7(d)(1)). This 12-month period is established in the same manner as in example one; or
(iii) Provided a statement each year from a qualified pilot, (after having flown the helicopter, not the subject FFS or another FFS, during the preceding 12-month period) stating that the subject FFS's performance and handling qualities represent the helicopter (as described in § 60.7(d)(2)). This statement is provided at least once in each 12-month period established in the same manner as in example one.
(b) There is no minimum number of hours of FFS use required.
(3) Example Three.
(a) A sponsor in New York (in this example, a Part 142 certificate holder) establishes “satellite” training centers in Chicago and Moscow.
(b) The satellite function means that the Chicago and Moscow centers must operate under the New York center's certificate (in accordance with all of the New York center's practices, procedures, and policies; e.g., instructor and/or technician training/checking requirements, record keeping, QMS program).
(c) All of the FFSs in the Chicago and Moscow centers could be dry-leased (i.e., the certificate holder does not have and use FAA-approved flight training programs for the FFSs in the Chicago and Moscow centers) because—
(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 certificate holder's FAA-approved flight training program for the helicopter (as described in § 60.7(d)(1)); OR
(ii) A statement is obtained from a qualified pilot (having flown the helicopter, not the subject FFS or another FFS during the preceding 12-month period) stating that the performance and handling qualities of each FFS in the Chicago and Moscow centers represents the helicopter (as described in § 60.7(d)(2)).
7. Additional Responsibilities of the Sponsor (§ 60.9).
The phrase “as soon as practicable” in § 60.9(a) means without unnecessarily disrupting or delaying beyond a reasonable time the training, evaluation, or experience being conducted in the FFS.
No additional regulatory or informational material applies to § 60.11, FFS Use.
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 programming 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 helicopter 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 personnel.
(3) An understanding of the accuracy of the data to be gathered using appropriate alternative data sources, procedures, and instrumentation that is traceable to a recognized standard as described in Attachment 2, Table C2D of this appendix.
(4) Appropriate and sufficient data acquisition equipment or system(s), including appropriate data reduction and analysis methods and techniques, acceptable to the FAA's Aircraft Certification Service.
b. The data, regardless of source, must be presented:
(1) In a format that supports the FFS validation 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 C2A of this appendix.
(4) With any necessary instructions or other details provided, such as Stability Augmentation System (SAS) or throttle position; 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 correct the errors appears in the QTG. The corrected 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 responsible Flight Standards office 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 paragraph is data used to validate the performance, handling qualities, or other characteristics 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 responsible Flight Standards office of the existence of this data; and
(2) Within 45 calendar days, notify the responsible Flight Standards office 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 “series 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 instant of time captured by the snap shot.
f. The FFS sponsor is encouraged to maintain a liaison with the manufacturer of the aircraft being simulated (or with the holder of the aircraft type certificate for the aircraft being simulated if the manufacturer is no longer in business), and, if appropriate, with the person who supplied the aircraft data package for the FFS in order to facilitate the notification required by § 60.13(f).
g. It is the intent of the responsible Flight Standards office that for new aircraft entering service, at a point well in advance of preparation of the QTG, the sponsor should submit to the responsible Flight Standards office for approval, a descriptive document (see Table C2D, Sample Validation Data Roadmap for Helicopters) containing 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 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 simulation data are used or where flight test methods require further explanations. It should also provide a brief narrative describing the cause and effect of any deviation from data requirements. The aircraft manufacturer 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 responsible Flight Standards office notes that inexperienced data gatherers often provide data that is irrelevant, improperly marked, or lacking adequate justification for selection. Other problems include inadequate information regarding initial conditions or test maneuvers. The responsible Flight Standards office has been forced to refuse these data submissions as validation data for an FFS evaluation. It is for this reason that the responsible Flight Standards office recommends that any data supplier not previously experienced in this area review the data necessary for programming and for validating the performance of the FFS, and discuss the flight test plan anticipated for acquiring such data with the responsible Flight Standards office well in advance of commencing the flight tests.
i. The responsible Flight Standards office will consider, on a case-by-case basis, whether to approve supplemental validation data derived from flight data recording systems such as a Quick Access Recorder or Flight Data Recorder.
a. In the event that the responsible Flight Standards office determines that special equipment or specifically qualified persons will be required to conduct an evaluation, the responsible Flight Standards office will make every attempt to notify the sponsor at least one (1) week, but in no case less than 72 hours, in advance of the evaluation. Examples of special equipment include spot photometers, flight control measurement devices, and sound analyzers. Examples of specially qualified personnel include individuals specifically qualified to install or use any special equipment when its use is required.
b. Examples of a special evaluation include an evaluation conducted after an FFS is moved, at the request of the TPAA, or as a result of comments received from users of the FFS that raise questions about the continued qualification or use of the FFS.
a. In order to be qualified at a particular qualification level, the FFS must:
(1) Meet the general requirements listed in Attachment 1 of this appendix;
(2) Meet the objective testing requirements listed in Attachment 2 of this appendix; and
(3) Satisfactorily accomplish the subjective tests listed in Attachment 3 of this appendix.
b. The request described in § 60.15(a) must include all of the following:
(1) A statement that the FFS meets all of the applicable provisions of this part and all applicable provisions of the QPS.
(2) A confirmation that the sponsor will forward to the responsible Flight Standards office the statement described in § 60.15(b) in such time as to be received no later than 5 business days prior to the scheduled evaluation and may be forwarded to the responsible Flight Standards office via traditional or electronic means.
(3) A QTG, acceptable to the responsible Flight Standards office, that includes all of the following:
(a) Objective data obtained from aircraft testing or another approved source.
(b) Correlating objective test results obtained from the performance of the FFS as prescribed in the appropriate QPS.
(c) The result of FFS subjective tests prescribed in the appropriate QPS.
(d) A description of the equipment necessary to perform the evaluation for initial qualification and the continuing qualification evaluations.
c. The QTG described in paragraph (a)(3) of this section, must provide the documented proof of compliance with the simulator objective tests in Attachment 2, Table C2A of this appendix.
d. The QTG is prepared and submitted by the sponsor, or the sponsor's agent on behalf of the sponsor, to the responsible Flight Standards office for review and approval, and must include, for each objective test:
(1) Parameters, tolerances, and flight conditions.
(2) Pertinent and complete instructions for the conduct of automatic and manual tests.
(3) A means of comparing the FFS test results to the objective data.
(4) Any other information as necessary, to assist in the evaluation of the test results.
(5) Other information appropriate to the qualification level of the FFS.
e. The QTG described in paragraphs (a)(3) and (b) of this section, must include the following:
(1) A QTG cover page with sponsor and FAA approval signature blocks (see Attachment 4, Figure C4C, of this appendix, for a sample QTG cover page).
(2) A continuing qualification evaluation schedule requirements page. This page will be used by the responsible Flight Standards office to establish and record the frequency with which continuing qualification evaluations must be conducted and any subsequent changes that may be determined by the responsible Flight Standards office in accordance with § 60.19. See Attachment 4 of this appendix, Figure C4G, for a sample Continuing Qualification Evaluation Requirements page.
(3) An FFS information page that provides the information listed in this paragraph (see Attachment 4, Figure C4B, of this appendix for a sample FFS information page). For convertible FFSs, the sponsor must submit a separate page for each configuration of the FFS.
(a) The sponsor's FFS identification number or code.
(b) The helicopter model and series being simulated.
(c) The aerodynamic data revision number or reference.
(d) The source of the basic aerodynamic model and the aerodynamic coefficient data used to modify the basic model.
(e) The engine model(s) and its data revision number or reference.
(f) The flight control data revision number or reference.
(g) The flight management system identification and revision level.
(h) The FFS model and manufacturer.
(i) The date of FFS manufacture.
(j) The FFS computer identification.
(k) The visual system model and manufacturer, including display type.
(l) The motion system type and manufacturer, including degrees of freedom.
(4) A Table of Contents.
(5) A log of revisions and a list of effective pages.
(6) List of all relevant data references.
(7) A glossary of terms and symbols used (including sign conventions and units).
(8) Statements of compliance and capability (SOCs) with certain requirements.
(9) Recording procedures or equipment required to accomplish the objective tests.
(10) The following information for each objective test designated in Attachment 2 of this appendix, Table C2A, as applicable to the qualification level sought:
(a) Name of the test.
(b) Objective of the test.
(c) Initial conditions.
(d) Manual test procedures.
(e) Automatic test procedures (if applicable).
(f) Method for evaluating FFS objective test results.
(g) List of all relevant parameters driven or constrained during the automatically conducted test(s).
(h) List of all relevant parameters driven or constrained during the manually conducted test(s).
(i) Tolerances for relevant parameters.
(j) Source of Validation Data (document and page number).
(k) Copy of the Validation Data (if located in a separate binder, a cross reference for the identification and page number for pertinent data location must be provided).
(l) Simulator Objective Test Results as obtained by the sponsor. Each test result must reflect the date completed and must be clearly labeled as a product of the device being tested.
f. A convertible FFS is addressed as a separate FFS for each model and series helicopter to which it will be converted and for the FAA qualification level sought. If a sponsor seeks qualification for two or more models of a helicopter type using a convertible FFS, the sponsor must submit a QTG for each helicopter model, or a QTG for the first helicopter model and a supplement to that QTG for each additional helicopter model. The responsible Flight Standards office will conduct evaluations for each helicopter model.
g. Form and manner of presentation of objective test results in the QTG:
(1) The sponsor's FFS test results must be recorded in a manner acceptable to the responsible Flight Standards office, that allows easy comparison of the FFS test results to the validation data (e.g., use of a multi-channel recorder, line printer, cross plotting, overlays, transparencies).
(2) FFS results must be labeled using terminology common to helicopter parameters as opposed to computer software identifications.
(3) Validation data documents included in a QTG may be photographically reduced only if such reduction will not alter the graphic scaling or cause difficulties in scale interpretation or resolution.
(4) Scaling on graphical presentations must provide the resolution necessary to evaluate the parameters shown in Attachment 2, Table C2A of this appendix.
(5) Tests involving time histories, data sheets (or transparencies thereof) and FFS test results must be clearly marked with appropriate reference points to ensure an accurate comparison between the FFS and the helicopter with respect to time. Time histories recorded via a line printer are to be clearly identified for cross plotting on the helicopter data. Over-plots must not obscure the reference data.
h. The sponsor may elect to complete the QTG objective and subjective tests at the manufacturer's facility or at the sponsor's training facility. If the tests are conducted at the manufacturer's facility, the sponsor must repeat at least one-third of the tests at the sponsor's training facility in order to substantiate FFS performance. The QTG must be clearly annotated to indicate when and where each test was accomplished. Tests conducted at the manufacturer's facility and at the sponsor's training facility must be conducted after the FFS is assembled with systems and sub-systems functional and operating in an interactive manner. The test results must be submitted to the responsible Flight Standards office.
i. The sponsor must maintain a copy of the MQTG at the FFS location.
j. All FFSs for which the initial qualification is conducted after May 30, 2014, must have an electronic MQTG (eMQTG) including all objective data obtained from helicopter testing, or another approved source (reformatted or digitized), together with correlating objective test results obtained from the performance of the FFS (reformatted or digitized) as prescribed in this appendix. The eMQTG must also contain the general FFS performance or demonstration results (reformatted or digitized) prescribed in this appendix, and a description of the equipment necessary to perform the initial qualification evaluation and the continuing qualification evaluations. The eMQTG must include the original validation data used to validate FFS performance and handling qualities in either the original digitized format from the data supplier or an electronic scan of the original time-history plots that were provided by the data supplier. A copy of the eMQTG must be provided to the responsible Flight Standards office.
k. All other FFSs not covered in subparagraph “j” must have an electronic copy of the MQTG by May 30, 2014. An electronic copy of the MQTG must be provided to the responsible Flight Standards office. This may be provided by an electronic scan presented in a Portable Document File (PDF), or similar format acceptable to the responsible Flight Standards office.
l. During the initial (or upgrade) qualification evaluation conducted by the responsible Flight Standards office, the sponsor must also provide a person who is a user of the device (e.g., a qualified pilot or instructor pilot with flight time experience in that aircraft) and knowledgeable about the operation of the aircraft and the operation of the FFS.
m. Only those FFSs that are sponsored by a certificate holder as defined in Appendix F of this part will be evaluated by the responsible Flight Standards office. However, other FFS evaluations may be conducted on a case-by-case basis as the Administrator deems appropriate, but only in accordance with applicable agreements.
n. The responsible Flight Standards office will conduct an evaluation for each configuration, and each FFS must be evaluated as completely as possible. To ensure a thorough and uniform evaluation, each FFS is subjected to the general simulator requirements in Attachment 1 of this appendix, the objective tests listed in Attachment 2 of this appendix, and the subjective tests listed in Attachment 3 of this appendix. The evaluations described herein will include, but not necessarily be limited to the following:
(1) Helicopter responses, including longitudinal and lateral-directional control responses (see Attachment 2 of this appendix).
(2) Performance in authorized portions of the simulated helicopter's operating envelope, to include tasks evaluated by the responsible Flight Standards office in the areas of surface operations, takeoff, climb, cruise, descent, approach, and landing as well as abnormal and emergency operations (see Attachment 2 of this appendix).
(3) Control checks (see Attachment 1 and Attachment 2 of this appendix).
(4) Flight deck configuration (see Attachment 1 of this appendix).
(5) Pilot, flight engineer, and instructor station functions checks (see Attachment 1 and Attachment 3 of this appendix).
(6) Helicopter systems and sub-systems (as appropriate) as compared to the helicopter simulated (see Attachment 1 and Attachment 3 of this appendix).
(7) FFS systems and sub-systems, including force cueing (motion), visual, and aural (sound) systems, as appropriate (see Attachment 1 and Attachment 2 of this appendix).
(8) Certain additional requirements, depending upon the qualification level sought, including equipment or circumstances that may become hazardous to the occupants. The sponsor may be subject to Occupational Safety and Health Administration requirements.
o. The responsible Flight Standards office administers the objective and subjective tests, which includes an examination of functions. The tests include a qualitative assessment of the FFS by a pilot from the responsible Flight Standards office. The evaluation team leader may assign other qualified personnel to assist in accomplishing the functions examination and/or the objective and subjective tests performed during an evaluation when required.
(1) Objective tests provide a basis for measuring and evaluating FFS performance and determining compliance with the requirements of this part.
(2) Subjective tests provide a basis for:
(a) Evaluating the capability of the FFS to perform over a typical utilization period;
(b) Determining that the FFS satisfactorily simulates each required task;
(c) Verifying correct operation of the FFS controls, instruments, and systems; and
(d) Demonstrating compliance with the requirements of this part.
p. The tolerances for the test parameters listed in Attachment 2 of this appendix reflect the range of tolerances acceptable to the responsible Flight Standards office for FFS validation and are not to be confused with design tolerances specified for FFS manufacture. In making decisions regarding tests and test results, the responsible Flight Standards office relies on the use of operational and engineering judgment in the application of data (including consideration of the way in which the flight test was flown and way the data was gathered and applied), data presentations, and the applicable tolerances for each test.
q. In addition to the scheduled continuing qualification evaluation, each FFS is subject to evaluations conducted by the responsible Flight Standards office at any time without prior notification to the sponsor. Such evaluations would be accomplished in a normal manner (i.e., requiring exclusive use of the FFS for the conduct of objective and subjective tests and an examination of functions) if the FFS is not being used for flight crewmember training, testing, or checking. However, if the FFS were being used, the evaluation would be conducted in a non-exclusive manner. This non-exclusive evaluation will be conducted by the FFS evaluator accompanying the check airman, instructor, Aircrew Program Designee (APD), or FAA inspector aboard the FFS along with the student(s) and observing the operation of the FFS during the training, testing, or checking activities.
r. Problems with objective test results are handled as follows:
(1) If a problem with an objective test result is detected by the evaluation team during an evaluation, the test may be repeated or the QTG may be amended.
(2) If it is determined that the results of an objective test do not support the level requested but do support a lower level, the responsible Flight Standards office may qualify the FFS at that lower level. For example, if a Level D evaluation is requested and the FFS fails to meet sound test tolerances, it could be qualified at Level C.
s. After an FFS is successfully evaluated, the responsible Flight Standards office issues a certificate of qualification (COQ) to the sponsor. The responsible Flight Standards office recommends the FFS to the TPAA, who will approve the FFS for use in a flight training program. The COQ will be issued at the satisfactory conclusion of the initial or continuing qualification evaluation and will list the tasks for which the FFS is qualified, referencing the tasks described in Table C1B in Attachment 1 of this appendix. However, it is the sponsor's responsibility to obtain TPAA approval prior to using the FFS in an FAA-approved flight training program.
t. Under normal circumstances, the responsible Flight Standards office establishes a date for the initial or upgrade evaluation within ten (10) working days after determining that a complete QTG is acceptable. Unusual circumstances may warrant establishing an evaluation date before this determination is made. A sponsor may schedule an evaluation date as early as 6 months in advance. However, there may be a delay of 45 days or more in rescheduling and completing the evaluation if the sponsor is unable to meet the scheduled date. See Attachment 4, of this appendix, Figure C4A, Sample Request for Initial, Upgrade, or Reinstatement Evaluation.
u. The numbering system used for objective test results in the QTG should closely follow the numbering system set out in Attachment 2, FFS Objective Tests, Table C2A of this appendix.
v. Contact the responsible Flight Standards office for additional information regarding the preferred qualifications of pilots used to meet the requirements of § 60.15(d).
w. Examples of the exclusions for which the FFS might not have been subjectively tested by the sponsor or the responsible Flight Standards office and for which qualification might not be sought or granted, as described in § 60.15(g)(6), include takeoffs and landing from slopes and pinnacles.
No additional regulatory or informational material applies to § 60.16, Additional Qualifications for a Currently Qualified FFS.
a. In instances where a sponsor plans to remove an FFS from active status for a period of less than two years, the following procedures apply:
(1) The responsible Flight Standards office must be notified in writing and the notification must include an estimate of the period that the FFS will be inactive.
(2) Continuing Qualification evaluations will not be scheduled during the inactive period.
(3) The responsible Flight Standards office will remove the FFS from the list of qualified FSTDs on a mutually established date not later than the date on which the first missed continuing qualification evaluation would have been scheduled.
(4) Before the FFS is restored to qualified status, it must be evaluated by the responsible Flight Standards office. The evaluation content and the time required to accomplish the evaluation is based on the number of continuing qualification evaluations and sponsor-conducted quarterly inspections missed during the period of inactivity.
(5) The sponsor must notify the responsible Flight Standards office of any changes to the original scheduled time out of service.
b. Simulators qualified prior to May 30, 2008, are not required to meet the general simulation requirements, the objective test requirements, and the subjective test requirements of attachments 1, 2, and 3, of this appendix as long as the simulator continues to meet the test requirements contained in the MQTG developed under the original qualification basis.
c. After May 30, 2009, each visual scene or airport model beyond the minimum required for the FFS qualification level that is installed in and available for use in a qualified FFS must meet the requirements described in Attachment 3 of this appendix.
d. Simulators qualified prior to May 30, 2008, may be updated. If an evaluation is deemed appropriate or necessary by the responsible Flight Standards office after such an update, the evaluation will not require an evaluation to standards beyond those against which the simulator was originally qualified.
e. Other certificate holders or persons desiring to use an FFS may contract with FFS sponsors to use FFSs previously qualified at a particular level for a helicopter type and approved for use within an FAA-approved flight training program. Such FFSs are not required to undergo an additional qualification process, except as described in § 60.16.
f. Each FFS user must obtain approval from the appropriate TPAA to use any FFS in an FAA-approved flight training program.
g. The intent of the requirement listed in § 60.17(b), for each FFS to have an SOQ within 6 years, is to have the availability of that statement (including the configuration list and the limitations to authorizations) to provide a complete picture of the FFS inventory regulated by the FAA. The issuance of the statement will not require any additional evaluation or require any adjustment to the evaluation basis for the FFS.
h. Downgrading of an FFS is a permanent change in qualification level and will necessitate the issuance of a revised SOQ to reflect the revised qualification level, as appropriate. If a temporary restriction is placed on an FFS because of a missing, malfunctioning, or inoperative component or on-going repairs, the restriction is not a permanent change in qualification level. Instead, the restriction is temporary and is removed when the reason for the restriction has been resolved.
i. The responsible Flight Standards office will determine the evaluation criteria for an FFS that has been removed from active status. The criteria will be based on the number of continuing qualification evaluations and quarterly inspections missed during the period of inactivity. For example, if the FFS were out of service for a 1 year period, it would be necessary to complete the entire QTG, since all of the quarterly evaluations would have been missed. The responsible Flight Standards office will also consider how the FFS was stored, whether parts were removed from the FFS and whether the FFS was disassembled.
j. The FFS will normally be requalified using the FAA-approved MQTG and the criteria that was in effect prior to its removal from qualification. However, inactive periods of 2 years or more will require requalification under the standards in effect and current at the time of requalification.
a. The sponsor must conduct a minimum of four evenly spaced inspections throughout the year. The objective test sequence and content of each inspection must be developed by the sponsor and must be acceptable to the responsible Flight Standards office.
b. The description of the functional preflight check must be contained in the sponsor's QMS.
c. Record “functional preflight” in the FFS discrepancy log book or other acceptable location, including any item found to be missing, malfunctioning, or inoperative.
d. During the continuing qualification evaluation conducted by the responsible Flight Standards office, the sponsor must also provide a person knowledgeable about the operation of the aircraft and the operation of the FFS.
e. The responsible Flight Standards office will conduct continuing qualification evaluations every 12 months unless:
(1) The responsible Flight Standards office becomes aware of discrepancies or performance problems with the device that warrants more frequent evaluations; or
(2) The sponsor implements a QMS that justifies less frequent evaluations. However, in no case shall the frequency of a continuing qualification evaluation exceed 36 months.
f. The sponsor's test sequence and the content of each quarterly inspection required in § 60.19(a)(1) should include a balance and a mix from the objective test requirement areas listed as follows:
(1) Performance.
(2) Handling qualities.
(3) Motion system (where appropriate).
(4) Visual system (where appropriate).
(5) Sound system (where appropriate).
(6) Other FFS systems.
g. If the evaluator plans to accomplish specific tests during a normal continuing qualification evaluation that requires the use of special equipment or technicians, the sponsor will be notified as far in advance of the evaluation as practical; but not less than 72 hours. Examples of such tests include latencies, control dynamics, sounds and vibrations, motion, and/or some visual system tests.
h. The continuing qualification evaluations, described in § 60.19(b), will normally require 4 hours of FFS time. However, flexibility is necessary to address abnormal situations or situations involving aircraft with additional levels of complexity (e.g., computer controlled aircraft). The sponsor should anticipate that some tests may require additional time. The continuing qualification evaluations will consist of the following:
(1) Review of the results of the quarterly inspections conducted by the sponsor since the last scheduled continuing qualification evaluation.
(2) A selection of approximately 8 to 15 objective tests from the MQTG that provide an adequate opportunity to evaluate the performance of the FFS. The tests chosen will be performed either automatically or manually and should be able to be conducted within approximately one-third (1/3) of the allotted FFS time.
(3) A subjective evaluation of the FFS to perform a representative sampling of the tasks set out in attachment 3 of this appendix. This portion of the evaluation should take approximately two-thirds (2/3) of the allotted FFS time.
(4) An examination of the functions of the FFS may include the motion system, visual system, sound system, instructor operating station, and the normal functions and simulated malfunctions of the simulated helicopter systems. This examination is normally accomplished simultaneously with the subjective evaluation requirements.
No additional regulatory or informational material applies to § 60.20. Logging FFS Discrepancies.
No additional regulatory or informational material applies to § 60.21, Interim Qualification of FFSs for New Helicopter Types or Models.
a. The notification described in § 60.23(c)(2) must include a complete description of the planned modification, with a description of the operational and engineering effect the proposed modification will have on the operation of the FFS and the results that are expected with the modification incorporated.
b. Prior to using the modified FFS:
(1) All the applicable objective tests completed with the modification incorporated, including any necessary updates to the MQTG (e.g., accomplishment of FSTD Directives) must be acceptable to the responsible Flight Standards office; and
(2) The sponsor must provide the responsible Flight Standards office with a statement signed by the MR that the factors listed in § 60.15(b) are addressed by the appropriate personnel as described in that section.
(3) FSTD Directives are considered modifications of an FFS. See Attachment 4 of this appendix for a sample index of effective FSTD Directives. See Attachment 6 of this appendix for a list of all effective FSTD Directives applicable to Helicopter FFSs.
a. The sponsor's responsibility with respect to § 60.25(a) is satisfied when the sponsor fairly and accurately advises the user of the current status of an FFS, including any missing, malfunctioning, or inoperative (MMI) component(s).
b. It is the responsibility of the instructor, check airman, or representative of the administrator conducting training, testing, or checking to exercise reasonable and prudent judgment to determine if any MMI component is necessary for the satisfactory completion of a specific maneuver, procedure, or task.
c. If the 29th or 30th day of the 30-day period described in § 60.25(b) is on a Saturday, a Sunday, or a holiday, the FAA will extend the deadline until the next business day.
d. In accordance with the authorization described in § 60.25(b), the sponsor may develop a discrepancy prioritizing system to accomplish repairs based on the level of impact on the capability of the FFS. Repairs having a larger impact on FFS capability to provide the required training, evaluation, or flight experience will have a higher priority for repair or replacement.
If the sponsor provides a plan for how the FFS will be maintained during its out-of-service period (e.g., periodic exercise of mechanical, hydraulic, and electrical systems; routine replacement of hydraulic fluid; control of the environmental factors in which the FFS is to be maintained) there is a greater likelihood that the responsible Flight Standards office will be able to determine the amount of testing required for requalification.
If the sponsor provides a plan for how the FFS will be maintained during its out-of-service period (e.g., periodic exercise of mechanical, hydraulic, and electrical systems; routine replacement of hydraulic fluid; control of the environmental factors in which the FFS is to be maintained) there is a greater likelihood that the responsible Flight Standards office will be able to determine the amount of testing required for requalification.
a. FFS modifications can include hardware or software changes. For FFS modifications involving software programming changes, the record required by § 60.31(a)(2) must consist of the name of the aircraft system software, aerodynamic model, or engine model change, the date of the change, a summary of the change, and the reason for the change.
b. If a coded form for record keeping is used, it must provide for the preservation and retrieval of information with appropriate security or controls to prevent the inappropriate alteration of such records after the fact.
No additional regulatory or informational material applies to § 60.37, FFS Qualification on the Basis of a Bilateral Aviation Safety Agreement (BASA).
a. Certain requirements included in this appendix must be supported with an SOC as defined in Appendix F of this part, which may include objective and subjective tests. The requirements for SOCs are indicated in the “General Simulator Requirements” column in Table C1A of this appendix.
b. Table C1A describes the requirements for the indicated level of FFS. Many devices include operational systems or functions that exceed the requirements outlined in this section. However, all systems will be tested and evaluated in accordance with this appendix to ensure proper operation.
a. This attachment describes the general simulator requirements for qualifying a helicopter FFS. The sponsor should also consult the objective tests in Attachment 2 of this appendix and the examination of functions and subjective tests listed in Attachment 3 of this appendix to determine the complete requirements for a specific level simulator.
b. The material contained in this attachment is divided into the following categories:
(1) General flight deck configuration.
(2) Simulator programming.
(3) Equipment operation.
(4) Equipment and facilities for instructor/evaluator functions.
(5) Motion system.
(6) Visual system.
(7) Sound system.
c. Table C1A provides the standards for the General Simulator Requirements.
d. Table C1B provides the tasks that the sponsor will examine to determine whether the FFS satisfactorily meets the requirements for flight crew training, testing, and experience, and provides the tasks for which the simulator may be qualified.
e. Table C1C provides the functions that an instructor/check airman must be able to control in the simulator.
f. It is not required that all of the tasks that appear on the List of Qualified Tasks (part of the SOQ) be accomplished during the initial or continuing qualification evaluation.
g. Table C1A addresses only Levels B, C, and D helicopter simulators because there are no Level A Helicopter simulators.
Table C1A—Minimum Simulator Requirements
| Entry No. | QPS requirements | Simulator levels | Information |
| General simulator requirements | B | C | D | Notes |
| 1. | General Flight Deck Configuration |
| 1.a. | The simulator must have a flight deck that is a replica of the helicopter being simulated The simulator must have controls, equipment, observable flight deck indicators, circuit breakers, and bulkheads properly located, functionally accurate and replicating the helicopter. The direction of movement of controls and switches must be identical to that in the helicopter. Pilot seats must afford the capability for the occupant to be able to achieve the design “eye position” established for the helicopter being simulated. Equipment for the operation of the flight deck windows must be included, but the actual windows need not be operable. Fire axes, extinguishers, and spare light bulbs must be available in the FFS but may be relocated to a suitable location as near as practical to the original position. |
| Fire axes, landing gear pins, and any similar purpose instruments need only be represented in silhouette | X | X | X | For simulator purposes, the flight deck consists of all that space forward of a cross section of the fuselage at the most extreme aft setting of the pilots' seats including additional, required flight crewmember duty stations and those required bulkheads aft of the pilot seats. For clarification, bulkheads containing only items such as landing gear pin storage compartments, fire axes and extinguishers, spare light bulbs, and aircraft documents pouches are not considered essential and may be omitted. |
| 1.b. | Those circuit breakers that affect procedures or result in observable flight deck indications must be properly located and functionally accurate | X | X | X |
| 2. | Programming |
| 2.a. | A flight dynamics model that accounts for various combinations of air speed and power normally encountered in flight must correspond to actual flight conditions, including the effect of change in helicopter attitude, aerodynamic and propulsive forces and moments, altitude, temperature, mass, center of gravity location, and configuration An SOC is required | X | X | X |
| 2.b. | The simulator must have the computer capacity, accuracy, resolution, and dynamic response needed to meet the qualification level sought An SOC is required | X | X | X |
| 2.c. | Ground handling (where appropriate) and aerodynamic programming must include the following: |
| 2.c.1. | Ground effect Level B does not require hover programming An SOC is required | X | X | X | Applicable areas include flare and touch down from a running landing as well as for in-ground-effect (IGE) hover. |
| A reasonable simulation of ground effect includes modeling of lift, drag, pitching moment, trim, and power while in ground effect. 2.c.2. | Ground reaction Level B does not require hover programming An SOC is required | X | X | X | Reaction of the helicopter upon contact with the landing surface during landing (e.g., strut deflection, tire or skid friction, side forces) may differ with changes in gross weight, airspeed, rate of descent on touchdown, and slide slip. 2.d. | The simulator must provide for manual and automatic testing of simulator hardware and software programming to determine compliance with simulator objective tests as prescribed in Attachment 2 of this appendix An SOC is required | X | X | This may include an automated system, which could be used for conducting at least a portion of the QTG tests. Automatic “flagging” of out-of-tolerance situations is encouraged. 2.e. | The relative responses of the motion system, visual system, and flight deck instruments must be measured by latency tests or transport delay tests. |
| Motion onset must occur before the end of the scan of that video field. Instrument response may not occur prior to motion onset. Test results must be within the following limits: | The intent is to verify that the simulator provides instrument, motion, and visual cues that are like the helicopter responses within the stated time delays. It is preferable motion onset occur before the start of the visual scene change (the start of the scan of the first video field containing different information). For helicopter response, acceleration in the appropriate corresponding rotational axis is preferred. |
| 2.e.1. | Response must be within 150 milliseconds of the helicopter response | X |
| 2.e.2. | Response must be within 100 milliseconds of the helicopter response | X | X |
| 2.f. | The simulator must simulate brake and tire failure dynamics (including antiskid failure, if appropriate) An SOC is required. | X | X | The simulator should represent the motion (in the appropriate axes) and the directional control characteristics of the helicopter when experiencing simulated brake or tire failures. 2.g. | The aerodynamic modeling in the simulator must include: (1) Ground effect, (2) Effects of airframe and rotor icing (if applicable), (3) Aerodynamic interference effects between the rotor wake and fuselage, (4) Influence of the rotor on control and stabilization systems, (5) Representations of settling with power, and (6) Retreating blade stall. An SOC is required. | X | X | See Attachment 2 of this appendix for further information on ground effect. |
| 2.h. | The simulator must provide for realistic mass properties, including gross weight, center of gravity, and moments of inertia as a function of payload and fuel loading An SOC is required. | X | X | X |
| 3. | Equipment Operation |
| 3.a. | All relevant instrument indications involved in the simulation of the helicopter must automatically respond to control movement or external disturbances to the simulated helicopter; e.g., turbulence or windshear. Numerical values must be presented in the appropriate units | X | X | X |
| 3.b. | Communications, navigation, caution, and warning equipment must be installed and operate within the tolerances applicable for the helicopter being simulated | X | X | X | See Attachment 3 of this appendix for further information regarding long-range navigation equipment. |
| 3.c. | Simulated helicopter systems must operate as the helicopter systems operate under normal, abnormal, and emergency operating conditions on the ground and in flight | X | X | X |
| 3.d. | The simulator must provide pilot controls with control forces and control travel that correspond to the simulated helicopter. The simulator must also react in the same manner as the helicopter under the same flight conditions | X | X | X |
| 3.e. | Simulator control feel dynamics must replicate the helicopter simulated. This must be determined by comparing a recording of the control feel dynamics of the simulator to helicopter measurements. For initial and upgrade evaluations, the control dynamic characteristics must be measured and recorded directly from the flight deck controls, and must be accomplished in takeoff, cruise, and landing conditions and configurations | X | X |
| 4. | Instructor/Evaluator Facilities |
| 4.a. | In addition to the flight crewmember stations, the simulator must have at least two suitable seats for the instructor/check airman and FAA inspector. |
| These seats must provide adequate vision to the pilot's panel and forward windows. All seats other than flight crew seats need not represent those found in the helicopter but must be adequately secured to the floor and equipped with similar positive restraint devices | X | X | X | The responsible Flight Standards office will consider alternatives to this standard for additional seats based on unique flight deck configurations. |
| 4.b. | The simulator must have controls that enable the instructor/evaluator to control all required system variables and insert all abnormal or emergency conditions into the simulated helicopter systems as described in the sponsor's FAA-approved training program, or as described in the relevant operating manual as appropriate | X | X | X |
| 4.c. | The simulator must have instructor controls for all environmental effects expected to be available at the IOS; e.g., clouds, visibility, icing, precipitation, temperature, storm cells, and wind speed and direction | X | X | X |
| 4.d. | The simulator must provide the instructor or evaluator the ability to present ground and air hazards | X | X | For example, another aircraft crossing the active runway and converging airborne traffic. 4.e. | The simulator must provide the instructor or evaluator the ability to present the effect of re-circulating dust, water vapor, or snow conditions that develop as a result of rotor downwash | X | X | This is a selectable condition that is not required for all operations on or near the surface. |
| 5. | Motion System |
| 5.a. | The simulator must have motion (force) cues perceptible to the pilot that are representative of the motion in a helicopter | X | X | X | For example, touchdown cues should be a function of the rate of descent (RoD) of the simulated helicopter. |
| 5.b. | The simulator must have a motion (force cueing) system with a minimum of three degrees of freedom (at least pitch, roll, and heave) An SOC is required. | X |
| 5.c. | The simulator must have a motion (force cueing) system that produces cues at least equivalent to those of a six-degrees-of-freedom, synergistic platform motion system (i.e., pitch, roll, yaw, heave, sway, and surge) An SOC is required. | X | X |
| 5.d. | The simulator must provide for the recording of the motion system response time An SOC is required. | X | X | X |
| 5.e. | The simulator must provide motion effects programming to include the following: |
| (1) Runway rumble, oleo deflections, effects of ground speed, uneven runway, characteristics. | X | X | X |
| (2) Buffets due to transverse flow effects. |
| (3) Buffet during extension and retraction of landing gear. |
| (4) Buffet due to retreating blade stall. |
| (5) Buffet due to vortex ring (settling with power). |
| (6) Representative cues resulting from touchdown. |
| (7) High |
| speed rotor vibrations. |
| (8) Tire failure dynamics | X | X |
| (9) Engine malfunction and engine damage |
| (10) Airframe ground strike |
| (11) Motion vibrations that result from atmospheric disturbances | X | For air turbulence, general purpose disturbance models are acceptable if, when used, they produce test results that approximate demonstrable flight test data. 5.f. | The simulator must provide characteristic motion vibrations that result from operation of the helicopter (for example, retreating blade stall, extended landing gear, settling with power) in so far as vibration marks an event or helicopter state, which can be sensed in the flight deck | X | The simulator should be programmed and instrumented in such a manner that the characteristic buffet modes can be measured and compared to helicopter data. 6. | Visual System | Additional horizontal field-of-view capability may be added at the sponsor's discretion provided the minimum field-of-view is retained. |
| 6.a. | The simulator must have a visual system providing an out-of-the-flight deck view | X | X | X |
| 6.b. | The simulator must provide a continuous field-of-view of at least 75° horizontally and 30° vertically per pilot seat. Both pilot seat visual systems must be operable simultaneously. The minimum horizontal field-of-view coverage must be plus and minus one-half ( 1/2) of the minimum continuous field-of-view requirement, centered on the zero degree azimuth line relative to the aircraft fuselage. An SOC must explain the geometry of the installation An SOC is required. | X |
| 6.c. | The simulator must provide a continuous visual field-of-view of at least 146° horizontally and 36° vertically per pilot seat. Both pilot seat visual systems must be operable simultaneously. Horizontal field-of-view is centered on the zero degree azimuth line relative to the aircraft fuselage. |
| The minimum horizontal field-of-view coverage must be plus and minus one-half ( 1/2) of the minimum continuous field-of-view requirement, centered on the zero degree azimuth line relative to the aircraft fuselage. An SOC must explain the geometry of the installation. Capability for a field-of-view in excess of the minimum is not required for qualification at Level C. However, where specific tasks require extended fields of view beyond the 146º by 36º (e.g., to accommodate the use of “chin windows” where the accommodation is either integral with or separate from the primary visual system display), then the extended fields of view must be provided. When considering the installation and use of augmented fields of view, the sponsor must meet with the NSPM to determine the training, testing, checking, and experience tasks for which the augmented field-of-view capability may be required An SOC is required. | X | Optimization of the vertical field-of-view may be considered with respect to the specific helicopter flight deck cut-off angle. |
| The sponsor may request the responsible Flight Standards office to evaluate the FFS for specific authorization(s) for the following: (1) Specific areas within the database needing higher resolution to support landings, take-offs and ground cushion exercises and training away from a heliport, including elevated heliport, helidecks and confined areas. (2) For cross-country flights, sufficient scene details to allow for ground to map navigation over a sector length equal to 30 minutes at an average cruise speed. (3) For offshore airborne radar approaches (ARA), harmonized visual/radar representations of installations. 6.d. | The simulator must provide a continuous visual field-of-view of at least 176° horizontally and 56° vertically per pilot seat. Both pilot seat visual systems must be operable simultaneously. Horizontal field-of-view is centered on the zero degree azimuth line relative to the aircraft fuselage. |
| The minimum horizontal field-of-view coverage must be plus and minus one-half ( 1/2) of the minimum continuous field-of-view requirement, centered on the zero degree azimuth line relative to the aircraft fuselage. An SOC must explain the geometry of the installation. Capability for a field-of-view in excess of the minimum is not required for qualification at Level D. However, where specific tasks require extended fields of view beyond the 176º by 56º (e.g., to accommodate the use of “chin windows” where the accommodation is either integral with or separate from the primary visual system display), then the extended fields of view must be provided. When considering the installation and use of augmented fields of view, the sponsor must meet with the responsible Flight Standards office to determine the training, testing, checking, and experience tasks for which the augmented field-of-view capability may be required An SOC is required. | X | Optimization of the vertical field-of-view may be considered with respect to the specific helicopter flight deck cut-off angle. |
| The sponsor may request the responsible Flight Standards office to evaluate the FFS for specific authorization(s) for the following: (1) Specific areas within the database needing higher resolution to support landings, take-offs and ground cushion exercises and training away from a heliport, including elevated heliport, helidecks and confined areas. (2) For cross-country flights, sufficient scene details to allow for ground to map navigation over a sector length equal to 30 minutes at an average cruise speed. (3) For offshore airborne radar approaches (ARA), harmonized visual/radar representations of installations. 6.e. | The visual system must be free from optical discontinuities and artifacts that create non-realistic cues | X | X | X | Nonrealistic cues might include image “swimming” and image “roll-off,” that may lead a pilot to make incorrect assessments of speed, acceleration and/or situational awareness. |
| 6.f. | The simulator must have operational landing lights for night scenes.Where used, dusk (or twilight) scenes require operational landing lights. | X | X | X |
| 6.g. | The simulator must have instructor controls for the following: (1) Visibility in statute miles (kilometers) and runway visual range (RVR) in ft. (meters). |
| (2) Airport or landing area selection (3) Airport or landing area lighting | X | X | X |
| 6.h. | Each airport scene displayed must include the following: (1) Airport runways and taxiways (2) Runway definition (a) Runway surface and markings (b) Lighting for the runway in use, including runway threshold, edge, centerline, touchdown zone, VASI (or PAPI), and approach lighting of appropriate colors, as appropriate (c) Taxiway lights | X | X | X |
| 6.i. | The simulator must provide visual system compatibility with dynamic response programming | X | X | X |
| 6.j. | The simulator must show that the segment of the ground visible from the simulator flight deck is the same as from the helicopter flight deck (within established tolerances) when at the correct airspeed and altitude above the touchdown zone | X | X | X | This will show the modeling accuracy of the scene with respect to a predetermined position from the end of the runway “in use. |
| 6.k. | The simulator must provide visual cues necessary to assess rate of change of height, height AGL, and translational displacement and rates during takeoffs and landings | X |
| 6.l. | The simulator must provide visual cues necessary to assess rate of change of height, height AGL, as well as translational displacement and rates during takeoff, low altitude/low airspeed maneuvering, hover, and landing | X | X |
| 6.m. | The simulator must provide for accurate portrayal of the visual environment relating to the simulator attitude | X | X | X | Visual attitude vs. simulator attitude is a comparison of pitch and roll of the horizon as displayed in the visual scene compared to the display on the attitude indicator. 6.n | The simulator must provide for quick confirmation of visual system color, RVR, focus, and intensity An SOC is required. | X | X |
| 6.o. | The simulator must be capable of producing at least 10 levels of occulting | X | X |
| 6.p. | Night Visual Scenes. |
| The simulator must provide night visual scenes with sufficient scene content to recognize the airport, the terrain, and major landmarks around the airport. The scene content must allow a pilot to successfully accomplish a visual landing. Night scenes, as a minimum, must provide presentations of sufficient surfaces with appropriate textural cues that include self-illuminated objects such as road networks, ramp lighting, and airport signage, to conduct a visual approach, a landing, and airport movement (taxi). Scenes must include a definable horizon and typical terrain characteristics such as fields, roads and bodies of water and surfaces illuminated by helicopter landing lights | X | X | X |
| 6.q. | Dusk (Twilight) Visual Scenes. The simulator must provide dusk (or twilight) visual scenes with sufficient scene content to recognize the airport, the terrain, and major landmarks around the airport. The scene content must allow a pilot to successfully accomplish a visual landing. |
| Dusk (or twilight) scenes, as a minimum, must provide full color presentations of reduced ambient intensity, sufficient surfaces with appropriate textural cues that include self-illuminated objects such as road networks, ramp lighting and airport signage, to conduct a visual approach, landing and airport movement (taxi). Scenes must include a definable horizon and typical terrain characteristics such as fields, roads and bodies of water and surfaces illuminated by representative aircraft lighting (e.g., landing lights). If provided, directional horizon lighting must have correct orientation and be consistent with surface shading effects. Total scene content must be comparable in detail to that produced by 10,000 visible textured surfaces and 15,000 visible lights with sufficient system capacity to display 16 simultaneously moving objects An SOC is required. | X | X |
| 6.r. | Daylight Visual Scenes. The simulator must have daylight visual scenes with sufficient scene content to recognize the airport, the terrain, and major landmarks around the airport. |
| The scene content must allow a pilot to successfully accomplish a visual landing. No ambient lighting may “washout” the displayed visual scene. Total scene content must be comparable in detail to that produced by 10,000 visible textured surfaces and 6,000 visible lights with sufficient system capacity to display 16 simultaneously moving objects. The visual display must be free of apparent and distracting quantization and other distracting visual effects while the simulator is in motion An SOC is required. | X | X |
| 6.s | The simulator must provide operational visual scenes that portray physical relationships known to cause landing illusions to pilots | X | X | For example: short runways, landing approaches over water, uphill or downhill runways, rising terrain on the approach path, unique topographic features. 6.t. | The simulator must provide special weather representations of light, medium, and heavy precipitation near a thunderstorm on takeoff and during approach and landing. Representations need only be presented at and below an altitude of 2,000 ft. |
| (610 m) above the airport surface and within 10 miles (16 km) of the airport | X | X |
| 6.u. | The simulator must present visual scenes of wet and snow-covered runways, including runway lighting reflections for wet conditions, and partially obscured lights for snow conditions | X | X | The responsible Flight Standards office will consider suitable alternative effects. |
| 6.v. | The simulator must present realistic color and directionality of all airport lighting | X | X |
| 7. | Sound System |
| 7.a. | The simulator must provide flight deck sounds that result from pilot actions that correspond to those that occur in the helicopter | X | X | X |
| 7.b. | Volume control, if installed, must have an indication of the sound level setting | X | X | X |
| 7.c. | The simulator must accurately simulate the sound of precipitation, windshield wipers, and other significant helicopter noises perceptible to the pilot during normal and abnormal operations, and include the sound of a crash (when the simulator is landed in an unusual attitude or in excess of the structural gear limitations); normal engine sounds; and the sounds of gear extension and retraction An SOC is required. | X | X |
| 7.d. | The simulator must provide realistic amplitude and frequency of flight deck noises and sounds. Simulator performance must be recorded, compared to amplitude and frequency of the same sounds recorded in the helicopter, and made a part of the QTG | X | |
Table C1B—Table of Tasks vs. Simulator Level
| QPS requirements | Information |
| Entry No. | Subjective requirements The simulator must be able to perform the tasks associated with that level of qualification. | Simulator levels | Notes |
| B | C | D |
1. Preflight Procedures
| 1.a. | Preflight Inspection (Flight deck Only) switches, indicators, systems, and equipment | X | X | X |
| 1.b. | APU/Engine start and run-up |
| 1.b.1. | Normal start procedures | X | X | X |
| 1.b.2. | Alternate start procedures | X | X | X |
| 1.b.3. | Abnormal starts and shutdowns (hot start, hung start) | X | X | X |
| 1.c. | Taxiing—Ground | X | X | X |
| 1.d. | Taxiing—Hover | X | X | X |
| 1.e. | Pre-takeoff Checks | X | X | X |
2. Takeoff and Departure Phase
| 2.a. | Normal takeoff |
| 2.a.1. | From ground | X | X | X |
| 2.a.2. | From hover | X | X |
| 2.a.3. | Running | X | X | X |
| 2.b. | Instrument | X | X | X |
| 2.c. | Powerplant Failure During Takeoff | X | X | X |
| 2.d. | Rejected Takeoff | X | X | X |
| 2.e. | Instrument Departure | X | X | X |
3.
Climb
| 3.a. | Normal | X | X | X |
| 3.b. | Obstacle clearance | X | X | X |
| 3.c. | Vertical | X | X | X |
| 3.d. | One engine inoperative | X | X | X |
4. In-flight Maneuvers
| 4.a. | Turns (timed, normal, steep) | X | X | X |
| 4.b. | Powerplant Failure—Multiengine Helicopters | X | X | X |
| 4.c. | Powerplant Failure—Single-Engine Helicopters | X | X | X |
| 4.d. | Recovery From Unusual Attitudes | X | X | X |
| 4.e. | Settling with Power | X | X | X |
| 4.f. | Specific Flight Characteristics incorporated into the user's FAA approved flight training program | A | A | A |
5.
Instrument Procedures
| 5.a. | Instrument Arrival | X | X | X |
| 5.b. | Holding | X | X | X |
| 5.c. | Precision Instrument Approach |
| 5.c.1. | Normal—All engines operating | X | X | X |
| 5.c.2. | Manually controlled—One or more engines inoperative | X | X | X |
| 5.d. | Non-precision Instrument Approach | X | X | X |
| 5.e. | Missed Approach |
| 5.e.1. | All engines operating | X | X | X |
| 5.e.2. | One or more engines inoperative | X | X | X |
| 5.e.3. | Stability augmentation system failure | X | X | X |
6. Landings and Approaches to Landings
| 6.a. | Visual Approaches (normal, steep, shallow) | X | X | X |
| 6.b. | Landings |
| 6.b.1. | Normal/crosswind |
| 6.b.1.a. | Running | X | X | X |
| 6.b.1.b. | From Hover | X | X |
| 6.b.2. | One or more engines inoperative | X | X | X |
| 6.b.3. | Rejected Landing | X | X | X |
7.
Normal and Abnormal Procedures
| 7.a. | Powerplant | X | X | X |
| 7.b. | Fuel System | X | X | X |
| 7.c. | Electrical System | X | X | X |
| 7.d. | Hydraulic System | X | X | X |
| 7.e. | Environmental System(s) | X | X | X |
| 7.f. | Fire Detection and Extinguisher Systems | X | X | X |
| 7.g. | Navigation and Aviation Systems | X | X | X |
| 7.h. | Automatic Flight Control System, Electronic Flight Instrument System, and Related Subsystems | X | X | X |
| 7.i. | Flight Control Systems | X | X | X |
| 7.j. | Anti-ice and Deice Systems | X | X | X |
| 7.k. | Aircraft and Personal Emergency Equipment | X | X | X |
| 7.l. | Special Missions tasks (e.g., Night Vision goggles, Forward Looking Infrared System, External Loads and as listed on the SOQ) | A | A | X |
8.
Emergency procedures (as applicable)
| 8.a. | Emergency Descent | X | X | X |
| 8.b. | Inflight Fire and Smoke Removal | X | X | X |
| 8.c. | Emergency Evacuation | X | X | X |
| 8.d. | Ditching | X | X | X |
| 8.e. | Autorotative Landing | X | X | X |
| 8.f. | Retreating blade stall recovery | X | X | X |
| 8.g. | Mast bumping | X | X | X |
| 8.h. | Loss of tail rotor effectiveness | X | X | X |
| 8.i. | Vortex recovery | X | X | X |
9. Postflight Procedures
| 9.a | After-Landing Procedures | X | X | X |
| 9.b. | Parking and Securing |
| 9.b.1. | Rotor brake operation | X | X | X |
| 9.b.2. | Abnormal/emergency procedures | X | X | X | |
Note: An “A” in the table indicates that the system, task, or procedure may be examined if the appropriate aircraft system or control is simulated in the FFS and is working properly
Table C1C—Table of Tasks vs. Simulator Level
| QPS requirements | Information |
| Entry No. | Subjective requirements The simulator must be able to perform the tasks associated with that level of qualification. | Simulator levels | Notes |
| B | C | D |
| 1. | Instructor Operating Station (IOS), as appropriate |
| 1.a. | Power switch(es) | X | X | X |
| 1.b. | Helicopter conditions | X | X | X | e.g., GW, CG, Fuel loading, Systems, Ground Crew. |
| 1.c. | Airports/Heliports/Helicopter Landing Areas | X | X | X | e.g., Selection, Surface, Presets, Lighting controls |
| 1.d. | Environmental controls. | X | X | X | e.g., Clouds, Visibility, RVR, Temp, Wind, Ice, Snow, Rain, and Windshear. |
| 1.e. | Helicopter system malfunctions (Insertion/deletion) | X | X | X |
| 1.f. | Locks, Freezes, and Repositioning | X | X | X |
| 2. | Sound Controls. |
| 2.a. | On/off/adjustment | X | X | X |
| 3. | Motion/Control Loading System |
| 3.a. | On/off/emergency stop | X | X | X |
| 4. | Observer Seats/Stations |
| 4.a. | Position/Adjustment/Positive restraint system | X | X | X | |
Table of Contents
| Paragraph No. | Title |
| 1. | Introduction. |
| 2. | Test Requirements. |
| Table C2A, Objective Tests. |
| 3. | General. |
| 4. | Control Dynamics. |
| 5. | [Reserved] |
| 6. | Motion System. |
| 7. | Sound System. |
| 8. | Additional Information About Flight Simulator Qualification for New or Derivative Helicopters. |
| 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. |
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 responsible Flight Standards office 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.
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 responsible Flight Standards office. 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 single-engine helicopter, or a hover test for a Level B simulator). Each test result is compared against the validation data described in § 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 responsible Flight Standards office 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.
f. When comparing the parameters listed to those of the helicopter, sufficient data must also be provided to verify the correct flight condition and helicopter configuration changes. For example, to show that control force is within ±0.5 pound (0.22 daN) in a static stability test, data to show the correct airspeed, power, thrust or torque, helicopter configuration, altitude, and other appropriate datum identification parameters must also be given. If comparing short period dynamics, normal acceleration may be used to establish a match to the helicopter, but airspeed, altitude, control input, helicopter configuration, and other appropriate data must also be given. All airspeed values must be properly annotated (e.g., indicated versus calibrated). In addition, the same variables must be used for comparison (e.g., compare inches to inches rather than inches to centimeters).
g. The QTG provided by the sponsor must clearly describe how the simulator will be set up and operated for each test. Each simulator subsystem may be tested independently, but overall integrated testing of the simulator must be accomplished to assure that the total simulator system meets the prescribed standards. A manual test procedure with explicit and detailed steps for completing each test must also be provided.
h. For previously qualified simulators, the tests and tolerances of this attachment may be used in subsequent continuing qualification evaluations for any given test if the sponsor has submitted a proposed MQTG revision to the responsible Flight Standards office and has received responsible Flight Standards office approval.
i. Motion System Tests:
(a) The minimum excursions, accelerations, and velocities for pitch, roll, and yaw must be measurable about a single, common reference point and must be achieved by driving one degree of freedom at a time.
(b) The minimum excursions, accelerations, and velocities for heave, sway, and surge may be measured about different, identifiable reference points and must be achieved by driving one degree of freedom at a time.
j. Tests of handling qualities must include validation of augmentation devices. FFSs for highly augmented helicopters will be validated both in the unaugmented configuration (or failure state with the maximum permitted degradation in handling qualities) and the augmented configuration. Where various levels of handling qualities result from failure states, validation of the effect of the failure is necessary. For those performance and static handling qualities tests where the primary concern is control position in the unaugmented configuration, unaugmented data are not required if the design of the system precludes any affect on control position. In those instances where the unaugmented helicopter response is divergent and non-repeatable, it may not be feasible to meet the specified tolerances. Alternative requirements for testing will be mutually agreed upon by the sponsor and the responsible Flight Standards office on a case-by-case basis.
k. Some tests will not be required for helicopters using helicopter hardware in the simulator flight deck (e.g., “helicopter modular controller”). These exceptions are noted in Table C2A of this attachment. However, in these cases, the sponsor must provide a statement that the helicopter hardware meets the appropriate manufacturer's specifications and the sponsor must have supporting information to that fact available for responsible Flight Standards office review.
l. In cases where light-class helicopters are being simulated, prior coordination with the responsible Flight Standards office on acceptable weight ranges is required. The terms “light”, “medium”, and “near maximum”, as defined in Appendix F of this part, may not be appropriate for the simulation of light-class helicopters.
m. In those cases where the objective test results authorize a “snapshot test” or a “series 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 instant of time captured by the snap shot.
n. For references on basic operating weight, see AC 120-27, Aircraft Weight and Balance; and FAA-H-8083-1, Aircraft Weight and Balance Handbook.
Table C2A—Full Flight Simulator (FFS) Objective Tests
| QPS requirements | Information |
| Test | Tolerance(s) | Flight condition | Test details | Simulator level | Notes |
| Entry No. | Title | B | C | D |
1. Performance
| 1.a. | Engine Assessment |
| 1.a.1. | Start Operations |
| 1.a.1.a | Engine start and acceleration (transient) | Light Off Time—±10% or ±1 sec., Torque—±5%, Rotor Speed—±3%, Fuel Flow—±10%, Gas Generator Speed—±5%, Power Turbine Speed—±5%, Gas Turbine Temp.—±30 °C | Ground with the Rotor Brake Used and Not Used, if applicable. | Record each engine start from the initiation of the start sequence to steady state idle and from steady state idle to operating RPM. | X | X | X |
| 1.a.1.b. | Steady State Idle and Operating RPM conditions | Torque—±3%, Rotor Speed—±1.5%, Fuel Flow—±5%, Gas Generator Speed—±2%, Power Turbine Speed—±2%, Turbine Gas Temp.—±20 °C | Ground | Record both steady state idle and operating RPM conditions. |
| May be a series of snapshot tests. | X | X | X |
| 1.a.2. | Power Turbine Speed Trim | ±10% of total change of power turbine speed, or ±0.5% change of rotor speed. | Ground | Record engine response to trim system actuation in both directions. | X | X | X |
| 1.a.3. | Engine and Rotor Speed Governing | Torque—±5%, Rotor Speed—1.5% | Climb and descent | Record results using a step input to the collective. May be conducted concurrently with climb and descent performance tests. | X | X | X |
| 1.b. | Surface Operations |
| 1.b.1. | Minimum Radius Turn | ±3 ft. (0.9m) or 20% of helicopter turn radius. | Ground | If brakes are used, brake pedal position and brake system pressure must be matched to the helicopter flight test value. | X | X | X |
| 1.b.2. | Rate of Turn vs. Pedal Deflection, Brake Application, or Nosewheel Angle, as applicable | ±10% or ±2°/sec. |
| Turn Rate. | Ground Takeoff | If brakes are used, brake pedal position and brake system pressure must be matched to the helicopter flight test value. | X | X | X |
| 1.b.3. | Taxi | Pitch Angle—±1.5°, Torque—±3%, Longitudinal Control Position—±5%, Lateral Control Position—±5%, Directional Control Position—±5%, Collective Control Position—±5% | Ground | Record results for control position and pitch attitude during ground taxi for a specific ground speed, wind speed and direction, and density altitude. | X | X | X |
| 1.b.4. | Brake Effectiveness | ±10% of time and distance. | Ground | X | X | X |
| 1.c. | Takeoff When the speed range for the following tests is less than 40 knots, the applicable airspeed tolerance may be applied to either airspeed or ground speed, as appropriate. |
| 1.c.1. | All Engines | Airspeed—±3 kt, Altitude—±20 ft (6.1m), Torque—±3%, Rotor Speed—±1.5%, Vertical Velocity—±100 fpm (0.50m/sec) or 10%, Pitch Attitude—±1.5°, Bank Attitude—±2°, Heading—±2°, Longitudinal Control Position—±10%, Lateral Control Position—±10%, Directional Control Position—±10%, Collective Control Position—±10% | Ground/Takeoff and Initial Segment of Climb. | Record results of takeoff flight path as appropriate to helicopter model simulated (running takeoff for Level B, takeoff from a hover for Level C and D). For Level B, the criteria apply only to those segments at airspeeds above effective translational lift. |
| Results must be recorded from the initiation of the takeoff to at least 200 ft (61m) AGL. | X | X | X |
| 1.c.2. | One Engine Inoperative continued takeoff. | Airspeed—±3 kt, Altitude—±20 ft (6.1m), Torque—±3%, Rotor Speed—±1.5%, Vertical Velocity—±100 fpm (0.50m/sec) or 10%, Pitch Attitude—±1.5°, Bank Attitude—±2°, Heading—±2°, Longitudinal Control Position—±10% Lateral Control Position—±10%, Directional Control Position—±10%, Collective Control Position—±10% | Ground/Takeoff; and Initial Segment of Climb. | Record takeoff flight path as appropriate to helicopter model simulated. Results must be recorded from the initiation of the takeoff to at least 200 ft (61m) AGL. | X | X | X | Because several kinds of takeoff procedures can be performed, the specific type of takeoff profile should be recorded to ensure the proper takeoff profile comparison test is used. |
| 1.c.3. | One Engine inoperative, rejected take off. | Airspeed—±3 kt, Altitude—±20 ft (6.1m), Torque—±3%, Rotor Speed—±1.5%, Pitch Attitude—±1.5°, Roll angle—±1.5°, Heading—±2°, Longitudinal Control Position—±10%, Lateral Control Position—±10%, Directional Control Position—±10%, Collective Control Position—±10%, Distance—±7.5% or ±30m (100ft). | Ground, Takeoff | Time history from the take off point to touch down. Test conditions near limiting performance. | X | X |
| 1.d. | Hover |
| Performance | Torque—±3%, Pitch Attitude—±1.5°, Bank Attitude—±1.5°, Longitudinal Control Position—±5%, Lateral Control Position—±5%, Directional Control Position—±5%, Collective Control Position—±5%. | In Ground Effect (IGE); and Out of Ground Effect (OGE). | Record results for light and heavy gross weights. May be a series of snapshot tests. | X | X |
| 1.e. | Vertical Climb |
| Performance | Vertical Velocity—±100 fpm (0.50 m/sec) or ±10%, Directional Control Position—±5%, Collective Control Position—±5%. | From OGE Hover | Record results for light and heavy gross weights. |
| May be a series of snapshot tests. | X | X |
| 1.f. | Level Flight |
| Performance and Trimmed Flight Control Positions. | Torque—±3%, Pitch Attitude—±1.5°, Sideslip Angle—±2°, Longitudinal Control Position—±5%, Lateral Control Position—±5%, Directional Control Position—±5%, Collective Control Position—±5%. | Cruise (Augmentation On and Off). | Record results for two gross weight and CG combinations with varying trim speeds throughout the airspeed envelope. May be a series of snapshot tests. | X | X | X | This test validates performance at speeds above maximum endurance airspeed. 1.g. | Climb |
| Performance and Trimmed Flight Control Positions. | Vertical Velocity—±100 fpm (6.1m/sec) or ±10%, Pitch Attitude—±1.5°, Sideslip Angle—±2°, Longitudinal Control Position—±5%, Lateral Control Position—±5%, Directional Control Position—±5%, Collective Control Position—±5%. | All engines operating; One engine inoperative; Augmentation System(s) On and Off. | Record results for two gross weight and CG combinations. The data presented must be for normal climb power conditions. |
| May be a series of snapshot tests. | X | X | X |
| 1.h. | Descent |
| 1.h.1. | Descent Performance and Trimmed Flight Control Positions. | Torque—±3%, Pitch Attitude—±1.5°, Sideslip Angle—±2°, Longitudinal Control Position—±5%, Lateral Control Position—±5%, Directional Control Position—±5%, Collective Control Position—±5%. | At or near 1,000 fpm (5 m/sec) rate of descent (RoD) at normal approach speed. Augmentation System(s) On and Off. | Results must be recorded for two gross weight and CG combinations. May be a series of snapshot tests. | X | X | X |
| 1.h.2. | Autorotation Performance and Trimmed Flight Control Positions. | Pitch Attitude—±1.5°, Sideslip Angle—±2°, Longitudinal Control Position—±5%, Lateral Control Position—±5%, Directional Control Position—±5%, Collective Control Position—±5%, Vertical Velocity—±100 fpm or 10%, Rotor Speed—±1.5%. | Steady descents. Augmentation System(s) On and Off. | Record results for two gross weight conditions. Data must be recorded for normal operating RPM. (Rotor speed tolerance applies only if collective control position is full down. |
| Data must be recorded for speeds from 50 kts, ±5 kts, through at least maximum glide distance airspeed, or maximum allowable autorotation airspeed, whichever is slower. May be a series of snapshot tests. | X | X | X |
| 1.i. | Autorotation |
| Entry | Rotor Speed—±3%, Pitch Attitude—±2°, Roll Attitude—±3°, Yaw Attitude—±5°, Airspeed—±5 kts., Vertical Velocity—±200 fpm (1.00 m/sec) or 10%. | Cruise or Climb | Record results of a rapid throttle reduction to idle. If the cruise condition is selected, comparison must be made for the maximum range airspeed. If the climb condition is selected, comparison must be made for the maximum rate of climb airspeed at or near maximum continuous power. | X | X |
| 1.j. | Landing When the speed range for tests 1.j.1., 1.j.2., or 1.j.3. is less than 40 knots, the applicable airspeed tolerance may be applied to either airspeed or ground speed, as appropriate. 1.j.1. | All Engines | Airspeed—±3 kts., Altitude—±20 ft. |
| (6.1m), Torque—±3%, Rotor Speed—±1.5%, Pitch Attitude—±1.5°, Bank Attitude—±1.5°, Heading—±2°, Longitudinal Control Position—±10%, Lateral Control Position—±10%, Directional Control Position—±10%, Collective Control Position—±10%. | Approach | Record results of the approach and landing profile as appropriate to the helicopter model simulated (running landing for Level B, or approach to a hover for Level C and D). For Level B, the criteria apply only to those segments at airspeeds above effective translational lift. | X | X | X |
| 1.j.2. | One Engine Inoperative. | Airspeed—±3 kts., Altitude—±20 ft. (6.1m), Torque—±3%, Rotor Speed—±1.5%, Pitch Attitude—±1.5°, Bank Attitude—±1.5°, Heading—±2°, Longitudinal Control Position—±10%, Lateral Control Position—±10%, Directional Control Position—±10%, Collective Control Position—±10%. | Approach | Record results for both Category A and Category B approaches and landing as appropriate to helicopter model simulated. |
| For Level B, the criteria apply only to those segments at airspeeds above effective translational lift. | X | X | X |
| 1.j.3. | Balked Landing | Airspeed—±3 kts, Altitude—±20 ft. |
| (6.1m), Torque—±3%, Rotor Speed—±1.5%, Pitch Attitude—±1.5°, Bank Attitude—±1.5°, Heading—±2°, Longitudinal Control Position—±10%, Lateral Control Position—±10%, Directional Control Position—±10%, Collective Control Position—±10%. | Approach | Record the results for the maneuver initiated from a stabilized approach at the landing decision point (LDP). | X | X | X |
| 1.j.4. | Autorotational Landing | Torque—±3%, Rotor Speed—±3%, Vertical Velocity—±100 fpm (0.50m/sec) or 10%, Pitch Attitude—±2º, Bank Attitude—±2º, Heading—±5º, Longitudinal Control Position—±10%, Lateral Control Position—±10%, Directional Control Position—±10%, Collective Control Position—±10% | Landing | Record the results of an autorotational deceleration and landing from a stabilized autorotational descent, to touch down If flight test data containing all required parameters for a complete power-off landing is not available from the aircraft manufacturer for this test and other qualified flight test personnel are not available to acquire this data, the sponsor may coordinate with the responsible Flight Standards |
| office to determine if it is appropriate to accept alternative testing means | X | X | Alternative approaches for acquiring this data may be acceptable, depending on the aircraft as well as the personnel and the data recording, reduction, and interpretation facilities to be used, are: (1) a simulated autorotational flare and reduction of rate of descent (ROD) at altitude; or (2) a power-on termination following an autorotational approach and flare. 2. Handling Qualities |
| 2.a. | Control System Mechanical Characteristics |
| For simulators requiring Static or Dynamic tests at the controls (i.e., cyclic, collective, and pedal), special test fixtures will not be required during initial or upgrade evaluations if the sponsor's QTG/MQTG shows both test fixture results and the results of an alternative approach, such as computer plots produced concurrently showing satisfactory agreement. Repeat of the alternative method during the initial or upgrade evaluation satisfies this test requirement. |
| For initial and upgrade evaluations, the control dynamic characteristics must be measured at and recorded directly from the flight deck controls, and must be accomplished in hover, climb, cruise, and autorotation | Contact the responsible Flight Standards office for clarification of any issue regarding helicopters with reversible controls or where the required validation data is not attainable. 2.a.1. | Cyclic | Breakout—±0.25 lbs. (0.112 daN) or 25%; Force—±1.0 lb. (0.224 daN) or 10%. | Ground; Static conditions with the hydraulic system (if applicable) pressurized; supplemental hydraulic pressurization system may be used. Trim On and Off. Friction Off Augmentation (if applicable) On and Off. | Record results for an uninterrupted control sweep to the stops. (This test does not apply if aircraft hardware modular controllers are used.) | X | X | X | Flight Test Data for this test does not require the rotor to be engaged/turning. |
| The phrase “if applicable” regarding stability augmentation systems means if an augmentation system is available and if this system may be operational on the ground under static conditions as described here. 2.a.2. | Collective/Pedals | Breakout—±0.5 lb. (0.224 daN) or 25%; Force—±1.0 lb. (0.224 daN) or 10%. | Ground; Static conditions with the hydraulic system (if applicable) pressurized; supplemental hydraulic pressurization system may be used. Trim On and Off. Friction Off. Augmentation (if applicable) On and Off. | Record results for an uninterrupted control sweep to the stops. | X | X | X | Flight Test Data for this test does not require the rotor to be engaged/turning. The phrase “if applicable” regarding stability augmentation system means if a stability augmentation system is available and if this system may be operational on the ground under static conditions as described here. 2.a.3. | Brake Pedal Force vs. Position. | ±5 lbs. |
| (2.224 daN) or 10%. | Ground; Static conditions. | X | X | X |
| 2.a.4. | Trim System Rate (all applicable systems) | Rate—±10%. | Ground; Static conditions. Trim On, Friction Off. | The tolerance applies to the recorded value of the trim rate. | X | X | X |
| 2.a.5. | Control Dynamics (all axes) | ±10% of time for first zero crossing and ±10 (N + 1)% of period thereafter, ±10% of amplitude of first overshoot, 20% of amplitude of 2nd and subsequent overshoots greater than 5% of initial displacement, ±1 overshoot. | Hover/Cruise, Trim On, Friction Off. | Results must be recorded for a normal control displacement in both directions in each axis. | X | X | Typically, control displacement of 25% to 50% is necessary for proper excitation. Control Dynamics for irreversible control systems may be evaluated in a ground/static condition. Additional information on control dynamics is found later in this attachment. “N” is the sequential period of a full cycle of oscillation. |
| 2.a.6. | Control System Freeplay | ±0.10 inches (±2.5 mm). | Ground; Static conditions; with the hydraulic system (if applicable) pressurized; supplemental hydraulic pressurization system may be used. | Record and compare results for all controls. | X | X | X | Flight Test Data for this test does not require the rotor to be engaged/turning. 2.b. | Low Airspeed Handling Qualities |
| 2.b.1. | Trimmed Flight Control Positions. | Torque—±3%, Pitch Attitude—±1.5°, Bank Attitude—±2°, Longitudinal Control Position—±5%. Lateral Control Position—±5%, Directional Control Position—±5%, Collective Control Position—±5%. | Translational Flight IGE—Sideward, rearward, and forward flight. Augmentation On and Off. | Record results for several airspeed increments to the translational airspeed limits and for 45 kts. forward airspeed. |
| May be a series of snapshot tests. | X | X |
| 2.b.2. | Critical Azimuth | Torque—±3%, Pitch Attitude—±1.5°, Bank Attitude—±2°, Longitudinal Control Position—±5%, Lateral Control Position—±5%, Directional Control Position—±5%, Collective Control Position—±5%. | Stationary Hover. Augmentation On and Off. | Record results for three relative wind directions (including the most critical case) in the critical quadrant. May be a series of snapshot tests. | X | X |
| 2.b.3. | Control Response |
| 2.b.3.a. | Longitudinal | Pitch Rate—±10% or ±2°/sec., Pitch Attitude Change—±10% or 1.5°. | Hover Augmentation On and Off. | Record results for a step control input. The Off-axis response must show correct trend for unaugmented cases. | X | X | This is a “short time” test conducted in a hover, in ground effect, without entering translational flight, to provide better visual reference. 2.b.3.b. | Lateral | Roll Rate—±10% or ±3°/sec., Roll Attitude Change—±10% or ±3°. | Hover Augmentation On and Off. | Record results for a step control input. |
| The Off-axis response must show correct trend for unaugmented cases. | X | X | This is a “short time” test conducted in a hover, in ground effect, without entering translational flight, to provide better visual reference. 2.b.3.c. | Directional | Yaw Rate—±10% or ±2°/sec., Heading Change—±10% or ±2°. | Hover Augmentation On and Off. | Record results for a step control input. The Off-axis response must show correct trend for unaugmented cases. | X | X | This is a “short time” test conducted in a hover, in ground effect, without entering translational flight, to provide better visual reference. 2.b.3.d. | Vertical | Normal Acceleration—±0.1 g. | Hover Augmentation On and Off. | Record results for a step control input. The Off-axis response must show correct trend for unaugmented cases. | X | X |
| 2.c. | Longitudinal Handling Qualities |
| 2.c.1. | Control Response | Pitch Rate—±10% or ±2°/sec., Pitch Attitude Change—±10% or ±1.5°. | Cruise Augmentation On and Off. | Results must be recorded for two cruise airspeeds to include minimum power required speed. |
| Record data for a step control input. The Off-axis response must show correct trend for unaugmented cases. | X | X | X |
| 2.c.2. | Static Stability | Longitudinal Control Position: ±10% of change from trim or ±0.25 in. (6.3 mm) or Longitudinal Control Force : ±0.5 lb. (0.223 daN) or ±10%. | Cruise or Climb. Autorotation. Augmentation On and Off. | Record results for a minimum of two speeds on each side of the trim speed. May be a series of snapshot tests. | X | X | X |
| 2.c.3. | Dynamic Stability |
| 2.c.3.a. | Long-Term Response. | ±10% of calculated period, ±10% of time to 1/2 or double amplitude, or ±0.02 of damping ratio.For non-periodic responses, the time history must be matched within ±3° pitch; and ±5 kts airspeed over a 20 sec period following release of the controls. | Cruise Augmentation On and Off. | For periodic responses, record results for three full cycles (6 overshoots after input completed) or that sufficient to determine time to 1/2 or double amplitude, whichever is less. |
Continue reading ↓ 120 of 291 passages shown
[Docket FAA-2002-12461, 73 FR 26490, May 9, 2008, as amended by Docket FAA-2018-0119, Amdt. 60-5, 83 FR 9170, Mar. 5, 2018; Amdt. 60-6, 83 FR 30275, June 27, 2018; Docket FAA-2022-1355, Amdt. 60-7, 87 FR 75822, Dec. 9, 2022; Amdt. No. 60-9, 90 FR 42525, Sept. 3, 2025]