RSLFAC_UH-60M FTD SPEC_DRAFT.pdf

PRF-PT-00909

28 October 2026

Rev. 0.1

CUI

I

CUI

Performance Specification for the

Royal Saudi Land Forces Aviation Corps

UH-60M

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

II

Revision History

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

DRAFT

III

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 Multi-Function Displays (MFDs)

3.3.2 Flight Management Systems (FMS)/Control Display Unit

(CDU)

3.3.3 Flight Director/Display Control Panels (FD/DCP)

3.3.4 Embedded GPS/INS (EGI)

3.3.5 Engine Indication and Crew Alerting System (EICAS)

3.3.6 Data Transfer System (DTS)

3.3.7 Communication Systems

3.3.8 Navigation Systems

3.3.9 Aircraft Survivability Equipment (ASE)

3.4 Engine and Powertrain Systems

3.4.1 Engines

3.4.2 Digital Electronic Control Unit (DEC/EDECU)

3.4.3 Power Train System

3.4.4 Rotor System

3.5 Fuel System

3.6 Hydraulic Systems

3.7 Flight Control System

3.7.1 Primary Flight Controls

3.7.2 Automatic Flight Control System (AFCS)

3.7.3 Stabilator

3.8 Electrical System

IV

3.8.1 Clean Power

3.9 Utility and Miscellaneous Systems

3.9.1 Engine Inlet Barrier Filter (EIBF)

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 Rescue Hoist and Cargo Hook

3.10 Emergency Procedures

3.11 Sensory Cueing System

3.11.1 Control Loading System

3.11.2 Vibration and Tactile Cueing System

3.11.3 Aural Cue System

3.12 Visual System

3.12.1 Visual Database

3.12.1.1 Geographic Coverage and Fidelity

3.12.1.2 High Fidelity Zones

3.12.1.2.1 Designated Training Airfields and Fidelity Categories

3.12.1.2.2 Airfield and Airport Environment Content

3.12.1.3 Tactical Features and Obstacles

3.12.1.4 Degraded Visual Environment (DVE)

3.12.1.5 Dynamic Effects

3.12.1.6 Database Correlation

3.12.1.7 Moving Models and Entity Database

3.12.2 Display System Performance

3.12.2.1 Field of View (FOV)

3.12.2.2 Eye Point Selection

3.12.2.3 Resolution, Brightness and Image Quality

3.12.2.4 Dipvergence and Collimation

3.12.2.5 Rendering Performance

3.12.2.6 Night Vision Device (NVD) Compatibility

3.13 Instructor Operator Station (IOS)

3.13.1 Control and States

3.13.2 Crew Monitoring and Display Mirroring

3.13.3 Scenario and Environment Management

3.13.4 Malfunctions and Fault Injection

3.13.5 Communications

3.13.6 Live Video and AAR Integration

3.13.7 Remote Observation Capability

3.13.8 Safety and Emergency Functions

3.13.9 Performance and Availability

V

3.13.10 Access Control and Audit

3.14 After Action Review (AAR)

3.14.1 Recorded Data

3.14.2 Time Base and Synchronization

3.14.3 Playback

3.14.4 Instructor Tools

3.14.5 Data Quality and Performance

3.14.6 Data Management and Security

3.15 Reliability, Availability, and Maintainability (RAM)

3.15.1 Availability

3.15.2 Reliability

3.15.3 Maintainability

3.16 System Safety

3.16.1 Emergency Stop (E-Stop)

3.16.2 Electrical and Mechanical Safety

3.16.3 Material Flammability

3.16.4 Safe Ingress and Egress

3.17 Cybersecurity

3.17.1 Authentication and Authorization

3.17.2 System Hardening

3.17.3 Audit and Logging

3.17.4 Data Protection

3.17.5 Network Isolation and Boundary Protection

3.18 Architectural Commonality for Future Interoperability

3.18.1 Strategic Intent

3.18.2 Technical Implementation

4. VERIFICATION

4.1 Methods of Verification

4.2 Verification Milestones

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 Training Scenarios

