Guatemala Bell 412 EPX FTD Technical Requirements_10.21.2026.pdf

GUATEMALA BELL 412 EPX FLIGHT TRAINING DEVICE (FTD)

Technical Requirement

FTD Technical specifications and requirements.

1. General / Certification Requirements

1.1 The simulator shall be a 412 EPX flight training device configured as a multi-crew cockpit representative of the customer’s aircraft (avionics, engine/rotor configuration, and mission equipment).

1.2 The device shall be designed to achieve at least FTD Level 6 (or equivalent national standard) for rotary-wing training, supporting procedures, systems, and mission training.

1.3 The simulator shall be designed to support qualification under EASA, FAA, ICAO, and other relevant CAA regulations as applicable, with all required technical documentation and Master Qualification Test Guide (MQTG) provided by the manufacturer.

1.4 The system shall support automatic or semi-automatic Qualification Test Guides (QTGs) for initial and recurrent certifications.

1.5 The device shall be capable of being updated to comply with future regulatory changes without hardware replacement (through software upgrades and modular architecture).

2. Cockpit & Avionics Requirements

2.1 The simulator shall provide a full 412 EPX cockpit layout, with all primary flight controls, engine controls, and essential systems replicated in form, function, and ergonomics.

2.2 All flight controls (cyclic, collective, pedals) shall provide realistic feel and control forces consistent with the actual aircraft.

2.3 The avionics configuration shall match the customer aircraft configuration and may include:

• Original or functionally equivalent GTN-series units or the selected avionics suite, if installed in the real fleet.

• Primary flight display/EFIS, navigation radios, transponder, audio panels, and any mission-specific avionics (e.g., GPS, moving map).

2.4 All key aircraft systems shall be simulated, including:

• Electrical, fuel, hydraulic, engine/rotor, AFCS/autopilot, and warning/caution systems.

• Normal, abnormal, and emergency procedures for each system.

2.5 Cockpit switches, controls, and indications shall behave identically to the real aircraft systems for training purposes (wherever practicable).

3. Flight & Systems Modeling

3.1 The flight model shall accurately simulate 412 EPX performance and handling characteristics across the operational envelope, including:

• Hover, transition, climb, cruise, descent, approach, and landing.

• Single-engine and degraded performance profiles.

• Weight, balance, and environmental effects (temperature, altitude, wind).

3.2 The flight model shall be validated against real aircraft data or manufacturer performance data sufficient to meet FTD Level 6 requirements.

3.3 Systems simulation shall support:

• Normal operations and checklists.

• Failure modes (engine, hydraulic, electrical, avionics failures, etc.).

• Emergency and abnormal procedures training.

4. Visual System Requirements

4.1 The simulator shall include a high-fidelity visual system with:

• LED or projector-based display providing an immersive field of view comparable to at least 200° x 70° (or suitable coverage for realistic helicopter operations).

4.2 The image generator shall:

• Provide high-resolution, real-time rendering of terrain, weather, and lighting.

• Support day, night, and dusk conditions, including realistic shadows and atmospheric effects.

• Model degraded visual environments (rain, fog, dust, low illumination) suitable for high-risk mission training.

4.3 The visual database shall include:

• Geo-specific terrain and cultural data for Guatemala and operationally relevant border/security regions (e.g., jungles, mountains, coastal areas, airfields, known trafficking corridors).

• Obstacle and terrain detail sufficient for low-level and confined-area operations.

4.4 The system shall support future updates to visual databases (e.g., additional regions, updated infrastructure) through software upgrades.

5. Mission & Training Capability Requirements

5.1 The simulator shall support training in the following mission areas:

• Border security and aerial surveillance.

• Detection, tracking, targeting, and interdiction of illicit trafficking (air, ground, riverine).

• CASEVAC and medical evacuation operations using the 412 EPX fleet.

• IFR and PBN operations if applicable to the fleet’s avionics.

• High-risk mission profiles (night operations, adverse weather, confined-area landings).

5.2 Scenario-based training shall allow:

• Custom definition of mission routes, threats, and events.

• Dynamic changes during the scenario (weather, failures, threat behavior).

• Multi-crew coordination and joint training with simulated ground or maritime elements.

5.3 The simulator shall support Crew Resource Management (CRM), OPC/proficiency checks, and procedural memory training, including:

