RSLFAC_CH-47F FTD SPEC_DRAFT.pdf

PRF-PT-00908

28 Oct 2026

Rev. 0.1

CUI

CUI

Performance Specification for the

Royal Saudi Land Forces Aviation Corps

CH-47F Block I

Flight Training Device

X_______________________

SYSTEMS ENGINEER

X_______________________

CHIEF ENGINEER

U.S. Army Capability Program Executive Simulation, Training, Test & Threat (CPE

ST3)

11221 Science Drive Orlando, FL 32826-3224 DRAFT

Rev. 0.1

CUI

I

CUI

Revision History

Date Version Revision Description 10/28/2026 0.1 Initial Draft

DRAFT

Rev. 0.1

CUI

II

Table of Contents

Section Title Page

1. SCOPE

1.1 Purpose

1.2 System Description

2. APPLICABLE DOCUMENTS

2.1 Government Documents

3. REQUIREMENTS

3.1 General Requirements

3.1.1 System Fidelity

3.1.2 Operational States

3.1.3 Training Modes

3.1.4 Interoperability

3.2 Cockpit and Crew Environment

3.2.1 Crew Stations

3.2.2 Controls, Panels, and Instruments

3.2.3 Lighting Systems

3.3 Avionics Systems

3.3.1 Common Avionics Architecture System (CAAS)

3.3.2 Multi-Function Displays (MFDs)

3.3.3 Control Display Units (CDUs)

3.3.4 Multi-Function Knobs (MFKs)

3.3.5 General Purpose Processor Units (GPPUs)

3.3.6 Data Concentrator Units (DCUs)

3.3.7 Voice Warning System (VWS)

3.3.8 Data Transfer Unit (DTU)

3.3.9 Emission Control (EMCON)

3.3.10 Multi-Function Control Units (MFCUs)

3.3.11 Communication Systems

3.3.12 Navigation Systems

3.3.13 Aircraft Survivability Equipment (ASE)

3.3.14 Weather Detection System

3.4 Engine and Powertrain Systems

3.4.1 Engines

3.4.2 Full Authority Digital Electronic Control (FADEC)

3.4.3 FADEC Control Panel

3.4.4 Power and Temperature Indications (PTIT/Torque)

3.4.5 Power Train System

3.4.6 Rotor System

3.5 Fuel System

III

3.5.1 Extended Range Fuel System (ERFS)

3.5.2 Mass and Center of Gravity Effects

3.5.3 Avionics Integration

3.6 Hydraulic Systems

3.6.1 System Integration and Crew Alerting

3.7 Flight Control System

3.7.1 DAFCS and System Integration

3.8 Electrical System

3.8.1 System Integration and Crew Alerting

3.8.2 Clean Power

3.9 Utility and Miscellaneous Systems

3.9.1 Engine Air Particle Separator (EAPS)

3.9.2 Anti-icing System

3.9.3 Auxiliary Power Unit (APU)

3.9.4 Environmental Control System

3.9.4.1 Facility-Independent Cooling

3.9.5 Wheel Brake System

3.9.6 Maintenance Panel

3.10 Emergency Procedures

3.11 Mission-Related Systems

3.12 Sensory Cueing System

3.12.1 Control Loading System

3.12.2 Vibration and Tactile Cueing System

3.12.3 Aural Cue System

3.13 Visual System

3.13.1 Visual Database

3.13.1.1 Geographic Coverage and Fidelity

3.13.1.2 High Fidelity Zones

3.13.1.2.1 Designated Training Airfields and Fidelity Categories

3.13.1.2.2 Airfield and Airport Environment Content

3.13.1.3 Tactical Features and Obstacles

3.13.1.4 Degraded Visual Environment (DVE)

3.13.1.5 Dynamic Effects

3.13.1.6 Database Correlation

3.13.1.7 Moving Models and Entity Database

3.13.2 Display System Performance

3.13.2.1 Field of View (FOV)

3.13.2.2 Eye Point Selection

3.13.2.3 Resolution, Brightness and Image Quality

3.13.2.4 Dipvergence and Collimation

3.13.2.5 Rendering Performance

IV

3.13.2.6 Night Vision Device (NVD) Compatibility

3.14 Instructor Operator Station (IOS)

3.14.1 Control and States

3.14.2 Crew Monitoring and Display Mirroring

3.14.3 Scenario and Environment Management

3.14.4 Malfunctions and Fault Injection

3.14.5 Communications

3.14.6 Live Video and AAR Integration

3.14.7 Remote Observation Capability

3.14.8 Safety and Emergency Functions

3.14.9 Performance and Availability

3.14.10 Access Control and Audit

3.15 After Action Review (AAR)

3.15.1 Recorded Data

3.15.2 Time Base and Synchronization

3.15.3 Playback

3.15.4 Instructor Tools

3.15.5 Data Quality and Performance

3.15.6 Data Management and Security

3.16 Reliability, Availability, and Maintainability (RAM)

3.16.1 Availability

3.16.2 Reliability

3.16.3 Maintainability

3.17 System Safety

3.17.1 Emergency Stop (E-Stop)

3.17.2 Electrical and Mechanical Safety

3.17.3 Material Flammability

3.17.4 Safe Ingress and Egress

3.18 Cybersecurity

3.18.1 Authentication and Authorization

3.18.2 System Hardening

3.18.3 Audit and Logging

3.18.4 Malicious Code Protection

3.18.5 Data Protection

3.18.6 Network Isolation and Boundary Protection

3.19 Architectural Commonality for Future Interoperability

3.19.1 Strategic Intent

3.19.2 Technical Implementation

4. VERIFICATION

4.1 Methods of Verification

4.2 Verification Milestones