4.3.11 Mission Tests

VI

4.3.12 Stress Tests

4.3.13 Free Play Tests

4.3.14 Threat Environment Tests

4.3.15 Malfunctions Test

4.3.16 Database Correlation Tests

4.3.17 Interoperability Tests

4.3.18 Product Assurance Tests

4.3.19 Thermal Survey

4.3.20 EMR Tests

4.3.21 ESD Tests

4.3.22 Human Systems Integration Engineering Compliance Tests

4.3.23 Nonfunctional Examinations

APPENDIX SECTION

APPENDIX A – Designated Visual Database Locations APPENDIX C – Acronym List

Performance Specification for

Royal Saudi Land Forces Aviation Corps UH-60M Flight Training Device

1. SCOPE

1.1 Purpose

This Performance Specification establishes the technical, functional, interoperability, fidelity, environmental, cybersecurity, and verification requirements for the UH-60M 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 King Khalid Military City (KKMC), Kingdom of Saudi Arabia.

The FTD shall achieve a fidelity and performance standard equivalent to an 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 UH-60M military aircraft configuration and shall not require FAA qualification.

1.2 System Description

The FTD shall provide a high-fidelity simulation of the RSLFAC-configured UH-60M 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, cue integration, and system integration comparable to a Federal Aviation Administration (FAA) Flight Training Device (FTD) Level 7, while remaining fully tailored to the military UH-60M configuration and RSLFAC training requirements. The FTD shall provide pilot and copilot crew stations configured to support the required UH- 60M training tasks. 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 UH-60M 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.

2.1 Government Documents

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 Flight Training Device (FTD) shall replicate the form, fit, function, and training-relevant performance of the RSLFAC UH-60M. The FTD shall provide a level of simulation fidelity, responsiveness, cue integration, and system complexity comparable to a Federal Aviation Administration (FAA) Flight Training Device (FTD) Level 7, tailored to the military UH-60M configuration.

3.1 General Requirements

3.1.1 System Fidelity

The FTD shall model the UH-60M 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 UH-60M 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 interoperability central/master IOS.

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 UH-60M 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 be designed to support networked training in which the device may be connected with other compatible simulators to perform multi-ship mission training. The required training tasks supported by the FTD are identified in Appendix B, Task List.

3.1.4 Interoperability

The FTD shall be designed with an open systems architecture and provide external interfaces for simulation data exchange (e.g., HLA/DIS), visual systems (e.g., CIGI), and instructor stations that are identical to those defined in the CH-47F FTD interoperability solution, to preserve future interoperability options and support future compliance with PRF-PT-00910, Saudi Arabia RSLFAC Interoperability Performance Specification.

3.2 Cockpit and Crew Environment

The FTD shall provide a high-fidelity physical replication of the UH-60M 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 UH-60M 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, and cockpit mission/system controls required for UH-60M pilot and copilot operation.

3.2.3 Lighting Systems

The FTD shall simulate all cockpit lighting systems required for UH-60M pilot and copilot operations, including control behaviors, intensity ranges, and integration with NVG-compatible illumination. The cockpit shall be Night Vision Goggle (NVG) compatible and shall support pilot and copilot training operations in aided and unaided night conditions.

3.3 Avionics Systems

The FTD shall implement the UH-60M integrated avionics system consistent with the RSLFAC configuration. All functionality, update rates, color schemes, symbology, control logic, data flow, and display behavior shall match the design-basis aircraft. The FTD shall provide functional replications of the primary avionics’ subsystems. The update rate for all avionics displays and data shall be a minimum of 30 Hz. The latency from a simulated event to the corresponding avionics alert or indication shall not exceed 100 milliseconds.

3.3.1 Multi-Function Displays (MFDs)

The FTD shall provide MFDs that replicate the display formats (PFD, EICAS, etc.), symbology, color usage, operational modes, page families, and declutter options of the UH-60M aircraft.

3.3.2 Flight Management Systems (FMS)/Control Display Unit (CDU) The FTD shall replicate the dual UH-60M FMS via the CDUs, including page layouts, navigation logic, data entry, alphanumeric input, menu structures, and system configuration functions.

