title: Transportstyrelsens föreskrifter och allmänna råd om utbildningshjälpmedel för flygsimulering (FSTD), TSFS 2009:87

text: Utbildningshjälpmedel för flygsimulering ska, för att erhålla ett kvalificeringsbevis, uppfylla Joint Aviation Requirements – Flight Simulation Training Devices Aeroplane (JAR-FSTD A) eller Joint Aviation Requirements – Flight Simulation Training Devices Helicopter (JAR-FSTD H) som antogs av Joint Aviation Authorities (JAA) den 1 maj 2008. JAR- FSTD A och JAR-FSTD H finns i bilaga 1 och bilaga 2 till dessa föreskrifter. Bilagorna innehåller även Advisory Circulars Joint (ACJ) som utgör allmänna råd till dessa föreskrifter. Dessa föreskrifter ska även tillämpas när utbildningshjälpmedel för flygsimulering ska godkännas för att användas vid flygutbildning och flygprov för certifikat och behörigheter samt vid kompetenskontroller.

type: stycke

type: paragraf

text: Definitioner och förkortningar

type: rubrik

text: I dessa föreskrifter avses med behörighet anteckning i ett certifikat som fastställer speciella villkor, befogenheter eller begränsningar för certifikatet

text: Anmälan har gjorts enligt

text: Europaparlamentets och rådets direktiv 98/34/EG av den 22 juni 1998

text: om ett informationsförfarande beträffande tekniska standarder och föreskrifter (EGT L 204, 21.7.1998, s. 37, Celex 31998L0034, ändrat genom

text: Europaparlamentets och rådets direktiv 98/48/EG

text: (EGT L 217, 5.8.1998, s. 18, Celex 31998L0048).

text: flygplan luftfartyg tyngre än luften, som framdrivs av en kraftkälla och som får sin lyftkraft huvudsakligen genom luftens reaktioner mot ytor, vilka förblir fasta under givna flygtillstånd och som inte definieras som ultralätta flygplan flygprov uppvisande av färdigheter vid utfärdande av certifikat eller behörigheter, inbegripet sådana muntliga prov som kontrollanten kan kräva flygsimulator utbildningshjälpmedel för flygsimulering som har rörelsesystem, visuellt system och möjlighet till realistisk återgivning av viss typ av luftfartyg FSTD (Flight Simulation Training Devices) utbildningshjälpmedel för flygsimulering FSTD A (Flight Simulation Training Devices Aeroplane) utbildningshjälpmedel för flygsimulering flygplan FSTD H (Flight Simulation Training Devices Helicopter) utbildningshjälpmedel för flygsimulering helikopter helikopter luftfartyg tyngre än luften som får lyftkraft under flygning genom luftens reaktioner mot en eller flera motordrivna rotorer JAR (Joint Aviation Requirement) gemensamma luftfartsbestämmelser kompetens- uppvisande av färdigheter för att förlänga eller förnya kontroll behörigheter, inbegripet sådana muntliga prov som kontrollanten kan kräva OPC (Operator Proficiency Check) operatörens kompetenskontroll PC (Proficiency Check) kompetenskontroll utbildnings- teknisk utrustning som i olika grad och funktion återger hjälpmedel för ett luftfartygs förarutrymme.

text: flygsimulering

text: När det i bilaga 1 (JAR-FSTD A) eller i bilaga 2 (JAR-FSTD H) hänvisas till en JAR-publikation som har ersatts av en EG-förordning eller en certifieringsspecifikation från EASA, får JAR-publikationen inte tillämpas, såvida inte annat anges i den berörda EG-förordningen eller certifieringsspecifikationen från EASA.

text: Ömsesidigt erkännande

text: En produkt som är lagligen tillverkad eller saluförs enligt regelverk i andra medlemsstater inom Europeiska unionen, Turkiet eller Europeiska ekonomiska samarbetsområdet (EES) jämställs med produkter som uppfyller kraven i dessa föreskrifter, under förutsättning att en likvärdig säker-

text: hetsnivå uppnås genom dessa staters regelverk. Likvärdigheten på produkten ska kunna styrkas.

text: Indelning av utbildningshjälpmedel för flygsimulering (FSTD)

text: Utbildningshjälpmedel för flygsimulering som i olika grad och funktion återger ett luftfartygs förarutrymme ska användas vid utbildning, träning, prov och kompetenskontroller med flygbesättningsmedlemmar. Utbildningshjälpmedel för flygsimulering får helt eller delvis ersätta övningar i luftfartyg. Utbildningshjälpmedel för flygsimulering indelas med hänsyn till utförande och utbildningsändamål i följande kategorier: 1. flygsimulator (FFS, Full Flight Simulator), 2. flygutbildningshjälpmedel (FTD, Flight Training Device), 3. utbildningshjälpmedel för flygträning och navigationsprocedurer (FNPT, Flight and Navigation Procedures Trainer), 4. utbildningshjälpmedel för grundläggande instrumentutbildning (BITD, Basic Instrument Training Device), 5. andra utbildningshjälpmedel (OTD, Other Training Device) än FFS, FTD, FNPT eller BITD.

text: Godkännande

text: Utbildningshjälpmedel för flygsimulering ska ha ett kvalificeringsbevis utfärdat eller godkänt av Transportstyrelsen enligt kraven i bilaga 1 (JAR-FSTD A) eller bilaga 2 (JAR-FSTD H).

text: Den som använder ett utbildningshjälpmedel för flygsimulering vid utbildning, träning, prov eller kompetenskontroll ska inneha ett användargodkännande utfärdat av Transportstyrelsen. Den som ansöker om ett användargodkännande ska dokumentera att de utbildningshjälpmedel för flygsimulering som används kan simulera de funktioner och manövrar som ingår i utbildningen på ett realistiskt sätt.

text: Simulerad flygträning får ersätta övningar i luftfartyg endast i den omfattning som anges i användargodkännandet eller i Transportstyrelsens föreskrifter.

text: Funktionskrav

text: Den som innehar ett godkännande av ett utbildningshjälpmedel för flygsimulering ska säkerställa att hjälpmedlet underhålls så att det kontinuerligt uppfyller kraven enligt dessa föreskrifter med bilagor.

text: För att utbildningstid i ett utbildningshjälpmedel för flygsimulering ska få tillgodoräknas krävs att hjälpmedlet uppfyller kraven i dessa före-

text: skrifter med bilagor samt att övningarna kan genomföras på ett tillfredsställande sätt.

text: Undantag

text: Transportstyrelsen kan medge undantag från dessa föreskrifter.

text: Ikraftträdande- och övergångsbestämmelser

text: 1. Denna författning träder i kraft den 1 november 2009. 2. Genom denna författning upphävs Luftfartsverkets föreskrifter om ändring i Bestämmelser för Civil Luftfart – certifikatbestämmelser (BCL-C) 1.5 (

text: LFS 1999:98

text: ), Syntetisk flygträning, Luftfartsverkets föreskrifter om ändring i Bestämmelser för Civil Luftfart – certifikatbestämmelser (BCL-C) 8.1 (

text: LFS 1998:14

text: ), Kompletterande bestämmelser till JAR-STD 1A aeroplane flight simulators, Luftfartsverkets föreskrifter om ändring i Bestämmelser för Civil Luftfart – certifikatbestämmelser (BCL-C) 8.2 (

text: LFS 2001:28

text: ), Kompletterande bestämmelser till JAR-STD 2A aeroplane flight training devices, Luftfartsverkets föreskrifter om ändring i Bestämmelser för Civil Luftfart – certifikatbestämmelser (BCL-C) 8.3 (

text: LFS 1999:99

text: ), Kompletterande bestämmelser till JAR-STD 3A aeroplane flight and navigation procedures trainers, Luftfartsverkets föreskrifter om ändring i Bestämmelser för Civil Luftfart – certifikatbestämmelser (BCL-C) 8.4 (

text: LFS 2004:7

text: ), Kompletterande bestämmelser till JAR-STD 4A basic instrument training devices, Luftfartsverkets föreskrifter om ändring i Bestämmelser för Civil Luftfart – certifikatbestämmelser (BCL-C) 8.5 (

text: LFS 2004:8

text: ), Kompletterande bestämmelser till JAR-STD 1H helicopter flight simulators, Luftfartsverkets föreskrifter om ändring i Bestämmelser för Civil Luftfart – certifikatbestämmelser (BCL-C) 8.6 (

text: LFS 2004:9

text: ), Kompletterande bestämmelser till JAR-STD 2H helicopter flight training devices, Luftfartsverkets föreskrifter om ändring i Bestämmelser för Civil Luftfart – certifikatbestämmelser (BCL-C) 8.7 (

text: LFS 2004:10

text: ), Kompletterande bestämmelser till JAR-STD 3H helicopter flight and navigation procedures trainers, Luftfartsverkets föreskrifter om Gemensamma luftfartsbestämmelser (JAR), JAR-STD 1A Aeroplane Flight Simulators (

text: LFS 2004:11

text: ), Luftfartsverkets föreskrifter om Gemensamma luftfartsbestämmelser (JAR), JAR-STD 2A Aeroplane Flight Training Devices (

text: LFS 2001:31

text: ), Luftfartsverkets föreskrifter om Gemensamma luftfartsbestämmelser (JAR), JAR-STD 3A Aeroplane Flight and Navigation Procedures Trainers (

text: LFS 2001:32

text: ), Luftfartsverkets föreskrifter om Gemensamma luftfartsbestämmelser (JAR), JAR-STD 4 A Basic Instrument Traning Devices (

text: LFS 2004:12

text: ), Luftfartsverkets föreskrifter om Gemensamma luftfartsbestämmelser (JAR), JAR-STD 1H Helicopter Flight Simulators (

text: LFS 2004:13

text: Luftfartsverkets föreskrifter om Gemensamma luftfartsbestämmelser (JAR), JAR-STD 2H Helicopter Flight Training Devices (

text: LFS 2004:14

text: ), Luftfartsverkets föreskrifter om Gemensamma luftfartsbestämmelser (JAR), JAR-STD 3H Helicopter Flight and Navigation Procedures Trainers (

text: LFS 2004:15

text: ). 3. Äldre föreskrifter gäller fortfarande vid förlängning och förnyelse av kvalificeringsbevis för utbildningshjälpmedel som har beviljats före den 1 november 2009, under förutsättning att utbildningshjälpmedlet inte ändras till en ny kvalificeringsnivå enligt dessa föreskrifter med bilagor.

text: På Transportstyrelsens vägnar

text: STAFFAN WIDLERT Kaj Skärstrand (Luftfartsavdelningen)

text: Utgivare: Kristina Nilsson, Transportstyrelsen, Norrköping ISSN 2000-1975

text: Bilaga 1

text: JAR-FSTD A

text: Utbildningshjälpmedel för flygsimulering (flygplan)

text: Bilaga 1

text: CONTENTS (general layout)

text: JAR–FSTD A

text: AEROPLANE FLIGHT SIMULATION TRAINING DEVICES

text: FOREWORD

text: SECTION 1 – REQUIREMENTS

text: SUBPART A — APPLICABILITY SUBPART B — GENERAL SUBPART C — AEROPLANE FLIGHT SIMULATION TRAINING DEVICES

text: SECTION 2 – ADVISORY CIRCULARS JOINT (ACJ)

text: ACJ B — GENERAL ACJ C — AEROPLANE FLIGHT SIMULATION TRAINING DEVICES

text: C-1 2009-11-01

text: Bilaga 1

text: INTENTIONALLY LEFT BLANK 2009-11-01 C-2

text: Bilaga 1

text: CONTENTS (details)

text: JAR–FSTD A

text: Paragraph Page

text: SECTION 1 – REQUIREMENTS

text: General and Presentation 1-0-1

text: SUBPART A – APPLICABILITY

text: JAR–FSTD A.001 Applicability 1-A-1

text: SUBPART B – GENERAL

text: JAR–FSTD A.005 Terminology 1-B-1

text: SUBPART C – AEROPLANE FLIGHT SIMULATION TRAINING DEVICES

text: JAR–FSTD A.015 Application for FSTD Qualification 1-C-1 JAR–FSTD A.020 Validity FSTD Qualification 1-C-1 JAR–FSTD A.025 Rules governing FSTD Operators 1-C-1 JAR–FSTD A.030 Requirements for FSTDs qualified on or after 1-C-2 1 August 2008 JAR–FSTD A.031 Requirements for FFSs qualified on or after 1-C-3 1 April 1998 and before 1 August 2008 JAR–FSTD A.032 Requirements for FTDs qualified on or after 1 July 2000 1-C-3 and before 1 August 2008 JAR–FSTD A.033 Requirements for FNPTs qualified on or after 1 July 1999 1-C-3 and before 1 August 2008 JAR–FSTD A.034 Requirements for BITD qualified on or after 1 January 2003 1-C-3 and before 1 August 2008 JAR–FSTD A.035 Requirements for FFSs approved or qualified 1-C-3 before 1 April 1998 JAR–FSTD A.036 Requirements for FTDs approved or qualified 1-C-4 before 1 July 2000 JAR–FSTD A.037 Requirements for FNPTs approved or qualified 1-C-4 before 1 July 1999 JAR–FSTD A.040 Changes to qualified FSTDs 1-C-4 JAR–FSTD A.045 Interim FSTD Qualification 1-C-5 JAR–FSTD A.050 Transferability of FSTD Qualification 1-C-5 Appendix 1 to FSTD Standards 1-C-7 JAR–FSTD A.030

text: C-3 2009-11-01

text: Bilaga 1

text: General and Presentation 2-0-1

text: ACJ B – GENERAL

text: ACJ FSTD A.005 Terminology, Abbreviations 2-B-1

text: ACJ C – AEROPLANE FSTDS

text: ACJ No. 1 to FSTD Qualification – Application and Inspection 2-C-1 JAR- FSTD A.015 ACJ No. 2 to FSTD Evaluations 2-C-6 JAR- FSTD A.015 ACJ FSTD A.020 Validity of an FSTD Qualification 2-C-10 ACJ No. 1 to Quality System 2-C-10 JAR- FSTD A.025 ACJ No. 2 to BITD Operators Quality System 2-C-17 JAR-FSTD A.025 ACJ No. 3 to Installations 2-C-18 JAR-FSTD A.025 ACJ No. 1 to FSTDs qualified on or after 1 August 2008 2-C-19 JAR-FSTD A.030 Appendix 1 to ACJ No. 1 Validation Test Tolerances 2-C-112 to JAR-FSTD A.030 Appendix 2 to ACJ No. 1 Validation Data Roadmap 2-C-114 to JAR-FSTD A.030 Appendix 3 to ACJ No. 1 Data Requirements for Alternate Engines 2-C-116 to JAR-FSTD A.030 Appendix 4 to ACJ No. 1 Data Requirements for Alternate Avionics 2-C-118 to JAR-FSTD A.030 Appendix 5 to ACJ No. 1 Transport Delay Testing Method 2-C-119 to JAR-FSTD A.030 Appendix 6 to ACJ No. 1 Recurrent Evaluations – Validation Test Data Presentation 2-C-122 to JAR-FSTD A.030 Appendix 7 to ACJ No 1 Applicability 2-C-123 to JAR-FSTD A.030 Appendix 8 to ACJ No 1 General technical Requirements for FSTD Qualification 2-C-125 JAR–FSTD A.030 Levels ACJ No. 2 to Guidance on Design and Qualification of Level “A” 2-C-130 JAR-FSTD A.030 Aeroplane FFSs ACJ No. 3 to Guidance on Design and Qualification of FNPTs 2-C-132 JAR-FSTD A.030 ACJ No. 4 to Guidance on Design and Qualification of BITDs 2-C-136 JAR-FSTD A.030 ACJ No.1 to Engineering Simulator Validation Data 2-C-140 JAR-FSTD A.030(c)(1)

text: 2009-11-01 C-4

text: Bilaga 1

text: ACJ No.2 to Engineering Simulator Validation Data – Approved Guidelines 2-C-141 JAR-FSTD A.030(c)(1) ACJ to FSTD A.035 FFS Approved or Qualified before 1 April 1998 2-C-143 ACJ to FSTD A.036 FTD Approved or Qualified before 1 July 2000 2-C-145 ACJ to FSTD A.037 FNPT Approved or Qualified before 1 July 1999 2-C-146 ACJ to FSTD A.045 New Aeroplane FFS/FTD Qualification – Additional Information 2-C-147

text: INTENTIONALLY LEFT BLANK

text: C-5 2009-11-01

text: Bilaga 1

text: INTENTIONALLY LEFT BLANK 2009-11-01 C-6

text: Bilaga 1

text: FOREWORD

text: 1 The Civil Aviation Authorities of certain European countries have agreed common comprehensive and detailed aviation requirements, referred to as Joint Aviation Requirements (JARs), with a view to minimising Type Certification problems on joint ventures, to facilitate the export and import of aviation products, to make it easier for maintenance carried out in one European country to be accepted by the Civil Aviation Authority in another European country and to regulate commercial air transport operations.

text: 2 JARs are recognised by the Civil Aviation Authorities of participating countries as an acceptable basis for showing compliance with their national codes.

text: 3 The content has been prepared using the expertise available in this field as well as the ICAO Document 9625, the ‘Manual for the Qualification of Flight Simulators’ and added to where necessary by making use of existing European regulations and the Federal Aviation Requirements of the United States of America where acceptable.

text: 4 JAR–FSTD A is issued with no National Variants. It may be felt that the document does not contain all of the detailed compliance and interpretative information which some Civil Aviation Authorities and Industry organisations would like to see. However, it is accepted that JAR– FSTD A should be applied in practice and the lessons learned embodied in future amendments. The Civil Aviation Authorities of the JAA are therefore committed to early amendment in the light of experience.

text: 5 Future development of the requirements of JAR–FSTD A, including the commitment in Paragraph 4, will be in accordance with the JAA’s Notice of Proposed Amendment (NPA) procedures. These procedures allow for the amendment of JAR–FSTD A to be proposed by any organisation or person.

text: 6 The Civil Aviation Authorities have agreed they should not unilaterally initiate amendment of their national codes without having made a proposal for amendment of JAR–FSTD A in accordance with the agreed procedure.

text: 7 Definitions and abbreviations of terms used in JAR–FSTD A that are considered generally applicable are contained in JAR–1, Definitions and Abbreviations. However, definitions and abbreviations of terms used in JAR–FSTD A that are specific to a Subpart of JAR–FSTD A are normally given in the Subpart concerned or, exceptionally, in the associated compliance or interpretative material.

text: 8 Amendments to the text in JAR–FSTD A are issued as Replacement Pages. These show an effective date and have the same status and applicability as JAR–FSTD A from that date.

text: 9 New, amended and corrected text will be enclosed within heavy brackets until a subsequent ‘Amendment’ is issued.

text: 10 Comment/Response documents developed following Notices of Proposed Amendment (NPA) consultation have been produced by the JAA and are published on the JAA Internet Site: www.jaa.nl. Readers can also apply to JAA for copies of specific Comment/Response Documents as required.

text: F-1 2009-11-01

text: Bilaga 1

text: INTENTIONALLY LEFT BLANK 2009-11-01 F-2

text: Bilaga 1

text: SEC TION 1 – REQUIREMENTS

text: 1 GENERAL 1.1 This Section contains the requirements for aeroplane Flight Simulation Training Devices. 2 PRESENTATION 2.1 The requirements of JAR–FSTD A are presented in two columns on loose pages, each page being identified by the date of issue and the Amendment number under which it is amended or reissued. 2.2 Sub-headings are in italic typeface. 2.3 Explanatory Notes not forming part of the requirements appear in smaller typeface. 2.4 New, amended and corrected text will be enclosed within heavy brackets until a subsequent ‘Amendment’ is issued. 2.5 After each paragraph, the various changes and amendments, if any since the initial issue, are indicated together with their date of issue.

text: INTENTIONALLY LEFT BLANK

text: 1-0-1 2009-11-01

text: Bilaga 1

text: INTENTIONALLY LEFT BLANK 2009-11-01 1-0-2

text: Bilaga 1

text: SUBPART A – APPLICABILITY

text: JAR–FSTD A.001 Applicability

text: JAR–FSTD A as amended applies to those persons, organisations or enterprises (Flight Simulation Training Devices (FSTD) operators) or, in the case of BITDs only, manufacturers seeking initial qualification of FSTDs. The version of JAR-FSTD A agreed by the Authority and used for issue of the initial qualification shall be applicable for future recurrent qualifications of the FSTD unless recategorised. FSTD users shall also gain approval to use the FSTD as part of their approved training programmes despite the fact that the FSTD has been previously qualified.

text: INTENTIONALLY LEFT BLANK INTENTIONALLY LEFT BLANK

text: 2009-11-01 1-A-1 JAR-FSTD A

text: SECTION 1

text: Bilaga 1

text: INTENTIONALLY LEFT BLANK 2009-11-01 1-A-2 JAR-FSTD A

text: Bilaga 1

text: SUBPART B - GENERAL

text: (JAR-FSTD A.005 continued)

text: JAR–FSTD A.005 Terminology for training where a complete flight deck environment

text: (See ACJ to FSTD A.005) is not necessary.

text: (g) Flight Simulation Training Device User Because of the technical complexity of FSTD Approval (FSTD User Approval). The extent to which qualification, it is essential that standard terminology an FSTD of a specified Qualification Level may be is used throughout. The following principal terms and used by persons, organisations or enterprises as abbreviations shall be used in order to comply with approved by the Authority. It takes account of JAR–FSTD (A). Further terms and abbreviations are aeroplane to FSTD differences and the operating and contained in ACJ to FSTD A.005. training ability of the organisation.

text: (a) Flight Simulation Training Device (h) Flight Simulation Training Device Operator (FSTD). A training device which is a Full Flight (FSTD operator). That person, organisation or Simulator (FFS), a Flight Training Device (FTD), a enterprise directly responsible to the Authority for Flight & Navigation Procedures Trainer (FNPT) , or a requesting and maintaining the qualification of a Basic Instrument Training Device (BITD). particular FSTD.

text: (b) Full Flight Simulator (FFS). A full size (i) Flight Simulation Training Device User replica of a specific type or make, model and series (FSTD User). The person, organisation or enterprise aeroplane flight deck, including the assemblage of all requesting training, checking and testing credits equipment and computer programmes necessary to through the use of an FSTD. represent the aeroplane in ground and flight

text: operations, a visual system providing an out of the (j) Flight Simulation Training Device

text: flight deck view, and a force cueing motion system. It Qualification (FSTD Qualification). The level of

text: is in compliance with the minimum standards for FFS technical ability of an FSTD as defined in the

text: Qualification. compliance document.

text: (c) Flight Training Device (FTD). A full size (k) BITD Manufacturer. That organisation or

text: replica of a specific aeroplane type’s instruments, enterprise being directly responsible to the Authority

text: equipment, panels and controls in an open flight deck for requesting the initial BITD model qualification.

text: area or an enclosed aeroplane flight deck, including (l) BITD Model. A defined hardware and the assemblage of equipment and computer software software combination, which has obtained a programmes necessary to represent the aeroplane in qualification. Each BITD will equate to a specific ground and flight conditions to the extent of the model and be a serial numbered unit. systems installed in the device. It does not require a

text: force cueing motion or visual system. It is in (m) Qualification Test Guide (QTG). A

text: compliance with the minimum standards for a specific document designed to demonstrate that the

text: FTD Level of Qualification. performance and handling qualities of an FSTD agree

text: within prescribed limits with those of the aeroplane (d) Flight and Navigation Procedures Trainer and that all applicable regulatory requirements have (FNPT). A training device which represents the been met. The QTG includes both the aeroplane and flight deck or cockpit environment including the FSTD data used to support the validation. assemblage of equipment and computer

text: programmes necessary to represent an aeroplane or

text: class of aeroplane in flight operations to the extent

text: that the systems appear to function as in an

text: aeroplane. It is in compliance with the minimum

text: standards for a specific FNPT Level of

text: Qualification.

text: (e) Basic Instrument Training Device (BITD). A

text: ground based training device which represents the

text: student pilot‘s station of a class of aeroplanes. It may

text: use screen based instrument panels and springloaded

text: flight controls, providing a training platform for at INTENTIONALLY LEFT BLANK

text: least the procedural aspects of instrument flight.

text: (f) Other Training Device (OTD). A training aid

text: other than FFS, FTD, FNPT or BITD which provides

text: 2009-11-01 1-B-1 JAR-FSTD A

text: SECTION 1

text: Bilaga 1

text: INTENTIONALLY LEFT BLANK JAR-FSTD A 1-B-2 2009-11-01

text: Bilaga 1

text: JAR-FSTD A.020(d) (continued)

text: JAR–FSTD A.015 Application for FSTD

text: (d) The qualification of each BITD model serial

text: Qualification

text: number is valid for 36 months from the (See ACJ No. 1 to JARcommencement of operation, unless reduced by the FSTD A.015) Authority. It is the operator‘s responsibility to (See ACJ No. 2 to JARapply for the revalidation of the qualification. FSTD A.015)

text: (a) The FSTD operator requiring evaluation of a

text: FFS, FTD or FNPT shall apply to the Authority

text: JAR–FSTD A.025 Rules Governing FSTD

text: giving 3 months notice. In exceptional cases this

text: Operators

text: period may be reduced to one month at the (See ACJ No. 1 to JARdiscretion of the Authority. FSTD A.025)

text: (b) An FSTD Qualification Certificate will be (See ACJ No. 2 to JAR-

text: issued following satisfactory completion of an FSTD A.025)

text: evaluation of the FFS, FTD or FNPT by the (See ACJ No. 3 to JAR-

text: Authority. FSTD A.025)

text: (c) For BITDs the manufacturer of a new BITD The FSTD operator shall demonstrate his capability

text: model which requires evaluation shall apply to the to maintain the performance, functions and other

text: Authority giving 3 months notice. In exceptional characteristics specified for the FSTD Qualification

text: cases this period may be reduced to one month at Level as follows:

text: the discretion of the Authority. (a) Quality System

text: (d) A BITD Qualification Certificate will be issued (1) A Quality System shall be for the BITD model to the manufacturer following established and a Quality Manager designated to satisfactory completion of an initial evaluation by monitor compliance with, and the adequacy of, the Authority. This qualification certificate is valid procedures required to ensure the maintenance for any devices manufactured to this standard of the Qualification Level of FSTDs. without the need for the device to be subjected to Compliance monitoring shall include a feedback further technical evaluation. The BITD model must system to the Accountable Manager to ensure clearly be identified by a BITD model number. corrective action as necessary.

text: (e) The numbering of the BITD model must (2) The Quality System shall include a clearly define the hardware and software Quality Assurance Programme that contains configuration of the qualified BITD model. A procedures designed to verify that the specified running serial number shall follow the BITD model performance, functions and characteristics are identification number. being conducted in accordance with all

text: applicable requirements, standards and

text: procedures.

text: JAR–FSTD A.020 Validity of FSTD

text: (3) The Quality System and the Quality

text: Qualification

text: Manager shall be acceptable to the Authority. (See ACJ to JAR-FSTD

text: A.020) (4) The Quality System shall be

text: described in relevant documentation. (a) An FSTD qualification is valid for 12 months

text: unless otherwise specified by the Authority. (b) Updating. A link shall be maintained between

text: the operator’s organization, the Authority and the (b) An FSTD qualification revalidation can take relevant manufacturers to incorporate important place at any time within the 60 days prior to the modifications, especially: expiry of the validity of the qualification document.

text: The new period of validity shall continue from the (1) Aeroplane modifications that are

text: expiry date of the previous qualification document. essential for training and checking shall be

text: introduced into all affected FSTDs whether or (c) The Authority shall refuse, revoke, suspend or not enforced by an airworthiness directive. vary an FSTD qualification, if the provisions of

text: JAR–FSTD A are not satisfied. (2) Modification of FSTDs, including

text: motion and visual systems (where applicable):

text: 2009-11-01 1-C-1 JAR-FSTD A

text: Bilaga 1

text: JAR-FSTD A.025(b) (continued) (i) When essential for training JAR–FSTD A.030 Requirements for FSTD and checking, FSTD operators shall qualified on or after 1 update their FSTDs (for example in the August 2008 light of data revisions). Modifications of (See Appendix 1 to JAR– the FSTD hardware and software that FSTD A.030) affect handling, performance and systems (See ACJ No. 1 to JARoperation or any major modifications of FSTD A.030) the motion or visual system shall be (See ACJ No. 2 to JARevaluated to determine the impact on the FSTD A.030) original qualification criteria. FSTD (See ACJ No. 3 to JARoperators shall prepare amendments for FSTD A.030) any affected validation tests. The FSTD (See ACJ No. 4 to JARoperator shall test the FSTD to the new FSTD A.030) criteria. (See ACJ No. 1 to JAR- FSTD A.030(c)(1)) (ii) The Authority shall be advised (See ACJ No. 2 to JARin advance of any major changes to FSTD A.030(c)(1)) determine if the tests carried out by the FSTD operator are satisfactory. A special (a) Any FSTD submitted for initial evaluation on evaluation of the FSTD may be necessary or after 1 August 2008 will be evaluated against prior to returning it to training following applicable JAR–FSTD A criteria for the the modification. Qualification Levels applied for. Recurrent evaluations of a FSTD will be based on the same (3) BITD operators shall maintain a link version of JAR-FSTD A that was applicable for its between their own organisation, the Authority initial evaluation. An upgrade will be based on the and the BITD manufacturer to incorporate currently applicable version of JAR-FSTD A. important modifications. (b) A FSTD shall be assessed in those areas that (c) Installations. Ensure that the FSTD is housed are essential to completing the flight crewmember in a suitable environment that supports safe and training and checking process as applicable. reliable operation. (c) The FSTD shall be subjected to: (1) The FSTD operator shall ensure that the FSTD and its installation comply with the (1) Validation tests and local regulations for health and safety. However, (2) Functions & subjective tests as a minimum all FSTD occupants and maintenance personnel shall be briefed on FSTD (d) Data shall be of a standard that satisfies the safety to ensure that they are aware of all safety Authority before the FSTD can gain a Qualification equipment and procedures in the FSTD in case Level. of emergency. (e) The FSTD operator shall submit a QTG in a (2) The FSTD safety features such as form and manner that is acceptable to the emergency stops and emergency lighting shall Authority. be checked at least annually and recorded by the (f) The QTG will only be approved after FSTD operator. completion of an initial or upgrade evaluation, and (d) Additional Equipment. Where additional when all the discrepancies in the QTG have been equipment has been added to the FSTD, even addressed to the satisfaction of the Authority. After though not required for qualification, it will be inclusion of the results of the tests witnessed by the assessed to ensure that it does not adversely affect Authority, the approved QTG becomes the Master the quality of training. Therefore any subsequent QTG (MQTG), which is the basis for the FSTD modification, removal or unserviceability could qualification and subsequent recurrent FSTD affect the qualification of the device. evaluations. A copy of the MQTG shall be delivered by the BITD manufacteurer together with any BITD model delivered to an Operator. (g) The FSTD operator shall: (1) Run the complete set of tests contained within the MQTG progressively between each annual evaluation by the Authority. Results shall be dated and retained in

text: JAR-FSTD A 1-C-2 2009-11-01

text: Bilaga 1

text: JAR-FSTD A.030(g) (continued) JAR-FSTD A.033 (continued)

text: order to satisfy both the FSTD operator and the current validity period. This re-evaluation, and all

text: Authority that FSTD standards are being future re-evaluations, will be conducted in

text: maintained; and accordance with the requirements of the same

text: version of JAR-STD 3A, which was applicable for (2) Establish a Configuration Control its last evaluation prior to implementation of JAR- System to ensure the continued integrity of the FSTD A. Any upgrade will be based on the hardware and software of the qualified FSTD. currently applicable version of JAR-FSTD A.

text: JAR-FSTD A.031 Requirements for FFS JAR-FSTD A.034 Requirements for Basic qualified on or after 1 Instrument Training April 1998 and before 1 Devices (BITD) qualified August 2008 on or after 1 January 2003

text: Any FFS submitted for initial evaluation on or after and before 1 August 2008

text: 1 April 1998 and before 1 August 2008, shall Any BITD submitted for initial evaluation on or automatically be granted an equivalent after 1 January 2003 and before 1 August 2008, qualification under JAR-FSTD A with effect from shall automatically be granted an equivalent the re-evaluation conducted at the end of the qualification under JAR-FSTD A with effect from current validity period. This re-evaluation, and all the re-evaluation conducted at the end of the future re-evaluations, will be conducted in current validity period. This re-evaluation, and all accordance with the requirements of the same future re-evaluations, will be conducted in version of JAR-STD 1A, which was applicable for accordance with the requirements of the same its last evaluation prior to implementation of JARversion of JAR-STD 4A, which was applicable for FSTD A. Any upgrade will be based on the its last evaluation prior to implementation of JARcurrently applicable version of JAR-FSTD A. FSTD A. Any upgrade will be based on the

text: currently applicable version of JAR-FSTD A.

text: JAR-FSTD A.032 Requirements for Flight Training Devices (FTD) JAR–FSTD A.035 Requirements for Full qualified on or after 1 Flight Simulators July 2000 and before 1 approved or qualified August 2008 before 1 April 1998

text: Any FTD submitted for initial evaluation on or (See ACJ to JAR-FSTD

text: after 1 January 2000 and before 1 August 2008, A.035)

text: shall automatically be granted an equivalent (a) FFS approved or qualified in accordance with qualification under JAR-FSTD A with effect from national regulations of JAA Member States before the re-evaluation conducted at the end of the 1 April 1998 will either be recategorised or will current validity period. This re-evaluation, and all continue to maintain their approval under the future re-evaluations, will be conducted in Grandfather Rights provision, in accordance with accordance with of the same version of JAR-STD sub-paragraphs (c) and (d) below. For FFS that are 2A, which was applicable for its last evaluation not re-categorized, maximum credit shall under no prior to implementation of JAR-FSTD A. Any circumstances exceed originally issued National upgrade will be based on the currently applicable credits. version of JAR-FSTD A.

text: (b) FFS’s, neither previously recategorised nor

text: with an approval maintained under the Grandfather

text: Rights provision, will be qualified in accordance

text: JAR-FSTD A.033 Requirements for Flight

text: with JAR–FSTD A.030.

text: & Navigation Procedures

text: Trainers (FNPT) qualified (c) FFS that are not recategorised but that have a

text: on or after 1 July 1999 primary reference document used for their testing,

text: and before 1August 2008 may be qualified by the Authority to an equivalent

text: JAR–FSTD A Qualification Level, either AG, BG, Any FNPT submitted for initial evaluation on or CG or DG. An upgrade requires the after 1 July 1999 and before 1 August 2008, shall recategorisation of the FFS. automatically be granted an equivalent

text: qualification under JAR-FSTD A with effect from (1) To gain and maintain an equivalent

text: the re-evaluation conducted at the end of the Qualification Level, these FFS shall be assessed

text: 2009-11-01 1-C-3 JAR-FSTD A

text: Bilaga 1

text: JAR-FSTD A.035 (continued) JAR-FSTD A.036 (continued)

text: in those areas that are essential to completing (v) Functioning during normal, the flight crewmember training and checking abnormal, emergency and, where process, as applicable. applicable non normal operation;

text: (2) The FFS shall be subjected to: (vi) Instructor station function and FTD control, and (i) Validation tests; and (vii) Certain additional (ii) Functions and subjective tests. requirements depending on the (d) FFS that are not recategorised and that do not Qualification Level and the installed have a primary reference document used for their equipment. testing shall be qualified by special arrangement. Such FFS will be issued with a Special Category (2) The FTD shall be subjected to: and shall be subjected to functions and subjective (i) Validation Tests, and tests corresponding to those detailed in this (ii) Functions and Subjective document. In addition any previously recognised Tests. validation test shall be used. (d) FTDs that are not recategorised and that do not have a primary reference document used for their JAR–FSTD A.036 Requirements for Flight testing shall be qualified by special arrangement. Training Devices (1) Such FTDs will be issued with approved or qualified Special Categories.

text: before 1 July 2000

text: (2) These FTDs shall be subjected to the (See ACJ to JAR-FSTD same Functions and Subjective Tests referred to A.036) in JAR–FSTD A.036(c) (2) (ii). (a) FTDs approved or qualified in accordance with national regulations of JAA Members States before (3) In addition any previously recognised Validation Test shall be used. 1 July 2000 either will be recategorised or will continue to maintain their approval under the Grandfather Rights provision, in accordance with JAR–FSTD A.036(c) and JAR–FSTD A.036 (d). JAR–FSTD A.037 Requirements for Flight

text: Navigation and

text: (b) FTDs, neither previously recategorised nor with an approval maintained under the Grandfather Procedures Trainers Rights provision, will be qualified in accordance approved or qualified

text: before 1 July 1999

text: with JAR–FSTD A.030. (See ACJ to JAR-FSTD (c) FTDs that are not recategorised but that have a A.037) primary reference document used for their testing may be qualified by the Authority to an equivalent (No Longer Applicable) JAR–FSTD Qualification Level, either 1G or 2G. These Qualification Levels refer to similar credits achieved by JAR–FSTD A Level 1 and 2. JAR–FSTD A.040 Changes to qualified

text: FSTD

text: (1) To gain and maintain an equivalent Qualification Level, these FTDs shall be (a) Requirement to notify major changes to a assessed in those areas which are essential to FSTD. The operator of a qualified FSTD shall completing the flight crew member training and inform the Authority of proposed major changes checking process, including: such as:

text: (i) Longitudinal, lateral and (1) Aeroplane modifications, which directional handling qualities (where could affect FSTD qualification. applicable); (2) FSTD hardware and or software (ii) Performance on the ground modifications that could affect the handling and in the air; qualities, performances or system (iii) Specific operations where representations. applicable; (3) Relocation of the FSTD; and (iv) Flight deck configuration; (4) Any deactivation of the FSTD.

text: JAR-FSTD A 1-C-4 2009-11-01

text: Bilaga 1

text: JAR-FSTD A.040 (continued)

text: The Authority may complete a special evaluation following major changes or when a FSTD appears not to be performing at its initial Qualification JAR–FSTD A.045 Interim FSTD Level. Qualification (See ACJ to FSTD A.045) (b) Upgrade of a FSTD. A FSTD may be upgraded to a higher Qualification Level. Special evaluation (a) In case of new aeroplane programmes, special is required before the award of a higher Level of arrangements shall be made to enable an interim Qualification. Qualification Level to be achieved. (1) If an upgrade is proposed the FSTD (b) For Full Flight Simulators, an Interim operator shall seek the advice of the Authority Qualification Level will only be granted at levels and give full details of the modifications. If the A, B or C. upgrade evaluation does not fall upon the (c) Requirements, details relating to the issue, and anniversary of the original qualification date, a the period of validity of an interim Qualification special evaluation is required to permit the Level will be decided by the Authority. FSTD to continue to qualify even at the previous Qualification Level. (2) In the case of a FSTD upgrade, an

text: JAR–FSTD A.050 Transferability of FSTD

text: FSTD operator shall run all validation tests for

text: Qualification

text: the requested Qualification Level. Results from previous evaluations shall not be used to When there is a change of FSTD operator: validate FSTD performance for the current (a) The new FSTD operator shall advise the upgrade. Authority in advance in order to agree upon a plan (c) Relocation of a FSTD of transfer of the FSTD. (1) In instances where a FSTD is moved (b) At the discretion of the Authority, the FSTD to a new location, the Authority shall be advised shall be subject to an evaluation in accordance with before the planned activity along with a its original JAA qualification criteria. schedule of related events. (c) Provided that the FSTD performs to its original (2) Prior to returning the FSTD to standard, its original Qualification Level shall be service at the new location, the FSTD operator restored. Revised user approval(s) may also be shall perform at least one third of the validation required. tests and, functions and subjective tests to ensure that the FSTD performance meets its original qualification standard. A copy of the test documentation shall be retained together with the FSTD records for review by the Authority. (3) An evaluation of the FSTD in accordance with its original JAA qualification criteria shall be at the discretion of the Authority. INTENTIONALLY LEFT BLANK

text: (d) Deactivation of a currently qualified FSTD (1) If a FSTD operator plans to remove a FSTD from active status for prolonged periods, the Authority shall be notified and suitable controls established for the period during which the FSTD is inactive. (2) The FSTD operator shall agree a procedure with the Authority to ensure that the FSTD can be restored to active status at its original Qualification Level.

text: 2009-11-01 1-C-5 JAR-FSTD A

text: SECTION 1

text: Bilaga 1

text: INTENTIONALLY LEFT BLANK JAR-FSTD A 1-C-6 2009-11-01

text: Bilaga 1

text: Appendix 1 to JAR-FSTD A.030 Flight Simulation Training Device Standards

text: This appendix describes the minimum Full Flight Simulator (FFS), Flight Training Device (FTD), Flight and Navigation Procedures Trainer (FNPT) and Basic Instrument Training Devices (BITD) requirements for qualifying devices to the required Qualification Levels. Certain requirements included in this section shall be supported with a statement of compliance (SOC) and, in some designated cases, an objective test. The SOC will describe how the requirement was met. The test results shall show that the requirement has been attained. In the following tabular listing of FSTD standards, statements of compliance are indicated in the compliance column. For FNPT use in Multi-Crew Co-operation (MCC) training the general technical requirement are expressed in the MCC column with additional systems, instrumentation and indicators as required for MCC training and operation. For MCC (Multi Crew Co-operation) minimum technical requirements are as for Level II, with the following additions or amendments:

text: 1 Turbo-jet or turbo-prop engines. 2 Performance reserves, in case of an engine failure, to be in accordance with JAR-25. These may be simulated by a reduction in the aeroplane gross mass. 3 Retractable landing gear. 4 Pressurisation system. 5 De-icing systems 6 Fire detection / suppression system 7 Dual controls 8 Autopilot with automatic approach mode 9 2 VHF transceivers including oxygen masks intercom system 10 2 VHF NAV receivers (VOR, ILS, DME) 11 1 ADF receiver 12 1 Marker receiver 13 1 transponder The following indicators shall be located in the same positions on the instrument panels of both pilots: 1 Airspeed 2 Flight attitude with flight director 3 Altimeter 4 Flight director with ILS (HSI) 5 Vertical speed 6 ADF 7 VOR 8 Marker indication (as appropriate) 9 Stop watch (as appropriate)

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 1-C-7 JAR-FSTD A

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: FLIGHT SIMULATOR TRAINING DEVICE STANDARDS FFS LEVEL FTD FNPT LEVEL BITD LEVEL t

text: A o :8

text: J

text: A 7

text: A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD a.1 A fully enclosed flight deck 9 9 9 9 A.0 30 a.2 A cockpit/flight deck sufficiently enclosed to exclude 9 9 9 9 9 (co distraction, which will replicate that of the aeroplane n or class of aeroplane simulated ti n u e d a.3 Flight deck, a full scale replica of the aeroplane 9 9 9 9 Flight deck observer seats are not considered to be ) simulated. additional flight crewmember duty stations and may be omitted. Equipment for operation of the cockpit windows shall 1-C be included in the FSTD, but the actual windows need not be operable. -8 Bulkheads containing items such as switches, circuit The flight deck, for FSTD purposes, consists of all breakers, supplementary radio panels, etc. to which that space forward of a cross section of the fuselage the flight crew may require access during any event at the most extreme aft setting of the pilots' seats. after pre-flight cockpit preparation is complete are Additional required flight crewmember duty stations considered essential and may not be omitted. and those required bulkheads aft of the pilot seats are also considered part of the flight deck and shall Bulkheads containing only items such as landing replicate the aeroplane. gear pin storage compartments, fire axes or S extinguishers, spare light bulbs, aircraft document pouches etc. are not considered essential and may be omitted. Such items, or reasonable facsimile, shall still be available in the FSTD but may be relocated to a suitable location as near as practical to the original position. Fire axes and any similar purpose instruments need only be represented in silhouette.

text: a.4 Direction of movement of controls and switches 9 9 9 9 identical to that in the aeroplane.

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: A SE

text: 20 ppen

text: CT

text: 09 di IO -11 x 1

text: FLIGHT SIMULATOR TRAINING DEVICE STANDARDS FFS LEVEL FTD FNPT LEVEL BITD N 1 LEVEL t

text: -0 o

text: 1 J 1- A A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD a.5 A full size panel of replicated system(s) which will 9 9 The use of electronically displayed images with A.0 have actuation of controls and switches that physical overlay incorporating operable switches, replicate those of the aeroplane simulated. knobs, buttons replicating aeroplane instruments 30

text: panels may be acceptable. (co

text: n a.6 Cockpit/flight deck switches, instruments, equipment, 9 9 9 9 For Multi-Crew Co-operation (MCC) qualification ti n u panels, systems, primary and secondary flight controls additional instrumentation and indicators may be e d sufficient for the training events to be accomplished shall required. See table at start of this appendix.. ) be located in a spatially correct flight deck area and will operate as, and represent those in, that aeroplane or For BITDs the switches and controls size and shape class of aeroplane. and their location in the cockpit shall be representative.

text: C -9

text: a.7 Crew members seats shall be provided with 9 9 9

text: sufficient adjustment to allow the occupant to achieve the design eye reference position appropriate to the aeroplane or class of aeroplane Bilag

text: and for the visual system to be installed to align with that eye position.

text: b.1 Circuit breakers that affect procedures and/or result 9 9 9 9 9 9 9 9

text: in observable cockpit indications properly located and functionally accurate.

text: JA TSF R-FS a S 2 TD A 1 0 09:8

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: A o :8

text: J

text: A 7

text: A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD c.1 Flight dynamics model that accounts for various 9 9 9 9 9 9 9 9 9 9 For FTD Levels 1 and 2 aerodynamic modelling A.0 combinations of drag and thrust normally sufficient to permit accurate systems operation and encountered in flight corresponding to actual flight indication is acceptable. 30 conditions, including the effect of change in (co aeroplane attitude, sideslip, thrust, drag, altitude, For FNPTs and BITDs class specific modelling is n temperature, gross weight, moments of inertia, acceptable. ti n u centre of gravity location, and configuration. e d )

text: d.1 All relevant instrument indications involved in the 9 9 9 9 9 9 9 9 9 9 For FNPTs instrument indications sufficient for the simulation of the applicable aeroplane shall training events to be accomplished. Reference ACJ No. 1- automatically respond to control movement by a 3 to JAR-FSTD A.030. C- flight crewmember or induced disturbance to the 10 simulated aeroplane; e.g., turbulence or wind shear. For BITDs instrument indications sufficient for the training events to be accomplished. Reference ACJ No. 4 to JAR-FSTD A.030.

text: d.2 Lighting environment for panels and instruments 9 9 9 9 9 9 For FTD Level 2 lighting environment shall be as per shall be sufficient for the operation being conducted. aeroplane.

text: e.1 Communications, navigation, and caution and 9 9 9 9 9 9 For FTD 1 applies where the appropriate systems S

text: warning equipment corresponding to that installed in are replicated. the applicant’s aeroplane with operation within the tolerances prescribed for the applicable airborne equipment.

text: e.2 Navigation equipment corresponding to that of the 9 9 9 9 replicated aeroplane or class of aeroplanes, with operation within the tolerances prescribed for the actual airborne equipment. This shall include communication equipment (interphone and air/ground communications systems).

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: A SE

text: 20 ppen

text: CT

text: 09 di IO -11 x 1

text: -0 o

text: 1 J 1- A A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD e.3 Navigational data with the corresponding approach 9 9 9 9 9 9 9 9 9 9 For FTD 1 applies where navigation equipment is A.0 facilities. Navigation aids should be usable within replicated. range without restriction. 30 For all FFSs and FTDs 2 where used for area or (co airfield competence training or checking, navigation n data should be updated within 28 days. ti n u e d

text: For FNPTs and BITDs complete navigational data for ) at least 5 different European airports with corresponding precision and non-precision approach procedures including current updating within a period of 3 months.

text: C- 11

text: f.1 In addition to the flight crewmember duty stations, 9 9 9 9 9 9 9 9 9 9 For FTDs and FNPT’s suitable seating three suitable seats for the instructor, delegated arrangements for the Instructor and Examiner or examiner and Authority inspector. The Authority will Authority’s Inspector should be provided. consider options to this standard based on unique cockpit configurations. These seats shall provide Bilag adequate vision to the pilot’s panel and forward windows. Observer seats need not represent those For BITDs suitable viewing arrangements for the found in the aeroplane but in the case of FSTDs Instructor should be provided. fitted with a motion system, the seats shall be adequately secured to the floor of the FSTD, fitted with positive restraint devices and be of sufficient integrity to safely restrain the occupant during any known or predicted motion system excursion.

text: JA TSF R-FS a S 2 TD A 1 0 09:8

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: A o :8

text: J

text: A 7

text: A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD g.1 FSTD systems shall simulate applicable aeroplane 9 9 9 9 9 9 9 9 For FTD Level 1, applies where system is simulated. A.0 system operation, both on the ground and in flight. For FNPTs systems shall be operative to the extent that Systems shall be operative to the extent that all it shall be possible to perform all normal, abnormal and 30

text: normal, abnormal, and emergency operating emergency operations as may be appropriate to the (co procedures can be accomplished. aeroplane or class of aeroplanes being simulated and n as required for the training. ti n u e d )

text: 1- h.1 Instructor controls shall enable the operator to 9 9 9 9 9 9 9 9 9 9 Where applicable and as required for training the C- control all required system variables and insert following shall be available : 12 abnormal or emergency conditions into the

text: aeroplane systems. - Position and flight freeze.

text: - A facility to enable the dynamic plotting of the flight path on approaches, commencing at the final approach fix, including the vertical profile

text: - Hard copy of map and approach plot S

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: A SE

text: 20 ppen

text: CT

text: 09 di IO -11 x 1

text: -0 o

text: 1 J 1- A A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD i.1 Control forces and control travel shall correspond to 9 9 9 9 9 9 9 9 9 For FTD Level 2 Control forces and control travel A.0 that of the replicated aeroplane. Control forces shall should correspond to that of the replicated react in the same manner as in the aeroplane under aeroplane with CT&M. It is not intended that the 30

text: the same flight conditions. device should be flown manually other than for short (co periods when the autopilot is temporarily n disengaged. ti n u e d For FNPT Level I and BITDs control forces and ) control travel shall broadly correspond to that of the replicated aeroplane or class of aeroplane. Control force changes due to an increase/decrease in aircraft speed are not necessary.

text: C- In addition for FNPT Level II and MCC control forces 13 and control travels shall respond in the same

text: manner under the same flight conditions as in the aeroplane or class of aeroplane being simulated.

text: Bilag

text: JA TSF R-FS a S 2 TD A 1 0 09:8

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: A o :8

text: J

text: A 7

text: A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD j.1 Ground handling and aerodynamic programming 9 9 9 9 9 9 Statement of Compliance required. Tests required. A.0 shall include: For Level ‘A’ FFS, generic ground handling to the 30 extent that allows turns within the confines of the (co runway, adequate control on flare, touchdown and n (1) Ground Effect. For example: round-out, flare, roll-out (including from a cross -wind landing) only is ti n and touchdown. This requires data on lift, u acceptable. e d drag, pitching moment, trim, and power ground ) effect. For FNPTs a generic ground handling model need only be provided to enable representative flare and touch down effects.

text: C- (2) Ground reaction – reaction of the aeroplane 14 upon contact with the runway during landing to include strut deflections, tyre friction, side forces, and other appropriate data, such as weight and speed, necessary to identify the flight condition and configuration.

text: S

text: (3) Ground handling characteristics – steering inputs to include crosswind, braking, thrust reversing, deceleration and turning radius.

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: A SE

text: 20 ppen

text: CT

text: 09 di IO -11 x 1

text: -0 o

text: 1 J 1- A A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD k.1 Windshear models shall provide training in the 9 9 Tests required. A.0 specific skills required for recognition of wind shear phenomena and execution of recovery manoeuvres. 30

text: Such models shall be representative of measured or (co accident derived winds, but may include See ACJ No 1 to JAR-FSTD A.030, Para 2.3, g. n simplifications which ensure repeatable encounters. ti n u For example, models may consist of independent e d variable winds in multiple simultaneous components. ) Wind models shall be available for the following critical phases of flight:

text: (1) Prior to take-off rotation

text: C- (2) At lift-off 15

text: (3) During initial climb

text: (4) Short final approach

text: l.1 Instructor controls for environmental effects 9 9 9 9 9 9 9 9 9 9 For FTDs environment modelling sufficient to permit including wind speed and direction shall be accurate systems operation and indication. Bilag

text: provided.

text: JA TSF R-FS a S 2 TD A 1 0 09:8

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: A o :8

text: J

text: A 7

text: A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD m.1 Stopping and directional control forces shall be 9 9 Statement of Compliance required. A.0 representative for at least the following runway conditions based on aeroplane related data: 30 (co (1) Dry Objective Tests required for (1), (2), (3), Subjective n check for (4), (5), (6). ti n u (2) Wet e d ) (3) Icy

text: (4) Patchy wet

text: C- (5) Patchy icy

text: (6) Wet on rubber residue in touchdown zone.

text: n.1 Brake and tyre failure dynamics (including antiskid) 9 9 Statement of Compliance required. and decreased brake efficiency due to brake temperatures shall be representative and based on Subjective test is required for decreased braking aeroplane related data. efficiency due to brake temperature, if applicable.

text: S

text: o.1 A means for quickly and effectively conducting daily 9 9 Statement of Compliance required. testing of FSTD programming and hardware shall be available.

text: p.1 Computer capacity, accuracy, resolution, and 9 9 9 9 9 9 Statement of Compliance required. dynamic response shall be sufficient to fully support the overall fidelity, including its evaluation and testing.

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: A SE

text: 20 ppen

text: CT

text: 09 di IO -11 x 1

text: -0 o

text: 1 J 1- A A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD q.1 Control feel dynamics shall replicate the aeroplane 9 9 Tests required. simulated. A.0

text: 30 Free response of the controls shall match that of the (co aeroplane within the tolerances specified. Initial and upgrade evaluations will include control free response n ti (pitch, roll and yaw controller) measurements recorded at n u the controls. The measured responses shall correspond to e d those of the aeroplane in take-off, cruise, and landing ) configurations.

text: (1) For aeroplanes with irreversible control systems, measurements may be obtained on the ground if proper pitot static inputs are provided to represent C- conditions typical of those encountered in flight. 17 Engineering validation or aeroplane manufacturer rationale will be submitted as justification to ground test or omit a configuration.

text: (2) For FSTDs requiring static and dynamic tests at the controls, special test fixtures will not be required during initial evaluation if the FSTD

text: Bilag

text: operator’s MQTG shows both text fixture results and alternate test method results such as computer data plots, which were obtained concurrently. Repetition of the alternate method during initial evaluation may then satisfy this requirement.

text: JA TSF R-FS a S 2 TD A 1 0 09:8

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: A o :8

text: J

text: A 7

text: A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD r.1 Tests required.

text: 9 9 9 9 9 9 9 9 9 9 A.0

text: One of the following two methods is acceptable as a means to prove compliance: For Level ‘A’ & ‘B’ FFSs, and applicable systems for 30

text: FTDs, FNPTs and BITDs the maximum permissible (co

text: delay is 300 milliseconds. n ti n u e d )

text: (1) Transport Delay: A transport delay test may be used to demonstrate that the FSTD system response does not exceed 150 milliseconds. This test shall

text: measure all the delay encountered by a step signal

text: C-

text: migrating from the pilot’s control through the control

text: loading electronics and interfacing through all the simulation software modules in the correct order, using a handshaking protocol, finally through the normal output interfaces to the motion system, to the visual

text: system and instrument displays.

text: (see next page) S

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: A SE

text: 20 ppen

text: CT

text: 09 di IO -11 x 1

text: -0 o

text: 1 J 1- A A B C D 1 2 I II MCC R- 1.1 General COMPLIANCE F S TD

text: (continued) A.0

text: 30 (2) Latency: The visual system, flight deck (co instruments and initial motion system response shall respond to abrupt pitch, roll and yaw inputs n ti from the pilot's position within 150 milliseconds n u e of the time, but not before the time, when the d aeroplane would respond under the same )

text: conditions.

text: C- 19

text: Bilag

text: JA TSF R-FS a S 2 TD A 1 0 09:8

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: FLIGHT SIMULATOR TRAINING DEVICE FFS LEVEL FTD FNPT LEVEL BITD t

text: A o :8

text: STANDARDS LEVEL J

text: A 7

text: COMPLIANCE R- F S 1.1 General A B C D 1 2 I II MCC TD

text: A.0 s.1 Aerodynamic modelling shall be provided. This shall 9 9 Statement of Compliance required. Mach effect, include, for aeroplanes issued an original type aeroelastic representations, and non-linearities 30 certificate after June 1980, low altitude level flight due to sideslip are normally included in the FSTD (co ground effect, Mach effect at high altitude, normal aerodynamic model. The Statement of Compliance n ti and reverse dynamic thrust effect on control shall address each of these items. Separate tests n u surfaces, aeroelastic representations, and for thrust effects and a Statement of Compliance e d representations of non-linearities due to sideslip are required. ) based on aeroplane flight test data provided by the manufacturer.

text: 1- t.1 Modelling that includes the effects of airframe and 9 9 9 9 Statement of Compliance required.

text: C-

text: engine icing. 20 SOC shall describe the effects that provide

text: training in the specific skills required for recognition of icing phenomena and execution of recovery.

text: u.1 Aerodynamic and ground reaction modelling for the 9 9 9 Statement of Compliance required. effects of reverse thrust on directional control shall

text: S

text: be provided. (page 2–C–44).

text: v.1 Realistic aeroplane mass properties, including mass, 9 9 9 9 Statement of Compliance required at initial centre of gravity and moments of inertia as a evaluation. SOC shall include a range of tabulated function of payload and fuel loading shall be target values to enable a demonstration of the implemented. mass properties model to be conducted from the instructor’s station.

text: w.1 Self-testing for FSTD hardware and programming to 9 9 Statement of Compliance required. Tests required. determine compliance with the FSTD performance tests shall be provided. Evidence of testing shall include FSTD number, date, time, conditions, tolerances, and the appropriate dependent variables portrayed in comparison with the aeroplane 20 standard.

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: A SE

text: 20 ppen

text: CT

text: 09 di IO -11 x 1

text: FLIGHT SIMULATOR TRAINING DEVICE FFS LEVEL FTD FNPT LEVEL BITD N 1 STANDARDS LEVEL t

text: -0 o

text: 1 COMPLIANCE J 1- A R- 1.1 General A B C D 1 2 I II MCC F S TD x.1 Timely and permanent update of hardware and 9 9 9 9 9 9 A.0 programming subsequent to aeroplane modification sufficient for the Qualification Level sought. 30

text: (co y.1 Daily pre-flight documentation either in the daily log 9 9 9 9 9 9 9 9 9 9 n ti or in a location easily accessible for review is n u required. e d )

text: C- 21

text: Bilag

text: JA TSF R-FS a S 2 TD A 1 0 09:8

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: A o :8

text: STANDARDS LEVEL J

text: A 7

text: R- A B C D 1 2 I II MCC F S COMPLIANCE TD

text: 2. Motion system

text: A.0 a.1 Motion cues as perceived by the pilot 9 9 9 9 For FSTDs where motion systems are 30 shall be representative of the aeroplane, not specifically required, but have been (co e.g. touchdown cues shall be a function added, they will be assessed to ensure n ti of the simulated rate of descent. that they do not adversely affect the n u qualification of the FSTD. e d ) b.1 A motion system shall: Statement of Compliance required.

text: (1) Provide sufficient cueing, which 9 Tests required. 1- may be of a generic nature to C- accomplish the required tasks.

text: (2) Have a minimum of 3 degrees of 9 freedom (pitch, roll & heave).

text: (3) Produce cues at least equivalent to 9 9 those of a six-degrees-of-freedom synergistic platform motion system.

text: S

text: c.1 A means of recording the motion 9 9 9 9 response time as required.

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: A SE

text: 20 ppen

text: CT

text: 09 di IO -11 x 1

text: -0 o

text: 1 J 1- A A B C D 1 2 I II MCC R- COMPLIANCE F S 2. Motion system TD

text: A.0 d.1 Motion effects programming shall include: 9 9 9 9 For Level ‘A’FFS: Effects may be of a generic nature sufficient to accomplish 30 (1) Effects of runway rumble, oleo the required tasks. (co deflections, groundspeed, uneven n runway, centreline lights and ti n u taxiway characteristics. e d ) (2) Buffets on the ground due to spoiler/speedbrake extension and thrust reversal.

text: (3) Bumps associated with the landing C- gear. 23 (4) Buffet during extension and retraction of landing gear.

text: (5) Buffet in the air due to flap and spoiler/speedbrake extension.

text: Bilag

text: (6) Approach to stall buffet.

text: (7) Touchdown cues for main and nose gear.

text: (8) Nose wheel scuffing.

text: (9) Thrust effect with brakes set.

text: JA TSF R-FS a S

text: (See next page) 2

text: TD A 1 0 09:8

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: FLIGHT SIMULATOR TRAINING DEVICE FFS LEVEL FTD FNPT LEVEL BITD STANDARDS LEVEL t

text: A o :8

text: J

text: A 7

text: A B C D 1 2 I II MCC R- COMPLIANCE F S 2. Motion system TD

text: A.0 d.1 (continued) 9 9 9 9 30 (co (10) Mach and manoeuvre buffet. n ti n (11) Tyre failure dynamics. u e d (12) Engine malfunction and engine )

text: damage.

text: 1- (13) Tail and pod strike.

text: C- 24

text: e.1 Motion vibrations: Tests with recorded 9 Statement of Compliance required. results that allow the comparison of relative amplitudes versus frequency are Tests required. required.

text: Characteristic motion vibrations that S result from operation of the aeroplane in so far as vibration marks an event or aeroplane state that can be sensed at the flight deck shall be present. The FSTD shall be programmed and instrumented in such a manner that the characteristic vibration modes can be measured and compared with aeroplane data.

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: A SE

text: 20 ppen

text: CT

text: 09 di IO -11 x 1

text: FLIGHT SIMULATOR TRAINING DEVICE FS LEVEL FTD FNPT LEVEL BITD N 1 STANDARDS LEVEL t

text: -0 o

text: 1 J 1- A A B C D 1 2 I II MCC R- COMPLIANCE F S 3 Visual System TD

text: A.0 a.1 The visual system shall meet all the 9 9 9 9 9 9 For FTDs, FNPT 1s and BITDs, when visual standards enumerated as applicable to systems have been added by the FSTD 30 the level of qualification requested by the operator even though not attracting specific (co applicant. credits, they will be assessed to ensure that n they do not adversely affect the qualification ti n u of the FSTD. e d ) For FTDs if the visual system is to be used for the training of manoeuvring by visual reference (such as route and airfield competence) then the visual system should at least comply with that required for level A C- FFS. 25

text: b.1 Continuous minimum collimated visual 9 9 SOC is acceptable in place of this test. field-of-view of 45 degrees horizontal and 30 degrees vertical field of view simultaneously for each pilot. Bilag

text: b.2 Continuous, cross-cockpit, minimum 9 9 Consideration shall be given to optimising collimated visual field of view providing the vertical field of view for the respective each pilot with 180 degrees horizontal aeroplane cut-off angle. and 40 degrees vertical field of view. Application of tolerances require the field SOC is acceptable in place of this test. of view to be not less than a total of 176 measured degrees horizontal field of view JA (including not less than ±88 measured TSF

text: R-FS degrees either side of the centre of the design eye point) and not less than a total S

text: a 2

text: of 36 measured degrees vertical field of 1

text: TD A 0

text: view from the pilot’s and co-pilot’s eye 09:8 points.

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: FLIGHT SIMULATOR TRAINING DEVICE FS LEVEL FTD FNPT LEVEL BITD STANDARDS LEVEL t

text: A o :8

text: J

text: A 7

text: A B C D 1 2 I II MCC R- COMPLIANCE F S 3 Visual System TD

text: A.0 b.3 A visual system (night/dusk or day) capable 9 9 The visual system need not be collimated but of providing a field-of-view of a minimum of shall be capable of meeting the standards laid 30 45 degrees horizontally and 30 degrees down in Part 3 and 4 (Validation, Functions and (co vertically, unless restricted by the type of Subjective Tests - See ACJ No.1 to JAR-FSTD n aeroplane, simultaneously for each pilot, A.030). ti n u including adjustable cloud base and visibility. e d SOC is acceptable in place of this test. )

text: c.1 A means of recording the visual response 9 9 9 9 9 9 1- time for visual systems.

text: C-

text: 26 d.1 System Geometry. The system fitted shall 9 9 9 9 9 9 Test required. A Statement of Compliance is be free from optical discontinuities and acceptable in place of this test. artefacts that create non-realistic cues.

text: e.1 Visual textural cues to assess sink rate 9 9 9 9 For Level ‘A’ FFS visual cueing shall be and depth perception during take-off and sufficient to support changes in approach landing shall be provided. path by using runway perspective.

text: S

text: f.1 Horizon, and attitude shall correlate to the 9 9 9 9 Statement of Compliance required. simulated attitude indicator.

text: g.1 Occulting - A minimum of ten levels shall 9 9 9 9 Occulting shall be demonstrated. be available.

text: Statement of Compliance required.

text: h.1 Surface (Vernier) resolution shall occupy 9 9 Test and Statement of Compliance required a visual angle of not greater than 2 arc containing calculations confirming minutes in the visual display used on a resolution. 20 scene from the pilot’s eyepoint.

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: A SE

text: 20 ppen

text: CT

text: 09 di IO -11 x 1

text: -0 o

text: A.0 i.1 Surface contrast ratio shall be 9 9 Test and Statement of Compliance required. demonstrated by a raster drawn test 30

text: pattern showing a contrast ratio of not (co less than 5:1 n ti n u j.1 Highlight brightness shall be 9 9 Test and Statement of Compliance required. e d demonstrated using a raster drawn test Use of calligraphic lights to enhance raster ) pattern. The highlight brightness shall not brightness is acceptable. be less than 20 cd/m (6ft-lamberts).

text: k.1 Light point size – not greater than 5 arc 9 9 Test and Statement of Compliance required.

text: minutes. This is equivalent to a light point resolution C- of 2.5 arc minutes. 27

text: l.1 Light point contrast ratio – not less than 9 9 Test and Statement of compliance required.

text: l.2 Light point contrast ratio – not less than 9 9 Test and Statement of compliance required.

text: Bilag

text: m.1 Daylight, twilight and night visual 9 9 9 9 Statement of Compliance required for

text: capability as applicable for level of system capability. qualification sought. System objective and scene content tests are required.

text: JA TSF

text: R-FS m.2 The visual system shall be capable of 9 9 9 9 meeting, as a minimum, the system a S

text: TD A brightness and contrast ratio criteria as 1

text: applicable for level of qualification sought 09:8

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: A o :8

text: J

text: A 7

text: A.0 m.3 Total scene content shall be comparable 9 9 in detail to that produced by 10000 visible 30

text: textured surfaces and (in day) 6000 (co visible lights or (in twilight or night) 15000 n visible lights, and sufficient system ti n u capacity to display 16 simultaneously e d moving objects. )

text: m.4 The system, when used in training, shall 9 9 1- provide in daylight, full colour C- presentations and sufficient surfaces with 28 appropriate textural cues to conduct a

text: visual approach, landing and airport movement (taxi). Surface shading effects shall be consistent with simulated (static) sun position.

text: S

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: A SE

text: 20 ppen

text: CT

text: 09 di IO -11 x 1

text: -0 o

text: 1 J 1- A A B C D 1 2 I II MCC R- COMPLIANCE F S 3 Visual System TD A.0 m.5 The system, when used in training, shall 9 9 provide at twilight, as a minimum, full 30 colour presentations of reduced ambient (co intensity, sufficient surfaces with n appropriate textural cues that include self- ti n u illuminated objects such as road e d networks, ramp lighting and airport ) signage, to conduct a visual approach, landing and airport movement (taxi). Scenes shall include a definable horizon and typical terrain characteristics such as fields, roads and bodies of water and C- surfaces illuminated by representative 29 ownship lighting (e.g. landing lights). If provided, directional horizon lighting shall have correct orientation and be consistent with surface shading effects.

text: Bilag

text: m.6 The system, when used in training, shall 9 9 9 9 provide at night, as a minimum, all features applicable to the twilight scene, as defined above, with the exception of the need to portray reduced ambient intensity that removes ground cues that are not self-illuminating or illuminated by ownship lights (e.g. landing lights).

text: JA TSF R-FS a S 2 TD A 1 0 09:8

text: JA A Bi TS

text: ppen

text: R-FS la FS ga 1 di 2 TD x 1 009

text: A o :8

text: J

text: A 7

text: R- COMPLIANCE F S 4 Sound System TD A B C D 1 2 I II MCC A.0

text: a.1 Significant flight deck sounds which result 9 9 9 9 9 9 9 9 9 For FNPT Level I and BITD engine sounds (co

text: from pilot actions corresponding to those only need be available n ti of the aeroplane or class of aeroplane. n u e d b.1 Sound of precipitation, rain removal 9 9 Statement of Compliance required. )

text: equipment and other significant aeroplane noises perceptible to the pilot during normal and abnormal operations and the 1- sound of a crash when the FSTD is C- landed in excess of limitations.

text: c.1 Comparable amplitude and frequency of 9 Tests required.

text: flight deck noises, including engine and airframe sounds. The sounds shall be coordinated with the required weather.

text: d.1 The volume control shall have an 9 9 9 9

text: S

text: indication of sound level setting which meets all qualification requirements.

text: E

text: 09 C -11 T

text: IO

text: -0 N

text: 1 1

text: Bilaga 1

text: SEC TION 2 – ADVISORY CIRCUL ARS JOINT (AC J)

text: 1 GENERAL

text: 1.1 T his Section c ontains Advisor y Circ ulars J oint (ACJ) providing acceptable means of complianc e and/or interpretative/explanator y material that have been agreed for inc lus ion in JAR–FSTD A.

text: 1.2 W here a partic ular JAR paragraph does not have an Advis ory Circ ular Joint (ACJ), it is cons idered that no s upplementary mate rial is required.

text: 2 PRESENTATION

text: 2.1 T he ACJ s are presented in full-page width on loose pages, each page being identified b y the date of iss ue and the Amendment number under which it is amended or reissued.

text: 2.2 A numbering s ys tem has been used in which the Advis or y Circular Joint (ACJ ) us es the same number as the J AR pa ragraph to whic h it refers . The number is introduced b y the letters ACJ to distinguish the material from the JAR itself.

text: 2.3 T he ac ron ym ACJ also indicates the nature of the material and for this purpose the t ype of material is defined as follows :

text: Advisory Circulars Joint (ACJ) illustrate a means , or several alternative means , but not necessarily the only possible means by which a requirement can be met. It should ho we ver be noted that where a new ACJ is developed, any such ACJ (wh ich may b e additional to an existing ACJ) will be amended into the doc ument following consultation under the NPA procedure. Suc h ACJ will be designated b y (acceptable means of compliance).

text: An ACJ as interpretative/explanatory material may c ontain material that helps to illustrate the meaning of a requirement. Such ACJ will be des ignated by ( interpretative/explanator y material).

text: 2.4 New ACJ material may, in the first place, be made available rapidly by being published as a Temporary Guidance Leaflet (T GL). FSTD TGLs (JAR–FSTD) can be found in the Joint A viation Authorities Administrative & Guidance Material, Section 6 – Flight Simulation Training Devices (FSTD), Part Three: Temporar y Guidance Leaflet (JAR–FST D). The procedures associated with Temporary Guidance Leaflets are included in the FSTD Joint Implementation Procedures, Section 6 – Flight Simulation Training Devices (FSTD), Part T wo: Proc edures (JAR–FSTD) Chapter 9. Note: Any person who considers that there may be alternative ACJ to those published should submit details to the Operations Director, with a copy to the Regulation Director, for alternatives to be properly considered by the JAA. Possible alternative ACJ may not be used until published by the JAA as ACJ or TGLs.

text: 2.5 Explanator y Notes not forming part of the ACJ te xt appear in a smaller t ypeface.

text: 2.6 New, amended or corrected text is enc losed within heav y brackets .

text: 2009-11-01 2-0-1 JAR-FSTD A

text: SECTION 2

text: Bilaga 1

text: 2.7 After each ACJ, the various c hanges and amendments, when an y s inc e the initial issue, are indic ated together with their date of issue.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD A 2-0-2 2009-11-01

text: Bilaga 1

text: ACJ B – GENERAL

text: ACJ to JAR-FSTD A.005 Terminology, Abbreviations See JAR–FSTD A.005

text: 1 Terminology 1.1 In addition to the principal terms defined in the requirement itself, additional terms used in the context of JAR–FSTD A and JAR-FSTD H have the following meanings: a Acceptable Change. A change to configuration, software etc., which qualifies as a potential candidate for alternative approach to validation. b Aircraft Performance Data. Performance data published by the aircraft manufacturer in documents such as the Aeroplane or Rotorcraft Flight Manual, Operations Manual, Performance Engineering Manual, or equivalent. c Airspeed. Calibrated airspeed unless otherwise specified (knots). d Altitude. Pressure altitude (metres or feet) unless specified otherwise. e Audited Engineering Simulation. An aircraft manufacturer’s engineering simulation which has undergone a review by the appropriate regulatory Authorities and been found to be an acceptable source of supplemental validation data. f Automatic Testing. Flight Synthetic Training Device (FSTD) testing wherein all stimuli are under computer control. g Bank. Bank/Roll angle (degrees) h Baseline. A fully flight-test validated production aircraft simulation. May represent a new aircraft type or a major derivative. i Breakout. The force required at the pilot’s primary controls to achieve initial movement of the control position. j Closed Loop Testing. A test method for which the input stimuli are generated by controllers which drive the FSTD to follow a pre-defined target response. k Computer Controlled Aircraft. An aircraft where the pilot inputs to the control surfaces are transferred and augmented via computers. l Control Sweep. A movement of the appropriate pilot’s control from neutral to an extreme limit in one direction (Forward, Aft, Right, or Left), a continuous movement back through neutral to the opposite extreme position, and then a return to the neutral position. m Convertible FSTD. An FSTD in which hardware and software can be changed so that the FSTD becomes a replica of a different model or variant, usually of the same type aircraft. The same FSTD platform, cockpit shell, motion system, visual system, computers, and necessary peripheral equipment can thus be used in more than one simulation. n Critical Engine Parameter. The engine parameter which is the most appropriate measure of propulsive force. o Damping (critical). The CRITICAL DAMPING is that minimum Damping of a second order system such that no overshoot occurs in reaching a steady state value after being displaced from a position of equilibrium and released. This corresponds to a relative Damping ratio of 1:0 p Damping (over-damped). An OVER-DAMPED response is that Damping of a second order system such that it has more Damping than is required for Critical Damping, as described above. This corresponds to a relative Damping ratio of more than 1:0. q Damping (under-damped). An UNDER-DAMPED response is that Damping of a second order system such that a displacement from the equilibrium position and free release results in one or more overshoots or oscillations before reaching a steady state value. This corresponds to a relative Damping ratio of less than 1:0.

text: 2009-11-01 2-B-1 JAR-FSTD A

text: Bilaga 1

text: ACJ to JAR-FSTD A.005 (continued)

text: r Daylight Visual. A visual system capable of meeting, as a minimum, system brightness, contrast ratio requirements and performance criteria appropriate for the level of qualification sought. The system, when used in training, should provide full colour presentations and sufficient surfaces with appropriate textural cues to successfully conduct a visual approach, landing and airport movement (taxi). s Deadband. The amount of movement of the input for a system for which there is no reaction in the output or state of the system observed. t Distance. Distance in Nautical Miles unless specified otherwise. u Driven. A state where the input stimulus or variable is ‘driven’ or deposited by automatic means, generally a computer input. The input stimulus or variable may not necessarily be an exact match to the flight test comparison data – but simply driven to certain predetermined values. v Engineering Simulation. An integrated set of mathematical models representing a specific aircraft configuration, which is typically used by the aircraft manufacturer for a wide range of engineering analysis tasks including engineering design, development and certification: and to generate data for checkout, proofof-match/validation and other training FSTD data documents. w Engineering Simulator. The term for the aircraft manufacturer’s simulator which typically includes a full-scale representation of the simulated aircraft flight deck, operates in real time and can be flown by a pilot to subjectively evaluate the simulation. It contains the engineering simulation models, which are also released by the aircraft manufacturer to the industry for FSTDs: and may or may not include actual on-board system hardware in lieu of software models. x Engineering Simulator Data. Data generated by an engineering simulation or engineering simulator, depending on the aircraft manufacturer’s processes. y Engineering Simulator Validation Data. Validation data generated by an engineering simulation or engineering simulator. z Entry into Service. Refers to the original state of the configuration and systems at the time a new or major derivative aircraft is first placed into commercial operation. aa Essential Match. A comparison of two sets of computer-generated results for which the differences should be negligible because essentially the same simulation models have been used. Also known as a virtual match. bb FSTD Approval. The extent to which an FSTD of a specified Qualification Level may be used by an operator or training organisation as agreed by the Authority. It takes account of differences between aircraft and FSTDs and the operating and training ability of the organisation. cc FSTD Data. The various types of data used by the FSTD manufacturer and the applicant to design, manufacture, test and maintain the FSTD. dd FSTD Evaluation. A detailed appraisal of an FSTD by the Authority to ascertain whether or not the standard required for a specified Qualification Level is met. ee FSTD Operator. That person, organisation or enterprise directly responsible to the authority for requesting and maintaining the qualification of a particular FSTD. ff FSTD Qualification Level. The level of technical capability of a FSTD. gg Flight Test Data. Actual aircraft data obtained by the aircraft manufacturer (or other supplier of acceptable data) during an aircraft flight test programme. hh Free Response. The response of the aircraft after completion of a control input or disturbance. ii Frozen/Locked. A state where a variable is held constant with time. jj Fuel used. Mass of fuel used (kilos or pounds) kk Full Sweep. Movement of the controller from neutral to a stop, usually the aft or right stop, to the opposite stop and then to the neutral position. ll Functional Performance. An operation or performance that can be verified by objective data or other suitable reference material that may not necessarily be flight test data.

text: JAR-FSTD A 2-B-2 2009-11-01

text: Bilaga 1

text: ACJ to JAR-FSTD A.005 (continued)

text: mm Functions Test. A quantitative and/or qualitative assessment of the operation and performance of an FSTD by a suitably qualified evaluator. The test can include verification of correct operation of controls, instruments, and systems of the simulated aircraft under normal and non-normal conditions. Functional performance is that operation or performance that can be verified by objective data or other suitable reference material which may not necessarily be Flight Test Data. nn Grandfather Rights. The right of an FSTD operator to retain the Qualification Level granted under a previous regulation of a JAA member state. Also the right of an FSTD user to retain the training and testing/checking credits which were gained under a previous regulation of a JAA member state. oo Ground Effect. The change in aerodynamic characteristics due to modification of the air flow past the aircraft caused by the presence of the ground. pp Hands-off Manoeuvre. A test manoeuvre conducted or completed without pilot control inputs. qq Hands-on Manoeuvre. A test manoeuvre conducted or completed with pilot control inputs as required. rr Heavy. Operational mass at or near maximum for the specified flight condition. ss Height. Height above ground = AGL (meters or feet) tt Highlight Brightness. The maximum displayed brightness, which satisfies the appropriate brightness test. uu Icing Accountability. A demonstration of minimum required performance whilst operating in maximum and intermittent maximum icing conditions of the applicable airworthiness requirement.Refers to changes from normal (as applicable to the individual aircraft design) in takeoff, climb (enroute, approach, landing) or landing operating procedures or performance data, in accordance with the AFM/RFM, for flight in icing conditions or with ice accumulation on unprotected surfaces. vv Integrated Testing. Testing of the FSTD such that all aircraft system models are active and contribute appropriately to the results. None of the aircraft system models should be substituted with models or other algorithms intended for testing only. This may be accomplished by using controller displacements as the input. These controllers should represent the displacement of the pilot’s controls and these controls should have been calibrated. ww Irreversible Control System. A control system in which movement of the control surface will not backdrive the pilot’s control on the flight deck. xx Latency. The additional time, beyond that of the basic perceivable response time of the aircraft due to the response time of the FSTD. yy Light. Operational mass at or near minimum for the specified flight condition. zz Line Oriented Flight Training (LOFT). Refers to aircrew training which involves full mission simulation of situations which are representative of line operations, with special emphasis on situations which involve communications, management and leadership. It means ‘real-time’, full-mission training. aaa Manual Testing. FSTD testing wherein the pilot conducts the test without computer inputs except for initial setup. All modules of the simulation should be active. bbb Master Qualification Test Guide (MQTG). The Authority approved QTG which incorporates the results of tests witnessed by the Authority. The MQTG serves as the reference for future evaluations. ccc Medium. Normal operational weight for flight segment. ddd Night Visual. A visual system capable of meeting, as a minimum, the system brightness and contrast ratio requirements and performance criteria appropriate for the level of qualification sought. The system, when used in training, should provide, as a minimum, all features applicable to the twilight scene, as defined below, with the exception of the need to portray reduced ambient intensity that removes ground cues that are not self-illuminating or illuminated by own ship lights (e.g. landing lights). eee Nominal. Normal operational weight, configuration, speed etc. for the flight segment specified. fff Non-normal Control. A term used in reference to Computer Controlled Aircraft. Non-normal Control is the state where one or more of the intended control, augmentation or protection functions are not fully available.

text: 2009-11-01 2-B-3 JAR-FSTD A

text: Bilaga 1

text: ACJ to JAR-FSTD A.005 (continued) ACJ to JAR-FSTD A.005 (continued) (NOTE: Specific terms such as ALTERNATE, DIRECT, SECONDARY, BACKUP, etc, may be used to define an actual level of degradation). ggg Normal Control. A term used in reference to Computer Controlled Aircraft. Normal Control is the state where the intended control, augmentation and Protection Functions are fully available. hhh Objective Test (Objective Testing). A quantitative assessment based on comparison with data. iii One Step. Refers to the degree of changes to an aircraft that would be allowed as an acceptable change, relative to a fully flight-test validated simulation. The intention of the alternative approach is that changes would be limited to one, rather than a series, of steps away from the baseline configuration. It is understood, however, that those changes which support the primary change (e.g. weight, thrust rating and control system gain changes accompanying a body length change) are considered part of the ‘one step’. jjj Operator. A person, organisation or enterprise engaging in or offering to engage in an aircraft operation. kkk Power Lever Angle. The angle of the pilot's primary engine control lever(s) on the flight deck. This may also be referred to as PLA, THROTTLE, or POWER LEVER. lll Predicted Data. Data derived from sources other than type specific aircraft flight tests. mmm Primary Reference Document. Any regulatory document which has been used by an Authority to support the initial evaluation of a FSTD. nnn Proof-of-Match (POM). A document which shows agreement within defined tolerances between model responses and flight test cases at identical test and atmospheric conditions. ooo Protection Functions. Systems functions designed to protect an aircraft from exceeding its flight and manoeuvre limitations. ppp Pulse Input. An abrupt input to a control followed by an immediate return to the initial position. qqq Qualification Test Guide (QTG). The primary reference document used for the evaluation of an FSTD. It contains test results, statements of compliance and other information to enable the evaluator to assess if the FSTD meets the test criteria described in this manual. rrr Reversible Control System. A partially powered or unpowered control system in which movement of the control surface will backdrive the pilot’s control on the flight deck and/or affect its feel characteristics. sss Robotic Test. A basic performance check of a system’s hardware and software components. Exact test conditions are defined to allow for repeatability. The components are tested in their normal operational configuration and may be tested independently of other system components. ttt Sideslip. Sideslip Angle (degrees) uuu Snapshot. A presentation of one or more variables at a given instant of time. vvv Statement of Compliance (SOC). A declaration that specific requirements have been met. www Step Input. An abrupt input held at a constant value. xxx Subjective Test (Subjective Testing). A qualitative assessment based on established standards as interpreted by a suitably qualified person. yyy Throttle Lever Angle (TLA). The angle of the pilot’s primary engine control lever(s) on the flight deck. zzz Time History. A presentation of the change of a variable with respect to time. aaaa Transport Delay. The total FSTD system processing time required for an input signal from a pilot primary flight control until the motion system, visual system, or instrument response. It is the overall time delay incurred from signal input until output response. It does not include the characteristic delay of the aircraft simulated. bbbb Twilight (Dusk/Dawn) Visual. A visual system capable of meeting, as a minimum, the system brightness and contrast ratio requirements and performance criteria appropriate for the level of qualification sought. The system, when used in training, should provide, as a minimum, full colour presentations of

text: JAR-FSTD A 2-B-4 2009-11-01

text: Bilaga 1

text: reduced ambient intensity (as compared with a daylight visual system), sufficient to conduct a visual approach, landing and airport movement (taxi) cccc Update. The improvement or enhancement of an FSTD. dddd Upgrade. The improvement or enhancement of an FSTD for the purpose of achieving a higher qualification. eeee Validation Data. Data used to prove that the FSTD performance corresponds to that of the aircraft.

text: ffff Validation Flight Test Data. Performance, stability and control, and other necessary test parameters electrically or electronically recorded in an aircraft using a calibrated data acquisition system of sufficient resolution and verified as accurate by the organisation performing the test to establish a reference set of relevant parameters to which like FSTD parameters can be compared. gggg Validation Test. A test by which FSTD parameters can be compared with the relevant validation data. hhhh Visual Ground Segment Test. A test designed to assess items impacting the accuracy of the visual scene presented to the pilot at a decision height (DH) on an ILS approach. iiii Visual System Response Time. The interval from an abrupt control input to the completion of the visual display scan of the first video field containing the resulting different information.

text: jjjj Well-Understood Effect. An incremental change to a configuration or system which can be accurately modelled using proven predictive methods based on known characteristics of the change.

text: 2 Abbreviations

text: A = Aeroplane AC = Advisory Circular ACJ = Advisory Circular Joint A/C = Aircraft Ad = Total initial displacement of pilot controller (initial displacement to final resting amplitude) AFM = Aeroplane Flight Manual AFCS = Automatic Flight Control System AGL = Above Ground Level (metres or feet) An = Sequential amplitude of overshoot after initial X axis crossing, e.g. A1 = 1st overshoot. AEO = All Engines Operating AOA = Angle of Attack (degrees)

text: BC = ILS localizer back course

text: CAT I/II/III = Landing category operations CCA = Computer Controlled Aeroplane 2 2 2 cd/m = Candela/metre , 3.4263 candela/m = 1 ft-Lambert CG = Centre of gravity cm(s) = Centimetre, centimetres CT&M = Correct Trend and Magnitude

text: daN = DecaNewtons dB = Decibel deg(s) = Degree, degrees DGPS = Differential Global Positioning System DH = Decision Height DME = Distance Measuring Equipment DPATO = Defined Point After Take-off DPBL = Define Point Before Landing

text: 2009-11-01 2-B-5 JAR-FSTD A

text: Bilaga 1

text: ACJ to JAR-FSTD A.005 (continued)

text: EGPWS = Enhanced Ground Proximity Warning System EPR = Engine Pressure Ratio EW = Empty Weight

text: FAA = United States Federal Aviation Administration (U.S.) FD = Flight Director FOV = Field Of View FPM = Feet Per Minute FTO = Flying Training Organisation ft = Feet, 1 foot = 0.304801 metres ft-Lambert = Foot-Lambert, 1 ft-Lambert = 3.4263 candela/m

text: 2 2 g = Acceleration due to gravity (metres or feet/sec ), 1g = 9.81 m/sec or 32.2 feet/sec G/S = Glideslope GPS = Global Positioning System GPWS = Ground Proximity Warning System

text: H = Helicopter HGS = Head-up Guidance System

text: IATA = International Air Transport Association ICAO = International Civil Aviation Organisation IGE = In Ground Effect ILS = Instrument Landing System IMC = Instrument Meteorological Conditions in = Inches 1 in = 2.54 cmIOS = Instructor Operating Station IPOM = Integrated proof of match IQTG = International Qualification Test Guide (RAeS Document)

text: JAA = Joint Aviation Authorities JAR = Joint Aviation Requirement JAWS = Joint Airport Weather Studies

text: km = Kilometres 1 km = 0.62137 Statute Miles kPa = KiloPascal (Kilo Newton/Metres2). 1 psi = 6.89476 kPa kts = Knots calibrated airspeed unless otherwise specified, 1 Knot = 0.5148 m/sec or 1.689 ft/sec

text: lb = Pounds LOC = Localizer LOFT = Line oriented flight training LOS = Line oriented simulation LDP = Landing Decision Point

text: m = Metres, 1 Metre = 3.28083 feet MCC = Multi-Crew Co-operation MCTM = Maximum certificated take-off mass (kilos/pounds) MEH = Multi-engine Helicopter min = Minutes MLG = Main landing gear mm = Millimetres MPa = MegaPascals [1 psi = 6894.76 pascals] MQTG = Master Qualification Test Guide ms = Millisecond(s) MTOW = Maximum Take-off Weight

text: n = Sequential period of a full cycle of oscillation

text: JAR-FSTD A 2-B-6 2009-11-01

text: Bilaga 1

text: ACJ to JAR-FSTD A.005 (continued)

text: N = NORMAL CONTROL Used in reference to Computer Controlled Aircraft N/A = Not Applicable N1 = Engine Low Pressure Rotor revolutions per minute expressed in percent of maximum N1/Ng = Gas Generator Speed N2 = Engine High Pressure Rotor revolutions per minute expressed in percent of maximum N2/Nf = Free Turbine Speed NAA = National Aviation Authority NDB = Non-directional beacon NM = Nautical Mile, 1 Nautical Mile = 6 080 feet = 1 852m NN = Non-normal control a state referring to computer controlled aircraft NR = Main Rotor Speed NWA = Nosewheel Angle (degrees)

text: OEI = One Engine Inoperative OGE = Out of Ground Effect OM-B = Operations Manual – Part B (AFM) OTD = Other Training Device

text: P0 = Time from pilot controller release until initial X axis crossing (X axis defined by the resting amplitude) P1 = First full cycle of oscillation after the initial X axis crossing P2 = Second full cycle of oscillation after the initial X axis crossing PANS = Procedure for air navigation services PAPI = Precision Approach Path Indicator System PAR = Precision approach radar Pf = Impact or Feel Pressure PLA = Power Lever Angle PLF = Power for Level Flight Pn = Sequential period of oscillation POM = Proof-of-Match PSD = Power Spectral Density psi = pounds per square inch. (1 psi = 6·89476 kPa) PTT = Part-Task Trainer

text: QTG = Qualification Test Guide

text: R/C = Rate of Climb (metres/sec or feet/min) R/D = Rate of Descent (metres/sec or feet/min) RAE = Royal Aerospace Establishment RAeS = Royal Aeronautical Society REIL = Runway End Identifier Lights RNAV = Radio navigation RVR = Runway Visual Range (metres or feet)

text: s = second(s) sec(s) = second, seconds sm = Statute Mile 1 Statute Mile = 5280 feet = 1609m SOC = Statement of Compliance SUPPS = Supplementary procedures referring to regional supplementary procedures

text: TCAS = Traffic alert and Collision Avoidance System TGL = Temporary Guidance Leaflet T(A) = Tolerance applied to Amplitude T(p) = Tolerance applied to period T/O = Take-off Tf = Total time of the flare manoeuvre duration

text: 2009-11-01 2-B-7 JAR-FSTD A

text: Bilaga 1

text: ACJ to JAR-FSTD A.005 (continued)

text: Ti = Total time from initial throttle movement until a 10% response of a critical engine parameter TLA = Throttle lever angle TLOF = Touchdown and Lift Off TDP = Take-off Decision Point Tt = Total time from Ti to a 90% increase or decrease in the power level specified

text: VASI = Visual Approach Slope Indicator System VDR = Validation Data Roadmap VFR = Visual Flight Rules VGS = Visual Ground Segment Vmca = Minimum Control Speed (Air) Vmcg = Minimum Control Speed (Ground) Vmcl = Minimum Control Speed (Landing) VOR = VHF omni-directional range Vr = Rotate Speed Vs = Stall Speed or minimum speed in the stall V1 = Critical Decision Speed VTOSS = Take-off Safety Speed Vy = Optimum Climbing Speed Vw = Wind Velocity WAT = Weight, Altitude, Temperature 1st Segment = That portion of the take-off profile from lift-off to completion of gear retraction (JAR 25) 2nd Segment = That portion of the take-off profile from after gear retraction to end of climb at V2 and initial flap/slat retraction (JAR 25) 3rd Segment = That portion of the take-off profile after flap/slat retraction is complete (JAR 25)

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD A 2-B-8 2009-11-01

text: Bilaga 1

text: ACJ C – AEROPLANE FLIGHT SIMULATION TRAINING DEVICES

text: ACJ No. 1 to JAR-FSTD A.015 (acceptable means of compliance) FSTD Qualification – Application and Inspection See JAR–FSTD A.015

text: 1 Letter of Application A sample of letter of application is provided overleaf.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-1 JAR-FSTD A

text: Bilaga 1

text: ACJ No 1 to JAR FSTD A.015 (continued)

text: LETTER OF APPLICATION FOR INITIAL JAA EVALUATION OF A FLIGHT SIMULATION TRAINING DEVICE (except BITD).

text: Part A

text: To be submitted not less than 3 months prior to requested qualification date

text: (Date) PRINCIPAL INSPECTOR (JAA NAA OFFICE) (Address)……………………………………………. …………………………………………………………. (City)…………………………………………………. (Country)…………………………………………….

text: Type of FSTD Aircraft Qualification Level Sought Type/Class Flight Simulator FFS A B C D Flight Training Device FTD 1 2 Flight and Navigation Procedures FNPT I II II MCC Trainer Basic Instrument Training Device BITD

text: Dear,

text: Training Device for JAR-FSTD A qualification. The ..…...(FSTD Manufacturer Name) FSTD with its

text: Evaluation is requested for the following configurations and engine fits as applicable: e.g. 767 PW/GE and 757RR 1…………….. 2……………. 3…………….

text: Dates requested are:……………………….. and the FSTD will be located at ………………………………………………………………………………………………………………

text: The QTG will be submitted by……(Date)………… and in any event not less than 30 days before the requested evaluation date unless otherwise agreed with the Authority.

text: Comments: ……………………………………………………………………………………………………………………………… ……………………………………………………………………………………………………………………………… …………………………………………….

text: Signed

text: ……………………… Print name…………….. position/appointment held………………. e mail address……………. telephone number…………

text: JAR-FSTD A 2-C-2 2009-11-01

text: Bilaga 1

text: ACJ No 1 to JAR FSTD A.015 (continued)

text: Part B

text: To be completed with attached QTG results

text: (Date)…………. We have completed tests of the FSTD and declare that it meets all applicable requirements of the JAR– FSTD A (Aeroplane) except as noted below. Appropriate hardware and software configuration control procedures have been established and these are appended for your inspection and approval. The following MQTG tests are outstanding: Tests Comments

text: (Add boxes as required) It is expected that they will be completed and submitted 3 weeks prior to the evaluation date. Signed ………………………

text: position/appointment held………………. E-mail address……………. Telephone number…………

text: 2009-11-01 2-C-3 JAR-FSTD A

text: Bilaga 1

text: ACJ No 1 to JAR FSTD A.015 (continued) 2 Composition of Evaluation Team 2.1 To gain a Qualification Level, an FSTD is evaluated in accordance with a structured routine conducted by a technical team which is appointed by the Authority. The team normally consists of at least the following personnel: a. A technical FSTD inspector of the Authority, or an accredited inspector from another JAA Authority, qualified in all aspects of flight simulation hardware, software and computer modelling or, exceptionally, a person designated by the Authority with equivalent qualifications; and b. One of the following: i. A flight inspector of the Authority, or an accredited inspector from another JAA Authority, who is qualified in flight crew training procedures and is holding a valid type rating on the aeroplane (or for BITD, class rated on the class of aeroplane) being simulated; or ii. A flight inspector of the Authority who is qualified in flight crew training procedures assisted by a Type Rating Instructor, holding a valid type rating on the aeroplane (or for BITD, class rated on the class of aeroplane) being simulated; or, exceptionally, iii. A person designated by the Authority who is qualified in flight crew training procedures and is holding a valid type rating on the aeroplane (or for BITD, class rated on the class of aeroplane) being simulated and sufficiently experienced to assist the technical team. This person should fly out at least part of the functions and subjective test profiles. Where a designee is used as a substitute for one of the Authority’s inspectors, the other person shall be a properly qualified inspector of the Authority or an accredited inspector from another JAA Authority. For an FTD level 1 and FNPT Type I, one suitably qualified Inspector may combine the functions in a. and b. above. For a BITD this team consists of an Inspector from a JAA National Aviation Authority and one from another JAA National Aviation Authority, including the manufacturer‘s Authority if applicable. 2.2 Additionally the following persons should be present: a. For FFS, FTD and FNPT a type or class rated Training Captain from the FSTD operator or main FSTD users. b. For all types, sufficient FSTD support staff to assist with the running of tests and operation of the instructor’s station. 2.3 On a case-by-case basis, when an FFS is being evaluated, the Authority may reduce the evaluation team to an Authority flight inspector supported by a type rated training captain from a main flight simulator user for evaluation of a specific flight simulator of a specific FSTD operator, provided: a. This composition is not being used prior to the second recurrent evaluation; b. Such an evaluation will be followed by an evaluation with a full authority evaluation team; c. The Authority flight inspector will perform some spot checks in the area of objective testing; d. No major change or upgrading has been applied since the directly preceding evaluation; e. No relocation of the FSTD has taken place since the last evaluation; f. A system is established enabling the Authority to monitor and analyse the status of the FSTD on a continuous basis; g. The FSTD hardware and software has been working reliably for the previous years. This should be reflected in the number and kind of (technical log) discrepancies and the results of the quality system audits.

text: 2009-11-01 2-C-5 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 2 to JAR- FSTD A.015 (explanatory material) FSTD Evaluations See JAR–FSTD A.015

text: 1 General 1.1 During initial and recurrent FSTD evaluations it will be necessary for the Authority to conduct the Objective and Subjective tests described in JAR–FSTD A.030 and JAR–FSTD A.035, and detailed in ACJ No 1 to JAR-FSTD A.030. There will be occasions when all tests cannot be completed – for example during recurrent evaluations on a convertible FSTD – but arrangements should be made for all tests to be completed within a reasonable time. 1.2 Following an evaluation, it is possible that a number of defects may be identified. Generally these defects should be rectified and the Authority notified of such action within 30 days. Serious defects, which affect flight crew training, testing and checking, could result in an immediate downgrading of the Qualification Level, or if any defect remains unattended without good reason for period greater than 30 days, subsequent downgrading may occur or the FSTD Qualification could be revoked.

text: 2 Initial Evaluations 2.1 Objective Testing 2.1.1 Objective Testing is centred around the QTG. Before testing can begin on an initial evaluation the acceptability of the validation tests contained in the QTG should be agreed with the Authority well in advance of the evaluation date to ensure that the FSTD time especially devoted to the running of some of the tests by the Authority is not wasted. The acceptability of all tests depends upon their content, accuracy, completeness and recency of the results. 2.1.2 Much of the time allocated to Objective Tests depends upon the speed of the automatic and manual systems set up to run each test and whether or not special equipment is required. The Authority will not necessarily warn the FSTD operator of the sample validations tests which will be run on the day of the evaluation, unless special equipment is required. It should be remembered that the FSTD cannot be used for Subjective Tests whilst part of the QTG is being run. Therefore sufficient time (at least 8 consecutive hours) should be set aside for the examination and running of the QTG. A useful explanation of how the validation tests should be run is contained in the ‘RAeS Aeroplane Flight Simulator Evaluation Handbook’ (February 95 or as amended) produced in support of the ICAO Manual of Criteria for the Qualification of Flight Simulators and JAR–FSTD A. 2.2 Subjective Testing

text: 2.2.1 The Subjective Tests for the evaluation can be found in ACJ No 1 to JAR-FSTD A.030, and a suggested Subjective Test Profile is described in sub-paragraph 4.6 below. 2.2.2 Essentially one working day is required for the Subjective Test routine, which effectively denies use of the FSTD for any other purpose. 2.3 Conclusion 2.3.1 To ensure adequate coverage of Subjective and Objective Tests and to allow for cost effective rectification and re-test before departure of the inspection team, adequate time (up to three consecutive days) should be dedicated to an initial evaluation of an FSTD. 3 Recurrent Evaluations 3.1 Objective Testing 3.1.1 During recurrent evaluations, the Authority will wish to see evidence of the successful running of the QTG between evaluations. The Authority will select a number of tests to be run during the evaluation, including those that may be cause for concern. Again adequate notification would be given when special equipment is required for the test. 3.1.2 Essentially the time taken to run the Objective Tests depends upon the need for special equipment, if any, and the test system, and the FSTD cannot be used for Subjective Tests or other functions whilst testing is in progress. For a modern FSTD incorporating an automatic test system, four (4) hours would normally be required. FSTDs that rely upon Manual Testing may require a longer period of time. 3.2 Subjective Testing

text: JAR-FSTD A 2-C-6 2009-11-01

text: Bilaga 1

text: ACJ No. 2 to JAR-FSTD A.015 (continued)

text: 3.2.1 Essentially the same subjective test routine should be flown as per the profile described in subparagraph 4.6 below with a selection of the subjective tests taken from ACJ No 1 to JAR- FSTD A.030. 3.2.2 Normally, the time taken for recurrent Subjective Testing is about four (4) hours, and the FSTD cannot perform other functions during this time. 3.3 Conclusion 3.3.1 To ensure adequate coverage of Subjective and Objective Tests during a recurrent evaluation, a total of 8 hours should be allocated, (4 hours for a BITD). However, it should be remembered that any FSTD deficiency that arises during the evaluation could necessitate the extension of the evaluation period. 3.3.2 In the case of a BITD, the recurrent evaluation may be conducted by one suitably qualified Flight Inspector only, in conjunction with the visit of any Registered Facility or inspection of any Flight Training Organisation, using the BITD.

text: 4 Functions and Subjective Tests – Suggested Test Routine 4.1 During initial and recurrent evaluations of an FSTD, the competent Authority will conduct a series of Functions and Subjective Tests that together with the Objective Tests complete the comparison of the FSTD with the type or class of aeroplane. 4.2 Whereas functions tests verify the acceptability of the simulated aeroplane systems and their integration, Subjective Tests verify the fitness of the FSTD in relation to training, checking and testing tasks.

text: 4.3 The FSTD should provide adequate flexibility to permit the accomplishment of the desired/required tasks while maintaining an adequate perception by the flight crew that they are operating in a real aeroplane environment. Additionally, the Instructor Operating Station (IOS) should not present an unnecessary distraction from observing the activities of the flight crew whilst providing adequate facilities for the tasks. 4.4 Section 1 of JAR– FSTD A sets out the requirements, and the ACJs in Section 2 the means of compliance for qualification. However, it is important that both the competent Authority and the FSTD operator understand what to expect from the routine of FSTD Functions and Subjective Tests. It should be remembered that part of the Subjective Tests routine for an FSTD should involve an uninterrupted fly-out (except for FTD level 1) comparable with the duration of typical training sessions in addition to assessment of flight freeze and repositioning. An example of such a profile is to be found in sub-paragraph 4.6 (4.7 for BITD) below. (A useful explanation of Functions and Subjective Tests and an example of Subjective Test routine check-list may be found in the RAeS Airplane Flight Simulator Evaluation Handbook Volume II (February 95 or as amended) produced in support of the ICAO Manual of Criteria for the Qualification of Flight Simulators and JAR–FSTD A. 4.5 JAA Regulatory Authorities and FSTD operators who are unfamiliar with the evaluation process are advised to contact a suitably experienced JAA Authority.

text: 2009-11-01 2-C-7 JAR-FSTD A

text: Bilaga 1

text: ACJ No 2 to JAR FSTD A.015 (continued)

text: 4.6 Typical Test Profile for a FSTD A.

text: FL180 ENG-OUT 1 CABIN EN-RTE DEPRESS CLIMB V+TRIM (WARN PERF TAXI FL070 ENG ±20 KT MASKS) CX INSTRUMENT 5,000 ENG S/DOWN DEPARTURE ENG OUT SLAMS CLIMB FL050 R-CLIMB PERF R/W TURNS etc... MMO CRUISE (WARN APU FL350 FUNCTION (CAB PRESS) TRIMS CONTROLS)

text: ENG S/DOWN FL290 ENG 2 RELIGHT RELIGHT

text: 1 FL140

text: (WINDMILL OR INTERNAL) 2

text: HIGH SPEED DESCENT

text: VMO FL150 (WARN STALLS L/G & FLAPS CONTROLS) FL100 HYDRAULIC RAT NON NORMAL

text: INSTRUMENT 3

text: 3 ARRIVAL G/A VISUAL CCT ILS LEFT/RIGHT NORMAL

text: ILS NORMAL LAND

text: Note: (1) The Typical Test Profile (approximately 2 hours) should be flown at aeroplane masses at, or close to, the maximum allowable mass for the ambient atmospheric conditions. Those ambient conditions should be varied from Standard Atmosphere to test the validity of the limits of temperature and pressure likely to be required in the practical use of the FSTD. Visual exercises only apply to FSTDs fitted with a visual system.

text: (2) Flight with AFCS

text: (3) Manual handling qualities are purely generic and should not provide negative training

text: 4.7 Typical Subjective Test Profile for BITDs (approximately 2 hours) - items and altitudes as applicable.

text: - Instrument departure, rate of climb, climb performance

text: - Level-off at 4 000 ft

text: - Fail engine (if applicable)

text: - Engine out climb to 6 000 ft (if applicable)

text: - Engine out cruise performance (if applicable), restart engine

text: - All engine cruise performance with different power settings

text: - Descent to 2000 ft

text: - All engine performance with different configurations, followed by ILS approach

text: - All engine go-around

text: - Non-precision approach

text: JAR-FSTD A 2-C-8 2009-11-01

text: Bilaga 1

text: ACJ No 2 to JAR FSTD A.015 (continued) - Go-around with engine failure (if applicable) - Engine out ILS approach (if applicable) - Go-around engine out (if applicable) - Non precision approach engine out (if applicable), followed by go-around - Restart engine (if applicable) - Climb to 4000 ft - Manoeuvring: - Normal turns left and right - Steep turns left and right - Acceleration and deceleration within operational range - Approaching to stall in different configurations - Recovery from spiral dive - Auto flight performance (if applicable) - System malfunctions - Approach

text: 2009-11-01 2-C-9 JAR-FSTD A

text: Bilaga 1

text: ACJ to JAR-FSTD A.020 (acceptable means of compliance) Validity of FSTD Qualification See JAR-FSTD A.020

text: 1. Prerequisites 1.1 On a case-by-case basis, the Authority may grant an extended validity of a FSTD qualification in excess of 12 months up to a maximum of 36 months, to a specific FSTD operator for a specific FSTD, provided: a. an initial and at least one recurrent successful evaluation have been performed on this FSTD by the same Authority; b. the FSTD operator has got a satisfactory record of successful regulatory FSTD evaluations over a period of at least 3 years; c. the FSTD operator has established and successfully maintained a Quality System for at least 3 years; d. the Authority performs a formal audit of the FSTD operator's Quality System every calendar year; e. an accountable person of the FSTD operator with FSTD and training experience acceptable to the Authority (such as a type rated training captain), reviews the regular reruns of the QTG and conducts the relevant function and subjective tests every 12 months; f. a report detailing the results of the QTG rerun tests and function and subjective evaluation will be signed and submitted by the accountable person described under subparagraph (e) above to the Authority.

text: 2. Prerogative of the Authority The Authority reserves the right to perform FSTD evaluations whenever it deems it necessary.

text: ACJ No.1 to JAR-FSTD A.025 (acceptable means of compliance) Quality System See JAR– FSTD A.025

text: 1. Introduction

text: 1.1 In order to show compliance with JAR– FSTD A.025, an FSTD operator should establish his Quality System in accordance with the instructions and information contained in the following paragraphs. 2 General 2.1 Terminology a. The terms used in the context of the requirement for an FSTD operator’s Quality System have the following meanings: i. Accountable Manager. The person acceptable to the Authority who has corporate authority for ensuring that all necessary activities can be financed and carried out to the standard required by the Authority, and any additional requirements defined by the FSTD operator. ii. Quality Assurance. All those planned and systematic actions necessary to provide adequate confidence that specified performance, functions and characteristics satisfy given requirements. iii. Quality Manager. The manager, acceptable to the Authority, responsible for the management of the Quality System, monitoring function and requesting corrective actions. 2.2 Quality Policy 2.2.1 An FSTD operator should establish a formal written Quality Policy Statement that is a commitment by the Accountable Manager as to what the Quality System is intended to achieve. The Quality Policy should reflect the achievement and continued compliance with JAR– FSTD A together with any additional standards specified by the FSTD operator.

text: JAR-FSTD A 2-C-10 2009-11-01

text: Bilaga 1

text: ACJ No 1 to JAR FSTD A 025 (continued)ACJ No. 1 to JAR-FSTD A.025 (continued) 2.2.2 The Accountable Manager is an essential part of the FSTD qualification holder’s organisation. With regard to the above terminology, the term ‘Accountable Manager’ is intended to mean the Chief Executive/President/Managing Director/General Manager etc. of the FSTD operator’s organisation, who by virtue of his position has overall responsibility (including financial) for managing the organisation. 2.2.3 The Accountable Manager will have overall responsibility for the FSTD qualification holder’s Quality System including the frequency, format and structure of the internal management evaluation activities as prescribed in paragraph 4.9 below. 2.3 Purpose of the Quality System 2.3.1 The Quality System should enable the FSTD operator to monitor compliance with JAR– FSTD A, and any other standards specified by that FSTD operator, or the Authority, to ensure correct maintenance and performance of the device. 2.4 Quality Manager 2.4.1 The primary role of the Quality Manager is to verify, by monitoring activity in the fields of FSTD qualification, that the standards required by the Authority, and any additional requirements defined by the FSTD operator, are being carried out under the supervision of the relevant Manager. 2.4.2 The Quality Manager should be responsible for ensuring that the Quality Assurance Programme is properly established, implemented and maintained. 2.4.3 The Quality Manager should: a. Have direct access to the Accountable Manager; b. Have access to all parts of the FSTD operator’s and, as necessary, any sub-contractor’s organisation. 2.4.4 The posts of the Accountable Manager and the Quality Manager may be combined by FSTD operators whose structure and size may not justify the separation of those two posts. However, in this event, Quality Audits should be conducted by independent personnel. 3 Quality System 3.1 Introduction 3.1.1 The FSTD operator’s Quality System should ensure compliance with FSTD qualification requirements, standards and procedures. 3.1.2 The FSTD operator should specify the structure of the Quality System. 3.1.3 The Quality System should be structured according to the size and complexity of the organisation to be monitored. 3.2 Scope 3.2.1 As a minimum, the Quality System should address the following: a. The provision of JAR–FSTD A. b. The FSTD operator’s additional standards and procedures. c. The FSTD operator’s Quality Policy. d. The FSTD operator’s organisational structure. e. Responsibility for the development, establishment and management of the Quality System. f. Documentation, including manuals, reports and records. g. Quality Procedures. h. Quality Assurance Programme. i. The provision of adequate financial, material and human resources. j. Training requirements for the various functions in the organisation.

text: 2009-11-01 2-C-11 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 1 to JAR-FSTD A.025 (continued) 3.2.2 The Quality System should include a feedback system to the Accountable Manager to ensure that corrective actions are both identified and promptly addressed. The feedback system should also specify who is required to rectify discrepancies and non-compliance in each particular case, and the procedure to be followed if corrective action is not completed within an appropriate timescale. 3.3 Relevant Documentation Relevant documentation should include the following: a. Quality Policy. b. Terminology. c. Reference to specified STD technical standards. d. A description of the organisation. e. The allocation of duties and responsibilities. f. Qualification procedures to ensure regulatory compliance. g. The Quality Assurance Programme, reflecting: i. Schedule of the monitoring process. ii. Audit procedure iii. Reporting procedures. iv. Follow-up and corrective action procedures. v. Recording system. h. Document control. 4. Quality Assurance Programme 4.1 Introduction 4.1.1 The Quality Assurance Programme should include all planned and systematic actions necessary to provide confidence that all maintenance is conducted and all performance maintained in accordance with all applicable requirements, standards and procedures. 4.1.2 When establishing a Quality Assurance Programme, consideration should, at least, be given to the paragraphs 4.2 to 4.9 below. 4.2 Quality Inspection 4.2.1 The primary purpose of a quality inspection is to observe a particular event/action/document etc., in order to verify whether established procedures and requirements are followed during the accomplishment of that event and whether the required standard is achieved. 4.2.2 Typical subject areas for quality inspections are: Actual STD operation. Maintenance. Technical standards. Flight simulator safety features. 4.3 Audit 4.3.1 An audit is a systematic and independent comparison of the way in which an activity is being conducted against the way in which the published procedures say it should be conducted. 4.3.2 Audits should include at least the following quality procedures and processes: a. A statement explaining the scope of the audit. b. Planning and preparation.

text: JAR-FSTD A 2-C-12 2009-11-01

text: Bilaga 1

text: ACJ No. 1 to JAR-FSTD A.025 (continued) c. Gathering and recording evidence d. Analysis of the evidence. 4.3.3 Techniques which contribute to an effective audit are: a. Interviews or discussions with personnel. b. A review of published documents. c. The examination of an adequate sample of records. d. The witnessing of the activities which make up the operation e. The preservation of documents and the recording of observations. 4.4 Auditors 4.4.1 An FSTD operator should decide, depending on the complexity and size of the organisation, whether to make use of a dedicated audit team or a single auditor. In any event, the auditor or audit team should have relevant FSTD experience. 4.4.2 The responsibilities of the auditors should be clearly defined in the relevant documentation. 4.5 Auditor’s Independence 4.5.1 Auditors should not have any day to day involvement in the area of activity which is to be audited. An FSTD operator may, in addition to using the services of full-time dedicated personnel belonging to a separate quality department, undertake the monitoring of specific areas or activities by the use of part-time auditors. Due to the technological complexity of FSTDs, which requires auditors with very specialised knowledge and experience, an FSTD operator may undertake the audit function by the use of part-time personnel from within his own organisation or from an external source under the terms of an agreement acceptable to the Authority. In all cases the FSTD operator should develop suitable procedures to ensure that persons directly responsible for the activities to be audited are not selected as part of the auditing team. Where external auditors are used, it is essential that any external specialist is familiar with the type of device conducted by the FSTD operator. 4.5.2 The FSTD operator’s Quality Assurance Programme should identify the persons within the company who have the experience, responsibility and authority to: a. Perform quality inspections and audits as part of ongoing Quality Assurance. b. Identify and record any concerns or findings, and the evidence necessary to substantiate such concerns or findings. c. Initiate or recommend solutions to concerns or findings through designated reporting channels. d. Verify the implementation of solutions within specific time scales. e. Report directly to the Quality Manager. 4.6 Audit Scope 4.6.1 FSTD operators are required to monitor compliance with the procedures they have designed to ensure specified performance and functions. In doing so they should as a minimum, and where appropriate, monitor: a. Organisation. b. Plans and objectives. c. Maintenance procedures. d. FSTD Qualification Level. e. Supervision. f. FSTD technical status. g. Manuals, logs, and records. h. Defect deferral.

text: 2009-11-01 2-C-13 JAR-FSTD A

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.025 (continued) ACJ No. 1 to JAR-FSTD A.025 (continued)

text: i. Personnel training. j. Aeroplane modifications management. 4.7 Auditing scheduling 4.7.1 A Quality Assurance Programme should include a defined audit schedule and a periodic review. The schedule should be flexible, and allow unscheduled audits when trends are identified. Follow-up audits should be scheduled when necessary to verify that corrective action was carried out and that it was effective. 4.7.2 An FSTD operator should establish a schedule of audits to be completed during a specified calendar period. All aspects of the operation should be reviewed within every period of 12 months in accordance with the programme unless an extension to the audit period is accepted as explained below. An FSTD operator may increase the frequency of audits at his discretion but should not decrease the frequency without the agreement of the Authority. 4.7.3 When an FSTD operator defines the audit schedule, significant changes to the management, organisation, or technologies should be considered as well as changes to the regulatory requirements. 4.7.4 For FSTD operators whose structure and size may not justify the completion of a complex system of audits, it may be appropriate to develop a Quality Assurance Programme that employs a checklist. The checklist should have a supporting schedule that requires completion of all checklist items within a specified time scale, together with a statement acknowledging completion of a periodic review by top management. 4.7.5 Whatever arrangements are made, the FSTD operator retains the ultimate responsibility for the Quality System and especially the completion and follow up of corrective actions. 4.8 Monitoring and Corrective Action 4.8.1 The aim of monitoring within the Quality System is primarily to investigate and judge its effectiveness and thereby to ensure that defined policy, performance and function standards are continuously complied with. Monitoring activity is based upon quality inspections, audits, corrective action and follow-up. The FSTD operator should establish and publish a quality procedure to monitor regulatory compliance on a continuing basis. This monitoring activity should be aimed at eliminating the causes of unsatisfactory performance. 4.8.2 Any non-compliance identified as a result of monitoring should be communicated to the manager responsible for taking corrective action or, if appropriate, the Accountable Manager. Such non-compliance should be recorded, for the purpose of further investigation, in order to determine the cause and to enable the recommendation of appropriate corrective action. 4.8.3 The Quality Assurance Programme should include procedures to ensure that corrective actions are taken in response to findings. These quality procedures should monitor such actions to verify their effectiveness and that they have been completed. Organisational responsibility and accountability for the implementation of corrective actions resides with the department cited in the report identifying the finding. The Accountable Manager will have the ultimate responsibility for resourcing the corrective action and ensuring, through the Quality Manager, that the corrective action has re-established compliance with the standard required by the Authority, and any additional requirements defined by the FSTD operator. 4.8.4 Corrective action a. Subsequent to the quality inspection/audit, the FSTD operator should establish: i. The seriousness of any findings and any need for immediate corrective action. ii. Cause of the finding. iii. Corrective actions required to ensure that the non-compliance does not recur. iv. A schedule for corrective action. v. The identification of individuals or departments responsible for implementing corrective action. vi. Allocation of resources by the Accountable Manager, where appropriate.

text: JAR-FSTD A 2-C-14 2009-11-01

text: Bilaga 1

text: ACJ No. 1 to JAR-FSTD A.025 (continued) 4.8.5 The Quality Manager should: a. Verify that corrective action is taken by the manager responsible in response to any finding of noncompliance. b. Verify that corrective action includes the elements outlined in paragraph 4.8.4 above. c. Monitor the implementation and completion of corrective action. d. Provide management with an independent assessment of corrective action, implementation and completion. e. Evaluate the effectiveness of corrective action through the follow-up process. 4.9 Management Evaluation 4.9.1 A management evaluation is a comprehensive, systematic, documented review of the Quality System and procedures by the management, and it should consider: a. The results of quality inspections, audits and any other indicators. b. The overall effectiveness of the management organisation in achieving stated objectives. 4.9.2 A management evaluation should identify and correct trends, and prevent, where possible, future non-conformities. Conclusions and recommendations made as a result of an evaluation should be submitted in writing to the responsible manager for action. The responsible manager should be an individual who has the authority to resolve issues and take action. 4.9.3 The Accountable Manager should decide upon the frequency, format, and structure of internal management evaluation activities. 4.10 Recording 4.10.1 Accurate, complete, and readily accessible records documenting the results of the Quality Assurance Programme should be maintained by the FSTD operator. Records are essential data to enable an FSTD operator to analyse and determine the root causes of non-conformity, so that areas of non-compliance can be identified and addressed. 4.10.2 The following records should be retained for a period of 5 years: a. Audit schedules. b. Quality inspection and audit reports. c. Response to findings. d. Corrective action reports. e. Follow-up and closure reports; and f. Management evaluation reports. 5 Quality Assurance responsibility for sub-contractors 5.1 Sub-contractors 5.1.1 FSTD operators may decide to sub-contract out certain activities to external agencies for the provision of services related to areas such as: a. Maintenance. b. Manual preparation. 5.1.2 The ultimate responsibility for the product or service provided by the sub-contractor always remains with the FSTD operator. A written agreement should exist between the FSTD operator and the subcontractor clearly defining the services and quality to be provided. The sub-contractor's activities relevant to the agreement should be included in the FSTD operator's Quality Assurance Programme.

text: 2009-11-01 2-C-15 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 1 to JAR-FSTD A.025 (continued) 5.1.3 The FSTD operator should ensure that the sub-contractor has the necessary authorisation/approval when required, and commands the resources and competence to undertake the task. If the FSTD operator requires the sub-contractor to conduct activity which exceeds the sub-contractor’s authorisation/approval, the FSTD operator is responsible for ensuring that the sub-contractor’s Quality Assurance takes account of such additional requirements.

text: 6 Quality System Training 6.1 General 6.1.1 An FSTD operator should establish effective, well planned and resourced quality related briefing for all personnel. 6.1.2 Those responsible for managing the Quality System should receive training covering: a. An introduction to the concept of the Quality System. b. Quality management. c. Concept of Quality Assurance. d. Quality manuals. e. Audit techniques. f. Reporting and recording g. The way in which the Quality System will function in the organisation. 6.1.3 Time should be provided to train every individual involved in quality management and for briefing the remainder of the employees. The allocation of time and resources should be sufficient for the scope of the training. 6.2 Sources of Training 6.2.1 Quality management courses are available from the various national or international Standards Institutions, and an FSTD operator should consider whether to offer such courses to those likely to be involved in the management of Quality Systems. FSTD operators with sufficient appropriately qualified staff should consider whether to carry out in-house training. 7. Standard Measurements for Flight Simulator Quality 7.1 General 7.1.1 It is recognised that a Quality System tied to measurement of FSTD performance will probably lead to improving and maintaining training quality. One acceptable means of measuring FSTD performance is as th defined and agreed by industry in ARINC report 433 (May 15 , 2001 or as amended) entitled “Standard Measurements for Flight Simulator Quality”.

text: JAR-FSTD A 2-C-16 2009-11-01

text: Bilaga 1

text: ACJ No. 2 to JAR-FSTD A.025 BITD Operator's Quality System See JAR-FSTD A.025

text: 1 Introduction 1.1 In order to show compliance with JAR-FSTD A.025, a BITD operator should establish his Quality System in accordance with the instructions and information contained in the following paragraphs. 2 Quality Policy 2.1 A BITD operator should establish a formal written Quality Policy Statement that is a commitment by the Accountable Manager as to what the Quality System is intended to achieve. 2.2 The Accountable Manager is someone who by virtue of his position has overall authority and responsibility (including financial) for managing the organization. 2.3 The Quality Manager is responsible for the function of the Quality System and requesting corrective actions. 3 Quality System 3.1 The Quality System should enable the BITD operator to monitor compliance with JAR-FSTD A, and any other standards specified by that BITD operator to ensure correct maintenance and performance of the device. 3.2 A Quality Manager oversees the day-to-day control of quality. 3.3 For a small FSTD operator the position of the Accountable Manager and the Quality Manager may be combined. However, in this event, independent personnel should conduct Quality Audits. 4 Quality Assurance Programme 4.1 A Quality Assurance Programme together with a statement acknowledging completion of a periodic review by the Accountable Manager should include the following: 4.1.1 A maintenance facility which provides suitable BITD hardware and software test and maintenance capability. 4.1.2 A recording system in the form of a technical log in which defects, deferred defects and development work are listed, interpreted, actioned and reviewed within a specified time scale. 4.1.3 Planned routine maintenance of the BITD and periodic running of the QTG with adequate manning to cover BITD operating periods and routine maintenance work. 4.1.4 A planned audit schedule and a periodic review should be used to verify that corrective action was carried out and that it was effective. The auditor should have adequate knowledge of BITDs and should be acceptable to the Authority. 5 Quality System Training 5.1 The Quality Manager should receive appropriate Quality System training and brief other personnel on the procedures.

text: 2009-11-01 2-C-17 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 3 to JAR-FSTD A.025 Installations See JAR-FSTD A.025(c)

text: 1 Introduction 1.1 This ACJ identifies those elements that are expected to be addressed, as a minimum, to ensure that the FSTD installation provides a safe environment for the users and operators of the FSTD under all circumstances. 2 Expected Elements 2.1 Adequate fire/smoke detection, warning and suppression arrangements should be provided to ensure safe passage of personnel from the FSTD. 2.2 Adequate protection should be provided against electrical, mechanical, hydraulic and pneumatic hazards – including those arising from the control loading and motion systems to ensure maximum safety of all personnel in the vicinity of the FSTD. 2.3 Other areas that should be addressed include: a. A two way communication system that remains operational in the event of a total power failure. b. Emergency lighting c. Escape exits and escape routes d. Occupant restraints (seats, seat belts etc.). e. External warning of motion and access ramp or stairs activity. f. Danger area markings. g. Guard rails and gates h. Motion and control loading emergency stop controls accessible from either pilot or instructor seats; and i. A manual or automatic electrical power isolation switch.

text: JAR-FSTD A 2-C-18 2009-11-01

text: Bilaga 1

text: ACJ No. 1 to JAR-FSTD A.030 (acceptable means of compliance) FSTDs qualified on or after 1 August 2008 See JAR–FSTD A.030

text: NOTE: The structure and numbering of this ACJ departs from JAA layout due to the complexity of the technical content and the need to retain harmonisation with the ICAO Manual of Criteria for the Qualification of Flight Simulators (1995 or as amended). 1 Introduction 1.1 Purpose. This ACJ establishes the criteria that define the performance and documentation requirements for the evaluation of FSTDs used for training, testing and checking of flight crewmembers. These test criteria and methods of compliance were derived from extensive experience of Authorities and the industry.

text: 1.2 Background 1.2.1 The availability of advanced technology has permitted greater use of FSTDs for training, testing and checking of flight crewmembers. The complexity, costs and operating environment of modern aircraft also encourages broader use of advanced simulation. FSTDs can provide more in-depth training than can be accomplished in aircraft and provide a safe and suitable learning environment. Fidelity of modern FSTDs is sufficient to permit pilot assessment with the assurance that the observed behaviour will transfer to the aircraft. Fuel conservation and reduction in adverse environmental effects are important by-products of FSTD use. 1.2.2 The methods, procedures, and testing criteria contained in this ACJ are the result of the experience and expertise of Authorities, operators, and aeroplane and FSTD manufacturers. From 1989 to 1992 a specially convened international working group under the sponsorship of the Royal Aeronautical Society (RAeS) held several meetings with the stated purpose of establishing common test criteria that would be recognised internationally. The final RAeS document, entitled International Standards for the Qualification of Airplane Flight Simulators, dated January 1992 (ISBN 0–903409–98–4), was the core document used to establish these JAA criteria and also the ICAO Manual of Criteria for the Qualification of Flight Simulators (1995 or as amended). An international review under the co-chair of FAA and JAA during 2001 was the basis for a major modification of the ICAO Manual of Criteria for the Qualification of Flight Simulators (1995 or as amended) and for the JAR-FSTD A document. 1.2.3 In showing compliance with JAR–FSTD A.030, the Authority expects account to be taken of the IATA document entitled ‘Design and Performance Data Requirements for Flight Simulators’ – (1996 or as amended), as appropriate to the Qualification Level sought. In any case early contact with the Authority is advised at the initial stage of FSTD build to verify the acceptability of the data. 1.3 Levels of FSTD qualification. Parts 2, and 3 of this ACJ describe the minimum requirements for qualifying Level A, B, C and D aeroplane FFS, Level 1 and 2 aeroplane FTDs, FNPT types I, II and IIMCC and BITDs.

text: See also Appendix 1 to JAR-FSTD A.030 1.4 Terminology. Terminology and abbreviations of terms used in this ACJ are contained in ACJ to JAR-FSTD A.005. 1.5 Testing for FSTD qualification 1.5.1 The FSTD should be assessed in those areas that are essential to completing the flight crewmember training, testing and checking process. This includes the FSTDs’ longitudinal and lateraldirectional responses; performance in take-off, climb, cruise, descent, approach, landing; specific operations; control checks; flight deck, flight engineer, and instructor station functions checks; and certain additional requirements depending on the complexity or Qualification Level of the FSTD. The motion and visual systems (where applicable) will be evaluated to ensure their proper operation. Tolerances listed for parameters in the validation tests (Paragraph 2) of this ACJ are the maximum acceptable for FSTD qualification and should not be confused with FSTD design tolerances.

text: 1.5.2 For FFSs and FTDs the intent is to evaluate the FSTD as objectively as possible. Pilot acceptance, however, is also an important consideration. Therefore, the FSTD will be subjected to validation, and functions and subjective tests listed in Part 2 and 3 of this ACJ.

text: 2009-11-01 2-C-19 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 1 to JAR-FSTD A.030 (continued)

text: Validation tests are used to compare objectively FFSs and FTDs with aircraft data to ensure that they agree within specified tolerances. Functions and subjective tests provide a basis for evaluating FSTD capability to perform over a typical training period and to verify correct operation of the FSTD.

text: 1.5.3 For initial qualification of FFSs and FTDs aeroplane manufacturer’s validation flight test data is preferred. Data from other sources may be used, subject to the review and concurrence of the Authority. 1.5.4 For FNPTs and BITDs generic data packages can be used. In this case, for an initial evaluation only Correct Trend and Magnitude (CT&M) can be used. The tolerances listed in this ACJ are applicable for recurrent evaluations and should be applied to ensure the device remains at the standard initially qualified. For initial qualification testing of FNPTs and BITDs, Validation Data will be used. They may be derived from a specific aeroplane within the class of aeroplane the FNPT or BITD is representing or they may be based on information from several aeroplanes within the class. With the concurrence of the Authority, it may be in the form of a manufacturer's previously approved set of Validation Data for the applicable FNPT or BITD. Once the set of data for a specific FNPT or BITD has been accepted and approved by the Authority, it will become the Validation Data that will be used as reference for subsequent recurrent evaluations with the application of the stated tolerances.

text: The substantiation of the set of data used to build the Validation Data should be in the form of an engineering report and shall show that the proposed Validation Data are representative of the aeroplane or the class of aeroplane modelled. This report may include flight test data, manufacturer’s design data, information from the Aeroplane Flight Manual (AFM) and Maintenance Manuals, results of approved or commonly accepted simulations or predictive models, recognized theoretical results, information from the public domain, or other sources as deemed necessary by the FSTD manufacturer to substantiate the proposed model.

text: 1.5.5 In the case of new aircraft programmes, the aircraft manufacturer’s data partially validated by flight test data, may be used in the interim qualification of the FSTD. However, the FSTD should be re-evaluated following the release of the manufacturer’s approved data. The schedule should be as agreed by the Authority, FSTD operator, FSTD manufacturer, and aircraft manufacturer. 1.5.6 FSTD operators seeking initial or upgrade evaluation of a FSTD should be aware that performance and handling data for older aircraft may not be of sufficient quality to meet some of the test standards contained in this ACJ. In this instance it may be necessary for an operator to acquire additional flight test data. 1.5.7 During FSTD evaluation, if a problem is encountered with a particular validation test, the test may be repeated to ascertain if the problem was caused by test equipment or FSTD operator error. Following this, if the test problem persists, an FSTD operator should be prepared to offer an alternative test. 1.5.8 Validation tests that do not meet the test criteria should be addressed to the satisfaction of the Authority.

text: 1.6 Qualification Test Guide (QTG) 1.6.1 The QTG is the primary reference document used for evaluating a FSTD. It contains test results, statements of compliance and other information for the evaluator to assess if the FSTD meets the test criteria described in this ACJ. 1.6.2 The FSTD operator (in case of a BITD the manufacturer) should submit a QTG that includes:

text: a. A title page with FSTD operator (in case of a BITD the manufacturer) and approval Authority signature blocks. b. A FSTD information page (for each configuration in the case of convertible FSTDs) providing: i. FSTD operator’s FSTD identification number, for a BITD the model and serial number. ii. Aeroplane model and series being simulated. For FNPTs and BITDs aeroplane model or class being simulated. iii. References to aerodynamic data or sources for aerodynamic model.

text: JAR-FSTD A 2-C-20 2009-11-01

text: Bilaga 1

text: ACJ No. 1 to JAR-FSTD A.030 (continued) iv. References to engine data or sources for engine model. v. References to flight control data or sources for flight controls model. vi. Avionic equipment system identification where the revision level affects the training and checking capability of the FSTD. vii. FSTD model and manufacturer. viii. Date of FSTD manufacture. ix. FSTD computer identification. x. Visual system type and manufacturer (if fitted). xi. Motion system type and manufacturer (if fitted). c. Table of contents. d. List of effective pages and log of test revisions. e. Listing of all reference and source data. f. Glossary of terms and symbols used. g. Statements of Compliance (SOC) with certain requirements. SOC’s should refer to sources of information and show compliance rationale to explain how the referenced material is used, applicable mathematical equations and parameter values, and conclusions reached. h. Recording procedures and required equipment for the validation tests. i. The following items are required for each validation test: i. Test title. This should be short and definitive, based on the test title referred to in paragraph 2.3 of this ACJ; ii. Test objective. This should be a brief summary of what the test is intended to demonstrate; iii. Demonstration procedure. This is a brief description of how the objective is to be met; iv. References. These are the aeroplane data source documents including both the document number and the page or condition number; v. Initial conditions. A full and comprehensive list of the test initial conditions is required; vi. Manual test procedures. Procedures should be sufficient to enable the test to be flown by a qualified pilot, using reference to flight deck instrumentation and without reference to other parts of the QTG or flight test data or other documents; vii. Automatic test procedures (if applicable). viii. Evaluation criteria. Specify the main parameter(s) under scrutiny during the test; ix. Expected result(s). The aeroplane result, including tolerances and, if necessary, a further definition of the point at which the information was extracted from the source data. For FNPTs and BITDs, the initial validation test result including tolerances is sufficient. x. Test result. Dated FSTD validation test results obtained by the FSTD operator. Tests run on a computer that is independent of the FSTD are not acceptable. For a BITD the validation test results are normally obtained by the manufacturer; xi. Source data. Copy of the aeroplane source data, clearly marked with the document, page number, issuing authority, and the test number and title as specified in sub-para (i) above. Computer generated displays of flight test data overplotted with FSTD data are insufficient on their own for this requirement. xii. Comparison of results. An acceptable means of easily comparing FSTD test results with the validation data. xiii. The preferred method is overplotting. The FSTD operator’s FSTD test results should be recorded on a multi-channel recorder, line printer, electronic capture and display or other

text: 2009-11-01 2-C-21 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 1 to JAR-FSTD A.030 (continued) appropriate recording media acceptable to the Authority conducting the test. FSTD results should be labelled using terminology common to aeroplane parameters as opposed to computer software identifications. These results should be easily compared with the supporting data by employing cross plotting or other acceptable means. Aeroplane data documents included in the QTG may be photographically reduced only if such reduction will not alter the graphic scaling or cause difficulties in scale interpretation or resolution. Incremental scales on graphical presentations should provide resolution necessary for evaluation of the parameters shown in paragraph 2. The test guide will provide the documented proof of compliance with the FSTD validation tests in the tables in paragraph 2. For tests involving time histories, flight test data sheets, FSTD test results should be clearly marked with appropriate reference points to ensure an accurate comparison between the FSTD and aeroplane with respect to time. FSTD operators using line printers to record time histories should clearly mark that information taken from line printer data output for cross plotting on the aeroplane data. The cross plotting of the FSTD operator’s FSTD data to aeroplane data is essential to verify FSTD performance in each test. The evaluation serves to validate the FSTD operator’s FSTD test results. j. A copy of the version of the primary reference document as agreed with the Authority and used in the initial evaluation should be included.

text: 1.7 Configuration control. A configuration control system should be established and maintained to ensure the continued integrity of the hardware and software as originally qualified. 1.8 Procedures for initial FSTD qualification 1.8.1 The request for evaluation should reference the QTG and also include a statement that the FSTD operator has thoroughly tested the FSTD and that it meets the criteria described in this document except as noted in the application form. The FSTD operator – for a BITD the manufacturer - should further certify that all the QTG checks, for the requested Qualification Level, have been achieved and that the FSTD is representative of the respective aeroplane or, for FNPTs and BITDs representative of the respective class of aeroplane. 1.8.2 A copy of the FSTD operator’s or BITD manufacturer's QTG, marked with test results, should accompany the request. Any QTG deficiencies raised by the Authority should be addressed prior to the start of the on-site evaluation.

text: 1.8.3 The FSTD operator may elect to accomplish the QTG validation tests while the FSTD is at the manufacturer’s facility. Tests at the manufacturer’s facility should be accomplished at the latest practical time prior to disassembly and shipment. The FSTD operator should then validate FSTD performance at the final location by repeating at least one-third of the validation tests in the QTG and submitting those tests to the Authority. After review of these tests, the Authority will schedule an initial evaluation. The QTG should be clearly annotated to indicate when and where each test was accomplished. This may not be applicable for BITDs that would normally undergo initial qualification at the manufacturer’s facility.

text: 1.9 FSTD recurrent qualification basis 1.9.1 Following satisfactory completion of the initial evaluation and qualification tests, a periodic check system should be established to ensure that FSTDs continue to maintain their initially qualified performance, functions and other characteristics. 1.9.2 The FSTD operator should run the complete QTG, which includes validation, functions & subjective tests, between each annual evaluation by the Authority. As a minimum, the QTG tests should be run progressively in at least four approximately equal 3 monthly blocks on an annual cycle. Each block of QTG tests should be chosen to provide coverage of the different types of validation, functions & subjective tests. Results shall be dated and retained in order to satisfy both the FSTD operator as well as the Authority that the FSTD standards are being maintained. It is not acceptable that the complete QTG is run just prior to the annual evaluation. 2 FSTD Validation Tests

text: 2.1 General 2.1.1 FSTD performance and system operation should be objectively evaluated by comparing the results of tests conducted in the FSTD with aeroplane data unless specifically noted otherwise. To facilitate the

text: JAR-FSTD A 2-C-22 2009-11-01

text: Bilaga 1

text: ACJ No. 1 to JAR-FSTD A.030 (continued) ACJ No. 1 to JAR-FSTD A.030 (continued)

text: validation of the FSTD, an appropriate recording device acceptable to the Authority should be used to record each validation test result. These recordings should then be compared to the approved validation data.

text: 2.1.2 Certain tests in this ACJ are not necessarily based upon validation data with specific tolerances. However, these tests are included here for completeness, and the required criteria should be fulfilled instead of meeting a specific tolerance. 2.1.3 The FSTD MQTG should describe clearly and distinctly ho90 w the FSTD will be set up and operated for each test. Use of a driver programme designed to accomplish the tests automatically is encouraged. Overall integrated testing of the FSTD should be accomplished to assure that the total FSTD system meets the prescribed standards. Historically, the tests provided in the QTG to support FSTD qualification have become increasingly fragmented. During the development of the ICAO Manual of Criteria for the Qualification of Flight Simulators, 1993 by an RAeS Working Group, the following text was inserted: “It is not the intent, nor is it acceptable, to test each Flight Simulator subsystem independently. Overall Integrated Testing of the Flight Simulator should be accomplished to assure that the total Flight Simulator system meets the prescribed standards.” This text was developed to ensure that the overall testing philosophy within a QTG fulfilled the original intent of validating the FSTD as a whole whether the testing was carried out automatically or manually. To ensure compliance with this intent, QTGs should contain explanatory material which clearly indicates how each test (or group of tests) is constructed and how the automatic test system is controlling the test e.g. which parameters are driven, free, locked and the use of closed and open loop drivers. A test procedure with explicit and detailed steps for completion of each test must also be provided. Such information should greatly assist with the review of a QTG that involves an understanding of how each test was constructed in addition to the checking of the actual results A manual test procedure with explicit and detailed steps for completion of each test should also be provided. 2.1.4 Submittals for approval of data other than flight test should include an explanation of validity with respect to available flight test information. Tests and tolerances in this paragraph should be included in the FSTD MQTG. For FFS devices representing aeroplanes certificated after January 2002 the MQTG should be supported by a Validation Data Roadmap (VDR) as described in Appendix 2 to ACJ No. 1 to JAR-FSTD A.030. Data providers are encouraged to supply a VDR for older aeroplanes. For FFS devices representing aeroplanes certificated prior to January 1992, an operator may, after reasonable attempts have failed to obtain suitable flight test data, indicate in the MQTG where flight test data are unavailable or unsuitable for a specific test. For such a test, alternative data should be submitted to the Authority for approval. 2.1.5 The table of FSTD Validation Tests in this ACJ indicates the required tests. Unless noted otherwise, FSTD tests should represent aeroplane performance and handling qualities at operating weights and centres of gravity (cg) positions typical of normal operation.

text: For FFS devices, if a test is supported by aeroplane data at one extreme weight or cg, another test supported by aeroplane data at mid-conditions or as close as possible to the other extreme should be included. Certain tests, which are relevant only at one extreme weight or cg condition, need not be repeated at the other extreme. Tests of handling qualities should include validation of augmentation devices. Although FTDs are not designed for the purpose of training and testing of flight handling skills, it will be necessary, particularly for FTD Level 2 to include tests which ensure stability and repeatability of the generic flight package. These tests are also indicated in the tables.

text: 2.1.6 For the testing of Computer Controlled Aeroplane (CCA) FSTDs, flight test data are required for both the normal (N) and non-normal (NN) control states, as applicable to the aeroplane simulated and, as indicated in the validation requirements of this paragraph. Tests in the non-normal state should always include the least augmented state. Tests for other levels of control state degradation may be required as detailed by the Authority at the time of definition of a set of specific aeroplane tests for FSTD data. Where applicable, flight test data should record:

text: 2009-11-01 2-C-23 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 1 to JAR-FSTD A.030 (continued)

text: ACJ No. 1 to JAR-FSTD A.030 (continued)

text: a. pilot controller deflections or electronically generated inputs including location of input; and b. flight control surface positions unless test results are not affected by, or are independent of, surface positions.

text: 2.1.7 The recording requirements of 2.1.6 a) and b) above apply to both normal and non-normal states. All tests in the table of validation tests require test results in the normal control state unless specifically noted otherwise in the comments section following the computer controlled aeroplane designation (CCA). However, if the test results are independent of control state, non-normal control data may be substituted. 2.1.8 Where non-normal control states are required, test data should be provided for one or more nonnormal control states including the least augmented state.

text: 2.1.9 Where normal, non-normal or other degraded control states are not applicable to the aeroplane being simulated, appropriate rationales should be included in the aeroplane manufacturer’s validation data roadmap (VDR), which is described in Appendix 2 to ACJ No. 1 to JAR-FSTD A.030. 2.2 Test requirements 2.2.1 The ground and flight tests required for qualification are listed in the table of FSTD Validation Tests. Computer generated FSTD test results should be provided for each test. The results should be produced on an appropriate recording device acceptable to the Authority. Time histories are required unless otherwise indicated in the table of validation tests. 2.2.2 Approved validation data that exhibit rapid variations of the measured parameters may require engineering judgement when making assessments of FSTD validity. Such judgement should not be limited to a single parameter. All relevant parameters related to a given manoeuvre or flight condition should be provided to allow overall interpretation. When it is difficult or impossible to match FSTD to aeroplane data or approved validation data throughout a time history, differences should be justified by providing a comparison of other related variables for the condition being assessed. 2.2.2.1 Parameters, tolerances, and flight conditions. The table of FSTD validation tests in paragraph 2.3 below describes the parameters, tolerances, and flight conditions for FSTD validation. When two tolerance values are given for a parameter, the less restrictive may be used unless indicated otherwise. Where tolerances are expressed as a percentage:  for parameters that have units of percent, or parameters normally displayed in the cockpit in units of percent (e.g. N1, N2, engine torque or power), then a percentage tolerance will be interpreted as an absolute tolerance unless otherwise specified (i.e. for an observation of 50% N1 and a tolerance of 5%, the acceptable range shall be from 45% to 55%).  for parameters not displayed in units of percent, a tolerance expressed only as a percentage will be interpreted as the percentage of the current reference value of that parameter during the test, except for parameters varying around a zero value for which a minimum absolute value should be agreed with the Authority If a flight condition or operating condition is shown which does not apply to the qualification level sought, it should be disregarded. FSTD results should be labelled using the tolerances and units specified. 2.2.2.2 Flight condition verification. When comparing the parameters listed to those of the aeroplane, sufficient data should also be provided to verify the correct flight condition. For example, to show the control force is within ± 2.2 daN (5 pounds) in a static stability test, data to show correct airspeed, power, thrust or torque, aeroplane configuration, altitude, and other appropriate datum identification parameters should also be given. If comparing short period dynamics on a FSTD, normal acceleration may be used to establish a match to the aeroplane, but airspeed, altitude, control input, aeroplane configuration, and

text: other appropriate data should also be given. All airspeed values should be assumed to be calibrated unless annotated otherwise and like values used for comparison. 2.2.2.3 Where the tolerances have been replaced by ‘Correct Trend and Magnitude’ (CT&M), the FSTD should be tested and assessed as representative of the aeroplane or class of aeroplane to the satisfaction of

text: JAR-FSTD A 2-C-24 2009-11-01

text: Bilaga 1

text: the Authority. To facilitate future evaluations, sufficient parameters should be recorded to establish a reference. For the initial qualification of FNPTs and BITDs no tolerances are to be applied and the use of CT&M is to be assumed throughout. 2.2.2.4 Flight conditions. The flight conditions are specified as follows: a. Ground-on ground, independent of aeroplane configuration b. Take-off - gear down with flaps in any certified takeoff position c. Second segment climb – gear up with flaps in any certified take off position d. Clean – flaps and gear up e. Cruise – clean configuration at cruise altitude and airspeed f. Approach – gear up or down with flaps at any normal approach positions as recommended by the aeroplane manufacturer g. Landing – gear down with flaps in any certified landing position.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-25 JAR-FSTD A

text: SECTION 2

text: Bilaga 1

text: INTENTIONALLY LEFT BLANK JAR-FSTD A 2-C-26 2009-11-01

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: 2.3 Table of FSTD Validation Tests o J A R-FS

text: 2.3.1 A number of tests within the QTG have had their requirements reduced to ‘Correct Trend and Magnitude’ (CT&M) for initial evaluations thereby avoiding the need for specific Flight Test Data. Where CT&M is used it is strongly recommended that an automatic recording system be used to ‘footprint’ the baseline results TD A. thereby avoiding the effects of possible divergent subjective opinions on recurrent evaluation. 0

text: 30 (c However, the use of CT&M is not to be taken as an indication that certain areas of simulation can be ignored. It is imperative that the specific characteristics are present, and incorrect effects would be unacceptable. o ntinued

text: 2.3.2 In all cases the tests are intended for use in recurrent evaluations at least to ensure repeatability. )

text: FLIGHT TESTS TOLERANCE FSTD LEVEL COMMENTS CONDITIONS

text: -C FS FTD FNPT BITD

text: A B C D Init. Rec I II MCC Init. Rec

text: It is accepted that tests and associated tolerances will only apply to a Level 1 FTD if that system or flight condition is simulated.

text: 1. PERFORMANCE

text: a. TAXY

text: (1) Minimum ± 0.9 m (3 ft) or ± 20% Ground Plot both main and nose gear-turning loci. Radius Turn. of aeroplane turn C Data for no brakes and the minimum thrust radius. T 9 9 9 required to maintain a steady turn except for

text: aeroplanes requiring asymmetric thrust or

text: M

text: braking to turn.

text: JAR- C

text: (2) Rate of Turn vs. ± 10% or Ground Tests for a minimum of two speeds, greater Nosewheel T 9 9 9 ± 2º/s turn rate. than minimum turning radius speed, with a FSTD Steering Angle & spread of at least 5 kts groundspeed. (NWA). M b. TAKE-OFF Note-All commonly used take-off flap

text: A

text: settings should be demonstrated at least TS once either in minimum unstick speed (1b3),

text: FS

text: normal take-off (1b4), critical engine failure

text: Bi 2

text: on take-off (1b5) or cross wind take-off (1b6). la 0

text: ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: FLIGHT 09:87

text: TESTS TOLERANCE FSTD LEVEL COMMENTS

text: A CONDITIONS

text: o J A

text: FS FTD FNPT BITD R-

text: FS

text: A B C D Init. Rec I II MCC Init. Rec TD A. (1) Ground ± 5% or ±1.5 s time Take-off C Acceleration time and distance should be and T C 0 Acceleration 9 9 9 9 recorded for a minimum of 80% of the total ± 5% or & 30 (c Time and T time from brake release to V . R

text: M &

text: Distance. ± 61 m (200 ft) on

text: M

text: distance tinued

text: May be combined with normal takeoff (1b4) or rejected takeoff (1b7). Plotted data ) should be shown using appropriate scales for each portion of the manoeuvre.

text: C For FTD's test limited to time only

text: -2 8

text: (2) Minimum ± 25% of maximum Take-off C Engine failure speed should be within Control Speed, T 9 9 9 aeroplane lateral ± 1 kt of aeroplane engine failure speed. ground (VMCG) & deviation or Engine thrust decay should be that resulting aerodynamic M ± 1.5 m (5 ft) from the mathematical model for the engine controls only per variant applicable to the flight simulator applicable For aeroplanes with under test. If the modelled engine variant is airworthiness reversible flight not the same as the aeroplane requirement or control systems: manufacturers’ flight test engine, then a alternative further test may be run with the same initial ± 10% or ± 2·2 daN (5 engine conditions using the thrust from the flight test lb) rudder pedal force inoperative test data as the driving parameter. If a VMCG test to demonstrate is not available an acceptable alternative is a ground control flight test snap engine deceleration to idle at characteristics. a speed between V1 and V1-10 kts, followed 200 by control of heading using aerodynamic

text: control only and recovery should be

text: 11 achieved with the main gear on the ground. To ensure only aerodynamic control, SEC

text: nosewheel steering should be disabled (i.e., castored) or the nosewheel held slightly off T the ground. ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FLIGHT

text: TESTS TOLERANCE FSTD LEVEL COMMENTS o J CONDITIONS A

text: R-FS

text: FS FTD FNPT BITD

text: TD A.

text: A B C D Init. Rec I II MCC Init. Rec

text: (3) Minimum ± 3 kts airspeed Take-off VMU is defined as the minimum speed at 0 ± 1.5º pitch angle C 30 (c Unstick Speed 9 9 9 which the last main landing gear leaves the

text: T

text: (VMU) or ground. Main landing gear strut compression o

text: equivalent test or equivalent air/ground signal should be

text: M ntinued

text: to demonstrate recorded. early rotation If a VMU test is not available, alternative ) take off acceptable flight tests are a constant highcharacteristics. attitude take-off run through main gear liftoff, or an early rotation take-off. Record time history data from 10 kts before start of

text: -C

text: rotation until at least 5 seconds after the

text: occurrence of main gear lift-off.

text: (4) Normal Take-off. ± 3 kts airspeed Take-off Data required for near maximum certificated

text: C 9 9 9

text: ± 1.5º pitch angle take-off weight at mid centre of gravity and

text: T

text: ± 1.5º AOA light take-off weight at an aft centre of gravity.

text: ± 6 m (20 ft) height M If the aeroplane has more than one For aeroplanes with certificated take-off configuration, a different reversible flight configuration should be used for each weight. control systems: Record take-off profile from brake release to at least 61 m (200 ft) AGL. ± 10% or ± 2·2 daN (5 lb) column force May be used for ground acceleration time and distance (1b1).

text: JAR-

text: Plotted data should be shown using FSTD appropriate scales for each portion of the manoeuvre.

text: A TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: FLIGHT 09:87

text: TESTS TOLERANCE FSTD LEVEL COMMENTS

text: A CONDITIONS

text: o J A

text: FS FTD FNPT BITD R-

text: FS

text: A B C D Init. Rec I II MCC Init. Rec TD A.

text: (5) Critical Engine ± 3 kts airspeed Take-off Record take-off profile to at least 61 m (200 ± 1.5º pitch angle C 9 9 9 0 Failure on Take- ft) AGL. Engine failure speed should be 30 (c

text: T

text: off. ± 1.5º AOA within ± 3 kts of aeroplane data. Test

text: ± 6 m (20 ft) height at near maximum take-off weight. on

text: M

text: ± 2º bank and sideslip

text: tinued

text: angle

text: ± 3° heading angle )

text: For aeroplanes with 2- reversible flight

text: C

text: control systems:

text: -3 0

text: ± 10% or ± 2·2 daN (5 lb) column force

text: ± 10% or ± 1·3 daN (3 lb) wheel force

text: ± 10% or ± 2·2 daN (5 lb) rudder pedal force.

text: 9- 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FLIGHT

text: R-FS

text: FS FTD FNPT BITD

text: TD A.

text: A B C D Init. Rec I II MCC Init. Rec

text: (6) Crosswind Take- ± 3 kts airspeed Take-off Record take-off profile from brake release to 0

text: C 30 (c

text: off. ± 1.5º pitch angle 9 9 9 at least 61 m (200 ft) AGL.

text: T

text: ± 1.5º AOA Requires test data, o

text: ± 6 m (20 ft) height including wind profile,

text: M ntinued

text: ± 2º bank and sideslip for a crosswind component of at least 60% of angle the AFM value measured at 10m (33 ft)

text: above the runway. ± 3° heading

text: -C Correct trends at -31 airspeeds below 40 kts for rudder/pedal and heading.

text: For aeroplanes with reversible flight control systems:

text: ± 10% or ± 2·2 daN (5 lb) column force

text: ± 10% or ± 1·3 daN (3 lb) wheel force

text: ± 10% or ± 2·2 daN (5 JAR- lb) rudder pedal force

text: (7) Rejected Take- ± 5% time or Take-off Record near maximum take-off weight. Speed

text: FSTD C 9 9 9

text: off. ± 1.5 s for reject should be at least 80% of V1.

text: T

text: ± 7.5% distance or Autobrakes will be used where applicable.

text: A ± 76 m (250 ft) Maximum braking effort, auto or manual.

text: M

text: Time and distance should be recorded from TS brake release to a full stop. FS

text: Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: FLIGHT 09:87

text: TESTS TOLERANCE FSTD LEVEL COMMENTS

text: A CONDITIONS

text: o J A

text: FS FTD FNPT BITD R-

text: FS

text: (8) Dynamic Engine ± 20% or ± 2º/s body Take-off Engine failure speed should be within ± 3 kts

text: C 9 9 9 0

text: Failure after angular rates of aeroplane data. Engine failure may be a 30 (c

text: T

text: Take-off. snap deceleration to idle. Record hands off

text: from 5 secs before engine failure to + 5 secs on

text: M

text: or 30 deg bank, whichever occurs first.

text: tinued

text: Note: for safety considerations, aeroplane flight test may be performed out of ground )

text: effect at a safe altitude, but with correct aeroplane configuration and airspeed.

text: C CCA: Test in normal AND Non-normal

text: 2 Control state.

text: c. CLIMB

text: (1) Normal Climb ± 3 kts airspeed Clean Flight test data or aeroplane performance All Engines ± 5% or or specified 9 9 9 9 9 9 9 9 9 9 9 manual data may be used. Record at nominal Operating ± 0·5 m/s climb climb speed and mid initial climb altitude.

text: (100 ft/min) R/C configuration FSTD performance to be recorded over an

text: interval of at least 300 m (1 000 ft).

text: For FTD's may be a Snapshot test

text: 9- 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FLIGHT

text: TESTS TOLERANCE FSTD LEVEL COMMENTS o J

text: CONDITIONS A

text: R-FS

text: FS FTD FNPT BITD

text: TD A.

text: A B C D Init. Rec I II MCC Init. Rec

text: (2) One Engine ± 3 kts airspeed 2nd Segment Flight test data or aeroplane performance 0

text: C C 30 (c

text: Inoperative ± 5% or ± 0.5 m/s Climb 9 9 9 9 9 9 9 9 manual data may be used. Record at

text: T T

text: Second (100 ft/min) R/C but nominal climb speed. Flight simulator o

text: Segment Climb. not less than AFM for FNPTs and performance to be recorded over an interval

text: M M ntinued

text: values. BITDs Gear up of at least 300m (1 000 ft). and Take-off Test at WAT (Weight, Altitude, or ) Flaps Temperature) limiting condition.

text: -C For FTD's may be a Snapshot test

text: (3) One Engine ± 10% time Clean Flight test data or aeroplane performance

text: 9 9 9 9 C 9

text: Inoperative En ± 10% distance manual data may be used.

text: T

text: route ± 10% fuel used

text: Climb. M Test for at least a 1 550 m (5 000 ft) segment.

text: (4) One Engine ± 3 kts airspeed Approach Flight test data or aeroplane performance Inoperative ± 5% or ± 0.5 m/s 9 9 manual data may be used. FSTD

text: Approach Climb (100 ft/min) R/C but performance to be recorded over an interval for aeroplanes not less than AFM of at least 300 m (1 000 ft). with icing values Test near maximum certificated landing JAR- accountability if weight as may be applicable to an approach

text: required by the in icing conditions. FSTD flight manual for Aeroplane should be configured with all antithis phase of ice and de-ice systems operating normally, flight. A gear up and go-around flap. All icing

text: accountability considerations, in accordance TS

text: with the flight manual for an approach in icing FS conditions, should be applied. Bi 2

text: la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: FLIGHT 09:87

text: TESTS TOLERANCE FSTD LEVEL COMMENTS

text: A CONDITIONS

text: o J A

text: FS FTD FNPT BITD R-

text: FS

text: d. CRUISE / DESCENT 0

text: 30 (c

text: (1) Level Flight ± 5% time Cruise Minimum of 50 kts increase using maximum

text: C on

text: Acceleration 9 9 9 9 9 continuous thrust rating or equivalent.

text: T tinued

text: & For very small aeroplanes, speed change may M be reduced to 80% of operational speed range. )

text: (2) Level Flight ± 5% time Cruise Minimum of 50 kts decrease using idle power.

text: C 9 9 9 9 9

text: Deceleration T For very small aeroplanes, speed change may 2- & be reduced to 80% of operational speed range. C M

text: 4 (3) Cruise ± 0.05 EPR or Cruise May be a single snapshot showing

text: Performance ± 5% N1 or ± 5% 9 9 9 9 9 9 instantaneous fuel flow, or a minimum of two

text: torque consecutive snapshots with a spread of at ± 5% fuel flow least 3 minutes in steady flight.

text: (4) Idle Descent ± 3 kts airspeed Clean Idle power stabilised descent at normal 9 9 9 9 descent speed at mid altitude. Flight ± 5% or ± 1·0 m/s simulator performance to be recorded over an (200 ft/min) R/D interval of at least 300 m (1 000 ft).

text: (5) Emergency ± 5 kts airspeed As per AFM Stabilised descent to be conducted with Descent 9 9 9 9 speedbrakes extended if applicable, at mid ± 5% or ± 1·5 m/s altitude and near VMO or according to (300 ft/min) R/D emergency descent procedure. Flight 200 simulator performance to be recorded over an interval of at least 900 m (3 000 ft).

text: 11 e. STOPPING

text: -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FLIGHT

text: R-FS

text: FS FTD FNPT BITD

text: TD A.

text: A B C D Init. Rec I II MCC Init. Rec

text: (1) Deceleration ± 5% or ±1.5 s time. Landing Time and Distance should be recorded for at 0

text: C 30 (c

text: Time and 9 9 9 least 80% of the total time from touchdown to

text: T

text: Distance, a full stop. Data required for medium and o For distances & Manual Wheel near maximum certificated landing weight. up to 1 220 m (4 000 M ntinued

text: Brakes, Dry Engineering data may be used for the ft) ± 61 m (200 ft) or Runway, medium weight condition. Brake system ± 10%, whichever is ) No Reverse pressure should be recorded. the smaller. Thrust.

text: For distances greater -C than 1 220 m (4 000 -35 ft) ± 5% distance.

text: (2) Deceleration ± 5% or ±1.5 s time Landing Time and distance should be recorded for at

text: C 9 9 9

text: Time and and the smaller of least 80% of the total time from initiation of

text: T

text: Distance, ± 10% or reverse thrust to full thrust reverser minimum

text: Reverse Thrust, ± 61 m (200 ft) of operating speed. Data required for medium

text: M

text: No Wheel distance. and near maximum certificated landing Brakes, Dry weights. Runway. Engineering data may be used for the medium weight condition.

text: (3) Stopping ± 10% or Landing Either flight test or manufacturers Distance, Wheel ± 61 m (200 ft) 9 9 performance manual data should be used

text: Brakes, Wet distance where available. Engineering data, based on Runway. dry runway flight test stopping distance and JAR- the effects of contaminated runway braking coefficients, are an acceptable alternative. FSTD (4) Stopping ± 10% or Landing Either flight test or manufacturer’s

text: Distance, Wheel ± 61 m (200 ft) 9 9 performance manual data should be used Brakes, lcy distance where available. Engineering data, based on

text: A

text: Runway. dry runway flight test stopping distance and TS the effects of contaminated runway braking FS coefficients, are an acceptable alternative. Bi

text: 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: FLIGHT 09:87

text: TESTS TOLERANCE FSTD LEVEL COMMENTS

text: A CONDITIONS

text: o J A

text: FS FTD FNPT BITD R-

text: FS

text: A B C D Init. Rec I II MCC Init. Rec TD A. f. ENGINES

text: (1) Acceleration ± 10% Ti or Approach or Ti = Total time from initial throttle movement 30 (c

text: C 9 9 9 9 9 9 9 9 9 9

text: Landing until a 10% response of a critical engine ± 0·25s T on parameter. ± 10% Tt &

text: tinued

text: M Tt = Total time from initial throttle movement to 90% of go around power. Critical engine ) parameter should be a measure of power (N1, N2, EPR, etc). Plot from flight idle to go around power for a rapid throttle movement.

text: C FTD, FNPT and BITD only: CT&M -3 acceptable.

text: (2) Deceleration ± 10% TI or Ground Ti = Total time from initial throttle movement

text: C 9 9 9 9 9 9 9 9 9 9

text: until a 10% response of a critical engine ± 0·25s T parameter. ± 10% Tt & M Tt = Total time from initial throttle movement to 90% decay of maximum take-off power. Plot from maximum take-off power to idle for a rapid throttle movement.

text: FTD, FNPT and BITD only: CT&M acceptable.

text: 2. HANDLING QUALITIES

text: 9- 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FLIGHT

text: TESTS TOLERANCE FSTD LEVEL COMMENTS o J

text: CONDITIONS A

text: R-FS

text: FS FTD FNPT BITD

text: TD A.

text: A B C D Init. Rec I II MCC Init. Rec

text: a. STATIC CONTROL NOTE: Pitch, roll and yaw controller position 0

text: 30 (c

text: CHECKS vs. force or time shall be measured at the control. An alternative method would be to o instrument the FSTD in an equivalent manner

text: ntinued

text: to the flight test aeroplane. The force and position data from this instrumentation can be

text: directly recorded and matched to the aeroplane data. Such a permanent installation could be used without any time for installation of external devices.

text: -C

text: CCA: Testing of position versus force is not

text: applicable if forces are generated solely by use of aeroplane hardware in the FSTD.

text: (1) Pitch Controller ± 0.9 daN (2 lbs) Ground Uninterrupted control sweep to stops. Should

text: 9 9 9 9 C 9

text: Position vs. breakout. be validated (where possible) with inflight

text: T

text: Force and ± 2.2 daN (5 lbs) or data from tests such as longitudinal static

text: Surface Position ± 10% force. stability, stalls, etc.

text: M

text: Calibration. ± 2º elevator angle Static and dynamic flight control tests should be accomplished at the same feel or impact pressures.

text: Column Position ± 2.2 daN (5 lbs) Cruise or FNPT 1 and BITD: Control forces and travel

text: 9 9 9 C 9

text: vs. Force only. Approach shall broadly correspond to that of the or ± 10% Force. T replicated class of aeroplane.

text: JAR- &

text: M

text: FSTD (2) Roll Controller ± 0.9 daN (2 lbs) Ground Uninterrupted control sweep to stops. Should

text: 9 9 9 9 C 9

text: Position vs. breakout be validated with in-flight data from tests

text: T

text: Force and ± 1.3 daN (3 lbs) such as engine out trims, steady state

text: A Surface Position or ± 10% force sideslips, etc. Static and dynamic flight

text: M TS

text: Calibration. ± 2º aileron angle control tests should be accomplished at the ± 3º spoiler angle same feel or impact pressures. FS

text: Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: FLIGHT 09:87

text: TESTS TOLERANCE FSTD LEVEL COMMENTS

text: A CONDITIONS

text: o J A

text: FS FTD FNPT BITD R-

text: FS

text: ± 1.3 daN (3 lbs) Cruise or FNPT 1 and BITD: Control forces and travel

text: 9 9 9 C 9 0

text: Approach shall broadly correspond to that of the 30 (c Wheel Position or ± 10% Force T replicated class of aeroplane vs. Force only. &

text: M on

text: (3) Rudder Pedal ± 2.2 daN (5 lbs) Ground Uninterrupted control sweep to stops. Should tinued

text: Position vs. breakout 9 9 9 9 C 9 be validated with in flight data from tests such

text: Force and ± 2.2 daN (5 lbs) T as engine out trims, steady state sideslips,

text: Surface Position or ± 10% force & etc. Static and dynamic flight control tests

text: Calibration. ± 2º rudder angle M should be accomplished at the same feel or

text: 2- impact pressures. Pedal Position

text: C

text: vs. Force only. ± 2.2 daN (5 lbs) Cruise or FNPT 1 and BITD: Control forces and travel

text: -3 C

text: 8 Approach 9 9 9 9 shall broadly correspond to that of the or ± 10% Force. T replicated class of aeroplane

text: & M

text: (4) Nosewheel ± 0.9 daN (2 lbs) Ground Uninterrupted control sweep to stops.

text: C 9 9 9

text: Steering breakout

text: T

text: Controller Force ± 1.3 daN (3 lbs)

text: and Position or ± 10% force

text: M

text: Calibration. ± 2º NWA

text: (5) Rudder Pedal ± 2º NWA Ground Uninterrupted control sweep to stops.

text: C 9 9 9

text: Steering

text: T

text: Calibration.

text: & M

text: (6) Pitch Trim ± 0.5º trim angle. Ground Purpose of test is to compare flight simulator 200 Indicator vs. 9 9 9 9 against design data or equivalent.

text: 9- Surface Position C ±1° of trim angle Ground BITD: Only applicable if appropriate trim 11 Calibration T 9 9 9 9 9 9 settings are available, e.g. data from the

text: -01 & SEC

text: AFM.

text: M

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FLIGHT

text: TESTS TOLERANCE FSTD LEVEL COMMENTS o J

text: CONDITIONS A

text: R-FS

text: FS FTD FNPT BITD

text: TD A.

text: A B C D Init. Rec I II MCC Init. Rec

text: (7) Pitch Trim Rate ± 10% or ± 0.5 deg/s Ground and Trim rate to be checked at pilot primary 0

text: 30 (c

text: trim rate (°/s) approach 9 9 9 9 9 9 induced trim rate (ground) and autopilot or

text: pilot primary trim rate in flight at go-around o flight conditions.

text: ntinued

text: (8) Alignment of ± 5º of TLA Ground Simultaneous recording for all engines. The Cockpit Throttle 9 9 9 9 9 9 9 9 9 9 9 tolerances apply against aeroplane data and ) or ± 3% N1 Lever vs. between engines. Selected Engine or ± 0·03 EPR For aeroplanes with throttle detents, all Parameter. or ± 3% torque detents to be presented.

text: -C

text: -39 For propeller-driven

text: aeroplanes, where the In the case of propeller-driven aeroplanes, if propeller levers do not an additional lever, usually referred to as the have angular travel, a propeller lever, is present, it should also be tolerance of ± 2 cm (± checked. 0.8 in) applies. Where these levers do not have angular travel a tolerance of ± 2 cm (± 0.8 inches) applies.

text: May be a series of Snapshot tests.

text: (9) Brake Pedal ± 2.2 daN (5 lbs) or Ground Flight simulator computer output results may

text: C 9 9 9

text: Position vs. be used to show compliance. JAR- ± 10% force. T Force and Brake & Relate the hydraulic system pressure to pedal System ± 1.0 MPa (150 psi) or M FSTD position in a ground static test. Pressure ± 10% brake system Calibration. pressure.

text: A TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S J No F

text: ga S

text: FSTD 20

text: . 1 t

text: A o J A R- FS FLIGHT TD A.

text: TESTS TOLERANCE FSTD LEVEL

text: CONDITIONS COMMENTS 0 30 (c FS FTD FNPT BITD on Rec Rec A B C D Init. I II MCC Init. tinued . . b DYNAMIC Tests 2b1, 2b2, and 2b3 are not applicable if ) . CONTROL dynamic response is generated solely by use CHECKS of aeroplane hardware in the flight simulator. Power setting may be that required for level 2- flight unless otherwise specified. C -4 0

text: 9- 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FLIGHT o J TESTS TOLERANCE FSTD LEVEL A CONDITIONS COMMENTS R-FS

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (1) Pitch Control. For underdamped Take-off, Data should be for normal control

text: o

text: systems: Cruise, and 9 9 displacements in both directions Landing (approximately 25% to 50% full throw or ntinued

text: ± 10% of time from approximately 25% to 50% of maximum 90% of initial ) allowable pitch controller deflection for flight displacement (Ad) to conditions limited by the manoeuvring load first zero crossing and envelope). Tolerances apply against the ± 10(n+1)% of period absolute values of each period (considered thereafter -C independently). -41 n = The sequential period of a full oscillation.

text: ± 10% amplitude of first overshoot applied Refer to paragraph 2.4.1 to all overshoots greater than 5% of initial displacement (Ad).

text: ± 1 overshoot (first significant overshoot should be matched)

text: For overdamped systems:

text: JAR- ± 10% of time from 90% of initial FSTD displacement (Ad) to 10 % of initial displacement (0·1 Ad).

text: A TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: 09:87 A

text: FLIGHT o J TESTS TOLERANCE FSTD LEVEL A CONDITIONS COMMENTS R-

text: FS

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (2) Roll Control. For underdamped Take-off, Data should be for normal control on systems: Cruise, and 9 9 displacement (approximately 25% to 50% of

text: tinued

text: Landing full throw or approximately 25% to 50% of ± 10% of time from maximum allowable roll controller deflection 90% of initial ) for flight conditions limited by the displacement (Ad) to manoeuvring load envelope). first zero crossing and ± 10(n+1)% of period Refer to paragraph 2.4.1

text: thereafter.

text: C -4 2

text: ± 10% amplitude of first overshoot applied to all overshoots greater than 5% of initial displacement (Ad).

text: For overdamped systems:

text: 200 ± 10% of time from 90% of initial 9- displacement (Ad) to 11 10 % of initial

text: -01 SEC

text: displacement (0·1 Ad).

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (3) Yaw Control. For underdamped Take-off, Data should be for normal displacement

text: o

text: systems: Cruise, and 9 9 (Approximately 25% to 50% of full throw). Landing ntinued

text: ± 10% of time from Refer to paragraph 2.4.1 90% of initial ) displacement (Ad) to first zero crossing and ± 10(n+1)% of period thereafter.

text: -C -43

text: For overdamped systems: JAR- ± 10% of time from 90% of initial FSTD displacement (Ad) to 10 % of initial displacement (0·1 Ad).

text: A TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: FLIGHT 09:87 A TESTS TOLERANCE FSTD LEVEL CONDITIONS COMMENTS o J

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: Rec Rec A B C D Init. I II MCC Init. . .

text: 30 (c

text: (4) Small Control ± 0·15 °/s body pitch Approach or Control inputs should be typical of minor Inputs - pitch. rate or Landing 9 9 corrections made while established on an

text: on

text: ILS approach (approximately 0·5 to 2 °/s ± 20% of peak body tinued pitch rate). Test in both directions. Show pitch rate applied time history data from 5 seconds before until throughout the time ) at least 5 seconds after initiation of control history. input.

text: CCA: Test in normal AND non-normal control 2- state.

text: C

text: -4 (5) Small Control ± 0·15 °/s body roll Approach or Control inputs should be typical of minor

text: Inputs - roll rate or ± 20% of peak Landing 9 9 corrections made while established on an

text: body roll rate applied ILS approach (approximately 0·5 to 2 °/s roll

text: throughout the time rate). Test in one direction. For aeroplanes history that exhibit non-symmetrical behaviour, test in both directions. Show time history data from 5 seconds before until at least 5 seconds after initiation of control input.

text: CCA: Test in normal AND non-normal control state.

text: 9- 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FLIGHT o J

text: TESTS TOLERANCE FSTD LEVEL A CONDITIONS COMMENTS R-FS

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (6) Small Control ± 0·15 °/s body yaw Approach or Control inputs should be typical of minor

text: o

text: Inputs – yaw rate or Landing 9 9 corrections made while established on an ILS approach (approximately 0·5 to 2 °/s yaw ntinued

text: ± 20% of peak body rate). Test in one direction. For aeroplanes yaw rate applied ) that exhibit non-symmetrical behaviour, test throughout the time in both directions. Show time history data history from 5 seconds before until at least 5 seconds after initiation of control input.

text: -C -45

text: JAR-

text: FSTD

text: A TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: 09:87 A

text: FLIGHT o J

text: TESTS TOLERANCE FSTD LEVEL A CONDITIONS COMMENTS R-

text: FS

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: c LONGITUDINAL Power setting may be that required for level

text: on

text: . flight unless otherwise specified.

text: tinued

text: (1) Power Change ± 3 kts airspeed Approach Power change from thrust for approach or 9 9 9 9 C 9 9 9 ) Dynamics. ± 30 m (100 ft) level flight to maximum continuous or go-

text: T

text: altitude. around power. Time history of uncontrolled

text: ± 1.5º or ± 20% pitch M free response for a time increment equal to

text: angle at least 5 secs before initiation of the power

text: change to completion of the power change

text: C

text: -4 + 15 secs.

text: CCA: Test in Normal AND Non-normal

text: Control state.

text: Power Change Force ± 2.2 daN (5 lbs) Approach For an FNPT I and a BITD the power change 9 9 9 C 9 force test only is acceptable. or ± 10% Force T

text: & M

text: (2) Flap Change ± 3 kts airspeed Take-off Time history of uncontrolled free response 9 9 9 9 C 9 9 9 Dynamics. ± 30 m (100 ft) through initial for a time increment equal to at least 5 secs

text: T

text: altitude. flap retraction before initiation of the reconfiguration

text: ± 1.5º or ± 20% pitch and approach change to completion of the reconfiguration

text: M

text: angle to landing change + 15 secs.

text: CCA: Test in Normal AND Non-normal

text: 9- Control state.

text: Flap Change Force ± 2.2 daN (5 lbs) For an FNPT I and a BITD the flap change SEC

text: -01 C

text: 9 9 9 9 force test only is acceptable. or ± 10% Force T

text: & T

text: ION

text: M

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FLIGHT o J

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (3) Spoiler / ± 3 kts airspeed Cruise Time history of uncontrolled free response C o Speedbrake ± 30 m (100 ft) 9 9 9 9 9 9 9 for a time increment equal to at least 5 secs

text: T ntinued

text: Change altitude. before initiation of the reconfiguration

text: Dynamics. ± 1.5 º or ± 20% pitch change to completion of the reconfiguration

text: M )

text: angle change + 15 secs.

text: Results required for both extension and

text: retraction.

text: -C CCA: Test in Normal AND Non-normal

text: -47 Control state.

text: (4) Gear Change ± 3 kts airspeed Takeoff Time history of uncontrolled free response 9 9 9 9 C 9 9 9 Dynamics. ± 30 m (100 ft) (retraction) for a time increment equal to at least 5 secs

text: T

text: altitude. and Approach before initiation of the configuration change

text: ± 1.5º or ± 20% pitch (extension) to completion of the reconfiguration change

text: M

text: angle + 15 secs.

text: For FNPTs and CCA: Test in Normal AND Non-normal

text: BITDs, ± 2º or ± 20% Control state.

text: pitch angle

text: Gear Change Force ± 2.2 daN (5 lbs) Take-off and For an FNPT I and a BITD the gear change 9 9 9 C 9 Approach force test only is acceptable. or ± 20% Force. T

text: JAR-

text: M

text: FSTD (5) Longitudinal Trim. ± 1º elevator Cruise, Steady-state wings level trim with thrust for 9 9 9 9 C 9 Approach and level flight. May be a series of snapshot ± 0·5º stabilizer T Landing tests.

text: A ± 1º pitch angle

text: M CCA: Test in Normal OR Non-normal Control TS

text: ± 5% net thrust or state. FS

text: equivalent Bi

text: 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 30 (c

text: ± 2 deg Pitch Control Cruise, May be a series of Snapshot tests.

text: 9 9 9 C 9

text: (Elevator & Stabilizer) Approach T FNPT I and BITD may use equivalent stick and on ± 2 deg Pitch & trim controllers. tinued

text: M

text: ± 5% Power or

text: Equivalent

text: (6) Longitudinal ± 2.2 daN (5 lbs) or Cruise, Continuous time history data or a series of

text: 9 9 9 9 9 9 C 9

text: Manoeuvring ± 10% pitch controller Approach and snapshot tests may be used. Test up to

text: 2- T

text: Stability (Stick force Landing approximately 30º of bank for approach and C & -4 Force/g). M landing configurations. 8 Alternative method:

text: Test up to approximately 45º of bank for the ± 1º or ± 10% change cruise configuration. Force tolerance not of elevator applicable if forces are generated solely by

text: the use of aeroplane hardware in the FSTD.. Alternative method applies to aeroplanes

text: which do not exhibit stick-force-per-g

text: characteristics.

text: CCA: Test in Normal AND Non-normal

text: Control state as applicable.

text: (7) Longitudinal Static ± 2.2 daN (5 lbs) or Approach Data for at least two speeds above and two

text: 9 9 9 9 C 9 9 C 9

text: Stability. ± 10% pitch controller speeds below trim speed.

text: T T

text: force. & & May be a series of snapshot tests. Alternative method: M M 200 Force tolerance not applicable if forces are

text: 9- ± 1° or ± 10% change generated solely by the use of aeroplane

text: 11 of elevator hardware in the FSTD. Alternative method -01 applies to aeroplanes which do not exhibit SEC

text: speed stability characteristics.

text: T

text: CCA: Test in Normal OR Non-normal Control ION

text: state as applicable.

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (8) Stall ± 3 kts airspeed for 2nd Segment Wings-level (1 g) stall entry with thrust at or

text: o

text: Characteristics. initial buffet, stall Climb and 9 9 9 9 9 9 9 9 9 9 9 near idle power. Time history data should be warning, and stall Approach or shown to include full stall and initiation of ntinued

text: speeds. Landing recovery. Stall warning signal should be recorded and should occur in the proper )

text: relation to stall. FSTDs for aeroplanes For aeroplanes with exhibiting a sudden pitch attitude change or reversible flight ‘g break’ should demonstrate this -C control systems (for characteristic. -49 FS only): CCA: Test in Normal AND Non-normal ± 10% or ± 2·2 daN (5 Control state. lb) column force (prior FNPT and BITD: Test need only determine to g-break only.) the actuation of the stall warning device only.

text: (9) Phugoid ± 10% period. Cruise Test should include 3 full cycles or that Dynamics. 9 9 9 9 9 9 necessary to determine time to ½ or double ± 10% time to ½ or amplitude, whichever is less. double amplitude CCA: Test in Non-normal Control state. or ± 0.02 of damping ratio.

text: ± 10% Period with Cruise C Test should include at least 3 full cycles.

text: 9 T 9

text: representative JAR- & Time history recommended. damping

text: M

text: FSTD (10) Short Period ± 1.5º pitch angle or Cruise CCA: Test in Normal AND Non-normal

text: Dynamics. ± 2º/s pitch rate. 9 9 9 9 9 9 Control state. ± 0.1 g normal

text: A

text: acceleration. TS

text: FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: d LATERAL 30 (c Power setting may be that required for level . flight unless otherwise specified. DIRECTIONAL on

text: tinued

text: (1) Minimum Control ± 3 kts airspeed Take-off or Minimum speed may be defined by a )

text: C 9 9 9 C 9 C C C C C Speed, Air (VMCA Landing performance or control limit which prevents

text: T T T T T T T

text: or VMCL), per (whichever is demonstration of VMC or VMCL in the

text: Applicable most critical in M M M M M M M conventional manner. Take-off thrust should

text: C Airworthiness the aeroplane) be set on the operating engine(s). Time -5 Standard – or – history or snapshot data may be used 0 Low Speed CCA: Test in Normal OR Non-normal Control Engine Inoperstate. ative Handling

text: Characteristics in FNPT and BITD: It is important that there exists a

text: the Air. realistic speed relationship between Vmca and Vs

text: for all configurations and in particular the most

text: critical full-power engine-out take-off

text: configurations.

text: (2) Roll Response ± 10% or Cruise and Test with normal roll control displacement

text: 9 9 9 9 C 9 9 9 9 C 9

text: (Rate). ± 2º/sec roll rate Approach or (about 30% of maximum control wheel). May

text: T T

text: Landing be combined with step input of flight deck roll FS only: For & & M M controller test (2d3). aeroplanes with

text: reversible flight 9- control systems: 11 ± 10% or ± 1·3 daN (3 -01 lb) roll controller force. SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FLIGHT o J

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (3) Step Input of ± 10% or Approach or With wings level, apply a step roll control

text: o

text: Cockpit Roll ± 2º bank angle Landing 9 9 9 9 9 9 input using approximately one-third of roll Controller (or Roll controller travel. At approximately 20° to 30° ntinued

text: Overshoot). bank, abruptly return the roll controller to neutral and allow at least 10 seconds of )

text: aeroplane free response. May be combined

text: with roll response (rate) test (2d2).

text: CCA: Test in Normal AND Non-normal -C Control state.

text: (4) Spiral Stability. Correct trend and Cruise and Aeroplane data averaged from multiple tests

text: 9 9 9 9 C 9 C 9 9 C 9

text: ± 2º or Approach or may be used. Test for both directions. As an

text: T T T

text: ± 10% bank angle in Landing alternative test, show lateral control required

text: 20 seconds to maintain a steady turn with a bank angle

text: M M M

text: of approximately 30°. If alternate test is

text: used: correct trend and ± 2° aileron. CCA: Test in Non-normal Control state.

text: (5) Engine Inoperative ± 1º rudder angle or 2nd Segment Test should be performed in a manner similar

text: 9 9 9 9 C 9 9 9

text: Trim. Climb and to that for which a pilot is trained to trim an ± 1º tab angle or T Approach or engine failure condition. 2nd segment climb equivalent pedal. & Landing M test should be at take-off thrust. Approach or ± 2º sideslip angle. landing test should be at thrust for level flight. JAR- May be snapshot tests.

text: (6) Rudder Response. ± 2º/s or Approach or Test with stability augmentation ON and OFF.

text: FSTD

text: Landing 9 9 9 9 ± 10% yaw rate Test with a step input at approximately 25%

text: of full rudder pedal throw. A ± 2 deg/sec or

text: C 9 9 C 9 CCA: Test in Normal AND Non-normal TS ± 10% yaw rate or T T FS Control state. heading change & & Bi

text: M M

text: la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 30 (c

text: on

text: (7) Dutch Roll (Yaw ± 0.5 s or Cruise and Test for at least 6 cycles with stability tinued

text: C C C

text: Damper OFF). ± 10% of period. Approach or 9 9 9 9 augmentation OFF.

text: T T T

text: Landing ) ± 10% of time to ½or & & & CCA: Test in Non-normal Control state. double amplitude or M M M ± 0.02 of damping 2- ratio.

text: C

text: -5 ± 20% or 2 ± 1 s of time

text: difference between peaks of bank and sideslip

text: 9- 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (8) Steady State For a given rudder Approach or C C May be a series of snapshot tests using at T T o Sideslip. position: Landing 9 9 9 9 9 9 9 least two rudder positions (in each direction

text: & & ntinued

text: for propeller driven aeroplanes) one of which ± 2º bank angle M M should be near maximum allowable rudder. ± 1º sideslip angle ) ± 10% or For FNPT and BITD a roll controller position ± 2º aileron tolerance of ± 10% or ± 5º applies instead of ± 10% or the aileron tolerance. ± 5º spoiler or -C For a BITD the force tolerance shall be equivalent roll -53 CT&M. controller position or force

text: For FFSs representing aircraft with reversible flight control systems:

text: ±10% or ±1·3 daN (3 lb) wheel force

text: ±10% or ±2·2 daN (5 lb) rudder pedal force.

text: e LANDINGS

text: JAR-

text: FSTD

text: A TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 30 (c

text: (1) Normal Landing ± 3 kts airspeed Landing Test from a minimum of 61 m (200 ft) AGL to

text: C 9 9 9

text: nosewheel touch- down. ± 1.5º pitch angle T on & Two tests should be shown, including two

text: tinued

text: ± 1.5º AOA M normal landing flaps (if applicable) one of ± 3 m (10 ft) or which should be near maximum certificated ) ± 10% of height landing weight, the other at light or medium weight For aeroplanes with reversible flight CCA: Test in Normal AND Non-normal

text: C control systems: Control state if applicable.

text: 4 ± 10% or ± 2·2 daN (5

text: lb) column force

text: (2) Minimum Flap ± 3 kts airspeed Minimum Test from a minimum of 61 m (200 ft) AGL to Landing. Certified 9 9 9 nosewheel touchdown. ± 1.5º pitch angle Landing Flap Test at near maximum landing weight. ± 1.5º AOA Configuration

text: ± 3 m (10 ft) or ± 10% of height

text: ± 10% or ± 2·2 daN (5 200 lb) column force

text: 9- 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (3) Crosswind ± 3 kts airspeed Landing Test from a minimum of 61 m (200 ft) AGL to

text: o

text: Landing. 9 9 9 a 50% decrease in main landing gear ± 1.5º pitch angle ntinued touchdown speed. ± 1.5º AOA Requires test data, including wind profile, for ) ± 3 m (10 ft) or a crosswind component of at least ± 10% height 60% of AFM value measured at 10m (33 ft) above the runway. ± 2º bank angle

text: -C

text: ± 2º sideslip angle

text: ± 3° heading angle

text: ± 10% or ± 2·2 daN (5 lb) column force

text: ± 10% or ± 1·3 daN (3 lb) wheel force

text: JAR-

text: FSTD

text: A TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 30 (c

text: (4) One Engine ± 3 kts airspeed Landing Test from a minimum of 61 m (200 ft) AGL to Inoperative 9 9 9 a 50% decrease in main landing gear ± 1.5º pitch angle on Landing. touchdown speed.

text: tinued

text: ± 1.5º AOA

text: ± 3 m (10 ft) or )

text: ± 10% height

text: ± 2º bank angle

text: C ± 2º sideslip angle

text: 6 ± 3° heading angle

text: (5) Autopilot Landing ± 1.5 m (5 ft) flare Landing If autopilot provides rollout guidance, record (if applicable). height. 9 9 9 lateral deviation from touchdown to a 50%

text: ± 0.5 s or ± 10%Tf. decrease in main landing gear touchdown speed. Time of autopilot flare mode engage ± 0.7 m/s (140 ft/min) and main gear touchdown should be noted. R/D This test is not a substitute for the ground at touchdown. effects test requirement. ± 3 m (10 ft) lateral deviation during Tf = Duration of Flare. rollout.

text: (6) All engine ± 3 kts airspeed As per AFM Normal all engine autopilot go around should autopilot Go 9 9 9 be demonstrated (if applicable) at medium ± 1.5° pitch angle 200 Around. weight.

text: ± 1.5° AOA 9- CCA: Test in Normal AND Non-normal

text: 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (7) One-Engine- ± 3 kts airspeed As per AFM Engine inoperative go-around required near

text: o

text: inoperative Go- 9 9 9 maximum certificated landing weight with ±1·5° pitch angle ntinued around critical engine(s) inoperative. Provide one ±1·5° AOA test with autopilot (if applicable) and one without autopilot. ) ± 2° bank angle

text: ± 2° sideslip angle CCA: Non-autopilot test to be conducted in -C Non-normal mode.

text: (8) Directional ± 5 kts airspeed Landing Apply rudder pedal input in both directions Control (Rudder 9 9 9 using full reverse thrust until reaching full ± 2°/s yaw rate Effectiveness) thrust reverser minimum operating speed. with Reverse Thrust symmetric).

text: (9) Directional ± 5 kts airspeed Landing With full reverse thrust on the operating Control (Rudder 9 9 9 engine(s), maintain heading with rudder ± 3° heading angle Effectiveness) pedal input until maximum rudder pedal input with Reverser or thrust reverser minimum operating speed Thrust is reached. (asymmetric)

text: JAR-

text: FSTD f GROUND EFFECT .

text: A TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 30 (c

text: (1) A Test to ± 1º elevator Landing See Paragraph 2.4.2. A rationale should be demonstrate 9 9 9 provided with justification of results. ± 0·5º stabilizer angle. on Ground Effect.

text: tinued

text: ± 5% net thrust or

text: equivalent. CCA: Test in Normal OR Non-normal control

text: ± 1º AOA state.

text: ± 1.5 m (5 ft) or

text: ± 10% height

text: ± 3 kts airspeed

text: C

text: -5 ± 1º pitch angle

text: 9- 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: o J

text: FLIGHT A TESTS TOLERANCE FSTD LEVEL R-FS CONDITIONS COMMENTS

text: TD A.

text: FS FTD FNPT BITD

text: Rec Rec 30 (c A B C D Init. I II MCC Init. . .

text: o

text: g WIND SHEAR

text: . ntinued

text: (1) Four Tests, two None Take-off and Wind shear models are required which ) take-off and two Landing 9 9 provide training in the specific skills required landing with one for recognition of wind shear phenomena and of each conducted execution of recovery manoeuvres. in still air and the -C other with Wind -59 Shear active to

text: demonstrate Wind Shear models.

text: JAR-

text: FSTD

text: A TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 30 (c

text: Wind shear models should be representative of measured or accident derived winds, but may on be simplifications which ensure repeatable encounters. For example, models may consist tinued

text: of independent variable winds in multiple simultaneous components. Wind models ) should be available for the following critical phases of flight:

text: (1) Prior to take-off rotation

text: C (2) At lift-off

text: 0 (3) During initial climb

text: (4) Short final approach

text: The United States Federal Aviation Administration (FAA) Wind shear Training Aid, wind models from the Royal Aerospace Establishment (RAE), the United States Joint Aerodrome Weather studies (JAWS) Project or other recognised sources may be implemented and should be supported and properly referenced in the QTG. Wind models from alternate sources may also be used if supported by aeroplane related data and such data are properly supported and referenced in the QTG. Use of alternate data should be coordinated with the Authority prior to submittal of 200 the QTG for approval.

text: 9- 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c h FLIGHT AND This paragraph is only applicable to

text: . o

text: MANOEUVRE computer-controlled aeroplanes. Time

text: ntinued history results of response to control inputs

text: ENVELOPE

text: during entry into each envelope protection

text: PROTECTION )

text: function (i.e., with normal and degraded FUNCTIONS control states if function is different) are required. Set thrust as required to reach the envelope protection function.

text: -C

text: (1) Overspeed. ± 5 kts airspeed Cruise

text: -61 9 9 9 9 9 9

text: (2) Minimum Speed. ± 3 kts airspeed Take-off, Cruise and 9 9 9 9 9 9 Approach or Landing

text: (3) Load Factor. ± 0.1 g Take-off, Cruise 9 9 9 9 9 9

text: (4) Pitch Angle. ± 1.5º pitch angle Cruise, Approach 9 9 9 9 9 9

text: (5) Bank Angle. ± 2º or Approach ± 10% bank angle 9 9 9 9 9 9

text: (6) Angle of Attack. ± 1.5º AOA Second

text: JAR- 9 9 9 9 9 9

text: Segment Climb and FSTD Approach or

text: Landing A 3 MOTION SYSTEM

text: . TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 0 a 30 (c

text: Frequency response As specified by the Not Applicable Appropriate test to demonstrate frequency . applicant for flight 9 9 9 9 response required. See also ACJ No. 1 to

text: on

text: simulator JAR-FSTD A.030 para 2.4.3.2 qualification. tinued

text: b Leg Balance As specified by the Not Applicable Appropriate test to demonstrate leg balance ) . applicant for flight 9 9 9 9 required See also ACJ No. 1 to JAR-FSTD simulator A.030 para 2.4.3.2 qualification.

text: C c Turn-around check As specified by the Not Applicable Appropriate test to demonstrate turn-around -6 . applicant for flight 9 9 9 9 required. See also ACJ No. 1 to JAR-FSTD

text: simulator A.030 para 2.4.3.2 qualification.

text: d Motion effects Refer to ACJ No 1 to JAR-FSTD A.030 3.3(n) . subjective testing

text: e Motion System ± 0·05g actual None . repeatability platform linear 9 9 Ensure that motion system hardware and accelerations software (in normal flight simulator operating mode) continue to perform as originally qualified. Performance changes from the original baseline can be readily identified with this information.

text: See ACJ No. 1 to JAR-FSTD A.030 para 200 2.4.3.4

text: 9- 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: f Motion cueing None Ground and For a given set of flight simulation critical . o performance flight 9 9 9 9 manoeuvres record the relevant motion signature. variables. ntinued

text: These tests should be run with the motion buffet module disabled.

text: See ACJ No. 1 to JAR-FSTD A.030 para -C 2.4.3.3

text: g Characteristic motion None Ground and The recorded test results for characteristic . vibrations flight buffets should allow the comparison of relative amplitude versus frequency. For atmospheric disturbance testing, general purpose disturbance models that approximate demonstrable flight test data are acceptable.

text: Principally, the flight simulator results should exhibit the overall appearance and trends of the aeroplane plots, with at least some of the frequency “spikes” being present within 1 or JAR- 2 Hz of the aeroplane data.

text: FSTD

text: See ACJ No. 1 to JAR-FSTD A.030 para 2.4.3.5

text: A TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 30 (c

text: The following tests with recorded results

text: on

text: and an SOC are required for tinued

text: characteristic motion

text: vibrations, which can be sensed at the flight deck where 2- applicable by C aeroplane type:

text: 4 (1) Thrust effects with n/a Ground Test should be conducted at maximum brakes set 9 possible thrust with brakes set.

text: (2) Landing gear n/a Flight Test condition should be for a normal extended buffet 9 operational speed and not at the gear limiting speed.

text: (3) Flaps extended n/a Flight Test condition should be for a normal buffet 9 operational speed and not at the flap limiting speed.

text: (4) Speedbrake n/a Flight deployed buffet 9

text: (5) Approach-to-stall n/a Flight Test condition should be approach-to-stall. buffet 9 Post-stall characteristics are not required.

text: (6) High speed or n/a Flight Test condition should be for high speed 9- Mach buffet 9 manoeuvre buffet/wind-up-turn or 11 alternatively Mach buffet.

text: -01 SEC

text: (7) In-flight vibrations n/a Flight (clean Test should be conducted to be configuration) 9 representative of in-flight vibrations for T propeller driven aeroplanes. ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: o J

text: TD A.

text: FS FTD FNPT BITD

text: o

text: 4 VISUAL SYSTEM

text: . ntinued

text: a SYSTEM ) . RESPONSE TIME

text: (1) Transport Delay. 150 milliseconds or Pitch, roll and One separate test is required in each axis. less after controller yaw 9 9 See Appendix 5 to ACJ FSTD A.030 -C movement.

text: 300 milliseconds or less after controller FNPT I and BITD only the instrument movement. response time applies.

text: 9 9 9 9 9 9 9 9 9

text: -- or --

text: (2) Latency - 150 milliseconds or Take-off, One test is required in each axis (pitch, roll, less after controller Cruise, and 9 9 yaw) for each of the 3 conditions compared movement. Approach or with aeroplane data for a similar input. The Landing visual scene or test pattern used during the - 300 milliseconds or response testing shall be representative of less after controller the required system capacities to meet the movement. 9 9 9 9 9 9 9 9 9 daylight, twilight (dusk/dawn) and night visual capability as applicable. JAR- FS only: Response tests should be confirmed

text: in daylight , twilight and night settings as FSTD applicable.

text: FNPT I and BITD only the instrument A response time applies.

text: TS

text: b DISPLAY SYSTEM

text: FS

text: . TESTS

text: Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 30 (c

text: (a) Continuous Continuous, cross- Not Applicable Field of view should be measured using a on

text: 9 9

text: collimated cross- cockpit, minimum visual test pattern filling the entire visual tinued

text: cockpit visual field collimated visual field scene (all channels) consisting of a matrix of of view of view providing each black and white 5° squares. Installed ) pilot with 180 degrees alignment should be confirmed in a horizontal and 40 Statement of Compliance. degrees vertical field 2- of view.

text: C

text: -6 Horizontal FOV: Not

text: less than a total of 176 measured degrees (including not less than ±88 measured degrees either side of the centre of the design eye point).

text: Vertical FOV: Not less than a total of 36 measured degrees from the pilot’s and co-pilot’s eye point.

text: 200 (b) Continuous Continuous, minimum Not Applicable 30 degrees vertical field of view may be collimated visual collimated visual field insufficient to meet the requirements of ACJ

text: 11 field of view of view providing each 9 9 No. 1 to JAR-FSTD A.030 Table 2.3 pilot with 45 degrees paragraph 4.c (visual ground segment) SEC

text: horizontal and 30 degrees vertical field T of view ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (2) System geometry 5° even angular Not Applicable System geometry should be measured using

text: o

text: spacing within ± 1° as 9 9 9 9 a visual test pattern filling the entire visual measured from either scene (all channels) consisting of a matrix of ntinued

text: pilot eye-point, and black and white 5° squares with light points at within 1·5° for the intersections. The operator should ) adjacent squares. demonstrate that the angular spacing of any chosen 5° square and the relative spacing of adjacent squares are within the stated -C tolerances. The intent of this test is to -67 demonstrate local linearity of the displayed image at either pilot eye-point.

text: (3) Surface Contrast Not less than 5:1 Not Applicable Surface contrast ratio should be measured Ratio 9 9 using a raster drawn test pattern filling the entire visual scene (all channels). The test pattern should consist of black and white squares, 5 per square with a white square in the centre of each channel.

text: Measurement should be made on the centre bright square for each channel using a 1° spot photometer. This value should have a minimum brightness of 7 cd/m2 (2 foot- JAR- lamberts). Measure any adjacent dark squares. The contrast ratio is the bright FSTD square value divided by the dark square value. A Note. During contrast ratio testing, simulator aft-cab and flight deck ambient light levels TS should be zero. FS

text: Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 2 30 (c

text: (4) Highlight Not less than 20 cd/m Not Applicable Highlight brightness should be measured by Brightness (6 ft-lamberts) on the 9 9 maintaining the full test pattern described in

text: on

text: display paragraph 4.b 3) above, superimposing a highlight on the centre white square of each tinued

text: channel and measuring the brightness using

text: the 1° spot photometer. Lightpoints are not acceptable. Use of calligraphic capabilities to enhance raster brightness is acceptable.

text: 2- C

text: -6 (5) Vernier Resolution Not greater than 2 arc Not Applicable Vernier resolution should be demonstrated by

text: minutes 9 9 a test of objects shown to occupy the required visual angle in each visual display used on a scene from the pilot’s eye-point. The eye will subtend two arc minutes (arc tan (4/6 876)x60) when positioned on a 3 degree glideslope, 6 876 ft slant range from the centrally located threshold of a black runway surface painted with white threshold bars that are 16 ft wide with 4-ft gaps in-between. This should be confirmed by calculations in a statement of compliance.

text: (6) Lightpoint Size Not greater than 5 arc Not Applicable Lightpoint size should be measured using a minutes. 9 9 test pattern consisting of a centrally located single row of lightpoints reduced in length

text: until modulation is just discernible in each 9- visual channel. A row of 48 lights will form a 11 4° angle or less.

text: -01 SEC

text: T ION

text: 2 A SE 009 C J No CT -1

text: IO

text: 1- . 1 t 01 2 N 2 FLIGHT o J

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0 . . 30 (c

text: (7) Lightpoint Not less than 10:1 Not Applicable Lightpoint contrast ratio should be measured o Contrast Ratio. 9 9 using a test pattern demonstrating a 1° area filled with lightpoints (i.e. lightpoint ntinued

text: modulation just discernible) and should be compared to the adjacent background. )

text: Not less than 25:1 Note. During contrast ratio testing, simulator -C aft-cab and flight deck ambient light levels 9 9 -69 should be zero.

text: JAR-

text: FSTD

text: A

text: TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 0 c 30 (c

text: VISUAL GROUND Near end. The lights Trimmed in the Visual Ground Segment. This test is . SEGMENT computed to be visible landing 9 9 9 9 9 9 designed to assess items impacting the

text: on

text: should be visible in configuration accuracy of the visual scene presented to a the FSTD. at 30 m (100 pilot at DH on an ILS approach. Those items tinued

text: ft) wheel include Far end: ± 20% of the ) height above computed VGS touchdown RVR,

text: zone elevation glideslope (G/S) and localiser modelling 2- on glide slope accuracy (location and slope) for an ILS, C at a RVR -7 setting of 300 for a given weight, configuration and speed

text: m (1 000 ft) or representative of a point within the 350m (1 200ft) aeroplane’s operational envelope for a

text: normal approach and landing.

text: If non-homogenous fog is used, the vertical variation in horizontal visibility should be described and be included in the slant range visibility calculation used in the VGS computation.

text: FNPT: If a generic aeroplane is used as the basic model, a generic cut-off angle of 15 deg. 200 is assumed as an ideal.

text: 9- 11 -01 SEC

text: T ION

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: 5 SOUND SYSTEMS . All tests in this section should be presented o using an unweighted 1/3-octave band format ntinued

text: from band 17 to 42 (50 Hz to 16 kHz). A

text: minimum 20 second average should be taken )

text: at the location corresponding to the aeroplane data set. The aeroplane and flight simulator results should be produced using

text: -C comparable data analysis techniques.

text: See ACJ FSTD A.030 para 2.4.5

text: a TURBO-JET . AEROPLANES

text: (1) Ready for engine ± 5 dB per 1/3 octave Ground Normal condition prior to engine start. The start band 9 APU should be on if appropriate.

text: (2) All engines at idle ± 5 dB per 1/3 octave Ground Normal condition prior to take-off. band 9

text: (3) All engines at ± 5 dB per 1/3 octave Ground Normal condition prior to take-off. maximum band 9 allowable thrust JAR- with brakes set

text: (4) Climb ± 5 dB per 1/3 octave En-route climb Medium altitude.

text: FSTD

text: band 9

text: A (5) Cruise ± 5 dB per 1/3 octave Cruise Normal cruise configuration. band 9 TS

text: FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 30 (c

text: (6) Speedbrake / ± 5 dB per 1/3 octave Cruise Normal and constant speedbrake deflection spoilers extended band 9 for descent at a constant airspeed and

text: on

text: (as appropriate) power setting.

text: tinued

text: (7) Initial approach ± 5 dB per 1/3 octave Approach Constant airspeed, gear up, flaps/slats as band 9 appropriate. )

text: (8) Final approach ± 5 dB per 1/3 octave Landing Constant airspeed, gear down, full flaps. band 9

text: b PROPELLER

text: C

text: . AEROPLANES

text: -7 2

text: (2) All propellers ± 5 dB per 1/3 octave Ground Normal condition prior to take-off. feathered band 9

text: (3) Ground idle or ± 5 dB per 1/3 octave Ground Normal condition prior to take-off. equivalent band 9

text: (4) Flight idle or ± 5 dB per 1/3 octave Ground Normal condition prior to take-off. equivalent band 9

text: (5) All engines at ± 5 dB per 1/3 octave Ground Normal condition prior to take-off.

text: maximum band 9 9- allowable power 11 with brakes set

text: -01 SEC

text: T

text: (6) Climb ± 5 dB per 1/3 octave En-route climb Medium altitude. ION band 9

text: 2 A SE

text: 009 C

text: J No CT

text: IO

text: 1- . 1 t

text: 01 2 N 2

text: FLIGHT o J

text: FS FTD FNPT BITD TD A.

text: Rec Rec A B C D Init. I II MCC Init. 0

text: . . 30 (c

text: (7) Cruise ± 5 dB per 1/3 octave Cruise Normal cruise configuration.

text: o

text: band 9

text: ntinued

text: (8) Initial approach ± 5 dB per 1/3 octave Approach Constant airspeed, gear up, flaps extended

text: band 9 as appropriate, RPM as per operating

text: manual.

text: -C (9) Final approach ± 5 dB per 1/3 octave Landing Constant airspeed, gear down, full flaps, -73 band 9 RPM as per operating manual.

text: c SPECIAL CASES ± 5 dB per 1/3 octave Special cases identified as particularly . band 9 significant to the pilot, important in training,

text: or unique to a specific aeroplane type or variant.

text: d FLIGHT SIMULATOR Initial evaluation: not Results of the background noise at initial . BACKGROUND applicable. 9 qualification should be included in the QTG

text: NOISE document and approved by the qualifying Recurrent evaluation: authority. The simulated sound will be ± 3dB per 1/3 octave evaluated to ensure that the background band compared to noise does not interfere with training. Refer initial evaluation to ACJ FSTD A.030 para 2.4.5.6. The JAR- measurements are to be made with the

text: simulation running, the sound muted and a FSTD dead cockpit.

text: A TS FS Bi 2 la 0 ga 0 9 :8

text: 1 7

text: JAR- A Bila T C S

text: J No F

text: ga S FSTD 20 1

text: . 1 t

text: A R-

text: FS FTD FNPT BITD FS

text: TD A.

text: 0 e 30 (c

text: FREQUENCY Initial evaluation: not Only required if the results are to be used . RESPONSE applicable. 9 9 during recurrent evaluations according to on Recurrent evaluation: ACJ FSTD A.030 para 2.4.5.7. The results tinued

text: cannot exceed ± 5 dB shall be acknowledged by the authority at on three consecutive initial qualification. )

text: bands when compared to initial evaluation and the 2- average of the

text: C

text: absolute differences

text: 4 between initial and

text: recurrent evaluation results cannot exceed 2 dB.

text: 9- 11 -01 SEC

text: T ION

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued)

text: 2.4 Information for Validation Tests 2.4.1 Control dynamics 2.4.1.1 General The characteristics of an aircraft flight control system have a major effect on handling qualities. A significant consideration in pilot acceptability of an aircraft is the ‘feel’ provided through the flight controls. Considerable effort is expended on aircraft feel system design so that pilots will be comfortable and will consider the aircraft desirable to fly. In order for a FSTD to be representative, it too should present the pilot with the proper feel – that of the aircraft being simulated. Compliance with this requirement should be determined by comparing a recording of the control feel dynamics of the FSTD to actual aircraft measurements in the relevant configurations. a. Recordings such as free response to a pulse or step function are classically used to estimate the dynamic properties of electromechanical systems. In any case, the dynamic properties can only be estimated since the true inputs and responses are also only estimated. Therefore, it is imperative that the best possible data be collected since close matching of the FSTD control loading system to the aircraft systems is essential. The required dynamic control checks are indicated in paragraph 2.3–2b(1) to (3) of the table of FSTD validation tests. b. For initial and upgrade evaluations, it is required that control dynamics characteristics be measured at and recorded directly from the flight controls. This procedure is usually accomplished by measuring the free response of the controls using a step input or pulse input to excite the system. The procedure should be accomplished in relevant flight conditions and configurations. c. For aeroplanes with irreversible control systems, measurements may be obtained on the ground if proper pitot-static inputs (if applicable) are provided to represent airspeeds typical of those encountered in flight. Likewise, it may be shown that for some aeroplanes, take-off, cruise, and landing configurations have like effects. Thus, one may suffice for another. If either or both considerations apply, engineering validation or aeroplane manufacturer rationale should be submitted as justification for ground tests or for eliminating a configuration. For FSTDs requiring static and dynamic tests at the controls, special test fixtures will not be required during initial and upgrade evaluations if the MQTG shows both test fixture results and the results of an alternate approach, such as computer plots which were produced concurrently and show satisfactory agreement. Repeat of the alternate method during the initial evaluation would then satisfy this test requirement. 2.4.1.2 Control dynamics evaluation.

text: The dynamic properties of control systems are often stated in terms of frequency, damping, and a number of other classical measurements which can be found in texts on control systems. In order to establish a consistent means of validating test results for FSTD control loading, criteria are needed that will clearly define the interpretation of the measurements and the tolerances to be applied. Criteria are needed for underdamped, critically damped, and overdamped systems. In the case of an underdamped system with very light damping, the system may be quantified in terms of frequency and damping. In critically damped or overdamped systems, the frequency and damping are not readily measured from a response time history. Therefore, some other measurement should be used. Tests to verify that control feel dynamics represent the aeroplane should show that the dynamic damping cycles (free response of the controls) match that of the aeroplane within specified tolerances. The method of evaluating the response and the tolerance to be applied is described in the underdamped and critically damped cases are as follows:

text: a. Underdamped Response. 1. Two measurements are required for the period, the time to first zero crossing (in case a rate limit is present) and the subsequent frequency of oscillation. It is necessary to measure cycles on an individual basis in case there are non-uniform periods in the response. Each period will be independently compared with the respective period of the aeroplane control system and, consequently, will enjoy the full tolerance specified for that period.

text: 2. The damping tolerance should be applied to overshoots on an individual basis. Care should be taken when applying the tolerance to small overshoots since the significance of such overshoots becomes

text: 2009-11-01 2-C-75 JAR-FSTD A

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued)

text: questionable. Only those overshoots larger than 5% of the total initial displacement should be considered. The residual band, labelled T(Ad) in Figure 1 is ± 5% of the initial displacement amplitude Ad from the steady state value of the oscillation. Only oscillations outside the residual band are considered significant. When comparing FSTD data to aeroplane data, the process should begin by overlaying or aligning the FSTD and aeroplane steady state values and then comparing amplitudes of oscillation peaks, the time of the first zero crossing, and individual periods of oscillation. The FSTD should show the same number of significant overshoots to within one when compared against the aeroplane data. This procedure for evaluating the response is illustrated in Figure 1 below. b. Critically damped and overdamped response. Due to the nature of critically damped and overdamped responses (no overshoots), the time to reach 90% of the steady state (neutral point) value should be the same as the aeroplane within ± 10%. Figure 2 illustrates the procedure. c. Special considerations. Control systems, which exhibit characteristics other than classical overdamped or underdamped responses should meet specified tolerances. In addition, special consideration should be given to ensure that significant trends are maintained. 2.4.1.3. Tolerances. The following table summarises the tolerances, T. See figures 1 and 2 for an illustration of the referenced measurements.

text: T(P0) ± 10% of P0 T(P1) ± 20% of P1 T(P2) ± 30% of P2 T(Pn) ± 10(n+1)% of Pn T(An) ± 10% of A1 T(Ad) ± 5% of Ad = residual band Significant overshoots First overshoot and ± 1 subsequent overshoots

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD A 2-C-76 2009-11-01

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued)

text: Ad P = Period A = Amplitude 0.9Ad T(P) = Tolerance applied to period (10% of P0, 10(n+1)% of Pn) T(A) = Tolerance applied to amplitude (0.1 A1)

text: Displacement vs T(A) Time Residual Band T(P0) T(P1) T(A) T(P2 T(Ad)

text: T(A)

text: T(A) A1 P0 P1 P2

text: Figure 1 : Underdamped step response

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-77 JAR-FSTD A

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued)

text: Ad 0.9Ad

text: T(P0) 0.1 Ad

text: P0 Displacement vs Time

text: Figure 2 : Critically damped step response

text: 2.4.1.4 Alternate method for control dynamics evaluation. An alternate means for validating control dynamics for aircraft with hydraulically powered flight controls and artificial feel systems is by the measurement of control force and rate of movement. For each axis of pitch, roll, and yaw, the control should be forced to its maximum extreme position for the following distinct rates. These tests should be conducted at typical flight and ground conditions. a. Static test – Slowly move the control such that approximately 100 seconds are required to achieve a full sweep. A full sweep is defined as movement of the controller from neutral to the stop, usually aft or right stop, then to the opposite stop, then to the neutral position. b. Slow dynamic test – Achieve a full sweep in approximately 10 seconds. c. Fast dynamic test – Achieve a full sweep in approximately 4 seconds. Note: Dynamic sweeps may be limited to forces not exceeding 44.5 daN (100 lbs). 2.4.1.5 Tolerances 1. Static test , see paragraph 2.3 – 2.a(1), (2), and (3) of the table of FSTD validation tests. 2. Dynamic test – ± 0.9 daN (2 lbs) or ± 10% on dynamic increment above static test. The Authority is open to alternative means such as the one described above. Such alternatives should, however, be justified and appropriate to the application. For example, the method described here may not apply to all manufacturers’ systems and certainly not to aeroplanes with reversible control systems. Hence, each case should be considered on its own merit on an ad hoc basis. Should the Authority find that alternative methods do not result in satisfactory performance, then more conventionally accepted methods should be used. 2.4.2 Ground Effect 2.4.2.1 For a FSTD to be used for take-off and landing it should faithfully reproduce the aerodynamic changes which occur in ground effect. The parameters chosen for FSTD validation should be indicative of these changes. A dedicated test should be provided which will validate the aerodynamic ground effect characteristics.

text: JAR-FSTD A 2-C-78 2009-11-01

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued)

text: The selection of the test method and procedures to validate ground effect is at the option of the organisation performing the flight tests; however, the flight test should be performed with enough duration near the ground to validate sufficiently the ground-effect model.

text: 2.4.2.2 Acceptable tests for validation of ground effect include: a. Level fly-bys. The level fly-bys should be conducted at a minimum of three altitudes within the ground effect, including one at no more than 10% of the wingspan above the ground, one each at approximately 30% and 50% of the wingspan where height refers to main gear tyre above the ground. In addition, one level-flight trim condition should be conducted out of ground effect, e.g. at 150% of wingspan. b. Shallow approach landing. The shallow approach landing should be performed at a glide slope of approximately one degree with negligible pilot activity until flare. If other methods are proposed, a rationale should be provided to conclude that the tests performed validate the ground-effect model. 2.4.2.3 The lateral-directional characteristics are also altered by ground effect. For example, because of changes in lift, roll damping is affected. The change in roll damping will affect other dynamic modes usually evaluated for FSTD validation. In fact, Dutch roll dynamics, spiral stability, and roll-rate for a given lateral control input are altered by ground effect. Steady heading sideslips will also be affected. These effects should be accounted for in the FSTD modelling. Several tests such as ‘crosswind landing’, ‘one engine inoperative landing’, and ‘engine failure on take-off’ serve to validate lateral-directional ground effect since portions of them are accomplished whilst transiting heights at which ground effect is an important factor. 2.4.3 Motion System 2.4.3.1 General

text: a. Pilots use continuous information signals to regulate the state of the aeroplane. In concert with the instruments and outside-world visual information, whole-body motion feedback is essential in assisting the pilot to control the aeroplane’s dynamics, particularly in the presence of external disturbances. The motion system should therefore meet basic objective performance criteria, as well as being subjectively tuned at the pilot's seat position to represent the linear and angular accelerations of the aeroplane during a prescribed minimum set of manoeuvres and conditions. Moreover, the response of the motion cueing system should be repeatable. b. The objective validation tests presented in this paragraph are intended to qualify the FSTD motion cueing system from a mechanical performance standpoint. Additionally, the list of motion effects provides a representative sample of dynamic conditions that should be present in the FSTD. A list of representative training-critical manoeuvres that should be recorded during initial qualification (but without tolerance) to indicate the FSTD motion cueing performance signature has been added to this document. These are intended to help to improve the overall standard of FSTD motion cueing.

text: 2.4.3.2 Motion System Checks. The intent of tests as described in the table of FSTD validation tests, paragraph 2.3 - 3.a, frequency response, 3.b leg balance, and 3.c, turn-around check, is to demonstrate the performance of the motion system hardware, and to check the integrity of the motion set-up with regard to calibration and wear. These tests are independent of the motion cueing software and should be considered as robotic tests.

text: 2.4.3.3 Motion Cueing Performance Signature a. Background. The intent of this test is to provide quantitative time history records of motion system response to a selected set of automated QTG manoeuvres during initial qualification. This is not intended to be a comparison of the motion platform accelerations against the flight test recorded accelerations (i.e. not to be compared against aeroplane cueing). This information describes a minimum set of manoeuvres and a guideline for determining the FSTD’s motion footprint. If over time there is a change to the initially certified motion software load or motion hardware then these baseline tests should be rerun.

text: b. List of tests. Table 1 delineates those tests that are important to pilot motion cueing and are general tests applicable to all types of aeroplanes and thus the motion cueing performance signature should be run for initial qualification. These tests can be run at any time deemed acceptable to the Authority prior to or

text: 2009-11-01 2-C-79 JAR-FSTD A

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued) during the initial qualification. The tests in table 2 are also significant to pilot motion cues but are provided for information only. These tests are not required to be run. c. Priority. A priority (X) is given to each of these manoeuvres, with the intent of placing greater importance on those manoeuvres that directly influence pilot perception and control of the aeroplane motions. For the manoeuvres designated with a priority in the tables below, the FSTD motion cueing system should have a high tilt co-ordination gain, high rotational gain, and high correlation with respect to the aeroplane simulation model. d. Data Recording. The minimum list of parameters provided should allow for the determination of the FSTD’s motion cueing performance signature for the initial qualification. The following parameters are recommended as being acceptable to perform such a function: 1. flight model acceleration and rotational rate commands at the pilot reference point; 2. motion actuators position; 3. actual platform position; 4. actual platform acceleration at pilot reference point. 2.4.3.4 Motion System Repeatability. The intent of this test is to ensure that the motion system software and motion system hardware have not degraded or changed over time. This diagnostic test should be run during recurrent checks in lieu of the robotic tests. This will allow an improved ability to determine changes in the software or determine degradation in the hardware that have adversely affected the training value of the motion as was accepted during the initial qualification. The following information delineates the methodology that should be used for this test. a. Conditions: 1. One test case on-ground: to be determined by the operator; 2. One test case In-flight: to be determined by the operator. b. Input: The inputs should be such that both rotational accelerations/rates and linear accelerations are inserted before the transfer from aeroplane centre of gravity to pilot reference point with a minimum amplitude of 5deg/sec/sec, 10deg/sec and 0·3g respectively to provide adequate analysis of the output. c. Recommended output: 1. actual platform linear accelerations; the output will comprise accelerations due to both the linear and rotational motion acceleration; 2. motion actuators position

text: JAR-FSTD A 2-C-80 2009-11-01

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued)

text: No. Associated Manoeuvre Priority Comments validation test 1 1b4 Take-off rotation (Vr to V2) X Pitch attitude due to initial climb should dominate over cab tilt due to longitudinal acceleration. 2 1b5 Engine failure between V1 and Vr X 3 2e6 Pitch change during go-around X 4 2c2 & 2c4 Configuration changes X 5 2c1 Power change dynamics X Resulting effects of power changes 6 2e1 Landing flare X 7 2e1 Touchdown bump

text: Table 1 – Tests required for initial qualification

text: No. Associated Manoeuvre Priority Comments validation test 8 1a2 Taxi (including acceleration, turns, X braking), with presence of ground rumble 9 1b4 Brake release and initial acceleration X 10 1b1 & 3g Ground rumble on runway, acceleration X Scuffing and velocity cues are given during take off, scuffing, runway lights priority and surface discontinuities 11 1b2 & 1b7 Engine failure prior to V1 (RTO) X Lateral and directional cues are given priority 12 1c1 Steady-state climb X 13 1d1& 1d2 Level flight acceleration and deceleration 14 2c6 Turns X 15 1b8 Engine failures 16 2c8 Stall characteristics X 17 System failures X Priority depending on the type of system failure and aeroplane type (e.g. flight controls failures, rapid decompression, inadvertent thrust reverser deployment) 18 2g1 & 2e3 Wind shear/crosswind landing X Influence on vibrations and on attitude control 19 1e1 Deceleration on runway Including contamination effects

text: Table 2 – Tests that are significant but are not required to be run

text: 2009-11-01 2-C-81 JAR-FSTD A

text: Bilaga 1

text: ACJ No.1 to JAR-STD 1A.030 (continued)

text: 2.4.3.5 Motion vibrations a. Presentation of results. The characteristic motion vibrations are a means to verify that the FSTD can reproduce the frequency content of the aeroplane when flown in specific conditions. The test results should be presented as a Power Spectral Density (PSD) plot with frequencies on the horizontal axis and amplitude on the vertical axis. The aeroplane data and FSTD data should be presented in the same format with the same scaling. The algorithms used for generating the FSTD data should be the same as those used for the aeroplane data. If they are not the same then the algorithms used for the FSTD data should be proven to be sufficiently comparable. As a minimum the results along the dominant axes should be presented and a rationale for not presenting the other axes should be provided.

text: b. Interpretation of results. The overall trend of the PSD plot should be considered while focusing on the dominant frequencies. Less emphasis should be placed on the differences at the high frequency and low amplitude portions of the PSD plot. During the analysis it should be considered that certain structural components of the FSTD have resonant frequencies that are filtered and thus may not appear in the PSD plot. If such filtering is required the notch filter bandwidth should be limited to 1 Hz to ensure that the buffet feel is not adversely affected. In addition, a rationale should be provided to explain that the characteristic motion vibration is not being adversely affected by the filtering. The amplitude should match aeroplane data as per the description below; however, if for subjective reasons the PSD plot was altered a rationale should be provided to justify the change. If the plot is on a logarithmic scale it may be difficult to interpret the -3 2 amplitude of the buffet in terms of acceleration. A 1x10 grms /Hz would describe a heavy buffet. On the -6 2 other hand, a 1x10 grms /Hz buffet is almost not perceivable; but may represent a buffet at low speed. The previous two examples could differ in magnitude by 1 000. On a PSD plot this represents three decades (one decade is a change in order of magnitude of 10; two decades is a change in order of magnitude of 100, etc.).

text: 2.4.4 Visual System 2.4.4.1 Visual Display System a. Contrast ratio (daylight systems). Should be demonstrated using a raster drawn test pattern filling the entire visual scene (three or more channels) consisting of a matrix of black and white squares no larger than 5 degrees per square with a white square in the centre of each channel. Measurement should be made on the centre bright square for each channel using a 1 degree spot photometer. Measure any adjacent dark squares. The contrast ratio is the bright square value divided by the dark square value. Lightpoint contrast ratio is measured when lightpoint modulation is just discernable compared to the adjacent background. See paragraph 2.3.4.b.(3) and paragraph 2.3.4.b.(7). b. Highlight brightness test (daylight systems). Should be demonstrated by maintaining the full test pattern described above, the superimposing a highlight on the centre white square of each channel and measure the brightness using the 1 degree spot photometer. Lightpoints are not acceptable. Use of calligraphic capabilities to enhance raster brightness is acceptable. See paragraph 2.3.4.b.(4).

text: c. Resolution (daylight systems) should be demonstrated by a test of objects shown to occupy a visual angle of not greater than the specified value in arc minutes in the visual scene from the pilot’s eyepoint. This should be confirmed by calculations in the statement of compliance. See paragraph 2.3.4.b.(5). d. Lightpoint size (daylight systems) –should be measured in a test pattern consisting of a single row of lightpoints reduced in length until modulation is just discernible. See paragraph 2.3.4.b.(6).

text: e. Lightpoint size (twilight and night systems) – of sufficient resolution so as to enable achievement of visual feature recognition tests according to paragraph 2.3.4.b.(6). 2.4.4.2 Visual ground segment (a) Altitude and RVR for the assessment have been selected in order to produce a visual scene that can be readily assessed for accuracy (RVR calibration) and where spatial accuracy (centreline and G/S) of the simulated aeroplane can be readily determined using approach/runway lighting and flight deck instruments. (b) The QTG should indicate the source of data, i.e. airport and runway used, ILS G/S antenna location (airport and aeroplane), pilot eye reference point, flight deck cut-off angle, etc., used to make accurately visual ground segment (VGS) scene content calculations.

text: JAR-FSTD A 2-C-82 2009-11-01

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued) (c) Automatic positioning of the simulated aeroplane on the ILS is encouraged. If such positioning is accomplished, diligent care should be taken to ensure the correct spatial position and aeroplane attitude is achieved. Flying the approach manually or with an installed autopilot should also produce acceptable results. 2.4.5 Sound System 2.4.5.1 General. The total sound environment in the aeroplane is very complex, and changes with atmospheric conditions, aeroplane configuration, airspeed, altitude, power settings, etc. Thus, flight deck sounds are an important component of the flight deck operational environment and as such provide valuable information to the flight crew. These aural cues can either assist the crew, as an indication of an abnormal situation, or hinder the crew, as a distraction or nuisance. For effective training, the FSTD should provide flight deck sounds that are perceptible to the pilot during normal and abnormal operations, and that are comparable to those of the aeroplane. Accordingly, the FSTD operator should carefully evaluate background noises in the location being considered. To demonstrate compliance with the sound requirements, the objective or validation tests in this paragraph have been selected to provide a representative sample of normal static conditions typical of those experienced by a pilot. 2.4.5.2 Alternate engine fits. For FSTDs with multiple propulsion configurations any condition listed in paragraph 2.3, the table of FSTD validation tests, that is identified by the aeroplane manufacturer as significantly different, due to a change in engine model, should be presented for evaluation as part of the QTG. 2.4.5.3 Data and Data Collection System (a) Information provided to the FSTD manufacturer should comply with "IATA Flight Simulator Design & Performance Data Requirements", 6th Edition, 2000. This information should contain calibration and frequency response data. (b) The system used to perform the tests listed in para.2.3.5, within the table of FSTD validation tests, should comply with the following standards: (1) ANSI S1.11-1986 - Specification for octave, half octave and third octave band filter sets; (2) IEC 1094-4 - 1995 - measurement microphones - type WS2 or better. 2.4.5.4 Headsets. If headsets are used during normal operation of the aeroplane they should also be used during the FSTD evaluation. 2.4.5.5 Playback equipment. Recordings of the QTG conditions according to paragraph 2.3, table of FSTD validation tests, should be provided during initial evaluations. 2.4.5.6 Background noise (a) Background noise is the noise in the FSTD due to the FSTD's cooling and hydraulic systems that is not associated with the aeroplane, and the extraneous noise from other locations in the building. Background noise can seriously impact the correct simulation of aeroplane sounds, so the goal should be to keep the background noise below the aeroplane sounds. In some cases, the sound level of the simulation can be increased to compensate for the background noise. However, this approach is limited by the specified tolerances and by the subjective acceptability of the sound environment to the evaluation pilot. (b) The acceptability of the background noise levels is dependent upon the normal sound levels in the aeroplane being represented. Background noise levels that fall below the lines defined by the following points, may be acceptable (refer to figure 3): (1) 70 dB @ 50 Hz; (2) 55 dB @ 1 000 Hz; (3) 30 dB @ 16 kHz. These limits are for unweighted 1/3 octave band sound levels. Meeting these limits for background noise does not ensure an acceptable FSTD. Aeroplane sounds, which fall below this limit require careful review and may require lower limits on the background noise.

text: 2009-11-01 2-C-83 JAR-FSTD A

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued) (c) The background noise measurement may be rerun at the recurrent evaluation as stated in paragraph 2.4.5.8. The tolerances to be applied are that recurrent 1/3 octave band amplitudes cannot exceed ± 3 dB when compared to the initial results. 2.4.5.7 Frequency response - Frequency response plots for each channel should be provided at initial evaluation. These plots may be rerun at the recurrent evaluation as per paragraph 2.4.5.8. The tolerances to be applied are as follows: (a) recurrent 1/3 octave band amplitudes cannot exceed ± 5 dB for three consecutive bands when compared to initial results. (b) the average of the sum of the absolute differences between initial and recurrent results cannot exceed 2 dB (refer table 3). 2.4.5.8 Initial and recurrent evaluations. If recurrent frequency response and FSTD background noise results are within tolerance, respective to initial evaluation results, and the operator can prove that no software or hardware changes have occurred that will affect the aeroplane cases, then it is not required to rerun those cases during recurrent evaluations. If aeroplane cases are rerun during recurrent evaluations then the results may be compared against initial evaluation results rather than aeroplane master data. 2.4.5.9 Validation testing. Deficiencies in aeroplane recordings should be considered when applying the specified tolerances to ensure that the simulation is representative of the aeroplane. Examples of typical deficiencies are: (a) variation of data between tail numbers;

text: (b) frequency response of microphones;

text: (c) repeatability of the measurements;

text: (d) extraneous sounds during recordings.

text: JAR-FSTD A 2-C-84 2009-11-01

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued)

text: Fi

text: 80.0 70 dB @ 50 Hz 70.0

text: 60.0 55 dB @ 1 kHz 50.0

text: dB SP

text: L 40.0

text: 30.0 30 dB @ 16 kHz 20.0

text: 0.0 0 0 0 50 63 80 100 125 160 200 250 315 400 500 630 800 1000 1250 1600 2000 2500 3150 4000 5000 6300 8000 1000 1250 1600

text: Figure 3. 1/3 Octave Band Frequency (Hz)

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-85 JAR-FSTD A

text: SECTION 2

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued)

text: Band Initial Recurrent Absolute Centre Results Results Difference Freq. (dBSPL) (dBSPL)

text: 50 75.0 73.8 1.2 63 75.9 75.6 0.3 80 77.1 76.5 0.6 100 78.0 78.3 0.3 125 81.9 81.3 0.6 160 79.8 80.1 0.3 200 83.1 84.9 1.8 250 78.6 78.9 0.3 315 79.5 78.3 1.2 400 80.1 79.5 0.6 500 80.7 79.8 0.9 630 81.9 80.4 1.5 800 73.2 74.1 0.9 1000 79.2 80.1 0.9 1250 80.7 82.8 2.1 1600 81.6 78.6 3.0 2000 76.2 74.4 1.8 2500 79.5 80.7 1.2 3150 80.1 77.1 3.0 4000 78.9 78.6 0.3 5000 80.1 77.1 3.0 6300 80.7 80.4 0.3 8000 84.3 85.5 1.2 10000 81.3 79.8 1.5 12500 80.7 80.1 0.6 16000 71.1 71.1 0.0 Average 1.1

text: Table 3 - Example of recurrent frequency response test tolerance

text: JAR-FSTD A 2-C-86 2009-11-01

text: Bilaga 1

text: ACJ No.1 to JAR-FSTD A.030 (continued)

text: Functions and Subjective Tests

text: 3.1 Discussion 3.1.1 Accurate replication of aeroplane systems functions will be checked at each flight crewmember position. This includes procedures using the operator’s approved manuals, aeroplane manufacturers approved manuals and checklists. A useful source of guidance for conducting the tests required to establish that the criteria set out in this document are complied with by the flight simulator under evaluation are published in the RAeS Airplane Flight Simulator Evaluation Handbook. Handling qualities, performance, and FSTD systems operation will be subjectively assessed. In order to assure the functions tests are conducted in an efficient and timely manner, operators are encouraged to coordinate with the appropriate Authority responsible for the evaluation so that any skills, experience or expertise needed by the Authority in charge of the evaluation team are available. 3.1.2 The necessity of functions and subjective tests arises from the need to confirm that the simulation has produced a totally integrated and acceptable replication of the aeroplane. Unlike the objective tests listed in paragraph 2 above, the subjective testing should cover those areas of the flight envelope which may reasonably be reached by a trainee, even though the FSTD has not been approved for training in that area. Thus it is prudent to examine, for example, the normal and abnormal FSTD performance to ensure that the simulation is representative even though it may not be a requirement for the level of qualification being sought. (Any such subjective assessment of the simulation should include reference to paragraph 2 and 3 above in which the minimum objective standards acceptable for that Qualification Level are defined. In this way it is possible to determine whether simulation is an absolute requirement or just one where an approximation, if provided, has to be checked to confirm that it does not contribute to negative training.) 3.1.3 At the request of the Authority, the FSTD may be assessed for a special aspect of an operator’s training programme during the functions and subjective portion of an evaluation. Such an assessment may include a portion of a Line Oriented Flight Training (LOFT) scenario or special emphasis items in the operator’s training programme. Unless directly related to a requirement for the current Qualification Level, the results of such an evaluation would not affect the FSTD’s current status.

text: 3.1.4 Functions tests will be run in a logical flight sequence at the same time as performance and handling assessments. This also permits real time FSTD running for 2 to 3 hours, without repositioning or flight or position freeze, thereby permitting proof of reliability. 3.2 Test requirements 3.2.1 The ground and flight tests and other checks required for qualification are listed in the table of functions and subjective tests. The table includes manoeuvres and procedures to assure that the FSTD functions and performs appropriately for use in pilot training, testing and checking in the manoeuvres and procedures normally required of a training, testing and checking programme. 3.2.2 Manoeuvres and procedures are included to address some features of advanced technology aeroplanes and innovative training programmes. For example, ‘high angle of attack manoeuvring’ is included to provide an alternative to ‘approach to stalls’. Such an alternative is necessary for aeroplanes employing flight envelope limiting technology.

text: 3.2.3 All systems functions will be assessed for normal and, where appropriate, alternate operations. Normal, abnormal, and emergency procedures associated with a flight phase will be assessed during the evaluation of manoeuvres or events within that flight phase. Systems are listed separately under ‘any flight phase’ to assure appropriate attention to systems checks. 3.2.4 When evaluating functions and subjective tests, the fidelity of simulation required for the highest level of qualification should be very close to the aeroplane. However, for the lower levels of qualification the degree of fidelity may be reduced in accordance with the criteria contained in paragraph 2 above. 3.2.5 Evaluation of the lower orders of FSTD should be tailored only to the systems and flight conditions which have been simulated. Similarly, many tests will be applicable for automatic flight. Where automatic flight is not possible and pilot manual handling is required, the FSTD shall be at least controllable to permit the conduct of the flight. 3.2.6 Any additional capability provided in excess of the minimum required standards for a particular Qualification Level should be assessed to ensure the absence of any negative impact on the intended training and testing manoeuvres.

text: 2009-11-01 2-C-87 JAR-FSTD A

text: SECTION 2

text: Bilaga 1

text: INTENTIONALLY LEFT BLANK JAR-FSTD A 2-C-88 2009-11-01

text: 2 A SEC

text: 009 C

text: J No

text: -1 T 1- .1 IO

text: 01 2 t N

text: o J 2

text: Functions and subjective tests A

text: R-FS

text: TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT BITD

text: TD A.

text: A B C D 1 2 I II MCC

text: a PREPARATION FOR FLIGHT 0 30 (c (1) Preflight. Accomplish a functions check of all switches, indicators, systems, and equipment at all crewmembers’ and instructors’ stations and determine that; o (a) the flight deck design and functions are identical to that of the aeroplane or class of 9 9 9 9 9 9 9 9 9 ntinued

text: aeroplane simulated ) (b) design and functions represent those of the simulated class of aeroplane 9

text: b SURFACE OPERATIONS (PRE-TAKE-OFF)

text: (1) Engine Start

text: -C

text: -89 (a) Normal start 9 9 9 9 9 9 9 9 9 9

text: (b) Alternate start procedures 9 9 9 9 9 9

text: (c) Abnormal starts and shutdowns (hot start, hung start, tail pipe fire, etc.) 9 9 9 9 9 9

text: (2) Pushback/Powerback 9 9 9 9

text: (3) Taxi

text: (a) Thrust response 9 9 9 9 9 9 9

text: (b) Power lever friction 9 9 9 9 9 9 9

text: (c) Ground handling 9 9 9 9 9 9 9

text: (d) Nose wheel scuffing 9 9 9 9

text: (e) Brake operation (normal and alternate/emergency) 9 9 9

text: A Brake fade (if applicable) 9 9 9 9

text: B. Other 9 9 9 9

text: JAR-FSTD A TSFS 2

text: Bilaga 1 0 0 9 :8 7

text: JA R- A Bila T FS C S

text: J No F

text: TD ga S

text: 1 20 A .1 t 09:87

text: o J TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT BITD A R- A B C D 1 2 I II MCC FS TD A.

text: c TAKE-OFF 0 30 (c (1) Normal 9(1) on (a) Aeroplane/engine parameter relationships 9 9 9 9 9 9 9 9 9 9 tinued)

text: (b) Acceleration characteristics (motion) 9 9 9 9

text: (c) Acceleration characteristics (not associated with motion) 9 9 9 9 9 9 9 9 9 9 2- (d) Nose wheel and rudder steering 9 9 9 9 9 9 9 9 9

text: C-

text: 90 (e) Crosswind (maximum demonstrated) 9 9 9 9 9 9

text: (f) Special performance (e.g. reduced V1, max de-rate, short field operations) 9 9 9 9

text: (g) Low visibility take-off 9 9 9 9 9 9

text: (h) Landing gear, wing flap leading edge device operation 9 9 9 9 9 9 9 9

text: (i) Contaminated runway operation 9 9 9 9

text: (j) Other 9 9 9 9

text: (2) Abnormal/emergency

text: (a) Rejected 9 9 9 9 9

text: (b) Rejected special performance (e.g. reduced V1, max de-rate, short field 9 9 9 9 operations) 2 (c) With failure of most critical engine at most critical point, continued take-off 9 9 9 9

text: 0 (d) With wind shear 9 9 9 9

text: -1 (e) Flight control system failures, reconfiguration modes, manual reversion and 9 9 9 9

text: 01 associated handling (f) Rejected, brake fade 9 9 9 9

text: (g) Rejected, contaminated runway 9 9 9 9

text: (h) Other 9 9 9 9 SEC

text: T ION

text: 2 A SEC

text: 009 C

text: J No

text: -1 T 1- .1 IO

text: 01 2 t N

text: o J 2 A R-FS

text: A B C D 1 2 I II MCC TD A.

text: 0 d CLIMB 30 (c

text: (1) Normal 9 9 9 9 9 9 9 9 9 9 o (2) One or more engines inoperative 9 9 9 9 9 9 9(2) 9 9 9(2) ntinued

text: (3) Other 9 9 9 9 9 9 )

text: e CRUISE

text: (1) Performance characteristics (speed vs. power) 9 9 9 9 9 9 9 9 9 9 -C (2) High altitude handling 9 9 9 9 9 9 9 9

text: (3) High Mach number handling (Mach tuck, Mach buffet) and recovery (trim change) 9 9 9 9 9 9 9(3) 9(3)

text: (4) Overspeed warning (in excess of Vmo or Mmo) 9 9 9 9

text: (5) High IAS handling 9 9 9 9 9 9 9 9

text: JAR-FSTD A TSFS 2

text: Bilaga 1 0 0 9 :8 7

text: JA R- A Bila T FS C S

text: J No F

text: TD ga S

text: 1 20 A .1 t 09:87

text: f MANOEUVRES 0 30 (c (1) High angle of attack, approach to stalls, stall warning, buffet, and g-break (take-off, 9 9 9 9 9 9 9 9 9 9 cruise, approach, and landing configuration) on (2) Flight envelope protection (high angle of attack, bank limit, overspeed, etc) 9 9 9 9 9 9 tinued)

text: (3) Turns with/without speedbrake/spoilers deployed 9 9 9 9 9 9 9 9 9

text: (4) Normal and standard rate turns 9 9 9 9 9

text: C- (5) Steep turns 9 9 9 9 9

text: (6) Performance turn 9 9 9 9

text: (7) In flight engine shutdown and restart (assisted and windmill) 9 9 9 9 9 9 9

text: (8) Manoeuvring with one or more engines inoperative, as appropriate 9 9 9 9 9 9 9(2) 9 9 9(2)

text: (9) Specific flight characteristics (e.g. direct lift control) 9 9 9 9 9 9

text: (10) Flight control system failures, reconfiguration modes, manual reversion and associated 9 9 9 9 9 9 9 handling (11) Other 9 9 9 9 9 9

text: g DESCENT

text: (1) Normal 9 9 9 9 9 9 9 9 9 9

text: (2) Maximum rate (clean and with speedbrake, etc) 9 9 9 9 9 9 9 9 9

text: 0 (3) With autopilot 9 9 9 9 9

text: 0 9

text: -1 (4) Flight control system failures, reconfiguration modes, manual reversion and associated 9 9 9 9 9 9 9

text: handling

text: (5) Other 9 9 9 9 9 9

text: SEC

text: T ION

text: 2 A SEC

text: 009 C

text: J No

text: -1 T 1- .1 IO

text: 01 2 t N

text: o J 2 A R-FS

text: A B C D 1 2 I II MCC TD A.

text: h INSTRUMENT APPROACHES AND LANDING 0 30 (c Only those instrument approach and landing tests relevant to the simulated aeroplane type or class should be selected from the following list, where tests should be made with limiting wind o velocities, wind shear and with relevant system failures, including the use of Flight Director. ntinued (1) Precision (a) PAR 9 9 9 9 9 9 9 9 )

text: (b) CAT I/GBAS (ILS/MLS) published approaches A Manual approach with/without flight director including landing 9 9 9 9 9 9 9 9 -C B Autopilot/autothrottle coupled approach and manual landing 9 9 9 9 9 9 9

text: C Manual approach to DH and G/A all engines 9 9 9 9 9 9 9 9 9 9

text: D Manual one engine out approach to DH and G/A 9 9 9 9 9 9 9 9(2) 9(2) 9 E Manual approach controlled with and without flight director to 30 m (100 ft) below CAT I minima 9 9 9 9 (i) with cross-wind (maximum demonstrated) (ii) with wind shear 9 9 9 9

text: F Autopilot/autothrottle coupled approach, one engine out to DH and G/A 9 9 9 9 9 9 9

text: G Approach and landing with minimum/standby electrical power 9 9 9 9 9 9 9

text: (c) CAT II/GBAS (ILS/MLS) published approaches A Autopilot/autothrottle coupled approach to DH and landing 9 9 9 9 9 9 B Autopilot/autothrottle coupled approach to DH and G/A 9 9 9 9 9 9

text: C Autocoupled approach to DH and manual G/A 9 9 9 9 9 9

text: D Autocoupled/autothrottle Category II published approach 9 9 9 9

text: JAR-FSTD A TSFS 2

text: Bilaga 1 0 0 9 :8 7

text: JA R- A Bila T FS C S

text: J No F

text: TD ga S

text: 1 20 A .1 t 09:87

text: (d) CAT III/GBAS (ILS/MLS) published approaches 0 30 (c A Autopilot/autothrottle coupled approach to land and rollout 9 9 9 9 9 9

text: on B Autopilot/autothrottle coupled approach to DH/Alert Height and G/A 9 9 9 9 9 9 tinued) C Autopilot/autothrottle coupled approach to land and rollout with one engine out 9 9 9 9 9 9

text: D Autopilot/autothrottle coupled approach to DH/Alert Height and G/A with one 9 9 9 9 9 9 engine out

text: C- E Autopilot/autothrottle coupled approach (to land or to go around) 94 (i) with generator failure 9 9 9 9

text: (ii) with 10 knot tail wind 9 9 9 9

text: (iii) with 10 knot crosswind 9 9 9 9

text: (2) Non-precision

text: (a) NDB 9 9 9 9 9 9 9 9 9 9 (b) VOR, VOR/DME, VOR/TAC 9 9 9 9 9 9 9 9 9 9 (c) RNAV (GNSS) 9 9 9 9 9 9 9

text: (d) ILS LLZ (LOC), LLZ(LOC)/BC 9 9 9 9 9 9 9 9 9 9 (e) ILS offset localizer 9 9 9 9

text: (f) direction finding facility 9 9 9 9

text: 0 (g) surveillance radar 9 9 9 9

text: 9 NOTE: If Standard Operating Procedures are to use autopilot for non-precision

text: 1- approaches then these should be evaluated.

text: SEC

text: T ION

text: 2 A SEC

text: 009 C

text: J No

text: -1 T 1- .1 IO

text: 01 2 t N

text: o J 2 A R-FS

text: A B C D 1 2 I II MCC TD A.

text: i VISUAL APPROACHES (SEGMENT) AND LANDINGS 0 30 (c (1) Manoeuvring, normal approach and landing all engines operating with and without visual 9 9 9 9 9 9 approach aid guidance o (2) Approach and landing with one or more engines inoperative 9 9 9 9 9 9 ntinued

text: (3) Operation of landing gear, flap/slats and speedbrakes (normal and abnormal) 9 9 9 9 ) (4) Approach and landing with crosswind (max. demonstrated for Flight simulator) 9 9 9 9 9 9

text: (5) Approach to land with wind shear on approach 9 9 9 9

text: (6) Approach and landing with flight control system failures,(for Flight simulator - 9 9 9 9 9

text: -C

text: reconfiguration modes, manual reversion and associated handling (most significant

text: degradation which is probable)) (7) Approach and landing with trim malfunctions (a) longitudinal trim malfunction 9 9 9 9

text: (b) lateral-directional trim malfunction 9 9 9 9

text: (8) Approach and landing with standby (minimum) electrical/hydraulic power 9 9 9 9

text: (9) Approach and landing from circling conditions (circling approach) 9 9 9 9

text: (10) Approach and landing from visual traffic pattern 9 9 9 9

text: (11) Approach and landing from non-precision approach 9 9 9 9

text: (12) Approach and landing from precision approach 9 9 9 9

text: (13) Approach procedures with vertical guidance (APV), e.g., SBAS 9 9 9 9

text: (14) Other 9 9 9 9

text: NOTE: FSTD with visual systems, which permit completing a special approach procedure in accordance with applicable regulations, may be approved for that particular approach procedure.

text: JAR-FSTD A TSFS 2

text: Bilaga 1 0 0 9 :8 7

text: JA R- A Bila T FS C S

text: J No F

text: TD ga S

text: 1 20 A .1 t 09:87

text: j MISSED APPROACH

text: 9 9 9 9 9 9 9 9 9 9 0 (1) All engines 30 (c

text: (2) One or more engine(s) out 9 9 9 9 9 9 9(2) 9 9 9(2) on (3) With flight control system failures, reconfiguration modes, manual reversion and for flight 9 9 9 9 9 9 9 tinued) simulator - associated handling

text: k SURFACE OPERATIONS (POST LANDING)

text: 2- (1) Landing roll and taxi

text: C-

text: (a) Spoiler operation 9 9 9 9 9 9 9 9

text: (b) Reverse thrust operation 9 9 9 9 9 9 9 9

text: (c) Directional control and ground handling, both with and without reverse thrust 9 9 9 9 9 9

text: (d) Reduction of rudder effectiveness with increased reverse thrust (rear pod-mounted 9 9 9 9 engines) (e) Brake and anti-skid operation with dry, wet, and icy condition 9 9 9 9

text: (f) Brake operation, to include auto-braking system where applicable 9 9 9 9 9 9 9 9 9

text: (g) Other 9 9 9 9 9 9

text: l ANY FLIGHT PHASE

text: (1) Aeroplane and powerplant systems operation (a) Air conditioning and pressurisation (ECS) 9 9 9 9 9 9 9

text: 0 (b) De-icing/anti-icing 9 9 9 9 9 9 9 9

text: 0 9

text: (c) Auxiliary powerplant/auxiliary power unit (APU) 9 9 9 9 9 9

text: -1 1-

text: 01 (d) Communications 9 9 9 9 9 9 9 9 9 9

text: (e) Electrical 9 9 9 9 9 9 9 9 9 9

text: (f) Fire and smoke detection and suppression 9 9 9 9 9 9 9

text: SEC

text: T ION

text: 2 A SEC

text: 009 C

text: J No

text: -1 T 1- .1 IO

text: 01 2 t N

text: o J 2 TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT BITD A R-FS

text: A B C D 1 2 I II MCC

text: TD A. (g) Flight controls (primary and secondary) 9 9 9 9 9 9 9 (h) Fuel and oil, hydraulic and pneumatic 9 9 9 9 9 9 9 9 9 9 0 30 (c (i) Landing gear 9 9 9 9 9 9 9 9 9 9 o (j) Oxygen 9 9 9 9 9 9 9 ntinued (k) Powerplant 9 9 9 9 9 9 9 9 9 9 ) (l) Airborne radar 9 9 9 9 9 9 (m) Autopilot and Flight Director 9 9 9 9 9 9 9 (n) Collision avoidance systems. (e.g. GPWS,TCAS) 9 9 9 9 9 9 -C (o) Flight control computers including stability and control augmentation 9 9 9 9 9 9

text: (p) Flight display systems 9 9 9 9 9 9 (q) Flight management computers 9 9 9 9 9 9 (r) Head-up guidance, head-up displays 9 9 9 9 9 9 (s) Navigation systems 9 9 9 9 9 9 9 9 (t) Stall warning/avoidance 9 9 9 9 9 9 9 (u) Wind shear avoidance equipment 9 9 9 9 (v) Automatic landing aids 9 9 9 9

text: (2) Airborne procedures (a) Holding 9 9 9 9 9 9 9 9 9 9 (b) Air hazard avoidance. (traffic, weather) 9 9 9 9 (c) Wind shear 9 9 9 9

text: (3) Engine shutdown and parking (a) Engine and systems operation 9 9 9 9 9 9 9 9 9

text: (b) Parking brake operation 9 9 9 9 9 9 9 9 9

text: JAR-FSTD A TSFS 2

text: (4) Other as appropriate including effects of wind 9 9 9 9 9 9 9 9 9 9

text: Bilaga 1 0 0 9 :8 7

text: JA R- A Bila T FS C S

text: J No F

text: TD ga S

text: 1 20 A .1 t 09:87

text: o J A A B C D 1 2 I II MCC R- FS m VISUAL SYSTEM TD A.

text: (1) Functional test content requirements (Levels C and D) 0 Note—The following is the minimum airport model content requirement to satisfy visual 30 (c capability tests, and provides suitable visual cues to allow completion of all functions and subjective tests described in this appendix. FSTD operators are encouraged to use the model on content described below for the functions and subjective tests. If all of the elements cannot be tinued) found at a single real world airport, then additional real world airports may be used. The intent of this visual scene content requirement description is to identify that content required to aid the pilot in making appropriate, timely decisions.

text: C- (a) two parallel runways and one crossing runway displayed simultaneously; at least two 9 9 98 runways should be lit simultaneously (b) runway threshold elevations and locations shall be modelled to provide sufficient 9 9 correlation with aeroplane systems (e.g., HGS, GPS, altimeter); slopes in runways, taxiways, and ramp areas should not cause distracting or unrealistic effects, including pilot eye-point height variation

text: 2 0 0 9 -1 1- 01

text: SEC

text: T ION

text: 2 A SEC

text: 009 C

text: J No

text: -1 T 1- .1 IO

text: 01 2 t N

text: o J 2 A R-FS

text: A B C D 1 2 I II MCC TD A.

text: 0 (c) representative airport buildings, structures and lighting 9 9 30 (c

text: (d) one useable gate, set at the appropriate height, for those aeroplanes that typically 9 9 o operate from terminal gates ntinued (e) representative moving and static gate clutter (e.g., other aeroplanes, power carts, 9 9 tugs, fuel trucks, additional gates) ) (f) representative gate/apron markings (e.g., hazard markings, lead-in lines, gate 9 9 numbering) and lighting (g) representative runway markings, lighting, and signage, including a wind sock that 9 9 gives appropriate wind cues (h) representative taxiway markings, lighting, and signage necessary for position 9 9

text: -C

text: identification, and to taxi from parking to a designated runway and return to parking;

text: representative, visible taxi route signage shall be provided; a low visibility taxi route (e.g. Surface Movement Guidance Control System, follow-me truck, daylight taxi lights) should also be demonstrated (i) representative moving and static ground traffic (e.g., vehicular and aeroplane) 9 9

text: (j) representative depiction of terrain and obstacles within 25 NM of the reference airport 9 9

text: (k) representative depiction of significant and identifiable natural and cultural features 9 9 within 25 NM of the reference airport

text: Note—This refers to natural and cultural features that are typically used for pilot orientation in flight. Outlying airports not intended for landing need only provide a reasonable facsimile of runway orientation.

text: (l) representative moving airborne traffic 9 9

text: (m) appropriate approach lighting systems and airfield lighting for a VFR circuit and 9 9 landing, non-precision approaches and landings, and Category I, II and III precision approaches and landings (n) representative gate docking aids or a marshaller 9 9

text: JAR-FSTD A TSFS 2

text: Bilaga 1 0 0 9 :8 7

text: JA R- A Bila T FS C S

text: J No F

text: TD ga S

text: 1 20 A .1 t 09:87

text: (2) Functional test content requirements (Levels A and B) 0 30 (c Note—The following is the minimum airport model content requirement to satisfy visual capability tests, and provides suitable visual cues to allow completion of all functions and on subjective tests described in this appendix. FSTD operators are encouraged to use the tinued) model content described below for the functions and subjective tests.

text: (a) representative airport runways and taxiways 9 9 9 9 9

text: -C (b) runway definition 9 9 9 9 9

text: (c) runway surface and markings 9 9 9 9 9

text: (d) lighting for the runway in use including runway edge and centreline lighting, visual 9 9 9 9 9 approach aids and approach lighting of appropriate colours (e) representative taxiway lights 9 9

text: (3) Visual scene management

text: (a) Runway and approach lighting intensity for any approach should be set at an intensity 9 9 9 9 representative of that used in training for the visibility set; all visual scene light points should fade into view appropriately (b) The directionality of strobe lights, approach lights, runway edge lights, visual landing 9 9 9 9 aids, runway centre line lights, threshold lights, and touchdown zone lights on the runway of intended landing should be realistically replicated

text: 2 0 0 9 -1 1- 01

text: SEC

text: T ION

text: 2 A SEC

text: 009 C

text: J No

text: -1 T 1- .1 IO

text: 01 2-C t N

text: o J 2 A R-FS

text: TD A.

text: A B C D 1 2 I II MCC

text: 0 30 (c (4) Visual feature recognition o Note—Tests 4(a) through 4(g) below contain the minimum distances at which runway ntinued features should be visible. Distances are measured from runway threshold to an aeroplane aligned with the runway on an extended 3-degree glide slope in suitable simulated ) meteorological conditions. For circling approaches, all tests below apply both to the runway used for the initial approach and to the runway of intended landing

text: (a) Runway definition, strobe lights, approach lights, and runway edge white lights from 8 9 9 9 9 9 9 km

text: 0 (5 sm) of the runway threshold

text: (b) Visual Approach Aids lights from 8 km (5 sm) of the runway threshold 9 9

text: (c) Visual Approach Aids lights from 5 km (3 sm) of the runway threshold 9 9 9 9

text: (d) Runway centreline lights and taxiway definition from 5 km (3 sm) 9 9 9 9 9 9

text: (e) Threshold lights and touchdown zone lights from 3 km (2 sm) 9 9 9 9 9 9

text: (f) Runway markings within range of landing lights for night scenes as required by the 9 9 9 9 9 9 surface resolution test on day scenes (g) For circling approaches, the runway of intended landing and associated lighting 9 9 9 9 should fade into view in a non-distracting manner

text: JAR-FSTD A TSFS 2

text: Bilaga 1 0 0 9 :8 7

text: JA R- A Bila T FS C S

text: J No F

text: TD ga S

text: 1 20 A .1 t 09:87

text: (5) Airport model content 0 30 (c Minimum of three specific airport scenes as defined below; (a) terminal approach area on A accurate portrayal of airport features is to be consistent with published data used 9 9 tinued)

text: for aeroplane operations B all depicted lights should be checked for appropriate colours, directionality, 9 9 2 behaviour and spacing (e.g., obstruction lights, edge lights, centre line, -C touchdown zone, VASI, PAPI, REIL and strobes) -10 C depicted airport lighting should be selectable via controls at the instructor station 9 9 2 as required for aeroplane operation D selectable airport visual scene capability at each model demonstrated for: 9 9 (i) night (ii) twilight (iii) day

text: E (i) ramps and terminal buildings which correspond to an operator’s LOFT and LOS 9 9 scenarios (ii) terrain- appropriate terrain, geographic and cultural features (iii) dynamic effects - the capability to present multiple ground and air hazards such 9 9 as another aeroplane crossing the active runway or converging airborne traffic; 9 9 hazards should be selectable via controls at the instructor station

text: 0 (iv) illusions - operational visual scenes which portray representative physical 9 9 0 relationships known to cause landing illusions, for example short runways,

text: -1 landing approaches over water, uphill or downhill runways, rising terrain on the 1- approach path and unique topographic features

text: Note - Illusions may be demonstrated at a generic airport or specific aerodrome.

text: SEC

text: T ION

text: 2 A SEC

text: 009 C

text: J No

text: -1 T 1- .1 IO

text: 01 2-C t N

text: A B C D 1 2 I II MCC

text: TD A.

text: (6) Correlation with aeroplane and associated equipment 0 30 (c (a) visual system compatibility with aerodynamic programming 9 9 9 9 9 9 (b) visual cues to assess sink rate and depth perception during landings. Visual cueing o 9 9 9 9 9 sufficient to support changes in approach path by using runway perspective. ntinued

text: Changes in visual cues during take-off and approach should not distract the pilot (c) accurate portrayal of environment relating to flight simulator attitudes 9 9 9 9 9 9 )

text: (d) the visual scene should correlate with integrated aeroplane systems, where fitted 9 9 (e.g. terrain, traffic and weather avoidance systems and Head-up Guidance System (HGS))

text: -1 (e) representative visual effects for each visible, ownship, aeroplane external light 0 9 9 9

text: (f) the effect of rain removal devices should be provided 9 9

text: (7) Scene quality (a) surfaces and textural cues should be free from apparent quantization (aliasing) 9 9 (b) system capable of portraying full colour realistic textural cues (c) the system light points should be free from distracting jitter, smearing or streaking 9 9

text: 9 9 9 9

text: JAR-FSTD A TSFS 2

text: Bilaga 1 0 0 9 :8 7

text: JA R- A Bila T FS C S

text: J No F

text: TD ga S

text: 1 20 A .1 t 09:87

text: o J TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT BITD A R- A B C D 1 2 I II MCC FS TD A. (d) demonstration of occulting through each channel of the system in an operational 9 9 scene 0 (e) demonstration of a minimum of ten levels of occulting through each channel of the 9 9 30 (c system in an operational scene (f) system capable of providing focus effects that simulate rain and light point 9 9 on perspective growth tinued) (g) system capable of six discrete light step controls (0-5) 9 9 9 9

text: (8) Environmental effects

text: 2 (a) the displayed scene should correspond to the appropriate surface contaminants and 9 9

text: -C

text: include runway lighting reflections for wet, partially obscured lights for snow, or

text: suitable alternative effects 4 (b) Special weather representations which include the sound, motion and visual effects 9 9 of light, medium and heavy precipitation near a thunderstorm on take-off, approach and landings at and below an altitude of 600 m (2 000 ft) above the aerodrome surface and within a radius of 16 km (10 sm) from the aerodrome (c) in - cloud effects such as variable cloud density, speed cues and ambient changes 9 9 should be provided (d) the effect of multiple cloud layers representing few, scattered, broken and overcast 9 9 conditions giving partial or complete obstruction of the ground scene (e) gradual break-out to ambient visibility/RVR, defined as up to 10% of the respective 9 9 cloud base or top, 20 ft ≤ transition layer ≤200 ft; cloud effects should be checked at and below a height of 600 m (2 000 ft) above the aerodrome and within a radius of 16 km (10 sm) from the airport

text: 2 0 0 9 -1 1- 01

text: SEC

text: T ION

text: 2 A SEC

text: 009 C

text: J No

text: -1 T 1- .1 IO

text: 01 2-C t N

text: o J 2 A R-FS

text: A B C D 1 2 I II MCC TD A.

text: (f) visibility and RVR measured in terms of distance. Visibility/RVR should be checked at 9 9 9 9 0 and below a height of 600 m (2 000 ft) above the aerodrome and within a radius of 16 30 (c km (10 sm.) from the airport (g) patchy fog giving the effect of variable RVR Note – Patchy fog is sometimes referred 9 9 o to as patchy RVR. nti nued (h) effects of fog on aerodrome lighting such as halos and defocus 9 9

text: ) (i) effect of ownship lighting in reduced visibility, such as reflected glare, to include 9 9 landing lights, strobes, and beacons (j) wind cues to provide the effect of blowing snow or sand across a dry runway or 9 9 taxiway should be selectable from the instructor station

text: (9) Instructor controls of:

text: 0 (a) Environmental effects, e.g. cloud base, cloud effects, cloud density, visibility in 9 9 9 9 9 9

text: kilometres/statute miles and RVR in metres/feet (b) Airport/aerodrome selection 9 9 9 9 9 9 9

text: (c) Airport/aerodrome lighting including variable intensity where appropriate 9 9 9 9 9(4) 9(4)

text: (d) Dynamic effects including ground and flight traffic 9 9 9 9

text: (10) Night visual scene capability 9 9 9 9

text: (11) Twilight visual scene capability 9 9

text: (12) Daylight visual scene capability 9 9

text: JAR-FSTD A TSFS 2

text: Bilaga 1 0 0 9 :8 7

text: JA R- A Bila T FS C S

text: J No F

text: TD ga S

text: 1 20 A .1 t 09:87

text: o J A A B C D 1 2 I II MCC R- FS n MOTION EFFECTS TD A.

text: 0 30 (c The following specific motion effects are required to indicate the threshold at which a flight crewmember should recognise an event or situation. Where applicable below, flight simulator on pitch, side loading and directional control characteristics should be representative of the aeroplane as a function of aeroplane type: tinued)

text: (1) Effects of runway rumble, oleo deflections, ground speed, uneven runway, runway * 9 9 9 centreline lights and taxiway characteristics 2 (a) After the aeroplane has been pre-set to the takeoff position and then released, taxi at -C various speeds, first with a smooth runway, and note the general characteristics of -10 the simulated runway rumble effects of oleo deflections. Next repeat the manoeuvre

text: 6 with a runway roughness of 50%, then finally with maximum roughness. The associated motion vibrations should be affected by ground speed and runway roughness. If time permits, different gross weights can also be selected as this may also affect the associated vibrations depending on aeroplane type. The associated motion effects for the above tests should also include an assessment of the effects of centreline lights, surface discontinuities of uneven runways, and various taxiway characteristics

text: (2) Buffets on the ground due to spoiler/speedbrake extension and thrust * 9 9 9 (a) Perform a normal landing and use ground spoilers and reverse thrust – either individually or in combination with each other – to decelerate the simulated aeroplane. Do not use wheel braking so that only the buffet due to the ground spoilers and thrust reversers is felt.

text: 2 0 0 9

text: -1 (3) Bumps associated with the landing gear * 9 9 9

text: (a) Perform a normal take-off paying special attention to the bumps that could be

text: perceptible due to maximum oleo extension after lift-off. When the landing gear is extended or retracted, motion bumps could be felt when the gear locks into position

text: SEC

text: T ION

text: 2 A SEC

text: 009 C

text: J No

text: -1 T 1- .1 IO

text: 01 2-C t N

text: A B C D 1 2 I II MCC

text: TD A. (4) Buffet during extension and retraction of landing gear * 9 9 9 (a) Operate the landing gear. Check that the motion cues of the buffet experienced are 0 reasonably representative of the actual aeroplane 30 (c

text: o (5) Buffet in the air due to flap and spoiler/speedbrake extension and approach to stall buffet * 9 9 9 ntinued

text: (a) First perform an approach and extend the flaps and slats, especially with airspeeds ) deliberately in excess of the normal approach speeds. In cruise configuration verify the buffets associated with the spoiler/speedbrake extension. The above effects could also be verified with different combinations of speedbrake/flap/gear settings to assess the interaction effects

text: 0 (6) Approach to stall buffet 9 9 9 7 * (a) Conduct an approach-to-stall with engines at idle and a deceleration of 1 knot/second. Check that the motion cues of the buffet, including the level of buffet increase with decreasing speed, are reasonably representative of the actual aeroplane

text: (7) Touchdown cues for main and nose gear * 9 9 9 (a) Fly several normal approaches with various rates of descent. Check that the motion cues of the touchdown bump for each descent rate are reasonably representative of the actual aeroplane

text: (8) Nose wheel scuffing * 9 9 9 (a) Taxi the simulated aeroplane at various ground speeds and manipulate the nose wheel steering to cause yaw rates to develop which cause the nose wheel to vibrate against the ground (“scuffing”). Evaluate the speed/nose wheel combination needed to produce scuffing and check that the resultant vibrations are reasonably representative of the actual aeroplane

text: JAR-FSTD A TSFS 2

text: Bilaga 1 0 0 9 :8 7

text: JA R- A Bila T FS C S

text: J No F

text: TD ga S

text: 1 20 A .1 t 09:87

text: o J A A B C D 1 2 I II MCC R- FS (9) Thrust effect with brakes set * 9 9 9 TD A.

text: (a) With the simulated aeroplane set with the brakes on at the take-off point, increase the engine power until buffet is experienced and evaluate its characteristics. This 0 30 (c effect is most discernible with wing mounted engines. Confirm that the buffet increases appropriately with increasing engine thrust on tinued)

text: (10) Mach and manoeuvre buffet * 9 9 9 2 (a) With the simulated aeroplane trimmed in 1 g flight while at high altitude, increase the -C engine power such that the Mach number exceeds the documented value at which -10 Mach buffet is experienced. Check that the buffet begins at the same Mach number

text: 8 as it does in the aeroplane (for the same configuration) and that buffet levels are a reasonable representation of the actual aeroplane. In the case of some aeroplanes, manoeuvre buffet could also be verified for the same effects. Manoeuvre buffet can occur during turning flight at conditions greater than 1 g, particularly at higher altitudes

text: (11) Tyre failure dynamics 9 9 (a) Dependent on aeroplane type, a single tire failure may not necessarily be noticed by the pilot and therefore there should not be any special motion effect. There may possibly be some sound and/or vibration associated with the actual tire losing pressure. With a multiple tire failure selected on the same side the pilot may notice some yawing which should require the use of the rudder to maintain control of the 2 aeroplane

text: 0 0 9

text: -1 (12) Engine malfunction and engine damage 1- * 9 9 9 01 (a) The characteristics of an engine malfunction as stipulated in the malfunction definition document for the particular FSTD should describe the special motion effects felt by the pilot. The associated engine instruments should also vary according to the nature of the malfunction

text: SEC

text: T ION

text: 2 A SEC

text: 009 C

text: J No

text: -1 T 1- .1 IO

text: 01 2-C t N

text: A B C D 1 2 I II MCC

text: TD A. (13) Tail strikes and pod strikes * 9 9 9 (a) Tail-strikes can be checked by over-rotation of the aeroplane at a speed below Vr 0 whilst performing a takeoff. The effects can also be verified during a landing. The 30 (c motion effect should be felt as a noticeable bump. If the tail strike affects the aeroplane’s angular rates, the cueing provided by the motion system should have an o associated effect. ntinued

text: (b) Excessive banking of the aeroplane during its take-off/landing roll can cause a pod 9 9 9 * strike. The motion effect should be felt as a noticeable bump. If the pod strike affects ) the aeroplane’s angular rates, the cueing provided by the motion system should have an associated effect

text: o SOUND SYSTEM

text: (1) The following checks should be performed during a normal flight profile with motion

text: 0 (a) precipitation 9 9 9

text: (b) rain removal equipment 9 9

text: (c) significant aeroplane noises perceptible to the pilot during normal operations, such as 9 9 9 9 9 9 engine, flaps, gear, spoiler extension/retraction, thrust reverser to a comparable level of that found in the aeroplane (d) abnormal operations for which there are associated sound cues including, but not 9 9 limited to, engine malfunctions, landing gear/tire malfunctions, tail and engine pod strike and pressurization malfunction (e) sound of a crash when the flight simulator is landed in excess of limitations 9 9

text: (f) significant engine/propeller noise perceptible to pilot during normal operations 9 9 9 9

text: JAR-FSTD A TSFS 2

text: Bilaga 1 0 0 9 :8 7

text: JA R- A Bila T FS C S

text: J No F

text: TD ga S

text: 1 20 A .1 t 09:87

text: p SPECIAL EFFECTS 0 30 (c (1) Braking Dynamics on (a) representative brake failure dynamics (including antiskid) and decreased brake 9 9 efficiency due to high brake temperatures based on aeroplane related data. These tinued)

text: representations should be realistic enough to cause pilot identification of the problem and implementation of appropriate procedures. FSTD pitch, side-loading and directional control characteristics should be representative of the aeroplane

text: 2 -C

text: -11 (2) Effects of Airframe and Engine Icing 9 9 0 (a) See Appendix 1 to JAR FSTD A.030 par 2.1(t). NOTE- For Level ‘A’, an asterisk (*) denotes that the appropriate effect is required to be present. NOTE -It is accepted that tests will only apply to FTD Level 1 if that system and flight condition is simulated. It is intended that the tests listed below should be conducted in automatic flight. Where automatic flight is not possible and pilot manual handling is required, the FTD shall be at least controllable to permit the conduct of the flight.

text: Notes General: Motion and buffet cues will only be applicable to FSTD equipped with an appropriate motion system (1) Takeoff characteristics sufficient to commence the airborne exercises (2) For FNPT 1 and BITD only if multi-engine (3) Only trim change required

text: 0 (4) For FNPT, variable intensity airport lighting not required.

text: 0 9 -1 1- 01

text: SEC

text: T ION

text: Bilaga 1

text: Appendix 1 to ACJ No. 1 to JAR-FSTD A.030 (interpretative material) Validation Test Tolerances

text: 1 Background 1.1 The tolerances listed in ACJ No. 1 of JAR-FSTD A.030 are designed to be a measure of quality of match using flight-test data as a reference. 1.2 There are many reasons, however, why a particular test may not fully comply with the prescribed tolerances: (a) Flight-test is subject to many sources of potential error, e.g. instrumentation errors and atmospheric disturbance during data collection; (b) Data that exhibit rapid variation or noise may also be difficult to match; (c) Engineering simulator data and other calculated data may exhibit errors due to a variety of potential differences discussed below. 1.3 When applying tolerances to any test, good engineering judgement should be applied. Where a test clearly falls outside the prescribed tolerance(s) for no apparent reasons, then it should be judged to have failed. 1.4 The use of non-flight-test data as reference data was in the past quite small, and thus these tolerances were used for all tests. The inclusion of this type of data as a validation source has rapidly expanded, and will probably continue to expand. 1.5 When engineering simulator data are used, the basis for their use is that the reference data are produced using the same simulation models as used in the equivalent flight training simulator; i.e., the two sets of results should be ‘essentially’ similar. The use of flight-test based tolerances may undermine the basis for using engineering simulator data, because an essential match is needed to demonstrate proper implementation of the data package. 1.6 There are, of course, reasons why the results from the two sources can be expected to differ: (a) Hardware (avionics units and flight controls); (b) Iteration rates; (c) Execution order; (d) Integration methods; (e) Processor architecture; (f) Digital drift: (1) Interpolation methods; (2) Data handling differences; (3) Auto-test trim tolerances, etc. 1.7 Any differences should, however, be small and the reasons for any differences, other than those listed above, should be clearly explained. 1.8 Historically, engineering simulation data were used only to demonstrate compliance with certain extra modelling features: (a) Flight test data could not reasonably be made available; (b) Data from engineering simulations made up only a small portion of the overall validation data set; (c) Key areas were validated against flight-test data. 1.9 The current rapid increase in the use and projected use of engineering simulation data is an important issue because: (a) Flight-test data are often not available due to sound technical reasons; (b) Alternative technical solutions are being advanced; (c) Cost is an ever-present issue.

text: 2009-11-01 2-C-111 JAR-FSTD A

text: Bilaga 1

text: Appendix 1 to ACJ No. 1 to JAR-FSTD A.030 (continued)

text: 1.10 Guidelines are therefore needed for the application of tolerances to engineering-simulator-generated validation data. 2 Non-Flight-Test Tolerances 2.1 Where engineering simulator data or other non-flight-test data are used as an allowable form of reference validation data for the objective tests listed in the table of validation tests, the match obtained between the reference data and the FSTD results should be very close. It is not possible to define a precise set of tolerances as the reasons for other than an exact match will vary depending upon a number of factors discussed in paragraph one of this appendix. 2.2 As guidance, unless a rationale justifies a significant variation between the reference data and the FSTD results, 20% of the corresponding ‘flight-test’ tolerances would be appropriate. 2.3 For this guideline (20% of flight-test tolerances) to be applicable, the data provider should supply a well-documented mathematical model and testing procedure that enables an exact replication of their engineering simulation results.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD A 2-C-112 2009-11-01

text: Bilaga 1

text: Appendix 2 to ACJ No.1 to JAR-FSTD A.030 Validation Data Roadmap

text: 1 General

text: 1.1 Aeroplane manufacturers or other sources of data should supply a validation data roadmap (VDR) document as part of the data package. A VDR document contains guidance material from the aeroplane validation data supplier recommending the best possible sources of data to be used as validation data in the QTG. A VDR is of special value in the cases of requests for ‘interim’ qualification, requests for qualification of simulations of aeroplanes certificated prior to 1992, and for qualification of alternate engine or avionics fits (see Appendices 3 and 4 of this ACJ). A VDR should be submitted to the authority as early as possible in the planning stages for any FSTD planned for qualification to the standards contained herein. The respective State civil aviation authority is the final authority to approve the data to be used as validation material for the QTG. The United States Federal Aviation Administration’s National Simulator Program Manager and the Joint Aviation Authorities’ FSTD Steering Group have committed to maintain a list of agreed VDR’s. 1.2 The validation data roadmap should clearly identify (in matrix format) sources of data for all required tests. It should also provide guidance regarding the validity of these data for a specific engine type and thrust rating configuration and the revision levels of all avionics affecting aeroplane handling qualities and performance. The document should include rationale or explanation in cases where data or parameters are missing, engineering simulation data are to be used, flight test methods require explanation, etc., together with a brief narrative describing the cause/effect of any deviation from data requirements. Additionally, the document should make reference to other appropriate sources of validation data (e.g., sound and vibration data documents). 1.3 Table 1, below, depicts a generic roadmap matrix identifying sources of validation data for an abbreviated list of tests. A complete matrix should address all test conditions. 1.4 Additionally, two examples of ‘rationale pages’ are presented in Appendix F of the IATA Flight Simulator Design & Performance Data Requirements document. These illustrate the type of aeroplane and avionics configuration information and descriptive engineering rationale used to describe data anomalies, provide alternative data, or provide an acceptable basis to the authority for obtaining deviations from QTG validation requirements.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-113 JAR-FSTD A

text: Bilaga 1

text: Appendix 2 to ACJ No. 1 to JAR-FSTD A.030 (continued)

text: . ry a ss e ec n

text: be ay

text: s m

text: mn lu

text: p

text: co a re m

text: o d

text: m

text: ta Roa da ta

text: n tio

text: n Da

text: lida io

text: a at

text: v

text: as lid

text: d

text: : Va

text: use re

text: a ble 1

text: e)

text: Ta

text: lin . se

text: ba ition d d n n a o e c st tiv e va t ri ch a de ., r e .g fo (e ed e ib yp t scr ft a de cr e ir a ll b e a n h o s n a de th mo re A o C m 1 C 2 If * *

text: JAR-FSTD A 2-C-114 2009-11-01

text: Bilaga 1

text: Appendix 3 to ACJ No.1 to JAR-FSTD 1A.030 Data Requirements for Alternate Engines - Approval Guidelines (Applicable to FFS only)

text: 1 Background 1.1 For a new aeroplane type, the majority of flight validation data are collected on the first aeroplane configuration with a ‘baseline’ engine type. These data are then used to validate all FSTDs representing that aeroplane type.

text: 1.2 In the case of FSTDs representing an aeroplane with engines of a different type than the baseline, or a different thrust rating than that of previously validated configurations, additional flight test validation data may be needed. 1.3 When a FSTD with additional and/or alternate engine fits is to be qualified, the QTG should contain tests against flight test validation data for selected cases where engine differences are expected to be significant.

text: 2 Approval Guidelines for validating alternate Engine Fits 2.1 The following guidelines apply to FSTDs representing aeroplanes with an alternate engine fit; or, with more than one engine type or thrust rating. 2.2 Validation tests can be segmented into those that are dependent on engine type or thrust rating and those that are not.

text: 2.3 For tests that are independent of engine type or thrust rating, the QTG can be based on validation data from any engine fit. Tests in this category should be clearly identified. 2.4 For tests which are affected by engine type, the QTG should contain selected engine-specific flight test data sufficient to validate that particular aeroplane-engine configuration. These effects may be due to engine dynamic characteristics, thrust levels and/or engine-related aeroplane configuration changes. This category is primarily characterised by differences between different engine manufacturers’ products, but also includes differences due to significant engine design changes from a previously flight-validated configuration within a single engine type. See Table 1 below for a list of acceptable tests. 2.5 For those cases where the engine type is the same, but the thrust rating exceeds that of a previously flight-validated configuration by five percent (5%) or more, or is significantly less than the lowest previously validated rating (a decrease of fifteen percent (15%) or more), the QTG should contain selected enginespecific flight test data sufficient to validate the alternate thrust level. See Table 1 below for a list of acceptable tests. However, if an aeroplane manufacturer, qualified as a validation data supplier under the guidelines of ACJ nos1 and 2 to JAR-FSTD A.030(c)(1), shows that a thrust increase greater than 5% will not significantly change the aeroplane’s flight characteristics, and then flight validation data are not needed. 2.6 No additional flight test data are required for thrust ratings which are not significantly different from that of the baseline or other applicable flight-validated engine-airframe configuration (i.e., less than 5% above or 15% below), except as noted in paragraphs 2.7 and 2.8, below. As an example, for a configuration validated with 50,000 pound-thrust-rated engines, no additional flight validation data are required for ratings between 42,500 and 52,500 lbs. If multiple engine ratings are tested concurrently, only test data for the highest rating are needed. 2.7 Throttle calibration data (i.e., commanded power setting parameter versus throttle position) should be provided to validate all alternate engine types, and engine thrust ratings which are higher or lower than a previously validated engine. Data from a test aeroplane or engineering test bench are acceptable, provided the correct engine controller (both hardware and software) is used. 2.8 The validation data described in paragraphs 2.4 through 2.7 above should be based on flight test data, except as noted in those paragraphs, or where other data are specifically allowed within ACJ No. 1 to JAR-FSTD 1A.030(c)(1). However, if certification of the flight characteristics of the aeroplane with a new thrust rating (regardless of percentage change) does require certification flight testing with a comprehensive stability and control flight instrumentation package, then the conditions in table 1 below should be obtained from flight testing and presented in the QTG. Conversely, flight test data other than throttle calibration as described above are not required if the new thrust rating is certified on the aeroplane without need for a comprehensive stability and control flight instrumentation package.

text: 2009-11-01 2-C-115 JAR-FSTD A

text: Bilaga 1

text: Appendix 2 to ACJ No. 1 to JAR-FSTD A.030 (continued) 2.9 As a supplement to the engine-specific flight tests of table 1 below and baseline engine-independent tests, additional engine-specific engineering validation data should be provided in the QTG, as appropriate, to facilitate running the entire QTG with the alternate engine configuration. The specific validation tests to be supported by engineering simulation data should be agreed with the authority well in advance of FSTD evaluation. 2.10 A matrix or ‘roadmap’ should be provided with the QTG indicating the appropriate validation data source for each test (see Appendix 2 of this ACJ). The following flight test conditions (one per test number) are appropriate and should be sufficient to validate implementation of alternate engine fits in a FSTD.

text: TEST TEST DESCRIPTION ALTERNATE ALTERNATE

text: NUMBER ENGINE TYPE THRUST RATING

text: 1.b.1, 4 Normal take-off/ground acceleration time & distance X X 1.b.2 Vmcg, if performed for aeroplane certification X X 1.b.5 Engine-out take-off Either test may X be performed. 1.b.8 Dynamic engine failure after take-off 1.b.7 Rejected take-off if performed for aeroplane certification X 1.d.3 Cruise performance X 1.f.1, 2 Engine acceleration and deceleration X X 2.a.8 Throttle calibration X X 2.c.1 Power change dynamics (acceleration) X X 2.d.1 Vmca if performed for aeroplane certification X X 2.d.5 Engine inoperative trim X X 2.e.1 Normal landing X Should be provided for all changes in engine type or thrust rating (see paragraph 2.7, above). See paragraphs 2.5 through 2.8 above for a definition of applicable thrust ratings.

text: Note: this table does not take in to consideration additional configuration settings and control laws.

text: Table 1: Alternate Engine Validation Flight Tests

text: JAR-FSTD A 2-C-116 2009-11-01

text: Bilaga 1

text: Appendix 4 to ACJ No.1 to JAR-FSTD A.030 Data Requirements for Alternate Avionics (Flight-related Computers & Controllers) – Approval Guidelines

text: 1. Background 1.1 For a new aeroplane type, the majority of flight validation data are collected on the first aeroplane configuration with a ‘baseline’ flight-related avionics ship-set (see paragraph 2.2, below). These data are then used to validate all FSTDs representing that aeroplane type. 1.2 In the case of FSTDs representing an aeroplane with avionics of a different hardware design than the baseline, or a different software revision than that of previously validated configurations, additional validation data may be required. 1.3 When a FSTD with additional and/or alternate avionics configurations is to be qualified, the QTG should contain tests against validation data for selected cases where avionics differences are expected to be significant. 2. Approval Guidelines for Validating Alternate Avionics 2.1 The following guidelines apply to FSTDs representing aeroplanes with a revised, or more than one, avionics configuration. 2.2 The aeroplane avionics can be segmented into those systems or components that can significantly affect the QTG results and those that cannot. The following avionics are examples of those for which hardware design changes or software revision updates may lead to significant differences relative to the baseline avionics configuration: Flight control computers and controllers for engines, autopilot, braking system, nose wheel steering system, high lift system, and landing gear system. Related avionics such as stall warning and augmentation systems should also be considered. The aeroplane manufacturer should identify for each validation test, which avionics systems, if changed, could affect test results. 2.3 The baseline validation data should be based on flight test data, except where other data are specifically allowed (see ACJ No.1 and 2 to JAR-FSTD A.030(c)(1)). 2.4 For changes to an avionics system or component that cannot affect MQTG validation test results, the QTG test can be based on validation data from the previously validated avionics configuration. 2.5 For changes to an avionics system or component that could affect an QTG validation test, but where that test is not affected by this particular change (e.g., the avionics change is a BITE update or a modification in a different flight phase), the QTG test can be based on validation data from the previously-validated avionics configuration. The aeroplane manufacturer should clearly state that this avionics change does not affect the test. 2.6 For an avionics change which affects some tests in the QTG, but where no new functionality is added and the impact of the avionics change on aeroplane response is a small, well-understood effect, the QTG may be based on validation data from the previously-validated avionics configuration. This should be supplemented with avionics-specific validation data from the aeroplane manufacturer’s engineering simulation, generated with the revised avionics configuration. In such cases, the aeroplane manufacturer should provide a rationale explaining the nature of the change and its effect on the aeroplane response. 2.7 For an avionics change that significantly affects some tests in the QTG, especially where new functionality is added, the QTG should be based on validation data from the previously-validated avionics configuration and supplemental avionics-specific flight test data sufficient to validate the alternate avionics revision. However, additional flight validation data may not be needed if the avionics changes were certified without need for testing with a comprehensive flight instrumentation package. The aeroplane manufacturer should co-ordinate FSTD data requirements in this situation, in advance, with the authority. 2.8 A matrix or ‘roadmap’ should be provided with the QTG indicating the appropriate validation data source for each test (see Appendix 2 of ACJ No 1 to JAR-FSTD 1A.030).

text: 2009-11-01 2-C-117 JAR-FSTD A

text: Bilaga 1

text: Appendix 5 to ACJ No.1 to JAR-FSTD A.030 Transport Delay And Latency Testing Methods

text: 1. General 1.1 The purpose of this appendix is to demonstrate how to determine the introduced transport delay through the FSTD system such that it does not exceed a specific time delay. That is, measure the transport delay from control inputs through the interface, through each of the host computer modules and back through the interface to motion, flight instrument and visual systems, and show that it is no more than the tolerances required in the validation test tables. (For Latency testing methods see para 2). 1.2 Four specific examples of transport delay are described as follows: (a) simulation of classic non-computer controlled aircraft; (b) simulation of computer controlled aircraft using real aircraft equipment;

text: (c) simulation of computer controlled aircraft using software emulation of aircraft equipment; (d) simulation using software avionics or re-hosted instruments. 1.3 Figure 1 illustrates the total transport delay for a non-computer-controlled aircraft, or the classic transport delay test. 1.4 Since there are no aircraft-induced delays for this case, the total transport delay is equivalent to the introduced delay.

text: 1.5 Figure 2 illustrates the transport delay testing method employed on a FSTD that uses the real aircraft controller system. 1.6 To obtain the induced transport delay for the motion, instrument and visual signal, the delay induced by the aircraft controller should be subtracted from the total transport delay. This difference represents the introduced delay.

text: 1.7 Introduced transport delay is measured from the cockpit control input to the reaction of the instruments, and motion and visual systems (See figure 1). 1.8 Alternatively, the control input may be introduced after the aircraft controller system and the introduced transport delay measured directly from the control input to the reaction of the instruments, and FSTD motion and visual systems (See figure 2). 1.9 Figure 3 illustrates the transport delay testing method employed on a FSTD that uses a software emulated aircraft controller system. 1.10 By using the simulated aircraft controller system architecture for the pitch, roll and yaw axes, it is not possible to measure simply the introduced transport delay. Therefore, the signal should be measured directly from the pilot controller. Since in the real aircraft the controller system has an inherent delay as provided by the aircraft manufacturer, the FSTD manufacturer should measure the total transport delay and subtract the inherent delay of the actual aircraft components and ensure that the introduced delay does not exceed the tolerances required in the validation test tables.

text: 1.11 Special measurements for instrument signals for FSTDs using a real aircraft instrument display system, versus a simulated or re-hosted display. For the case of the flight instrument systems, the total transport delay should be measured, and the inherent delay of the actual aircraft components subtracted to ensure that the introduced delay does not exceed the tolerances required in the validation test tables. 1.11.1 Figure 4A illustrates the transport delay procedure without the simulation of aircraft displays. The introduced delay consists of the delay between the control movement and the instrument change on the data bus. 1.11.2 Figure 4B illustrates the modified testing method required to correctly measure introduced delay due to software avionics or re-hosted instruments. The total simulated instrument transport delay is measured and the aircraft delay should be subtracted from this total. This difference represents the introduced delay and shall not exceed the tolerances required in the validation test tables. The inherent delay of the aircraft between the data bus and the displays is indicated as XX msec (See figure 4A). The display manufacturer shall provide this delay time.

text: JAR-FSTD A 2-C-118 2009-11-01

text: Bilaga 1

text: Appendix 5 to ACJ No. 1 to JAR-FSTD A.030 (continued)

text: 1.12 Recorded signals. The signals recorded to conduct the transport delay calculations should be

text: explained on a schematic block diagram. The FSTD manufacturer should also provide an explanation of why

text: each signal was selected and how they relate to the above descriptions.

text: 1.13 Interpretation of results. It is normal that FSTD results vary over time from test to test. This can easily

text: be explained by a simple factor called ‘sampling uncertainty.’ All FSTDs run at a specific rate where all

text: modules are executed sequentially in the host computer. The flight controls input can occur at any time in the

text: iteration, but these data will not be processed before the start of the new iteration. For a FSTD running at 60

text: Hz a worst-case difference of 16·67 msec can be expected. Moreover, in some conditions, the host computer

text: and the visual system do not run at the same iteration rate, therefore the output of the host computer to the

text: visual will not always be synchronised.

text: 1.14 The transport delay test should account for the worst case mode of operation of the visual system.

text: The tolerance is as required in the validation test tables and motion response shall occur before the end of the

text: first video scan containing new information.

text: y Instruments

text: HOST reaction Flight Simulator

text: y Motion controls flight control y Instruments

text: reaction

text: input interface y Motion y Visual y Visual

text: reaction

text: Simulator introduced transport delay

text: Total simulator transport delay

text: Figure 1: Transport Delay for simulation of classic non-computer controlled aircraft

text: HOST

text: Simulator y Instruments

text: Flight Aeroplane flight reaction

text: controls controller y Instruments control y Motion reaction input system y Motion interface y Visual reaction y Visual

text: Aircraft delay Simulator introduced delay

text: Total simulator transport delay

text: Figure 2: Transport Delay for simulation of computer controlled aircraft using real aircraft equipment

text: y Instruments

text: HOST Simulator Simulated reaction Flight

text: flight aeroplane y Motion controls y Instruments

text: control controller reaction

text: input y Motion interface system y Visual y Visual

text: reaction

text: Total simulator transport delay

text: Figure 3: Transport Delay for simulation of computer controlled aircraft using software emulation of aircraft equipment

text: 2009-11-01 2-C-119 JAR-FSTD A

text: Bilaga 1

text: A: FSTD using real aircraft instruments

text: Aircraft hardware Flight control cabinet Host computer Data bus Control, Flight controls Flight, EFIS symbol signal Instruments, Interface generator Display unit Software

text: Delay less than "req’d value" Aircraft delay = XX msec

text: B: FSTD using software avionics or re-hosted instruments

text: Aircraft hardware Flight control cabinet Host computer Control, Software avionics Flight controls Flight, or signal Instruments, Interface Re-hosted instrument Display unit Software

text: Total transport delay (including aircraft delays)

text: Figure 4A and 4B: Transport delay for simulation of aircraft using real or re-hosted instrument drivers 2. Latency Test Methods

text: 2.1 The visual system, flight deck instruments and initial motion system response shall respond to abrupt pitch, roll and yaw inputs from the pilot's position within the specified time, but not before the time, when the aeroplane would respond under the same conditions. The objective of the test is to compare the recorded response of the FSTD to that of the actual aeroplane data in the take-off, cruise and landing configuration for rapid control inputs in all three rotational axes. The intent is to verify that the FSTD system response does not exceed the specified time (this does not include aeroplane response time as per the manufacturer’s data) and that the motion and visual cues relate to actual aeroplane responses. For aeroplane response, acceleration in the appropriate corresponding rotational axis is preferred. 2.2 Interpretation of results. It is normal that FSTD results vary over time from test to test. This can easily be explained by a simple factor called ‘sampling uncertainty.’ All FSTDs run at a specific rate where all modules are executed sequentially in the host computer. The flight controls input can occur at any time in the iteration, but these data will not be processed before the start of the new iteration. For a FSTD running at 60 Hz a worst-case difference of 16·67 msec can be expected. Moreover, in some conditions, the host computer and the visual system do not run at the same iteration rate, therefore the output of the host computer to the visual will not always be synchronised.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD A 2-C-120 2009-11-01

text: Bilaga 1

text: Appendix 6 to ACJ No.1 to JAR-FSTD A.030 Recurrent Evaluations - Validation Test Data Presentation

text: 1. Background 1.1 During the initial evaluation of a FSTD the MQTG is created. This is the master document, as amended, to which FSTD recurrent evaluation test results are compared. 1.2 The currently accepted method of presenting recurrent evaluation test results is to provide FSTD results over-plotted with reference data. Test results are carefully reviewed to determine if the test is within the specified tolerances. This can be a time consuming process, particularly when reference data exhibits rapid variations or an apparent anomaly requiring engineering judgement in the application of the tolerances. In these cases the solution is to compare the results to the MQTG. If the recurrent results are the same as those in the MQTG, the test is accepted. Both the FSTD operator and the authority are looking for any change in the FSTD performance since initial qualification. 2. Recurrent Evaluation Test Results Presentation 2.1 To promote a more efficient recurrent evaluation, FSTD operators are encouraged to over-plot recurrent validation test results with MQTG FSTD results recorded during the initial evaluation and as amended. Any change in a validation test will be readily apparent. In addition to plotting recurrent validation test and MQTG results, operators may elect to plot reference data as well. 2.2 There are no suggested tolerances between FSTD recurrent and MQTG validation test results. Investigation of any discrepancy between the MQTG and recurrent FSTD performance is left to the discretion of the FSTD operator and the authority. 2.3 Differences between the two sets of results, other than minor variations attributable to repeatability issues (see Appendix 1 of this ACJ), which cannot easily be explained, may require investigation. 2.4 The FSTD should still retain the capability to over-plot both automatic and manual validation test results with reference data.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-121 JAR-FSTD A

text: Bilaga 1

text: Appendix 7 to ACJ No.1 to JAR-FSTD A.030 Applicability of JAR-STD Amendments to FSTD Data Packages for Existing Aeroplanes

text: Except where specifically indicated otherwise within ACJ No 1 to JAR-FSTD A.030 Para 2.3, validation data for QTG objective tests are expected to be derived from aeroplane flight-testing. Ideally, data packages for all new FSTDs will fully comply with the current standards for qualifying FSTDs. For types of aeroplanes first entering into service after the publication of a new amendment of JAR-FSTD A, the provision of acceptable data to support the FSTD qualification process is a matter of planning and regulatory agreement (see ACJ No. 1 to JAR-FSTD A.045 New Aeroplane FSTD Qualification). For aeroplanes certificated prior to the release of the current amendment of JAR FSTD A, it may not always be possible to provide the required data for any new or revised objective test cases compared to the previous amendments. After certification, manufacturers do not normally keep flight test aeroplanes available with the required instrumentation to gather additional data. In the case of flight test data gathered by independent data providers, it is most unlikely that the test aeroplane will still be available. Notwithstanding the above discussion, except where other types of data are already acceptable (see, for example, ACJ Nos 1 and 2 to JAR-FSTD A.030(c)(1)), the preferred source of validation data is flight test. It is expected that best endeavours will be made by data suppliers to provide the required flight test data. If any flight test data exist (flown during the certification or any other flight test campaigns) that addresses the requirement, these test data should be provided. If any possibility exists to do this flight test during the occasion of a new flight test campaign, this should be done and provided in the data package at the next issue. Where these flight test data are genuinely not available, alternative sources of data may be acceptable using the following hierarchy of preferences: (a) as defined in Flight test at an alternate but near equivalent condition/configuration. (b) Data from an audited engineering simulation ACJ JAR-FSTD A.005 Para 1.1.e from an acceptable source (for example meets the guidelines laid out in ACJ No 1 to JAR-FSTD A.030(c)(1) Para 2), or as used for aircraft certification. (c) Aeroplane Performance Data as defined in ACJ JAR-FSTD A.005 Para 1.1.b or other approved published sources (e.g., Production flight test schedule) for the following tests: i. 1c1 Normal climb, all engines ii. 1c2 one engine inoperative 2nd segment climb iii. 1c3 one engine inoperative en-route climb iv. 1c4 one engine inoperative approach climb for aeroplanes with icing accountability v. 1e3 stopping distance, wheel brakes, wet runway, and test vi. 1e4 stopping distance, wheel brakes, icy runway (d) Where no other data is available then, in exceptional circumstances only, the following sources may be acceptable subject to a case-by-case review with the Authorities concerned taking into consideration the level of qualification sought for the FSTD vii. Unpublished but acceptable sources e.g., calculations, simulations, video or other simple means of flight test analysis or recording viii. Footprint test data from the actual training FSTD requiring qualification validated by NAA appointed pilot subjective assessment. In certain cases, it may make good engineering sense to provide more than one test to support a particular objective test requirement. An example might be a VMCG test, where the flight test engine and thrust profile do not match the simulated engine. The VMCG test could be run twice, once with the flight test thrust profile as an input and a second time with a fully integrated response to a fuel cut on the simulated engine. For aeroplanes certified prior to the date of issue of an amendment, an operator may, after reasonable attempts have failed to obtain suitable flight test data, indicate in the MQTG where flight test data are unavailable or unsuitable for a specific test. For each case, where the preferred data are not available, a rationale should be provided laying out the reasons for the non-compliance and justifying the alternate data and or test(s).

text: JAR-FSTD A 2-C-122 2009-11-01

text: Bilaga 1

text: Appendix 7 to ACJ No. 1 to JAR-FSTD A.030 (continued) These rationales should be clearly recorded within the Validation Data Road map (VDR) in accordance with and as defined in Appendix 2 to ACJ No. 1 to JAR-FSTD A.030. It should be recognised that there may come a time when there are so little compatible flight test data available that new flight test may be required to be gathered.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-123 JAR-FSTD A

text: Bilaga 1

text: Appendix 8 to ACJ No. 1 to JAR-FSTD A.030 General technical requirements for FSTD Qualification Levels

text: This Appendix summarises the general technical requirements for Flight Simulators levels A, B, C and D, FTD levels 1 and 2, FNPT levels I, II and IIMCC, and BITD.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD A 2-C-124 2009-11-01

text: Bilaga 1

text: Appendix 8 to ACJ No. 1 to JAR-FSTD A.030 (continued)

text: Table 1 – General technical requirements for JAA Level A, B, C and D Full Flight Simulators

text: Qualification General Technical Requirements Level

text: A The lowest level of flight simulator technical complexity. An enclosed full-scale replica of the aeroplane cockpit/flight deck including simulation of all systems, instruments, navigational equipment, communications and caution and warning systems. An instructor’s station with seat shall be provided. Seats for the flight crewmembers and two seats for inspectors/observers shall also be provided. Control forces and displacement characteristics shall correspond to that of the replicated aeroplane and they shall respond in the same manner as the aeroplane under the same flight conditions. The use of class specific data tailored to the specific aeroplane type with fidelity sufficient to meet the objective tests, functions and subjective tests is allowed. Generic ground effect and ground handling models are permitted. Motion, visual and sound systems sufficient to support the training, testing and checking credits sought are required. The visual system shall provide at least 45 degrees horizontal and 30 degrees vertical field of view per pilot. The response to control inputs shall not be greater than 300 milliseconds more than that experienced on the aircraft.

text: B As for Level A plus: Validation flight test data shall be used as the basis for flight and performance and systems characteristics. Additionally ground handling and aerodynamics programming to include ground effect reaction and handling characteristics shall be derived from validation flight test data.

text: C The second highest level of flight simulator fidelity. As for Level B plus: A daylight/twilight/night visual system is required with a continuous, cross-cockpit, minimum collimated visual field of view providing each pilot with 180 degrees horizontal and 40 degrees vertical field of view. A six degrees of freedom motion system shall be provided. The sound simulation shall include the sounds of precipitation and other significant aeroplane noises perceptible to the pilot and shall be able to reproduce the sounds of a crash landing. The response to control inputs shall not be greater than 150 milliseconds more than that experienced on the airplane. Windshear simulation shall be provided.

text: D The highest level of flight simulator fidelity. As for Level C plus: There shall be complete fidelity of sounds and motion buffets.

text: 2009-11-01 2-C-125 JAR-FSTD A

text: Bilaga 1

text: Table 2 – General technical requirements for JAA Level 1 and 2 FTDs

text: 1 Type specific with at least 1 system fully represented. Enclosed or open flight deck. Choice of systems simulated is the responsibility of the organisation seeking approval or reapproval for the course. The aeroplane system simulated shall comply with the relevant subjective and objective tests relevant to that system.

text: 2 Type specific device with all applicable systems fully represented. An enclosed flight deck with an onboard instructor station. Type specific or generic flight dynamics (but shall be representative of aircraft performance). Primary flight controls which control the flight path and be broadly representative of airplane control characteristics. Significant sounds. Control of atmospheric conditions. Navigation Data Base sufficient to support simulated aeroplane systems.

text: Table 3A - General technical requirements for JAA Type I FNPTs

text: FNPT Type I A cockpit/flight deck sufficiently enclosed to exclude distraction, which will replicate that of the aeroplane or class of aeroplane simulated and in which the navigation equipment, switches and the controls will operate as, and represent those in, that aeroplane or class of aeroplane. An instructor’s station with seat shall be provided and shall provide an adequate view of the crewmembers panels and station. Effects of aerodynamic changes for various combinations of drag and thrust normally encountered in flight, including the effect of change in aeroplane attitude, sideslip, altitude, temperature, gross mass, centre of gravity location and configuration. Complete navigational data for at least 5 different European airports with corresponding precision and non-precision approach procedures including current updating within a period of 3 months. Stall recognition device corresponding to that of the replicated aeroplane or class of aeroplane.

text: JAR-FSTD A 2-C-126 2009-11-01

text: Bilaga 1

text: Table 3B - General technical requirements for JAA Type II FNPTs

text: FNPT Type II As for Type I with the following additions or amendments:

text: An enclosed flight deck, including the instructor’s station.

text: Crew members’ seats shall be provided with sufficient adjustment to allow the occupant to achieve the design eye reference position appropriate to the aeroplane or class of aeroplane and for the visual system to be installed to align with that eye position.

text: Control forces and control travels which respond in the same manner under the same flight conditions as in the aeroplane or class of aeroplane being simulated.

text: Circuit breakers shall function accurately when involved in procedures or malfunctions requiring or involving flight crew response.

text: Aerodynamic modelling shall reflect: (a) the effects of airframe icing; (b) the rolling moment due to yawing.

text: A generic ground handling model shall be provided to enable representative flare and touch down effects to be produced by the sound and visual systems.

text: Systems shall be operative to the extent that it shall be possible to perform all normal, abnormal and emergency operations as may be appropriate to the aeroplane or class of aeroplanes being simulated and as required for the training.

text: Significant cockpit/flight deck sounds.

text: A visual system (night/dusk or day) capable of providing a field-of-view of a minimum of 45 degrees horizontally and 30 degrees vertically, unless restricted by the type of aeroplane, simultaneously for each pilot. The visual system need not be collimated.

text: The responses of the visual system and the flight deck instruments to control inputs shall be closely coupled to provide the integration of the necessary cues.

text: Table 3C - General technical requirements for JAA Type II MCC FNPTs

text: For use in Multi-Crew Co-operation (MCC) training - as for Type II with additional instrumentation and FNPT Type II indicators as required. for MCC training and operation. Reference ACJ no. 3 to JAR-FSTD A.030. MCC

text: 2009-11-01 2-C-127 JAR-FSTD A

text: Bilaga 1

text: Table 4 - General technical requirements for JAA BITDs

text: BITD A student pilot‘s station that represents a class of aeroplane sufficiently enclosed to exclude distraction. The switches and all the controls shall be of a representative size, shape, location and shall operate as and represent those as in the simulated class of aeroplane. In addition to the pilot’s seat, suitable viewing arrangements for the instructor shall be provided allowing an adequate view of the pilot’s panels. The Control forces, control travel and aeroplane performance shall be representative of the simulated class of aeroplane. Navigation equipment for flights under IFR with representative tolerances. This shall include communication equipment. Complete navigation database for at least 3 airports with corresponding precision and nonprecision approach procedures including regular updates. Engine sound shall be available. Instructor controls of atmospheric conditions and to set and reset malfunctions relating to flight instruments, navigation aids, flight controls, engine out operations (for multi engine aeroplanes only). Stall recognition device corresponding to that of the simulated class of aeroplane.

text: JAR-FSTD A 2-C-128 2009-11-01

text: Bilaga 1

text: ACJ No. 2 to JAR-FSTD A.030 (interpretative material) Guidance on Design and Qualification of Level 'A' Aeroplane FFSs

text: 1 Background 1.1 When determining the cost effectiveness of any FSTD many factors should be taken into account such as: (a) Environmental (b) Safety (c) Accuracy (d) Repeatability (e) Quality and depth of training (f) Weather and crowded airspace. 1.2 The requirements as laid down by the various regulatory bodies for the lowest level of FFS do not appear to have been promoting the anticipated interest in the acquisition of lower cost FFS for the smaller aeroplanes used by the general aviation community. 1.3 The significant cost drivers associated with the production of any FSTD are: (a) Type specific data package, (b) QTG flight test data, (c) Motion system, (d) Visual system, (e) Flight controls and (f) Aircraft parts. Note: To attempt to reduce the cost of ownership of a JAA Level A FFS, each element has been examined in turn and with a view to relaxing the requirements where possible whilst recognising the training, checking and testing credits allowed on such a device. 2 Data package 2.1 The cost of collecting specific flight test data sufficient to provide a complete model of the aerodynamics, engines and flight controls can be significant. The use of a class specific data package which could be tailored to represent a specific type of aeroplane (e.g. PA34 to PA31) is encouraged. This may enable a well-engineered light twin baseline data package to be carefully tuned to adequately represent any one of a range of similar aeroplanes. Such work including justification and the rationale for the changes would have to be carefully documented and made available for consideration by the JAA FSTD Steering Group as part of the qualification process. Note that for this lower level of FFS, the use of generic ground handling and generic ground effect models is allowed. 2.2 However specific flight test data to meet the needs of each relevant test within the QTG will be required. Recognising the cost of gathering such data, two points should be borne in mind: (a) For this class of FFS, much of the flight test information could be gathered by simple means e.g. stopwatch, pencil and paper or video. However comprehensive details of test methods and initial conditions should be presented. (b) A number of tests within the QTG have had their tolerances reduced to ‘Correct Trend and Magnitude’ (CT&M) thereby avoiding the need for specific flight test data. (c) The use of CT&M is not to be taken as an indication that certain areas of simulation can be ignored. Indeed in the class of aeroplane envisaged, that might take advantage of Level A, it is imperative that the specific characteristics are present, and incorrect effects would be unacceptable (e.g. if the aeroplane has a weak positive spiral stability, it would not be acceptable for the FFS to exhibit neutral or negative spiral stability).

text: 2009-11-01 2-C-129 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 2 to JAR-FSTD A.030 (continued)

text: (d) Where CT&M is used as a tolerance, it is strongly recommended that an automatic recording system be used to ‘footprint’ the baseline results thereby avoiding the effects of possible divergent subjective opinions on recurrent evaluations.

text: 3 Motion 3.1 For Level A FFS, the requirements for both the primary cueing and buffet simulation have been not specified in detail. Traditionally, for primary cueing, emphasis has been laid on the numbers of axes available on the motion system. For this level of FFS, it is felt appropriate that the FFS manufacturer should be allowed to decide on the complexity of the motion system. However, during the evaluation, the motion system will be assessed subjectively to ensure that it is supporting the piloting task, including engine failures, and is, under no circumstances, providing negative cueing. 3.2 Buffet simulation is important to add realism to the overall simulation; for Level A, the effects can be simple but they should be appropriate, in harmony with the sound cues and, under no circumstances, provide negative training. 4 Visual

text: 4.1 Other than field of view (FOV), specific technical criteria for the visual systems are not specified. The emergence of lower cost ‘raster only’ daylight systems is recognised. The adequacy of the performance of the visual system will be determined by its ability to support the flying tasks. e.g. ‘visual cueing sufficient to support changes in approach path by using runway perspective’. 4.2 The need for collimated visual optics may not always be necessary. A single channel direct viewing system would be acceptable for a FFS of a single crew aeroplane. (The risk here is that, should the aeroplane be subsequently upgraded to multi-crew, the non-collimated visual system may be unacceptable.)

text: 4.3 The vertical FOV specified (30°) may be insufficient for certain tasks. Some smaller aeroplane have large downward viewing angles which cannot be accommodated by the +/–15° vertical FOV. This can lead to two limitations: (a) At the CAT I all weather operations Decision Height, the appropriate visual ground segment may not be ‘seen’; and

text: (b) During an approach, where the aeroplane goes below the ideal approach path, during the subsequent pitch-up to recover, adequate visual reference to make a landing on the runway may be lost. 5 Flight Controls The specific requirements for flight controls remain unchanged. Because the handling qualities of smaller aeroplanes are inextricably intertwined with their flight controls, there is little scope for relaxation of the tests and tolerances. It could be argued that with reversible control systems that the on the ground static sweep should in fact be replaced by more representative ‘in air’ testing. It is hoped that lower cost control loading systems would be adequate to fulfil the needs of this level of simulation (i.e. electric). 6 Aeroplane Parts As with any level of FSTD, the components used within the flight deck area need not be aeroplane parts; however, any parts used should be robust enough to endure the training tasks. Moreover, the Level A FFS is type specific, thus all relevant switches, instruments, controls etc. within the simulated area will be required to look and feel ‘as aeroplane’.

text: JAR-FSTD A 2-C-130 2009-11-01

text: Bilaga 1

text: ACJ No. 3 to JAR-FSTD A.030 (interpretative material) Guidance on Design and Qualification of FNPTs See also JAR-FSTD A.030

text: 1 Background 1.1 Traditionally training devices used by the ab-initio professional pilot schools have been relatively simple instrument flight-only aids. These devices were loosely based on the particular school's aeroplane. The performance would be approximately correct in a small number of standard configurations, however the handling characteristics could range from rudimentary to loosely representative. The instrumentation and avionics fit varied between basic and very close to the target aeroplane. The approval to use such devices as part of a training course was based on a regular subjective evaluation of the equipment and its operator by an authority inspector. 1.2 JAR-FSTD A introduces two new devices: FNPT I & FNPT II. The FNPT I device is essentially a replacement for the traditional instrument flight ground training device taking advantage of recent technologies and having a more objective design basis. The FNPT II device is the more advanced of the two defined standards and fulfils the wider requirements of the various JAR-FCL professional pilot training modules up to and including (optionally with additional features) multi-crew co-operation (MCC) training. 1.3 The currently available technologies enable such new devices to have much greater fidelity and lower life-cycle costs than was previously possible. A more objective design basis encourages better understanding and therefore modelling of the aeroplane systems, handling and performance. These advances combined with the ever upwardly spiralling costs of flying and with the environmental pressures all point towards the need for revised standards. 1.4 The FNPT II device essentially bridges the gap in design complexity between the traditional subjectively created device and the objectively based Level A FFS. 1.5 These new standards are designed to replace the highly subjective design standards and qualification methods with new objective and subjective methods, which ensure that the devices fulfil their intended goals throughout their service lives. 2 Design Standards There are two sets of design standards specified within JAR-FSTD A, FNPT I and FNPT II, the more demanding one of which is FNPT II. 2.1 Simulated Aeroplane Configuration

text: Unlike FFS devices, FNPT I and FNPT II devices are intended to be representative of a class of aeroplane (although they may in fact be type specific if desired). The configuration chosen should sensibly represent the aeroplane or aeroplanes likely to be used as part of the overall training package. Areas such as general layout, seating, instruments and avionics, control type, control force and position, performance and handling and powerplant configuration should be representative of the class of aeroplane or the aeroplane itself.

text: It would be in the interest of all parties to engage in early discussions with the Authority to broadly agree a suitable configuration (known as the "designated aeroplane configuration"). Ideally any such discussion would take place in time to avoid any hold-ups in the design/build/acceptance process thereby ensuring a smooth entry into service. 2.2 The Cockpit/Flight Deck The cockpit/flight deck should be representative of the designated aeroplane configuration. For good training ambiance the cockpit/flight deck should be sufficiently enclosed for FNPT I to exclude any distractions. For an FNPT II the cockpit/flight deck should be fully enclosed. The controls, instruments and avionics controllers should be representative: touch, feel, layout, colour and lighting to create a positive learning environment and good transfer of training to the aeroplane. 2.3 Cockpit/Flight Deck Components As with any training device, the components used within the cockpit/flight deck area do not need to be aircraft parts: however, any parts used should be representative of typical training aeroplanes and should be robust enough to endure the training tasks. With the current state of technology the use of simple CRT monitor based representations and touch screen controls would not be acceptable. The training tasks envisaged for these

text: 2009-11-01 2-C-131 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 3 to JAR-FSTD A.030 (continued)

text: devices are such that appropriate layout and feel is very important: i.e. the altimeter sub-scale knob needs to be physically located on the altimeter. The use of CRTs with physical overlays incorporating operational switches/knobs/buttons replicating an aeroplane instrument panel may be acceptable. 2.4 Data The data used to model the aerodynamics flight controls and engines should be soundly based on the "designated aeroplane configuration". It is not acceptable and would not give good training if the models merely represented a few key configurations bearing in mind the extent of the credits available. Validation data may be derived from a specific aeroplane within a set of aeroplanes that the FNPT is intended to represent, or it may be based on information from several aeroplanes within a set/group/range ("designated aeroplane configuration"). It is recommended that the intended validation data together with a substantiation report be submitted to the Authority for evaluation and approval prior to the commencement of the manufacturing process. 2.4.1 Data Collection and Model Development Recognizing the cost of and complexity of flight simulation models, it should be possible to generate generic class "typical" models. Such models should be continuous and vary sensibly throughout the required training flight envelope. A basic requirement for any modelling is the integrity of the mathematical equations and models used to represent the flying qualities and performance of the class of aeroplane simulated. Data to tune the generic model to represent a more specific aeroplane can be obtained from many sources without recourse to expensive flight test: (a) Aeroplane design data (b) Flight and Maintenance Manuals (c) Observations on ground and in air Data obtained on the ground and in flight can be measured and recorded using a range of simple means such as: (a) Video (b) Pencil and paper (c) Stopwatch (d) New technologies (i.e. GPS) Any such data gathering should take place at representative masses and centres of gravity. Development of such a data package including justification and the rationale for the design and intended performance, the measurement methods and recorded parameters (e.g. mass, c of g, atmospheric conditions) should be carefully documented and available for inspection by the Authority as part of the qualification process. 2.5 Limitations A further possible complication is the strong interaction between the flight control forces and the effects of both the engines and the aerodynamic configuration. For this reason a simple force cueing system in which forces vary not only with position but with configuration (speed, flaps, trim) will be necessary for the FNPT II device. For an FNPT I device a force cueing system may be spring-loaded, but it should be remembered that it is vitally important that negative characteristics would not be acceptable. It should be remembered however that whilst a simple model may be sufficient for the task, it is vitally important that negative characteristics are not present. 3 Visual Unless otherwise stated, the visual requirements are as specified for a Level A FFS. 3.1 Other than Field-of-View (FoV) specific technical criteria for the visual systems are not specified. The emergence of lower cost raster only daylight systems is recognised. The adequacy of the performance of the visual system will be determined by its ability to support the flying tasks. e.g. "visual cueing sufficient to support changes in approach path by using runway perspective". 3.2 The need for collimated visual optics is probably not necessary. A single channel direct viewing system (single projector or a monitor for each pilot) would probably be acceptable as no training credits for

text: JAR-FSTD A 2-C-132 2009-11-01

text: Bilaga 1

text: ACJ No. 3 to JAR-FSTD A.030 (continued)

text: landing will be available. Distortions due to non-collimation would only become significant during on ground or near to the ground operations. 3.3 The minimum specified vertical FoV of 30 deg may not be sufficient for certain tasks. Where the FNPT does not simulate a particular aeroplane type, then the design of the out-of-cockpit/flight deck view should be matched to the visual system such that the pilot has a FoV sufficient for the training tasks. For example during an instrument approach the pilot should be able to see the appropriate visual segment at Decision Height. Additionally where the aeroplane deviates from the permitted approach path, undue loss of visual reference should not occur during the subsequent correction in pitch. 3.4 There are two methods of establishing latency, which is the relative response of the visual system, cockpit/flight deck instruments and initial motion system response. These should be coupled closely to provide integrated sensory cues. For a generic FNPT, a Transport Delay test is the only suitable test that demonstrates that the FNPT system does not exceed the permissible delay. If the FNPT is based upon a particular aeroplane type, either Transport Delay or Latency tests are acceptable. Response time tests check response to abrupt pitch, roll, and yaw inputs at the pilot's position is within the permissible delay, but not before the time when the aeroplane would respond under the same conditions. Visual scene changes from steady state disturbance should occur within the system dynamic response limit but not before the resultant motion onset. The test to determine compliance with these requirements should include simultaneously recording the analogue output from the pilot's control column, wheel, and pedals, the output from the accelerometer attached to the motion system platform located at an acceptable location near the pilots’ seats, the output signal to the visual system display (including visual system analogue delays), and the output signal to the pilot's attitude indicator or an equivalent test approved by the Authority. The test results in a comparison of a recording of the simulator's response with actual aeroplane response data in the take-off, cruise, and landing configuration. The intent is to verify that the FNPT system Transport Delays or time lags are less than the permissible delay and that the motion and visual cues relate to actual aeroplane responses. For aeroplane response, acceleration in the appropriate rotational axis is preferred. The Transport Delay test should measure all the delay encountered by a step signal migrating from the pilot's control through the control loading electronics and interfacing through all the simulation software modules in the correct order, using a handshaking protocol, finally through the normal output interfaces to the motion system, to the visual system and instrument displays. A recordable start time for the test should be provided by a pilot flight control input. The test mode should permit normal computation time to be consumed and should not alter the flow of information through the hardware/software system. The Transport Delay of the system is then the time between control input and the individual hardware responses. It need only be measured once in each axis 3.5 Care should be taken when using the limited processing power of the lower cost visual systems to concentrate on the key areas which support the intended uses thereby avoiding compromising the visual model by including unnecessary features e.g. moving ground traffic, marshallers. The capacity of the visual model should be directed towards: (a) Runway surface (b) Runway lighting systems (c) PAPI/ VASI approach guidance aids (d) Approach lighting systems (e) Simple taxiway (f) Simple large-scale ground features e.g. large bodies of water, big hills (g) Basic environmental lighting (night/dusk)

text: 4 Motion Although motion is not a requirement for either an FNPT I or II, should the operator choose to have one fitted, it will be evaluated to ensure that its contribution to the overall fidelity of the device is positive. Unless

text: 2009-11-01 2-C-133 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 3 to JAR-FSTD A.030 (continued) otherwise stated in this document, the motion requirements are as specified for a Level A FFS, see ACJ No 2 to JAR-FSTD A.030 5 Testing / Evaluation To ensure that any device meets its design criteria initially and periodically throughout its life a system of objective and subjective testing will be used. The subjective testing may be similar to that in use in the recent past. The objective testing methodology is drawn from that used currently on FSTD. The validation tests specified (ACJ No 1 to JAR-FSTD A.030 par. 2.3) can be "flown" by a suitably skilled person and the results recorded manually. Bearing in mind the cost implications, the use of automatic recording (and testing) is encouraged thereby increasing the repeatability of the achieved results. The tolerances specified are designed to ensure that the device meets its original target criteria year after year. It is therefore important that such target data is carefully derived and values are agreed with the appropriate inspecting authority in advance of any formal qualification process. For initial qualification, it is highly desirable that the device should meet its design criteria within the listed tolerances, however unlike the tolerances specified for FSTDs, the tolerances contained within this document are specifically intended to be used to ensure repeatability during the life of the device and in particular at each recurrent regulatory inspection. A number of tests within the QTG have had their tolerances reduced to "Correct Trend and Magnitude" (CT&M) thereby avoiding the need for specific validation data. The use of CT&M is not to be taken as an indication that certain areas of simulation can be ignored. For such tests, the performance of the device should be appropriate and representative of the simulated designated aeroplane and should under no circumstances exhibit negative characteristics. Where CT&M is used as a tolerance, it is strongly recommended that an automatic recording system be used to "footprint" the baseline results thereby avoiding the effects of possible divergent subjective opinions during recurrent evaluations. The subjective tests listed under "Functions and Manoeuvres" (ACJ No 1 to JAR- FSTD A.030 para. 3) should be flown out by a suitably qualified and experienced pilot. Subjective testing will review not only the interaction of all of the systems but the integration of the FNPT with: (a) Training environment (b) Freezes and repositions (c) Navaid environment (d) Communications (e) Weather and visual scene contents In parallel with this objective/subjective testing process it is envisaged that suitable maintenance arrangements as part of a Quality Assurance Programme shall be in place. Such arrangements will cover routine maintenance, the provision of satisfactory spares holdings and personnel. 6 FNPT Type I The design standards, testing and evaluation requirements for the FNPT Type I device are less demanding than those required for a FNPT Type II device. This difference in standard is in line with the reduced JAR-FCL credits available for this type of device. 7 Additional features Any additional features in excess of the minimum design requirements added to an FNPT Type I & II will be subject to evaluation and should meet the appropriate standards in JAR-FSTD A.

text: JAR-FSTD A 2-C-134 2009-11-01

text: Bilaga 1

text: ACJ No. 4 to JAR-FSTD A.030 (interpretative material) Guidance on Design and Qualification of BITDs See JAR–FSTD A.030

text: 1 Background 1.1 Traditionally training devices used by the ab-initio pilot schools have been relatively simple instrument flight-only aids. These devices were loosely based on the particular school's aeroplane. The performance would be approximately correct in a small number of standard configurations, however the handling characteristics could range from rudimentary to loosely representative. The instrumentation and avionics fit varied between basic and very close to the target aeroplane. The approval to use such devices as part of a training course was based on a regular subjective evaluation of the equipment and its operator by an Authority inspector. 1.2 JAR-FSTD A introduces two new devices, FNPT type I and FNPT type II, where the FNPT I device is essentially a replacement for the traditional instrument flight ground training device taking advantage of recent technologies and having a more objective design basis. 1.3 JAR-FSTD A sets also the requirements and guidelines for the lowest level of FSTDs by introducing BITDs. It should be clearly understood that a BITD never can replace an FNPT I. The main purpose of a BITD is to replace an old instrument training device that cannot be longer approved either due to poor fidelity or system reliability. 2 Design Standards 2.1 Unlike FFS devices, a BITD is intended to be representative of a class of aeroplane. The configuration chosen should broadly represent the aeroplane likely to be used as part of the overall training package. It would be in the interest of all parties to engage in early discussions with the Authority to broadly agree a suitable configuration, known as the 'designated aeroplane configuration'. 2.2 The student pilot station should be broadly representative of the designated aeroplane configuration and should be sufficiently enclosed to exclude any distractions. 2.3 The main instrument panel in a BITD may be displayed on a CRT. Touch screen or mouse and keyboard operation by the student pilot would not be acceptable for any instrument or system. 2.4 The standards for BITDs were developed for low cost devices and therefore were kept as simple as possible. With advances in technology the higher standards defined for FFSs and FNPTs should be used where economically possible. 3 Validation Data 3.1 The data used to model the aerodynamics and engine(s) should be soundly based on the designated aeroplane configuration. It is not acceptable if the models merely represent a few key configurations. 3.2 Recognising the cost and complexity of flight simulation models, it should be possible to generate a generic class typical model. Such models should be continuous and vary sensibly throughout the required training flight envelope. A basic principal for any modelling is the integrity of the mathematical equations and models used to represent the flying qualities and performance of the class of aeroplane simulated. Data to tune the generic model to represent a more specific aeroplane can be obtained from many sources without recourse to expensive flight test: (a) Aeroplane design date (b) Flight and Maintenance Manuals (c) Observations on ground and during flight Data obtained on ground or in flight can be measured and recorded using a range of simple means such as: (a) Video (b) Pencil and paper (c) Stopwatch (d) New technologies like GPS etc.

text: 2009-11-01 2-C-135 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 4 to JAR-FSTD A.030 (continued)

text: Any such data gathering should take place at representative masses and centres of gravity. Development of such a data package including justification and the rationale for the design and intended performance, the measurement methods and recorded parameters should be carefully documented and available for inspection by the Authority as part of the qualification process.

text: 4 Limitations

text: A force cueing system may be spring-loaded. But it should be remembered that it is vitally important that negative characteristics would not be acceptable. 5 Testing and Evaluation

text: To ensure that any device meets its design criteria initially and periodically throughout its ‘life’ a system of objective and subjective testing will be used. The subjective testing may be similar to that in use in the recent past. The objective testing methodology is drawn from that used currently on higher level training devices. The validation tests specified in ACJ No 1 to JAR-FSTD A.030, para. 2.3 can be flown by a suitably skilled person and the results recorded manually. However a print out of the parameters of interest is highly recommended, thereby increasing the repeatability of the achieved results.

text: The tolerances specified are designated to ensure that the device meets its original target criteria year after year. It is therefore important that such target data is carefully derived and values are agreed with the inspecting Authority in advance of any formal qualification process. For initial qualification, it is highly desirable that the device meets its design criteria within the listed tolerances, however the tolerances contained in this document are specifically intended to be used to ensure repeatability during the ‘life’ of the device and in particular at each recurrent Authority evaluation.

text: Most of the tests within the QTG had their tolerances reduced to Correct Trend and Magnitude (CT&M). The use of CT&M is not to be taken as an indication that certain areas of simulation can be ignored. For such tests, the performance of the device should be approximate and representative of the simulated class of aeroplane and should under no circumstances exhibit negative characteristics. In all these cases it is strongly recommended to print out the baseline results during initial evaluation thereby avoiding the effects of possible divergent subjective opinions during recurrent evaluations.

text: The subjective tests listed under ACJ No 1 to JAR-FSTD A.030, para. 3, functions and manoeuvres, should be flown out by a suitably qualified and experienced pilot. Subjective testing will not only review the interaction of all the applicable systems but the integration of the BITD within a training syllabus, including: (a) Training environment (b) Freezes and repositions

text: (c) Navaid environment In parallel with this objective and subjective testing process it is envisaged that suitable maintenance arrangements as part of a Quality System are in place. Such arrangements will cover routine maintenance, the provision of satisfactory spares supply and personnel.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD A 2-C-136 2009-11-01

text: Bilaga 1

text: ACJ No. 4 to JAR-FSTD A.030 (continued)

text: 6 Guidelines for an Instrument Panel displayed on a Screen

text: a. The basic flight instruments shall be displayed and arranged in the usual "T-layout". Instruments shall be displayed very nearly full-size as in the simulated class of aeroplane. The following instruments shall be displayed so as to be representative for the simulated class of aeroplane: 1. An attitude indicator with at least 5° and 10° pitch markings, and bank angle markings for 10°, 20°, 30° and 60°. 2. Adjustable altimeter(s) with 20 ft markings. Controls to adjust the QNH shall be located spatially correct at the respective instrument. 3. An airspeed indicator with at least 5 kts markings within a representative speed range and colour coding. 4. An HSI or heading indicator with incremental markings each of at least 5°, displayed on a 360° circle. The heading figures shall be radially aligned. Controls to adjust the course or heading bugs shall be located spatially correct at the respective instrument. 5. A vertical speed indicator with 100 fpm markings up to 1 000 fpm and 500 fpm thereafter within a representative range. 6. A turn and bank indicator with incremental markings for a rate of 3° per second turn for left and right turns. The 3° per second rate index shall be inside of the maximum deflection of the indicator. 7. A slip indicator representative of the simulated class of aeroplane, where a coordinated flight condition is indicated with the ball in centre position. A triangle slip indicator is acceptable if applicable for the simulated class of aeroplane 8. A magnetic compass with incremental markings each 10°. 9. Engine instruments as applicable to the simulated class of aeroplane, with markings for normal ranges, minimum and maximum limits. 10. A suction gauge or instrument pressure gauge, as applicable, with a display as applicable for the simulated class of aeroplane. 11. A flap position indicator, which displays the current flap setting. This indicator shall be representative of the simulated class of aeroplane. 12. A pitch trim indicator with a display that shows zero trim and appropriate indices of aeroplane nose down and nose up trim. 13. A stop watch or digital timer, which allows the readout of seconds and minutes. b. A communication and navigation panel shall be displayed in a manner that the frequency in use is shown. Controls to select the frequencies and other functions may be located on a central COM/NAV panel or on a separate ergonomically located panel. The NAV equipment shall include ADF, VOR, DME and ILS indicators with the following incremental markings: 1. One-half dot or less for course and glide slope indications on the VOR and ILS display. 2. 5° or less of bearing deviation for ADF and RMI, as applicable. All NAV radios shall be equipped with an aural identification feature. A marker beacon receiver shall also be installed with an optical and aural identification.

text: 2009-11-01 2-C-137 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 4 to JAR-FSTD A.030 (continued) c. All instrument displays shall be visible during all flight operation. The instrument system shall be designed to ensure jumping and stepping is not a distraction and to display all changes within the range of the replicated instruments that are equal or greater than the values stated below: 1. Attitude ½° pitch and 1° bank 2. Turn and bank of ¼ standard rate turn 3. IAS 1 kts 4. VSI 20 fpm 5. Altitude 3 ft 6. Heading on HSI ½° 7. Course and Heading on OBS and/or RMI 1° 8. ILS ¼° 9. RPM 25 10. MP ½ inch d. The update rate of all displays shall be proofed by a SOC. The resolution shall provide an image of the instruments that: 1. does not appear out of focus. 2. does not appear to "jump" or "step" to a distracting degree during operation. 3. does not appear with distracting jagged lines or edges.

text: 7 Additional Information Unlike with other FSTDs the manufacturer of a BITD has the responsibility for the initial evaluation of a new BITD model. Because all serial numbers of such a model are automatically qualified, the user approval at the operator's site becomes more important before the course approval is granted.

text: JAR-FSTD A 2-C-138 2009-11-01

text: Bilaga 1

text: ACJ No. 1 to JAR-FSTD A.030(c)(1) (acceptable means of compliance) Engineering Simulator Validation Data See JAR-FSTD A.030(c)(1)

text: 1. When a fully flight-test validation simulation is modified as a result of changes to the simulated aircraft configuration, a qualified aircraft manufacturer may choose, with the prior agreement of the Authority, to supply validation data from an “audited” engineering simulator/simulation to supplement selectively flight test data. This arrangement is confined to changes which are incremental in nature and which are both easily understood and well defined. 2. To be qualified to supply engineering simulator validation data, an aircraft manufacturer should: (a) Have a proven track record of developing successful data packages: (b) Have demonstrated high quality prediction methods through comparisons of predicted and flight test validated data; (c) Have an engineering simulator which - has models that run in an integrated manner, - uses the same models as released to the training community (which are also used to produce stand/alone proof-of-match and checkout documents), - is used to support aircraft development and certification; (d) Use the engineering simulation to produce a representative set of integrated proof-of-match cases; (e) Have an acceptable configuration control system in place covering the engineering simulator and all other relevant engineering simulations. 3. Aircraft manufacturers seeking to take advantage of this alternative arrangement shall contact the Authority at the earliest opportunity. 4. For the initial application, each applicant should demonstrate his ability to qualify to the satisfaction of the JAA FSTD Steering Group, in accordance with the criteria in this ACJ and the corresponding ACJ No. 2 to JAR-FSTD A.030(c)(1).

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-139 JAR-FSTD A

text: Bilaga 1

text: ACJ No. 2 to JAR-FSTD A.030(c)(1) (interpretative material) Engineering Simulator Validation Data – Approval Guidelines See JAR-FSTD A.030(c)(1)

text: 1. Background 1.1. In the case of fully flight-test validated simulation models of a new or major derivative aircraft, it is likely that these models will become progressively unrepresentative as the aircraft configuration is revised. 1.2. Traditionally as the aircraft configuration has been revised, the simulation models have been revised to reflect changes. In the case of aerodynamic, engine, flight control and ground handling models, this revision process normally results in the collection of additional flight-test data and the subsequent release of new models and validation data. 1.3. The quality of the prediction of simulation models has advanced to the point where differences between the predicted and the flight-test validation models are often quite small. 1.4. The major aircraft manufacturers utilise the same simulation models in their engineering simulations as released to the training community. These simulations vary from physical engineering simulators with and without aircraft hardware to non-real-time workstation based simulations. 2. Approval Guidelines – for using Engineering Simulator Validation Data 2.1. The current system of requiring flight test data as a reference for validating training simulators should continue. 2.2. When a fully flight-test-validated simulation is modified as a result of changes to the simulated aircraft configuration, a qualified aircraft manufacturer may choose, with prior agreement of the Authority, to supply validation data from an engineering simulator/simulation to supplement selectively flight test data. 2.3. In cases where data from an engineering simulator is used, the engineering simulation process would have to be audited by the Authority. 2.4 In all cases a data package verified to current standards against flight test should be developed for the aircraft “entry-into-service” configuration of the baseline aircraft. 2.5 Where engineering simulator data is used as part of a QTG, an essential match is expected as described in Appendix 1 to JAR-FSTD A.030. 2.6 In cases where the use of engineering simulator data is envisaged, a complete proposal should be presented to the appropriate regulatory body(ies). Such a proposal would contain evidence of the aircraft manufacturer’s past achievements in high fidelity modelling. 2.7 The process will be applicable to “one step” away from a fully flight validated simulation. 2.8 A configuration management process should be maintained, including an audit trail which clearly defines the simulation model changes step by step away from a fully flight validated simulation, so that it would be possible to remove the changes and return to the baseline (flight validated) version. 2.9 The Authorities will conduct technical reviews of the proposed plan and the subsequent validation data to establish acceptability of the proposal. 2.10 The procedure will be considered complete when an approval statement is issued. This statement will identify acceptable validation data sources. 2.11 To be admissible as an alternative source of validation data an engineering simulator would: (a) Have to exist as a physical entity, complete with a flight deck representative of the affected class of aircraft, with controls sufficient for manual flight. (b) Have a visual system; and preferably also a motion system. (c) Where appropriate, have actual avionics boxes interchangeable with the equivalent software simulations, to support validation of released software.

text: JAR-FSTD A 2-C-140 2009-11-01

text: Bilaga 1

text: ACJ No. 2 to JAR-FSTD A.030(c)(1) (continued) (d) Have a rigorous configuration control system covering hardware and software. (e) Have been found to be a high fidelity representation of the aircraft by the pilots of the manufacturers, operators and the Authority. 2.12 The precise procedure followed to gain acceptance of engineering simulator data will vary from caseto-case between aircraft manufacturers and type of change. Irrespective of the solution proposed, engineering simulations/simulators should conform to the following criteria: (a) The original (baseline) simulation models should have been fully flight-test validated. (b) The models as released by the aircraft manufacturer to the industry for use in training FSTDs should be essentially identical to those used by the aircraft manufacturer in their engineering simulations/simulators. (c) These engineering simulation/simulators will have been used as part of the aircraft design, development and certification process. 2.13 Training flight simulator(s) utilising these baseline simulation models should be currently qualified to at least internationally recognised standards such as contained in the ICAO Document 9625, the “Manual of Criteria for the Qualification of Flight Simulators”. 2.14 The type of modifications covered by this alternative procedure will be restricted to those with “well understood effects”: (a) Software (e.g., flight control computer, autopilot, etc.). (b) Simple (in aerodynamic terms) geometric revisions (e.g., body length). (c) Engines – limited to non-propeller-driven aircraft. (d) Control system gearing/rigging/deflection limits (e) Brake, tyre and steering revisions. 2.15 The manufacturer, who wishes to take advantage of this alternative procedure, is expected to demonstrate a sound engineering basis for his proposed approach. Such analysis would show that the predicted effects of the change(s) were incremental in nature and both easily understood and well defined, confirming that additional flight test data were not required. In the event that the predicted effects were not deemed to be sufficiently accurate, it might be necessary to collect a limited set of flight test data to validate the predicted increments. 2.16 Any applications for this procedure will be reviewed by an Authorities team established by the JAA FSTD Steering Group.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-141 JAR-FSTD A

text: Bilaga 1

text: ACJ to JAR-FSTD A.035 FFS Approved or Qualified before 1 April 1998 See JAR–FSTD A.035

text: 1 Introduction 1.1 Under previous National Rules, FFS may have gained credits in accordance with primary reference documents, which state appropriate technical criteria.

text: 1.2 Other FFS may not have been monitored to the same extent, but may have documents or statements from their Authority giving broad or specific permission for them to be used for certain training, testing and checking manoeuvres. 1.3 It is intended that FFS devices should continue to maintain their Qualification Level and or approval granted prior to the adoption of JAR–STD 1A and subsequently JAR-FSTD A. 2 Recategorisation

text: Some of these FFS may be of a standard that permits them to be recategorised as if they were FFS presented for initial qualification on or after 1 April 1998. 3 Equivalent categories AG, BG, CG, DG 3.1 FFS that are not recategorised and that do have an acceptable primary reference document used for their original national qualification or national approval, will gain a JAA qualification based upon their original technical Qualification Level. The equivalent qualification will relate to permitted manoeuvres in the original national qualification or approval document providing that these older FFS continue to meet the original national criteria when evaluated by the Authority. 3.2 The letter G will be added to each originally issued Qualification Level to show that the existing Qualification Level deserves its credit under the grandfather right provisions. To comply with the rule, the primary reference document should have meaningful validation, functions and subjective tests criteria, which reasonably cover the performance envelope of the FFS, and in particular the manoeuvres for which the equivalent JAA Qualification Level is given. The minimum acceptable standard is FAA AC 120-40A or equivalent. 4 Original national qualification 4.1 FFS that are not recategorised and that do not have an acceptable primary reference document may continue to enjoy credits for an agreed list of training, testing and checking manoeuvres, provided they maintain their performance in accordance with any validation, functions and subjective tests which have been previously established or a list of tests selected from ACJ No 1 to JAR-FSTD A.030 by agreement with the Authority. Again the tests should relate to the list of manoeuvres permitted under the original national qualification or approval document. 4.2 The award of credits to an FFS user should be at the discretion of the Authority. Current FFS users may retain the credits granted under their previous national criteria.

text: JAR-FSTD A 2-C-142 2009-11-01

text: Bilaga 1

text: ACJ to JAR-FSTD A.035 (continued)

text: 5 Grandfather rights summary

text: The following table summarises the arrangements for FFS approved or qualified before 1 April 1998 and which are not recategorised:

text: Primary Reference JAA equivalent Performance Document available qualification level criteria

text: Yes AG Maximum training, Perform to the original national BG testing and checking validation functions and CG Credits similar subjective tests from DG to A, B, C, D reference doc.

text: No Special Categories Original validation, functions and subjective tests or a list of tests Unique list of manoeuvres selected from ACJ No 1 to JAR- FSTD A.030 (by agreement)

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-143 JAR-FSTD A

text: Bilaga 1

text: ACJ to JAR-FSTD A.036 Flight Training Devices Approved or Qualified before 1 July 2000 See JAR–FSTD A.036

text: 1 Introduction 1.1 Under previous national rules, FTDs may have gained credits in accordance with primary reference documents which state appropriate technical criteria. 1.2 Other FTDs may not have been monitored to the same extent, but may have documents or statements from their National Authority giving broad or specific permission for them to be used for certain training, testing and checking manoeuvres. 1.3 In any case, it is intended that FTDs should continue to maintain their Qualification Level and or approval granted prior to the adoption of JAR–FSTD A in accordance with previous national criteria. 2 Recategorisation Some of these FTDs may be of a standard which permits them to be recategorised as if they were FTDs presented for initial qualification on or after 1 July 2000. 3 Original national qualification 3.1 FTDs that are not recategorised and that do not have an acceptable primary reference document may continue to enjoy credits for an agreed list of training, testing and checking manoeuvres, provided they maintain their performance in accordance with any validation, functions and subjective tests which have been previously established or a list of tests selected from ACJ No 1 to JAR-FSTD A.030 by agreement with the Authority. Again these tests should relate to the list of manoeuvres permitted under the original national qualification or approval document. 3.2 The award of credits to an FTD user should be at the discretion of the Authority. Current FTD users may retain the credits granted under their previous national criteria.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD A 2-C-144 2009-11-01

text: Bilaga 1

text: ACJ to JAR-FSTD A.037 FNPT Approved or Qualified before 1 July 1999 See JAR–FSTD A.037

text: 1 The period of Grandfather Rights granted to FNPT’s had a period of validity of a maximum of six years from 1 July 1999 (which corresponds to the date of JAR-FCL 1 implementation). This period has now expired and Grandfather Rights under JAR-FSTD A.037 are no longer applicable to FNPT’s. All devices are now required to be qualified in accordance with JAR-STD 3A or JAR-FSTD A, as applicable

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-145 JAR-FSTD A

text: Bilaga 1

text: ACJ to JAR-FSTD A.045 (explanatory material) New Aircraft FFS/FTD Qualification – Additional Information See JAR–FSTD A.045

text: 1 It is usual that aircraft manufacturer’s approved final data for performance, handling qualities, systems or avionics will not be available until well after a new or derivative aircraft has entered service. It is often necessary to begin flight crew training and certification several months prior to the entry of the first aircraft into service and consequently it may be necessary to use aircraft manufacturer-provided preliminary data for interim qualification of FSTDs. 2 In recognition of the sequence of events that should occur and the time required for final data to become available, the Authority may accept certain partially validated preliminary aircraft and systems data, and early release (‘red label’) avionics in order to permit the necessary programme schedule for training, certification and service introduction. 3 FSTD operators seeking qualification based on preliminary data should, however, consult the Authority as soon as it is known that special arrangements will be necessary or as soon as it is clear that the preliminary data will need to be used for FSTD qualification. Aircraft and FSTD manufacturers should also be made aware of the needs and be agreed party to the data plan and FSTD qualification plan. The plan should include periodic meetings to keep the interested parties informed of project status. 4 The precise procedure to be followed to gain Authority acceptance of preliminary data will vary from case to case and between aircraft manufacturers. Each aircraft manufacturer’s new aircraft development and test programme is designed to suit the needs of the particular project and may not contain the same events or sequence of events as another manufacturer’s programme or even the same manufacturer’s programme for a different aircraft. Hence, there cannot be a prescribed invariable procedure for acceptance of preliminary data, but instead there should be a statement describing the final sequence of events, data sources, and validation procedures agreed by the FSTD operator, the aircraft manufacturer, the FSTD manufacturer, and the Authority. NOTE: A description of aircraft manufacturer-provided data needed for flight simulator modelling and validation is to be found in the IATA Document ‘Flight Simulator Design and Performance Data Requirements’ – (Edition 6 2000 or as amended). 5 There should be assurance that the preliminary data are the manufacturer’s best representation of the aircraft and reasonable certainty that final data will not deviate to a large degree from these preliminary, but refined, estimates. Data derived from these predictive or preliminary techniques should be validated by available sources including, at least, the following:

text: (a) Manufacturer’s engineering report. Such report will explain the predictive method used and illustrating past success of the method on similar projects. For example, the manufacturer could show the application of the method to an earlier aircraft model or predict the characteristics of an earlier model and compare the results to final data for that model. (b) Early flight tests results. Such data will often be derived from aircraft certification tests, and should be used to maximum advantage for early FSTD validation. Certain critical tests, which would normally be done early in the aircraft certification programme, should be included to validate essential pilot training and certification manoeuvres. These include cases in which a pilot is expected to cope with an aircraft failure mode including engine failures. The early data available will, however, depend on the aircraft manufacturer’s flight test programme design and may not be the same in each case. However it is expected that the flight test programme of the aircraft manufacturer include provisions for generation of very early flight tests results for FSTD validation. 6 The use of preliminary data is not indefinite. The aircraft manufacturer’s final data should be available within 6 months after aircraft first ‘service entry’ or as agreed by the Authority, the FSTD operator and the aircraft manufacturer, but usually not later than 1 year. In applying for an interim qualification, using preliminary data, the FSTD operator and the Authority should agree upon the update programme. This will normally specify that the final data update will be installed in the FSTD within a period of 6 months following the final data release unless special conditions exist and a different schedule agreed. The FSTD performance and handling validation would then be based on data derived from flight test. Initial aircraft systems data should be updated after engineering tests. Final aircraft systems data should also be used for FSTD programming and validation.

text: JAR-FSTD A 2-C-146 2009-11-01

text: Bilaga 1

text: ACJ to JAR-FSTD A.045 (continued) 7 FSTD avionics should stay essentially in step with aircraft avionics (hardware & software) updates. The permitted time lapse between aircraft and FSTD updates is not a fixed time but should be minimal. It may depend on the magnitude of the update and whether the QTG and pilot training and certification is affected. Permitted differences in aircraft and FSTD avionics versions and the resulting effects on FSTD qualification should be agreed between the FSTD operator and the Authority. Consultation with the FSTD manufacturer is desirable throughout the agreement of the qualification process. 8 The following describes an example of the design data and sources which might be used in the development of an interim qualification plan. (a) The plan should consist of the development of a QTG based upon a mix of flight test and engineering simulation data. For data collected from specific aircraft flight tests or other flights the required designed model and data changes necessary to support an acceptable Proof of Match (POM) should be generated by the aircraft manufacturer. (b) In order that the two sets of data are properly validated, the aircraft manufacturer should compare their simulation model responses against the flight test data, when driven by the same control inputs and subjected to the same atmospheric conditions as were recorded in the flight test. The model responses should result from a simulation where the following systems are run in an integrated fashion and are consistent with the design data released to the FSTD manufacturer: (1) Propulsion (2) Aerodynamics (3) Mass properties (4) Flight controls (5) Stability augmentation (6) Brakes and landing gear. 9 For the qualification of FSTD of new aircraft types, it may be beneficial that the services of a suitably qualified test pilot are used for the purpose of assessing handling qualities and performance evaluation. NOTE: The Proof of Match should meet the relevant ACJ No. 1 to JAR-FSTD A.030 tolerances.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-147 JAR-FSTD A

text: Bilaga 2

text: JAR-FSTD H

text: Utbildningshjälpmedel för flygsimulering (helikopter)

text: Bilaga 2

text: CONTENTS (general layout)

text: JAR–FSTD H

text: HELICOPTER FLIGHT SIMULATION TRAINING DEVICES

text: FOREWORD

text: SECTION 1 – REQUIREMENTS

text: SUBPART A — APPLICABILITY SUBPART B — GENERAL SUBPART C — HELICOPTER FLIGHT SIMULATION TRAINING DEVICES

text: ACJ B — GENERAL ACJ C — HELICOPTER FLIGHT SIMULATION TRAINING DEVICES

text: C-1 2009-11-01

text: Bilaga 2

text: INTENTIONALLY LEFT BLANK 2009-11-01 C-2

text: Bilaga 2

text: CONTENTS (details)

text: JAR–FSTD H

text: Paragraph Page

text: SECTION 1 – REQUIREMENTS

text: General and Presentation 1-0-1

text: SUBPART A – APPLICABILITY

text: JAR–FSTD H.001 Applicability 1-A-1

text: SUBPART B – GENERAL

text: JAR–FSTD H.005 Terminology 1-B-1

text: SUBPART C – HELICOPTER FLIGHT SIMULATION TRAINING DEVICES

text: JAR–FSTD H.015 Application for FSTD Qualification 1-C-1 JAR–FSTD H.020 Validity FSTD Qualification 1-C-1 JAR–FSTD H.025 Rules governing FSTD Operators 1-C-1 JAR–FSTD H.030 Requirements for FSTDs qualified on or after 1-C-2 1 August 2008 JAR–FSTD H.031 Requirements for FFS qualified on or after 1-C-2 1 April 2001 and before 1 August 2008 JAR–FSTD H.032 Requirements for FTDs qualified on or after 1 January 2004 1-C-3 and before 1 August 2008 JAR–FSTD H.033 Requirements for FNPTs qualified on or after 1 January 2003 1-C-3 and before 1 August 2008 JAR–FSTD H.035 Requirements for FFSs approved or qualified 1-C-3 before 1 April 2001 JAR–FSTD H.036 Requirements for FTDs approved or qualified 1-C-3 before 1 January 2004 JAR–FSTD H.037 Requirements for FNPTs approved or qualified 1-C-4 before 1 January 2003 JAR–FSTD H.040 Changes to qualified FSTDs 1-C-4 JAR–FSTD H.045 Interim FSTD Qualification 1-C-5 JAR–FSTD H.050 Transferability of FSTD Qualification 1-C-5 Appendix 1 to FSTD Standards 1-C-6 JAR–FSTD H.030

text: C-3 2009-11-01

text: Bilaga 2

text: General and Presentation 2-0-1

text: ACJ B – GENERAL

text: ACJ FSTD H.005 Terminology, Abbreviations 2-B-1

text: ACJ C – HELICOPTER FLIGHT SIMULATION TRAINING DEVICES

text: ACJ No. 1 to FSTD Qualification – Application and Inspection 2-C-1 JAR-FSTD H.015 ACJ No. 2 to FSTD Evaluations 2-C-7 JAR-FSTD H.015 ACJ to Validity of FSTD Qualification 2-C-10 JAR-FSTD H.020 ACJ No. 1 to Quality System 2-C-10 JAR-FSTD H.025 ACJ No. 2 to Installations 2-C-16 JAR-FSTD H.025 ACJ No. 1 to FSTDs qualified on or after 1 August 2008 2-C-17 JAR-FSTD H.030 Appendix 1 to ACJ No. 1 Validation Test Tolerances 2-C-106 to JAR-FSTD H.030 Appendix 2 to ACJ No. 1 Validation Data Roadmap 2-C-108 to JAR-FSTD H.030 Appendix 3 to ACJ No. 1 Rotor Aerodynamic Modeling Techniques 2-C-110 to JAR-FSTD H.030 Appendix 4 to ACJ No. 1 Vibration Platforms for Helicopter FSTDs 2-C-112 to JAR-FSTD H.030 Appendix 5 to ACJ No. 1 Transport Delay Testing Method 2-C-114 to JAR-FSTD H.030 Appendix 6 to ACJ No. 1 Recurrent Evaluations – Validation Test Data Presentation 2-C-117 to JAR-FSTD H.030 Appendix 7 to ACJ No 1 Applicability 2-C-118 to JAR-FSTD H.030 Appendix 8 to ACJ No 1 Visual Display Systems 2-C-119 JAR–FSTD H.030 Appendix 9 to ACJ No 1 General technical Requirements for FSTD Qualification 2-C-122 JAR–FSTD H.030 Levels ACJ No. 2 to Guidance on Design & Qualification of Level ‘A’ Helicopter FFS 2-C-127 JAR-FSTD H.030 ACJ No. 3 to Guidance on Design & Qualification of Helicopter FTDs 2-C-129 JAR-FSTD H.030 ACJ No. 4 to Use of Data for Helicopter FTDs 2-C-132 JAR-FSTD H.030 ACJ No. 5 to Guidance on Design & Qualification of Helicopter FNPTs 2-C-133 JAR-FSTD H.030

text: 2009-11-01 C-4

text: Bilaga 2

text: ACJ No. 1 to Engineering Simulator Validation Data 2-C-141 JAR-FSTD H.030(c)(1) ACJ No. 2 to Engineering Simulator Validation Data – Approved Guidelines 2-C-142 JAR-FSTD H.030(c)(1) ACJ to FSTD H.035 FFS Approved or Qualified before 1 April 2001 2-C-144 ACJ to FSTD H.037 FNPTs Approved or Qualified before 1 January 2003 2-C-145 ACJ to FSTD H.045 New Helicopter FFS/FTD Qualification 2-C-146

text: INTENTIONALLY LEFT BLANK

text: C-5 2009-11-01

text: Bilaga 2

text: INTENTIONALLY LEFT BLANK 2009-11-01 C-6

text: Bilaga 2

text: FOREWORD

text: 3 The content has been prepared using the expertise available in this field and added to where necessary by making use of existing European regulations and the Federal Aviation Requirements of the United States of America where acceptable.

text: 4 JAR–FSTD H is issued with no National Variants. It may be felt that the document does not contain all of the detailed compliance and interpretative information which some Civil Aviation Authorities and Industry organisations would like to see. However, it is accepted that JAR–FSTD H should be applied in practice and the lessons learned embodied in future amendments. The Civil Aviation Authorities of the JAA are therefore committed to early amendment in the light of experience.

text: 5 Future development of the requirements of JAR–FSTD H, including the commitment in Paragraph 4, will be in accordance with the JAA’s Notice of Proposed Amendment (NPA) procedures. These procedures allow for the amendment of JAR–FSTD H to be proposed by any organisation or person.

text: 6 The Civil Aviation Authorities have agreed they should not unilaterally initiate amendment of their national codes without having made a proposal for amendment of JAR–FSTD H in accordance with the agreed procedure.

text: 7 Definitions and abbreviations of terms used in JAR–FSTD H that are considered generally applicable are contained in JAR–1, Definitions and Abbreviations. However, definitions and abbreviations of terms used in JAR–FSTD H that are specific to a Subpart of JAR–FSTD H are normally given in the Subpart concerned or, exceptionally, in the associated compliance or interpretative material.

text: 8 Amendments to the text in JAR–FSTD H are issued as Replacement Pages. These show an effective date and have the same status and applicability as JAR–FSTD H from that date.

text: 9 New, amended and corrected text will be enclosed within heavy brackets until a subsequent Amendment’ is issued.

text: 10 Comment/Response documents developed following Notices of Proposed Amendment (NPA) consultation have been produced by the JAA and are published on the JAA Internet Site: www.jaa.nl. Readers can also apply to Central JAA for copies of specific Comment/Response Documents as required.

text: F-1 2009-11-01

text: Bilaga 2

text: INTENTIONALLY LEFT BLANK 2009-11-01 F-2

text: Bilaga 2

text: SECTION 1 – REQUIREME NTS

text: 1 GENERAL 1.1 This Section contains the requirements for helicopter Flight Simulation Training Devices.

text: 2 PRESENTATION 2.1 The requirements of JAR–FSTD H are presented in two columns on loose pages, each page being identified by the date of issue and the Amendment number under which it is amended or reissued. 2.2 Sub-headings are in italic typeface. 2.3 Explanatory Notes not forming part of the requirements appear in smaller typeface. 2.4 New, amended and corrected text will be enclosed within heavy brackets until a subsequent ‘Amendment’ is issued. 2.5 After each paragraph, the various changes and amendments, if any since the initial issue, are indicated together with their date of issue.

text: INTENTIONALLY LEFT BLANK

text: 1-0-1 2009-11-01

text: Bilaga 2

text: Bilaga 2

text: SUBPART A - APPLICABILITY SUBPART A - APPLICABILITY

text: JAR–FSTD H.001 Applicability

text: JAR–FSTD H as amended applies to those persons, organisations or enterprises (Flight Simulation Training Devices (FSTD) operators) seeking initial qualification of FSTDs. The version of JAR-FSTD H agreed by the Authority and used for issue of the initial qualification shall be applicable for future recurrent qualifications of the FSTD unless recategorised. FSTD users shall also gain approval to use the FSTD as part of their approved training programmes despite the fact that the FSTD has been previously qualified.

text: 2009-11-01 1-A-1 JAR-FSTD H

text: SECTION 1

text: Bilaga 2

text: INTENTIONALLY LEFT BLANK JAR-FSTD H 1-A-2 2009-11-01

text: Bilaga 2

text: SUBPART B – GENERAL

text: JAR-FSTD H.005(f) (continued) JAR–FSTD H.005 Terminology account of helicopter to FSTD differences and the (See ACJ to FSTD H.005) operating and training ability of the organization.

text: Because of the technical complexity of FSTD (g) Flight Simulation Training Device qualification, it is essential that standard Operator (FSTD operator). That person, terminology is used throughout. The following organisation or enterprise directly responsible to principal terms and abbreviations shall be used in the Authority for requesting and maintaining the order to comply with JAR–FSTD (H). Further qualification of a particular FSTD. terms and abbreviations are contained in ACJ to (h) Flight Simulation Training Device User FSTD H.005. (FSTD User). The person, organization or (a) Flight Simulation Training Device enterprise requesting training, checking and testing (FSTD). A training device which is a Full Flight credits through the use of an FSTD. Simulator (FFS), a Flight Training Device (FTD), a (i) Flight Simulation Training Device Flight & Navigation Procedures Trainer (FNPT). Qualification (FSTD Qualification). The level of (b) Full Flight Simulator (FFS). A full size technical ability of an FSTD as defined in the replica of a specific type or make, model and series compliance document. helicopter flight deck, including the assemblage of (j) Qualification Test Guide (QTG). A all equipment and computer programmes necessary document designed to demonstrate that the to represent the helicopter in ground and flight performance and handling qualities of an FSTD operations, a visual system providing an out of the agree within prescribed limits with those of the flight deck view, and a force cueing motion system. helicopter and that all applicable regulatory It is in compliance with the minimum standards for requirements have been met. The QTG includes FFS Qualification. both the helicopter and FSTD data used to support (c) Flight Training Device (FTD). A full size the validation. replica of a specific helicopter type’s instruments, equipment, panels and controls in an open flight deck area or an enclosed helicopter flight deck, including the assemblage of equipment and computer software programmes necessary to represent the helicopter in ground and flight conditions to the extent of the systems installed in the device. It does not require a force cueing motion or visual system. It is in compliance with the minimum standards for a specific FTD Level of Qualification.

text: (d) Flight and Navigation Procedures Trainer (FNPT). A training device which represents the INTENTIONALLY LEFT BLANK flight deck or cockpit environment including the assemblage of equipment and computer programmes necessary to represent a helicopter in flight operations to the extent that the systems appear to function as in a helicopter. It is in compliance with the minimum standards for a specific FNPT Level of Qualification. (e) Other Training Device (OTD). A training aid other than FFS, FTD or FNPT which provides for training where a complete flight deck environment is not necessary.

text: (f) Flight Simulation Training Device User Approval (FSTD User Approval). The extent to which an FSTD of a specified Qualification Level may be used by persons, organisations or enterprises as approved by the Authority. It takes

text: 2009-11-01 1-B-1 JAR-FSTD H

text: SECTION 1

text: Bilaga 2

text: INTENTIONALLY LEFT BLANK JAR-FSTD H 1-B-2 2009-11-01

text: Bilaga 2

text: JAR-FSTD H.015 (continued) JAR–FSTD H.015 Application for FSTD FSTDs. Compliance monitoring shall include a Qualification feedback system to the Accountable Manager (See ACJ No. 1 to JAR- to ensure corrective action as necessary. FSTD H.015) (2) The Quality System shall include a (See ACJ No. 2 to JAR- Quality Assurance Programme that contains FSTD H.015) procedures designed to verify that the (a) The FSTD operator requiring evaluation specified performance, functions and of a FFS, FTD, or FNPT shall apply to the characteristics are being conducted in Authority giving 3 months notice. In exceptional accordance with all applicable requirements, cases this period may be reduced to one month standards and procedures. at the discretion of the Authority. (3) The Quality System and the (b) An FSTD Qualification Certificate will be Quality Manager shall be acceptable to the issued following satisfactory completion of an Authority. evaluation of the FFS, FTD or FNPT by the (4) The Quality System shall be Authority. described in relevant documentation.

text: (b) Updating. A link shall be maintained JAR–FSTD H.020 Validity of FSTD between the operator’s organization, the Qualification Authority and the relevant manufacturers to (See ACJ to JAR-FSTD incorporate important modifications, especially: H.020) (1) Helicopter modifications which are (a) A FSTD qualification is valid for 12 essential for training and checking shall be months unless otherwise specified by the introduced into all affected FSTDs whether or Authority. not enforced by an airworthiness directive. (b) A FSTD qualification revalidation can (2) Modification of FSTDs, including take place at any time within the 60 days prior to motion and visual systems (where applicable): the expiry of the validity of the qualification (i) When essential for training document. The new period of validity shall and checking, FSTD operators shall continue from the expiry date of the previous update their FSTDs (for example in the qualification document. light of data revisions). Modifications of (c) The Authority shall refuse, revoke, suspend the FSTD hardware and software which or vary a FSTD qualification, if the provisions of affect handling, performance and JAR–FSTD H are not satisfied. systems operation or any major modifications of the motion or visual system shall be evaluated to determine JAR–FSTD H.025 Rules Governing FSTD the impact on the original qualification Operators criteria. FSTD operators shall prepare (See ACJ No. 1 to JAR- amendments for any affected validation FSTD H.025) tests. The FSTD operator shall test the (See ACJ No. 2 to JAR- FSTD to the new criteria. FSTD H.025) (ii) The Authority shall be The FSTD operator shall demonstrate his advised in advance of any major capability to maintain the performance, functions changes to determine if the tests carried and other characteristics specified for the FSTD out by the FSTD operator are Qualification Level as follows: satisfactory. A special evaluation of the FSTD may be necessary prior to (a) Quality System returning it to training following the (1) A Quality System shall be modification. established and a Quality Manager designated (c) Installations. Ensure that the FSTD is to monitor compliance with, and the adequacy housed in a suitable environment which supports of, procedures required to ensure the safe and reliable operation. maintenance of the Qualification Level of

text: 2009-11-01 1-C-1 JAR-FSTD H

text: Bilaga 2

text: JAR-FSTD H.015 (continued) JAR-FSTD H.030 (continued)

text: (1) The FSTD operator shall ensure (2) Functions & subjective tests that the FSTD and its installation comply with (d) Data shall be of a standard that the local regulations for health and safety. satisfies the Authority before the FSTD can However, as a minimum all FSTD occupants gain a Qualification Level. and maintenance personnel shall be briefed on FSTD safety to ensure that they are (e) The FSTD operator shall submit a aware of all safety equipment and QTG in a form and manner which is acceptable procedures in the FSTD in case of to the Authority. emergency. (f) The QTG will only be approved after (2) The FSTD safety features such completion of an initial or upgrade evaluation, as emergency stops and emergency lighting and when all the discrepancies in the QTG shall be checked at least annually and have been addressed to the satisfaction of the recorded by the FSTD operator. Authority. After inclusion of the results of the tests witnessed by the Authority, the approved (d) Additional Equipment. Where QTG becomes the Master QTG (MQTG), which additional equipment has been added to the is the basis for the FSTD qualification and FSTD even though not required for subsequent recurrent FSTD evaluations qualification, it will be assessed to ensure that it does not adversely affect the quality of (g) The FSTD operator shall: training. Therefore any subsequent (1) Run the complete set of tests modification, removal or unserviceability of contained within the MQTG progressively such equipment could affect the qualification of between each annual evaluation by the the device. Authority. Results shall be dated and retained in order to satisfy both the FSTD operator and the Authority that FSTD

text: JAR–FSTD H.030 Requirements for FSTD

text: standards are being maintained; and

text: qualified on or after 1

text: August 2008 (2) Establish a Configuration Control (See Appendix 1 to JAR– System to ensure the continued integrity of FSTD H.030) the hardware and software of the qualified (See ACJ No. 1 to JAR- FSTD. FSTD H.030) (See ACJ No. 2 to JAR- FSTD H.030) JAR-FSTD H.031 Requirements for FFS (See ACJ No. 3 to JAR- qualified on or after 1 FSTD H.030) April 2001 and before 1 (See ACJ No. 4 to JAR- August 2008 FSTD H.030) (See ACJ No. 5 to JAR- FSTD H.030) Any FFS submitted for initial evaluation on or after 1 April 2001 and before 1 August 2008, shall automatically be granted an equivalent (a) Any FSTD submitted for initial evaluation qualification under JAR-FSTD H with effect on or after 1 August 2008 will be evaluated from the re-evaluation conducted at the end of against applicable JAR-FSTD H criteria for the the current validity period. This re-evaluation, Qualifications levels for which qualification has and all future re-evaluations, will be conducted been applied. Recurrent evaluations of a FSTD in accordance with the requirements of the will be based on the same version of JAR- same version of JAR-STD 1H, which was FSTD H that was applicable for its initial applicable for its last evaluation prior to evaluation. An upgrade will be based upon the implementation of JAR-FSTD H. Any upgrade currently applicable version of JAR-FSTD H. will be based on the currently applicable version of JAR-FSTD H. (b) A FSTD shall be assessed in those areas which are essential to completing the flight crew member training, testing and checking process as applicable. (c) The FSTD shall be subjected to: (1) Validation tests and

text: JAR-FSTD H 1-C-2 2009-11-01

text: Bilaga 2

text: JAR-FSTD H.032 (continued) JAR-FSTD H.035(c) (continued)

text: JAR-FSTD H.032 Requirements for Flight circumstances exceed originally issued

text: Training Devices (FTD) National credits.

text: qualified on or after 1

text: (b) FFS’s neither recategorised nor with

text: January 2004 and before

text: an approval maintained under the Grandfather

text: 1 August 2008

text: Rights provision, will be qualified in

text: accordance with JAR–FSTD H.030.

text: Any FTD submitted for initial evaluation on or (c) FFS that are not recategorised but that

text: after 1 January 2004 and before 1 August have a primary reference document used for

text: 2008, shall automatically be granted an their testing may be qualified by the Authority

text: equivalent qualification under JAR-FSTD H to an equivalent JAR–FSTD H Qualification

text: with effect from the re-evaluation conducted at Level, either AG, BG, CG or DG. An upgrade

text: the end of the current validity period. This re- requires the recategorisation of the FFS.

text: evaluation, and all future re-evaluations, will be (1) To gain and maintain an conducted in accordance with the equivalent Qualification Level, these FFS requirements of the same version of JAR-STD shall be assessed in those areas which are 2H, which was applicable for its last evaluation essential to completing the flight crew prior to implementation of JAR-FSTD H. Any member training and checking process, as upgrade will be based on the currently applicable. applicable version of JAR-FSTD H.

text: (2) The FFS shall be subjected to:

text: (i) Validation tests; and

text: JAR-FSTD H.033 Requirements for Flight &

text: Navigation Procedures (ii) Functions and subjective

text: Trainers (FNPT) qualified tests.

text: on or after 1 January 2003

text: (d) FFS that are not recategorised and

text: and before 1 August 2008

text: that do not have a primary reference document

text: used for their testing, shall be qualified by

text: special arrangement. Such FFS will be issued Any FNPT submitted for initial evaluation on or with a Special Category and shall be subjected after 1 January 2003 and before 1 August to functions and subjective tests corresponding 2008, shall automatically be granted an to those detailed within this document. In equivalent qualification under JAR-FSTD H addition any previously recognised validation with effect from the re-evaluation conducted at test shall be used. the end of the current validity period. This re-

text: evaluation, and all future re-evaluations, will be

text: conducted in accordance with the

text: JAR–FSTD H.036 Requirements for Flight

text: requirements of the same version of JAR-STD

text: Training Devices

text: 3H, which was applicable for its last evaluation

text: approved or qualified

text: prior to implementation of JAR-FSTD H. Any

text: before 1 January 2004

text: upgrade will be based on the currently

text: applicable version of JAR-FSTD H.

text: No longer applicable.

text: JAR–FSTD H.035 Requirements for Full Flight Simulators approved or qualified before 1 April 2001

text: (See ACJ to JAR-FSTD

text: (a) FFS approved or qualified in

text: accordance with national regulations of JAA

text: Member States before 1 April 2001 will either

text: be recategorised or will continue to maintain

text: their approval under the Grandfather Rights INTENTIONALLY LEFT BLANK

text: provision, in accordance with sub-paragraphs

text: (c) and (d) below. For FFS which are not re-

text: categorized, maximum credit shall under no

text: 2009-11-01 1-C-3 JAR-FSTD H

text: Bilaga 2

text: JAR-FSTD H.040 (continued)

text: JAR–FSTD H.037 Requirements for Flight

text: (1) Helicopter modifications which

text: Navigation Procedures

text: could affect FSTD qualification.

text: Trainers approved or

text: (2) FSTD hardware and or software

text: qualified before 1 January

text: modifications which could affect the

text: handling qualities, performance or system (See ACJ to JAR-FSTD representations. H.037)

text: (3) Relocation of the FSTD; and (a) FNPTs or devices approved or

text: qualified in accordance with national (4) Any deactivation of the FSTD.

text: regulations of JAA Members States before 1 The Authority may complete a special January 2003 will either be recategorised or evaluation following major changes or when a will continue to maintain their approval under FSTD appears not to be performing at its initial the Grandfather Rights provision, in Qualification Level. accordance with sub-paragraphs (c) and (d)

text: below. Grandfather Rights shall cease to exist (b) Upgrade of a FSTD. A FSTD may be st on the 1 January 2009. For FNPT which are upgraded to a higher Qualification Level.

text: not recategorised maximum credits shall under Special evaluation is required before the award

text: no circumstances exceed originally issued of a higher Level of Qualification.

text: National credits. (1) If an upgrade is proposed the

text: (b) Recategorised FNPTs will be qualified FSTD operator shall seek the advice of the

text: in accordance with JAR-FSTD H.030. Authority and give full details of the

text: modifications. If the upgrade evaluation (c) FNPTs that are not recategorised, but does not fall upon the anniversary of the that have a primary reference document used original qualification date, a special for their testing, may continue under previous evaluation is required to permit the FSTD to authorisation, provided that they continue to continue to qualify even at the previous comply with the primary reference document. Qualification Level.

text: (1) To gain and maintain their (2) In the case of a FSTD upgrade, equivalent qualification level, these FNPTs an FSTD operator shall run all validation shall be assessed in those areas which are tests for the requested Qualification Level. essential to completing the flight crew Results from previous evaluations shall not member training process, as applicable. be used to validate FSTD performance for

text: (2) The devices shall be subjected the current upgrade.

text: to: (c) Relocation of a FSTD

text: (i) Validation tests and (1) In instances where a FSTD is

text: (ii) Functions and subjective moved to a new location, the Authority shall

text: tests. be advised before the planned activity along

text: with a schedule of related events. (d) FNPTs that are not recategorised and

text: that do not have a primary reference document (2) Prior to returning the FSTD to

text: used for their testing shall be qualified by service at the new location the FSTD

text: special arrangement. Such FNPTs will be operator shall perform at least one third of

text: issued with a Special Category and shall be the validation tests and all functions and

text: subjected to Functions and Subjective Tests subjective tests to ensure that the FSTD

text: corresponding to those detailed within this performance meets its original qualification

text: document. In addition any previously standard. A copy of the test documentation

text: recognized Validation tests shall be used. shall be retained together with the FSTD

text: records for review by the Authority.

text: (3) An evaluation of the FSTD in

text: JAR–FSTD H.040 Changes to qualified

text: accordance with its original JAA

text: FSTD

text: qualification criteria shall be at the

text: (a) Requirement to notify major changes discretion of the Authority.

text: to a FSTD. The operator of a qualified FSTD (d) Deactivation of a currently qualified shall inform the Authority of proposed major FSTD changes such as:

text: JAR-FSTD H 1-C-4 2001-11-01

text: Bilaga 2

text: JAR-FSTD H.040(d) (continued)

text: (1) If a FSTD operator plans to remove a FSTD from active status for prolonged periods, the Authority shall be notified and suitable controls established for the period during which the FSTD is inactive. (2) The FSTD operator shall agree a procedure with the Authority to ensure that the FSTD can be restored to active status at its original Qualification Level.

text: JAR–FSTD H.045 Interim FSTD Qualification

text: (See ACJ to JAR-FSTD H.045)

text: (a) In the case of new helicopter programmes, special arrangements shall be made to enable an interim Qualification Level to be achieved. (b) For Full Flight Simulators, an interim INTENTIONALLY LEFT BLANK Qualification Level will only be granted at levels A, B or C (c) Requirements, details relating to the issue, and the period of validity of an interim Qualification Level will be decided by the Authority.

text: JAR–FSTD H.050 Transferability of FSTD Qualification

text: When there is a change of FSTD operator: (a) The new FSTD operator shall advise the Authority in advance in order to agree upon a plan of transfer of the FSTD. (b) At the discretion of the Authority, the FSTD shall be subject to an evaluation in accordance with its original JAA qualification criteria. (c) Provided that the FSTD performs to its original standard, its original Qualification Level shall be restored. Revised user approval(s) may also be required.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 1-C-5 JAR-FSTD H

text: Bilaga 2

text: Appendix 1 to JAR-FSTD H.030 Flight Simulation Training Device Standards General

text: This appendix describes the minimum Full Flight Simulator (FFS), Flight Training Device (FTD) and Flight Navigation Procedures Trainer (FNPT) requirements for qualifying devices to the required Qualification Levels. Certain requirements included in this section shall be supported with a statement of compliance (SOC) and, in some designated cases, an objective test. The SOC will describe how the requirement was met. The test results shall show that the requirement has been attained. In the following tabular listing of FSTD standards, statements of compliance are indicated in the compliance column. For FNPT use in Multi-Crew Co-operation (MCC) training the general technical requirement are expressed in the MCC column with additional systems, instrumentation and indicators as required for MCC training and operation. For MCC (Multi Crew Co-operation) minimum technical requirements are as for Level II or III, with the following additions or amendments: 1 Multi engine and multi pilot helicopter 2 Performance reserves, in case of an engine failure, to be in accordance with CAT. A criteria. 3 Anti icing or de-icing systems 4 Fire detection / suppression system 5 Dual controls 6 Autopilot with upper modes 7 2 VHF transceivers 8 2 VHF NAV receivers (VOR, ILS, DME) 9 1 ADF receiver 10 1 Marker receiver 11 1 transponder 12 Weather radar

text: The following indicators shall be located in the same positions on the instrument panels of both pilots: 1 Airspeed 2 Flight attitude 3 Altimeter and radio altimeter 4 HSI 5 Vertical speed 6 ADF 7 VOR, ILS, DME 8 Marker indication 9 Stop watch

text: JAR-FSTD H 1-C-6 2001-11-01

text: App SECT

text: 20 e

text: n

text: 09 d IO

text: FSTD STANDARDS FFS FTD FNPT COMPLIANCE ix 1 N

text: -11 t 1

text: LEVEL LEVEL LEVEL o JAR-

text: 1 1.1 General A B C D 1 2 3 I II III MCC

text: FSTD H. 9 9 9 9 9 9 a.1 A flight deck that is a full-scale replica of the

text: helicopter simulated. Additional required

text: crewmember duty stations and those required 0 3 bulkheads aft of the pilot seats are also 0 (c

text: considered part of the cockpit and shall o n replicate the helicopter. ti n ued) 9 9 9 9 9 A flight deck that replicates the helicopter.

text: 9 9 9 9 a.2 The flight deck, including the instructor’s

text: station is fully enclosed.

text: 9 9 9 9 9 9 9 A flight deck, including the instructor’s station

text: 1 that is sufficiently closed off to exclude

text: -C

text: distractions.

text: -7 JA

text: 9 9 9 9 9 9 9 For FTD Level 1 as appropriate for the replicated b.1 Full size panels with functional controls, system switches, instruments and primary and

text: secondary flight controls, which shall be The use of electronically displayed images with

text: operating in the correct direction and with the physical overlay incorporating operable switches,

text: knobs and buttons may be acceptable. This option correct range of movement. is not acceptable for analogue instruments in FFS.

text: 9 9 9 9 The use of electronically displayed images with Functional controls, switches, instruments and physical overlay incorporating operable switches, primary and secondary flight controls sufficient knobs and buttons is acceptable. for the training events to be accomplished,

text: shall be located in a spatially correct area of

text: the flight deck.

text: R-FSTD

text: H TSFS 20

text: Bilaga 2 09 :87

text: JA A Bi TSFS 20

text: pp

text: R la

text: en g

text: -F di a S 2

text: T x 1

text: D 09

text: to

text: H :87

text: FSTD STANDARDS FFS FTD FNPT COMPLIANCE JAR-

text: LEVEL LEVEL LEVEL

text: FSTD H.

text: 1.1 General A B C D 1 2 3 I II III MCC

text: c.1 Lighting for panels and instruments shall be as 9 9 9 9 9 9 030 per the helicopter. (co 9 9 9 9 9 nti Lighting for panels and instruments shall be nue sufficient for the training events d Flight deck ambient lighting environment shall be 9 9 ) c.2 dynamically consistent with the visual display and sufficient for the training event. The ambient lighting should provide an 9 9 9 9 9 9 9 1- even level of illumination which is not

text: distracting to the pilot. 9 9 9 9 9 9 9 9 9 9 d.1 Relevant flight deck circuit breakers shall be located as per the helicopter and shall function accurately when involved in operating procedures or malfunctions requiring or involving flight crew response.

text: 9 9 9 9 9 9 9 9 9 9 Effects of Cg, mass and configuration changes are not e.1 Effect of aerodynamic changes for various combinations of airspeed and power normally required for FNPT Level I. encountered in flight, including the effect of change in helicopter attitude, aerodynamic and propulsive forces and moments, altitude, temperature, mass, centre of gravity location and configuration.

text: Aerodynamic and environment modelling shall 9

text: be sufficient to permit accurate systems operation and indication.

text: SECT

text: 20 09- 11

text: IO

text: -01 N

text: App SECT

text: 20 e

text: n

text: 09 d IO

text: ix 1 N

text: -11 t 1

text: FSTD STANDARDS FFS FTD FNPT COMPLIANCE o JAR- -0 LEVEL LEVEL LEVEL

text: 1.1 General FSTD H.

text: A B C D 1 2 3 I II III MCC

text: e.2 Aerodynamic modelling which includes ground 9 9 9 9 9 9 9 0 effect, effects of airframe and rotor icing (if 3 0 applicable), aerodynamic interference effects ( c between the rotor wake and fuselage, influence o n ti of the rotor on control and stabilization systems, n ued) and representations of nonlinearities due to sideslip, vortex ring and retreating blade stall.

text: f.1 Validation flight test data shall be used as the 9 9 9 9 basis for flight and performance and systems characteristics.

text: 1 -C

text: -9 JA Representative/generic aerodynamic data 9 9 9 9 9 9 9 Aerodynamic data need not be necessarily

text: tailored to the helicopter with fidelity sufficient based on flight test data. to meet the objective tests and sufficient to permit accurate system operation and indication.

text: g.1 All relevant flight deck instrument indications 9 9 9 9 9 9 9 9 9 9 9 automatically respond to control movement by a crewmember, helicopter performance, or external simulated environmental effects upon the helicopter

text: R-FSTD

text: H TSFS 20

text: Bilaga 2 09 :87

text: JA A Bi TSFS 20

text: pp

text: R la

text: en g

text: -F di a S 2

text: T x 1

text: D 09

text: to

text: H :87

text: LEVEL LEVEL LEVEL

text: FSTD H.

text: 1.1 General A B C D 1 2 3 I II III MCC

text: 9 9 9 9 9 9 9 For FTD 1 applies where the appropriate systems h.1 All relevant communications, navigation, 030 caution and warning equipment shall are replicated. correspond to that installed in the helicopter. (co

text: nti All simulated navigation aids within range nue shall be usable without restriction. Navigational data shall be capable of being d ) updated.

text: 9 9 9 9 h.2 Navigation equipment corresponding to that 1- of a helicopter, with operation within the

text: C

text: tolerances typically applied to the airborne

text: 0 equipment. This shall include communication

text: equipment (interphone and air/ground

text: communications systems).

text: 9 9 9 9 9 9 9 9 9 9 9 For FFSs and FTDs the navigation database h.3 Navigational data with the corresponding approach facilities. Navigation aids should should be updated within 28 days.

text: be usable within range without restriction For FNPTs complete navigational data for at least 5 different European airports with corresponding precision and non-precision approach procedures including current updating within a period of 3 months.

text: 9 9 9 9 The Authority will consider options to this standard i.1 In addition to the flight crewmember stations, at based on unique cockpit configurations. least two suitable seats for the instructor and an Any additional seats installed shall be equipped with additional observer shall be provided permitting similar safety provisions. adequate vision to the crewmembers' panel and

text: forward windows. Observer seats need not

text: represent those found in the helicopter but SECT

text: shall be adequately secured to the floor of the flight

text: simulator, fitted with positive restraint devices and

text: be of sufficient integrity to safely restrain the

text: occupant during any known or predicted motion IO

text: -01 N

text: system excursion.

text: App SECT

text: 20 e

text: n

text: 09 d IO

text: -11 t 1

text: LEVEL LEVEL LEVEL o JAR-

text: FSTD H.

text: 9 9 9 9 9 9 9 The instructor's and observer’s seats need not i.2 Crewmember seats shall afford the capability for the represent those found in the helicopter.

text: occupants to be able to achieve the design eye 0 3 reference position. In addition to the flight 0 (c crewmember stations, at least two suitable seats for o n the instructor and an additional observer shall be ti n ued) provided permitting adequate vision to the

text: crewmembers' panel and forward windows.

text: 1- C-1

text: 1 JA

text: R-FSTD

text: H TSFS 20

text: Bilaga 2 09 :87

text: JA A Bi TSFS 20

text: pp

text: R la

text: en g

text: -F di a S 2

text: T x 1

text: D 09

text: to

text: H :87

text: LEVEL LEVEL LEVEL

text: FSTD H.

text: 1.1 General A B C D 1 2 3 I II III MCC

text: FFS systems shall simulate the applicable 9 9 9 9 j.1 helicopter system operation, both on the ground 030 and in flight. Systems shall be operative to the extent that (co normal, abnormal, and emergency operating nti procedures appropriate to the simulator nue application can be accomplished. Once activated, d proper system operation shall result from system ) management by the flight crew and not require input from instructor controls. 1- FTD systems represented shall be fully operative 9 9 9 j.2 to the extent that normal, abnormal and

text: C

text: -1 emergency operating procedures can be 2 accomplished. Once activated, proper system operation shall result from system management by the flight crew and not require input from instructor controls. The systems should be operative to the extent 9 9 9 9 j.3 that it should be possible to perform normal, abnormal, and emergency operations appropriate to a helicopter as required for training. Once activated, proper systems operations should result from the system management by the crewmember and not require any further input from the instructor’s controls. The instructor shall be able to control system 9 9 9 9 9 9 9 9 9 9 9 FNPT I: applicable only to enable the instructor to k.1 variables and insert abnormal or emergency carry out selective failure of basic flight conditions into the helicopter systems. instruments and navigation equipment.

text: For FNPT Level I: Ability to set the FNPT to Independent freeze and reset facilities shall be minimum IMC speed or above provided.

text: SECT

text: 20 09- 11

text: IO

text: -01 N

text: App SECT

text: 20 e

text: n

text: 09 d IO

text: ix 1 N

text: -11 t 1

text: 1.1 General A B C D 1 2 3 I II III MCC FSTD H.

text: 9 9 9 9 For Level A only static control force

text: l.1 Control forces and control travel which correspond to that of the replicated helicopter. Control forces characteristics need to be tested. 0 3 shall react in the same manner as in the helicopter 0 (c under the same flight conditions. o n 9 9 9 For FTD level 1 as appropriate for the system ti Control forces and control travel shall be n ued) training required representative of the replicated helicopter under the

text: same flight conditions as in the helicopter..

text: 9 Only static control force characteristics need to be Control forces and control travel shall broadly tested. correspond to that of a helicopter.

text: 9 9 9 Only static control force characteristics need to be 1- Control forces and control travels shall respond in tested. C-1 the same manner under the same flight conditions

text: 3 as in a helicopter.

text: JA

text: Cockpit control dynamics, which replicate the 9 9 9 9 9 For helicopters with irreversible control systems, l.2 helicopter simulated. Free response of the controls measurements may be obtained on the ground. Engineering validation or helicopter manufacturer shall match that of the helicopter within the given rationale will be submitted as justification for tolerance. Initial and upgrade evaluation will include ground test or to omit a configuration. control free response (cyclic, collective, and pedal) measurements recorded at the controls. The For FFS requiring static and dynamic tests at the controls, special test fixtures will not be required measured responses shall correspond to those of during the initial evaluations if the FSTD operator’s the helicopter in ground operations, hover, climb, QTG shows both test fixture results and alternate

text: cruise, and auto-rotation. test method results, such as computer data plots,

text: which were obtained concurrently. Use of the alternate method during initial evaluation may then satisfy this test requirement.

text: FTD Level 2 data can be representative/generic R-FSTD and need not necessarily be based on flight test

text: data.

text: H TSFS 20

text: Bilaga 2 09 :87

text: JA A Bi TSFS 20

text: pp

text: R la

text: en g

text: -F di a S 2

text: T x 1

text: D 09

text: to

text: H :87

text: Ground handling and aerodynamic programming to 9 9 9 9 Level A can utilise generic simulation of ground JARm.1 include the following: effect and ground handling. FSTD H. Ground effect - hover and transition IGE.

text: (Ground reaction - reaction of the helicopter upon contact with the landing surface during landing to 030 include strut deflections, tire or skid friction, side forces, and other appropriate data, such as weight (co and speed, necessary to identify the flight condition nti and configuration. nue

text: Ground handling characteristics -- control inputs to d ) include braking, deceleration turning radius and the effects of crosswind.

text: 1- 9 9

text: Ground handling and aerodynamic ground effects

text: C

text: models should be provided to enable lift-off, hover,

text: 4 and touch down effects to be simulated and harmonized with the sound and visual system.

text: Generic ground handling and aerodynamic 9 9 9 ground effects models should be provided to enable lift-off, hover, and touch down effects to be simulated and harmonized with the sound and visual system.

text: SECT

text: 20 09- 11

text: IO

text: -01 N

text: App SECT

text: 20 e

text: n

text: 09 d IO

text: ix 1 N

text: -11 t 1

text: Instructor controls for n.1 9 9 9 9 9 9 9 9 9 9 0 (i) Wind speed and direction 3 0 9 9 9 9 9 9 9 9 9 9 (c (ii) Turbulence o n ti 9 9 9 9 Examples: Generic atmospheric models of local wind n (iii) Other atmospheric models to support the ued) patterns around mountains and structures.. required training. 9 9 9 9 9 9 9 9 9 (iv) Adjustment of cloud base and visibility.

text: 9 9 9 9 9 9 9 9 9 9 9 (v) Temperature and barometric pressure.

text: C-1 Representative stopping and directional control 9 9 o.1 forces for at least the following landing surface 5 conditions based on helicopter related data, for a

text: JA

text: running landing.

text: (i) Dry

text: (ii) Wet (soft surface and hard surface)

text: (iii) Icy

text: (iv) Patchy Wet

text: (v) Patchy Icy

text: Representative brake and tire failure dynamics. 9 9 p.1

text: Cockpit control dynamics, which replicate the 9 9 9 9 9 9 9 9 For helicopters with irreversible control systems, q.1 helicopter simulated. Free response of the measurements may be obtained on the ground.

text: controls shall match that of the helicopter within Engineering validation or helicopter manufacturer R-FSTD the given tolerance. Initial and upgrade rationale will be submitted as justification for evaluation will include control free response ground test or to omit a configuration. (cyclic, collective, and pedal) measurements For FFS requiring static and dynamic tests at the recorded at the controls. The measured controls, special test fixtures will not be required H responses shall correspond to those of the during the initial evaluations if the FSTD perator’s helicopter in ground operations, hover, climb, QTG shows both test fixture results and alternate TSFS 20

text: cruise, and auto-rotation. test method results, such as computer data plots, which were obtained concurrently. Use of the Bilaga 2 alternate method during initial evaluation may

text: 09 :87

text: JA A Bi TSFS 20

text: pp

text: R la

text: en g

text: -F di a S 2

text: T x 1 D FSTD STANDARDS FFS FTD FNPT COMPLIANCE 09 to

text: H :87

text: LEVEL LEVEL LEVEL JAR-

text: then satisfy this test requirement. FTD Level 2 aerodynamic data can be representative/generic and need not necessarily be based on flight test 030 data. (co nti (1) Transport delay. Transport delay is the 9 9 9 9 9 9 9 9 9 9 9 For FTD Level 1, only instrument response is nue r.1 time between control input and the individual required within a maximum permissible delay of d hardware (systems) responses. 200 milliseconds )

text: For Level 'A' & 'B' FFS and Level 2 FTD the As an alternative, a Latency test may be used maximum permissible delay is 150 milliseconds to demonstrate that the flight simulator

text: C system does not exceed the permissible For Level 'C' & ‘D’ FFS and Level 3 FTD the -1 delay. maximum permissible delay is 100 milliseconds

text: (2) Latency. Relative response of the 9 9 9 9 9 9 9 For FTD Level 1 and FNPT Level I, only instrument visual system, cockpit instruments and initial response is required within a maximum permissible motion system response shall be coupled delay of 200 milliseconds closely to provide integrated sensory cues. For Level 'A' & 'B' FFS, Level 2 FTD and FNPT These systems shall respond to abrupt pitch, Level II and III the maximum permissible delay is roll, and yaw inputs at the pilot's position within 150 milliseconds the permissible delay, but not before the time, when the helicopter would respond under the For Level 'C' & 'D' FFS and Level 3 FTD the same conditions. Visual scene changes from maximum permissible delay is 100 milliseconds steady state disturbance shall occur within the system dynamic response limit but not before the resultant motion onset.

text: SECT

text: 20 09- 11

text: IO

text: -01 N

text: App SECT

text: 20 e

text: n

text: 09 d IO

text: ix 1 N

text: -11 t 1

text: 9 9 9 9 9 Recommended for FTD Level 1,FNPT Level I and s.1 A means for quickly and effectively testing II FSTD programming and hardware. This may 0 3 include an automated system, which could Automatic flagging of "out-of-tolerance" tests results 0 (c be used for conducting at least a portion of is encouraged. o n the tests in the QTG. ti n ued) 9 9 9 Self-testing for FSTD hardware and programming to determine compliance with the FSTD performance tests. Evidence of testing shall include FSTD number, date, time, conditions, tolerances, and the appropriate 1- dependent variables portrayed in comparison C-1 with the helicopter standard

text: 7 9 9 9 9 9 9 9 JA t.1 A system allowing for timely continuous updating of FSTD hardware and programming consistent with helicopter modifications. 9 9 9 9 9 9 9 9 9 9 9 u.1 The FSTD operator shall submit a Qualification Test Guide in a form and manner acceptable to the Authority. A recording system shall be provided that will enable the FSTD performance to be compared with QTG criteria. 9 9 9 9 9 9 9 9 9 9 9 v.1 FSTD computer capacity, accuracy, resolution and dynamic response sufficient for the Qualification Level sought. 9 9 9 9 9 9 9 9 9 9 9 w.1 Daily preflight documentation either in the daily R-FSTD log or in a location easily accessible for review.

text: H TSFS 20

text: Bilaga 2 09 :87

text: JA A Bi TSFS 20

text: pp

text: R la

text: en g

text: -F di a S 2

text: T x 1

text: D 09

text: to

text: H :87

text: LEVEL LEVEL LEVEL

text: FSTD H.

text: 1.2 Motion System A B C D 1 2 3 I II III MCC

text: 9 9 9 9 Motion tests to demonstrate that each axes onset a.1 Motion cues as perceived by the pilot shall be 030 cues are properly phased with pilot input and representative of the helicopter, e.g. touchdown helicopter response. (co cues should be a function of the simulated rate of nti descent. nue

text: d The instructor's and observer’s seats need not ) b.1 A motion system: represent those found in the helicopter.

text: Having a minimum of 3 degrees of freedom 1- 9 (pitch, roll, heave) to accomplish the required C task. -1 8

text: 6 degrees of freedom synergistic platform

text: For level B, a reduced motion performance

text: motion system

text: envelope is acceptable. 9 9 9

text: 9 9 9 9 See para 1.1 (r.1) above. c.1 A means of recording the motion response time

text: as required

text: SECT

text: 20 09- 11

text: IO

text: -01 N

text: App SECT

text: 20 e

text: n

text: 09 d IO

text: ix 1 N

text: -11 t 1

text: 1.2 Motion System A B C D 1 2 3 I II III MCC FSTD H.

text: 9 9 9 9 d.1 Special effects programming to include the For level A it may be of a generic nature following: sufficient to accomplish the required tasks. 0 3 0 (c (1) Runway rumble, oleo deflections, effects o of groundspeed and uneven surface n ti characteristics. n ued)

text: (2) Buffet due to translational lift.

text: (3) Buffet during extension and retraction of landing gear. See Appendix 4 to ACJ No. 1 to JAR-FSTD H.030 para 2.2 on Vibration Platforms for 1- (4) Buffet due to high speed and retreating Helicopter FSTDs. C-1 blade stall.

text: 9 (5) Buffet due to vortex ring.

text: JA

text: (6) Representative cues resulting from;

text: (i) touchdown

text: (ii) translational lift.

text: (7) Antitorque device ineffectiveness.

text: (8) Buffet due to turbulence.

text: R-FSTD

text: H TSFS 20

text: Bilaga 2 09 :87

text: JA A Bi TSFS 20

text: pp

text: R la

text: en g

text: -F di a S 2

text: T x 1

text: D 09

text: to

text: H :87

text: LEVEL LEVEL LEVEL

text: FSTD H.

text: 9 e.1 Characteristic vibrations/buffets that result Statement of Compliance required. 030 from operation of the helicopter and which can be sensed in the cockpit. Simulated Tests required with recorded results which (co cockpit vibrations to include seat(s), flight allow the comparison of relative amplitudes nti nue controls and instrument panel(s), although versus frequency in the longitudinal, lateral these need not be tested independently. and vertical axes with helicopter data.. d ) Steady state tests are acceptable.

text: See Appendix 4 to ACJ No. 1 to JAR-FSTD 1- H.030 para 2.2 on Vibration Platforms for C Helicopter FSTDs.

text: -2 0

text: SECT

text: 20 09- 11

text: IO

text: -01 N

text: App SECT

text: 20 e

text: n

text: 09 d IO

text: ix 1 N -11 FSTD STANDARDS FFS FTD FNPT COMPLIANCE t 1 o LEVEL LEVEL LEVEL JAR-

text: 1 1.3 Visual System

text: A B C D 1 2 3 I II III MCC

text: FSTD H. 9 9 9 9 9 9 9 9 9 The choice of the display system and of the field of a.1 Visual system capable of meeting all the standards view requirements should fully consider the of this paragraph and the respective paragraphs of intended use of the FSTD. The balance between validation tests as well as functions and subjective 0 training and testing/checking may influence the 3 0 tests as applicable to the Level of Qualification choice and geometry of the display system. In ( c requested by the FSTD operator. addition the diverse operational requirements o n should be addressed. ti n ued) Visual system capable of providing at least a 45 9 b.1 degree horizontal and 30 degree vertical field of

text: view simultaneously for each pilot.

text: Visual system capable of providing at least a 75 9

text: degrees horizontal and 40 degrees vertical field of

text: view simultaneously for each pilot.

text: C-2 9 9 9 9 A minimum of 75 degrees horizontal field of view on “Continuous”, cross-cockpit, minimum visual field of either side of the zero degree azimuth line relative 1 view providing each pilot with 150 degrees JA to the helicopter fuselage is required. horizontal and 40 degrees vertical

text: 9 9 A minimum of 75 degrees horizontal field of view on b.2 “Continuous,” cross-cockpit, minimum visual field of either side of the zero degree azimuth line relative view providing each pilot with 150 degrees to the helicopter fuselage is required. This will allow horizontal and 60 degrees vertical an offset per side of the horizontal field of view if

text: required for the training.

text: Where training tasks require extended fields of view beyond the 150 degrees x 60 degrees, then such extended fields of view should be provided.

text: .“Continuous” cross cockpit, minimum visual field of 9 A minimum of 75 degrees of horizontal field of view b.3 on either side of zero degrees azimuth line relative view providing each pilot with180 degrees horizontal and 60 degrees vertical to the helicopter fuselage is required. This will allow an offset per side of the horizontal field of view if required for the training.

text: R-FSTD

text: Where training tasks require extended fields of view beyond the 180 degrees x 60 degrees, then such extended fields of view shall be provided.

text: H TSFS 20

text: Bilaga 2 09 :87

text: JA A Bi TSFS 20

text: pp

text: R la

text: en g

text: -F di a S 2

text: T x 1

text: D 09

text: to

text: H :87

text: LEVEL LEVEL LEVEL

text: FSTD H.

text: 1.3 Visual System A B C D 1 2 3 I II III MCC

text: 9 9 9 9 9 9 9 9 9 c.1 A means of recording the visual response time for 030

text: the visual system shall be provided. (co 9 9 For Level 'A', Visual cueing sufficient to support d.1 Visual cues to assess rate of change of height, nti changes in approach path by using FATO translational displacements and rates, during takeoff nue perspective and landing. d ) 9 9 9 9 9 9 9 . Visual cues to assess rate of change of height,

text: height AGL, translational displacements and rates,

text: 1- during takeoff, low altitude/low airspeed

text: C manoeuvring, hover, and landing. -2 9 9 9 9 9 9 9 9 9 Statement of compliance required. Test required 2 e.1 Test procedures to quickly confirm visual system

text: colour, RVR, focus, intensity, level horizon, and

text: attitude as compared with the specified parameters.

text: 9 9 9 9 9 9 9 Statement of compliance required. Test required f.1 A minimum of 10 levels of occulting. This capability

text: should be demonstrated by a visual model through

text: each channel.

text: 9 9 9 9 9 9 9 Statement of compliance required. Test required g.1 Surface (Vernier) resolution shall be demonstrated

text: by a test pattern of objects shown to occupy a visual

text: angle of not greater than 3 arc minutes in the visual

text: display used on a scene from the pilot's eye point..

text: 9 9 This is equivalent to a light point resolution of 3 arc h.1 Lightpoint size shall not be greater than 6 arc minutes. minutes

text: 9 9 9 9 9 9 This is equivalent to a light point resolution of 4 arc Lightpoint size shall not be greater than 8 arc minutes. minutes

text: SECT

text: 20 09- 11

text: IO

text: -01 N

text: App SECT

text: 20 e

text: n

text: 09 d IO

text: ix 1 N

text: -11 t 1

text: 1.3 Visual System A B C D 1 2 3 I II III MCC FSTD H.

text: 9 9 9 9 9 9 9 i.1 Daylight, dusk, and night visual scenes with sufficient scene content to recognise aerodromes, 0 3 heliports, terrain, and major landmarks around the 0 (c Final Approach and Take-off (FATO) area and to o n successfully accomplish low airspeed/low altitude ti n ued) manoeuvres to include lift-off, hover, translational lift, landing and touchdown. A visual database sufficient to support the requirements, 9 9 9 9 9 9 9 9 Generic database is acceptable only for FTDs and j.1 including FNPTs.

text: (i) Specific areas within the database 1- needing higher resolution to support C-2 landings, take-offs and ground cushion

text: 3 exercises and training away from a JA heliport. Including elevated helipad,

text: helidecks and confined areas

text: (ii) For cross-country flights sufficient scene details to allow for ground to map Where applicable navigation over a sector length equal to 30 minutes at an average cruise speed.

text: (iii) For offshore airborne radar approaches (ARA), harmonized visual/radar representations of installations. Where applicable (iv) (For training in the use of Night Vision Goggles (NVG) a visual display with the ability to represent various scenes with

text: R-FSTD

text: the required levels of ambient light/colour. Where applicable

text: H Daylight, twilight (dusk/dawn) and night visual 9 9 9 9 9 9 9 The ambient lighting should provide an even level

text: k.1 TSFS 20

text: capability for system brightness and contrast of illumination, which is not distracting to the pilot. ratio criteria as applicable for level of qualification

text: sought. Bilaga 2 09 :87

text: JA A Bi TSFS 20

text: pp

text: R la

text: en g

text: -F di a S 2

text: H :87

text: LEVEL LEVEL LEVEL JAR-

text: Night and Dusk scene 9 9

text: The visual system should be capable of producing: 9 9 9 9 9 9 9 030 k.2 Full colour presentations. (co Full colour texture shall be used to enhance visual cue nti perception for illuminated landing surfaces. nue

text: The visual system should be capable of Statement of Compliance required. d k.3 ) producing, as a minimum: Test required. (1) A scene content comparable in detail with that Freedom of apparent quantization and other 9 9 9 9 9 produced by 6,000 polygons for daylight and 1000 distracting visual effects are also applicable for 1- visible light points for night and dusk scenes for the C Levels A and B. entire visual system.

text: -2 4

text: (2) A scene content comparable in detail with that produced by 4,000 polygons for daylight and 5000 9

text: visible light points for night and dusk scenes for the entire visual system

text: (3) A scene content comparable in detail with that produced by 6,000 polygons for daylight and 7000 visible light points for night and 9 dusk scenes for the entire visual system.

text: l.1 Surface contrast ratio:

text: Demonstration model

text: Not less than 5:1. 9 9

text: Not less than 8:1 9 9 9 9 9

text: SECT

text: 20 09- 11

text: IO

text: -01 N

text: App SECT

text: 20 e

text: n

text: 09 d IO

text: ix 1 N

text: -11 t 1

text: 1.3 Visual Systems A B C D 1 2 3 I II III MCC FSTD H.

text: Lightpoint contrast ratio. l.2 9 9 9 9 0 Not less than 25:1. 3 0 Highlight Brightness. The minimum light measured (c m.1 o at the pilot's eye position should be : n ti n 14 cd/m² (4 ft-Lamberts) 9 ued)

text: 17 cd/m² (5ft-Lamberts) 9 9 9 9 9

text: 20 cd/m² (6 ft-Lamberts) 9

text: 1- C-2

text: 5 JA

text: R-FSTD

text: H TSFS 20

text: Bilaga 2 09 :87

text: JA A Bi TSFS 20

text: pp

text: R la

text: en g

text: -F di a S 2

text: T x 1

text: D 09

text: to

text: H :87

text: LEVEL LEVEL LEVEL

text: FSTD H.

text: 1.4 Sound Systems A B C D 1 2 3 I II III MCC

text: 9 9 9 9 9 9 9 9 9 9 For FTD level 1 as appropriate for the system a.1 Significant flight deck sounds, and those, which 030 training required. result from pilot actions corresponding to those of the helicopter shall be provided. Statement of Compliance required for FFS. (co

text: nti 9 nue a.2 Sounds due to engines, transmission and

text: rotors should be available d ) 9 9 9 9 Crash sounds may be generic b.1 Sound of precipitation, windshield wipers, the

text: sound resulting from a blade strike and a crash Statement of Compliance or Demonstration of 1- condition when operating the helicopter in representative sounds required.

text: C excess of limitations.

text: 6 9 Objective steady-state tests required c.1 Realistic amplitude and frequency of cockpit

text: acoustic environment.

text: 9 9 9 9 d.1 The volume control shall have an indication of

text: sound level setting which meets all qualification

text: requirements.

text: SECT

text: 20 09- 11

text: IO

text: -01 N

text: Bilaga 2

text: Appendix 1 to JAR-FSTD H.030 (continued) These standards always refer to the type of helicopter being simulated, except for FNPT, which may be generic. For FNPT, the term “the/a helicopter” is used to represent the aircraft being modelled which can be a specific helicopter type, a family of similar helicopter types or a totally generic helicopter. Wherever the term runway is used, it includes runways and FATO/TLOF.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 1-C-27 JAR-FSTD H

text: SECTION 1

text: Bilaga 2

text: INTENTIONALLY LEFT BLANK JAR-FSTD H 1-C-28 2009-11-01

text: Bilaga 2

text: 1 GENERAL 1.1 This Section contains Advisory Circulars Joint (ACJ) providing acceptable means of compliance and/or interpretative/explanatory material that have been agreed for inclusion in JAR–FSTD H. 1.2 Where a particular JAR paragraph does not have an ACJ, it is considered that no supplementary material is required.

text: 2 PRESENTATION 2.1 The ACJs are presented in full page width on loose pages, each page being identified by the date of issue and the Amendment number under which it is amended or reissued. 2.2 A numbering system has been used in which the ACJ uses the same number as the JAR paragraph to which it refers. The number is introduced by the letters ACJ to distinguish the material from the JAR itself. 2.3 The acronym ACJ also indicates the nature of the material and for this purpose the type of material is defined as follows: ACJ illustrate a means, or several alternative means, but not necessarily the only possible means by which a requirement can be met. It should however be noted that where a new ACJ is developed, any such ACJ (which may be additional to an existing ACJ) will be amended into the document following consultation under the NPA procedure. Such ACJ will be designated by (acceptable means of compliance). An ACJ as interpretative/explanatory material may contain material that helps to illustrate the meaning of a requirement. Such ACJ will be designated by (interpretative/explanatory material). 2.4 New ACJ material may, in the first place, be made available rapidly by being published as a Temporary Guidance Leaflet (TGL). FSTD TGLs (JAR–FSTD) can be found in the Joint Aviation Authorities Administrative & Guidance Material, Section 6 – Flight Simulation Training Devices (FSTD), Part Three: Temporary Guidance Leaflet (JAR–FSTD). The procedures associated with Temporary Guidance Leaflets are included in the FSTD Joint Implementation Procedures, Section 6 – Flight Simulation Training Devices (FSTD), Part Two: Procedures (JAR–FSTD) Chapter 9. Note: Any person who considers that there may be alternative ACJ to those published should submit details to the Operations Director, with a copy to the Regulation Director, for alternatives to be properly considered by the JAA. Possible alternative ACJ may not be used until published by the JAA as ACJ or TGLs. 2.5 Explanatory Notes not forming part of the ACJ text appear in a smaller typeface. 2.6 New, amended or corrected text is enclosed within heavy brackets. 2.7 After each ACJ, the various changes and amendments, when any since the initial issue, are indicated together with their date of issue.

text: 2009-11-01 2-0-1 JAR-FSTD H

text: SECTION 2

text: Bilaga 2

text: INTENTIONALLY LEFT BLANK JAR-FSTD H 2-0-2 2009-11-01

text: Bilaga 2

text: ACJ B – GENERAL

text: ACJ to JAR-FSTD H.005 Terminology, Abbreviations See JAR–FSTD H.005

text: 1 Terminology 1.1 In addition to the principal terms defined in the requirement itself, additional terms used in the context of JAR–FSTD A and JAR-FSTD H have the following meanings: a Acceptable Change. A change to configuration, software etc., which qualifies as a potential candidate for alternative approach to validation. b Aircraft Performance Data. Performance data published by the aircraft manufacturer in documents such as the Aeroplane or Rotorcraft Flight Manual, Operations Manual, Performance Engineering Manual, or equivalent. c Airspeed. Calibrated airspeed when relevant or other airspeed which is clearly annotated. d Altitude. Pressure altitude when relevant or other altitude which is clearly annotated. e Audited Engineering Simulation. An aircraft manufacturer’s engineering simulation which has undergone a review by the appropriate regulatory Authorities and been found to be an acceptable source of supplemental validation data. f Automatic Testing. Flight Synthetic Training Device (FSTD) testing wherein all stimuli are under computer control. g Bank. Bank/Roll angle (degrees) h Baseline. A fully flight-test validated production aircraft simulation. May represent a new aircraft type or a major derivative. i Breakout. The force required at the pilot’s primary controls to achieve initial movement of the control position. j Closed Loop Testing. A test method for which the input stimuli are generated by controllers which drive the FSTD to follow a pre-defined target response. k Computer Controlled Aircraft. An aircraft where the pilot inputs to the control surfaces are transferred and augmented via computers. l Control Sweep. A movement of the appropriate pilot’s control from neutral to an extreme limit in one direction (Forward, Aft, Right, or Left), a continuous movement back through neutral to the opposite extreme position, and then a return to the neutral position. m Convertible FSTD. An FSTD in which hardware and software can be changed so that the FSTD becomes a replica of a different model or variant, usually of the same type aircraft. The same FSTD platform, cockpit shell, motion system, visual system, computers, and necessary peripheral equipment can thus be used in more than one simulation. n Critical Engine Parameter. The engine parameter which is the most appropriate measure of the engine power delivered. o Damping (critical). The CRITICAL DAMPING is that minimum Damping of a second order system such that no overshoot occurs in reaching a steady state value after being displaced from a position of equilibrium and released. This corresponds to a relative Damping ratio of 1:0 p Damping (over-damped). An OVER-DAMPED response is that Damping of a second order system such that it has more Damping than is required for Critical Damping, as described above. This corresponds to a relative Damping ratio of more than 1:0. q Damping (under-damped). An UNDER-DAMPED response is that Damping of a second order system such that a displacement from the equilibrium position and free release results in one or more overshoots or oscillations before reaching a steady state value. This corresponds to a relative Damping ratio of less than 1:0.

text: 2009-11-01 2-B-1 JAR-FSTD H

text: Bilaga 2

text: ACJ to JAR-FSTD H.005 (continued)

text: r Daylight Visual. A visual system capable of meeting, as a minimum, system brightness, contrast ratio requirements and performance criteria appropriate for the level of qualification sought. The system, when used in training, should provide full colour presentations and sufficient surfaces with appropriate textural cues to successfully conduct a visual approach, landing and airport movement (taxi). s Deadband. The amount of movement of the input for a system for which there is no reaction in the output or state of the system observed.

text: t Distance. Distance in Nautical Miles unless specified otherwise. u Driven. A state where the input stimulus or variable is ‘driven’ or deposited by automatic means, generally a computer input. The input stimulus or variable may not necessarily be an exact match to the flight test comparison data – but simply driven to certain predetermined values.

text: v Engineering Simulation. An integrated set of mathematical models representing a specific aircraft configuration, which is typically used by the aircraft manufacturer for a wide range of engineering analysis tasks including engineering design, development and certification: and to generate data for checkout, proof-of-match/validation and other training FSTD data documents. w Engineering Simulator. The term for the aircraft manufacturer’s flight simulator which typically includes a full-scale representation of the simulated aircraft flight deck, operates in real time and can be flown by a pilot to subjectively evaluate the simulation. It contains the engineering simulation models, which are also released by the aircraft manufacturer to the industry for FSTDs: and may or may not include actual on-board system hardware in lieu of software models. x Engineering Simulator Data. Data generated by an engineering simulation or engineering simulator, depending on the aircraft manufacturer’s processes.

text: y Engineering Simulator Validation Data. Validation data generated by an engineering simulation or engineering simulator. z Entry into Service. Refers to the original state of the configuration and systems at the time a new or major derivative aircraft is first placed into commercial operation. aa Essential Match. A comparison of two sets of computer-generated results for which the differences should be negligible because essentially the same simulation models have been used. Also known as a virtual match. bb Flight Test Data. Actual aircraft data obtained by the aircraft manufacturer (or other supplier of acceptable data) during an aircraft flight test programme. cc Free Response. The response of the aircraft after completion of a control input or disturbance. dd Frozen/Locked. A state where a variable is held constant with time.

text: ee FSTD Approval. The extent to which an FSTD of a specified Qualification Level may be used by an operator or training organisation as agreed by the Authority. It takes account of differences between aircraft and FSTDs and the operating and training ability of the organisation.

text: ff FSTD Data. The various types of data used by the FSTD manufacturer and the applicant to design, manufacture, test and maintain the FSTD.

text: gg FSTD Evaluation. A detailed appraisal of an FSTD by the Authority to ascertain whether or not the standard required for a specified Qualification Level is met.

text: hh FSTD Operator. That person, organisation or enterprise directly responsible to the authority for requesting and maintaining the qualification of a particular FSTD.

text: ii FSTD Qualification Level. The level of technical capability of a FSTD.

text: JAR-FSTD H 2-B-2 2009-11-01

text: Bilaga 2

text: ACJ to JAR-FSTD H.005 (continued)

text: jj Fuel used. Mass of fuel used (kilos or pounds) kk Full Sweep. Movement of the controller from neutral to a stop, usually the aft or right stop, to the opposite stop and then to the neutral position. ll Functional Performance. An operation or performance that can be verified by objective data or other suitable reference material that may not necessarily be flight test data. mm Functions Test. A quantitative and/or qualitative assessment of the operation and performance of an FSTD by a suitably qualified evaluator. The test can include verification of correct operation of controls, instruments, and systems of the simulated aircraft under normal and non-normal conditions. Functional performance is that operation or performance that can be verified by objective data or other suitable reference material which may not necessarily be Flight Test Data. nn Grandfather Rights. The right of an FSTD operator to retain the Qualification Level granted under a previous regulation of a JAA member state. Also the right of an FSTD user to retain the training and testing/checking credits which were gained under a previous regulation of a JAA member state. oo Ground Effect. The change in aerodynamic characteristics due to modification of the air flow past the aircraft caused by the presence of the ground. pp Hands-off Manoeuvre. A test manoeuvre conducted or completed without pilot control inputs. qq Hands-on Manoeuvre. A test manoeuvre conducted or completed with pilot control inputs as required. rr Heavy. Operational mass at or near maximum for the specified flight condition. ss Height. Height above ground = AGL (meters or feet) tt Highlight Brightness. The maximum displayed brightness, which satisfies the appropriate brightness test. uu Icing Accountability. A demonstration of minimum required performance whilst operating in maximum and intermittent maximum icing conditions of the applicable airworthiness requirement. Refers to changes from normal (as applicable to the individual aircraft design) in takeoff, climb (enroute, approach, landing) or landing operating procedures or performance data, in accordance with the AFM/RFM, for flight in icing conditions or with ice accumulation on unprotected surfaces. vv Integrated Testing. Testing of the FSTD such that all aircraft system models are active and contribute appropriately to the results. None of the aircraft system models should be substituted with models or other algorithms intended for testing only. This may be accomplished by using controller displacements as the input. These controllers should represent the displacement of the pilot’s controls and these controls should have been calibrated. ww Irreversible Control System. A control system in which movement of the control surface will not backdrive the pilot’s control on the flight deck. xx Latency. The additional time, beyond that of the basic perceivable response time of the aircraft due to the response time of the FSTD. yy Light. Operational mass at or near minimum for the specified flight condition. zz Line Oriented Flight Training (LOFT). Refers to aircrew training which involves full mission simulation of situations which are representative of line operations, with special emphasis on situations which involve communications, management and leadership. It means ‘realtime’, full-mission training. aaa Manual Testing. FSTD testing wherein the pilot conducts the test without computer inputs except for initial setup. All modules of the simulation should be active.

text: 2009-11-01 2-B-3 JAR-FSTD H

text: Bilaga 2

text: ACJ to JAR-FSTD H.005 (continued)

text: bbb Master Qualification Test Guide (MQTG). The Authority approved QTG which incorporates the results of tests witnessed by the Authority. The MQTG serves as the reference for future evaluations. ccc Medium. Normal operational weight for flight segment. ddd Night Visual. A visual system capable of meeting, as a minimum, the system brightness and contrast ratio requirements and performance criteria appropriate for the level of qualification sought. The system, when used in training, should provide, as a minimum, all features applicable to the twilight scene, as defined below, with the exception of the need to portray reduced ambient intensity that removes ground cues that are not self-illuminating or illuminated by own ship lights (e.g. landing lights). eee Nominal. Normal operational weight, configuration, speed etc. for the flight segment specified. fff Non-normal Control. A term used in reference to Computer Controlled Aircraft. Nonnormal Control is the state where one or more of the intended control, augmentation or protection functions are not fully available. (NOTE: Specific terms such as ALTERNATE, DIRECT, SECONDARY, BACKUP, etc, may be used to define an actual level of degradation). ggg Normal Control. A term used in reference to Computer Controlled Aircraft. Normal Control is the state where the intended control, augmentation and Protection Functions are fully available. hhh Objective Test (Objective Testing). A quantitative assessment based on comparison with data. iii One Step. Refers to the degree of changes to an aircraft that would be allowed as an acceptable change, relative to a fully flight-test validated simulation. The intention of the alternative approach is that changes would be limited to one, rather than a series, of steps away from the baseline configuration. It is understood, however, that those changes which support the primary change (e.g. weight, thrust rating and control system gain changes accompanying a body length change) are considered part of the ‘one step’. jjj Operator. A person, organisation or enterprise engaging in or offering to engage in an aircraft operation. kkk Power Lever Angle. The angle of the pilot's primary engine control lever(s) on the flight deck. This may also be referred to as PLA, THROTTLE, or POWER LEVER. lll Predicted Data. Data derived from sources other than type specific aircraft flight tests. mmm Primary Reference Document. Any regulatory document which has been used by an Authority to support the initial evaluation of a FSTD. nnn Proof-of-Match (POM). A document which shows agreement within defined tolerances between model responses and flight test cases at identical test and atmospheric conditions. ooo Protection Functions. Systems functions designed to protect an aircraft from exceeding its flight and manoeuvre limitations. ppp Pulse Input. An abrupt input to a control followed by an immediate return to the initial position. qqq Qualification Test Guide (QTG). The primary reference document used for the evaluation of an FSTD. It contains test results, statements of compliance and other information to enable the evaluator to assess if the FSTD meets the test criteria described in this manual. rrr Reversible Control System. A partially powered or unpowered control system in which movement of the control surface will backdrive the pilot’s control on the flight deck and/or affect its feel characteristics. sss Robotic Test. A basic performance check of a system’s hardware and software components. Exact test conditions are defined to allow for repeatability. The components

text: JAR-FSTD H 2-B-4 2009-11-01

text: Bilaga 2

text: ACJ to JAR-FSTD H.005 (continued)

text: are tested in their normal operational configuration and may be tested independently of other system components. ttt Sideslip. Sideslip Angle (degrees) uuu Snapshot. A presentation of one or more variables at a given instant of time. vvv Statement of Compliance (SOC). A declaration that specific requirements have been met. www Step Input. An abrupt input held at a constant value. xxx Subjective Test (Subjective Testing). A qualitative assessment based on established standards as interpreted by a suitably qualified person. yyy Throttle Lever Angle (TLA). The angle of the pilot’s primary engine control lever(s) on the flight deck. zzz Time History. A presentation of the change of a variable with respect to time. aaaa Transport Delay. The total FSTD system processing time required for an input signal from a pilot primary flight control until the motion system, visual system, or instrument response. It is the overall time delay incurred from signal input until output response. It does not include the characteristic delay of the aircraft simulated. bbbb Twilight (Dusk/Dawn) Visual. A visual system capable of meeting, as a minimum, the system brightness and contrast ratio requirements and performance criteria appropriate for the level of qualification sought. The system, when used in training, should provide, as a minimum, full colour presentations of reduced ambient intensity (as compared with a daylight visual system), sufficient to conduct a visual approach, landing and airport movement (taxi) cccc Update. The improvement or enhancement of an FSTD. dddd Upgrade. The improvement or enhancement of an FSTD for the purpose of achieving a higher qualification. eeee Validation Data. Data used to prove that the FSTD performance corresponds to that of the aircraft. ffff Validation Flight Test Data. Performance, stability and control, and other necessary test parameters electrically or electronically recorded in an aircraft using a calibrated data acquisition system of sufficient resolution and verified as accurate by the organisation performing the test to establish a reference set of relevant parameters to which like FSTD parameters can be compared. gggg Validation Test. A test by which FSTD parameters can be compared with the relevant validation data. hhhh Vibration. A permanent effect resulting from airframe interaction with rotor, engine or transmission, as opposed to buffet which is a transient vibration effect resulting from either pilot action or aerodynamic effect on the airframe. iiii Visual Ground Segment Test. A test designed to assess items impacting the accuracy of the visual scene presented to the pilot at a decision height (DH) on an ILS approach. jjjj Visual System Response Time. The interval from an abrupt control input to the completion of the visual display scan of the first video field containing the resulting different information. kkkk Well-Understood Effect. An incremental change to a configuration or system which can be accurately modelled using proven predictive methods based on known characteristics of the change.

text: 2009-11-01 2-B-5 JAR-FSTD H

text: Bilaga 2

text: ACJ to JAR-FSTD H.005 (continued)

text: 2 Abbreviations

text: A = Aeroplane AC = Advisory Circular ACJ = Advisory Circular Joint A/C = Aircraft Ad = Total initial displacement of pilot controller (initial displacement to final resting amplitude) AFM = Aeroplane Flight Manual AFCS = Automatic Flight Control System AGL = Above Ground Level (metres or feet) An = Sequential amplitude of overshoot after initial X axis crossing, e.g. A1 = 1st overshoot. AEO = All Engines Operating AOA = Angle of Attack (degrees) ARA = Airborne Radar Approach

text: BC = ILS localizer back course

text: CAT I/II/III = Landing category operations CCA = Computer Controlled Aeroplane CCH = Computer Controlled Helicopter 2 2 2 cd/m = Candela/metre , 3.4263 candela/m = 1 ft-Lambert CG = Centre of gravity cm(s) = Centimetre, centimetres CT&M = Correct Trend and Magnitude daN = DecaNewtons dB = Decibel deg(s) = Degree, degrees DGPS = Differential Global Positioning System DH = Decision Height DME = Distance Measuring Equipment DPATO = Defined Point After Take-off DPBL = Define Point Before Landing

text: EPR = Engine Pressure Ratio EW = Empty Weight

text: FAA = United States Federal Aviation Administration (U.S.) FATO = Final Approach and Takeoff FD = Flight Director FOV = Field Of View FPM = Feet Per Minute FTO = Flying Training Organisation ft = Feet, 1 foot = 0.304801 metres ft-Lambert = Foot-Lambert, 1 ft-Lambert = 3.4263 candela/m

text: IATA = International Air Transport Association ICAO = International Civil Aviation Organisation

text: JAR-FSTD H 2-B-6 2009-11-01

text: Bilaga 2

text: ACJ to JAR-FSTD H.005 (continued)

text: IGE = In Ground Effect ILS = Instrument Landing System IMC = Instrument Meteorological Conditions in = Inches 1 in = 2.54 cm IOS = Instructor Operating Station IPOM = Integrated proof of match IQTG = International Qualification Test Guide (RAeS Document)

text: n = Sequential period of a full cycle of oscillation N = NORMAL CONTROL Used in reference to Computer Controlled Aircraft N/A = Not Applicable N1 = Engine Low Pressure Rotor revolutions per minute expressed in percent of maximum N1/Ng = Gas Generator Speed N2 = Engine High Pressure Rotor revolutions per minute expressed in percent of maximum N2/Nf = Free Turbine Speed NAA = National Aviation Authority NDB = Non-directional beacon NM = Nautical Mile, 1 Nautical Mile = 6 080 feet = 1 852m NN = Non-normal control a state referring to computer controlled aircraft NR = Main Rotor Speed NWA = Nosewheel Angle (degrees)

text: P0 = Time from pilot controller release until initial X axis crossing (X axis defined by the resting amplitude)

text: 2009-11-01 2-B-7 JAR-FSTD H

text: Bilaga 2

text: ACJ to JAR-FSTD H.005 (continued)

text: P1 = First full cycle of oscillation after the initial X axis crossing P2 = Second full cycle of oscillation after the initial X axis crossing PANS = Procedure for air navigation services PAPI = Precision Approach Path Indicator System PAR = Precision approach radar Pf = Impact or Feel Pressure PLA = Power Lever Angle PLF = Power for Level Flight Pn = Sequential period of oscillation POM = Proof-of-Match PSD = Power Spectral Density psi = pounds per square inch. (1 psi = 6·89476 kPa) PTT = Part-Task Trainer QTG = Qualification Test Guide R/C = Rate of Climb (metres/sec or feet/min) R/D = Rate of Descent (metres/sec or feet/min) RAE = Royal Aerospace Establishment RAeS = Royal Aeronautical Society REIL = Runway End Identifier Lights RNAV = Radio navigation RVR = Runway Visual Range (metres or feet) s = second(s) sec(s) = second, seconds sm = Statute Mile 1 Statute Mile = 5280 feet = 1609m SOC = Statement of Compliance SUPPS = Supplementary procedures referring to regional supplementary procedures TCAS = Traffic alert and Collision Avoidance System TGL = Temporary Guidance Leaflet T(A) = Tolerance applied to Amplitude T(p) = Tolerance applied to period T/O = Take-off Tf = Total time of the flare manoeuvre duration Ti = Total time from initial throttle movement until a 10% response of a critical engine parameter TLA = Throttle lever angle TLOF = Touchdown and Lift Off TDP = Take-off Decision Point Tt = Total time from Ti to a 90% increase or decrease in the power level specified VASI = Visual Approach Slope Indicator System VDR = Validation Data Roadmap VFR = Visual Flight Rules VGS = Visual Ground Segment Vmca = Minimum Control Speed (Air) Vmcg = Minimum Control Speed (Ground) Vmcl = Minimum Control Speed (Landing) VOR = VHF omni-directional range Vr = Rotate Speed Vs = Stall Speed or minimum speed in the stall V1 = Critical Decision Speed VTOSS = Take-off Safety Speed Vy = Optimum Climbing Speed Vw = Wind Velocity WAT = Weight, Altitude, Temperature

text: JAR-FSTD H 2-B-8 2009-11-01

text: Bilaga 2

text: ACJ No. 1 to JAR-FSTD H.015 (acceptable means of compliance) FSTD Qualification – Application and Inspection See JAR–FSTD H.015

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-1 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 1 to JAR-FSTD H.015 (continued)

text: LETTER OF APPLICATION FOR INITIAL JAA EVALUATION OF A FLIGHT SIMULATION TRAINING DEVICE.

text: Part A To be submitted not less than 3 months prior to requested qualification date (Date)………………… PRINCIPAL INSPECTOR (JAA NAA OFFICE) (Address)……………………………………………. ………………………………………………………… (City)…………………………………………………. (Country)…………………………………………….

text: Type of FSTD Aircraft Qualification Level Sought Type/class Full Flight Simulator FFS A B C D Flight Training Device FTD 1 2 3 Flight and Navigation FNPT I II III II MCC III MCC Procedures trainer

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD H 2-C-2 2009-11-01

text: Bilaga 2

text: ACJ No. 1 to JAR-FSTD H.015 (continued)

text: Dear…………………………….,

text: Evaluation is requested for the following configurations and engine fits as applicable: e.g. Turbomeca Makila 1A1 / 1A2 1…………….. 2……………. 3…………….

text: Dates requested are:……………………….. and the FSTD will be located at ……………………………………………………………………………………………………………… The QTG will be submitted by……(Date)………… and in any event not less than 30 days before the requested evaluation date unless otherwise agreed with the Authority. Comments: ………………………………………………………………………………………………………………………………… ………………………………………………………………………………………………………………………………… …………………………………………………………………………………………………………………………

text: Signed ……………………………………………………………………… Print name………………………………………………………… position/appointment held………………………………………. e mail address……………………………………………………. telephone number………………………………………………...

text: 2009-11-01 2-C-3 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 1 to JAR-FSTD H.015 (continued)

text: Part B To be completed with attached QTG results

text: (Date)…………………………...

text: We have completed tests of the FSTD and declare that it meets all applicable requirements of the JAR– FSTD H (Helicopter) except as noted below. Appropriate hardware and software configuration control procedures have been established and these are appended for your inspection and approval.

text: The following MQTG tests are outstanding:

text: Tests Comments

text: (Add boxes as required) It is expected that they will be completed and submitted 3 weeks prior to the evaluation date. Signed ……………………………………………………………..

text: position/appointment held…………………………….. E-mail address………………………………………….. Telephone number……………………………………...

text: JAR-FSTD H 2-C-4 2009-11-01

text: Bilaga 2

text: ACJ No. 1 to JAR-FSTD H.015 (continued)

text: Part C

text: To be completed not less than 7 days prior to initial evaluation

text: (Date)……………….…………..

text: The FSTD has been assessed by the following evaluation team: (name).…………………… Qualification……………………….. (name)……………………. Qualification……………………….. (name)……………………. Qualification……………………….. (name).…………………… Pilot’s Licence Nr………………… (name)……………………. Flight Engineer’s Licence Nr (if applicable)……………..

text: equivalently to those in that helicopter. This pilot has also assessed the performance and the flying qualities of the FSTD and finds that it represents the designated helicopter. (Additional comments as required) ……………………………………………………………. ……………………………………………………………. …………………………………………………………….

text: Signed ………………………

text: position/appointment held…………………………… E-mail address………………………………………… Telephone number…………………………………….

text: 2009-11-01 2-C-5 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 1 to JAR-FSTD H.015 (continued) ACJ No. 1 to JAR-FSTD H.015 (continued)

text: 2 Composition of Evaluation Team 2.1 To gain a Qualification Level, an FSTD is evaluated in accordance with a structured routine conducted by a technical team which is appointed by the Authority and consists of at least: a. A technical FSTD inspector of the Authority, or an accredited inspector from another JAA Authority, qualified in all aspects of flight simulation hardware, software and computer modelling or, exceptionally, a person designated by the Authority with equivalent qualifications; and b. One of the following: (i) A flight inspector of the Authority, or an accredited inspector from another JAA Authority, who is qualified in flight crew training procedures and is holding a valid type rating on the helicopter being simulated; or (ii). A flight inspector of the Authority who is qualified in flight crew training procedures assisted by a type rating instructor, holding a valid type rating on the helicopter being simulated ; or, exceptionally, c. A person designated by the Authority who is qualified in flight crew training procedures and is holding a valid type rating on the helicopter being simulated and sufficiently experienced to assist the technical team. This person should fly out at least part of the functions and subjective test profiles. d. Where a designated person is used as a substitute for one of the Authority’s inspectors, the other person shall be a properly qualified inspector of the Authority or an accredited inspector from another JAA Authority. e. For generic FNPT helicopters evaluations the valid type rating should be appropriate for the generic type of helicopter being represented. For FTD level 1 and FNPT level I, one suitably qualified Inspector may combine the functions in a. and b. above. 2.2 Additionally the following persons should be present: a. (For FFS, FTD and FNPT) A type rated Training Captain typically from the FSTD operator or main FSTD users. b. (For all types) Sufficient FSTD support staff to assist with the running of tests and operation of the instructor’s station. 2.3 On a case-by-case basis, when an FSTD is being evaluated, the Authority may reduce the evaluation team to an Authority flight inspector supported by a type rated training captain from the main flight simulator user for evaluation of a specific flight simulator of a specific FSTD operator, provided: a. This composition is not being used prior to the second recurrent evaluation; b. Such an evaluation will be followed by an evaluation with a full authority evaluation team; c. The Authority flight inspector will perform some spot checks in the area of objective testing; d. No major change or upgrading has been applied since the directly preceding evaluation; e. No relocation of the FSTD has taken place since the last evaluation; f. A system is established enabling the Authority to monitor and analyse the status of the FSTD on a continuous basis; g. The FSTD’s hardware and software has been working reliably for the previous years. This should be reflected in the number and kind of (technical log) discrepancies and the results of the quality system audits.

text: JAR-FSTD H 2-C-6 2009-11-01

text: Bilaga 2

text: ACJ No. 2 to JAR- FSTD H.015 (explanatory material) FSTD Evaluations See JAR–FSTD H.015

text: 1 General 1.1 During initial and recurrent FSTD evaluations it will be necessary for the Authority to conduct the objective and subjective tests described in JAR-FSTD H.030 and JAR-FSTD H.035 and detailed in ACJ No. 1 to JAR-FSTD H.030. There will be occasions when all tests cannot be completed - for example during recurrent evaluations on a convertible FSTD - but arrangements should be made for all tests to be completed within a reasonable time.

text: 1.2 Following an evaluation, it is possible that a number of defects may be identified; generally these defects should be rectified and the Authority notified of such action within 30 days. Serious defects which affect crew training, testing and checking when applicable, could result in an immediate downgrading of the Qualification Level, or if any defects remain unattended without good reason for period greater than 30 days, subsequent downgrading may occur or qualification could be revoked. 2 Initial Evaluations

text: 2.1 Objective Testing 2.1.1 Objective Testing is centered around the QTG. Before testing can begin on an initial evaluation the acceptability of the validation tests contained in the QTG should be agreed with the Authority well in advance of the evaluation date to ensure that the FSTD time especially devoted to the running of some of the tests by the Authority is not wasted. The acceptability of all tests depends upon their content, accuracy, completeness and recency of the results.

text: 2.1.2 Much of the time allocated to objective tests depends upon the speed of the automatic and manual systems set up to run each test and whether or not special equipment is required. The Authority will not necessarily warn the FSTD operator of the sample validations tests which will be run on the day of the evaluation, unless special equipment is required. It should be remembered that the FSTD cannot be used for subjective tests whilst part of the QTG is being run. Therefore sufficient time should be set aside for the examination and running of the QTG.

text: 2.2 Subjective Testing 2.2.1 The Subjective Tests for the evaluation can be found in ACJ No.1 to JAR- FSTD H.030, and a suggested Subjective Test Profile is described in sub-paragraph 4.6 below. 2.2.2 Essentially the subjective test routine effectively denies the use of the FSTD for any other purpose. 2.3 Conclusion

text: To ensure adequate coverage of subjective and objective tests and to allow for cost effective rectification and re-test before departure of the inspection team, a sufficient number of consecutive days should be dedicated to an initial evaluation of a FSTD. 3 Recurrent Evaluations 3.1 Objective Testing 3.1.1 During recurrent evaluations, the Authority will wish to see evidence of the successful running of the QTG between evaluations. The Authority will select a number of tests to be run during the evaluation, including those, which may be cause for concern. Again adequate notification would be given when special equipment is required for the test. 3.1.2 Essentially the time taken to run the objective tests depends upon the need for special equipment and the test system, and the FSTD cannot be used for subjective tests or other functions whilst testing is in progress. For a FSTD incorporating an automatic test system, four (4) hours would normally be required. FSTDs, which rely upon manual testing, may require a longer period of time. 3.2 Subjective testing 3.2.1 Essentially the same subjective test routine should be flown as per the profile described in subparagraph 4.6 below with a selection of the subjective tests taken from ACJ No 1 to JAR-FSTD H.030.

text: 2009-11-01 2-C-7 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 2 to JAR-FSTD H.015 (continued)

text: 3.2.2 Normally, the time taken for recurrent subjective testing is about four (4) hours, and the FSTD cannot perform other functions during this time. 3.3 Conclusion

text: To ensure adequate coverage of subjective and objective tests during a recurrent evaluation, a total of 8 hours should be allocated for a FSTD. However, it should be remembered that any FSTD deficiency, which arises during the evaluation could necessitate the extension of the evaluation period. 4 Functions and Subjective Tests - Suggested Test Routine

text: 4.1 During initial and recurrent evaluations of a FSTD, the competent Authority will conduct a series of functions and subjective tests, which together with the objective tests complete the comparison of the FSTD with the helicopter (may be a generic helicopter for FNPT). 4.2 Whereas functions tests verify the acceptability of the simulated helicopter systems and their integration, subjective tests verify the fitness of the FSTD in relation to training, checking and testing tasks.

text: 4.3 The FSTD should provide adequate flexibility to permit the accomplishment of the desired/required tasks while maintaining an adequate perception by the flight crew that they are operating in a real helicopter environment. Additionally, the operation of the Instructor Operating Station (IOS) should be simple enough to give the instructor spare capacity to observe the activities of the flight crew. 4.4 Section 1 of JAR-FSTD H sets out the requirements, and the ACJs in Section 2 the means of compliance for FSTD qualification. However, it is important that both the Authority and the FSTD operator understand what to expect from the routine of FSTD functions and subjective tests. It should be remembered that part of the subjective tests routine for a FSTD should involve an uninterrupted fly-out (except for FTD and level 1) comparable with the duration of typical training sessions in addition to assessment of flight freeze and repositioning). An example of such a profile is to be found in sub-paragraph 4.6 below. 4.5 JAA Authorities and FSTD operators who are unfamiliar with the evaluation process are advised to contact another JAA Authority, which is suitably experienced.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD H 2-C-8 2009-11-01

text: Bilaga 2

text: ACJ No. 2 to JAR-FSTD H.015 (continued)

text: 4.5 Typical Test Profile for a FSTD H:

text: Note: The Typical Test Profile should be flown at helicopter masses at, or close to, the maximum allowable mass for the ambient atmospheric conditions. Those ambient conditions should be varied from Standard Atmosphere to test the validity of the limits of temperature and pressure likely to be required in the practical use of the FSTD. Visual exercises only apply to FSTDs fitted with a visual system.

text: 2009-11-01 2-C-9 JAR-FSTD H

text: Bilaga 2

text: ACJ to JAR-FSTD H.020 (acceptable means of compliance) Validity of FSTD Qualification See JAR-FSTD H.020

text: 1. Prerequisites 1.1 On a case-by-case basis, the Authority may grant an extended validity of a FSTD qualification in excess of 12 months up to a maximum of 36 months, to a specific FSTD operator for a specific FSTD, provided: a. an initial and at least one recurrent successful evaluation have been performed on this FSTD by the same Authority;

text: b. the FSTD operator has got a satisfactory record of successful regulatory FSTD evaluations over a period of at least 3 years; c. the FSTD operator has established and successfully maintained a Quality System for at least 3 years; d. the Authority performs a formal audit of the FSTD operator's Quality System every calendar year;

text: e. an accountable person of the FSTD operator with FSTD and training experience acceptable to the Authority (such as a type rated training captain), reviews the regular reruns of the QTG and conducts the relevant function and subjective tests every 12 months; f. a report detailing the results of the QTG rerun tests and function and subjective evaluation will be signed and submitted by the accountable person described under subparagraph (e) above to the Authority.

text: 2. Prerogative of the Authority 2.1 The Authority reserves the right to perform flight simulator evaluations whenever it deems it necessary.

text: ACJ No. 1 to JAR-FSTD H.025 (acceptable means of compliance) Quality System See JAR– FSTD H.025

text: 1 Introduction 1.1 In order to show compliance with JAR– FSTD H.025, an FSTD operator should establish his Quality System in accordance with the instructions and information contained in the following paragraphs.

text: 2 General 2.1 Terminology a. The terms used in the context of the requirement for an FSTD operator’s Quality System have the following meanings: (i) Accountable Manager. The person acceptable to the Authority who has corporate authority for ensuring that all necessary activities can be financed and carried out to the standard required by the Authority, and any additional requirements defined by the FSTD operator. (ii) Quality Assurance. All those planned and systematic actions necessary to provide adequate confidence that specified performance, functions and characteristics satisfy given requirements. (iii) Quality Manager. The manager, acceptable to the Authority, responsible for the management of the Quality System, monitoring function and requesting corrective actions.

text: 2.2 Quality Policy 2.2.1 An FSTD operator should establish a formal written Quality Policy Statement that is a commitment by the Accountable Manager as to what the Quality System is intended to achieve. The Quality Policy should reflect the achievement and continued compliance with JAR– FSTD H together with any additional standards specified by the FSTD operator.

text: JAR-FSTD H 2-C-10 2009-11-01

text: Bilaga 2

text: ACJ No. 1 to JAR- FSTD H.025 (continued) 2.2.2 The Accountable Manager is an essential part of the FSTD qualification holder’s organisation. With regard to the above terminology, the term ‘Accountable Manager’ is intended to mean the Chief Executive/President/Managing Director/General Manager etc. of the FSTD operator’s organisation, who by virtue of his position has overall responsibility (including financial) for managing the organisation. 2.2.3 The Accountable Manager will have overall responsibility for the FSTD qualification holder’s Quality System including the frequency, format and structure of the internal management evaluation activities as prescribed in paragraph 4.9 below. 2.3 Purpose of the Quality System 2.3.1 The Quality System should enable the FSTD operator to monitor compliance with JAR– FSTD H, and any other standards specified by that FSTD operator, or the Authority, to ensure correct maintenance and performance of the device. 2.4 Quality Manager 2.4.1 The primary role of the Quality Manager is to verify, by monitoring activity in the fields of FSTD qualification, that the standards required by the Authority, and any additional requirements defined by the FSTD operator, are being carried out under the supervision of the relevant Manager. 2.4.2 The Quality Manager should be responsible for ensuring that the Quality Assurance Programme is properly established, implemented and maintained. 2.4.3 The Quality Manager should: a. Have direct access to the Accountable Manager; b. Have access to all parts of the FSTD operator’s and, as necessary, any sub-contractor’s organisation. 2.4.4 The posts of the Accountable Manager and the Quality Manager may be combined by FSTD operators whose structure and size may not justify the separation of those two posts. However, in this event, Quality Audits should be conducted by independent personnel. 3 Quality System 3.1 Introduction 3.1.1 The FSTD operator’s Quality System should ensure compliance with FSTD qualification requirements, standards and procedures. 3.1.2 The FSTD operator should specify the structure of the Quality System. 3.1.3 The Quality System should be structured according to the size and complexity of the organisation to be monitored. 3.2 Scope 3.2.1 As a minimum, the Quality System should address the following: a. The provision of JAR–FSTD H. b. The FSTD operator’s additional standards and procedures. c. The FSTD operator’s Quality Policy. d. The FSTD operator’s organisational structure. e. Responsibility for the development, establishment and management of the Quality System. f. Documentation, including manuals, reports and records. g. Quality Procedures. h. Quality Assurance Programme. i. The provision of adequate financial, material and human resources. j. Training requirements for the various functions in the organisation.

text: 2009-11-01 2-C-11 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 1 to JAR-FSTD H.025 (continued) 3.2.2 The Quality System should include a feedback system to the Accountable Manager to ensure that corrective actions are both identified and promptly addressed. The feedback system should also specify who is required to rectify discrepancies and non-compliance in each particular case, and the procedure to be followed if corrective action is not completed within an appropriate timescale. 3.3 Relevant Documentation 3.3.1 Relevant documentation should include the following: a. Quality Policy. b. Terminology. c. Reference to specified FSTD technical standards. d. A description of the organisation. e. The allocation of duties and responsibilities. f. Qualification procedures to ensure regulatory compliance. g. The Quality Assurance Programme, reflecting: (i) Schedule of the monitoring process. (ii) Audit procedures. (iii) Reporting procedures. (iv) Follow-up and corrective action procedures. (v) Recording system. (vi) Document control. 4. Quality Assurance Programme 4.1 Introduction 4.1.1 The Quality Assurance Programme should include all planned and systematic actions necessary to provide confidence that all maintenance is conducted and all performance maintained in accordance with all applicable requirements, standards and procedures. 4.1.2 When establishing a Quality Assurance Programme, consideration should, at least, be given to the paragraphs 4.2 to 4.9 below. 4.2 Quality Inspection 4.2.1 The primary purpose of a quality inspection is to observe a particular event/action/document etc., in order to verify whether established procedures and requirements are followed during the accomplishment of that event and whether the required standard is achieved. 4.2.2 Typical subject areas for quality inspections are: a. Actual FSTD operation. b. Maintenance. c. Technical standards. d. FSTD safety features. 4.3 Audit 4.3.1 An audit is a systematic and independent comparison of the way in which an activity is being conducted against the way in which the published procedures say it should be conducted. 4.3.2 Audits should include at least the following quality procedures and processes: a. A statement explaining the scope of the audit. b. Planning and preparation.

text: JAR-FSTD H 2-C-12 2009-11-01

text: Bilaga 2

text: ACJ No. 1 to JAR- FSTD H.025 (continued) c. Gathering and recording evidence; and d. Analysis of the evidence. 4.3.3 Techniques which contribute to an effective audit are: a. Interviews or discussions with personnel. b. A review of published documents. c. The examination of an adequate sample of records. d. The witnessing of the activities which make up the operation; and e. The preservation of documents and the recording of observations. 4.4 Auditors 4.4.1 An FSTD operator should decide, depending on the complexity and size of the organisation, whether to make use of a dedicated audit team or a single auditor. In any event, the auditor or audit team should have relevant FSTD experience. 4.4.2 The responsibilities of the auditors should be clearly defined in the relevant documentation. 4.5 Auditor’s Independence 4.5.1 Auditors should not have any day to day involvement in the area of activity which is to be audited. An FSTD operator may, in addition to using the services of full-time dedicated personnel belonging to a separate quality department, undertake the monitoring of specific areas or activities by the use of part-time auditors. Due to the technological complexity of FSTDs, which requires auditors with very specialised knowledge and experience, an FSTD operator may undertake the audit function by the use of part-time personnel from within his own organisation or from an external source under the terms of an agreement acceptable to the Authority. In all cases the FSTD operator should develop suitable procedures to ensure that persons directly responsible for the activities to be audited are not selected as part of the auditing team. Where external auditors are used, it is essential that any external specialist is familiar with the type of device conducted by the FSTD operator. 4.5.2 The FSTD operator’s Quality Assurance Programme should identify the persons within the company who have the experience, responsibility and authority to: a. Perform quality inspections and audits as part of ongoing Quality Assurance. b. Identify and record any concerns or findings, and the evidence necessary to substantiate such concerns or findings. c. Initiate or recommend solutions to concerns or findings through designated reporting channels. d. Verify the implementation of solutions within specific time scales. e. Report directly to the Quality Manager. 4.6 Audit Scope 4.6.1 FSTD operators are required to monitor compliance with the procedures they have designed to ensure specified performance and functions. In doing so they should as a minimum, and where appropriate, monitor: a. Organisation. b. Plans and objectives. c. Maintenance procedures. d. FSTD Qualification Level. e. Supervision. f. FSTD technical status. g. Manuals, logs, and records.

text: 2009-11-01 2-C-13 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 1 to JAR- FSTD H.025 (continued) h. Defect deferral. i. Personnel training. j. Helicopter modifications management. 4.7 Auditing scheduling 4.7.1 A Quality Assurance Programme should include a defined audit schedule and a periodic review. The schedule should be flexible, and allow unscheduled audits when trends are identified. Followup audits should be scheduled when necessary to verify that corrective action was carried out and that it was effective. 4.7.2 An FSTD operator should establish a schedule of audits to be completed during a specified calendar period. All aspects of the operation should be reviewed within every period of 12 months in accordance with the programme unless an extension to the audit period is accepted as explained below. An FSTD operator may increase the frequency of audits at his discretion but should not decrease the frequency without the agreement of the Authority. 4.7.3 When an FSTD operator defines the audit schedule, significant changes to the management, organisation, or technologies should be considered as well as changes to the regulatory requirements. 4.7.4 For FSTD operators whose structure and size may not justify the completion of a complex system of audits, it may be appropriate to develop a Quality Assurance Programme that employs a checklist. The checklist should have a supporting schedule that requires completion of all checklist items within a specified time scale, together with a statement acknowledging completion of a periodic review by top management. 4.7.5 Whatever arrangements are made, the FSTD operator retains the ultimate responsibility for the Quality System and especially the completion and follow up of corrective actions. 4.8 Monitoring and Corrective Action 4.8.1 The aim of monitoring within the Quality System is primarily to investigate and judge its effectiveness and thereby to ensure that defined policy, performance and function standards are continuously complied with. Monitoring activity is based upon quality inspections, audits, corrective action and follow-up. The FSTD operator should establish and publish a quality procedure to monitor regulatory compliance on a continuing basis. This monitoring activity should be aimed at eliminating the causes of unsatisfactory performance. 4.8.2 Any non-compliance identified as a result of monitoring should be communicated to the manager responsible for taking corrective action or, if appropriate, the Accountable Manager. Such noncompliance should be recorded, for the purpose of further investigation, in order to determine the cause and to enable the recommendation of appropriate corrective action. 4.8.3 The Quality Assurance Programme should include procedures to ensure that corrective actions are taken in response to findings. These quality procedures should monitor such actions to verify their effectiveness and that they have been completed. Organisational responsibility and accountability for the implementation of corrective actions resides with the department cited in the report identifying the finding. The Accountable Manager will have the ultimate responsibility for resourcing the corrective action and ensuring, through the Quality Manager, that the corrective action has reestablished compliance with the standard required by the Authority, and any additional requirements defined by the FSTD operator. 4.8.4 Corrective action a. Subsequent to the quality inspection/audit, the FSTD operator should establish: b. The seriousness of any findings and any need for immediate corrective action. c. Cause of the finding. d. Corrective actions required to ensure that the non-compliance does not recur. e. A schedule for corrective action.

text: JAR-FSTD H 2-C-14 2009-11-01

text: Bilaga 2

text: ACJ No. 1 to JAR- FSTD H.025 (continued) f. The identification of individuals or departments responsible for implementing corrective action. g. Allocation of resources by the Accountable Manager, where appropriate. 4.8.5 The Quality Manager should: a. Verify that corrective action is taken by the manager responsible in response to any finding of noncompliance. b. Verify that corrective action includes the elements outlined in paragraph 4.8.4 above. c. Monitor the implementation and completion of corrective action. d. Provide management with an independent assessment of corrective action, implementation and completion. e. Evaluate the effectiveness of corrective action through the follow-up process. 4.9 Management Evaluation 4.9.1 A management evaluation is a comprehensive, systematic, documented review of the Quality System and procedures by the management, and it should consider: a. The results of quality inspections, audits and any other indicators. b. The overall effectiveness of the management organisation in achieving stated objectives. 4.9.2 A management evaluation should identify and correct trends, and prevent, where possible, future non-conformities. Conclusions and recommendations made as a result of an evaluation should be submitted in writing to the responsible manager for action. The responsible manager should be an individual who has the authority to resolve issues and take action. 4.9.3 The Accountable Manager should decide upon the frequency, format, and structure of internal management evaluation activities. 4.10 Recording 4.10.1 Accurate, complete, and readily accessible records documenting the results of the Quality Assurance Programme should be maintained by the FSTD operator. Records are essential data to enable an FSTD operator to analyse and determine the root causes of non-conformity, so that areas of non-compliance can be identified and addressed. 4.10.2 The following records should be retained for a period of 5 years: a. Audit schedules. b. Quality inspection and audit reports. c. Response to findings. d. Corrective action reports. e. Follow-up and closure reports; and f. Management evaluation reports. 5 Quality Assurance responsibility for sub-contractors 5.1 Sub-contractors 5.1.1 FSTD operators may decide to sub-contract out certain activities to external agencies for the provision of services related to areas such as: a. Maintenance. b. Manual preparation. 5.1.2 The ultimate responsibility for the product or service provided by the sub-contractor always remains with the FSTD operator. A written agreement should exist between the FSTD operator and the subcontractor clearly defining the services and quality to be provided. The sub-contractor's activities

text: 2009-11-01 2-C-15 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 1 to JAR- FSTD H.025 (continued) relevant to the agreement should be included in the FSTD operator's Quality Assurance Programme. 5.1.3 The FSTD operator should ensure that the sub-contractor has the necessary authorisation/approval when required, and commands the resources and competence to undertake the task. If the FSTD operator requires the sub-contractor to conduct activity which exceeds the sub-contractor’s authorisation/approval, the FSTD operator is responsible for ensuring that the sub-contractor’s Quality Assurance takes account of such additional requirements. 6 Quality System Training 6.1 General 6.1.1 An FSTD operator should establish effective, well planned and resourced quality related briefing for all personnel. 6.1.2 Those responsible for managing the Quality System should receive training covering: a. An introduction to the concept of the Quality System. b. Quality management. c. Concept of Quality Assurance. d. Quality manuals. e. Audit techniques. f. Reporting and recording; and g. The way in which the Quality System will function in the organisation. 6.1.3 Time should be provided to train every individual involved in quality management and for briefing the remainder of the employees. The allocation of time and resources should be sufficient for the scope of the training. 6.2 Sources of Training 6.2.1 Quality management courses are available from the various national or international Standards Institutions, and an FSTD operator should consider whether to offer such courses to those likely to be involved in the management of Quality Systems. FSTD operators with sufficient appropriately qualified staff should consider whether to carry out in-house training. 7. Standard Measurements for Flight Simulator Quality 7.1 General 7.1.1 It is recognised that a Quality System tied to measurement of FSTD performance will probably lead to improving and maintaining training quality. One acceptable means of measuring FSTD th performance is as defined and agreed by industry in ARINC report 433 (May 15 , 2001 or as amended) entitled “Standard Measurements for Flight Simulator Quality”.

text: ACJ No. 2 to JAR-FSTD H.025 Installations See JAR-FSTD H.025(c)

text: 1 Introduction 1.1 This ACJ identifies those elements that are expected to be addressed, as a minimum, to ensure that the FSTD installation provides a safe environment for the users and operators of the FSTD under all circumstances. 2 Expected Elements 2.1 Adequate fire/smoke detection, warning and suppression arrangements should be provided to ensure safe passage of personnel from the FSTD.

text: JAR-FSTD H 2-C-16 2009-11-01

text: Bilaga 2

text: ACJ No. 2 to JAR- FSTD H.025 (continued)

text: 2.2 Adequate protection should be provided against electrical, mechanical, hydraulic and pneumatic hazards – including those arising from the control loading and motion systems to ensure maximum safety of all personnel in the vicinity of the FSTD. 2.3 Other areas that should be addressed include: a. A two way communication system that remains operational in the event of a total power failure. b. Emergency lighting c. Escape exits and escape routes d. Occupant restraints (seats, seat belts etc.). e. External warning of motion and access ramp or stairs activity. f. Danger area markings. g. Guard rails and gates h. Motion and control loading emergency stop controls accessible from either pilot or instructor seats; and i. A manual or automatic electrical power isolation switch.

text: ACJ No. 1 to JAR-FSTD H.030 acceptable means of compliance FSTDs qualified on or after 1 August 2008 See JAR–FSTD H.030

text: NOTE: The structure and numbering of this ACJ departs from JAA layout due to the complexity of the technical content and the need to retain harmonisation with the ICAO Manual of Criteria for the Qualification of Flight Simulators (1995 or as amended). 1 Introduction 1.1 Purpose. This ACJ establishes the criteria which define the performance and documentation requirements for the evaluation of FSTDs used for training, testing and checking of flight crewmembers. These test criteria and methods of compliance were derived from extensive experience of the Authorities and the industry. 1.2 Background 1.2.1 The availability of advanced technology has permitted greater use of FSTDs for training, testing and checking of flight crew-members. The complexity, costs and operating environment of modern aircraft also encourages broader use of advanced simulation. FSTDs can provide more in-depth training than can be accomplished in aircraft and provide a safe and suitable learning environment. Fidelity of modern FSTDs is sufficient to permit pilot assessment with the assurance that the observed behaviour will transfer to the aircraft. Fuel conservation and reduction in adverse environmental effects are important by-products of FSTD use. 1.2.2 The methods, procedures, and testing criteria contained in this ACJ are the result of the experience and expertise of Authorities, operators, and manufacturers of helicopters and FSTDs (FFS, FTD and FNPT). 1.2.3 In showing compliance with JAR–FSTD H.030, the Authority expects account to be taken of the RAeS document entitled ‘Data Package Requirements for Design and Performance Evaluation of Rotary Wing Synthetic Training Devices’ – (2004 or as amended), as appropriate to the Qualification Level sought. In any case early contact with the Authority is advised at the initial stage of FSTD build to verify the acceptability of the data. 1.3 Levels of FSTD qualification. 1.3.1 Parts 2, and 3 of this ACJ describe the minimum requirements for qualifying Level A, B, C and D helicopter FFS, Level 1, 2 and 3 helicopter FTDs and FNPT levels I, II, IIMCC, III and IIIMCC for generic helicopters.

text: 2009-11-01 2-C-17 JAR-FSTD H

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued)

text: NOTE: Where an FTD Level 1 simulates a single helicopter system, it shall comply with the subjective and objective tests relevant to that system. 1.4 Terminology.

text: 1.4.1 Terminology and abbreviations of terms used in this ACJ are contained in ACJ to FSTD H.005. 1.5 Testing for FSTD qualification 1.5.1 The FSTD should be assessed in those areas which are essential to completing the flight crewmember training, testing and checking process. This includes the FSTD’s longitudinal and lateraldirectional responses; performance in take-off, hover, climb, cruise, descent, approach, touchdown; specific operations; control checks; flight deck and instructor station functions checks; and certain additional requirements depending on the complexity or Qualification Level of the FSTD. The motion and visual systems (where applicable) will be evaluated to ensure their proper operation. 1.5.2 The intent is to evaluate the FSTD as objectively as possible. Pilot acceptance, however, is also an important consideration. Therefore, the FSTD will be subjected to validation, and functions and subjective tests listed in Part 2 and 3 of this ACJ. Validation tests are used to compare objectively FSTD and aircraft data to ensure that they agree within specified tolerances. Functions and subjective tests provide a basis for evaluating FSTD capability to perform over a typical training period and to verify correct operation of the FSTD. 1.5.3 Tolerances listed for parameters in the validation tests (Paragraph 2) of this ACJ are the maximum acceptable for FSTD qualification and should not be confused with FSTD design tolerances. 1.5.4 For initial qualification of FSTDs helicopter manufacturer’s validation flight test data is preferred. Data from other sources may be used, subject to the review and concurrence of the Authority.

text: 1.5.5 In the case of new aircraft programmes, the aircraft manufacturer’s data partially validated by flight test data, may be used in the interim qualification of the FSTD. However, the FSTD should be reevaluated following the release of the manufacturer’s approved data. The schedule should be as agreed by the Authority, FSTD operator, FSTD manufacturer, and aircraft manufacturer. 1.5.6 FSTD operators seeking initial or upgrade evaluation of a FSTD should be aware that performance and handling data for older aircraft may not be of sufficient quality to meet some of the test standards contained in this ACJ. In this instance it may be necessary for an operator to acquire additional flight test data. 1.5.7 During FSTD evaluation, if a problem is encountered with a particular validation test, the test may be repeated to ascertain if the problem was caused by test equipment or FSTD operator error. Following this, if the test problem persists, an FSTD operator should be prepared to offer an alternative test.

text: 1.5.8 Validation tests which do not meet the test criteria should be addressed to the satisfaction of the Authority. 1.6 Qualification Test Guide (QTG) 1.6.1 The QTG is the primary reference document used for evaluating a FSTD. It contains test results, statements of compliance and other information for the evaluator to assess if the FSTD meets the test criteria described in this ACJ.

text: 1.6.2 The FSTD operator should submit a QTG which includes: a. A title page with FSTD operator and approval Authority signature blocks. b. A FSTD information page (for each configuration in the case of convertible FSTDs) providing: (i) FSTD operator’s FSTD identification number. (ii) Helicopter model and series being simulated. (iii) References to aerodynamic data or sources for aerodynamic model. (iv) References to engine data or sources for engine model. (v) References to flight control data or sources for flight controls model. (vi) Avionic equipment system identification where the revision level affects the training and checking capability of the FSTD.

text: JAR-FSTD H 2-C-18 2009-11-01

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued) (vii) FSTD model and manufacturer. (viii) Date of FSTD manufacture. (ix) FSTD computer identification. (x) Visual system type and manufacturer (if fitted). (xi) Motion system type and manufacturer (if fitted). c. Table of contents. d. List of effective pages and log of test revisions. e. Listing of all reference and source data.

text: f. Glossary of terms and symbols used. g. Statements of Compliance (SOC) with certain requirements. SOC’s should refer to sources of information and show compliance rationale to explain how the referenced material is used, applicable mathematical equations and parameter values, and conclusions reached. h. Recording procedures and required equipment for the validation tests. i. The following items are required for each validation test:

text: (i) Test title. This should be short and definitive, based on the test title referred to in paragraph 2.3 of this ACJ; (ii) Test objective. This should be a brief summary of what the test is intended to demonstrate; (iii) Demonstration procedure. This is a brief description of how the objective is to be met; (iv) References. These are the helicopter data source documents including both the document number and the page or condition number; (v) Initial conditions. A full and comprehensive list of the test initial conditions is required; (vi) Manual test procedures. Procedures should be sufficient to enable the test to be flown by a qualified pilot, using reference to flight deck instrumentation and without reference to other parts of the QTG or flight test data or other documents; (vii) Automatic test procedures (if applicable). (viii) Evaluation criteria. Specify the main parameter(s) under scrutiny during the test; (ix) Expected result(s). The helicopter result, including tolerances and, if necessary, a further definition of the point at which the information was extracted from the source data; (x) Test result. Dated FSTD validation test results obtained by the FSTD operator. Tests run on a computer which is independent of the FSTD are not acceptable. (xi) Source data. Copy of the helicopter source data, clearly marked with the document, page number, issuing authority, and the test number and title as specified sub-para (i) above. Computer generated displays of flight test data overplotted with FSTD data are insufficient on their own for this requirement. (xii) Comparison of results. An acceptable means of easily comparing FSTD test results with the validation flight test data. Note: The preferred method is overplotting. The FSTD operator’s FSTD test results should be recorded on a multi-channel recorder, line printer, electronic capture and display or other appropriate recording media acceptable to the Authority conducting the test. FSTD results should be labelled using terminology common to helicopter parameters as opposed to computer software identifications. These results should be easily compared with the supporting data by employing cross plotting or other acceptable means. Helicopter data documents included in the QTG may be photographically reduced only if such reduction will not alter the graphic scaling or cause difficulties in scale interpretation or resolution. Incremental scales on graphical presentations should provide resolution necessary for evaluation of the parameters shown in paragraph 2. The test guide will provide the documented proof of compliance with the FSTD validation tests in the tables in paragraph 2. For tests involving time histories, flight test data sheets, FSTD test results should be clearly marked with appropriate reference points to ensure an accurate comparison between the FSTD and helicopter with respect to time. FSTD operators using line printers to record time histories should clearly mark that information taken from line printer data output for cross plotting on the helicopter data. The cross plotting of the FSTD operator’s simulator data to helicopter data is essential to verify FSTD performance in each test. The evaluation serves to validate the FSTD operator’s FSTD test results. j. A copy of the version of the primary reference document as agreed with the Authority and used in the initial evaluation should be included.

text: 2009-11-01 2-C-19 JAR-FSTD H

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued) 1.7 Configuration control. A configuration control system should be established and maintained to ensure the continued integrity of the hardware and software as originally qualified. 1.8 Procedures for initial FSTD qualification

text: 1.8.1 The request for evaluation should reference the QTG and also include a statement that the FSTD operator has thoroughly tested the FSTD and that it meets the criteria described in this document except as noted in the application form. The FSTD operator should further certify that all the QTG checks, for the requested Qualification Level, have been achieved and that the FSTD is representative of the helicopter. 1.8.2 A copy of the FSTD operator’s QTG, marked with test results, should accompany the request. Any QTG deficiencies raised by the Authority should be addressed prior to the start of the on-site evaluation. 1.8.3 The FSTD operator may elect to accomplish the QTG validation tests while the FSTD is at the manufacturer’s facility. Tests at the manufacturer’s facility should be accomplished at the latest practical time prior to disassembly and shipment. The FSTD operator should then validate FSTD performance at the final location by repeating at least one-third of the validation tests in the QTG and submitting those tests to the Authority. After review of these tests, the Authority will schedule an initial evaluation. The QTG should be clearly annotated to indicate when and where each test was accomplished. 1.9 FSTD recurrent qualification basis 1.9.1 Following satisfactory completion of the initial evaluation and qualification tests, a periodic check system should be established to ensure that FSTDs continue to maintain their initially qualified performance, functions and other characteristics. 1.9.2 The FSTD operator should run the complete QTG, which includes validation, functions & subjective tests, between each annual evaluation by the Authority. As a minimum, the QTG tests should be run progressively in at least four approximately equal 3 monthly blocks on an annual cycle. Each block of QTG tests should be chosen to provide coverage of the different types of validation, functions & subjective tests. Results shall be dated and retained in order to satisfy both the FSTD operator as well as the Authority that the FSTD standards are being maintained. It is not intended that the complete QTG is run just prior to the annual evaluation. 2 FSTD Validation Tests 2.1 General 2.1.1 FSTD performance and system operation should be objectively evaluated by comparing the results of tests conducted in the FSTD with helicopter data unless specifically noted otherwise. To facilitate the validation of the FSTD, an appropriate recording device acceptable to the Authority should be used to record each validation test result. These recordings should then be compared to the approved validation data. 2.1.2 Certain tests in this ACJ are not necessarily based upon validation data with specific tolerances. However, these tests are included here for completeness, and the required criteria should be fulfilled instead of meeting a specific tolerance.

text: 2.1.3 The FSTD MQTG should describe clearly and distinctly how the FSTD will be set up and operated for each test. Use of a driver programme designed to accomplish the tests automatically is encouraged. Overall integrated testing of the FSTD should be accomplished to assure that the total FSTD system meets the prescribed standards. Historically, the tests provided in the QTG to support FSTD qualification have become increasingly fragmented. During the development of the ICAO Manual of Criteria for the Qualification of Flight Simulators, 1993 by a RAeS Working Group, the following text was inserted: “It is not the intent, nor is it acceptable, to test each Flight Simulator subsystem independently. Overall Integrated Testing of the Flight Simulator should be accomplished to assure that the total Flight Simulator system meets the prescribed standards.”

text: JAR-FSTD H 2-C-20 2009-11-01

text: Bilaga 2

text: This text was developed to ensure that the overall testing philosophy within a QTG fulfilled the original intent of validating the FSTD as a whole whether the testing was carried out automatically or manually.

text: To ensure compliance with this intent, QTGs should contain explanatory material which clearly indicates how each test (or group of tests) is constructed and how the automatic test system is controlling the test e.g. which parameters are driven, free, locked and the use of closed and open loop drivers. A test procedure with explicit and detailed steps for completion of each test must also be provided. Such information should greatly assist with the review of a QTG which involves an understanding of how each test was constructed in addition to the checking of the actual results. A manual test procedure with explicit and detailed steps for completion of each test should also be provided. 2.1.4 Submittals for approval of data other than flight test should include an explanation of validity with respect to available flight test information. Tests and tolerances in this paragraph should be included in the FSTD MQTG.

text: 2.1.5 The table of FSTD Validation Tests in this ACJ indicates the test requirements. Unless noted otherwise, FSTD tests should represent helicopter performance and handling qualities at operating weights and centres of gravity (cg) positions typical of normal operation. For FFS devices, 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 should be included. Certain tests which are relevant only at one extreme weight or cg condition need not be repeated at the other extreme. Tests of handling qualities should include validation of augmentation devices. 2.1.6 For the testing of Computer Controlled Helicopter (CCH) FSTDs, flight test data are required for both the normal (N) and non-normal (NN) control states, as applicable to the helicopter simulated and, as indicated in the validation requirements of this paragraph. Tests in the non-normal state should always include the least augmented state. Tests for other levels of control state degradation may be required as detailed by the Authority at the time of definition of a set of specific helicopter tests for FSTD data. Where applicable, flight test data should record: a. pilot controller deflections or electronically generated inputs including location of input; and b. rotor blade pitch position or equivalent 2.1.7 Where extra equipment is fitted, such as a motion system or in an FTD Level 1 or FNPT Level I, a visual system, such equipment is expected to satisfy, as a minimum, tests as follows:

text: a. Visual system: where fitted to an FNPT Level I or FTD Level 1, validation tests are those specified for a FNPT Level II or for a FTD Level 2 respectively. b. Motion system: where fitted to an FTD or FNPT, validation tests are those specified for a Level A FFS. 2.2 Test requirements

text: 2.2.1 The ground and flight tests required for qualification are listed in the table of FSTD Validation Tests. Computer generated FSTD test results should be provided for each test. The results should be produced on an appropriate recording device acceptable to the Authority. Time histories are required unless otherwise indicated in the table of validation tests. 2.2.2 Approved validation data which exhibit rapid variations of the measured parameters may require engineering judgement when making assessments of FSTD validity. Such judgement should not be limited to a single parameter. All relevant parameters related to a given manoeuvre or flight condition should be provided to allow overall interpretation. When it is difficult or impossible to match FSTD to helicopter data or approved validation data throughout a time history, differences should be justified by providing a comparison of other related variables for the condition being assessed. Tolerances should be only applied in the validity domain of the parameter sensors. 2.2.2.1 Parameters, tolerances, and flight conditions.

text: 2009-11-01 2-C-21 JAR-FSTD H

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued)

text: a. The table of FSTD validation tests in paragraph 2.3 below describes the parameters, tolerances, and flight conditions for FSTD validation. When two tolerance values are given for a parameter, the less restrictive may be used unless indicated otherwise. Where tolerances are expressed as a percentage: b. for parameters that have units of percent, or parameters normally displayed in the cockpit in units of percent (e.g. N1, N2, engine torque or power), then a percentage tolerance will be interpreted as an absolute tolerance unless otherwise specified (i.e. for an observation of 50% N1 and a tolerance of 5%, the acceptable range shall be from 45% to 55%). c. for parameters not displayed in units of percent, a tolerance expressed only as a percentage will be interpreted as the percentage of the current reference value of that parameter during the test, except for parameters varying around a zero value for which a minimum absolute value should be agreed with the Authority. d. If a flight condition or operating condition is shown which does not apply to the qualification level sought, it should be disregarded. FSTD results should be labelled using the tolerances and units specified. 2.2.2.2 Flight condition verification. When comparing the parameters listed to those of the helicopter, sufficient data should also be provided to verify the correct flight condition. All airspeed values should be clearly annotated as to indicated, calibrated, true airspeed, etc… and like values used for comparison.

text: 2.2.2.3 Where the tolerances have been replaced by ‘Correct Trend and Magnitude’ (CT&M), the FSTD should be tested and assessed as representative of the helicopter to the satisfaction of the Authority. To facilitate future evaluations, sufficient parameters should be recorded to establish a reference. For the initial qualification of FNPTs no tolerances are to be applied and the use of CT&M is to be assumed throughout. 2.2.2.4 For the conditions where the design of the flight controls system does not imply any difference on the rotor blade pitch positions between augmented case and unaugmented case, unaugmented case validation data are not required for the unaugmented case. A rationale is to be provided to identify which tests are not performed. 2. 3 Table of FSTD Validation Tests 2.3.1 A number of tests within the QTG have had their requirements reduced to ‘Correct Trend and Magnitude’ (CT&M) for initial evaluations thereby avoiding the need for specific Flight Test Data. Where CT&M is used it is strongly recommended that an automatic recording system be used to ‘footprint’ the baseline results thereby avoiding the effects of possible divergent subjective opinions on recurrent evaluation. However, the use of CT&M is not to be taken as an indication that certain areas of simulation can be ignored. It is imperative that the specific characteristics are present, and incorrect effects would be unacceptable. 2.3.2 In all cases the tests are intended for use in recurrent evaluations at least to ensure repeatability. Note 1: It is accepted that tests and associated tolerances will only apply to a Level 1 FTD if that system or flight condition is simulated. Note 2: For piston engines, suitable alternative parameters should be used, which have to be agreed with the Authority.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD H 2-C-22 2009-11-01

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: TESTS TOLERANCE FLIGHT CONDITIONS FSTD LEVEL COMMENTS R-

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( 1. PERFORMANCE c onti n a. Engine Assessment u ed)

text: (1) Start Operations Light Off Time Ground Rotor Brake C 9 9 9 C 9 9 9 9 9 Time histories of each ± 10% or ± 1 sec used / Not used T T engine from initiation of start (i) Engine Start and & & sequence to steady state idle acceleration Torque ± 5% M M and from steady state idle to (transient) operating RPM. Rotor Speed ± 3%

text: C-

text: 23 Fuel Flow ± 10% Tolerance to be only applied Gas Generator Speed in the validity domain of the ± 5% engine parameter sensors

text: Power Turbine Speed ± 5%

text: Turbine Gas Temp. ± 30°C

text: JA R-FS

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: TESTS TOLERANCE FLIGHT CONDITIONS FSTD LEVEL COMMENTS

text: H to

text: JAR- :8 FFS FTD FNPT 7 FSTD H. A B C D 1 2 3 I II III MCC

text: (ii) Steady State Idle Torque ± 3% Ground C 9 9 9 C 9 9 9 9 9 Present data for both steady and Operating RPM T T state idle and operating RPM 03 Conditions Rotor Speed ± 1.5% & & conditions. May be a 0 ( c M M snapshot tests. onti Fuel Flow ± 5% nued)

text: Gas Generator Speed ± 2%

text: 2- Power Turbine Speed

text: C-

text: ± 2%

text: 2 4

text: Turbine Gas Temp. ± 20°C

text: (2) Power Turbine ± 10% of total change Ground C 9 9 9 C 9 9 9 9 9 Time history of engine Speed Trim of power turbine speed T T response to trim system & & actuation (both directions) or M M

text: ± 0.5% rotor speed

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( (3) Engine & Rotor Torque ± 5% Climb / Descent C 9 9 9 C 9 9 C 9 9 9 Collective step inputs. Can c onti Speed Governing T T T be conducted with climb & Rotor Speed ± 1.5% & & & descent performance tests n u ed) M M M

text: b. Ground Operations

text: C-

text: (1) Minimum Radius Helicopter turn radius ± Ground 9 9 9 If differential braking is used,

text: Turn 3ft (0.9m) or 20% brake force shall be set at the helicopter test flight value.

text: (2) Rate of Turn vs Turn rate Ground 9 9 9 Without use of wheel brake o Pedal Deflection or ± 10% or 2 / sec nosewheel angle

text: JA R-FS

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7 FSTD H. A B C D 1 2 3 I II III MCC o (3) Taxi Pitch attitude ± 1.5 Ground C 9 9 9 Control Position & Pitch T Attitude during ground taxi 03 Torque ± 3% & for a specific ground speed & 0 ( c M direction, and density altitude onti Longitudinal Control nued) Position ± 5%

text: Lateral Control Position ± 5%

text: 2- C-

text: Directional Control

text: 6 Position ± 5%

text: Collective Control Position ± 5%

text: (4) Brake Time : ± 10% or ± 1s Ground C 9 9 9 C C C Record data Until full stop. Effectiveness T T T T and & & & & M M M M Distance : ± 10% or ± 30m (100ft)

text: c. Take-off

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 Airspeed 0 ( (1) All engines Ground/lift off and initial C 9 9 9 C 9 9 9 9 9 Time history of takeoff flight c ± 3 kt onti climb T T path as appropriate to Altitude & & helicopter model simulated n ± 20 ft (6.1 m) u ed) Torque M M [running take off for FFS ± 3% Level B & FTD Level 2. Rotor Speed Takeoff from a hover for FS ± 1.5% Level C & D or FTD Level 3 Pitch Attitude ]. ± 1.5° Bank Attitude For FFS Level B and FTD C- ± 2° Level 2, criteria apply only to 27 Heading those segments at airspeeds ± 2° above effective translational Longitudinal Control lift. Position ± 10% Lateral Control Record data to at least 200 ft Position (61 meters)AGL/Vy ± 10% whichever comes later Directional Control Position ± 10%

text: Collective Control Position ± 10%

text: (2) One Engine See 1.c.(1) above for Takeoff & initial climb C 9 9 9 C 9 9 9 9 9 Time history of takeoff flight JA Inoperative continued tolerances and flight T T path as appropriate to R-FS takeoff conditions & & helicopter model simulated. M M Record data to at least 200 ft TD (61 meters)AGL/Vy H whichever comes later TS

text: FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC 9 (3) One Engine Airspeed ± 3 kt Ground/Takeoff C C 9 9 9 9 9 Time history from the take off inoperative rejected T T point to touch down. Test 03 take off Altitude ± 20 ft (6.1m) 0 ( & & conditions near limiting c Torque ± 3% M M performance onti ± nued) Rotor Speed 1.5%

text: Pitch Attitude ± 1.5°

text: Bank Attitude ± 1.5° 2- Heading ± 2°

text: C-

text: 2 Longitudinal Control

text: Position ± 10%

text: Lateral Control Position ± 10%

text: Directional Control Position ± 10%

text: Collective Control Position ± 10%

text: Distance: ± 7.5% or ± 30m (100ft)

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( d. Hover Performance Torque ± 3% In Ground Effect (IGE) C 9 9 9 C 9 9 9 9 9 Light/heavy gross weights. c onti T T May be snapshot tests. Pitch Attitude ± 1.5° n & & u ed) Bank Attitude ± 1.5° M M Refer to point 2.4.2 below for Out of Ground Effect additional guidance. Longitudinal Control (OGE) Position ± 5%

text: Lateral Control Position ± 5%

text: Directional Control

text: C-

text: Position ± 5% 29 Stability augmentation Collective Control on and off Position ± 5%

text: e. Vertical Climb Vertical Velocity ± 100 From OGE Hover C 9 9 9 C 9 9 9 9 9 Light/heavy gross weights. Performance fpm (0.50 m/sec) or T T May be snapshot tests. 10% & & M M Directional Control Position ± 5% Stability augmentation Collective Control on and off JA Position ± 5%

text: R-FS

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA

text: Bi TS

text: R- ACJ No

text: la

text: F FS

text: ga 2

text: S 2 TD .1 009

text: H to JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: f. Level Flight Torque ± 3% Cruise Stability C 9 9 9 C 9 9 9 9 9 9 Two combination of gross Performance and T T weight/cg and two speeds 03 Trimmed Flight Pitch Attitude ± 1.5° & & within the flight envelope. 0 ( c Control Position M M onti Sideslip Angle ± 2° May be snapshot tests. nued)

text: Longitudinal Control Stability augmentation For FNPT Level 1 changes in Position ± 5% on or off Cg are not required

text: 2- Lateral Control C- Position ± 5% 3 0 Directional Control Position ± 5%

text: Collective Control Position ± 5%

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( g. Climb Performance Vertical Velocity ± All engines operating C 9 9 9 C 9 9 9 9 9 9 Two gross weight/cg c onti and Trimmed Flight 100fpm (0.50 m/sec) or T T combinations. Control Position 10% & & n u ed) M M Data presented at relevant Pitch Attitude ± 1.5° climb power conditions. The achieved measured vertical Sideslip Angle ± 2° One engine velocity of the FSTD cannot inoperative be less than the appropriate Longitudinal Control Approved Flight Manual Position ± 5% values. For FNPT Level 1 C- changes in Cg are not 31 Lateral Control required. Position ± 5% May be snapshot tests. Directional Control Position ± 5% Stability augmentation on or off Collective Control Position ± 5%

text: Speed ± 3kts

text: JA R-FS

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: 0 (

text: c onti

text: h. Descent nued)

text: Torque ± 3% (1) Descent At or near 1000 fpm C 9 9 9 C 9 9 9 9 9 9 Two gross weight/CG Pitch Attitude ± 1.5° Performance and (5m/sec) Rate of T T combinations Sideslip Angle ± 2° trimmed Flight Control Descent (RoD) at & & 2- Longitudinal Control Position normal approach M M For FNPT Level 1 changes in C- Position ± 5% speed. Cg are not required. 3 Lateral Control

text: Position ± 5% Stability augmentation May be snapshot tests Directional Control on or off Position ± 5%

text: Collective Control

text: Position ± 5%

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H.

text: A B C D 1 2 3 I II III MCC 03

text: Vertical Velocity ± 0 ( (2) Autorotation Steady descents C 9 9 9 9 9 9 9 9 9 Two gross weight/CG c 100fpm (0.50 m/sec) or onti Performance and T combinations. 10% n trimmed Flight Control & u Rotor Speed ± 1.5% ed) Position M Rotor speed tolerance only Pitch Attitude ± 1.5° Stability augmentation applies if collective control Sideslip Angle ± 2° on or off position is fully down. Longitudinal Control

text: Position ± 5% Speed sweep from Lateral Control approximately 50 kt to at Position ± 5% least maximum glide Directional Control C- distance airspeed. May be a Position ± 5% 33 series of snapshot tests. Collective Control

text: Position ± 5%

text: Torque ± 3% 9 i. Auto-rotational Cruise or climb C 9 9 9 9 9 9 9 9 Time history of vehicle Rotor speed ± 3% Entry T response to a rapid power Pitch Attitude ± 2° & reduction to idle. Roll Attitude ± 3° M Heading ± 5° If cruise, data should be Airspeed ± 5 kt presented for the maximum Altitude ± 20ft (6.1m) range airspeed. If climb, data

text: should be presented for the

text: maximum rate of climb

text: JA airspeed at or near maximum

text: R-FS continuous power.

text: TD H TS

text: j. Landing FS

text: Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: Airspeed ± 3 kt (1) All Engines Approach and landing C 9 9 9 C 9 9 C 9 9 9 Time history of approach and Altitude ± 20 ft (6.1m) T T T landing profile as appropriate 03 Torque ± 3% 0 ( & & & to helicopter model simulated Rotor Speed ± 1.5% c M M M (running landing for FFS onti Pitch Attitude ± 1.5° Level B / FTD Level 2, nued) Bank Attitude ± 1.5° approach to a hover and to Heading ± 2° touchdown for FFS Level C & Longitudinal Control D / FTD Level 3 ). Position ± 10%

text: 2- Lateral Control For FFS levels A & B, and C- Position ± 10% FTD Levels 1 and 2, & FNPT 3 Directional Control 4 Level II and IIIcriteria apply Position ± 10% only to those segments at Collective Control airspeeds above effective Position ± 10% translational lift.

text: (2) One Engine See 1j(1) above for Approach and landing C 9 9 9 C 9 9 9 9 9 Include data for both

text: Inoperative tolerances T T Category A & Category B

text: & & Approaches & landings as

text: M M appropriate to the helicopter

text: model being simulated.

text: For FFS levels A & B, and SE

text: FTD Levels 1 and 2, and

text: CTIO

text: FNPT Level II and III criteria

text: apply to only those segments

text: N

text: at airspeeds above effective

text: translational lift

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09 to J -11 O A N 2 TESTS TOLERANCE FLIGHT CONDITIONS FSTD LEVEL COMMENTS R- -0 1 FSTD 2- FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( (3) Balked See 1j(1) above for Approach, one engine 9 9 9 9 9 9 9 9 From a stabilized approach c onti Landing/missed tolerances inoperative at the landing decision point approach (LDP). n u ed)

text: C- 35

text: JA R-FS

text: TD H TS

text: FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: (4) Auto-rotational Airspeed ± 3kts Approach and 9 9 C C Time history of auto- Landing with Touchdown T T rotational deceleration and 03 Touchdown Torque ± 3% & & touchdown from a stabilized 0 ( c M M auto-rotational descent. onti Rotor Speed ±3% nued)

text: Altitude ± 20ft (6.1m)

text: Pitch Attitude ± 2°

text: 2- C-

text: Bank Attitude ± 2°

text: 3 6

text: Heading ± 5°

text: Longitudinal Control Position ± 10%

text: Lateral Control Position ± 10%

text: Directional Control Position ± 10%

text: Collective Control Position ± 10%

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( 2. HANDLING c onti

text: QUALITIES

text: n u ed)

text: a. Control System Mechanical Characteristics

text: (1) Cyclic Breakout ± 0.25 lb Ground, Static 9 9 9 9 C 9 9 9 9 9 9 Uninterrupted control (0.112 daN) or 25% T sweeps. Trim On and Off & C- Force ± 0.5 lb (0.224 M This test is not required for 37 daN) or 10% Friction Off aircraft hardware modular controllers. Cyclic position Stability augmentation vs. force shall be measured on and off at the control. An alternate method acceptable to the Authority in lieu of the test fixture at the controls would be to instrument the FSTD in an equivalent manner to the flight test helicopter. The force position data from instrumentation can be directly recorded and JA matched to the helicopter R-FS data. Such a permanent installation could be used TD without requiring any time for H installation of external TS devices. FS

text: Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7 FSTD H. A B C D 1 2 3 I II III MCC (2) Collective/Pedals Breakout ± 0.5 lb Ground, Static 9 9 9 9 C 9 9 9 9 9 9 Uninterrupted control (0.224 daN) or 10% T sweeps. 03 Trim On/Off & 0 ( c Force ± 1.0 lb (0.448 M This test is not required for onti daN) or 10% Friction Off aircraft hardware modular nued) controllers. Collective and Stability augmentation pedal position vs. force shall on/off be measured at the control. An alternate method 2- acceptable to the Authority in

text: C-

text: lieu of the test fixture at the

text: 8 controls would be to instrument the FSTD in an equivalent manner to the flight test helicopter. The force position data from instrumentation can be directly recorded and matched to the helicopter data. Such a permanent installation could be used without requiring any time for installation of external devices.

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( (3) Brake Pedal Force ± 5 lb (2.224 daN) Ground, Static C 9 9 9 C 9 9 Simulator computer output c onti vs Position T T results may be used to show or 10% & & compliance. n u ed) M M

text: (4) Trim System Rate Rate ± 10% Ground, Static 9 9 9 9 C 9 9 9 9 9 9 Tolerance applies to (all applicable axes) T recorded value of trim rate. Trim on & M C- Friction off

text: (5) Control Dynamics ± 10% of time for first Hover and Cruise 9 9 9 C 9 Control dynamics for (all axes) zero crossing and T irreversible control systems Trim on & may be evaluated in a ± 10 (N+1)% of period ground/static condition. Data M thereafter Friction off should be for a normal control displacement in both ± 10% amplitude of Stability augmentation directions in each axis first overshoot on and off (approximately 25% to 50% of full throw). N is the ± 20% of amplitude of sequential period of a full 2nd and subsequent cycle of oscillation. Refer to overshoots greater 2.4.1 below. JA than 5% of initial R-FS displacement

text: TD ± 1 overshoot

text: H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: (6) Free play ± 0.10 in (2.5mm) Ground, Static 9 9 9 9 9 Applies to all controls. 03 Friction Off 0 ( c onti b. Low Airspeed nued)

text: Handling Qualities

text: (1) Trimmed Flight Torque ± 3% Translational Flight 9 9 9 9 Several airspeed increments Control Positions IGE. Sideways, to translational airspeed

text: 2- ±

text: Pitch Attitude 1.5° rearward and forward limits and 45 kt forward. May

text: C-

text: be a series of snapshot tests.

text: 0 Bank Attitude ± 2° Stability augmentation on or off Longitudinal Control Position ± 5%

text: Lateral Control Position ± 5%

text: Directional Control Position ± 5%

text: Collective Control Position ± 5%

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( (2) Critical Azimuth Torque ± 3% Hover 9 9 9 9 Present data for three c onti relative wind directions Pitch Attitude ± 1.5° Stability augmentation (including the most critical n u ed) on or off case) in the critical quadrant. Bank Attitude ± 2° May be a snapshot test. Longitudinal Control Position ± 5%

text: Lateral Control Precise wind measurement is C- Position ± 5% very difficult and simulated 41 wind obtained by Directional Control translational flight in calm Position ± 5% weather condition (no wind) is preferred in order to Collective Control control precisely flight Position ± 5% conditions by using groundspeed measurement (usually GPS).

text: In this condition, it would be more practical to realize this test with tests 2b (1) in order to ensure consistency JA between critical azimuth and R-FS other directions (forward, sideward and rearward)

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: (3) Control Response 03 (i) Longitudinal Pitch Rate ± 10% or ± Hover Stability 9 9 C 9 Step control input. Off axis 0 ( c 2°/sec augmentation on and T response must show correct onti off & trend for unaugmented nued) Pitch Attitude Change M cases. ± 10% or ± 1.5°

text: 2- Roll Rate (ii) Lateral Hover Stability 9 9 C 9 Step control input. Off axis

text: C- ± ±

text: 10% or 3°/sec augmentation on and T response must show correct

text: 2 off & trend for unaugmented Roll Attitude Change M cases. ± 10% or ± 3°

text: (iii) Directional Yaw Rate ± 10% or ± Hover Stability 9 9 C 9 Step control input. Off axis 2°/sec augmentation on and T response must show correct off & trend for unaugmented Heading Change ± M cases. 10% or ± 2°

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( (iv) Vertical Normal Acceleration ± Hover Stability 9 9 C 9 Step control input. Off axis c onti 0.1g augmentation on and T response must show correct off & trend for unaugmented n u ed) M cases.

text: C- 43

text: c. Longitudinal Handling Qualities

text: (1) Control Response Pitch Rate ± 10% Cruise 9 9 9 C 9 Two cruise airspeeds to

text: or T include minimum power ± 2°/sec Stability augmentation & required speed. on and off M JA Pitch Attitude Change Step control input. Off axis R-FS ± ± response must show correct 10% or 1.5° trend for unaugmented cases

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7 FSTD H. A B C D 1 2 3 I II III MCC 9 (2) Static Stability Longitudinal Control Cruise or Climb 9 9 9 9 C 9 Minimum of two speeds on Position ± 10% of T each side of the trim speed. 03 change from trim or ± and & 0 ( c 0.25 in (6.3 mm) May be a series of snapshot onti M Autorotation tests. nued) or Stability augmentation Longitudinal Control on or off Force ± 0.5 lb (0.224 2- daN) or ± 10%

text: C- 4

text: 4 (3) Dynamic Stability

text: (i) Long Term ± 10% of Calculated Cruise 9 9 9 C 9 9 9 9 Test should include three full Response Period T cycles (6 overshoots after Stability augmentation & input completed) or that ± 10% of Time to 1/2 off M sufficient to determine time or to ½ or double amplitude, whichever is less. For non- Double Amplitude or periodic response the time history should be matched. ± 0.02 of Damping Ratio

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( (ii) Short Term ± 1.5° Pitch attitude or Cruise or Climb 9 9 9 C 9 9 9 9 Two airspeeds. Time history c onti Response T to validate short helicopter ± 2°/sec Pitch Rate Stability augmentation & response due to control n u ed) on and off M pulse input. Check to stop 4 ± 0.1 g Normal seconds after completion of Acceleration input.

text: (4) Manoeuvring Longitudinal Control Cruise or Climb C 9 9 9 C 9 9 Force may be a cross plot for C- Stability Position ± 10% of T T irreversible systems. Two 45 change from trim or ± & & airspeeds. 0.25 in (6.3 mm) M M Stability augmentation May be a series of snapshot or on or off tests. Approximately 30° and 45° bank attitude data should Longitudinal Control be presented. Force ± 0.5 lb (0.224 daN) or ± 10% Left and right turns

text: 9 (5) Landing Gear ± 1 sec Takeoff (Retraction) 9 9 9 9 9 9 9 9 9 9 Operating Time Approach (Extension)

text: JA d. Lateral & Directional R-FS Handling Qualities.

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA

text: Bi TS

text: R- ACJ No

text: la

text: F FS

text: ga 2

text: S 2 TD .1 009

text: H to JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: (1) Control Response Roll Rate ± 10% or ± Cruise Stability 9 9 9 C 9 9 9 9 9 Two airspeeds to include one at 3°/sec augmentation on and T or near the minimum power 03 (i) Lateral off & required speed. Step control 0 ( c Roll Attitude Change ± M input. Off axis response must onti 10% or ± 3° show correct trend for nued) unaugmented cases.

text: (ii) Directional Yaw rate ± 10% or 2 Cruise Stability 9 9 9 C 9 9 9 9 9 Two airspeeds to include one at

text: /sec. Yaw Attitude augmentation on and T or near the minimum power 2- 0 Change ± 10% or ± 2 off & required speed. Step control C- M input. Off axis response must 4 6 show correct trend for

text: unaugmented cases.

text: SE CTIO

text: N 2

text: 20 09 -11

text: -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( (2) Directional Static Lateral Control Position Cruise or C 9 9 9 C 9 9 Steady heading sideslip. c onti Stability ± 10% of change from T T Minimum of two sideslip angles trim or ± 0.25in (6.3 mm) (Climb and Descent) & & on either side of the trim point. n u ed) , or , Lateral Control M M Force may be a cross plot for Force ± 0.5 lb (0.224 Stability augmentation on irreversible control systems. daN) or ± 10% or off May be a snapshot test.

text: Roll Attitude ± 1.5°

text: Directional Control C- Position ± 10% of 47 change from trim or ± 0.25 in (6.3 mm) or Directional Control Force ± 1 lb (0.448 daN) or ± 10%

text: Longitudinal Control Position ± 10% of change from trim or ± .25in (6.3mm)

text: JA (3) Dynamic Lateral and R-FS Directional Stability

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: (i) Lateral-Directional ± 0.5 sec or ± 10% of Cruise or Climb C 9 9 9 C C 9 9 9 9 Two airspeeds. Excite with Oscillations Period T T T cyclic or pedal doublet. Test 03 Stability augmentation on & & & should include six full cycles (12 0 ( c ± 10% of Time to ½ or and off M M M overshoots after input onti Double Amplitude or ± completed) or that sufficient to nued) .02 of Damping Ratio determine time to ½ or double amplitude, whichever is less. For non-periodic response, time history should be matched. 2- ± 20% or ± 1 sec of

text: C-

text: Time Difference between

text: 8 peaks of Bank and Sideslip

text: (ii) Spiral Stability Correct trend on Bank - Cruise or Climb C 9 9 9 C C 9 9 9 9 Time history of release from ±2° or ± 10% in 20 sec T T T pedal only or cyclic only turns in Stability augmentation on & & & both directions. Terminate and off M M M check at zero bank or unsafe attitude for divergent cases.

text: (iii) Adverse/Proverse Correct trend on side slip Cruise or Climb C 9 9 9 C 9 Time history of initial entry into Yaw ±2° T T cyclic only turns in both Stability augmentation on & & directions. Use moderate cyclic SE and off M M input rate. CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( 3. ATMOSPHERIC c onti

text: MODELS

text: n u ed) (1) A test to N/A Take-off, Cruise and 9 9 9 9 9 9 9 9 9 9 demonstrate turbulence Landing models

text: (2) Tests to 9 9 9 9 demonstrate other atmospheric models to C- support the required 49 training

text: 4. MOTION SYSTEM **

text: a. Motion Envelope

text: (1) Pitch N/A

text: (i) Displacement

text: ± 20 9 9

text: 0/ ± 25 9 9

text: JA

text: (ii) Velocity

text: R-FS

text: ± 15 /sec 9 9

text: TD H TS ** FS

text: For Level A, if more than the three specified degrees of freedom (DOF) are used, then the corresponding Level B performance standards should be used.

text: Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: o ±20 /sec 9 9 03 0 ( c onti (iii)Acceleration nued)

text: o ±75 /sec² 9 9

text: o ± 100 /sec² 9 9

text: (2) Roll N/A

text: C- 5

text: 0 (i) Displacement

text: ± 20 9 9

text: ± 25 9 9

text: (ii) Velocity

text: ± 15 /sec 9 9

text: o ±20 /sec 9 9

text: (iii)Acceleration

text: o ±75 /sec 9 9

text: SE

text: o CTIO

text: ± 100 /sec 9 9

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( (3) Yaw N/A c onti (i) Displacement n u ed)

text: ± 25 9 9 9

text: (ii) Velocity

text: ± 15 /sec 9

text: C-

text: o 51 ±20 /sec 9 9

text: (iii)Acceleration

text: o 9 ±75 /sec²

text: o ± 100 /sec² 9 9

text: (4) Vertical N/A

text: (i) Displacement

text: ± 22 in 9 9

text: JA

text: R-FS ± 34 in 9 9

text: TD (ii) Velocity

text: H TS

text: ± 16 in/sec 9 9 FS

text: Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: ± 24 in/sec 9 9 03 0 ( (iii) Acceleration c onti ± 0.6g 9 9 nued)

text: ± 0.8g 9 9

text: (5) Lateral N/A

text: 2- C-

text: (i) Displacement

text: 5 2

text: ± 26in 9

text: ± 45in 9 9

text: (ii) Velocity

text: ± 20 in/sec 9

text: ± 28 in/sec 9 9

text: (iii) Acceleration

text: ± 0.4g 9 SE

text: CTIO

text: ± 0.6g 9 9

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( (6) Longitudinal N/A c onti (i) Displacement n u ed) ± 27in 9

text: ± 34in 9 9

text: (ii) Velocity

text: C- ± 20in/sec 9

text: ± 28in/sec 9 9

text: (iii) Acceleration

text: ± 0.4g 9

text: ± 0.6g 9 9

text: (7) Initial Rotational N/A All relevant rotational axes

text: Acceleration Rate

text: JA All Axes ± 9 9 R-FS 225 /sec²/sec

text: TD ± 9 9 H 300 /sec²/sec TS

text: FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: (8) Initial Linear N/A Acceleration Rate 03 0 ( (i) Vertical c onti 9 9 nued) ± 4g/sec

text: ± 6g/sec 9 9

text: 2- (ii) Lateral

text: C- 5

text: 4 ± 2g/sec 9

text: ± 3g/sec 9 9

text: (iii) Longitudinal

text: ± 2g/sec 9

text: ± 3g/sec 9 9

text: b. Frequency Phase Amplitude N/A 9 9 9 All six axis

text: Response Band, Hz

text: SE

text: Deg Ratio Db

text: CTIO

text: 0.1 to- 1.0 0 to -20 ± 2

text: N

text: 1.1 to 3.0

text: 0 to -40 ± 4

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( c. Leg Balance 1.5 deg N/A 9 9 9 The phase shift between a c onti datum jack & any other jack shall be measured using a n u ed) heave (vertical) signal of or 0.5hz at ± 0.25g

text: Parasitic Acceleration 0.02g or 3deg/sec² The acceleration in the other (peak) five axes should be measured using a heave (vertical) signal of 0.5hz at ± C- 0.1g

text: d. Turn Around 0.05g 9 9 9 The motion base shall be driven sinusoidally in heave through a displacement of 6 in (150 mm) peak to peak at a frequency of 0.5Hz. Deviation from the desired sinusoidal acceleration shall be measured

text: JA R-FS

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: e. Characteristic Refer to section 1, appendix vibrations / buffet 1 to JAR-FSTD H 030 03 paragraph 1.2.e.1. 0 ( c (1) Vibrations - onti Tests to include1/Rev +3 / -6db or ± 10% of On ground (idle Flt Nr); 9 Correct trend refers to a nued) and n/Rev vibrations nominal vibration level Low & High speed comparison of vibration where n is the in flight cruise & transition to & from amplitudes between different number of rotor correct trend (see hover; manoeuvres. E.g. If the 1/rev blades comment) Level flight; vibration amplitude in the 2- Climb/descent helicopter is higher during

text: C-

text: (including vertical steady state turns than in

text: 6 climb; level flight this increasing Auto-rotation; trend shall be demonstrated Steady Turns in the simulator.

text: (2) Buffet Refer to section 1, appendix 1 to JAR-FSTD H.030 A test with recorded +3 / -6db or ± 10% of On ground and in flight 9 paragraph 1.2.e.1. results is required for nominal vibration level characteristic buffet in flight cruise & The recorded test results for motion which can be correct trend (see characteristic buffets should sensed in the cockpit comment) allow the checking of relative amplitude for different frequencies. SE

text: CTIO

text: For atmospheric disturbance, general purpose models are

text: N

text: acceptable which

text: approximate demonstrable 20 flight test data

text: 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09 to J -11 O A N 2 TESTS TOLERANCE FLIGHT CONDITIONS FSTD LEVEL COMMENTS R- -0 1 FSTD 2- FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( f. Motion Cue N/A 9 9 9 See para 2.4.3.3 below c onti

text: Repeatability

text: n u ed)

text: 5. VISUAL SYSTEM

text: Note: Refer to the table of functions & subjective tests for C- additional visual tests. 57

text: JA R-FS

text: TD H TS

text: FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7 FSTD H. A B C D 1 2 3 I II III MCC a. Visual Ground Near end. The lights Trimmed in the landing 9 9 9 9 Visual Ground Segment. This Segment (VGS) computed to be visible configuration at 30 m test is designed to assess 03 should be visible in the (100 ft) wheel height items impacting the accuracy 0 ( c FSTD. above touchdown zone of the visual scene presented onti elevation on glide to a pilot at DH on an ILS nued) Far end : ± 20% of the slope at a RVR setting approach. Those items computed VGS of 300 m (1 000 ft) or include 350 m (1 200 ft) 1) RVR,

text: 2- C-

text: 2) Glideslope (G/S) and

text: 8 localiser modelling accuracy (location and slope) for an Static at 200 ft (61 m) ILS, landing gear height above touchdown zone 3) For a given weight, on glide slope with 550 configuration and speed metres or 1805ft RVR representative of a point within the helicopter’s operational envelope for a normal approach and landing.

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( Visual Ground 9 9 9 9 9 If non-homogenous fog is c onti Segment (VGS) used, the vertical variation in horizontal visibility should be n u ed) (continued) described and be included in the slant range visibility calculation used in the VGS computation.

text: The downward field of view may be limited by the aircraft C- structure or the visual system 59 display. whichever is the less.

text: b. Display System Tests

text: JA R-FS

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: 1. (a) Continuous Continuous visual field Not 9 Field of view should be cross-cockpit of view providing each 03 Applicable measured using a visual test visual field of view pilot with 180º horizontal 0 ( pattern filling the entire visual and 60º vertical field of c scene (all channels) onti view. consisting of a matrix of nued) Horizontal FOV: Not black and white 5° squares.

text: less than a total of 176º Installed alignment should be (including not less than confirmed in a Statement of 75º measured either Compliance. 2- side of the centre of the C- design eye point). The 75º minimums allows an

text: 0 offset either side of the Vertical FOV: Not less horizontal field of view if than a total of 56 º measured from the required for the intended pilot’s and co-pilot’s use.

text: eye point.

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( 1. (b) Continuous Continuous visual field Not Applicable 9 9 9 Field of view should be c cross-cockpit visual onti of view providing each measured using a visual test field of view n pilot with 150º pattern filling the entire visual u ed) horizontal and 60º scene (all channels) vertical field of view. consisting of a matrix of black and white 5° squares. Horizontal FOV: Not Installed alignment should be less than a total of confirmed in a Statement of 146º (including not less Compliance. than 60º measured C- either side of the The 60º minimums allows an 61 centre of the design offset either side of the eye point). horizontal field of view if required for the intended use.

text: Vertical FOV: Not less than a total of 56 º measured from the pilot’s and co-pilot’s eye point.

text: JA R-FS

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: 1. (c) Continuous Continuous visual field Not Applicable 9 9 9 9 Field of view should be cross-cockpit visual of view providing each measured using a visual test 03 field of view pilot with 150º pattern filling the entire visual 0 ( c horizontal and 40º scene (all channels) onti vertical field of view. consisting of a matrix of nued) black and white 5° squares. Horizontal FOV: Not Installed alignment should be less than a total of confirmed in a Statement of 146º (including not less Compliance. 2- than 60º measured

text: C-

text: either side of the The 60º minimums allows an

text: 2 centre of the design offset either side of the eye point). horizontal field of view if required for the intended Vertical FOV: Not less use. than a total of 36 º measured from the pilot’s and co-pilot’s eye point.

text: 1. (d) Visual field of visual system providing Not Applicable 9 view each pilot with 75º horizontal and 40º vertical field of view

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( visual system providing 9 c onti each pilot with 45º horizontal and 30º n u ed) vertical field of view

text: 2. Occulting Demonstration model Not applicable 9 9 9 9 9 9 9

text: Demonstrate 10 C- levels of occulting 63 through each channel of the system

text: JA R-FS

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7 FSTD H. A B C D 1 2 3 I II III MCC 3. System geometry 5° even angular Not Applicable 9 9 9 9 9 9 9 9 9 System geometry should be spacing within ± 1° as measured using a visual test 03 measured from either pattern filling the entire visual 0 ( c pilot eye-point, and scene (all channels) onti within 1·5° for adjacent consisting of a matrix of nued) squares. black and white 5° squares with light points at the intersections. The operator should demonstrate that the 2- angular spacing of any

text: C-

text: chosen 5° square and the

text: 4 relative spacing of adjacent squares are within the stated tolerances. The intent of this test is to demonstrate local linearity of the displayed image at either pilot eyepoint.

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( Surface contrast ratio should 4. Surface Contrast Not less than 5:1. 9 9 9 9 9 9 9 c be measured using a raster onti Ratio Demonstration model drawn test pattern filling the n entire visual scene (all u ed) channels). The test pattern should consist of black and white squares, no larger than 10 degrees and no smaller than 5º per square with a white square in the centre of each channel. Measurement C- should be made on the centre 65 bright square for each channel using a 1° spot photometer. This value should have a minimum brightness of 7 cd/m2 (2 foot-lamberts). Measure any adjacent dark squares. The contrast ratio is the bright square value divided by the dark square value.

text: Note. During contrast ratio testing, FSTD aft-cab and flight deck ambient light levels

text: should be zero.

text: JA R-FS

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: 5. Highlight Brightness Not less than 20 cd/m2 Not Applicable 9 9 Highlight brightness should (6 foot-Lamberts) from be measured by maintaining 03 the display measured the full test pattern described 0 ( c at the design eye point in paragraph 5.b 3 above, onti superimposing a highlight on nued) the centre white square of each channel and measuring the brightness. Lightpoints are not acceptable. Use of 2- calligraphic capabilities to

text: C-

text: enhance raster brightness is

text: 6 acceptable.

text: Not less than 17 cd/m2 9 9 9 9 9 (5 foot-Lamberts) from the display measured at the design eye point

text: Not greater than 3 arc Vernier resolution should be 6. Vernier Resolution Not Applicable 9 9 9 9 9 9 9 demonstrated by a test of minutes objects shown to occupy the required visual angle in each visual display used on a scene from the pilot’s eye-point.

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( 7. Light point Size Not greater than 6 arc Not Applicable 9 9 9 Lightpoint size should be c onti minutes measured using a test pattern consisting of a n u ed) centrally located single row of lightpoints reduced in length until modulation is just discernible in each visual channel.

text: A row of 40 lights in the case C- of 6 arc minutes (30 lights in 67 the case of 8 arc minutes) will form a 4° angle or less. Not greater than 8 arc Not Applicable 9 9 9 9 minutes Demonstration model

text: 8. Light point Contrast Not less than 25:1 Not applicable 9 9 9 Lightpoint contrast ratio Ratio should be measured using a test pattern demonstrating a Not less than 5:1 9 9 9 9 1º area filled with lightpoints (i.e. lightpoint modulation just Demonstration model discernible) and should be JA compared to the adjacent R-FS background.

text: TD Note. During contrast ratio H testing, FSTD aft-cab and TS flight deck ambient light FS levels should be zero Bi 2

text: 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: 6 FSTD SYSTEMS

text: 03 a Visual, Motion and 0 ( Cockpit Instrument c onti Response nued)

text: (1) Transport Delay 200 milliseconds or 9 9 One test is required in each less after control axis (Pitch, Roll & Yaw) movement

text: C- 150 milliseconds or 9 9 9 9 9 9

text: 8 less after control movement

text: 100 milliseconds or 9 9 9 less after control movement

text: SE CTIO

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 This test should measure all 0 ( (1) Transport Delay c the delay encountered by a onti (continued) step signal migrating from n u the pilot’s control through the ed) control loading electronics and interfacing through all the simulation software modules in the correct order, using a handshaking protocol, finally through the normal output interfaces to

text: C-

text: the motion system (where

text: applicable), to the visual system and instrument displays. A recordable start time for the test should be provided by a pilot flight control input. The test mode should permit normal computation time to be consumed and should not alter the flow of information through the hardware/software system. The Transport Delay of the

text: JA

text: system is then the time

text: R-FS

text: between control input and the individual hardware

text: TD

text: (systems) responses.

text: H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC It need only be measured (1) Transport Delay once in each axis, being (continued) independent of flight 03 conditions. Visual change 0 ( may start before motion c onti response but motion nued) acceleration must occur before completion of visual scan of first video field that contains different information.

text: 2- C- 7 0

text: OR alternative test:

text: Latency

text: (2) Visual, motion 150 milliseconds or Climb, Cruise and 9 9 One test is required in each (where fitted), Instrument less after helicopter Descent axis (pitch, roll. and yaw) for System response to an response’ each of the flight conditions, abrupt pilot controller input, compared to compared to helicopter data.

text: helicopter response for a similar input. Visual change may start before motion response but motion acceleration must occur before completion of SE visual scan of first video field CTIO

text: that contains different information N

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( Latency (continued) 100 milliseconds or Climb, Cruise, Descent 9 9 9 The test to determine c onti less after helicopter and Hover (Hover FFS compliance should include response only) simultaneously recording the n u ed) output from the pilot's cyclic, collective and pedals, the output from an accelerometer attached to the motion system platform located at an acceptable location near the pilot's seats (where C- applicable), the output from 71 the visual system display (including visual system delays), and the output signal to the pilot's attitude indicator or an equivalent test approved by the Authority. The test results in a comparison of a recording of the simulator's response with actual helicopter data

text: b Sound

text: (1) Realistic engine and JA Not applicable 9 Statement of Compliance or rotor sounds R-FS demonstration of representative sounds

text: TD H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7 FSTD H. A B C D 1 2 3 I II III MCC 9 9 9 9 9 (2) Establish amplitude Not applicable On ground all engines 9 9 9 Test results should show a & frequency of flight deck on comparison of the amplitude 03 sounds & frequency content of the 0 ( and c sounds against data onti Hover recorded at the initial FSTD nued) qualification. and No reference data are Straight and Level required for initial FSTD 2- flight qualification.

text: C- 7

text: 2 (2) Establish amplitude All tests in this section & frequency of flight deck should be presented using sounds an unweighted 1/3-octave band format from band 17 to (continued) 42 (50 Hz to 16 kHz). A minimum 20 second average should be taken at the location corresponding to the Helicopter data set. The Helicopter and flight simulator results should be produced using comparable data analysis techniques.

text: SE

text: See ACJ No. 1 to JAR-FSTD

text: CTIO

text: H.030 para 2.4.5

text: N 2

text: 20 09 -11 -0 1

text: ACJ No

text: SE

text: 20 .1 CTI 09

text: to J

text: -11 O A N 2

text: 1 FSTD

text: FFS FTD FNPT H. A B C D 1 2 3 I II III MCC 03 0 ( (i) Ready for engine ± 5 dB per 1/3 octave Ground 9 Normal condition prior to c onti start band engine start. The APU should be on if appropriate. n u ed)

text: (ii) All engines at idle ± 5 dB per 1/3 octave Ground 9 Normal condition prior to lift-

text: band off.

text: a) rotor not turning (If applicable)

text: b) rotor turning

text: C-

text: 73 9

text: (iii) Hover ± 5 dB per 1/3 octave Hover

text: band

text: (iv) Climb ± 5 dB per 1/3 octave En-route climb 9 Medium altitude.

text: band

text: (v) Cruise ± 5 dB per 1/3 octave Cruise 9 Normal cruise configuration.

text: band

text: (vi) Final approach ± 5 dB per 1/3 octave Landing 9 Constant airspeed, gear

text: band down.

text: (3) Special Casess Not Applicable C Special cases identified as

text: JA

text: T particularly significant to the R-FS & pilot, important in training, or

text: unique to a specific

text: TD M

text: helicopter type or variant.

text: H TS FS Bi 2 0 la 0 ga 2 9 :8 7

text: JA Bi TS

text: R- ACJ No

text: la F FS ga 2 S 2 TD .1 009

text: H to

text: JAR- :8 FFS FTD FNPT 7

text: FSTD H. A B C D 1 2 3 I II III MCC

text: (4) Initial evaluation: not 9 Results of the background applicable. noise at initial qualification 03

text: should be included in the 0 ( Flight Simulator Recurrent evaluation: ± QTG document and c Background noise onti 3dB per 1/3 octave approved by the qualifying authority. The simulated nued) band compared to sound will be evaluated to initial evaluation ensure that the background noise does not interfere with training. Refer to ACJ No. 1 2- to JAR-FSTD H.030 para C- 2.4.5.6. The measurements

text: 7 are to be made with the 4 simulation running, the

text: sound muted and a dead cockpit.

text: (5) Frequency Initial evaluation: not 9 9 Only required if the results

text: Response applicable. are to be used during

text: recurrent evaluations Recurrent evaluation: according to ACJ No. 1 to cannot exceed ± 5 dB JAR-FSTD H.030 para on three consecutive 2.4.5.7. The results shall be bands when compared acknowledged by the to initial evaluation and authority at initial the average of the SE qualification. absolute differences CTIO

text: between initial and

text: recurrent evaluation N

text: results cannot exceed 2

text: 2 dB.

text: 20 09 -11 -0 1

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued)

text: 2.4 Information for Validation Tests, 2.4.1 Control dynamics 2.4.1.1 General The characteristics of an aircraft flight control system have a major effect on handling qualities. A significant consideration in pilot acceptability of an aircraft is the ‘feel’ provided through the flight controls. Considerable effort is expended on aircraft feel system design so that pilots will be comfortable and will consider the aircraft desirable to fly. In order for a FSTD to be representative, it too should present the pilot with the proper feel – that of the aircraft being simulated. Compliance with this requirement should be determined by comparing a recording of the control feel dynamics of the FSTD to actual aircraft measurements in the relevant configurations. a. Recordings such as free response to a pulse or step function are classically used to estimate the dynamic properties of electromechanical systems. In any case, the dynamic properties can only be estimated since the true inputs and responses are also only estimated. Therefore, it is imperative that the best possible data be collected since close matching of the FSTD control loading system to the helicopter systems is essential. The required dynamic control checks are indicated in paragraph 2.3–2b(1) to (3) of the table of FSTD validation tests. b. For initial and upgrade evaluations, it is required that control dynamics characteristics be measured at and recorded directly from the flight controls. This procedure is usually accomplished by measuring the free response of the controls using a step input or pulse input to excite the system. The procedure should be accomplished in relevant flight conditions and configurations. c. For helicopters with irreversible control systems, measurements may be obtained on the ground if proper pitot-static inputs (if applicable) are provided to represent airspeeds typical of those encountered in flight. Likewise, it may be shown that for some helicopters, hover, climb, cruise and autorotation may have like effects. Thus, one may suffice for another. If either or both considerations apply, engineering validation or helicopter manufacturer rationale should be submitted as justification for ground tests or for eliminating a configuration. For FSTDs requiring static and dynamic tests at the controls, special test fixtures will not be required during initial and upgrade evaluations if the MQTG shows both test fixture results and the results of an alternate approach, such as computer plots which were produced concurrently and show satisfactory agreement. Repeat of the alternate method during the initial evaluation would then satisfy this test requirement.

text: 2.4.1.2 Control dynamics evaluation. The dynamic properties of control systems are often stated in terms of frequency, damping, and a number of other classical measurements which can be found in texts on control systems. In order to establish a consistent means of validating test results for FSTD control loading, criteria are needed that will clearly define the interpretation of the measurements and the tolerances to be applied. Criteria are needed for underdamped, critically damped, and overdamped systems. In the case of an underdamped system with very light damping, the system may be quantified in terms of frequency and damping. In critically damped or overdamped systems, the frequency and damping are not readily measured from a response time history. Therefore, some other measurement should be used. Tests to verify that control feel dynamics represent the helicopter should show that the dynamic damping cycles (free response of the controls) match that of the helicopter within specified tolerances. The method of evaluating the response and the tolerance to be applied is described in the underdamped and critically damped cases are as follows: a. Underdamped Response. (i) Two measurements are required for the period, the time to first zero crossing (in case a rate limit is present) and the subsequent frequency of oscillation. It is necessary to measure cycles on an individual basis in case there are non-uniform periods in the response. Each period will be independently compared with the respective period of the helicopter control system and, consequently, will enjoy the full tolerance specified for that period.

text: 2009-11-01 2-C-75 JAR-FSTD H

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued) (ii) The damping tolerance should be applied to overshoots on an individual basis. Care should be taken when applying the tolerance to small overshoots since the significance of such overshoots becomes questionable. Only those overshoots larger than 5% of the total initial displacement should be considered. The residual band, labelled T(Ad) in Figure 1 is ± 5% of the initial displacement amplitude Ad from the steady state value of the oscillation. Only oscillations outside the residual band are considered significant. When comparing FSTD data to helicopter data, the process should begin by overlaying or aligning the FSTD and helicopter steady state values and then comparing amplitudes of oscillation peaks, the time of the first zero crossing, and individual periods of oscillation. The FSTD should show the same number of significant overshoots to within one when compared against the helicopter data. This procedure for evaluating the response is illustrated in Figure 1 below. b. Critically damped and overdamped response. Due to the nature of critically damped and overdamped responses (no overshoots), the time to reach 90% of the steady state (neutral point) value should be the same as the helicopter within ± 10%. Figure 2 illustrates the procedure. c. Special considerations. Control systems, which exhibit characteristics other than classical overdamped or underdamped responses should meet specified tolerances. In addition, special consideration should be given to ensure that significant trends are maintained. 2.4.1.3 Tolerances. The following table summarises the tolerances, T. See figures 1 and 2 for an illustration of the referenced measurements. T(P0) ± 10% of P0 T(P1) ± 20% of P1 T(P2) ± 30% of P2 T(Pn) ± 10(n+1)% of Pn T(An) ± 10% of A1 T(Ad) ± 5% of Ad = residual band Significant overshoots First overshoot and ± 1 subsequent overshoots

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD H 2-C-76 2009-11-01

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued)

text: T(A)

text: T(A) A1

text: P0 P1 P2

text: Figure 1: Underdamped step response

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-77 JAR-FSTD H

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued)

text: Ad 0.9Ad

text: T(P0) 0.1 Ad

text: P0 Displacement vs Time

text: cue Figure 2: Critically damped step response 2.4.1.4 Alternate method for control dynamics evaluation. An alternate means for validating control dynamics for aircraft with hydraulically powered flight controls and artificial feel systems is by the measurement of control force and rate of movement. For each axis of pitch, roll, and yaw, the control should be forced to its maximum extreme position for the following distinct rates. These tests should be conducted at typical flight and ground conditions. a. Static test – Slowly move the control such that approximately 100 seconds are required to achieve a full sweep. A full sweep is defined as movement of the controller from neutral to the stop, usually aft or right stop, then to the opposite stop, then to the neutral position. b. Slow dynamic test – Achieve a full sweep in approximately 10 seconds. c. Fast dynamic test – Achieve a full sweep in approximately 4 seconds. Note: Dynamic sweeps may be limited to forces not exceeding 44.5 daN (100 lbs). 2.4.1.5 Tolerances a. Static test, see paragraph 2.3 – 2.a(1), (2), and (3) of the table of flight simulator validation tests. b. Dynamic test – ± 0.9 daN (2 lbs) or ± 10% on dynamic increment above static test. The Authority is open to alternative means such as the one described above. Such alternatives should, however, be justified and appropriate to the application. For example, the method described here may not apply to all manufacturers’ systems and certainly not to aircraft with reversible control systems. Hence, each case should be considered on its own merit on an ad hoc basis. Should the Authority find that alternative methods do not result in satisfactory performance, then more conventionally accepted methods should be used. 2.4.2 Ground Effect 2.4.2.1 For a FSTD to be used for lift-off and touchdown it should faithfully reproduce the aerodynamic changes which occur in ground effect. The parameters chosen for FSTD validation should be indicative of these changes. The primary validation parameters for characteristics in Ground Effect are:

text: JAR-FSTD H 2-C-78 2009-11-01

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued)

text: a. Longitudinal, lateral, directional and collective control positions b. Torque required for hover c. Height d. Airspeed e. Pitch Attitude f. Roll Attitude A dedicated test should be provided which will validate the aerodynamic ground effect characteristics. The selection of the test method and procedures to validate ground effect is at the option of the organisation performing the flight tests; however, the flight test should be performed with enough duration near the ground to validate sufficiently the ground-effect model. 2.4.2.2 Acceptable tests for validation of ground effect include: a. Level fly-bys. The level fly-bys should be conducted at a minimum of three altitudes within the ground effect, including one at no more than 10% of the rotor diameter above the ground, one each at approximately 30% and 70% of the rotor diameter where height refers to main gear above the ground. In addition, one level-flight trim condition should be conducted out of ground effect, e.g. at 150% of rotor diameter. Level 2 / 3 FTD’s and II / III FNPT’s may use methods other than the level fly-by method. b. Shallow approach landing. The shallow approach landing should be performed at a glide slope of approximately one degree with negligible pilot activity until flare. If other methods are proposed, a rationale should be provided to conclude that the tests performed validate the ground-effect model. 2.4.3 Motion System 2.4.3.1 General Pilots use continuous information signals to regulate the state of the helicopter. In concert with the instruments and outside-world visual information, whole-body motion feedback is essential in assisting the pilot to control the helicopter’s dynamics, particularly in the presence of external disturbances. The motion system should therefore meet basic objective performance criteria, as well as being subjectively tuned at the pilot's seat position to represent the linear and angular accelerations of the helicopter during a prescribed minimum set of manoeuvres and conditions. Moreover, the response of the motion cueing system should be repeatable. 2.4.3.2 Motion System Checks. The intent of tests as described in the table of FSTD validation tests, paragraph 2.3 - 4.a, Motion Enveloppe, 4.b, Frequency Response Band, 4.c, Leg Balance and 4.d, Turn Around, is to demonstrate the performance of the motion system hardware, and to check the integrity of the motion set-up with regard to calibration and wear. These tests are independent of the motion cueing software and should be considered as robotic tests. 2.4.3.3 Motion Cue Repeatability Testing The motion syst em characteristics in the table of Validation Tests address bas ic system capability, but no t pilot cueing capability. Un til there is an ob jective pro cedure for determination of the motion cues nece ssa ry to support p ilot tasks and stimulate the pilot re sponse which occurs in an aircraft for the same tasks, motion sys tems will con tinue to be “tuned ” sub ject ive ly. Having tuned a motion sys tem, howeve r, it is important to demon strate obje ctively that the system continues to perform as o riginally qua lified. Any motion performance change fro m the initially qualified baseline can be measured objectively. An objective assessment of motion performance change will be accomplished at lea st annually using the follo wing testing procedure: a. The current performance of the motion system should be assessed by comparison with the initial recorded data.

text: 2009-11-01 2-C-79 JAR-FSTD H

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued)

text: b. The para meters to be recorded should be the motion sys tem drive algorithm acce leration command and the actual acceleration measured from the s imulator acce lerometers.

text: c. The test input s ignals shou ld be in serted at an appropriate point prior to the integrat ion in the equations of mot ion (see figure 3). d. The characterist ics of the test signal (see figure 4) should be set so that the acce leration command reaches 2/3 the motion s ystem acceleration envelope as defined in section 4 a) for the linear axes. For the angular axe s the velocity co mmand should reach 2/3 of the angular velocity envelope as def ined in section 4 a). The time T1 should be of suffic ient dura tion to ensure steady initial cond itions . NOTE: If the simulator weight or C.G. changes for any reason, (i.e. visual system change, or structural change) then the motion system baseline performance repeatability tests should be rerun and the new results used for future comparison.

text: Forces and Equations of Motion Drive Motion Moments Motion Algorithm Hardware

text: Linear Accelerations or Angular Velocities

text: T1 T2 T3 T4

text: Figure 4

text: 2.4.3.4 Motion vibrations

text: a. Presentation of results. The characteristic motion vibrations are a means to verify that the FSTD can reproduce the frequency content of the helicopter when flown in specific conditions. The test results should be presented as a Power Spectral Density (PSD) plot with frequencies on the horizontal axis and amplitude on the vertical axis. The helicopter data and FSTD data should be presented in the same format with the same scaling. The algorithms used for generating the FSTD data should be the same as those used for the helicopter data. If they are not the same then the algorithms used for the FSTD data should be proven to be sufficiently comparable. As a minimum the results along the dominant axes should be presented and a rationale for not presenting the other axes should be provided. b. Interpretation of results. The overall trend of the PSD plot should be considered while focusing on the dominant frequencies. Less emphasis should be placed on the differences at the high frequency and low amplitude portions of the PSD plot. During the analysis it should be considered that certain structural components of the FSTD have resonant frequencies that are filtered and thus may not appear in the PSD plot. If such filtering is required the notch filter bandwidth should be

text: JAR-FSTD H 2-C-80 2009-11-01

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued) limited to 1 Hz to ensure that the buffet feel is not adversely affected. In addition, a rationale should be provided to explain that the characteristic motion vibration is not being adversely affected by the filtering. The amplitude should match helicopter data as per the description below; however, if for subjective reasons the PSD plot was altered a rationale should be provided to justify the change. If the plot is on a logarithmic scale it may be difficult to interpret the amplitude of the buffet in terms of acceleration. A 1x10-3 grms2/Hz would describe a heavy buffet. On the other hand, a 1x10-6 grms2/Hz buffet is almost not perceivable; but may represent a buffet at low speed. The previous two examples could differ in magnitude by 1 000. On a PSD plot this represents three decades (one decade is a change in order of magnitude of 10; two decades is a change in order of magnitude of 100, etc.). 2.4.4 Visual System 2.4.4.1 Visual system

text: a. Contrast ratio (daylight systems). Should be demonstrated using a raster drawn test pattern filling the entire visual scene (three or more channels) consisting of a matrix of black and white squares no larger than 5 degrees per square with a white square in the centre of each channel. Measurement should be made on the centre bright square for each channel using a 1 degree spot photometer. Measure any adjacent dark squares. The contrast ratio is the bright square value divided by the dark square value. Lightpoint contrast ratio is measured when lightpoint modulation is just discernable compared to the adjacent background. See paragraph 2.3.5.b.(3) and paragraph 2.3.5.b.(7). b. Highlight brightness test (daylight systems). Should be demonstrated by maintaining the full test pattern described above, the superimposing a highlight on the centre white square of each channel and measure the brightness using the 1 degree spot photometer. Lightpoints are not acceptable. Use of calligraphic capabilities to enhance raster brightness is acceptable. See paragraph 2.3.5.b.(4).

text: c. Resolution (daylight systems) should be demonstrated by a test of objects shown to occupy a visual angle of not greater than the specified value in arc minutes in the visual scene from the pilot’s eyepoint. This should be confirmed by calculations in the statement of compliance. See paragraph 2.3.5.b.(5). d. Lightpoint size (daylight systems) –should be measured in a test pattern consisting of a single row of lightpoints reduced in length until modulation is just discernible. See paragraph2.3.5.b.(6).

text: e. Lightpoint size (twilight and night systems) – of sufficient resolution so as to enable achievement of visual feature recognition tests according to paragraph 2.3.5.b.(6). f. Field of View. A continuous field of view is a fundamental requirement. Any visual display solution would be considered as long as it fulfils this requirement. Deviations from the minimum required field of view would only be considered when associated with helicopter structural cockpit masking. Although the visual system has to meet the test requirements at the pilot's design eye reference point, the visual system should cater for nominal pilot(s) head movement in support of the training. 2.4.4.2 Visual ground segment a. Altitude and RVR for the assessment have been selected in order to produce a visual scene that can be readily assessed for accuracy (RVR calibration) and where spatial accuracy (centreline and G/S) of the simulated helicopter can be readily determined using approach/runway lighting and flight deck instruments.

text: b. The QTG should indicate the source of data, i.e. airport and runway used, ILS G/S antenna location (airport and helicopter), pilot eye reference point, flight deck cut-off angle, helicopter pitch attitude etc., used to make accurately visual ground segment (VGS) scene content calculations. c. Automatic positioning of the simulated helicopter on the ILS is encouraged. If such positioning is accomplished, diligent care should be taken to ensure the correct spatial position and helicopter attitude is achieved. Flying the approach manually or with an installed autopilot should also produce acceptable results. 2.4.5 Sound System

text: 2009-11-01 2-C-81 JAR-FSTD H

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued) ACJ No.1 to JAR-FSTD H.030 (continued)

text: 2.4.5.1 General. The total sound environment in the helicopter is very complex, and changes with atmospheric conditions, helicopter configuration, airspeed, altitude, power settings, etc. Thus, flight deck sounds are an important component of the flight deck operational environment and as such provide valuable information to the flight crew. These aural cues can either assist the crew, as an indication of an abnormal situation, or hinder the crew, as a distraction or nuisance. For effective training, the FSTD should provide flight deck sounds that are perceptible to the pilot during normal and abnormal operations, and that are comparable to those of the helicopter. Accordingly, the FSTD operator should carefully evaluate background noises in the location being considered. To demonstrate compliance with the sound requirements, the objective or validation tests in this paragraph have been selected to provide a representative sample of normal static conditions typical of those experienced by a pilot. 2.4.5.2 Alternate engine fits. For FSTDs with multiple engine configurations any condition listed in paragraph 2.3, the table of FSTD validation tests, that is identified by the helicopter manufacturer as significantly different, due to a change in engine model should be presented for evaluation as part of the QTG. 2.4.5.3 Data and Data Collection System a. Information provided to the FSTD manufacturer should contain calibration and frequency response data. b. The system used to perform the tests listed in para.2.3, within the table of FSTD validation tests, should comply with the following standards: (i) ANSI S1.11-1986 - Specification for octave, half octave and third octave band filter sets; (ii) IEC 1094-4 - 1995 - measurement microphones - type WS2 or better. 2.4.5.4 Headsets. If headsets are used during normal operation of the helicopter they should also be used during the FSTD evaluation. 2.4.5.5 Playback equipment. Recordings of the QTG conditions according to paragraph 2.3, table of FSTD validation tests, should be provided during initial evaluations. 2.4.5.6 Background noise a. Background noise is the noise in the FSTD, due to the FSTD's cooling and hydraulic systems, that is not associated with the helicopter, and the extraneous noise from other locations in the building. Background noise can seriously impact the correct simulation of helicopter sounds, so the goal should be to keep the background noise below the helicopter sounds. In some cases, the sound level of the simulation can be increased to compensate for the background noise. However, this approach is limited by the specified tolerances and by the subjective acceptability of the sound environment to the evaluation pilot. b. The acceptability of the background noise levels is dependent upon the normal sound levels in the helicopter being represented. Background noise levels that fall below the lines defined by the following points, may be acceptable (refer to figure 3):

text: (i) 70 dB @ 50 Hz; (ii) 55 dB @ 1 000 Hz; (iii) 30 dB @ 16 kHz. These limits are for unweighted 1/3 octave band sound levels. Meeting these limits for background noise does not ensure an acceptable FSTD. Helicopter sounds, which fall below this limit require careful review and may require lower limits on the background noise.

text: c. The background noise measurement may be rerun at the recurrent evaluation as stated in paragraph 2.4.5.8. The tolerances to be applied are that recurrent 1/3 octave band amplitudes cannot exceed ± 3 dB when compared to the initial results.

text: 2.4.5.7 Frequency response - Frequency response plots for each channel should be provided at initial evaluation. These plots may be rerun at the recurrent evaluation as per paragraph 2.4.5.8. The tolerances to be applied are as follows: a. recurrent 1/3 octave band amplitudes cannot exceed ± 5 dB for three consecutive bands when compared to initial results.

text: JAR-FSTD H 2-C-82 2009-11-01

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued) b. the average of the sum of the absolute differences between initial and recurrent results cannot exceed 2 dB (refer table 3). 2.4.5.8 Initial and recurrent evaluations. If recurrent frequency response and FSTD background noise results are within tolerance, respective to initial evaluation results, and the operator can prove that no software or hardware changes have occurred that will affect the helicopter cases, then it is not required to rerun those cases during recurrent evaluations. If helicopter cases are rerun during recurrent evaluations then the results may be compared against initial evaluation results rather than helicopter master data. 2.4.5.9 Validation testing. Deficiencies in helicopter recordings should be considered when applying the specified tolerances to ensure that the simulation is representative of the helicopter. Examples of typical deficiencies are: a. variation of data between tail numbers; b. frequency response of microphones; c. repeatability of the measurements; d. extraneous sounds during recordings.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-83 JAR-FSTD H

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued)

text: Fi

text: 80.0 70 dB @ 50 Hz 70.0

text: 60.0 55 dB @ 1 kHz 50.0

text: dB SP

text: L 40.0

text: 30.0 30 dB @ 16 kHz 20.0

text: 0.0 50 63 80 100 125 160 200 250 315 400 500 630 800 000 500 000 1000 1250 1600 2000 2500 3150 4000 5000 6300 8000 0 2 6 1 1 1

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD H 2-C-84 2009-11-01

text: SECTION 2

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued)

text: Table 3 - Example of recurrent frequency response test tolerance 3 Functions and Subjective Tests 3.1 Discussion 3.1.1 Accurate replication of helicopter systems functions will be checked at each flight crewmember position. This includes procedures using the operator’s approved manuals, helicopter manufacturers approved manuals and checklists. Handling qualities, performance, and FSTD systems operation will be subjectively assessed. In order to assure the functions tests are conducted in an efficient and timely manner, operators are encouraged to coordinate with the appropriate Authority responsible for the evaluation so that any skills, experience or expertise needed by the Authority in charge of the evaluation team are available. 3.1.2 The necessity of functions and subjective tests arises from the need to confirm that the simulation has produced a totally integrated and acceptable replication of the helicopter. Unlike the objective tests listed in paragraph 2 above, the subjective testing should cover those areas of the flight envelope which may reasonably be reached by a trainee, even though the FSTD has not been approved for training in that area. Thus it is prudent to examine, for example, the normal and abnormal FSTD performance to ensure that the simulation is representative even though it may not be a requirement for the level of qualification being sought. (Any such subjective assessment of the simulation should include reference to paragraph 2 and 3 above in which the minimum objective standards acceptable for that Qualification Level are defined. In this way it is possible to determine whether simulation is an absolute requirement or just one where an approximation, if provided, has to be checked to confirm that it does not contribute to negative training.)

text: 2009-11-01 2-C-85 JAR-FSTD H

text: Bilaga 2

text: ACJ No.1 to JAR-FSTD H.030 (continued)

text: 3.1.3 At the request of the Authority, the FSTD may be assessed for a special aspect of an operator’s training programme during the functions and subjective portion of an evaluation. Such an assessment may include a portion of a Line Oriented Flight Training (LOFT) scenario or special emphasis items in the operator’s training programme. Unless directly related to a requirement for the current Qualification Level, the results of such an evaluation would not affect the FSTD’s current status. 3.1.4 Functions tests will be run in a logical flight sequence at the same time as performance and handling assessments. This also permits real time FSTD running for 2 to 3 hours, without repositioning or flight or position freeze, thereby permitting proof of reliability. 3.2 Test requirements 3.2.1 The ground and flight tests and other checks required for qualification are listed in the table of functions and subjective tests. The table includes manoeuvres and procedures to assure that the FSTD functions and performs appropriately for use in pilot training, testing and checking in the manoeuvres and procedures normally required of a training, testing and checking programme. 3.2.2 Manoeuvres and procedures are included to address some features of advanced technology helicopters and innovative training programmes. 3.2.3 All systems functions will be assessed for normal and, where appropriate, alternate operations. Normal, abnormal, and emergency procedures associated with a flight phase will be assessed during the evaluation of manoeuvres or events within that flight phase. Systems are listed separately under ‘any flight phase’ to assure appropriate attention to systems checks. 3.2.4 When evaluating functions and subjective tests, the fidelity of simulation required for the highest level of qualification should be very close to the helicopter. However, for the lower levels of qualification the degree of fidelity may be reduced in accordance with the criteria contained in paragraph 2 above. 3.2.5 Evaluation of the lower orders of FSTD should be tailored only to the systems and flight conditions which have been simulated. Similarly, many tests will be applicable for automatic flight. Where automatic flight is not possible and pilot manual handling is required, the FSTD should be at least controllable to permit the conduct of the flight. 3.2.6 Any additional capability provided in excess of the minimum required standards for a particular Qualification Level should be assessed to ensure the absence of any negative impact on the intended training and testing manoeuvres.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD H 2-C-86 2009-11-01

text: A SEC

text: 20 C

text: J No

text: 09 T

text: -1 .1 to IO

text: 1-0 N J 2

text: 1 Functions and subjective tests A R-F

text: Notes

text: S T General: Motion and buffet cues will only be applicable to FSTD equipped with an appropriate motion system D H. (1) Limited to clear area profiles 0 3 0 (2) Limited to performance (conti

text: * Check for the absence of negative effects n u ed)

text: TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT

text: A B C D 1 2 3 I II III MCC

text: a PREPARATION FOR FLIGHT

text: C- Pre-Flight: Accomplish a functions check of all switches, indicators, systems and equipment 9 9 9 9 9 9 9 87 at crew members and instructors stations and determine that the flight deck design and functions are identical to that of the helicopter within the scope of simulation.

text: Pre-Flight: Accomplish a functions check of all switches, indicators, systems, and equipment 9 9 9 9 at all crew members’ and instructor’s stations and determine that the flight deck design and functions represents those of a helicopter

text: b SURFACE OPERATIONS

text: (1) Engine Start 9

text: (a) Normal Start 9 9 9 9 9 9 9 9 9 9

text: (b) Alternate start procedures 9 9 9 9 9 9 9

text: (c) Abnormal starts and shutdowns (hot start, hung start, fire, etc) 9 9 9 9 9 9 9 9 9 9 9

text: TS

text: (2) Rotor start/engagement and acceleration

text: F

text: (a) Rotor start/engagement and acceleration 9 9 9 9 9 9 9 9 9 9 9 S

text: 200 Bilaga 2 9:87

text: (b) Ground resonance (if applicable on type). 9 9 9 9

text: JAR

text: -FST

text: D H

text: JA ACJ No Bi TS R-FS la FS ga 2 2 .1 009

text: TD TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT to J H A B C D 1 2 3 I II III MCC :8 A R- 7 (3) Ground taxi (wheeled aircraft only) FSTD

text: (a) Power/cyclic input * 9 9 9 H. (b) Collective lever/cyclic friction * 9 9 9 03 0 ( (c) Ground handling * 9 9 9 c onti (d) Brake operation * 9 9 9 n u ed) (e) Tail-/nosewheel lock operation * 9 9 9

text: (f) Other * 9 9 9

text: c HOVER

text: 2- (1) Liftoff * 9 9 9

text: C-

text: 88 (2) Hover * 9 9 9 9 9 9 9 9

text: (3) Instrument response

text: (a) Engine instruments * 9 9 9 9 9 9 9 9

text: (b) Flight instruments * 9 9 9 9 9 9 9 9

text: (4) Hovering turns * * 9 9 9 9 9 9 9

text: (5) Hover power checks

text: (a) In ground effect (IGE) * 9 9 9 9 9 9 9 9

text: (b) Out of ground effect (OGE) * 9 9 9 9 9 9 9 9

text: (6) Anti-torque effect * 9 9 9 9 9 9 9 9

text: (7) Abnormal/emergency procedures: 2 (a) Engine failure(s) * 9 9 9 9 9 9 9 9

text: 0 0

text: 1 (b) Fuel governing system failure * 9 9 9 9 9 9 9 9

text: (c) Hydraulic system failure * 9 9 9 9 9 9 9 9

text: * 9 9 9 9 9 9 9 9 SECTI (d) Stability system failure (e) Directional control malfunctions * 9 9 9 9 9 9 9 9

text: ON

text: A SEC

text: 20 C

text: J No

text: 09 T

text: -1 .1 to IO

text: 1-0 N J 2

text: 1 TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT A R-F

text: A B C D 1 2 3 I II III MCC

text: S T (f) Other * 9 9 9 9 9 9 9 9 D H. (8) Crosswind/tailwind hover * 9 9 9 9 9 9 9 9 0 3 0 d AIR TAXI/TRANSIT (conti

text: (1) Forward * 9 9 9 9 9 9 9 9 n u (2) Sideways * 9 9 9 9 9 9 9 9 ed)

text: (3) Rearward * 9 9 9 9 9 9 9 9

text: e TAKE-OFF

text: (1) Cat. B or single engine helicopters

text: 2- C-

text: (a) Normal 9

text: (I) From hover * 9 9 9 9 9 9 9

text: (II) Crosswind/tailwind * 9 9 9 9 9 9 9 9

text: (III) MTOM * 9 9 9 9 9 9 9 9

text: (IV) Confined area * 9 9 9 9 9 9

text: (V) Slope * 9 9 9 9 9 9

text: (VI) Elevated heliport/helideck * 9 9 9 9 9 9

text: (VII) Vertical * 9 9 9 TS

text: F

text: (b) abnormal / emergency procedures S

text: 200 Bilaga 2

text: (I) Engine failure during take-off (If single engine, up to initiation of the flare) * 9 9 9 9 9 91 9 9

text: (II) Forced landing (If single engine, up to initiation of the flare) * 9 9 9 9 9 91 9 9

text: (2) Cat A operation for all certified profiles * 9 9 9 91 9 91 9 9

text: JAR

text: -FST

text: D H

text: TD TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT to J H A B C D 1 2 3 I II III MCC :8 A R- 7 Take-off with engine failure FSTD

text: (i) engine failure prior to TDP * 9 9 9 91 9 9 9 H. 03 (ii) engine failure at or after TDP 9 9 9 9 91 9 91 9 91 0 ( c onti F CLIMB n u ed) (1) Cat.B or single engine helicopters

text: (a) Clear area 9 9 9 9 9 9 9 9 9 9 9

text: 2- (b) Obstacle clearance 9 9 9 9 9 9 9 9 9

text: C-

text: 90 (c) Vertical * 9 9 9 9 9 9 9 9

text: (d) Engine failure 9 9 9 9 9 9 9 9 9

text: (2) Cat.A operation for all certified profiles

text: with engine failure up to 300m (1000ft) above the level of the heliport 9 9 9 9 9 9 9 9 9

text: G CRUISE

text: (1) Performance characteristics 9 9 9 9 9 9 9 9 9 9

text: (2) Flying qualities 9 9 9 9 9 9 9 9 9 9 9

text: 0 (3) Turns

text: 0 1

text: -11- (a) Turns at Rate 1 and 2 9 9 9 9 9 9 9 9 9 9

text: (b) Steep Turns 9 9 9 9 9 9 9 9 9 9 SECTI

text: ON

text: A SEC

text: 20 C

text: J No

text: 09 T

text: -1 .1 to IO

text: 1-0 N J 2

text: A B C D 1 2 3 I II III MCC

text: S T (4) Acceleration and decelerations 9 9 9 9 D H. 0 (5) High airspeed vibration cues 9 9 9 9 3 0 (conti (6) Abnormal/emergency procedures n (a) Engine fire 9 9 9 9 9 9 9 9 9 u ed)

text: (b) Engine failure 9 9 9 9 9 9 9 9 9

text: (c) Inflight engine shutdown and restart 9 9 9 9 9 9 9 9 9

text: 2- (d) Fuel governing system failures 9 9 9 9 9 9 9 9 9

text: C-

text: 91 (e) Hydraulic failure 9 9 9 9 9 9 9 9 9

text: (f) Stability system failure 9 9 9 9 9 9 9 9 9

text: (g) Directional control malfunction 9 9 9 9 9 9 9 9 9

text: (h) Rotor vibration cues 9 9 9 9

text: (I) Other 9 9 9 9 9 9

text: h DESCENT

text: (1) Normal 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 TS (2) Maximum rate 9 9

text: F S

text: (3) Autorotative (until flare initiation) 200

text: Bilaga 2

text: (a) Straight in * 9 9 9 9 9 9 9 9 9:87

text: (b) With turn * 9 9 9 9 9 9 9 9

text: JAR i VISUAL APPROACHES

text: -FST

text: D H

text: TD TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT to J H A B C D 1 2 3 I II III MCC :8 A R- 7 (1) Cat.B or single engine helicopters FSTD

text: (a) Approach H. 03 (i) Normal 9 9 9 9 9 9 9 9 9 0 ( c 9 9 9 9 9 9 9 9 9 onti (ii) Steep n u (iii) Shallow 9 9 9 9 9 9 9 9 9 ed)

text: (iv) Vertical 9 9 9 9 9 9 9 9 9

text: (b) Abnormal and emergency procedures:

text: C- (i) One engine inoperative 9 9 9 9 9 9 9 9 9

text: (ii) Fuel governing failure 9 9 9 9 9 9 9 9 9

text: (iii) Hydraulics failure 9 9 9 9 9 9 9 9 9

text: (iv) Stability system failure 9 9 9 9 9 9 9 9 9

text: (V) Directional control failure 9 9 9 9 9 9 9 9 9

text: (VI) Autorotation * 9 9 9 9 9 9 9 9

text: (VII) Other 9 9 9 9 9 9

text: (c) Balked landing

text: 2 (I) All engines operating 9 9 9 9 9 9 9 9 9

text: 0 0

text: 1 (II) One or more engines inoperative 9 9 9 9 9 9 9 9 9

text: 01 (2) Cat.A operation for all certified profiles

text: SECTI

text: (a) from 300m (1000ft) above the level of the heliport to or after LDP 9 9 9 9 9 9 9 9 9

text: ON

text: A SEC

text: 20 C

text: J No

text: 09 T

text: -1 .1 to IO

text: 1-0 N J 2

text: A B C D 1 2 3 I II III MCC

text: S T j INSTRUMENT APPROACHES D H.

text: 0 Only those instrument approach tests relevant to the simulated helicopter type or system(s) 3 0 (conti and MCC training should be selected from the following list.

text: n u ed)

text: (1) Non-precision

text: (a) All engines operating 9 9 9 9 9 9 9 9 9 9 9

text: (b) One or more engines inoperative 9 9 9 9 9 9 9 9 9 9 9

text: 2- C-

text: (c) Approach procedures:

text: (i) NDB 9 9 9 9 9 9 9 9 9 9 9

text: (ii) VOR/DME, RNAV 9 9 9 9 9 9 9 9 9 9 9

text: (iii) ARA (Airborne radar approach) 9 9 9 9 9 9 9 9 9 9 9

text: (iv) GPS 9 9 9 9 9 9 9 9 9 9 9

text: (v) Other 9 9 9 9 9 9 9 9 9 9 9

text: (d) Missed approach

text: (i) All engines operating 9 9 9 9 9 9 9 9 9 9 9

text: TS

text: F

text: (ii) One or more engines inoperative 9 9 9 9 9 9 9 9 9 9 9 S

text: 200 Bilaga 2

text: (iii) Auto-pilot failure 9 9 9 9 9 9 9 9 9 9 9

text: (2) Precision

text: JAR

text: -FST

text: D H

text: TD TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT to J H A B C D 1 2 3 I II III MCC :8 A R- 7 (b) One or more engines inoperative 9 9 9 9 9 9 9 9 9 9 9 FSTD

text: (c) Approach procedures: 9 9 9 9 9 9 9 9 9 9 9 H.

text: 03 (i) DGPS 9 9 9 9 9 9 9 9 9 9 9 0 (

text: c 9 9 9 9 9 9 9 9 9 9 9 onti (ii) ILS n u • Manual without Flight Director, ed)

text: • Manual with Flight Director

text: • Auto pilot coupled

text: • CAT I

text: • CAT II

text: C- 94

text: (iii) Other 9 9 9 9 9 9 9 9 9 9 9

text: (d) Missed approach

text: (ii) One or more engines inoperative 9 9 9 9 9 9 9 9 9 9 9

text: (iii) Auto pilot failure 9 9 9 9 9 9 9 9 9 9 9

text: k APPROACH TO LANDING AND TOUCHDOWN

text: (1) Cat B or single engine helicopters

text: (a) Normal approach

text: 2 0

text: 0 (i) To a hover * 9 9 9 91 9 91 9 9

text: 1 -11-

text: (ii) Elevated heliport/helideck 9 9 9 9 9 9

text: SECTI

text: (iii) Confined area * 9 9 9 9 9

text: ON

text: A SEC

text: 20 C

text: J No

text: 09 T

text: -1 .1 to IO

text: 1-0 N J 2

text: A B C D 1 2 3 I II III MCC

text: S T (iv) Crosswind/tailwind * 9 9 9 91 9 91 9 9 D H. * 9 9 9 91 9 91 9 9 0 (v) Other 3 0 (conti (b) Touchdown n (i) From a hover * 9 9 9 91 9 91 9 9 u ed)

text: (ii) Running * 9 9 9 91 9 91 9 9

text: (iii) Slope * * 9 9 9 9

text: 2- (c) Abnormal and emergency procedures during approach to landing and

text: C-

text: touchdown

text: (i) One engine inoperative 9 9 9 9 91 9 91 9 9

text: (ii) Fuel governing failure 9 9 9 9 91 9 91 9 9

text: (iii) Hydraulics failure 9 9 9 9 91 9 91 9 9

text: (iv) Stability system failure 9 9 9 9 91 9 91 9 9

text: (v) Directional control failure 9 9 9 9 91 9 91 9 9

text: (vi) Autorotation * 9 9 9 91 9 91 9 9

text: (vii) Other 9 9 9 9 91 9 91 9 9

text: TS

text: F

text: (2)Cat. A operation for all certified profiles S

text: 200 Bilaga 2

text: Landing with engine failure

text: (i) engine failure prior to or at LDP * 9 9 9 91 9 91 9 9

text: JAR

text: -FST

text: D H

text: JA ACJ No Bi TS R-FS la

text: FS ga 2 2

text: .1 009 TD TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT to J H A B C D 1 2 3 I II III MCC :8 A R- 7 (ii) engine failure at or after LDP * 9 9 9 91 9 91 9 9 FSTD

text: H.

text: 03 0 ( c onti

text: n u ed)

text: 2- C- 96

text: 2 0 0 1 -11-

text: SECTI

text: ON

text: A SEC

text: 20 C

text: J No

text: 09 T

text: -1 .1 to IO

text: 1-0 N J 2

text: 1 A

text: R-F

text: S A B C D 1 2 3 I II III MCC T D H.

text: l ANY FLIGHT PHASE

text: 0 3 . 0 (conti

text: (1) Helicopter and powerplant systems operation (As applicable) n u 9 9 9 9 9 9 9 9 9 9 ed) (a) Air conditioning

text: (b) Anti-icing/de-icing 9 9 9 9 9 9 9 9 9 9

text: (c) Auxiliary powerplant 9 9 9 9 9 9 9 9 9 9

text: 2- 9 9 9 9 9 9 9 9 9 9 (d) Communications

text: C- 97

text: (e) Electrical 9 9 9 9 9 9 9 9 9 9

text: (f) Lighting systems (internal and external) 9 9 9 9 9 9 9 9 9 9

text: (g) Fire and smoke detection and suppression 9 9 9 9 9 9 9 9 9 9

text: (h) Stabilizer 9 9 9 9 9 9 9 9 9 9

text: (i) Flight controls/antitorque systems 9 9 9 9 9 9 9 9 9 9

text: (j) Fuel and oil 9 9 9 9 9 9 9 9 9 9

text: (k) Hydraulic 9 9 9 9 9 9 9 9 9 9

text: TS

text: (l) Landing gear 9 9 9 9 9 9 9 9 9 9

text: F S

text: 9 9 9 9 9 9 9 9 9 9 200 (m) Power plant Bilaga 2

text: (n) Transmission systems 9 9 9 9 9 9 9 9 9 9

text: (o) Rotor systems 9 9 9 9 9 9 9 9 9 9

text: JAR

text: -FST

text: D H

text: TD TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT to J H A B C D 1 2 3 I II III MCC :8 A R- 7 (p) Flight control computers 9 9 9 9 9 9 9 9 9 9 FSTD

text: (q) Stability and control augmentation systems (SAS) 9 9 9 9 9 9 9 9 9 9 H.

text: 03 (r) Voice activated systems 9 9 9 9 9 9 9 9 9 9 0 (

text: c 9 9 9 9 9 9 9 9 9 9 onti (s) Other n u (2) Flight management and guidance systems (as applicable) ed)

text: (a) Airborne radar 9 9 9 9 9 9 9 9 9 9

text: (b) Automatic landing aids 9 9 9 9 9 9 9 9 9 9

text: C- (c) Autopilot 9 9 9 9 9 9 9 9 9 9

text: (d) Collision avoidance systems (GPWS, TCAS,…) 9 9 9 9 9 9 9 9 9 9

text: (e) Flight data displays 9 9 9 9 9 9 9 9 9 9

text: (f) Flight management computers 9 9 9 9 9 9 9 9 9 9

text: (g) Head-up displays 9 9 9 9 9 9 9 9 9 9

text: (h) Navigation system 9 9 9 9 9 9 9 9 9 9

text: (i) NVG 9 9 9 9 9 9 9 9 9 9

text: (j) Other 9 9 9 9 9 9 9 9 9 9

text: 2 (3) Airborne procedures

text: 0 0

text: 1 (a) Quickstop * * 9 9 9 9 9 9 9

text: 01 (b) Holding pattern 9 9 9 9 9 9 9 9 9 9

text: SECTI

text: ON

text: A SEC

text: 20 C

text: J No

text: 09 T

text: -1 .1 to IO

text: 1-0 N J 2

text: A B C D 1 2 3 I II III MCC

text: S T (c) Hazard avoidance (GPWS, TCAS, Weather radar, …) As applicable, except for * * 9 9 9 9 9 9 9 D H. Weather Radar required for MCC training in FNPT. 0 3 0 (conti (d) Retreating blade stall recovery (As applicable) * 9 9 9 9 9 9 9 9

text: (e) Rotor mast bumping (As applicable) 9 9 9 9 9 9 9 9 9 n u ed) (f) Vortex ring * 9 9 9 9 9 9 9 9

text: m ENGINE SHUTDOWN AND PARKING

text: (1) Engine and systems operation 9 9 9 9 9 9 9 9 9 9 9

text: 2- C-

text: (2) Parking brake operation 9 9 9 9 9 9 9 9 9 9

text: (3) Rotor brake operation 9 9 9 9 9 9 9 9 9 9

text: (4) Abnormal and emergency procedures 9 9 9 9 9 9 9 9 9 9

text: (5) Other 9 9 9 9 9 9 9 9 9 9

text: n MOTION EFFECTS

text: (1) Runway rumble, oleo deflections, effects of groundspeed and uneven surface * 9 9 9

text: characteristics

text: (2) Buffet due to translational lift * 9 9 9

text: TS

text: (3) Buffet during extension and retraction of landing gear * 9 9 9 F

text: S 200 Bilaga 2

text: (4) Buffet due to high speed and retreating blade stall * 9 9 9

text: (5) Buffet due to vortex ring * 9 9 9

text: (6) Representative cues resulting from touchdown * 9 9 9

text: JAR

text: -FST

text: D H

text: TD TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT to J H A B C D 1 2 3 I II III MCC :8 A R- 7 (7) Rotor(s) vibrations (motion cues) 9 9 9 9 FSTD

text: (8) Translational lift * 9 9 9 H.

text: 03 (9) Loss of anti-torque device effectiveness * 9 9 9 0 (

text: c onti

text: o SOUND SYSTEM

text: n u ed) Significant helicopter noises should include:

text: (1) Engine, rotor and transmission to a comparable level found in the helicopter. 9 9 9 9 9 9 9 9 9 9 9

text: 2) Sounds of a crash should be related to a logical manner to landing in an unusual 9 9 9 9 9 9 9 9 9

text: -C- attitude or in excess of structural limitations of the helicopter.

text: 0 (3) Significant flight deck sounds and those which result from pilot’s actions. 9 9 9 9 9 9 9 9 9 9

text: p SPECIAL EFFECTS

text: (1) Effects of icing

text: (a) Airframe * * 9 9 92 92 92 92 92

text: (b) Rotors * * 9 9 92 92 92 92 92

text: (2) Effects of rotor contamination. 9 9

text: q VISUAL SYSTEM

text: (1) Accurate portrayal of environment relating to simulator attitudes and position. 9 9 9 9 9 9 9 9 9

text: 2 0 0

text: 1 (2) Heliports

text: SECTI

text: ON

text: A SEC

text: 20 C

text: J No

text: 09 T

text: -1 .1 to IO

text: 1-0 N J 2

text: A B C D 1 2 3 I II III MCC

text: S T (a)The distances at which heliport features are visible should not be less than those listed D H. below. Distances are measured from the FATO centre to a helicopter aligned with the 0 3 0 FATO approach direction on an extended 3-degree glideslope. (conti

text: (i) Heliport definition, strobe lights, approach lights from 8km 9 9 9 9 9 9 9 9 9 n u ed) (ii) Visual approach Aids and FATO/LOF edge lights should be visible 9 9 9 9 9 9 9 9 9

text: from 5km through approach angles up to 12 degrees

text: (iii) FATO/LOF edge lights and taxiway definition from 3km 9 9 9 9 9 9 9 9 9

text: 2- 9 9 9 9 9 9 9 9 9 (iv) FATO and TLOF markings within range of landing lights for night

text: C-

text: 1 scenes

text: 0 1

text: (v) FATO and TLOF markings as required by surface resolution on day 9 9 9 9 9 9 9 9 9

text: scenes

text: (b) At least three different heliport scenes which should be:

text: (i) an airport 9 9 9 9 9 9 9 9 9

text: (ii) a surface level confined area and 9 9 9 9 9 9

text: (iii) an elevated heliport 9 9 9 9 9 9

text: (c) Representative heliport scene content including the following:

text: TS

text: 9 9 9 9 9 9 9 9 9 F (i) Surfaces and markings on runways, heliport, taxiways and ramps S

text: 200 Bilaga 2

text: (ii) Lighting for the FATO/TLOF, visual approach aids and approach 9 9 9 9 9 9 9 9 9

text: lighting of appropriate colours

text: (iii) Heliport perimeter and taxiway lighting 9 9 9 9 9 9 9 9 9

text: J A R- F S TD

text: H

text: TD TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT to J H A B C D 1 2 3 I II III MCC :8 A R- 7 (iv) Ramps and terminal buildings and vertical objects which correspond to 9 9 9 9 9 9 9 9 9 FSTD

text: the operational requirements of an operator’s LOFT scenario. H. (v) The directionality of strobe lights, approach lights, runway edge lights, 9 9 9 9 9 9 9 9 9 03 0 ( visual landing aids, runway centre line lights, threshold lights, and touchdown zone c onti

text: lights on the runway of intended landing should be realistically replicated n u ed) (3) Representative visual effect of helicopter external lighting in reduced visibility, such as 9 9 9 9 9 9 9 9

text: reflected glare, to include landing lights, strobes, and beacons

text: 2 (4) Instructor controls of the following:

text: -C-

text: 10 (a) Cloud base/cloud tops; 9 9 9 9 9 9 9 9 9

text: (b) Visibility in kilometres/nautical miles and RVR in meters/feet; 9 9 9 9 9 9 9 9 9

text: (c) Airport/heliport selection; 9 9 9 9 9 9 9 9 9

text: (d) Airport/heliport lighting; 9 9 9 9 9 9 9 9 9

text: (e) ground and flight traffic. 9 9 9 9 9

text: (5) Visual system compatibility with aerodynamic programming 9 9 9 9 9 9 9 9 9

text: (6) Visual cues to assess sink rate displacements, rates and height AGL during landings * 9 9 9 9 9 9 9 9

text: (e.g. runways/heliports, taxiways, ramps and terrain features).

text: 2 (7) visual scene capability.

text: 0 0

text: 1 (a) Twilight and night 9 9

text: 01 (b) Twilight, night and day 9 9 9 9 9 9 9

text: SECTI

text: ON

text: A SEC

text: 20 C

text: J No

text: 09 T

text: -1 .1 to IO

text: 1-0 N J 2

text: A B C D 1 2 3 I II III MCC

text: S T (8) General terrain characteristics. * 9 9 9 9 9 9 9 D H.

text: 0 Below 5000ft present realistic visual scene permitting navigation by sole reference to visual 3 0 (conti landmarks. Terrain contouring should be suitably represented.

text: (9) At and below 610m (2000ft) height above the airport/heliport and within a radius of 16 n u ed) kilometres (9NM) from the airport/heliport, weather representations, including the following;

text: (a) Variable cloud density 9 9

text: (b) Partial obscuration of ground scenes; the effect of a scattered to broken cloud 9 9 9 9 9 9

text: deck

text: C- 1

text: 0 (c) Visual cues of speed through clouds 9

text: (d) Gradual break out 9 9 9 9 9 9

text: (e) Visibility and RVR measured in terms of distance. 9 9 9 9 9 9 9 9 9

text: (f) Patchy fog 9 9

text: (g) The effect of fog on airport/heliport lighting. 9 9 9 9 9 9

text: (10) A capability to present ground and air hazards such as another aircraft crossing the 9 9 9

text: active runway and converging airborne traffic

text: (11) Operational visual scenes which provide a cue rich environment sufficient for precise 9 9 9 9 9 9 TS

text: F

text: low airspeed and low altitude manoeuvring and landing. S

text: 200 Bilaga 2

text: (12) Operational visual scenes which portray representative physical relationships known to 9

text: cause landing illusions such as short runways, landing approaches over water, uphill, downhill

text: and sloping landing areas, rising terrain on the approach path, and unique topographic

text: J features.

text: A R- F S TD

text: H

text: TD TABLE OF FUNCTIONS AND SUBJECTIVE TESTS FFS FTD FNPT to J H A B C D 1 2 3 I II III MCC :8 A R- 7 Note - Illusions may be demonstrated at a generic airport or specific aerodrome. FSTD

text: (13) Special weather representations of light, medium, heavy precipitation and lighting near 9 H.

text: a thunderstorm on takeoff, approach and landing at and below an altitude of 610m (2000 03 0 ( feet) above the airport/heliport surface and within a radius of 16 kilometres (9 NM) from the c onti airport/heliport. n u ed) (14) Wet and snow-covered landing areas including runway/heliport lighting reflections for 9

text: wet, partially obscured lights for snow or suitable alternative effects.

text: (15) The effects of swell and wind on a 3 dimensional ocean model should be simulated. 9

text: -C- (16) The effects of own helicopter downwash upon various surfaces such as snow, sand, 9

text: 4 dirt and grass should be simulated including associated effects of reduced visibility.

text: (17) Realistic colour and directionality of airport/heliport lighting. 9 9 9 9 9 9 9 9 9

text: (18) The visual scene should correlate with integrated helicopter systems, where fitted (e.g. 9 9 9 9 9

text: terrain, traffic and weather avoidance systems and Head-up Guidance System (HGS)) (For

text: FTD and FNPT may be restricted to specific geographical areas.) Weather radar

text: presentations in helicopters where radar information is presented on the pilot’s navigation

text: instruments. Radar returns should correlate to the visual scene.

text: (19) Dynamic visual representation of rotor tip path plane including effects of rotor start up 9 9

text: and shut down as well as orientation of the rotor disc due to pilot control input.

text: 2 9 9 9 9 0 (20) To support LOFT, the visual system should provide smooth transition to new

text: 0 1

text: operational scenes without flight through clouds.

text: 01 (21) The visual system should provide appropriate height and 3-D object collision detection 9 9 9 9 9 9 9

text: SECTI

text: feedback to support training.

text: ON

text: A SEC

text: 20 C

text: J No

text: 09 T

text: -1 .1 to IO

text: 1-0 N J 2

text: A B C D 1 2 3 I II III MCC

text: S T (22) Scene quality D H.

text: 9 9 9 9 9 9 9 9 9 0 (a) surfaces and textural cues should be free from distracting quantization (aliasing) 3 0 (conti (b) the system light points should be free from distracting jitter, smearing or 9 9

text: streaking n u ed) (c) system capable of six discrete light step controls (0-5) 9 9 9 9 9 9 9 9 9

text: Notes

text: General: Motion and buffet cues will only be applicable to FSTD equipped with an appropriate motion system

text: C- (1) Limited to clear area profiles

text: 0 (2) Limited to performance

text: * Check for the absence of negative effects

text: TS

text: F S 200 Bilaga 2 9:87

text: J A R- F S TD

text: H

text: Bilaga 2

text: Appendix 1 to ACJ No. 1 to JAR-FSTD H.030 (interpretative material) Validation Test Tolerances

text: Background 1.1 The tolerances listed in ACJ No. 1 of JAR-FSTD H.030 are designed to be a measure of quality of match using flight-test data as a reference. 1.2 There are many reasons, however, why a particular test may not fully comply with the prescribed tolerances: a. Flight-test is subject to many sources of potential error, e.g. instrumentation errors and atmospheric disturbance during data collection; b. Data that exhibit rapid variation or noise may also be difficult to match; c. Engineering simulator data and other calculated data may exhibit errors due to a variety of potential differences discussed below. 1.3 When applying tolerances to any test, good engineering judgement should be applied. Where a test clearly falls outside the prescribed tolerance(s) for no apparent reasons, then it should be judged to have failed. 1.4 The use of non-flight-test data as reference data was in the past quite small, and thus these tolerances were used for all tests. The inclusion of this type of data as a validation source has rapidly expanded, and will probably continue to expand. 1.5 When engineering simulator data are used, the basis for their use is that the reference data are produced using the same simulation models as used in the equivalent flight training simulator; i.e., the two sets of results should be ‘essentially’ similar. The use of flight-test based tolerances may undermine the basis for using engineering simulator data, because an essential match is needed to demonstrate proper implementation of the data package. 1.6 There are, of course, reasons why the results from the two sources can be expected to differ: a. Hardware (avionics units and flight controls); b. Iteration rates; c. Execution order; d. Integration methods; e. Processor architecture; f. Digital drift: (i) Interpolation methods; (ii) Data handling differences; (iii) Auto-test trim tolerances, etc. 1.7 Any differences should, however, be small and the reasons for any differences, other than those listed above, should be clearly explained. 1.8 Historically, engineering simulation data were used only to demonstrate compliance with certain extra modelling features: a. Flight test data could not reasonably be made available; b. Data from engineering simulations made up only a small portion of the overall validation data set; c. Key areas were validated against flight-test data. 1.9 The current rapid increase in the use and projected use of engineering simulation data is an important issue because: a. Flight-test data are often not available due to sound technical reasons; b. Alternative technical solutions are being advanced; c. Cost is an ever-present issue.

text: JAR-FSTD H 2-C-106 2009-11-01

text: Bilaga 2

text: Appendix 1 to ACJ No. 1 to JAR-FSTD H.030 (continued) 1.10 Guidelines are therefore needed for the application of tolerances to engineering-simulatorgenerated validation data. 2. Non-Flight-Test Tolerances 2.1 Where engineering simulator data or other non-flight-test data are used as an allowable form of reference validation data for the objective tests listed in the table of validation tests, the match obtained between the reference data and the FSTD results should be very close. It is not possible to define a precise set of tolerances as the reasons for other than an exact match will vary depending upon a number of factors discussed in paragraph one of this appendix. 2.2 As guidance, unless a rationale justifies a significant variation between the reference data and the FSTD results, 20% of the corresponding ‘flight-test’ tolerances would be appropriate. 2.3 For this guideline (20% of flight-test tolerances) to be applicable, the data provider should supply a well-documented mathematical model and testing procedure that enables an exact replication of their engineering simulation results.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-107 JAR-FSTD H

text: Bilaga 2

text: Appendix 2 to ACJ No.1 to JAR-FSTD H.030 Validation Data Roadmap

text: 1. General 1.1 Helicopter manufacturers or other sources of data should supply a validation data roadmap (VDR) document as part of the data package. A VDR document contains guidance material from the helicopter validation data supplier recommending the best possible sources of data to be used as validation data in the QTG. A VDR is of special value in the cases of requests for ‘interim’ qualification, and for qualification of alternate engine or avionics fits. A VDR should be submitted to the authority as early as possible in the planning stages for any FSTD planned for qualification to the standards contained herein. The respective State civil aviation authority is the final authority to approve the data to be used as validation material for the QTG. The United States Federal Aviation Administration’s National Simulator Program Manager and the Joint Aviation Authorities’ FSTD Steering Group have committed to maintain a list of agreed VDR’s.

text: 1.2 The validation data roadmap should clearly identify (in matrix format) sources of data for all required tests. It should also provide guidance regarding the validity of these data for a specific engine type and thrust rating configuration and the revision levels of all avionics affecting helicopter handling qualities and performance. The document should include rationale or explanation in cases where data or parameters are missing, engineering simulation data are to be used, flight test methods require explanation, etc., together with a brief narrative describing the cause/effect of any deviation from data requirements. Additionally, the document should make reference to other appropriate sources of validation data (e.g., sound and vibration data documents). 1.3 Table 1, below, depicts a generic roadmap matrix identifying sources of validation data for an abbreviated list of tests. A complete matrix should address all test conditions. 1.4 Additionally, two examples of ‘rationale pages’ are presented in Appendix F of the IATA Flight Simulator Design & Performance Data Requirements document. These illustrate the type of aircraft and avionics configuration information and descriptive engineering rationale used to describe data anomalies, provide alternative data, or provide an acceptable basis to the authority for obtaining deviations from QTG validation requirements.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD H 2-C-108 2009-11-01

text: Bilaga 2

text: Appendix 2 to ACJ No. 1 to JAR-FSTD H.030 (continued)

text: . ry

text: essa c e n

text: be ay

text: m s

text: mn lu

text: co re o ] m a a

text: dat n Dat n io tio

text: datli a Valida v

text: as d le 1 e b

text: a

text: us T re a e) lin e s

text: tion. ba d n ondi a c e t iv at tes riv ch a de ., r e .g o f (e d e b type scri ft e ra d c ir a ll be e n o sha n a h t mode re A o

text: 1 CC 2 If m * *

text: 2009-11-01 2-C-109 JAR-FSTD H

text: Bilaga 2

text: Appendix 3 to ACJ No. 1 to JAR-FSTD H.030, para 2.1 Rotor Aerodynamic Modelling Techniques

text: 1. Introduction

text: Several modelling choices are available to simulate rotor blade aerodynamics. These include rotor disks, rotor maps, and blade element rotor models. Cost, simulation fidelity, and training requirements are three factors that may determine the appropriate model to use.

text: 2. Disk models

text: 2.1 Rotor disk models typically approximate blade flapping by the first few terms of a Fourier series. The lift curve is assumed to be a linear function of angle of attack and inflow is usually assumed to be uniform over the entire disk. With these assumptions the forces and moments produced by the blades over the course of one complete revolution can be written analytically. Blade azimuthal position can then be ignored by the rest of the helicopter aerodynamic model which sees normalized forces as generated by a thrust producing disk. Disk models are usually easy to implement and tune, and require minimal computer resources to run. Disk models are best at matching static performance characteristics, and weakest in matching dynamic handling qualities and flight at extremes of the flight envelope where some of the underlying assumptions cease to be true. The risk is that these models may require an unmanageable accumulation of add-ons to simulate all the helicopter effects that do not flow naturally out of the model such as blade stall, dynamic stall, reverse flow, and cross coupling effects. For certain helicopter types, and for many tail rotors, some of these effects will be negligible or occur outside of the civil flight envelope and thus not impact the training requirements of the FSTD. Adding the effects of sharp wind gradients over the rotor disk, that may occur in confined areas or in pinnacle training is problematic as the formulation assumes constant wind speed over the disk.

text: Figure 1 3. Rotor map models

text: 3.1 Rotor map models, or coefficient models, are also not computationally demanding. In this method a database of coefficients or stability and control derivatives is used to compute aircraft forces and moments. The simulation will interpolate its performance from the nearest points in the database. This data base can be generated from flight test data analysis or from an off-line blade element model. Steady state performance can in theory, be easily tuned by simply adjusting data points in the database. However if the database is generated from an off-line model blade element model then considerable effort could be spent tuning the off-line model that is one step removed from the simulation. The net result is a saving in real time execution, but development costs may be as high as a full blade element model. The blade element model that generates the database, since it runs off-line, is not limited by real time constraints and thus can be considerably more complex than real time blade element models. FSTD fidelity may be limited by the overall size and coarseness of the database. Not every flight possibility will be covered by the database and separate databases may need to be generated to simulate failure modes. As with the rotor disk model the incorporation of known air flows into the simulation at the blade elements is problematic and could effect for example, the realism of simulated turbulence, and the effectiveness of confined area landing training where the winds have large gradients such that they will not be constant over the entire rotor disk.

text: JAR-FSTD H 2-C-110 2009-11-01

text: Bilaga 2

text: Appendix 3 to ACJ No. 1 to JAR-FSTD H.030, para 2.1 (continued)

text: CN

text: CY

text: CM

text: 90266F21.RT Figure 2 4 Blade Element Rotor Models

text: 4.1 A blade element rotor model, has at its core a division of the blade into discrete segments. Rotor speed and radial station as well as local winds at each segment are used to compute local angle of attack, sideslip and Mach number. Using the airfoil characteristics of airfoil at the blade segment aerodynamic forces are computed. Once all the forces and moments for all segments have been computed the equations of motion of each blade are solved. Real time constraints may limit the number of segments, and the degrees of freedom/flexibility of the blades and the complexity of the inflow model. A real time blade element model , and its associated inflow model is significantly more complex than a rotor disk, but offers a more rigorous simulation of a helicopter rotor blade dynamics. Blade motions even at very low rotor speeds are computed in the same manner, thus offering fidelity simulation of helicopter operations from rotor stopped, through start-up, to the full flight envelope including malfunctions and the effects of sharp wind gradients across the blade elements that occur in confined areas or in pinnacle training. The model can be used to provide helicopter vibrations amplitudes and trends.

text: L5 L4 WIND DIRECTION L3 L2 D5 D4 L1 D3 LB D2

text: e D1

text: Ω h DB 90272F23.RT

text: Figure 3

text: 5. Conclusions 5.1 The modelling choice alone, cannot ensure fidelity. The best guarantor of accurate simulation training remains validation with flight test data. A blade element rotor model reduces risk to simulation training by giving a more comprehensive rotor simulation, but comes at a price of increased complexity and computer resource requirements. This may be warranted where the training objectives of the simulation require a very high level of fidelity.

text: 2009-11-01 2-C-111 JAR-FSTD H

text: Bilaga 2

text: Appendix 4 to ACJ No. 1 to JAR-FSTD H.030 PARA 2.2 Vibration Platforms for Helicopter FSTDs

text: 1 The role of vibrations in pilot cueing 1.1 Motion feedback in rotary wing aircraft has a wide bandwidth of frequencies and amplitudes consisting of cues ranging from large sustained accelerations up to high frequency vibrations generated by the rotor harmonics. Vibrations on helicopters, in addition to creating a harsh operating environment, provide pilots with rotor dynamic feedback critical to his/her ability to control the aircraft. Normal and abnormal flying conditions are therefore sensed by the pilots through the vibration levels/amplitudes and are integral to helicopter flying. Rotor malfunctions/conditions such as icing or damage are rapidly identified subjectively by sensing the increased vibration levels and change in characteristics. 1.2 The FSTD training environment should subject the pilot to high fidelity and realistic levels of vibration in order to enhance the transfer of training. Vibrations, when accurately simulated and harmonized with visual and sound system cues, ensure that the pilot develops proper control strategies while experiencing representative workloads. 1.3 Three characteristics of the vibrations must be accurately reproduced to create an authentic flying environment and stimulate pilots with representative aircraft vibrations: the trends, the axes and the levels of vibrations. For example, the vibration trends will inform the pilot that the helicopter has entered a transition stage between hover and low speed level flight. Helicopter vibrations are multidimensional, that is, they are perceived as occurring in more than one degree of freedom at a time. Simulating combinations of X, Y and Z vibrations has demonstrated to be significant for pilot training. Accurate reproduction of vibration levels provides subjective information on the stresses that certain manoeuvres exert on the helicopter. 2 Limitations of using a 6 Degree-of-Freedom motion system to reproduce vibrations 2.1 The simulation of vibration cues for rotary wing aircraft as produced by a conventional six-degreeof-freedom (6-DOF) motion system is limited. While most motion systems are capable of reproducing vibrations, the dynamic range of helicopter vibration amplitudes and frequencies (3 Hz to 50 Hz, typically) exceed the limited bandwidth capability of synergistic motion systems (typically 0 Hz to 10 Hz in the vertical axis and lower in the longitudinal and lateral axes). 2.2 Moreover, the application of representative vibrations to the entire simulator structure may adversely impact the life span of some simulator components such as the visual system.

text: 3 Advantages of a dedicated 3 Degree-of-Freedom vibration platform 3.1 To augment the performance of a 6 DOF motion system and achieve accurate reproduction of vibrations while minimizing stresses on the simulator structure, it is proposed that the motion cueing frequency bandwidth be separated in two. Dedicated cueing devices would then be assigned to reproduce each specific frequency range. The lower frequency range is used to drive the motion system and the higher frequency range, with the majority of the vibration information, is used to drive the vibration platform.

text: 3.2 Two solutions may be used for simulating the vibrations: a. A vibration platform consisting of a 3 degree of freedom system tailored for vibrations and installed under the cockpit as illustrated in figure 1. This system combines high bandwidth, independent driving axes (to avoid crosstalk) and high stiffness. b. A vibration platform consisting of a 3 degree of freedom system to make the seats, the controls and the main instrument board vibrate independently from the cockpit. This solution decreases the moving mass relatively to the payload and therefore minimizes the risk of resonance.

text: JAR-FSTD H 2-C-112 2009-11-01

text: Bilaga 2

text: Appendix 4 to ACJ No. 1 to JAR-FSTD H.030 para 2.2 (continued) VIBRATING COCKPIT Figure 1: An Example of a three degree of freedom cockpit vibration system INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-113 JAR-FSTD H

text: Bilaga 2

text: Appendix 5 To ACJ No.1 To JAR-FSTD H.030 Transport Delay Testing Method

text: 1 General 1.1 The purpose of this appendix is to demonstrate how to determine the introduced transport delay through the FSTD system such that it does not exceed a specific time delay. That is, measure the transport delay from control inputs through the interface, through each of the host computer modules and back through the interface to motion, flight instrument and visual systems, and show that it is no more than the tolerances required in the validation test tables. 1.2 Four specific examples of transport delay are described as follows: a. simulation of classic non-computer controlled aircraft; b. simulation of computer controlled aircraft using real aircraft equipment;

text: c. simulation of computer controlled aircraft using software emulation of aircraft equipment; d. simulation using software avionics or re-hosted instruments. 1.3 Figure 1 illustrates the total transport delay for a non-computer-controlled aircraft, or the classic transport delay test. 1.4 Since there are no aircraft-induced delays for this case, the total transport delay is equivalent to the introduced delay.

text: 1.7 Introduced transport delay is measured from the cockpit control input to the reaction of the instruments, and motion and visual systems (See figure 1). 1.8 Alternatively, the control input may be introduced after the aircraft controller system and the introduced transport delay measured directly from the control input to the reaction of the instruments, and FSTD motion and visual systems (See figure 2). 1.9 Figure 3 illustrates the transport delay testing method employed on a FSTD that uses a software emulated aircraft controller system. 1.10 By using the simulated aircraft controller system architecture for the pitch, roll and yaw axes, it is not possible to measure simply the introduced transport delay. Therefore, the signal should be measured directly from the pilot controller. Since in the real aircraft the controller system has an inherent delay as provided by the aircraft manufacturer, the FSTD manufacturer should measure the total transport delay and subtract the inherent delay of the actual aircraft components and ensure that the introduced delay does not exceed the tolerances required in the validation test tables. 1.11 Special measurements for instrument signals for FSTDs using a real aircraft instrument display system, versus a simulated or re-hosted display. For the case of the flight instrument systems, the total transport delay should be measured, and the inherent delay of the actual aircraft components subtracted to ensure that the introduced delay does not exceed the tolerances required in the validation test tables.

text: 1.11.1 Figure 4A illustrates the transport delay procedure without the simulation of aircraft displays. The introduced delay consists of the delay between the control movement and the instrument change on the data bus. 1.11.2 Figure 4B illustrates the modified testing method required to correctly measure introduced delay due to software avionics or re-hosted instruments. The total simulated instrument transport delay is measured and the aircraft delay should be subtracted from this total. This difference represents the introduced delay and shall not exceed the tolerances required in the validation test tables. The

text: JAR-FSTD H 2-C-114 2009-11-01

text: Bilaga 2

text: Appendix 5 to ACJ No. 1 to JAR-FSTD H.030 (continued)

text: inherent delay of the aircraft between the data bus and the displays is indicated as XX msec (See figure 4A). The display manufacturer shall provide this delay time.

text: 1.12 Recorded signals. The signals recorded to conduct the transport delay calculations should be explained on a schematic block diagram. The FSTD manufacturer should also provide an explanation of why each signal was selected and how they relate to the above descriptions.

text: 1.13 Interpretation of results. It is normal that FSTD results vary over time from test to test. This can easily be explained by a simple factor called ‘sampling uncertainty.’ All FSTDs run at a specific rate where all modules are executed sequentially in the host computer. The flight controls input can occur at any time in the iteration, but these data will not be processed before the start of the new iteration. For a FSTD running at 60 Hz a worst-case difference of 16·67 msec can be expected. Moreover, in some conditions, the host FSTD and the visual system do not run at the same iteration rate, therefore the output of the host computer to the visual will not always be synchronised.

text: 1.14 The transport delay test should account for the worst-case mode of operation of the visual system. The tolerance is as required in the validation test tables and motion response shall occur before the end of the first video scan containing new information.

text: y Instruments

text: HOST reaction Flight Simulator

text: reaction

text: reaction

text: Simulator introduced transport delay

text: Total simulator transport delay

text: HOST

text: Simulator y Instruments

text: Flight Aircraft flight reaction controls controller Instruments

text: control y Motion reaction

text: input system Motion

text: interface y Visual reaction

text: Visual

text: Total simulator transport delay

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-115 JAR-FSTD H

text: Bilaga 2

text: y Instruments

text: control controller reaction

text: reaction

text: Total simulator transport delay

text: Figure 3: Transport Delay for simulation of computer controlled aircraft using software emulation of aircraft

text: equipment

text: A: FSTD using real aircraft instruments

text: Aircraft hardware

text: Flight control cabinet Host computer Data bus Control, Flight controls Flight, EFIS symbol signal Interface generator Display unit Instruments, Software

text: Delay < req’d value Aircraft delay = XX msec

text: Aircraft hardware

text: Flight control cabinet Host computer

text: Control, Software avionics Flight controls Flight, or signal Instruments, Interface Display unit Re-hosted Software instrument

text: Figure 4A and 4B: Transport delay for simulation of aircraft using real or re-hosted instrument drivers

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD H 2-C-116 2009-11-01

text: Bilaga 2

text: Appendix 6 to ACJ No.1 to JAR-FSTD H.030 Recurrent Evaluations - Validation Test Data Presentation

text: 1. Background 1.1 During the initial evaluation of a FSTD the MQTG is created. This is the master document, as amended, to which FSTD recurrent evaluation test results are compared. 1.2 The currently accepted method of presenting recurrent evaluation test results is to provide FSTD results over-plotted with reference data. Test results are carefully reviewed to determine if the test is within the specified tolerances. This can be a time consuming process, particularly when reference data exhibits rapid variations or an apparent anomaly requiring engineering judgement in the application of the tolerances. In these cases the solution is to compare the results to the MQTG. If the recurrent results are the same as those in the MQTG, the test is accepted. Both the FSTD operator and the authority are looking for any change in the FSTD performance since initial qualification.

text: 2. Recurrent Evaluation Test Results Presentation 2.1 To promote a more efficient recurrent evaluation, FSTD operators are encouraged to over-plot recurrent validation test results with MQTG FSTD results recorded during the initial evaluation and as amended. Any change in a validation test will be readily apparent. In addition to plotting recurrent validation test and MQTG results, operators may elect to plot reference data as well.

text: 2.2 There are no suggested tolerances between FSTD recurrent and MQTG validation test results. Investigation of any discrepancy between the MQTG and recurrent FSTD performance is left to the discretion of the FSTD operator and the authority. 2.3 Differences between the two sets of results, other than minor variations attributable to repeatability issues (see Appendix 1 of this ACJ), which cannot easily be explained, may require investigation. 2.4 The FSTD should still retain the capability to over-plot both automatic and manual validation test results with reference data. 2.5 For FNPT special consideration for recurrent qualification is provided in ACJ No. 5 to JAR-FSTD H.030 paragraph 5.4.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-117 JAR-FSTD H

text: Bilaga 2

text: Appendix 7 to ACJ No.1 to JAR- FSTD H.030 Applicability of JAR-FSTD Amendments to FSTD Data Packages for Existing Aircraft

text: Except where specifically indicated otherwise within ACJ No 1 to JAR-FSTD H.030 Para 2.3, validation data for QTG objective tests are expected to be derived from helicopter flight-testing. Ideally, data packages for all new FSTD will fully comply with the current standards for qualifying FSTDs. For types of helicopters first entering into service after the publication of a new amendment of JAR-FSTD H, the provision of acceptable data to support the FSTD qualification process is a matter of planning and regulatory agreement (see ACJ to JAR-FSTD H.045 New Helicopter FSTD Qualification). For helicopters certificated prior to the release of the current amendment of JAR-FSTD H, it may not always be possible to provide the required data for any new or revised objective test cases compared to the previous amendments. After certification, manufacturers do not normally keep flight test aircraft available with the required instrumentation to gather additional data. In the case of flight test data gathered by independent data providers, it is most unlikely that the test aircraft will still be available. Notwithstanding the above discussion, except where other types of data are already acceptable (see, for example, ACJ Nos 1 and 2 to JAR-FSTD H.030(c)(1)), the preferred source of validation data is flight test. It is expected that best endeavours will be made by data suppliers to provide the required flight test data. If any flight test data exist (flown during the certification or any other flight test campaigns) that addresses the requirement, these test data should be provided. If any possibility exists to do this flight test during the occasion of a new flight test campaign, this should be done and provided in the data package at the next issue. Where these flight test data are genuinely not available, alternative sources of data may be acceptable using the following hierarchy of preferences: (a) Flight test at an alternate but near equivalent condition/configuration. (b) Data from an audited engineering simulation as defined in ACJ JAR-FSTD H.005 Para 1.1.e from an acceptable source (for example meets the guidelines laid out in ACJ No 1 to JAR-FSTD H.030(c)(1) Para 2), or as used for aircraft certification. (c) Aircraft Performance Data as defined in ACJ JAR-FSTD H.005 Para 1.1.b or other approved published sources (e.g., Production flight test schedule) for the following tests:- (i) 1d Hover performance (IGE, OGE) (ii) 1g Climb performance (AEO, OEI) (d) Where no other data is available then, in exceptional circumstances only, the following sources may be acceptable subject to a case-by-case review with the Authorities concerned taking into consideration the level of qualification sought for the FSTD … (iii) Unpublished but acceptable sources e.g., calculations, simulations, video or other simple means of flight test analysis or recording (iv) Footprint test data from the actual training FSTD requiring qualification validated by NAA appointed pilot subjective assessment. In certain cases, it may make good engineering sense to provide more than one test to support a particular objective test requirement. For helicopters certified prior to the date of issue of an amendment, an operator may, after reasonable attempts have failed to obtain suitable flight test data, indicate in the MQTG where flight test data are unavailable or unsuitable for a specific test. For each case, where the preferred data are not available, a rationale should be provided laying out the reasons for the non-compliance and justifying the alternate data and or test(s). These rationales should be clearly recorded within the Validation Data Road map (VDR) in accordance with and as defined in Appendix 2 to ACJ No. 1 to JAR-FSTD H.030. It should be recognized that there may come a time when there are so little compatible flight test data available that new flight test may be required to be gathered.

text: JAR-FSTD H 2-C-118 2009-11-01

text: Bilaga 2

text: Appendix 8 to ACJ No. 1 to JAR-FSTD H.030 Visual Display Systems See ACJ No. 1 to JAR-FSTD H.030

text: 1. Introduction 1.1 When selecting a visual system configuration there are many compromises to be made dependent upon the helicopter cockpit geometry, crew complement and intended use of the training device. Some of these compromises and choices regarding display systems are discussed here. 2. Basic principles of a FSTD collimated display 2.1 The essential feature of a collimated display is that light rays coming from a given point in a picture are parallel. There are two main implications of the parallel rays: first the viewer’s eyes focus at infinity and have zero convergence thus providing a cue that the object is distant. Second, the angle to any given point in the picture does not change when viewed from a different position, and thus the object behaves geometrically as though it were located at a significant distance from the viewer. These cues are self consistent, and are appropriate for any object which has been modelled as being at a significant distance from the viewer. 2.2 In an ideal situation the rays are perfectly parallel, but most implementations provide only an approximation to the ideal. Typically, a FSTD display provides an image located not closer than about 6-10m from the viewer, with the distance varying over the field of view. A schematic representations of a collimated display is provided in Figure 1 below.

text: Screen Mirror Left Eye Or Perceived Viewing Position Of Poisition Image Object

text: Right Eye Or Viewing Poisition

text: Figure 1 - Collimated display

text: 2.3 Collimated displays are well suited to many simulation applications as the area of interest is relatively distant from the observer, and so the angles to objects should remain independent of viewing position. Consider the view of the runway seen by the flight crew lined up on an approach. In the real world the runway is distant, and therefore light rays from the runway to the eyes are parallel. The runway therefore appears to be straight ahead to both crew members. This situation is well simulated by a collimated display and is presented in Figure 2. Note that the distance to the runway has been shortened for clarity. If drawn to scale the runway would be farther away and the rays from the two seats would be closer to being parallel. 2.4 While the horizontal Field of View (FOV) of a collimated display can be extended to approximately 210-220 degrees, the vertical FOV has normally been limited to about 40-45 degrees. These limitations result from tradeoffs in optical quality as well as interference between the display components and cockpit structures, but were sufficient to meet FSTD regulatory approval for Helicopter FSTDs. More recently designs have been introduced with vertical FOVs of up to 60 degrees for helicopter applications.

text: 2009-11-01 2-C-119 JAR-FSTD H

text: Bilaga 2

text: Appendix 8 to ACJ No. 1 to JAR-FSTD H.030 (continued)

text: Mirror

text: Left Seat Apparent Runway

text: Right Seat

text: Figure 2 - Runway view in a collimated display 3. Basic principles of a FSTD dome display 3.1 The situation in a dome display is shown in Figure 3. As the angles can be correct for only one eye point at a time, the visual system has been calibrated for the right seat eye point position - the runway appears to this viewer to be straight ahead of the aircraft. To the left seat viewer, however, the runway appears to be somewhat to the right of the aircraft. As the aircraft is still moving towards the runway, the perceived velocity vector will be directed towards the runway and this will be interpreted as the aircraft having some yaw offset.

text: Left Image Position Seat On Dome

text: Runway

text: Right Seat

text: Figure 3 - Runway view in a dome display 3.2 The situation is substantially different for near field objects such as are encountered in helicopter operations close to the ground. Here, objects that should be interpreted as being close to the viewer will be misinterpreted as being distant in a collimated display. The errors can actually be reduced in a dome display as shown in Figure 4 and Figure 5.

text: Left Mirror

text: Seat Perceived Object Desired Object Position Position

text: Right Seat

text: Figure 4 - Near field object in a collimated display

text: JAR-FSTD H 2-C-120 2009-11-01

text: Bilaga 2

text: 3.3 The FOV possible with a dome display can be larger than that of a collimated display. Depending on the configuration, a FOV of 240 by 90 degrees is possible and can be exceeded.

text: Left Dome Seat

text: Desired Object Position

text: Right Seat

text: Figure 5 - Near field object in a dome display

text: 4. Additional display considerations 4.1 While the situations described above are for discrete viewing positions, the same arguments can be extended to moving eye points such as are produced by the viewer moving his head. In the real world, the parallax effects resulting from head movement provide distance cues. The effect is particularly strong for relative movement of cockpit structure in the near field and modelled objects in the distance. Collimated displays will provide accurate parallax cues for distant objects, but increasingly inaccurate cues for near field objects. The situation is reversed for dome displays. 4.2 Stereopsis cues resulting from the different images presented to each eye for objects relatively close to the viewer also provide depth cues. Yet again, the collimated and dome displays provide more or less accurate cues depending on the modelled distance of the objects being viewed. 5. Training implications 5.1 In view of the basic principles described above, it is clear that neither display approach provides a completely accurate image for all possible object distances. It is therefore important when configuring a FSTD display system to consider the training role of the FSTD. Depending on the training role, either display may be the optimum choice. Factors which should be considered when selecting a design approach should include relative importance of training tasks at low altitudes, the role of the two crew members in the flying tasks, and the FOV required for specific training tasks.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-121 JAR-FSTD H

text: Bilaga 2

text: Appendix 9 to ACJ No. 1 to JAR–FSTD H.030 General technical requirements for FSTD Qualification Levels

text: This Appendix summarizes the general technical requirements for FFS levels A, B, C and D, FTD levels 1, 2, and 3, FNPT levels I, II, IIMCC, III and IIIMCC. Note: For FNPT, the term “the/a helicopter” is used to represent the aircraft being modelled which can be a specific helicopter type, a family of similar helicopter types or a totally generic helicopter.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD H 2-C-122 2009-11-01

text: Bilaga 2

text: Appendix 9 to ACJ No. 1 to JAR-FSTD H.030 (continued)

text: Table 1 – General technical requirements for JAA Level A, B, C and D FFS

text: A (See also ACJ No.2 to JAR-FSTD H.030). The lowest level of FFS technical complexity. An enclosed full-scale replica of the helicopter flight deck with representative pilots seats, including simulation of all systems, instruments, navigational equipment, communications and caution and warning systems. An Instructor’s station with seat shall be provided and at least one additional seat for inspectors/observers. Static control forces and displacement characteristics shall correspond to that of the replicated helicopter and they shall reflect the helicopter under the same static flight conditions. Representative/generic aerodynamic data tailored to the specific helicopter type with fidelity sufficient to meet the Objective Tests shall be used. Generic Ground Effect and ground handling models are permitted. Motion, visual and sound systems sufficient to support the training, testing and checking credits sought are required. A motion system having a minimum of three degrees of freedom (pitch, roll, and heave) to accomplish the required training tasks shall be provided. The visual system shall provide at least 45 degrees horizontal and 30 degrees vertical field of view per pilot. A night/dusk scene is acceptable. The response to control inputs shall not be greater than 150 milliseconds more than that experienced on the helicopter.

text: B As for Level A plus:

text: Validation Flight Test Data shall be used as the basis for flight and performance and systems characteristics. Additionally ground handling and aerodynamics programming to include ground effect reaction and handling characteristics shall be derived from validation Flight Test Data.

text: A reduced six-axis motion performance envelope is acceptable. The visual system shall provide at least 75 degrees horizontal and 40 degrees vertical field of view per pilot.

text: C The second highest Level of simulator performance.

text: As for Level B plus:

text: A Daylight/Dusk/Night Visual system is required with a continuous field of view per pilot of not less than 150 degrees horizontal and 40 degrees vertical. The sound simulation shall include the sounds of precipitation and significant helicopter noises perceptible to the pilot and shall be able to reproduce the sounds of a crash landing. The response to control inputs shall not be greater than 100 milliseconds more than that experienced on the helicopter. Turbulence and other atmospheric models shall be provided to support the training, testing and checking credit sought.

text: D The highest Level of simulator performance. As for Level C plus:

text: A full Daylight/Dusk/Night visual system is required with a continuous field of view per pilot of not less than 180 degrees horizontal and 60 degrees vertical and there shall be complete fidelity of sounds and motion buffets.

text: 2009-11-01 2-C-123 JAR-FSTD H

text: Bilaga 2

text: Table 2 – General technical requirements for JAA level 1, 2 and 3 FTDs

text: Type specific with at least one system fully represented to support the training task 1 required. A flight-deck, sufficiently closed off to exclude distractions. A full size panel of replicated system or systems with functional controls and switches. Lighting environment for panels and instruments sufficient for the operation being conducted. Flight-deck circuit breakers located as per the helicopter and functioning accurately for the system(s) represented. Aerodynamic and environment modelling sufficient to permit accurate systems operation and indication. Navigational data with corresponding approach facilities where replicated. Suitable seating arrangements for the instructor/examiner and Authority’s inspector. Proper system(s) operation resulting from management by the flight crew independent from instructor control inputs. Instructor’s controls to insert abnormal or emergency conditions into the helicopter systems. Independent freeze and reset facilities. Appropriate control forces and control travel. Appropriate flight deck sounds.

text: As for level 1 with the following additions or amendments: 2 - All systems fully represented. - Lighting environment as per helicopter. - Representative / generic aerodynamic data tailored to the specific helicopter with the fidelity to meet the objective tests. - Adjustable crewmember seats. - Flight control characteristics representative of the helicopter. - A visual system (night/dusk and day) capable of providing a field-of-view of a minimum of 150 degrees horizontally from the middle eye point and 40 degrees vertically - A visual data base sufficient to support the training requirements - Significant flight deck sounds. - On board Instructor station with control of atmospheric conditions and freeze and reset.

text: As for level 2 with the following additions or amendments: 3 - Validation flight test data as the basis for objective testing of flight, performance and systems characteristics Visual system (night/dusk/day) capable of providing a field of view of a minimum of 150 degrees horizontally from the middle eye point and 60 degrees vertically.

text: JAR-FSTD H 2-C-124 2009-11-01

text: Bilaga 2

text: Table 3A - General technical requirements for JAA level I FNPTs

text: I The lowest level of FNPT technical complexity. A flight deck that is sufficiently closed off to exclude distractions, that replicates the helicopter. Instruments, equipment, panels, systems, primary and secondary flight controls sufficient for the training events to be accomplished shall be located in a spatially correct position. Suitable arrangements for an instructor shall be provided allowing an adequate view of the crew members' panels and station. Effects of aerodynamic and environment changes for various combinations of airspeed and power normally encountered in flight. Navigation and communication equipment corresponding to that of a helicopter. Navigational data, including enroute aids and appropriate heliports, with corresponding approach procedures. Control forces and control travel shall broadly correspond to those of a helicopter. Appropriate flight deck sounds shall be available. Variable effects of wind and turbulence; Hard copy of map and approach plot Instructor’s controls to insert abnormal or emergency conditions into the basic flight instruments and navigation equipment and to vary environmental conditions. Independent freeze and reset facilities

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-125 JAR-FSTD H

text: Bilaga 2

text: Table 3B - General technical requirements for JAA level II FNPTs

text: Qualificatio General Technical Requirements n Level

text: II As for Level I with the following additions or amendments: Circuit breakers shall function correctly when involved in procedures or malfunctions requiring or involving flight crew response. Crewmembers seats with adequate adjustment. An additional observer seat. Generic ground handling and aerodynamic ground effects models.

text: Systems shall be operative to the extent that it shall be possible to perform normal, abnormal and emergency operations. Adjustable cloud base and visibility. Control forces and control travels which respond in the same manner under the same flight conditions as in a helicopter. A more complex aerodynamic model . Significant flight deck sounds, responding to pilot actions A Daylight, Dusk and Night Visual system is required with a continuous field of view per pilot of not less than 150 degrees horizontal and 40 degrees vertical.

text: A visual data base shall be provided sufficient to support the training requirements, including at least (i) Specific areas within the database with higher resolution to support landings, take-offs and ground cushion exercises and training away from a heliport. (ii) Sufficient scene details to allow for ground to map navigation over a sector length equal to 30 minutes at an average cruise speed.

text: Table 3C - General technical requirements for JAA level III FNPTs

text: III As for Type II with the following additions or amendments: A Daylight, Dusk and Night Visual system is required with a continuous field of view per pilot of not less than 150 degrees horizontal and 60 degrees vertical. Detailed high resolution visual data bases as required to support advanced training.

text: Table 3D - General Technical Requirements for JAA level IIMCC, IIIMCC FNPTs

text: For use in Multi-Crew Co-operation (MCC) training - as for Levels II or III with additional IIMCC, IIIMCC systems, instrumentation and indicators as required for MCC training and operation. Reference Appendix 1 to JAR-FSTD H.030 .

text: JAR-FSTD H 2-C-126 2009-11-01

text: Bilaga 2

text: ACJ No. 2 to JAR-FSTD H.030(interpretative material) Guidance on Design and Qualification of Level 'A' Helicopter FFS

text: 1 Background 1.1 When determining the cost effectiveness of any FSTD many factors should be taken into account such as: (a) environmental (b) safety (c) accuracy (d) repeatability (e) quality and depth of training (f) weather and crowded airspace. 1.2 The requirements as laid down by the various regulatory bodies for the lowest level of FFS do not appear to have been promoting the anticipated interest in the acquisition of lower cost FFS for the smaller helicopter used by the general aviation community. 1.3 The significant cost drivers associated with the production of any FSTD are : (a) Type Specific Data Package, (b) QTG Flight Test Data, (c) Motion System, (d) Visual System, (e) Flight Controls and (f) Aircraft Parts. Note: To attempt to reduce the cost of ownership of a JAA Level A FFS , each element has been examined in turn and with a view to relaxing the requirements where possible whilst recognising the training, checking and testing credits allowed on such a device. 2 Data package

text: 2.1 The cost of collecting specific Flight Test Data sufficient to provide a complete model of the aerodynamics, engines and flight controls can be significant. In the absence of type specific data packages the use of a class specific data package which could be tailored to represent a specific type of helicopter is acceptable. This may enable a well engineered baseline data package to be carefully tuned to adequately represent any one of a range of similar helicopters. Such work including justification and the rationale for the changes would have to be carefully documented and made available for consideration by the JAR-FSTD Steering Group as part of the qualification process. Note that for this lower level of FFS, the use of generic ground handling and generic Ground Effect models is allowed. 2.2 However specific Flight Test Data to meet the needs of each relevant test within the QTG will be required. Recognising the cost of gathering such data, two points should be borne in mind: (a) For this class of FFS , much of the flight test information could be gathered by simple means e.g. stopwatch, pencil and paper or video. However comprehensive details of test methods and initial conditions should be presented. (b) A number of tests within the QTG have had their tolerances reduced to "Correct Trend and Magnitude" (CT&M) thereby avoiding the need for specific Flight Test Data. (c) The use of CT&M is not to be taken as a indication that certain areas of simulation can be ignored. Indeed in the class of helicopter FSTD envisaged, that might take advantage of Level A, it is imperative that the specific characteristics are present, and incorrect effects would be unacceptable (e.g. if the helicopter has a weak positive spiral stability, it would not be acceptable for the FFS to exhibit neutral or negative spiral stability). (d) Where CT&M is used as a tolerance, it is strongly recommended that an automatic recording system be used to "footprint" the baseline results thereby avoiding the effects of possible divergent subjective opinions on recurrent evaluations. 3 Motion 3.1 For Level A FFS , the requirements for both the primary cueing and buffet simulation have not been specified in detail. Traditionally, for primary cueing, emphasis has been laid on the numbers of axes available on the motion system. For this level of FFS, it is felt appropriate that the FFS

text: 2009-11-01 2-C-127 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 2 to JAR-FSTD H.030 (continued)

text: manufacturer should be allowed to decide on the complexity of the motion system. However, during the evaluation, the motion system will be assessed subjectively to ensure that it is supporting the piloting task, including engine failures, and is in no way providing negative cueing. 3.2 Buffet simulation is important to add realism to the overall simulation ; for Level A, the effects can be simple but they should be appropriate, in harmony with the sound cues and in no way providing negative training. 4 Visual 4.1 Other than field of view (FOV) technical criteria for the visual systems are not specified. The emergence of lower cost ‘raster only’ day light systems is recognised. The adequacy of the performance of the visual system will be determined by its ability to support the flying tasks. e.g. "Visual cueing sufficient to support changes in approach path by using runway perspective". 4.2 A single channel direct viewing system would be acceptable for this level of FFS. 4.3 The vertical field of view FOV specified (30°) may be insufficient for certain tasks. Some smaller helicopters have large downward viewing angles which cannot be accommodated by the ±15° vertical FOV. This can lead to two limitations : (a) at the CAT 1 decision height, the appropriate visual ground segment may not be "seen", and (b) during an approach, where the helicopter goes below the ideal approach path, during the subsequent pitch up to recover, adequate visual reference to make a landing on the runway may be lost. 5 Flight controls The specific requirements for flight controls remain unchanged. Because the handling qualities of smaller helicopters are inextricably intertwined with their flight controls, there is little scope for relaxation of the tests and tolerances. It could be argued that with Reversible Control Systems that the “on ground” static sweep should in fact be replaced by more representative "in air" testing. It is hoped that lower cost control loading systems would be adequate to fulfil the needs of this level of simulation (i.e. electric). 6 Aircraft parts As with any level of FSTD, the components used within the cockpit area need not be helicopter parts ; however, any parts used should be robust enough to endure the training tasks. Moreover, the Level A FFS is type specific, thus all relevant switches, instruments, controls etc. within the simulated area will be required to look, feel and have the same functionality as in the helicopter.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD H 2-C-128 2009-11-01

text: Bilaga 2

text: ACJ No. 3 to JAR-FSTD H.030 (explanatory material) Guidance on Design and Qualification of Helicopter FTDs See JAR-FSTD H.030

text: 1 Basic Philosophy 1.1 The basic premises in defining FTDs were to follow the prescribed JAR-FSTD practices but to reflect the unique training requirements of rotary wing aircraft. It was recognised, from the outset, that the training requirements and the operating/training economics of the average helicopter operator were rather different from those of the majority of fixed wing operators. The helicopter FTD was envisaged as a training device that could be justified both for systems training and secondarily for some type training, testing and checking. Finally, it was accepted that there could not be two differing sets of criteria for the qualification of FSTD that are approved for type testing & checking. If a technical criterion has been set as the minimum necessary for the type accreditation of a manoeuvre or training event in the FFS, the same criterion shall apply to the FTD in order that a two tier checking philosophy is not introduced. 1.2 Following upon these premises, it was decided to define three levels of helicopter FTD. 1.3 The FTD Level 1 would be to cater only for systems training and would be used by those operators who had helicopters including complex systems. In this role it could be utilised both in ground school technical training as well as operations type training. It would be without motion or visual systems and requires aerodynamic and environmental modelling (using design data that might be generic but tailored to represent the helicopter) of sufficient fidelity to provide accurate systems operation & indications. The validation of the simulation would be confirmed by objective tests designed to meet the training task for the systems for which accreditation was to be sought. The FTD Level 1 could prove to be a reasonably inexpensive and cost effective training solution but this level would not necessarily meet the criteria to enable its additional qualification as an FNPT. 1.4 The second and third level of FTD were designed to provide type specific devices with visual systems but no motion which can be offered for varying levels of credits.

text: 1.5 The helicopter FTD Level 2 would require the use of design & validation data similar to that for FTD Level 1 but all systems would have to be represented as well as a visual system meeting the requirements of an FNPT II. The FTD Level 2 criteria would permit the device to be used for part of the type rating training syllabus, for recency flying and IR revalidation. 1.6 The FTD 3 would require the use of the same quality of flight test data as the basis for flight & performance and system characteristics and validation flight test data for the objective testing, as is required for a FFS. A visual system meeting the criteria of that fitted to an FNPT III would be the minimum requirement. The FTD Level 3 should be capable of being approved for many of the type training, testing & checking manoeuvres and events awarded to a FFS, the exceptions would include those events for which motion cueing is considered necessary. 2 Design Standards There are three sets of FTD design standards specified within JAR-FSTD H, FTD Levels 1, 2 and 3, the most demanding being those for FTD Level 3. 2.1 The Flight Deck. The flight deck should be representative of the “helicopter”. The controls, instruments and avionics controllers should be representative in touch, feel, layout, colour and lighting to create a positive learning environment and good transfer of training to the helicopter. For good training ambience the flight deck of the FTD I should be sufficiently enclosed to exclude any distractions. For both FTD Level 2 and 3 the flight deck should be fully enclosed. Distractions arising from external sources, which may affect the student’s concentration or that may denigrate the effects of the simulation, should be avoided. Thus in the case of an FTD Level 1, if the rear of the device is open, it would be inappropriate to install this type of device in an non-enclosed room or in an area where several such devices are located. Where this is to be permitted, the activities in one device may affect those in an adjacent one. If the device is to be installed in an area shared by other devices then the rear of the flight deck including the instructors’ station should be fully enclosed, and this enclosure should extend to include the roof. In the case of the FTD 2 and 3 the same interpretations should apply but an additional consideration is that the performance of the visual system will be adversely

text: 2009-11-01 2-C-129 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 3 to JAR-FSTD H.030 (continued) affected by any light ingress or reflections. It follows that it would not be necessary to have a fully enclosed structure at the rear of the flight deck were the FTD to be installed in a separate room.

text: 2.2 Flight Deck Components. As with any training device, the components used within the flight deck area do not need to be helicopter parts: however, any parts used should be representative and should be robust enough to endure the training tasks. The use of CRTs or “Flat Panel” displays with physical overlays incorporating operational switches/knobs/buttons replicating a helicopter instrument panel would be acceptable. The training tasks envisaged for these devices are such that appropriate layout and feel is very important: i.e. the altimeter sub-scale knob needs to be physically located on the altimeter. 3 Latency and Visual 3.1 There are two methods of establishing latency which is the relationship between the controls and the visual system, flight deck instruments response and initial motion system response, if fitted. These should be coupled closely to provide integrated sensory cues.

text: 3.2 Either transport delay or response time tests are acceptable. Response time tests check that the response to abrupt pitch, roll, and yaw inputs at the pilot's position is within the permissible delay, but not before the time when the helicopter would respond under the same conditions. Visual scene changes from steady state disturbance should occur within the system dynamic response limit (but not before the resultant motion onset if fitted). 3.3 The transport delay test should measure all the delay encountered by a step signal migrating from the pilot's control through the control loading electronics (if applicable) and interfacing through all the simulation software modules in the correct order, using a handshaking protocol, finally through the normal output interfaces to the visual system and instrument displays. A recordable start time for the test should be provided by a pilot flight control input. The test mode should permit normal computation time to be consumed and should not alter the flow of information through the hardware/software system.

text: 3.4 The Transport Delay of the system is the time between control input and the individual hardware responses. It need only be measured once in each axis. 4 Motion Although motion is not a requirement for an FTD, should the FSTD operator choose to have one fitted, it will be evaluated to ensure that its contribution to the overall fidelity of the device is not negative. Unless otherwise stated in this document, the motion requirements are as specified for a Level A FFS, see ACJ No. 2 to JAR-FSTD H.030 4.1 For Level A flight simulators, the requirements for both the primary cueing and buffet simulation have been not specified in detail. Traditionally, for primary cueing, emphasis has been laid on the numbers of axes available on the motion system. For this level of flight simulator, it is felt appropriate that the simulator manufacturer should be allowed to decide on the complexity of the motion system. However, during the evaluation, the motion system will be assessed subjectively to ensure that it is supporting the piloting task, including engine failures, and is in no way providing negative cueing. 4.2 Buffet simulation is important to add realism to the overall simulation; for Level A, the effects can be simple but they should be appropriate, in harmony with the sound cues and in no way providing negative training. 4.3 The motion system transport delay should meet the standards prescribed for the visual display and cockpit instrument response. 5 Testing / Evaluation 5.1 To ensure that any device meets its design criteria initially and periodically throughout its life a system of objective and subjective testing will be used. The subjective and objective testing methodology should be similar to that in use for FFS.

text: JAR-FSTD H 2-C-130 2009-11-01

text: Bilaga 2

text: ACJ No. 3 to JAR-FSTD H.030 (continued)

text: 5.2 The validation tests specified under ACJ No. 1 to JAR-FSTD H.030, para 2 can be "flown" by a suitably skilled person and the results recorded manually. Bearing in mind the cost implications, the use of automatic recording (and testing) is encouraged thereby increasing the repeatability of the achieved results. 5.3 The tolerances specified are designed to ensure that the device meets its original target criteria year after year. It is therefore important that any such target data is carefully derived and values are agreed with the Authority in advance of any formal qualification process.

text: 5.4 The use of CT&M is not to be taken as an indication that certain areas of simulation can be ignored. For such tests, the performance of the device should be appropriate and representative of the helicopter configuration and should under no circumstances exhibit negative characteristics. Where CT&M is used as a tolerance, it is strongly recommended that an automatic recording system be used to "footprint" the baseline results thereby avoiding the effects of possible divergent subjective opinions during recurrent evaluations.

text: 5.5 The subjective tests listed under "Functions and Manoeuvres" in ACJ No. 1 to JAR-FSTD H.030, para 3, should be flown out by a suitably qualified and experienced pilot. Subjective testing will review not only the interaction of all of the systems but the integration of the FTD with: (a) Training environment (b) Freezes and repositions (c) Nav-aid environment (d) Communications (e) Weather and visual scene contents In parallel with this objective/subjective testing process it is envisaged that suitable maintenance arrangements as part of a Quality Assurance Programme shall be in place. Such arrangements will cover routine maintenance, the provision of satisfactory spares holdings and personnel and may be subject to a regulatory audit.

text: 6 Additional features 6.1 Any additional features in excess of the minimum design requirements added to any FTD Level 1, 2 and 3 will be subject to evaluation and should meet the appropriate standards in JAR-FSTD.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-131 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 4 to JAR-FSTD H.030 (explanatory material) Use of Data for Helicopter FTDs See ACJ No. 1 to JAR-FSTD H.030 See also ACJ to JAR-FSTD H.045

text: 1. Two types of data are required for the development and qualification of a FSTD; namely, design data, which are used to develop simulation models, and the second, termed validation data, are used to objectively confirm that the simulation models reflect the static as well as the dynamic performance characteristics of the helicopter. Some levels of FTD to be qualified under JAR-FSTD H require that their design data be based upon helicopter type specific data and/or that the validation tests have a similar baseline. It is not always intended that such design and validation data must be the helicopter manufacturers’ flown test data in the same manner as are required for FFS. Whilst this is the preferred source, cost and availability can preclude their use. Acceptable alternatives can be data obtained from research laboratories or other data procurement agencies and companies as well as preliminary data from a helicopter manufacturer’s engineering simulator.

text: 2. For the FTD Level 1 & 2 much of the flight test data could be gathered from helicopter maintenance, performance, flight manuals, and system user guides supplemented by data gathered and recorded, in flight, by simple means, e.g. video, stopwatch, pencil & paper. However for the latter, comprehensive details of test methods and initial and ambient conditions should be presented. In addition, this data may also be supplemented with theoretically calculated results. 3. For FTD Level 3 it is necessary to use validation flight test data, such as is required for higher level FFS but limited only to the validation of flight, performance, handling qualities and systems characteristics. 4. The substitution of Correct Trend & Magnitude (CT&M) for defined tolerances also reduces the reliance upon specific flight test data, but this must not be taken as an indication that certain areas of simulation can be ignored. It is imperative that the specific characteristics of the helicopter are present and incorrect effects would be unacceptable.

text: 5. The JAA will expect any FTD manufacturer who wishes to take advantage of the use of an alternative type of data to helicopter manufacturer’s flown data, to demonstrate a sound engineering basis for his proposed approach. Such demonstration will need to show the predicted simulation effects and that they are easily understood and defined. The JAA FSTD Steering Group will constitute an Authorities team to review any applications for the substitution of data other than that of the helicopter manufacturer’s flown data.

text: INTENTIONALLY LEFT BLANK

text: JAR-FSTD H 2-C-132 2009-11-01

text: Bilaga 2

text: ACJ No. 5 to JAR-FSTD H.030 (interpretative material) Guidance on Design and Qualification of Helicopter FNPTs See also JAR-FSTD H.030

text: 1 Basic philosophy 1.1 Traditionally training devices used by the ab-initio professional pilot schools have been relatively simple instrument flight-only aids. These devices were loosely based on the particular school's helicopter. The performance would be approximately correct in a small number of standard configurations, however the handling characteristics could range from rudimentary to loosely representative. The instrumentation and avionics fit varied between a basic fit and one very close to the target helicopter. The approval to use such devices as part of a training course was based on a regular subjective evaluation of the equipment and its operator by an authority inspector. 1.2 The FNPT I is essentially a replacement for the traditional instrument flight ground training device. The FNPT II and FNPT III are more sophisticated standards and each fulfil the wider requirements of the various JAR-FCL professional pilot training modules up to and including (optionally with additional features) multi-crew co-operation (MCC) training. 1.3 The currently available technology enables such devices to have much greater capabilities and lower life-cycle costs than was previously possible. A more objective design basis encourages better understanding and therefore better modelling of helicopter systems, handling and performance. These advances combined with the costs of flying and with the environmental pressures all point towards the need for FNPT standards. 2 Design Standards There are five sets of design standards specified within JAR-FSTD H, FNPT I , II , IIMCC, III and IIIMCC. 2.1 Simulated Helicopter Configuration Unlike FFS and FTD , FNPTs are not primarily intended to be representative of a specific type of helicopter (although they may in fact be type specific if desired). The configuration chosen should sensibly represent the helicopter or helicopters likely to be used as part of the overall training package. Areas such as general layout, seating, instruments and avionics, control type, control force and position, performance and handling and powerplant configuration should be representative of the class of helicopters or the helicopter itself. Note: throughout this document, the term “helicopter” is used to represent the aircraft being modelled which can be a specific helicopter type, a family of similar helicopter types or a totally generic helicopter. It would be beneficial for all parties involved in the acquisition of an FNPT to engage in early discussions with the Authority to broadly agree a suitable device configuration. Ideally any such discussion would take place in time to avoid any delays in the design/build/acceptance process thereby ensuring a smooth entry into service. The configuration chosen should be sensibly representative of the “helicopter” likely to be used as part of the overall training package, especially in areas such as general flight deck layout, seating, instruments and avionics, flying controls control forces and positions, performance, handling and powerplant. 2.2 The Flight Deck

text: The flight deck should be representative of the “helicopter”. The controls, instruments and avionics controllers should be representative in touch, feel, layout, colour and lighting to create a positive learning environment and good transfer of training to the helicopter. For good training ambience the flight deck of the FNPT I should be sufficiently enclosed to exclude any distractions. For both FNPT IIs and IIIs the flight deck should be fully enclosed. Distractions arising from external sources, which may affect the student’s concentration or that may denigrate the effects of the simulation, should be avoided. Thus in the case of an FNPT I, if the rear of the device is open, it would be inappropriate to install this type of device in a non-enclosed room or in an area where several such devices are located. Were this to be permitted, the activities in one device may affect those in an adjacent one. If the device is to be installed in an area shared by other devices then the rear of the flight deck including the instructor’s station should be fully enclosed, and this enclosure should extend to include the roof. In the case of the FNPT II and III the same interpretations should apply

text: 2009-11-01 2-C-133 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 5 to JAR-FSTD H.030 (continued)

text: but an additional consideration is that the performance of the visual system will be adversely affected by any light ingress or reflections. It follows that it would not be necessary to have a fully enclosed structure at the rear of the flight deck were the FNPT to be installed in a separate room. 2.3 Flight Deck Components As with any training device, the components used within the flight deck area do not need to be aircraft parts: however, any parts used should be representative and should be robust enough to endure the training tasks. With the current state of technology the use of simple CRT/LCD monitor based representations and touch screen controls would be acceptable. The training tasks envisaged for these devices are such that appropriate layout and feel is very important: i.e. the altimeter sub-scale knob needs to be physically located on the altimeter. The use of CRT/LCDs with physical overlays incorporating operational switches/knobs/buttons replicating a helicopter instrument panel may be acceptable.

text: 2.4 Data The data used to model the aerodynamics, flight controls and engines should be soundly based on a helicopter. It is not acceptable and would not give good training if the models merely represented a few key configurations bearing in mind the extent of the potential credits available. Validation data may be derived from a specific helicopter within a family of helicopters that the FNPT is intended to represent, or it may be based on information from several helicopters within a family. It is recommended that the intended validation data together with a substantiation report be submitted to the Authority for review.

text: 2.4.1 Data Collection and Model Development Recognising the cost and complexity of flight simulation models, it should be possible to generate generic family "typical" models. Such models should be continuous and vary sensibly throughout the required training flight envelope. A basic requirement for any modelling is the integrity of the mathematical equations and models used to represent the flying qualities and performance of the designated helicopter configuration simulated. Data to tune the generic model to represent a more specific helicopter can be obtained from many sources without recourse to expensive flight test such as: (a) Helicopter design data (b) Flight and Maintenance Manuals (c) Observations on ground and in air Data obtained on the ground and in flight can be measured and recorded using a range of simple means such as: (a) Video (b) Pencil and paper (c) Stopwatch (d) New technologies Any such data gathering should take place at representative masses and centres of gravity. Development of such a data set including justification and the rationale for the design and intended performance, the measurement methods and recorded parameters (e.g. mass, CG, atmospheric conditions) should be carefully documented and available for inspection by the Authority as part of the qualification process. 2.5 Limitations In helicopters, varied and different flight control configurations can be found: with and without servo-control assistance, with and without artificial feel trim control forces, trim control release and automatic trim. As a consequence, simulation of the flight control forces should take into account user requirements in order to define the optimum solution in an effort to simplify the control loading requirements. It should be remembered however that whilst a simple model may be sufficient for the task, it is vitally important that negative characteristics are not present. 3 Latency and Visual

text: JAR-FSTD H 2-C-134 2009-11-01

text: Bilaga 2

text: ACJ No. 5 to JAR-FSTD H.030 (continued)

text: There are two methods of establishing latency which is the relationship between the controls and the visual system, flight deck instruments (and initial motion system if fitted) response. These should be coupled closely to provide integrated sensory cues. For a generic FNPT, a Transport Delay test is the only suitable test which demonstrates that the FNPT system does not exceed the permissible delay. If the FNPT is based upon a particular helicopter type, either Transport Delay or Response Time tests are acceptable. Response time tests check that the response to abrupt pitch, roll, and yaw inputs at the pilot's position is within the permissible delay, but not before the time when the “helicopter” would respond under the same conditions. Visual scene changes from steady state disturbance should occur within the system dynamic response limit (but not before the resultant motion onset if fitted).The Transport Delay test should measure all the delay encountered by a step signal migrating from the pilot's control , through the control loading electronics (if applicable) and interfacing through all the simulation software modules in the correct order, using a handshaking protocol, finally through the normal output interfaces to the visual system and instrument displays. A recordable start time for the test should be provided by a pilot flight control input. The test mode should permit normal computation time to be consumed and should not alter the flow of information through the hardware/software system . The Transport Delay of the system is the time between control input and the individual hardware responses. It need only be measured once in each axis. 3.2 Care should be taken when using the limited processing power of the lower cost visual systems to concentrate on the key areas which support the intended uses thereby avoiding compromising the visual model by including unnecessary features e.g. moving ground traffic, marshallers. The capacity of the visual model should be directed towards: (a) Runway/Heliport surface (b) Runway/Heliport lighting systems (c) Approach guidance aids and lighting systems (d) TLOF and FATO (e) Detailed ground features where credits are required for navigation training (f) Basic environmental lighting (night/dusk) 4 Motion Although motion is not a requirement for either an FNPT, should the FSTD operator choose to have one fitted, it will be evaluated to ensure that its contribution to the overall fidelity of the device is not negative. Unless otherwise stated in this document, the motion requirements are as specified for a Level A FFS, see ACJ No. 2 to JAR-FSTD H.030 4.1 For Level A flight simulators, the requirements for both the primary cueing and buffet simulation have been not specified in detail. Traditionally, for primary cueing, emphasis has been laid on the numbers of axes available on the motion system. For this level of flight simulator, it is felt appropriate that the simulator manufacturer should be allowed to decide on the complexity of the motion system. However, during the evaluation, the motion system will be assessed subjectively to ensure that it is supporting the piloting task, including engine failures, and is in no way providing negative cueing. 4.2 Buffet simulation is important to add realism to the overall simulation; for Level A, the effects can be simple but they should be appropriate, in harmony with the sound cues and in no way providing negative training. 4.3 The motion system transport delay should meet the standards prescribed for the visual and flight instruments. 5 Testing / Evaluation 5.1. General The FNPT should be assessed in those areas which are essential to completing the pilot training, testing and checking process. This includes the FNPT's longitudinal and lateral directional responses, specific operations, control checks, flight deck, and instructor station functions checks, and certain additional requirements depending on the complexity or Qualification Level of the

text: 2009-11-01 2-C-135 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 5 to JAR-FSTD H.030 (continued)

text: FNPT. The visual system (where applicable) will be evaluated against tests contained in the table of validation tests (ACJ 1 to JAR-FSTD H 030) . To ensure that any device meets its design criteria initially and periodically throughout its life a system of objective and subjective testing will be used. The subjective and objective testing methodology should be similar to that in use for FFS. The validation tests specified (ACJ no 1 to JAR-FSTD H.030 section 2.3) can be "flown" by a suitably skilled person and the results recorded manually. Bearing in mind the cost implications, the use of automatic recording (and testing) is encouraged thereby increasing the repeatability of the achieved results but any such automatic test shall be capable of being rerun by manually flying the test. The tolerances specified are designed to ensure that the device meets its original target criteria year after year. It is therefore important that such target data is carefully derived and values are agreed with the appropriate inspecting authority in advance of any formal qualification process. For initial qualification, it is highly desirable that the device should meet its design criteria within the listed tolerances, however unlike the tolerances specified for FFS, the tolerances contained within this document are specifically intended to be used to ensure repeatability during the life of the device and in particular at each recurrent regulatory inspection. 5.2. Validation tests The intent is to evaluate the FNPT as objectively as possible. Pilot acceptance, however, is also an important consideration. Therefore, the FNPT will be subjected to Validation, and Functions and Subjective Tests listed in (ACJ 1 to JAR-FSTD H 030). Validation Tests are used to compare objectively FNPT performances against Validation Data to ensure that they agree within design tolerances acceptable to the Authority. Functions and Subjective Tests provide a basis for evaluating FNPT capability to perform over a typical training period determining that the FNPT will satisfactorily meet each stated training objective and competently simulate each training manoeuvre or procedure and to verify correct operation of the FNPT.

text: The design data may be derived from flight test data, manufacturer's design data, information from a helicopter Flight Manual and Maintenance Manuals, results of approved or commonly accepted simulations or predictive models, recognised theoretical results, information from the public domain, or other sources as deemed necessary by the FNPT manufacturer to be representative of a helicopter. The use of CT&M is not to be taken as an indication that certain areas of simulation can be ignored. For such tests, the performance of the device should be appropriate and representative of the “helicopter” configuration and should under no circumstances exhibit negative characteristics. Where CT&M is used as a tolerance, it is strongly recommended that an automatic recording system be used to "footprint" the baseline results thereby avoiding the effects of possible divergent subjective opinions during recurrent evaluations. 5.3 Subjective tests

text: The subjective tests listed under "Functions and Subjective tests" (ACJ 1 to JAR-FSTD H.030) should be flown out by a suitably qualified and experienced pilot. Subjective testing will review not only the interaction of all of the systems but the integration of the FNPT with : (a) Training environment (b) Freezes and repositions (c) Navaid environment (d) Communications (e) Weather and visual scene contents

text: JAR-FSTD H 2-C-136 2009-11-01

text: Bilaga 2

text: ACJ No. 5 to JAR-FSTD H.030 (continued)

text: 5.4. Initial qualification For initial qualification testing of FNPTs Validation Data will be used. They may be derived from a specific helicopter or they may be based on information from several helicopters within the group of helicopters. The substantiation of the set of data used to build the validation data should be in the form of an engineering report and should show that the proposed validation data are representative of a helicopter. With the concurrence of the Authority, it may be in the form of a manufacturer's previously approved set of Validation Data for the applicable FNPT. Once the set of data for a specific FNPT has been accepted and approved by the Authority, it will become the Validation Data that will be used as reference for subsequent recurrent evaluations. For FNPT initial qualification, the tolerances listed for parameters in the validation list table (ACJ 1 to JAR-FSTD H 030) should be replaced by ‘Correct Trend and Magnitude’ (CT & M) and the FNPT should be tested and assessed as representative of a helicopter to the satisfaction of the Authority.

text: Tolerances listed for parameters in the validation tests table (ACJ 1 to JAR-FSTD H 030) should not be confused with FNPT design tolerances. Validation test tolerances are the maximum acceptable for FNPT recurrent qualification testing. FSTD operators seeking initial or upgrade evaluation of an FNPT should be aware that performance and handling data for older helicopters may not be of sufficient quality to meet some of the test standards contained in this ACJ. In this instance it may be necessary for an FSTD operator to acquire additional design and/or validation data.

text: During FNPT evaluation, if a problem is encountered with a particular FSTD Validation Test, the test may be repeated to ascertain if the problem was caused by test equipment or FSTD operator error. Following this, if the test problem persists during initial FNPT evaluation an FSTD operator should be prepared to offer alternative test results which relate to the test in question. Validation Tests which do not meet the test criteria should be addressed to the satisfaction of the Authority.

text: 5.5. Maintenance In parallel with this objective/subjective testing process it is envisaged that suitable maintenance arrangements as part of a Quality Assurance Programme shall be in place. Such arrangements will cover routine maintenance, the provision of satisfactory spares holdings and personnel and may be subject to a regulatory audit.

text: 6 Additional features Any additional features in excess of the minimum design requirements added to an FNPT I, II & III will be subject to evaluation and should be assessed to avoid negative training.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-137 JAR-FSTD H

text: SECTION 2

text: Bilaga 2

text: ACJ No. 5 to JAR-FSTD H.030 (continued)

text: JAR-FSTD H 2-C-138 2009-11-01

text: SECTION 2

text: Bilaga 2

text: ACJ No. 5 to JAR-FSTD H.030 (continued)

text: 2009-11-01 2-C-139 JAR-FSTD H

text: SECTION 2

text: Bilaga 2

text: ACJ No. 5 to JAR-FSTD H.030 (continued)

text: JAR-FSTD H 2-C-140 2009-11-01

text: Bilaga 2

text: ACJ No. 1 to JAR-FSTD H.030(c)(1) (acceptable means of compliance) Engineering Simulator Validation Data See JAR-FSTD H.030(c)(1)

text: 1. When a fully flight-test validation simulation is modified as a result of changes to the simulated helicopter configuration, a qualified helicopter manufacturer may choose, with the prior agreement of the Authority, to supply validation data from an “audited” engineering simulator/simulation to supplement selectively flight test data.

text: This arrangement is confined to changes which are incremental in nature and which are both easily understood and well-defined. 2. To be qualified to supply engineering simulator validation data, an helicopter manufacturer should: (a) have a proven track record of developing successful data packages: (b) have demonstrated high quality prediction methods through comparisons of predicted and flight test validated data; (c) have an engineering simulator which - has models which run in an integrated manner, - uses the same models as released to the training community (which are also used to produce stand/alone proof-of-match and checkout documents), - is used to support helicopter development and certification; (d) use the engineering simulation to produce a representative set of integrated proof-ofmatch cases; (e) have an acceptable configuration control system in place covering the engineering simulator and all other relevant engineering simulations. 3. Helicopter manufacturers seeking to take advantage of this alternative arrangement shall contact the Authority at the earliest opportunity. 4. For the initial application, each applicant should demonstrate his ability to qualify to the satisfaction of the JAA FSTD Steering Group, in accordance with the criteria in this ACJ and the corresponding ACJ No. 2 to JAR-FSTD H.030(c)(1).

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-141 JAR-FSTD H

text: Bilaga 2

text: ACJ No. 2 to JAR-FSTD H.030(c)(1) (interpretative material) Engineering Simulator Validation Data – Approval Guidelines See JAR-FSTD H.030(c)(1)

text: 1. Background 1.1. In the case of fully flight-test validated simulation models of a new or major derivative aircraft, it is likely that these models will become progressively unrepresentative as the aircraft configuration is revised. 1.2. Traditionally as the aircraft configuration has been revised, the simulation models have been revised to reflect changes. In the case of aerodynamic, engine, flight control and ground handling models, this revision process normally results in the collection of additional flight-test data and the subsequent release of new models and validation data. 1.3. The quality of the prediction of simulation models has advanced to the point where differences between the predicted and the flight-test validation models are often quite small. 1.4. The major aircraft manufacturers utilise the same simulation models in their engineering simulations as released to the training community. These simulations vary from physical engineering simulators with and without aircraft hardware to non-real-time work station based simulations. 2. Approval Guidelines – for using Engineering Simulator Validation Data

text: 2.1. The current system of requiring flight test data as a reference for validating training simulators should continue. 2.2. When a fully flight-test-validated simulation is modified as a result of changes to the simulated aircraft configuration, a qualified aircraft manufacturer may choose, with prior agreement of the Authority, to supply validation data from an engineering simulator/simulation to supplement selectively flight test data.

text: 2.3. In cases where data from an engineering simulator is used, the engineering simulation process would have to be audited by the Authority. 2.4 In all cases a data package verified to current standards against flight test should be developed for the aircraft “entry-into-service” configuration of the baseline aircraft. 2.5 Where engineering simulator data is used as part of a QTG, an essential match is expected as described in Appendix 1 to ACJ No. 1 to JAR-FSTD H.030

text: 2.6 In cases where the use of engineering simulator data is envisaged, a complete proposal should be presented to the appropriate regulatory body(ies). Such a proposal would contain evidence of the aircraft manufacturer’s past achievements in high fidelity modelling. 2.7 The process will be applicable to “one step” away from a fully flight validated simulation. 2.8 A configuration management process should be maintained, including an audit trail which clearly defines the simulation model changes step by step away from a fully flight validated simulation, so that it would be possible to remove the changes and return to the baseline (flight validated) version. 2.9 The Authorities will conduct technical reviews of the proposed plan and the subsequent validation data to establish acceptability of the proposal. 2.10 The procedure will be considered complete when an approval statement is issued. This statement will identify acceptable validation data sources.

text: 2.11 To be admissible as an alternative source of validation data an engineering simulator would: (a) Have to exist as a physical entity, complete with a flight deck representative of the affected class of aircraft, with controls sufficient for manual flight. (b) Have a visual system; and preferably also a motion system. (c) Where appropriate, have actual avionics boxes interchangeable with the equivalent software simulations, to support validation of released software. (d) Have a rigorous configuration control system covering hardware and software.

text: JAR-FSTD H 2-C-142 2009-11-01

text: Bilaga 2

text: ACJ No. 2 to JAR-FSTD H.030(c)(1) (continued)

text: (e) Have been found to be a high fidelity representation of the aircraft by the pilots of the manufacturers, operators and the Authority. 2.12 The precise procedure followed to gain acceptance of engineering simulator data will vary from case-to-case between aircraft manufacturers and type of change. Irrespective of the solution proposed, engineering simulations/simulators should conform to the following criteria: (a) The original (baseline) simulation models should have been fully flight-test validated. (b) The models as released by the aircraft manufacturer to the industry for use in training FSTDs should be essentially identical to those used by the aircraft manufacturer in their engineering simulations/simulators. (c) These engineering simulation/simulators will have been used as part of the aircraft design, development and certification process. 2.13 Training FSTDs utilising these baseline simulation models should be currently qualified to at least internationally recognised standards.

text: 2.14 The type of modifications covered by this alternative procedure will be restricted to those with “well understood effects”: (a) Software (e.g., flight control computer, autopilot, etc.). (b) Simple (in aerodynamic terms) geometric revisions (e.g., body length). (c) Engines (d) Control system gearing, rigging, deflection limits (e) Brake, tyre and steering revisions. 2.15 The manufacturer, who wishes to take advantage of this alternative procedure, is expected to demonstrate a sound engineering basis for his proposed approach. Such analysis would show that the predicted effects of the change(s) were incremental in nature and both easily understood and well defined, confirming that additional flight test data were not required. In the event that the predicted effects were not deemed to be sufficiently accurate, it might be necessary to collect a limited set of flight test data to validate the predicted increments. 2.16 Any applications for this procedure will be reviewed by an Authorities team established by the JAA FSTD Steering Group.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-143 JAR-FSTD H

text: Bilaga 2

text: ACJ to JAR-FSTD H.035 FFS Approved or Qualified before 1 April 2001 See JAR–FSTD H.035

text: 1 Introduction 1.1 Under previous National Rules, FFS may have gained credits in accordance with primary reference documents which state appropriate technical criteria.

text: 1.2 Other FFS may not have been monitored to the same extent, but may have documents or statements from their Authority giving broad or specific permission for them to be used for certain training, testing and checking manoeuvres. 1.3 It is intended that FFS should continue to maintain their Qualification Level and or approval granted prior to the adoption of JAR-STD 1H and subsequently JAR-FSTD H. 2 Recategorisation

text: Some of these FFS may be of a standard which permits them to be recategorised as if they were FFS presented for initial qualification on or after 1 April 2001. 3 Equivalent categories AG, BG, CG, DG 3.1 FFS that are not recategorised and that do have an acceptable primary reference document used for their original national qualification or national approval, will gain a JAA qualification based upon their original technical Qualification Level. The equivalent qualification will relate to permitted manoeuvres in the original national qualification or approval document providing that these older FFS continue to meet the original national criteria when evaluated by the Authority. 3.2 The letter G will be added to each originally issued Qualification Level to show that the existing Qualification Level deserves its credit under the grandfather right provisions. To comply with the rule, the primary reference document should have meaningful Validation, Functions and Subjective Tests criteria which reasonably cover the performance envelope of the FFS and in particular the manoeuvres for which the equivalent JAA Level of Qualification is given. The minimum acceptable standard is AC120-63 or equivalent. 4 Original national qualification 4.1 FFS that are not recategorised and that do not have an acceptable primary reference document may continue to enjoy credits for an agreed list of training, testing and checking manoeuvres, provided they maintain their performance in accordance with any Validation and Functions and Subjective Tests which have been previously established or a list of tests selected from ACJ to JAR-FSTD H.030 by agreement with the Authority. Again the tests should relate to the list of manoeuvres permitted under the original national qualification or approval document. 4.2 The award of credits to a FFS user should be at the discretion of the Authority. Current FFS users may retain the credits granted under their previous national criteria. 5 Grandfather rights summary

text: The following table summarises the arrangements for FFS approved or qualified before 1 April 2001 and which are not recategorised :

text: JAA EQUIVALENT PERFORMANCE QUALIFICATION LEVEL CRITERIA

text: Primary Ref. Doc AG Maximum training, Perform to the original National BG testing and checking Validation Functions and Subjective CG Credits similar Tests from Reference Doc. DG to A, B, C, D

text: No Primary Ref. Doc Special Categories Original Validation, Functions and Unique list of Manoeuvres Subjective Tests or a list of tests selected from ACJ N°1 to JAR-FSTD H.030 (by agreement)

text: JAR-FSTD H 2-C-144 2009-11-01

text: Bilaga 2

text: ACJ to FSTD H.037 FNPT Approved or Qualified before 1 January 2003 See JAR–FSTD H.037

text: 1 Introduction 1.1 Under previous national rules, FNPTs may have gained credits in accordance with primary reference documents which state appropriate technical criteria. 1.2 Other FNPTs may not have been monitored to the same extent, but may have documents or statements from their National Authority giving broad or specific permission for them to be used for certain training, testing and checking manoeuvres. 1.3 In any case, it is intended that FNPTs should continue to maintain their Qualification Level and or approval granted prior to the adoption of JAR–FSTD H in accordance with previous national criteria. 2 Recategorisation Some of these FNPTs may be of a standard which permits them to be recategorised as if they were FNPTs presented for initial qualification on or after 1 January 2003. 3 Original national qualification 3.1 FNPTs that are not recategorised and that do not have an acceptable primary reference document may continue to enjoy credits for an agreed list of training, testing and checking manoeuvres, provided they maintain their performance in accordance with any validation, functions and subjective tests which have been previously established or a list of tests selected from ACJ N°1 to JAR-FSTD H.030 by agreement with the Authority. Again these tests should relate to the list of manoeuvres permitted under the original national qualification or approval document. 3.2 The award of credits to an FNPT user should be at the discretion of the Authority. Current FNPT users may retain the credits granted under their previous national criteria.

text: INTENTIONALLY LEFT BLANK

text: 2009-11-01 2-C-145 JAR-FSTD H

text: Bilaga 2

text: ACJ to FSTD H.045 (explanatory material) New Aircraft FFS/FTD Qualification – Additional Information See JAR–FSTD H.045

text: 1 It is usual that aircraft manufacturer’s approved final data for performance, handling qualities, systems or avionics will not be available until well after a new or derivative aircraft has entered service. It is often necessary to begin flight crew training and certification several months prior to the entry of the first aircraft into service and consequently it may be necessary to use aircraft manufacturer-provided preliminary data for interim qualification of FSTDs. 2 In recognition of the sequence of events that should occur and the time required for final data to become available, the Authority may accept certain partially validated preliminary aircraft and systems data, and early release (‘red label’) avionics in order to permit the necessary programme schedule for training, certification and service introduction. 3 FSTD operators seeking qualification based on preliminary data should, however, consult the Authority as soon as it is known that special arrangements will be necessary or as soon as it is clear that the preliminary data will need to be used for FSTD qualification. Aircraft and FSTD manufacturers should also be made aware of the needs and be agreed party to the data plan and FSTD qualification plan. The plan should include periodic meetings to keep the interested parties informed of project status. 4 The precise procedure to be followed to gain Authority acceptance of preliminary data will vary from case to case and between aircraft manufacturers. Each aircraft manufacturer’s new aircraft development and test programme is designed to suit the needs of the particular project and may not contain the same events or sequence of events as another manufacturer’s programme or even the same manufacturer’s programme for a different aircraft. Hence, there cannot be a prescribed invariable procedure for acceptance of preliminary data, but instead there should be a statement describing the final sequence of events, data sources, and validation procedures agreed by the FSTD operator, the aircraft manufacturer, the FSTD manufacturer, and the Authority.

text: NOTE: A description of aircraft manufacturer-provided data needed for flight simulator modelling and validation is to be found in the IATA Document ‘Flight Simulator Design and Performance Data Requirements’ – (Edition 6 2000 or as amended). 5 There should be assurance that the preliminary data are the manufacturer’s best representation of the aircraft and reasonable certainty that final data will not deviate to a large degree from these preliminary, but refined, estimates. Data derived from these predictive or preliminary techniques should be validated by available sources including, at least, the following: (a) Manufacturer’s engineering report. Such report will explain the predictive method used and illustrating past success of the method on similar projects. For example, the manufacturer could show the application of the method to an earlier aircraft model or predict the characteristics of an earlier model and compare the results to final data for that model. (b) Early flight tests results. Such data will often be derived from aircraft certification tests, and should be used to maximum advantage for early FSTD validation. Certain critical tests, which would normally be done early in the aircraft certification programme, should be included to validate essential pilot training and certification manoeuvres. These include cases in which a pilot is expected to cope with an aircraft failure mode including engine failures. The early data available will, however, depend on the aircraft manufacturer’s flight test programme design and may not be the same in each case. However it is expected that the flight test programme of the aircraft manufacturer include provisions for generation of very early flight tests results for FSTD validation.

text: 6 The use of preliminary data is not indefinite. The aircraft manufacturer’s final data should be available within 6 months after aircraft first ‘service entry’ or as agreed by the Authority, the FSTD operator and the aircraft manufacturer, but usually not later than 1 year. In applying for an interim qualification, using preliminary data, the FSTD operator and the Authority should agree upon the update programme. This will normally specify that the final data update will be installed in the FSTD within a period of 6 months following the final data release unless special conditions exist and a different schedule agreed. The FSTD performance and handling validation would then be based on data derived from flight test. Initial aircraft systems data should be updated after

text: JAR-FSTD H 2-C-146 2009-11-01

text: Bilaga 2

text: ACJ to FSTD H.045 (continued)

text: engineering tests. Final aircraft systems data should also be used for FSTD programming and validation. 7 FSTD avionics should stay essentially in step with aircraft avionics (hardware & software) updates. The permitted time lapse between aircraft and FSTD updates is not a fixed time but should be minimal. It may depend on the magnitude of the update and whether the QTG and pilot training and certification is affected. Permitted differences in aircraft and FSTD avionics versions and the resulting effects on FSTD qualification should be agreed between the FSTD operator and the Authority. Consultation with the FSTD manufacturer is desirable throughout the agreement of the qualification process. 8 The following describes an example of the design data and sources which might be used in the development of an interim qualification plan. (a) The plan should consist of the development of a QTG based upon a mix of flight test and engineering simulation data. For data collected from specific aircraft flight tests or other flights the required designed model and data changes necessary to support an acceptable Proof of Match (POM) should be generated by the aircraft manufacturer. (b) In order that the two sets of data are properly validated, the aircraft manufacturer should compare their simulation model responses against the flight test data, when driven by the same control inputs and subjected to the same atmospheric conditions as were recorded in the flight test. The model responses should result from a simulation where the following systems are run in an integrated fashion and are consistent with the design data released to the FSTD manufacturer: (1) propulsion (2) aerodynamics (3) mass properties (4) flight controls (5) stability augmentation (6) brakes and landing gear. 9 For the qualification of FSTD of new aircraft types, it may be beneficial that the services of a suitably qualified test pilot are used for the purpose of assessing handling qualities and performance evaluation. NOTE: The Proof of Match should meet the relevant ACJ No. 1 to JAR-FSTD H.030 tolerances.

text: 2009-11-01 2-C-147 JAR-FSTD H

text: SECTION 2

text: Bilaga 2

text: INTENTIONALLY LEFT BLANK JAR-FSTD H 2-C-148 2009-11-01