V

4.3 Inspections and Test

4.3.1 Visual Inspections

4.3.2 Computer System Tests

4.3.3 IOS Tests

4.3.4 Visual System Test and Verification

4.3.5 Structural Tests

4.3.6 Electrical Tests

4.3.7 Grounding and Grounding Systems Test

4.3.8 Vehicle Dynamics Test

4.3.9 Tactical Systems Tests

4.3.10 Operation and Mission Tests

4.3.11 Training Scenarios

4.3.12 Mission Tests

4.3.13 Stress Tests

4.3.14 Free Play Tests

4.3.15 Threat Environment Tests

4.3.16 Malfunctions Test

4.3.17 Database Correlation Tests

4.3.18 Interoperability Tests

4.3.19 Product Assurance Tests

4.3.20 Thermal Survey

4.3.21 EMR Tests

4.3.22 ESD Tests

4.3.23 Human Systems Integration Engineering Compliance Tests

4.4 Nonfunctional Examinations

APPENDIX SECTION ................................................................................................... 30DRAFT

Performance Specification for the Royal Saudi Land Forces Aviation Corps CH-47F Block 1

Flight Training Device

1. SCOPE

This performance specification establishes the technical, functional, interoperability, fidelity, environmental, cybersecurity, and verification requirements for the CH-47F Block I Flight Training Device (FTD) being procured for the Royal Saudi Land Forces Aviation Corps (RSLFAC) under the Foreign Military Sales (FMS) program.

This specification defines the system-level performance, subsystem requirements, interfaces, fidelity criteria, operational capabilities, training functions, supportability requirements, and verification methods required to design, develop, integrate, test, deliver, install, and sustain the FTD at Al-Qassim, Kingdom of Saudi Arabia.

The FTD shall achieve a fidelity and performance standard equivalent to a Federal Aviation Administration (FAA) FTD Level 7 device with respect to cueing, flight dynamics, system responsiveness, and avionics integration; however, all implementations shall be based solely on the CH‑47F Block I military aircraft configuration and shall not require FAA qualification.

The CH-47F Block I FTD shall provide a high-fidelity simulation of the RSLFAC-configured CH-47F Block I aircraft, including its cockpit layout, avionics suite, flight controls, aircraft systems, and flight performance characteristics. The FTD shall deliver a level of functional fidelity, responsiveness, and system integration comparable to a FAA FTD Level 7, while remaining fully tailored to the military CH-47F Block I configuration and training requirements. The FTD shall feature a two-seat cockpit consisting of the pilot and copilot crew stations only, with no jump seat or observer seat.

The system shall incorporate high-resolution visual displays, precise control loading, integrated vibration and tactile cueing, and accurate flight, systems, and environmental models to support qualification, continuation, tactical, and mission-oriented training for CH-47F pilots and copilots.

2. APPLICABLE DOCUMENTS

The following documents form a part of this specification to the extent specified herein.

In the event of a conflict between documents referenced herein and the contents of this specification, the contents of this specification take precedence. Nothing in this specification, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

SOW-2025-026 Statement of Work for CH-47F and UH-60M

Flight Training Devices PRF-PT-00910 RSLFAC Interoperability Performance

Specification

3. REQUIREMENTS

The FTD shall replicate the form, fit, function, and training-relevant performance of the RSLFAC CH-47F Block I aircraft. The FTD shall provide a level of simulation fidelity, responsiveness, cue integration, and system complexity comparable to a FAA FTD Level 7, tailored to the military CH-47F Block I configuration.

3.1.1 System Fidelity

The FTD shall model the CH-47F Block I aircraft flight dynamics, propulsion system performance, powertrain behavior, and all aircraft systems required to support all pilot and copilot training tasks, and shall accurately reproduce aircraft performance and characteristics through all phases of flight. The FTD shall simulate normal, abnormal, and emergency operating conditions in accordance with applicable CH-47F operational manuals and training requirements.

3.1.2 Operational States

The FTD shall provide operational states that include initialization, run, freeze, reposition, bookmark save/restore, reset, and shutdown. Each operational state shall be fully controlled through the Instructor Operator Station (IOS) or, when operating in a networked environment, through a designated central or master IOS. The FTD shall transition between states without introducing unsafe conditions or simulator anomalies.

3.1.3 Training Modes

The FTD shall support initial and recurring training for pilot and copilot personnel. The FTD shall provide training capability for all pilot and copilot training tasks required for the RSLFAC CH-47F Block I configuration. The FTD shall support individual and two-pilot crew training, scenario-based mission execution, instrument flight training, tactical flight tasks, degraded visual environment training, and night vision goggle (NVG) training. The FTD shall support training in normal, abnormal, and emergency conditions.

The FTD shall support networked training in which the device may be connected with other compatible simulators to perform multi-ship mission training, in accordance with the requirements defined in PRF-PT-00910, the Saudi Arabia RSLFAC Interoperability

Performance Specification. The required training tasks supported by the FTD are identified in Appendix B, Task List.

3.1.4 Interoperability

The FTD shall possess the architecture required to exchange simulation data in a networked environment with other training devices. The FTD shall be fully compliant with the requirements, protocols, and data exchange formats defined in PRF-PT-00910, the RSLFAC Interoperability Performance Specification.

Verification of CH-47F FTD compliance with PRF-PT-00910 shall be conducted in accordance with the phased interoperability verification approach defined in SOW-2025- 026, including representative-environment verification during GAT and end-to-end operational verification during OSAT at Al Qassim.

The FTD shall provide a high-fidelity physical replication of the CH-47F Block I cockpit environment. All controls, panels, and furnishings within the crew stations shall replicate the form, fit, function, and location of their aircraft counterparts to the extent necessary to support all specified training tasks.