3.3.3 Flight Director/Display Control Panels (FD/DCP)

The FTD shall replicate the FD/DCPs, including all mode selections, knob and button functionality, and display interactions.

3.3.4 Embedded GPS/INS (EGI)

The FTD shall simulate the behavior and performance of the dual EGI navigation units, including alignment, navigation, and failure modes.

3.3.5 Engine Indication and Crew Alerting System (EICAS)

The FTD shall fully replicate the EICAS, including all engine parameter displays, fuel quantity displays, and the presentation of all caution and advisory messages consistent with the aircraft's logic.

3.3.6 Data Transfer System (DTS)

The FTD shall simulate the DTS functions required to support data loading and mission data management.

3.3.7 Communication Systems

The FTD shall simulate the UH-60M communication systems, replicating the specific human-machine interface (HMI) and performance characteristics of the RSLFAC-configured radios (e.g., AN/ARC-201D, AN/ARC-231) and the Intercommunication System (ICS).

3.3.8 Navigation Systems

The FTD shall simulate the UH-60M navigation systems, including the specific HMI and performance of installed radio navigation units such as the AN/ARN-147 (VOR/ILS), AN/ARN-149 (ADF), and AN/ARN-153 (TACAN). The simulation shall also replicate the AN/APN-209 Radar Altimeter.

3.3.9 Aircraft Survivability Equipment (ASE)

The FTD shall simulate the ASE suite installed on the RSLFAC UH-60M, replicating the pilot/copilot interfaces, controls, and displays for systems such as the AN/APR-39 Radar Signal Detecting Set and the Common Missile Warning System (CMWS). The simulation shall also replicate the functionality of the IFF Transponder.

3.4 Engine and Powertrain Systems

3.4.1 Engines

The FTD shall simulate the performance, operation, and dynamic behavior of the T700- GE-701D engines. The model shall represent engine response to power control lever inputs, environmental conditions, system failures, and the effects of bleed air usage.

3.4.2 Digital Electronic Control Unit (DEC/EDECU)

The FTD shall simulate the UH-60M DEC/EDECU system. The simulation shall manage engine operation, fuel flow scheduling, NP governing, performance limiting, and torque matching behavior. All DEC/EDECU modes, including LOCKOUT, and associated cautions/advisories shall be represented.

3.4.3 Power Train System

The FTD shall simulate the UH-60M power train system, including the main transmission, intermediate gearbox, tail rotor gearbox, driveshafts, and accessory modules. The simulation shall model lubrication systems, chip detection, and all related caution and advisory logic.

3.4.4 Rotor System

The FTD shall simulate the UH-60M's single, four-bladed, fully articulated main rotor and the canted tail rotor. The simulation shall accurately model rotor dynamics, including flapping, lead-lag, blade stall, translational lift, and vortex ring state.

3.5 Fuel System

The FTD shall simulate the UH-60M fuel system, including main fuel tanks, fuel transfer, consumption, and quantity indication. Where applicable to the RSLFAC configuration, the simulation shall include the Crashworthy External Fuel System (CEFS) and/or the Internal Auxiliary Fuel Tank System (IAFTS), including all pilot procedures for fuel transfer and management. The model shall account for the real-time effects of fuel load on aircraft mass and center-of-gravity.

3.6 Hydraulic Systems

The FTD shall simulate the UH-60M No. 1 and No. 2 primary hydraulic systems and the backup hydraulic system. The simulation shall include pump performance, pressure and temperature dynamics, and leak conditions. The model shall be fully integrated with the flight controls, ensuring that loss of hydraulic pressure results in the corresponding changes to flight control forces and aircraft handling characteristics.

3.7 Flight Control System

3.7.1 Primary Flight Controls

The FTD shall simulate the UH-60M mechanical flight control system, including the cyclic, collective, and directional control pedals, and the associated mechanical mixing unit.

3.7.2 Automatic Flight Control System (AFCS)

