Start here
A few places to begin, from the aircraft’s story to the people who fly it.
Aircraft and configuration
The AW139 type certificate describes two PT6C engines, a five-blade main rotor, four-blade tail rotor and retractable tricycle landing gear. Its rotor-speed limits distinguish powered and unpowered operation, and VNE changes with altitude, temperature and power state.
Leonardo AW139 Long Nose
EASA · Read more ↗Meet Leonardo AW139 Long Nose
The AW139 type certificate describes two PT6C engines, a five-blade main rotor, four-blade tail rotor and retractable tricycle landing gear. Its rotor-speed limits distinguish powered and unpowered operation, and VNE changes with altitude, temperature and power state.
History & design
Forty-five minutes over Cascina Costa
The first AW139 flew from Cascina Costa di Samarate on 3 February 2001. Its 45-minute sortie included hovering, lateral and forward flight, with checks of handling and aircraft systems.
Leonardo · AW139 first-flight twentieth anniversary ↗Leonardo twentieth-anniversary account, February 2021
A multi-role intermediate twin
Initial deliveries began in early 2004. By Leonardo’s 2021 anniversary account, the helicopter was serving offshore transport alongside rescue, air ambulance, law-enforcement and other public-service roles. Assembly in Italy and Philadelphia supported that expanding customer base.
Leonardo · AW139 first-flight twentieth anniversary ↗Leonardo twentieth-anniversary account, February 2021
A platform adapted to many missions
By its February 2021 anniversary review, Leonardo reported more than three million fleet hours and customers in over seventy countries. Its account divided the fleet across offshore transport and public-service work such as rescue, air ambulance and law enforcement. That history explains the range of cabin, rescue and mission equipment associated with the AW139. The figures are a dated programme snapshot, while the long-nose X-Rotors aircraft identifies the specific simulator configuration.
Leonardo · AW139 first-flight twentieth anniversary ↗Leonardo twentieth-anniversary release, 3 February 2021
Systems & details
Controls and equipment
X-Rotors' long-nose X-Plane 12 aircraft includes Primus Epic Phase 7 avionics, a four-axis flight director and separate cyclic and collective force-trim functions. Winch, float and filter fits are offered.
In your simulator
No released simulator product is listed for this aircraft in the developers reviewed. Announced products are excluded.
Manuals & resources
Find your next read
Choose a topic for a short introduction and a link to the original source. Simulator references identify the developer and edition they cover.
Simulator documentation
Controls and equipmentLeonardo AW139 Long Nose
X-Rotors' long-nose X-Plane 12 aircraft includes Primus Epic Phase 7 avionics, a four-axis flight director and separate cyclic and collective force-trim functions. Winch, float and filter fits are offered.
AW139 version 5.05 product · systems and equipment
X-Rotors · Read the source ↗Read the original documentation from the people who created it. Manuals open on their publisher’s website.
Aircraft documentation
Leonardo AW139 Long Nose — aircraft documentationEASA · AW139 version 5.05 product · systems and equipmentSimulator documentation
Leonardo AW139 Long Nose — simulator documentationX-Rotors · AW139 version 5.05 product · systems and equipmentAircraft history
AW139 first-flight twentieth anniversaryLeonardo · Leonardo twentieth-anniversary account, February 2021Built-in force-feedback profiles
Read the documentary basis, editable starting settings and remaining questions for the aircraft you fly. Each explanation refers to the exact profile revision shown.
Catalogue programme-20261011-v3 · 2 profile choices
X-Rotors AW139 Long Nose (XP12)
X-Rotors · Free and Pro · Revision 1 · Inherited starting point
X-Plane 12
The twin-engine AW139 with a five-blade main rotor and retractable gear.
Leonardo AW139 Long Nose
Free and Pro · Revision 1 · Partial review
MSFS 2020 · MSFS 2024 · X-Plane 12
The twin-engine AW139 with a five-blade main rotor and retractable gear.
X-Rotors AW139 Long Nose (XP12)
The twin-engine AW139 with a five-blade main rotor and retractable gear.
Aircraft and simulator scope
- X-Rotors AW139 Long Nose (XP12) · X-Rotors · X-Plane 12 · Add-on starting point
The simulator model and controls
X-Rotors AW139 Long Nose (XP12) is the selected X-Rotors configuration.
How this profile feels
The spring stays independent of airspeed. Directed aerodynamic loading is omitted.
Local force trim is off. Autopilot following is off.
Aircraft and configuration
The AW139 type certificate describes two PT6C engines, a five-blade main rotor, four-blade tail rotor and retractable tricycle landing gear. Its rotor-speed limits distinguish powered and unpowered operation, and VNE changes with altitude, temperature and power state.
Controls and equipment
X-Rotors' long-nose X-Plane 12 aircraft includes Primus Epic Phase 7 avionics, a four-axis flight director and separate cyclic and collective force-trim functions. Winch, float and filter fits are offered.
About the values
Strengths are normalized hardware-feel settings. They set the effect balance; hand force depends on the device and its limits. The IAS reference is a tuning value.
Documentary review and sources
These decisions describe the documentary basis and remaining gaps for this revision. Aircraft documentation and a starting setting describe different kinds of evidence.
Aircraft and variant
InheritedX-Rotors AW139 Long Nose (XP12) is the selected X-Rotors configuration.
Flight controls
InheritedThe twin-engine AW139 with a five-blade main rotor and retractable gear.
Trim
InheritedLocal force trim is off. Autopilot following is off.
Autopilot and stability
InheritedAutopilot following is off; the configured spring and load retain the hardware feel.
Equipment
InheritedThe AW139 type certificate describes two PT6C engines, a five-blade main rotor, four-blade tail rotor and retractable tricycle landing gear. Its rotor-speed limits distinguish powered and unpowered operation, and VNE changes with altitude, temperature and power state.
Speeds and limits
InheritedThe indicated-speed references set the profile response scale; they are separate from aircraft operating limits.
Simulator integration
InheritedThe profile targets xplane12. Add-on-specific controls use only the supported references configured by this profile.
Force-feedback settings
InheritedThe settings define the profile’s effect balance. Device output limits affect physical hand force.
Starting settings and their rationale
These configured values are starting estimates. The explanations describe what each setting controls; physical validation appears separately below.
| Setting | Starting value | What it controls and why |
|---|---|---|
| Spring strength | Starting value0.1 | What it controls and whyRotor blades: Five main · four tail. The baseline spring is 0.1. Low-speed spring blending is off. |
| Master force gain | Starting value0.65 | What it controls and whyScales overall profile strength while preserving effect balance, subject to device and output limits. |
| Profile force gain | Starting value0 | What it controls and whyThe 0 gain omits sustained directed airspeed loading. Spring resistance remains independent. |
| Force tuning speed/reference | Starting value135 kt | What it controls and whySets the IAS reference for aerodynamic loading. It is an estimate, not published cruise TAS or a flight limit. |
| Spring response reference speed | Starting value70.0 kt | What it controls and whySets the IAS where the low-speed blend reaches baseline strength; high-speed stiffening also uses it. |
| Aileron force scale | Starting value1 | What it controls and whyRoll and pitch aerodynamic scales are 1 and 1, respectively. These stored weights do not create directed aerodynamic loading while that term is inactive. No custom spring-travel curve is enabled. |
| Elevator force scale | Starting value1 | What it controls and whyScales pitch aerodynamic loading; pitch spring travel and trim responses are separate settings. |
| Trim feel | Starting valueDisabled | What it controls and whyRetained for compatibility and group membership. Trim relief, rather than this flag, controls centre movement. |
| Trim relief | Starting valueDisabled | What it controls and whyAllows trim relief with supported control law and valid telemetry. Axis authorities set its amount. |
| Autopilot follow | Starting valueDisabled | What it controls and whyAutopilot following is off; the configured spring and load retain the hardware feel. |
| Autopilot neutral hold | Starting valueDisabled | What it controls and whyPermits centering hold during a supported AP state, separate from following a moving target. |
| Output force limit | Starting value0.55 | What it controls and whyCaps directed-force output. Native spring effects and device limits remain separate. |
All 44 starting settings and their rationale
The settings define the profile’s effect balance. Device output limits affect physical hand force.
| Setting | Starting value | What it controls and why |
|---|---|---|
| Spring strength | Starting value0.1 | What it controls and whyRotor blades: Five main · four tail. The baseline spring is 0.1. Low-speed spring blending is off. |
| Spring deadband | Starting value0.02 | What it controls and whySets travel around the centre before the baseline spring resists. Smaller values engage it sooner. |
| Profile force gain | Starting value0 | What it controls and whyThe 0 gain omits sustained directed airspeed loading. Spring resistance remains independent. |
| Master force gain | Starting value0.65 | What it controls and whyScales overall profile strength while preserving effect balance, subject to device and output limits. |
| QBlend Enabled | Starting valueDisabled | What it controls and whyAllows baseline spring strength to rise with indicated airspeed where the control law permits it. |
| QSpring Minimum Factor | Starting value1 | What it controls and whySets low-speed spring strength as a fraction of baseline when blending is enabled. One keeps full strength. |
| QSpring Start Knots | Starting value19.6 kt | What it controls and whySets the IAS where the low-speed spring blend starts rising. This is a feel threshold, not a flight limit. |
| Spring response reference speed | Starting value70.0 kt | What it controls and whySets the IAS where the low-speed blend reaches baseline strength; high-speed stiffening also uses it. |
| Force tuning speed/reference | Starting value135 kt | What it controls and whySets the IAS reference for aerodynamic loading. It is an estimate, not published cruise TAS or a flight limit. |
| Airspeed spring stiffening gain | Starting value0 | What it controls and whyAdds permitted spring resistance above the full-blend speed. Zero removes this high-speed increase. |
| Airspeed spring stiffening limit | Starting value5 | What it controls and whyLimits the squared airspeed ratio used for high-speed spring stiffening; it is not a device-force cap. |
| Aileron force scale | Starting value1 | What it controls and whyRoll and pitch aerodynamic scales are 1 and 1, respectively. These stored weights do not create directed aerodynamic loading while that term is inactive. No custom spring-travel curve is enabled. |
| Elevator force scale | Starting value1 | What it controls and whyScales pitch aerodynamic loading; pitch spring travel and trim responses are separate settings. |
| Output force limit | Starting value0.55 | What it controls and whyCaps directed-force output. Native spring effects and device limits remain separate. |
| Trim feel | Starting valueDisabled | What it controls and whyRetained for compatibility and group membership. Trim relief, rather than this flag, controls centre movement. |
| Trim relief | Starting valueDisabled | What it controls and whyAllows trim relief with supported control law and valid telemetry. Axis authorities set its amount. |
| Elevator Authority | Starting value0 | What it controls and whyScales supported pitch-trim relief and permitted centre movement. Zero removes pitch response. |
| Aileron Authority | Starting value0 | What it controls and whyScales supported roll-trim relief and permitted centre movement. Zero removes roll response. |
| Force Trim Enabled | Starting valueDisabled | What it controls and whyX-Rotors' long-nose X-Plane 12 aircraft includes Primus Epic Phase 7 avionics, a four-axis flight director and separate cyclic and collective force-trim functions. Local force trim is off. The stored latch parameters are inactive; the profile does not supply a local hold-where-left neutral. |
| GLoad Enabled | Starting valueEnabled | What it controls and whyAllows load-factor changes to modify permitted spring laws. Passive fly-by-wire feel can suppress it. |
| Rate Damping Enabled | Starting valueDisabled | What it controls and whyEnables rate damping with the configured coefficients and control law. |
| Autopilot follow | Starting valueDisabled | What it controls and whyAutopilot following is off; the configured spring and load retain the hardware feel. |
| Autopilot follow authority | Starting value0.05 | What it controls and whySets admitted AP-follow gain, not a percentage of travel. Runtime ownership and input limits still apply. |
| Autopilot neutral hold | Starting valueDisabled | What it controls and whyPermits centering hold during a supported AP state, separate from following a moving target. |
| Autopilot neutral hold strength | Starting value0.6 | What it controls and whySets admitted AP neutral-hold strength; inactive while neutral hold is disabled. |
| Enabled | Starting valueEnabled | What it controls and whyEnables aerodynamic cues; each still needs nonzero strength and its simulator conditions. |
| Gain | Starting value0 | What it controls and whySets stall-buffet strength. Zero removes the cue without changing simulator stalls or warnings. |
| Gain | Starting value0 | What it controls and whySets high-Mach buffet strength; onset and full-strength thresholds are separate. |
| Gain | Starting value0 | What it controls and whySets flap buffet at the configured position and speed gates. Flap movement texture is separate. |
| Maximum flap index | Starting value1 | What it controls and whySets the final flap index for detent normalization. UP plus three detents uses maximum index3. |
| Minimum flap index | Starting value1 | What it controls and whySets the first flap detent that admits buffet; this is a handle index, not degrees. |
| Gain | Starting value0 | What it controls and whySets gear aerodynamic buffet; movement and ground-contact cues are separate. |
| Shaker Enabled | Starting valueDisabled | What it controls and whyPermits shaker at supported warning conditions; the switch does not establish aircraft equipment. |
| Stick shaker amplitude | Starting value0.5 | What it controls and whySets triggered shaker strength; inactive while the shaker feature is disabled. |
| Enabled | Starting valueEnabled | What it controls and whyEnables ground effects; each still needs its own strength and contact or motion telemetry. |
| Gain | Starting value0.1 | What it controls and whySets rolling texture strength, modified by speed, surface and undercarriage configuration. |
| Gain | Starting value0.08 | What it controls and whySets gear-bump texture during ground motion, separate from touchdown impact. |
| Gain | Starting value0.2 | What it controls and whySets landing-impact strength; landing telemetry and response shape determine the pulse. |
| Gain | Starting value0 | What it controls and whySets reverse-thrust vibration with valid reverser and engine conditions. Zero removes the cue. |
| Enabled | Starting valueEnabled | What it controls and whyEnables engine cues with nonzero settings and valid running-engine telemetry. |
| Gain | Starting value0 | What it controls and whySets estimated engine vibration using configured telemetry and response, not measured cockpit vibration. |
| Enabled | Starting valueEnabled | What it controls and whyEnables accessory cues with configured strengths and observed accessory movement. |
| Gain | Starting value0 | What it controls and whySets texture from observed flap movement; a command without movement does not establish the cue. |
| Gain | Starting value0.02 | What it controls and whySets texture from observed gear movement, separate from aerodynamic and touchdown effects. |
Limits and open questions
- Cyclic resistance, damping and airframe textures are editable estimates, not measured grip forces. Installed-product and physical acceptance remain deferred.
- Fixed physical neutral is an approximation. Add-on trim, force-trim release, virtual centering, SAS and autopilot servo outputs are not synchronized with hardware. Local FTR, follow-up trim, both fixed-wing trim paths and AP follow/hold are disabled.
- No invented hydraulic-failure force, mast moment, collective-force axis, tail-rotor force, variable VNE or retreating-blade-stall warning. Reported custom sound or visual vibration does not establish a force telemetry contract.
- ETL and low-speed descent cues, where enabled, use generic heuristics and are not aircraft-specific warnings. All speed references are tuning choices, not operating limits.
- Documentary title patterns require a developer/configuration identifier. When identity is ambiguous or omitted, select the applicable profile and save it as the aircraft default.
- XP12 read-only native RPM and actual gear motion. Included reference guide is not publicly acquired; custom FD/SAS/FTR signals remain open. XP11 excluded.
- 313RPM operator reference;135KIAS tuning reference, not VNE. No fixed RBS or warning threshold.
- Standard XP12 main-rotor angular speed is converted to RPM and normalized by the stated reference. Rotor index applicability requires installed verification. Missing RPM silences rotor rumble; the forward-flight n/rev channel can fall back to combustion and a default frequency.
Physical validation
No physical force validation is recorded in this public catalogue for this revision. Documentary review and software checks do not establish how a particular device feels.
Discuss this aircraft (0)
Questions, observations and useful sources from the community.
No published discussions yet. Bring a question or share a useful source.
Open aircraft discussions →Content expanded · What’s new
Something missing or a source that needs attention?
Suggest a correction ↗