3.2.1 Crew Stations

The FTD cockpit shall provide two crew stations: a pilot station and a copilot station.

Each station shall replicate the corresponding controls, displays, switches, indicators, and human-machine interfaces present in the CH-47F Block I aircraft.

3.2.2 Controls, Panels, and Instruments

The FTD shall replicate all flight controls, avionics controls, system control panels, instruments, indicators, circuit breakers, and annunciators required for CH-47F Block I pilot and copilot operation. All replicated controls and panels shall be located and functionally integrated in accordance with the CH-47F Block I aircraft design layout.

Each control and indicator shall stimulate or interact with the underlying aircraft system models as applicable.

3.2.3 Lighting Systems

The FTD shall simulate cockpit lighting systems required for CH-47F Block I pilot and copilot operations. The simulation shall include control behaviors, intensity ranges, dimming characteristics, and integration with Night Vision Goggle (NVG)-compatible illumination. Lighting effects shall interact with the visual system to provide correct brightness and visibility characteristics. The cockpit shall be NVG compatible and shall support pilot and copilot training operations in aided and unaided night conditions.

The FTD shall implement the CH-47F Block I Common Avionics Architecture System (CAAS) consistent with the RSLFAC configuration. CAAS functionality, update rates, color schemes, symbology, control logic, data flow, and display behavior shall match the design-basis aircraft.

The FTD shall be delivered configured to the CAAS 9.4 software baseline. All CAAS-related functions and avionics subsystem behaviors described in this section shall reflect CH-47F Block I CAAS 9.4 functionality consistent with the RSLFAC configuration.

The FTD shall provide functional replications of the CAAS subsystems, including Multi-Function Displays (MFDs), Control Display Units (CDUs), General Purpose Processor Units (GPPUs), Data Concentrator Units (DCUs), Voice Warning System (VWS), Data Transfer Unit (DTU), and all associated CAAS interfaces required for pilot and copilot operation.

3.3.1 Common Avionics Architecture System (CAAS)

The FTD shall ensure that all CAAS functions respond to simulated aircraft conditions, system failures, environmental states, navigation inputs, and pilot/copilot control selections in accordance with the aircraft’s operational behavior.

3.3.2 Multi-Function Displays (MFDs)

The FTD shall provide MFDs that replicate the display formats, symbology, color usage, operational modes, page families, declutter options, overlays, data content, tactile buttoning logic, and timing behavior of the CH-47F Block I aircraft. Each MFD shall respond to crew inputs with update rates, animation behavior, and navigation between display pages consistent with the aircraft.

3.3.3 Control Display Units (CDUs)

The FTD shall replicate the CH-47F Block I Control Display Units, including page layouts, navigation logic, data entry, alphanumeric input, menu structures, cursor behavior, initialization sequences, and system configuration functions. CDU inputs shall affect the simulated aircraft systems and CAAS subsystems in accordance with design-basis functionality.

3.3.4 Multi-Function Knobs (MFKs)

The FTD shall provide MFKs identical in form, behavior, detent feel, and input response to those of the CH-47F Block I aircraft. MFK rotational and push-button inputs shall control display and CAAS functions consistent with the aircraft.

3.3.5 General Purpose Processor Units (GPPUs)

The FTD shall simulate or stimulate GPPU functionality such that CAAS behavior, system processing, data routing, and avionics mode transitions reflect design-basis aircraft performance. GPPU effects on display rendering, data validity, and system fault behavior shall be represented.

3.3.6 Data Concentrator Units (DCUs)

The FTD shall replicate DCU functions required for pilot/copilot tasks, including the routing of sensor data, aircraft system data, caution/advisory signals, and discrete inputs to avionics displays and warning systems. DCU behavior shall reflect CH‑47F Block I timing, filtering, and message prioritization characteristics.

3.3.7 Voice Warning System (VWS)

The FTD shall implement the CH-47F Block I VWS. The system shall reproduce aircraft-appropriate tones, alerts, synthesized voice messages, priority logic, inhibit rules, mute/reset behavior, and integration with CAAS caution and advisory messages.

3.3.8 Data Transfer Unit (DTU)

The FTD shall simulate DTU functions required to support data loading, mission data management, and any CH-47F Block I video record or playback behaviors applicable to RSLFAC configuration. DTU interactions shall follow aircraft sequencing, timing, and crew interface actions.

3.3.9 Emission Control (EMCON)

The FTD shall simulate CH-47F Block I EMCON functionality to the extent required for pilot/copilot task training. EMCON selections shall affect radios, navigation systems, and transmission behavior consistent with the aircraft configuration and RSLFAC mission requirements.

3.3.10 Multi-Function Control Units (MFCUs)

Where applicable to the RSLFAC configuration, the FTD shall simulate MFCU functionality consistent with the design-basis aircraft. All MFCU inputs, operational modes, annunciations, and effects on mission or avionics systems shall be replicated.

3.3.11 Communication Systems

The FTD shall simulate CH‑47F Block I communication systems relevant to pilot/copilot operation, including voice communication, radio frequency behaviors required for training, Intercommunication System (ICS) operation, and audio mixing.

The simulation shall replicate the specific human-machine interface (HMI) and performance characteristics of the RSLFAC-configured radios, including but not limited to the AN/ARC-231(V)(C) SATCOM/VHF/UHF radio and the AN/ARC-220(V)2 HF radio.

Communication system simulation shall support training tasks requiring frequency tuning, mode selection, volume control, communication discipline, and integration with the instructor’s communication interface. The simulation shall reproduce communication failures and degraded communication conditions consistent with aircraft operation.