The simulation shall include the AFCS, comprising the Stability Augmentation System (SAS), Trim systems, and Flight Path Stabilization (FPS). All AFCS modes, mode transitions, and failure behaviors shall be simulated.

3.7.3 Stabilator

The FTD shall simulate the UH-60M stabilator system in both automatic and manual modes. The simulation shall replicate its response to airspeed, collective inputs, and pitch rate, as well as all pilot controls for manual slewing and failure indications.

3.8 Electrical System

The FTD shall simulate the UH-60M 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 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.

3.9 Utility and Miscellaneous Systems

3.9.1 Engine Inlet Barrier Filter (EIBF)

The FTD shall simulate the EIBF system, including the bypass function, its effect on engine performance, and all associated cockpit indications.

3.9.2 Anti-icing System

The FTD shall simulate the engine, inlet, and windshield anti-icing functions and their effect on engine performance.

3.9.3 Auxiliary Power Unit (APU)

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

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 Rescue Hoist and Cargo Hook

Where applicable to the RSLFAC configuration, the FTD shall simulate the pilot/copilot tasks associated with rescue hoist and external load operations, including the flight dynamics of external loads and all relevant cockpit controls.

3.10 Emergency Procedures

The FTD shall support the execution of all UH-60M pilot and copilot emergency procedures documented in the applicable flight manuals and required for training. This shall include, but not be limited to, the complete simulation of the Fire Detection and Extinguishing System, including all cockpit warnings, T-handles, and system logic. Each emergency shall produce the correct cockpit indications, aircraft performance effects, and system behaviors consistent with the design-basis aircraft.

3.11 Sensory Cueing System

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.11.1 Control Loading System

The FTD shall include a control loading system that reproduces the force-feel, mechanical characteristics, and dynamic behavior of the UH-60M primary flight controls.

3.11.2 Vibration and Tactile Cueing System

The FTD shall provide a vibration and tactile cueing system that reproduces characteristic UH-60M rotor, drivetrain, and aerodynamic signatures.

3.11.3 Aural Cue System

The FTD shall provide a high-fidelity aural cueing environment that accurately reproduces the sounds of the UH-60M cockpit, including engines, rotor, transmissions, and all system warnings and voice messages.

3.12 Visual System

The 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 UH-60M pilot and copilot training. The visual system shall support individual and collective flight training tasks, instrument procedures, Nap-of-the-Earth (NOE) and low-level terrain flight, wire/obstacle avoidance, multi-ship and formation flight, tactical mission training, and mission rehearsal across continuous time-of-day transitions (dawn, bright day, dusk, and night) and Degraded Visual Environments (DVE). 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.12.1 Visual Database

The FTD shall include a comprehensive, real-time synthetic environment visual database that provides an accurate and correlated representation of the operational environment appropriate to UH-60M pilotage tasks and Royal Saudi Land Forces Aviation Command (RSLFAC) requirements. Because no Government Furnished Information (GFI) geospatial or aeronautical source data will be provided, the Contractor shall be 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 Contractor shall propose an optimized level-of-detail (LOD) and database paging architecture matched to their IG capabilities to prevent frame-rate degradation, polygon popping, or texture swimming during all required training tasks.

3.12.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), encompassing the King Khalid Military City (KKMC) and Al Qassim regions and ensuring continuous regional coverage across all designated Saudi Arabian training airfields without database reloading. The Contractor may propose an optimized, multi-tier commercial source data architecture across this gaming area, provided that within a 500 by 500 NM core operational region centered on KKMC/Al Qassim and along flight corridors connecting all designated airfields, the terrain elevation model has a post spacing of 30 meters or less (DTED Level 2 equivalent or better) and the ground ortho-imagery resolution is 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 NOE flight, low-level navigation, pilotage, instrument procedures, and tactical flight training.

3.12.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 Lower-Fidelity Airfields, NOE routes, and 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 high-resolution surface mesh modeling at runways, helipads, and pinnacle landing zones), and the ground imagery resolution shall be 0.5 meter-per-pixel or better.