• Multi-crew communication and coordination.

• Workload and task-sharing under time pressure.

• Standard and emergency operating procedures.

6. Motion / Haptics Requirements

6.1 The simulator shall include at least a vibration/haptic system that reproduces rotorcraft tactile cues, such as:

• Engine/rotor vibrations.

• Turbulence and ground resonance cues.

• Cueing for changes in flight regime and rotor RPM.

6.2 The vibration system shall be synchronized with the flight model and visual events to support pilot perception of aircraft state.

7. Debriefing & Data Analysis

7.1 The system shall include a dedicated debriefing station that provides:

• Playback of simulator sessions with synchronized views (cockpit, external, parameter plots).

• Timeline control (pause, rewind, fast forward).

• Display of key flight parameters (altitude, speed, attitude, power) over time.

7.2 Debrief tools shall enable:

• Assessment of mission outcomes (e.g., detection and interdiction success, time to target).

• Analysis of CRM and procedural adherence.

• Export of session data and reports (PDF or equivalent) for record-keeping and performance tracking.

7.3 The system shall support secure storage of recorded missions and training data with user management controls.

8. Software, Upgrades & In-House Technology

8.1 The architecture shall be modular and open enough to allow:

• Software updates to the flight model, systems, visuals, and avionics simulations.

• Integration of additional training features and mission equipment in the future.

8.2 The system shall support:

• Navigation database updates, with tools for loading and managing nav data.

• Visual database updates and patching without major downtime.

9. Networking, Remote Support & Cyber

9.1 The simulator shall provide a secure network interface to allow:

• Remote access by the manufacturer for software corrections, updates, and troubleshooting, subject to customer security policy.

• Transfer of navigation and visual database updates.

9.2 The system shall include:

• User access controls for instructor, administrator, and maintenance roles.

• Logging of configuration changes and software updates.

9.3 The simulator shall be compatible with the customer’s IT policies and enable isolation (air-gapping) where required, with a defined process for importing updates.

10. Instructor & Operator Station Requirements

10.1 The system shall include an instructor/operator station that enables:

• Creation, modification, and storage of training scenarios.

• Real-time control of weather, time of day, failures, and traffic.

• Monitoring of all major flight parameters and crew actions.

10.2 The instructor station shall support:

• Start/stop/reset of sessions.

• Freeze, reposition, and time-skip functions.

• Predefined training profiles (OPC checks, emergency procedures, mission scenarios).

10.3 The interface shall be intuitive, with multi-screen capability and context-sensitive help.

11. Installation, Facility & Infrastructure Requirements

11.1 The manufacturer shall provide a detailed simulator room specification, including:

• Required dimensions and clearances.

• Floor loading requirements.

• Environmental conditions (temperature, humidity, noise limits).

• Access routes for crating and installation.

11.2 Electrical requirements shall be specified, including:

• Voltage, frequency, and maximum current draw.

• Power quality and grounding requirements.

• UPS or power protection recommendations.

11.3 The manufacturer shall supply an installation checklist covering:

• Room readiness.

• Power and network connectivity.

• Safety and emergency shutdown systems.

12. Documentation, Training & Support

12.1 The manufacturer shall provide complete technical documentation, including:

• Installation, operation, and maintenance manuals.

• System architecture and interface descriptions.

• Preventive maintenance schedules and checklists.

12.2 A maintenance toolbox and any required special tools shall be provided to support routine and corrective maintenance.

12.3 The manufacturer shall provide training to the customer’s simulator technicians and instructors, covering:

• System operation and configuration.

• Routine maintenance procedures.

• Troubleshooting and basic repairs.

12.4 The manufacturer shall maintain maintenance centers or equivalent support capability, with access to spare parts and technical assistance for the life of the simulator.

12.5 A defined warranty period and spare-parts/obsolescence management plan shall be included.

13. Upgrade & Growth Requirements

13.1 The simulator shall be designed to support future upgrades, including but not limited to:

• Avionics changes or additions to match evolving aircraft configurations.

• Enhanced or expanded visual databases.

• Additional mission modules (e.g., SAR, firefighting, HEMS, police, cargo, offshore, military operations).

13.2 The hardware and I/O architecture shall accommodate:

• Additional panels, controls, or mission operator stations.

• Possible integration of NVIS, VR/MR/AR training options, and advanced visual systems.