3.3.12 Navigation Systems

The FTD shall simulate the CH-47F Block I navigation systems required for pilot and copilot training, including GPS/INS functionality, VOR/ILS, ADF, TACAN, radar altimeter behavior, and CAAS navigation pages. The simulation shall replicate the specific HMI and performance of installed units, such as the AN/ARN-149(V)1 (ADF), AN/ARN- 153(V) (TACAN), and AN/APN-209 (Radar Altimeter). Navigation sensors, computations, and failure behaviors shall interact with the visual system, flight model, and avionics systems consistent with the aircraft. Position, velocity, altitude, heading, and attitude data shall be computed and updated at rates sufficient to support accurate navigation display and guidance behavior.

3.3.13 Aircraft Survivability Equipment (ASE)

The FTD shall simulate the aircraft survivability equipment installed on the RSLFAC CH- 47F Block I configuration to the extent that pilot/copilot interaction is required. The simulation shall replicate the pilot/copilot interfaces, controls, displays, and alerts for the installed ASE suite, including the Radar Signal Detecting Set and the Common Missile Warning System (CMWS). The simulation shall also replicate the functionality of the AN/APX-123A(V) IFF Transponder. The simulation shall reproduce panel interfaces, caution/advisory messages, mode selections, system states, and crew indications relevant to ASE operation. Any simulated threat detection or countermeasure deployment shall provide pilot relevant cues within the limitations of an unclassified training environment.

3.3.14 Weather Detection System

Where applicable to the RSLFAC configuration, the FTD shall simulate the Stormscope (e.g., WX-500) or equivalent weather detection system. The simulation shall replicate the system's pilot/copilot interface, its integration with the MFDs, and its display of detected weather phenomena in a manner consistent with the aircraft's avionics.

The FTD shall simulate the complete CH-47F Block I propulsion and power transmission system, from engine response to pilot inputs to the delivery of torque through the powertrain to the rotors. The simulation shall represent the dynamic interactions between the engines, transmissions, and rotor system under all operating conditions.

3.4.1 Engines

The FTD shall simulate the performance, operation, and dynamic behavior of the T55-GA-714A engines installed on the CH-47F Block I aircraft. The engine model shall represent engine response to pilot control inputs, environmental conditions, system failures, fuel states, and aircraft loading conditions.

The FTD shall reproduce engine start, shutdown, transient response characteristics, torque-producing behavior, and engine-to-rotor coupling in accordance with available engineering data and flight test information.

3.4.2 Full Authority Digital Electronic Control (FADEC)

The FTD shall simulate the CH-47F Block I Full Authority Digital Electronic Control (FADEC) system. The simulated FADEC shall manage engine operation, fuel flow scheduling, governing, sensor interpretation, performance limiting, and torque sharing behavior consistent with aircraft performance. FADEC mode transitions, logic states, caution/advisory triggers, and failure behaviors shall be represented in accordance with CH-47F Block I aircraft characteristics.

3.4.3 FADEC Control Panel

The FTD shall replicate the FADEC control panel and shall ensure that all FADEC-related switches, selectors, annunciations, and control inputs affect the engine and powertrain simulation in a manner consistent with the aircraft. The FADEC control panel interface shall respond with correct sequencing, interlocks, and feedback.

3.4.4 Power and Temperature Indications (PTIT/Torque)

The FTD shall simulate the Power Turbine Inlet Temperature (PTIT) and engine torque indicators to support pilot and copilot monitoring, engine management, and emergency procedures. The simulated PTIT and torque values shall reflect engine operating state, environmental conditions, and aircraft system interactions consistent with the CH-47F Block I aircraft.

3.4.5 Power Train System

The FTD shall simulate the CH-47F Block I power train system, including the forward and aft transmissions, combining transmission, driveshafts, clutches, lubrication systems, chip detection, torque splitting, and related caution and advisory logic. The power train simulation shall represent system response to changes in torque demand, rotor loading, engine power production, aerodynamic state, and failure conditions.

Transmission temperature, pressure, and lubrication states shall be modeled in a manner sufficient to support the execution of all pilot and copilot procedures, including emergency procedures involving transmission malfunctions. Transmission and drive system failures shall exhibit appropriate effects on aircraft performance, rotor behavior, and system indications.

3.4.6 Rotor System

The FTD shall simulate the CH‑47F Block I rotor system, including dual rotor aerodynamic behavior, rotor‑to‑rotor interaction, phasing, blade dynamics, flapping response, induced flow, translational lift, vortex ring state, and low‑speed/high‑power conditions. The rotor system simulation shall accurately reflect changes in rotor speed (Nr), blade loading, and rotor aerodynamic performance resulting from pilot control inputs, aircraft maneuvers, environmental conditions, and system failures. The simulated rotor system shall interact with the visual system to provide correct visual references, including blade appearance and motion blur appropriate to the aircraft.

The FTD shall simulate the CH-47F Block I fuel system, including fuel storage, consumption, transfer operations, pressure dynamics, fuel quantity indication, crossfeed behavior, and associated caution/advisory messages. The fuel system model shall support training in normal and emergency procedures, including transfer malfunctions, low fuel conditions, pump/valve failures, and fuel imbalance effects.

3.5.1 Extended Range Fuel System (ERFS)

Where applicable to the RSLFAC configuration, the FTD shall simulate the Extended Range Fuel System (ERFS). The simulation shall include pilot/copilot procedures for managing fuel transfer from the ERFS tanks, the integration of ERFS quantity indications into the CAAS fuel pages, and the corresponding real-time effects on the aircraft's mass and center-of-gravity.

3.5.2 Mass and Center of Gravity Effects