3.12.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 UH-60M 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 ((15-NM High-Res Zone + Custom 3D Models):

• Hail

• Jubail

• Taif

• Bishah

• Jizan

• Najran

• Al Jiwa

• Qausumah

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

3.12.1.2.2 Airfield and Airport Environment Content

Airport and airfield environments shall accurately reflect current commercial/official aeronautical charts and 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, roll-on/running landing, and missed-approach training at all designated airfields during day, night, and Degraded Visual Environment (DVE) conditions.

3.12.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, NOE terrain flight courses, 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, NOE flight, and mission rehearsal.

3.12.1.4 Degraded Visual Environment (DVE)

The visual system shall provide a physics-based, dynamic 3D volumetric brownout and whiteout model tailored to UH-60M single-main-rotor and canted tail-rotor aerodynamics. The particulate cloud shall respond dynamically in real time to main-rotor downwash, tail-rotor vortex interaction, hover height above ground level (AGL), ground speed, translational lift, rotor pitch, and soil composition. The model shall accurately replicate UH-60M-specific dust cloud formation, including the ground-vortex forward roll-up of dust overtaking the cockpit during low-speed deceleration below Effective Translational Lift (ETL) and characteristic tail-rotor dust plumes. The brownout effect shall obscure visual ground references in both unaided and NVD modes consistent with the perceptual challenges of UH-60M brownout operations. 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.12.1.5 Dynamic Effects

The visual system shall render dynamic rotor-wash interactions with environmental surfaces, including concentric water ripples/spray, blowing grass/vegetation, sand/dust swirls, and loose objects, correlated with aircraft position, altitude, heading, and rotor state. The IG shall also render realistic main-rotor disk translucency, blade coning, shadow casting, and rotor strobe effects synchronized with simulated rotor RPM, as well as accurate UH-60M cockpit structural masking (windscreen center post, door frames, overhead greenhouse windows, windshield wipers, and pitot/wire-strike cutters) from both crew design eye points.

3.12.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. The visual database shall support simultaneous, fully correlated rendering for both unaided-eye and NVD viewing modes.

3.12.1.7 Moving Models and Entity Database

The FTD visual database and scene generation system shall include the static and articulated 3D moving models, special effects, and mission entities required to support UH-60M 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 (supporting close multi-ship and formation flight), Combat Service Support vehicles, Air Defense Artillery, armor and artillery, civilian vehicle/pedestrian traffic, ground marshallers with animated hand/wand signals, weapon/countermeasure lighting effects, and external sling-load cargo models (with dynamic cable/load swing physics). To support sling-load training where the UH-60M cargo hook is beneath the cabin floor, the Contractor shall provide an auxiliary belly/cargo-hook visual or camera view at the IOS for load monitoring and evaluation.

3.12.2 Display System Performance

3.12.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 to 225 degrees) and a vertical field of view of not less than 45 degrees (with an objective of 60 degrees or greater), centered on the UH-60M pilot and copilot design eye points. 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, and the vertical field of view shall populate the UH-60M lower forward chin bubbles required for hover, approach, slope landing, and obstacle-avoidance tasks.

3.12.2.2 Eye Point Selection

The image generator (IG) shall compute three independent eye points: pilot, copilot, and a midpoint between them. The location of the Pilot and Copilot DEPs shall correspond to the UH-60M design-basis aircraft geometry. 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.12.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, maintaining consistent resolution and focus 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 Contractor shall propose a modern solid-state projection system (such as LED or RGB Laser) and automated optical alignment/edge-blending calibration solution that minimizes image-quality degradation due to image motion, display optics, anti-aliasing, optical distortion, and channel transitions, accurately depicting fine light points, long-range cultural features, wires, and small obstacles critical to UH-60M low-level and NOE flight.

3.12.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 UH-60M 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 industry-standard optical instrumentation and procedures.

3.12.2.5 Rendering Performance

The 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 NOE flight and 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.12.2.6 Night Vision Device (NVD) Compatibility

The visual system shall replicate NVD‑correct spectral, radiometric, and luminance characteristics while simultaneously providing accurate unaided imagery. The system shall emulate UH‑60M‑appropriate NVG halo, bloom, contrast, grain, scene luminance response, and the performance differences between aided and unaided vision. The correlation between NVD and unaided imagery shall be maintained across all light levels, cultural lighting conditions, and environmental effects.

3.13 Instructor Operator Station (IOS)

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 (AAR). The IOS shall include provisions for future expansion to function as a master IOS supporting multiple UH‑60M simulators or distributed training services, including session discovery, authority management, and deterministic command distribution across a networked training environment.

3.13.1 Control and States

The IOS shall provide full control of all UH‑60M simulation states including initialization, start, run, pause, freeze, reposition, reset, termination, and recovery. The IOS shall allow the instructor to save and restore bookmarks that capture aircraft state, environmental conditions, system configurations, aircraft position and attitude, failures, and all relevant IOS settings.

3.13.2 Crew Monitoring and Display Mirroring

The IOS shall provide real‑time monitoring of UH‑60M pilot and copilot control inputs, system states, and avionics data. The IOS shall mirror crew‑station display pages including MFDs, EICAS, FMS/CDU pages, ASE displays, and communication pages.

The IOS shall provide configurable layouts, time‑history trend plots, limit overlays, and exceedance flags to support UH‑60M‑specific instruction, evaluation, and task performance tracking.

3.13.3 Scenario and Environment Management

The IOS shall control and modify environmental, operational, and mission parameters including date/time, solar/lunar illumination, weather and visibility, DVE effects

(including UH‑60M‑specific brownout behavior), winds, turbulence, traffic, navaids, aircraft configuration, and mass properties. The IOS shall allow precise repositioning of the aircraft to any geodetic coordinate, altitude, attitude, or ground location. The system shall detect simulator freezes or software crashes and offer automated recovery to the default baseline, the last running scenario, or any selected bookmark.

3.13.4 Malfunctions and Fault Injection

The IOS shall provide a comprehensive fault library consistent with UH‑60M systems including:

a. T700‑GE‑701D engines, DEC/EDECU functions, and LOCKOUT behavior.

b. Main transmission, intermediate gearbox, tail rotor gearbox, driveshafts, chip detectors.

c. Fuel system components including transfer logic and auxiliary tanks

(CEFS/IAFTS where applicable).

d. Electrical system including AC/DC buses, generators, power transfer logic, and circuit breakers.

e. No. 1, No. 2, and backup hydraulic systems.

f. UH‑60M mechanical flight controls, Stabilator system, and AFCS (SAS, Trim, FPS).

g. Navigation and avionics systems including MFDs, FMS, EGI, FD/DCP, and radar altimeter.

h. Communication systems including AN/ARC‑201D, AN/ARC‑231, ICS.

i. ASE systems including AN/APR‑39, CMWS, IFF transponder.

j. Caution/advisory system faults consistent with UH‑60M logic

Faults shall be applicable as immediate, timed, conditional, randomized, or scenario‑driven, and shall produce cockpit indications, system responses, and aircraft behavior consistent with UH‑60M operational manuals and training requirements.

3.13.5 Communications

The IOS shall integrate fully with the FTD’s Intercommunication System (ICS). The instructor shall be able to monitor and participate in all internal crew communications and selectively communicate with the pilot, copilot, or both. The IOS shall support transmit/receive monitoring of simulated UH‑60M radios and interphone channels.

3.13.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.13.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 data modifications into the active training environment. The Remote Observation Capability shall not degrade required simulator performance or disrupt live training operations.

3.13.8 Safety and Emergency Functions

The IOS shall provide an emergency stop that immediately commands a safe state, disables active vibration/tactile cueing and halts cues as required, and shall log emergency and shutdown actions with timestamps for audit and AAR.

3.13.9 Performance and Availability

The IOS shall execute instructor commands with deterministic timing sufficient to maintain synchronization with the UH‑60M simulation, audio, visual, and cueing systems. The IOS shall maintain a common time base with all simulation services and shall automatically reconnect following software restart or network disruptions while preserving logs, recordings, and bookmarks.