Fuel system behavior shall adjust the simulated aircraft's mass and center-of-gravity (CG) in real-time. The flight dynamics model shall respond correctly to these changes in mass properties resulting from fuel consumption, transfer, and jettison.

3.5.3 Avionics Integration

The fuel system model shall be fully integrated with the CAAS, providing accurate data to all relevant MFD fuel and status pages. All fuel-related cautions and advisories shall be displayed in accordance with the design-basis aircraft.

The FTD shall simulate the CH-47F Block I No. 1 and No. 2 Flight Control Hydraulic Systems and the Utility Hydraulic System. The simulation shall include fluid pressure behavior, temperature effects, quantity monitoring, actuator response, pump performance, leak conditions, and system degradation consistent with the aircraft.

3.6.1 System Integration and Crew Alerting

The hydraulic system model shall be fully integrated with the flight controls, DAFCS, and control loading system, ensuring that the loss or degradation of hydraulic pressure results in corresponding changes to flight control forces and aircraft handling characteristics. All associated indications, cautions, and advisories shall be presented on the CAAS displays in a manner consistent with CH-47F Block I alerting logic.

The FTD shall simulate the CH-47F Block I mechanical and assisted flight control system, including the cyclic, collective (thrust control lever), and directional control pedals, as well as all associated linkages, mixing units, and actuators. The simulated flight control system shall reproduce the steady-state response, control sensitivity, breakout forces, rate damping, and cross-coupling characteristics consistent with CH-47F Block I flight dynamics.

3.7.1 DAFCS and System Integration

The simulation shall include the Digital Advanced Flight Control System (DAFCS) and its interfaces with the primary flight controls. All DAFCS modes, mode transitions, sensor dependencies, and failure behaviors shall be simulated in accordance with the aircraft’s operational characteristics. All flight control inputs shall be processed at a rate sufficient to ensure accurate and stable aircraft response and shall interface correctly with both the control loading system and the aircraft system models.

The FTD shall simulate the CH-47F Block I electrical system, including all AC and DC buses, generator behavior, battery operation, power transfer logic, circuit breaker behavior, system loading effects, and electrical fault scenarios.

3.8.1 System Integration and Crew Alerting

The electrical system model shall be fully integrated with all other aircraft systems.

Electrical system state changes shall affect avionics availability, system initialization sequences, and mode transitions consistent with the aircraft. All associated electrical system indications, cautions, and advisories shall replicate aircraft behavior and be presented on the CAAS displays.

3.8.2 Clean Power

The FTD shall include a contractor-provided clean power solution for all trainer-unique and sensitive equipment. The contractor shall furnish and integrate the power conditioning, filtering, grounding, isolation, surge suppression, and associated protective features necessary to protect the FTD from voltage fluctuations, sags, surges, spikes, harmonics, electrical noise, grounding deficiencies, and other power anomalies that could cause equipment damage, erratic operation, data loss, uncommanded resets, performance degradation, or loss of training availability.

The FTD shall simulate the CH-47F Block I utility and miscellaneous systems required for pilot and copilot training. Each utility system simulation shall replicate normal and emergency operational behavior and shall produce indications, alerts, and performance effects consistent with CH-47F Block I operational guidance.

3.9.1 Engine Air Particle Separator (EAPS)

The FTD shall simulate the Engine Air Particle Separator (EAPS) system. The simulation shall include pilot/copilot controls for system activation and shall model the corresponding effect on engine performance (e.g., torque reduction) and CAAS indications. The simulation shall support all normal and emergency procedures associated with EAPS operation.

3.9.2 Anti-icing System

The FTD shall simulate the aircraft’s anti‑icing functions. The simulation shall include the effects of system activation on engine performance and shall generate the appropriate crew alerts and CAAS indications.

3.9.3 Auxiliary Power Unit (APU)

The FTD shall simulate the APU, including start and stop sequences, operational limitations, and its function as a power source for the electrical and pneumatic systems.

All associated controls and indications in the cockpit shall be replicated.

3.9.4 Environmental Control System

The FTD shall simulate the aircraft's environmental control system for cockpit heating and cooling. The simulation shall replicate the pilot/copilot controls and their function in accordance with the aircraft.

3.9.4.1 Facility-Independent Cooling

The FTD shall include a dedicated air-conditioning or equipment cooling solution independent of the facility/building HVAC system. The contractor shall propose, furnish, and integrate this solution such that the FTD remains operational and available for training when the building air-conditioning system is unavailable, degraded, or insufficient due to site environmental conditions. The dedicated cooling solution shall maintain required equipment temperatures and prevent overheating, performance degradation, automatic shutdown, or loss of training capability.

3.9.5 Wheel Brake System

The FTD shall simulate the wheel brake system, including the parking brake function.

The simulation shall replicate the relevant cockpit controls and their effect during ground operations.

3.9.6 Maintenance Panel

The FTD shall simulate the effects of maintenance panel interactions that are visible to the flight crew. Any maintenance panel function that alters a cockpit indication, system status, or operational mode available to the pilot shall be modeled and controllable from the IOS.

The FTD shall support the execution of all CH-47F Block I pilot and copilot emergency procedures documented in the applicable flight manuals and required for training. The simulation shall provide system states, indications, aircraft responses, and environmental interactions necessary to accurately replicate the conditions and cues associated with each procedure as defined in the applicable CH-47F operator’s manual.

This shall include, but not be limited to, the complete simulation of the Fire Detection and Extinguishing System. The FTD shall replicate all associated cockpit fire warning lights, audio tones, fire suppression T-handle controls, and the logic for agent discharge to the engines or APU. The resulting system effects and indications shall be consistent with the aircraft. Each emergency procedure shall produce cockpit indications, aircraft performance effects, flight control feedback, CAAS alerts, caution and advisory messages, and system behaviors consistent with the design-basis aircraft.