3.13.10 Access Control and Audit

The IOS shall enforce user authentication, role‑based access control, and audit logging of operator identity and actions, and shall protect logs from unauthorized modification in accordance with the cybersecurity requirements of this specification.

3.14 After Action Review (AAR)

The FTD shall include an integrated After‑Action Review capability that records, stores, and replays synchronized data from the training event. The AAR system shall operate without degrading real‑time simulation performance and shall continue recording across initialization, freeze, reposition, reset, and termination with event markers.

3.14.1 Recorded Data

The AAR system shall record aircraft state parameters, control inputs, system indications, avionics pages, environmental data, instructor actions, IOS events, and simulation metadata, and shall record synchronized cockpit video and intercom audio consistent with training requirements.

3.14.2 Time Base and Synchronization

The AAR system shall use a common deterministic time base shared with the simulation services and shall timestamp all recorded modalities with an end‑to‑end alignment error not exceeding 50 milliseconds and jitter not exceeding 10 milliseconds.

3.14.3 Playback

The AAR system shall support synchronized playback with controls for play, pause, rewind, fast‑forward, time‑jump navigation, and parameter overlay, and shall reproduce the visual scene, aircraft state, crew inputs, and audio consistent with the recorded event and event markers.

3.14.4 Instructor Tools

The AAR system shall allow the instructor to annotate, bookmark, and highlight portions of the recorded event and shall automatically index instructor actions, failure injections, freeze, reposition, and reset events.

3.14.5 Data Quality and Performance

The AAR system shall record aircraft state at not less than 50 Hz and control inputs at not less than 200 Hz, shall record cockpit video at not less than 1080p at 30 frames per second, and shall record intercom audio at not less than 48 kHz and 16-bit depth; the system shall maintain continuous capture suitable for debrief and shall not introduce perceptible latency or instability in the visual, avionics, control loading, or vibration/tactile systems.

3.14.6 Data Management and Security

The AAR system shall store recordings in a secure, organized format, protect recordings against unauthorized access or modification, and support export of AAR packages with synchronized data, video, audio, annotations, and event indices in accordance with program security and retention requirements. The AAR system shall provide active storage capacity for not less than twelve (12) hours of continuous recording per training event on the FTD’s local or immediately accessible storage, for extended exercises that span longer periods, the system shall support the seamless initiation of new, sequential AAR recordings without data loss or interruption to the overall simulation. The system shall provide sufficient active storage capacity on the FTD's local or immediately accessible storage to retain all recorded training events for a minimum of thirty (30) days. Data older than thirty (30) days shall be automatically or semi-automatically transferred to a designated network-attached storage (SAN) or equivalent archival system. The archival system shall provide sufficient capacity to retain all training event data for a minimum of one (1) year.

3.15 Reliability, Availability, and Maintainability (RAM)

The FTD shall be designed and constructed to achieve a high degree of operational availability through a combination of high reliability and ease of maintenance. The RAM requirements defined herein apply to the entire FTD system.

3.15.1 Availability

The FTD shall be designed to support an Operational Availability (𝐴𝐴𝑜𝑜) of not less than 95%. Operational Availability shall be calculated as: 𝐴𝐴𝑜𝑜 = 𝑀𝑀𝑀𝑀𝑀𝑀𝑀𝑀

𝑀𝑀𝑀𝑀𝑀𝑀𝑀𝑀+𝑀𝑀𝑀𝑀𝑀𝑀𝑀𝑀

, where MTBF is

Mean Time Between Failure and MTTR is Mean Time to Repair. The contractor shall provide a RAM analysis report during the design phase to ensure that the proposed design can achieve this availability.

3.15.2 Reliability

The FTD shall demonstrate a Mean Time Between Failure (MTBF) of not less than 200 operating hours. A failure is defined as any event, hardware or software, that prevents the accomplishment of a scheduled training task or results in the loss of a critical training cue.

3.15.3 Maintainability

The FTD shall demonstrate a Mean Time to Repair (MTTR) of not more than 2.0 hours.

MTTR is the average time required to diagnose, repair, and verify the correction of a failure. No single corrective maintenance action shall exceed a Maximum Time to Repair (MaxTTR) of 4.0 hours. The FTD design shall incorporate Built-In Test (BIT) capabilities and provide physical and logical access to all components to facilitate rapid fault isolation and repair.

3.16 System Safety

The FTD shall be designed to be safe for all personnel, including crew, instructors, and maintainers, under all operating, maintenance, and emergency conditions. The system design shall identify and mitigate potential hazards, including electrical, mechanical, and material hazards.

3.16.1 Emergency Stop (E-Stop)

The FTD shall be equipped with readily accessible Emergency Stop buttons located within the cockpit and at the Instructor Operator Station (IOS). Activation of any E-Stop button shall immediately and safely remove all electrical power from the control loading and vibration systems and place all other FTD subsystems into a safe, unpowered, or neutral state without causing damage to the equipment.

3.16.2 Electrical and Mechanical Safety

The FTD electrical system shall be designed and constructed in accordance with National Fire Protection Association (NFPA) 70 and NFPA 79 standards. The completed FTD shall be free of unprotected pinch points, sharp edges, and other physical hazards that could cause injury to personnel.

3.16.3 Material Flammability

All materials used in the construction of the crew station interior, including seating, lining, and furnishings, shall meet the flammability requirements of Federal Aviation

Regulation (FAR) 25.853(a) or an equivalent, recognized industry standard for fire resistance.

3.16.4 Safe Ingress and Egress

The FTD shall provide a clear and unobstructed path for crew ingress and egress. In the event of a primary power loss to the FTD, battery-powered emergency lighting shall automatically illuminate the egress path for a duration of not less than 30 minutes.

3.17 Cybersecurity

The FTD shall incorporate security controls to protect against unauthorized access, modification, disclosure and disruption of the system and its training data. The system shall be delivered in a secure configuration that minimizes its attack surface within the standalone training network environment.

3.17.1 Authentication and Authorization

The FTD shall enforce individual user authentication for all access to the Instructor Operator Station (IOS), maintenance interfaces, remote observation capability (if implemented), and any administrative functions. The system shall implement a role-based access control (RBAC) mechanism that restricts user privileges to only those necessary for their assigned role (e.g., instructor, maintainer, administrator). Privileged functions shall require re-authentication or elevated privileges.

3.17.2 System Hardening

All Commercial Off-The-Shelf (COTS) operating systems and software shall be configured in accordance with a recognized security hardening benchmark, such as the public domain Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs). All unnecessary software, services, accounts, and network ports shall be disabled or removed from the delivered system. The delivered configuration shall minimize the attack surface of the FTD within the standalone training network.

3.17.3 Audit and Logging

The FTD shall generate and protect audit logs that record network security-relevant events. At a minimum, these events shall include all successful and failed login attempts, changes to user privileges, and actions performed by privileged users. Each log entry shall include a timestamp, user identity (where applicable), and event description. Audit logs shall be protected from unauthorized modification or deletion.

3.17.4 Data Protection

The FTD shall protect the confidentiality and integrity of training data, including After- Action Review (AAR) recordings, scenario files, and anu data exchange over standalone interoperability network. Appropriate controls shall be applied to data at rest and data in transit within the isolated training environment.

3.17.5 Network Isolation and Boundary Protection

The FTD shall be designed to operate within standalone, isolated training network (intranet) with no connection to external or enterprise networks. The interoperability interfaces shall be strictly controlled so that only authorized traffic (as defined in the Interface Control Document) is permitted between the FTD and other federated training devices, if applicable. Network boundary devices shall enforce this isolation

3.18 Architectural Commonality for Future Interoperability

3.18.1 Strategic Intent

While there is no Day One requirement for the UH-60M FTD and the CH-47F FTD to interoperate, the vendor shall design both systems with the explicit provision for future co-location and seamless integration. The objective is to ensure maximum life-cycle flexibility for the RSLFAC and to preclude the need for a costly and complex future re-integration effort.