The FTD shall simulate all mission‑related aircraft systems that require pilot or copilot interaction in the CH‑47F Block I aircraft. The simulation shall include the systems’ operational modes, functional interfaces with avionics and displays, and resulting effects on aircraft performance and situational awareness. Where systems such as the External Rescue Hoist or Fast Rope Insertion and Extraction System (FRIES) are part of the RSLFAC training requirement, the FTD shall support the pilot/copilot tasks associated with these missions. This includes simulating the flight dynamics of precision hover, the effects of external loads on aircraft performance and handling and providing the instructor with the IOS tools to control mission events and provide verbal cues on behalf of other crew members (e.g., hoist operator, loadmaster). Mission‑related system behavior shall be integrated into the flight model, visual system, and avionics as required to support RSLFAC training tasks.

The FTD shall integrate aural, visual, and tactile cueing systems to support accurate pilot perception of aircraft state. The cueing systems shall provide synchronized and consistent responses to crew control inputs, aircraft system states, and environmental conditions modeled within the simulation. The end-to-end latency and synchronization between cueing systems shall be sufficient to prevent sensory mismatch or negative training.

3.12.1 Control Loading System

The FTD shall include a control loading system that reproduces the force‑feel, mechanical characteristics, and dynamic behavior of the CH‑47F Block I primary flight controls. The system shall apply forces and displacements to the cyclic, thrust control lever, and directional control pedals that correspond to aerodynamic loading, hydraulic system conditions, trim system states, flight regimes, and aircraft system malfunctions.

The control loading system shall operate within safe mechanical and electrical limits and transition to a safe, neutral state upon activation of the emergency stop (E-Stop).

3.12.2 Vibration and Tactile Cueing System

The FTD shall provide a vibration and tactile cueing system that reproduces characteristic CH‑47F Block I rotor, drivetrain, and aerodynamic signatures. The system shall generate seat‑level and cockpit‑level vibrations corresponding to rotor speed, power settings, aerodynamic loading, turbulence, and ground contact. All vibration and tactile cues shall operate in synchronization with the visual and aural cueing systems.

The vibration system shall transition to a safe state upon activation of the E-Stop.

3.12.3 Aural Cue System

The FTD shall provide a high-fidelity aural cueing environment that accurately reproduces the sounds of the CH-47F cockpit. The simulation shall include, at a minimum: engine and transmission sounds, rotor noise including blade slap, aerodynamic cues, landing gear and ground contact noises, and sounds for switches, relays, and the APU. All sounds shall be dynamic and respond appropriately to changes in aircraft state, power settings, and air speed. The aural cue system shall also generate all tones and voice messages from the Voice Warning System (VWS) and provide for the mixing of all communication system audio.

The Flight Training Device (FTD) shall provide a real-time, out-the-window (OTW) visual system—comprising the Image Generator (IG), display system, and visual database— that delivers an immersive, high-fidelity synthetic environment appropriate for CH-47F

Block I pilot and copilot training. The visual system shall support individual and collective flight training tasks, instrument procedures, low-level terrain flight, tactical mission training, and mission rehearsal across continuous time-of-day transitions (dawn, bright day, dusk, and night) and adverse weather conditions. The visual system shall provide a high-fidelity Night Vision Device (NVD) training capability for both crew stations while simultaneously maintaining a correctly rendered, color-balanced scene for the unaided eye.

3.13.1 Visual Database

The FTD shall include a comprehensive, real-time synthetic environment visual database tailored to CH-47F Block I operational requirements. Because no Government Furnished Information (GFI) geospatial or aeronautical source data will be provided, the Contractor shall be solely responsible for procuring, licensing, and processing all commercial satellite/aerial ortho-imagery, digital terrain elevation models (DEM), hydrographic data, vertical obstruction data, and current aeronautical charting publications required to construct and validate the database. All commercial source data and derived databases shall be delivered with perpetual, non-expiring, royalty-free usage rights for the Government and End User. The level of detail (LOD) across the database shall be balanced and optimized to match IG capabilities, preventing frame-rate degradation, polygon popping, or texture swimming during all required training tasks.

3.13.1.1 Geographic Coverage and Fidelity

The visual database shall encompass a continuous, seamless geographic gaming area of not less than 1,000 by 1,000 nautical miles (NM), centered on the Al Qassim region of the Kingdom of Saudi Arabia, ensuring continuous regional coverage encompassing all designated training airfields. Throughout the entire base gaming area, the terrain elevation model shall have a post spacing of 30 meters or less (DTED Level 2 equivalent or better), and the base satellite/aerial ortho-imagery resolution shall be 1.0 meter-per-pixel or better. The visual database shall be geo-specific and shall include accurate terrain elevation, hydrographic features, transportation networks, urban areas, and vertical cultural features necessary to support low-level navigation, pilotage, instrument procedures, and tactical flight training.

3.13.1.2 High Fidelity Zones

Within a 15-NM radius of all Government-designated High-Fidelity Airfields, and within a 5-NM radius of designated tactical training areas, the database fidelity shall be enhanced. Within these high-fidelity zones, the terrain elevation post spacing shall be 10 meters or less, with localized sub-meter terrain mesh modeling at runways, helipads, and pinnacle landing zones; the ground imagery resolution shall be 0.5 meter-per-pixel or better.

3.13.1.2.1 Designated Training Airfields and Fidelity Categories The visual database shall include geo-specific 3D representations of Government-designated Saudi Arabian training airfields, airports, heliports, and associated landing areas necessary to support CH-47F training tasks. At a minimum, the visual database shall include the following designated airfields and airports, represented at the fidelity category specified below:

High-fidelity airfields (15-NM High-Res Zone + Custom 3D Models:

• King Khalid Military City (KKMC)

• Al Qassim / Prince Nayef bin Abdulaziz International Airport (OEGQ)

• Tabuk

• Riyadh Air Base

• Dammam

• Khamis Mushait

• Abha

Lower-fidelity airfields (Standard Geo-Specific Airfield Layout):

• Hail

• Jubail

• Taif

• Bisha

• JizanNajran

• Al Jiwa

• Qaisumah

The database shall also include Government-designated heliports, hospital helipads, Forward Arming and Refueling Points (FARPs), Confined Area Landing (CAL) zones, slope landing sites, and pinnacle landing zones. Final coordinates, model extents, and fidelity assignments for each location shall be in accordance with Appendix A, Designated Visual Database Locations and Model Requirements.

3.13.1.2.2 Airfield and Airport Environment Content

Airport and airfield environments shall accurately reflect current aeronautical charts and National Geospatial-Intelligence Agency (NGA) / General Authority of Civil Aviation (GACA) publications. At a minimum, airfield environments shall include:

Feature Category Required Visual Element

Surfaces and Geometry Accurate runway, taxiway, apron, and helipad geometry, slopes, and surface textures (asphalt, concrete, desert hardpack).

Markings & Signage Standard ICAO/military runway markings, threshold markings, taxiway centerlines, hold-short lines, and illuminated airfield signage.

Airfield Lightning Controllable approach lighting systems (ALS), Precision Approach Path Indicators (PAPI), Visual Approach Slope Indicators (VASI), runway edge/centerline lights, taxiway lights, and rotating aerodrome beacons

Structures & Obstacles Geo-specific control towers, hangars, terminal buildings, windsocks, visual reporting points, and mission-relevant vertical obstacles.

The visual database shall support visual and instrument approach, departure, hover, taxi, slope landing, running takeoff/landing, and missed-approach training at all designated airfields during day, night, and Degraded Visual Environment (DVE) conditions.

3.13.1.3 Tactical Features and Obstacles

The database shall contain tactical training features, including active FARP layouts (fuel bladders, hoses, marshallers, and security vehicles), CAL zones, and high-altitude pinnacle/ridgeline landing zones. A realistic distribution of vertical hazards—including high-voltage transmission towers with catenary-curved power lines, guy wires, communication masts, and minarets—shall be modeled with accurate daytime visibility and nighttime obstruction lighting to support wire/obstacle avoidance and low-level terrain flight.

3.13.1.4 Degraded Visual Environment (DVE)

The visual system shall provide a physics-based, dynamic 3D volumetric brownout and whiteout model tailored to the CH-47F tandem-rotor configuration. The particulate cloud shall respond dynamically in real time to the interaction of the counterrotating forward and aft rotor downwash/outwash, aircraft altitude above ground level (AGL), ground speed, rotor pitch, and soil type. The brownout effect shall accurately replicate the progressive loss of visual references (including the forward fountain effect and dust overtaking the cockpit during deceleration and touchdown) in both unaided and NVD modes. Additionally, the visual system shall simulate continuous ceilings, variable cloud layers, fog, haze, rain, snow, smoke, and blowing sand/dust, plus an accurate astronomical ephemeris model (date/time/location-accurate sun, moon phase, and star field illumination).

3.13.1.5 Dynamic Effects

The visual system shall render dynamic rotor wash effects on environmental surfaces, including concentric water ripples/spray, blowing grass/vegetation, and loose surface dust disturbance. The IG shall also render realistic forward rotor disk occlusion, blade coning, shadow casting, and rotor strobe effects synchronized with simulated rotor RPM and ambient lighting. Physical or virtual cockpit structural masking (window frames, windshield wipers, and nose probes) shall be accurately represented from both crew design eye points.

3.13.1.6 Database Correlation

The visual database shall be fully correlated with the simulated aircraft navigation, terrain flight, and sensor databases, as well as the Instructor Operator Station (IOS) map display. The geographic position of any feature in the visual scene shall match the simulated navigation system (EGI/FMS) position for that feature to within 5.0 meters.

Visual terrain elevations shall correlate with the simulated radar altimeter and aerodynamic ground-contact model to within 1.0 foot at all runways, helipads, and prepared landing zones, and within 5.0 feet or 5% (whichever is greater) across general terrain.

3.13.1.7 Moving Models and Entity Database

The visual system shall include static and articulated 3D moving models, special effects, and mission entities required to support CH-47F training tasks in accordance with Appendix A. At a minimum, this shall include Royal Saudi Land Forces (RSLF) and coalition rotary- and fixed-wing aircraft, Combat Service Support vehicles, Air Defense Artillery, armor, civilian vehicle/pedestrian traffic, ground marshallers with animated hand/wand signals, and external sling-load cargo models (e.g., HMMWV, artillery pieces, cargo nets, and Bambi buckets) with dynamic pendant/cable physics. Because the CH-47F center cargo hooks are not visible from the forward cockpit seats, the visual system shall provide an auxiliary belly/cargo-hook camera view at the IOS (and optional simulated Flight Engineer station) to support sling-load training and evaluation.

3.13.2 Display System Performance

3.13.2.1 Field of View (FOV)

The visual system shall provide a continuous, seamless, collimated out-the-window horizontal field of view of not less than 200 degrees, with an objective of 220 degrees, and a vertical field of view of not less than 60 degrees across the main upper windscreens. At a minimum, the horizontal field of view shall ensure that both the pilot and copilot have an unobstructed 90-degree abeam (3 o'clock and 9 o'clock) line of sight from their respective on-side design eye points. In the forward quadrants, the visual system shall provide a total vertical field of view of not less than 80 degrees to fully populate the CH-47F left and right chin windows and support hover, pinnacle, and slope landing operations.

3.13.2.2 Eye Point Selection

The Image Generator (IG) shall selectively calculate three separate eye points: Pilot DEP, Copilot DEP, and a Cockpit Midpoint DEP (defined as the exact arithmetic average of the Pilot and Copilot DEPs). The location of the Pilot and Copilot DEPs shall be identical to the CH-47F Block I design basis aircraft. The Cockpit Midpoint DEP shall be the default system setting, and all three eye points shall be selectable both offline and dynamically in real time from the IOS without interrupting the training session.

3.13.2.3 Resolution, Brightness and Image Quality

The display system shall provide visual clarity equivalent to or better than 6.0 arc minutes per optical line pair (OLP) (with an objective of 4.0 arc minutes per OLP) at each design eye point and shall maintain consistent resolution across all specified display areas. Measured at the design eye point, the display system shall deliver a minimum highlight brightness of 6.0 foot-Lamberts (fL) (with an objective of 10.0 fL), a sequential full-on/full-off dark-room contrast ratio of not less than 1,000:1, and a simultaneous checkerboard contrast ratio of not less than 5:1. The system shall utilize solid-state light sources (LED or RGB Laser) and automated optical alignment and edge-blending calibration to minimize image-quality degradation due to image motion, display optics, anti-aliasing, and multi-channel blending, presenting fine light points and small tactical features with high fidelity.

3.13.2.4 Dipvergence and Collimation

The collimated display system shall maintain optical infinity cues across the viewing envelope, with dipvergence (vertical misalignment between eyes) not exceeding 5.0 milliradians at the Midpoint DEP and not exceeding 9.0 milliradians anywhere within the individual viewing volumes of the pilot and copilot. Convergence shall not exceed 7.0 milliradians, and divergence shall not exceed 4.0 milliradians. Dipvergence and collimation shall be measured and calibrated using Government-approved optical instrumentation and procedures.

3.13.2.5 Rendering Performance

visual system shall maintain a constant, stable native frame and refresh rate of not less than 60 Hz per channel (or 120 Hz if active time-multiplexing is utilized) under peak scene complexity, including full volumetric brownout in high-density environments. Total end-to-end visual system transport delay (latency)—measured from flight control mechanical input to the completion of the corresponding visual photon response on the display—shall not exceed 100 milliseconds. The visual system shall remain completely free of image tearing, stuttering, frame-rate instability, or visible rendering artifacts during rapid aircraft attitude changes and aggressive maneuvering.

3.13.2.6 Night Vision Device (NVD) Compatibility

The visual system shall provide NVD‑accurate spectral, radiometric, and luminance characteristics while simultaneously rendering a correct unaided‑eye scene. The system shall emulate NVG halo, grain, contrast, light bloom, and illumination‑dependent behavior required to support CH‑47F NVG flight tasks and shall maintain proper correlation between NVD and unaided imagery.

The FTD shall provide a single Instructor Operator Station that serves as the primary instructor interface for control, monitoring, scenario management, malfunction injection, communications, and After-Action Review support, and shall include provisions for future expansion to operate as a master IOS controlling multiple simulators or distributed training services with session discovery, authority management, and deterministic command distribution.

3.14.1 Control and States

The IOS shall allow the instructor to initialize, start, run, pause, freeze, reposition, reset, terminate, and recover the simulation, including save/restore of bookmarks that capture aircraft, environment, systems, positions, failures, and IOS settings.

3.14.2 Crew Monitoring and Display Mirroring

The IOS shall provide real-time monitoring of pilot and copilot control inputs and discrete states and shall mirror crew station avionics pages and indications with configurable GUI layouts, trend plots, exceedance flags, and limit overlays to support instruction and evaluation.

3.14.3 Scenario and Environment Management

The IOS shall control date/time, illumination, weather and visibility (including DVE effects), winds and turbulence, traffic and navaids, aircraft configuration, mass properties, and reposition to specified locations, and shall automatically detect simulator freezes or crashes and offer restoration to a default state, the last running scenario, or a selected bookmark.

3.14.4 Malfunctions and Fault Injection

The IOS shall provide a fault library for engines, powertrain, fuel, electrical, hydraulics, flight controls/DAFCS, sensors, avionics, radios/IFF/ASE, cautions/advisories, and environmental systems, with faults applicable as immediate, timed, conditional, or randomized and producing indications and responses consistent with CH‑47F Block I behavior.

3.14.5 Communications

The IOS shall be integrated with the FTD's intercommunication system (ICS). The instructor shall be able to monitor all crew communications and communicate with the crew over the ICS network.

3.14.6 Live Video and AAR Integration

The IOS shall provide multi‑camera cockpit video suitable for debrief at not less than 1080p at 30 fps, stream to the AAR station with less than 500 ms delay, and record time‑synchronized video, audio, instructor actions, and simulator data to secure storage.

3.14.7 Remote Observation Capability

The FTD shall provide a secure capability for authorized users at a location separate from the installation site to observe live training events in near real-time. The capability shall, at a minimum, support view-only observation of the active training session, including live cockpit video and selected IOS displays. Remote users shall have no ability to control the FTD, modify scenarios, inject malfunctions, change settings, or alter recorded data.

The Remote Observation Capability shall include access-control, authentication, and audit features sufficient to restrict access to authorized users and record user access activity. The capability shall operate within the standalone training network and shall be implemented such that remote users are isolated from FTD control functions and cannot introduce commands, configuration changes, or…