Start here
A few places to begin, from the aircraft’s story to the people who fly it.
Aircraft and simulator background
The Superjet 100 is a regional airliner powered by two SaM146 turbofans. Its first flight took place on 19 May 2008 at Komsomolsk-on-Amur. Type certification followed in January 2011, and Armavia began commercial passenger flying that April.
Sukhoi Superjet 100
United Aircraft Corporation · Read more ↗The SU95X systems project
Headwind describes SU95X as a maintained project derived from FlyByWire systems. That development lineage describes the simulator implementation, whose flight deck and systems remain documented by Headwind.
Sukhoi Superjet 100
Headwind Simulations · Read more ↗The documented SU95 package
The official aircraft release API lists SU95 assets with v0.6.1 in December 2024. Later v0.8.1 assets for A339 identify the A330 project, so they are kept separate from the Superjet's release history.
Sukhoi Superjet 100
Headwind Simulations · Read more ↗Meet Sukhoi Superjet 100
The Superjet 100 is a regional airliner powered by two SaM146 turbofans. Its first flight took place on 19 May 2008 at Komsomolsk-on-Amur. Type certification followed in January 2011, and Armavia began commercial passenger flying that April.
Headwind's SU95X is a simulator project derived from FlyByWire systems. Its release record includes a SU95 package in v0.6.1, published in December 2024; later A339-only assets belong to a separate aircraft project.
Sukhoi Superjet 100
Sukhoi → · Explore the family →
Sukhoi Superjet 100
United Aircraft Corporation · Superjet 100 ↗Aircraft type designators
No type designator selected for this reference.
History & design
From first flight to airline service
The Superjet's first prototype flew on 19 May 2008 from Komsomolsk-on-Amur, with Alexander Yablontsev and Leonid Chikunov at the controls. The 65-minute flight followed the aircraft's September 2007 rollout. Type certification came in January 2011, followed by Armavia's first passenger service from Yerevan to Moscow in April.
United Aircraft Corporation · Superjet 100 ↗Programme chronology; 19 May 2008 first flight; January and April 2011 milestones; SaM146 engines
Systems & details
The SU95X systems project
Headwind describes SU95X as a maintained project derived from FlyByWire systems. That development lineage describes the simulator implementation, whose flight deck and systems remain documented by Headwind.
The documented SU95 package
The official aircraft release API lists SU95 assets with v0.6.1 in December 2024. Later v0.8.1 assets for A339 identify the A330 project, so they are kept separate from the Superjet's release history.
In your simulator
Systems, equipment and documentation for each developer’s aircraft.
MSFS 2020Headwind Simulations Sukhoi Superjet100-95
Headwind Simulations · Released
Headwind Simulations Sukhoi Superjet100-95
Headwind Simulations · Released
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.
Manufacturer history
Superjet 100Sukhoi Superjet 100
Programme chronology; 19 May 2008 first flight; January and April 2011 milestones; SaM146 engines
United Aircraft Corporation · Read the source ↗Developer documentation
Current SU95 productSukhoi Superjet 100
Developer SU95X product
Headwind Simulations · Read the source ↗Official recent releases and artifact contentsSukhoi Superjet 100
Official aircraft release API v0.6.1 assets
Headwind Simulations · Read the source ↗Read the original documentation from the people who created it. Manuals open on their publisher’s website.
Manufacturer history
Superjet 100United Aircraft Corporation · Programme chronology; 19 May 2008 first flight; January and April 2011 milestones; SaM146 enginesDeveloper documentation
Current SU95 productHeadwind Simulations · Developer SU95X product Official recent releases and artifact contentsHeadwind Simulations · Official aircraft release API v0.6.1 assetsBuilt-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 · 1 profile choice
Headwind Simulations Sukhoi Superjet100-95
Headwind Simulations · Free and Pro · Revision 2 · Inherited starting point
MSFS 2020
A regional-jet family represented by Headwind's SU95X project.
Headwind Simulations Sukhoi Superjet100-95
A regional-jet family represented by Headwind's SU95X project.
Aircraft and simulator scope
- Headwind Simulations Sukhoi Superjet100-95 · Headwind Simulations · MSFS 2020 · Add-on starting point
The simulator model and controls
Headwind Simulations Sukhoi Superjet100-95 is the selected Headwind Simulations configuration.
How this profile feels
The spring stays independent of airspeed. Directed aerodynamic loading is omitted.
Pitch-trim relief is off. Autopilot following is off.
Aircraft and configuration
The Superjet 100 is a regional airliner powered by two SaM146 turbofans. Its first flight took place on 19 May 2008 at Komsomolsk-on-Amur. Type certification followed in January 2011, and Armavia began commercial passenger flying that April.
The SU95X systems project
Headwind describes SU95X as a maintained project derived from FlyByWire systems. That development lineage describes the simulator implementation, whose flight deck and systems remain documented by Headwind.
The documented SU95 package
The official aircraft release API lists SU95 assets with v0.6.1 in December 2024. Later v0.8.1 assets for A339 identify the A330 project, so they are kept separate from the Superjet's release history.
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
InheritedHeadwind Simulations Sukhoi Superjet100-95 is the selected Headwind Simulations configuration.
Flight controls
InheritedA regional-jet family represented by Headwind's SU95X project.
Trim
InheritedThe profile uses the trim behaviour configured below. Pitch relief is off, with stored authority 0; roll authority is 0.
Autopilot and stability
InheritedAutopilot following is off; the configured spring and load retain the hardware feel. Separate neutral hold is on at strength 0.28, when a supported autopilot state admits it.
Equipment
InheritedThe Superjet 100 is a regional airliner powered by two SaM146 turbofans. Its first flight took place on 19 May 2008 at Komsomolsk-on-Amur. Type certification followed in January 2011, and Armavia began commercial passenger flying that April.
Speeds and limits
InheritedThe indicated-speed references set the profile response scale; they are separate from aircraft operating limits.
Simulator integration
InheritedThe profile targets msfs2020. 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.55 | What it controls and whyHeadwind describes SU95X as a maintained project derived from FlyByWire systems. The baseline spring is 0.55. Low-speed spring blending is off. |
| Master force gain | Starting value0.85 | 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 stored 0 aerodynamic-load gain is inactive under the fixed-centre control law. |
| Force tuning speed/reference | Starting value230 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 value65 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. The pitch spring-travel curve reaches output 1 at input 1. The roll spring-travel curve reaches output 0.3 at input 1. Spring-travel response contributes separately to axis balance. |
| 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. Separate neutral hold is on at strength 0.28, when a supported autopilot state admits it. |
| Autopilot neutral hold | Starting valueEnabled | 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 49 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.55 | What it controls and whyHeadwind describes SU95X as a maintained project derived from FlyByWire systems. The baseline spring is 0.55. Low-speed spring blending is off. |
| Spring deadband | Starting value0.01 | What it controls and whySets travel around the centre before the baseline spring resists. Smaller values engage it sooner. |
| Starting centering force | Starting value0.03 | What it controls and whyThe centre preload is 0.03. It ramps outside the 0.01 deadband across 0.05 travel, shaping the passive centre independently of aircraft autotrim. |
| Center Starting Force Transition | Starting value0.05 | What it controls and whySets the travel used to ramp in centre preload. Wider intervals make its onset more gradual. |
| Profile force gain | Starting value0 | What it controls and whyThe stored 0 aerodynamic-load gain is inactive under the fixed-centre control law. |
| Master force gain | Starting value0.85 | 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 value0.55 | 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 value8 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 value65 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 value230 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 value2 | 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. The pitch spring-travel curve reaches output 1 at input 1. The roll spring-travel curve reaches output 0.3 at input 1. Spring-travel response contributes separately to axis balance. |
| 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. |
| Travel Enabled | Starting valueEnabled | What it controls and whyApplies the configured pitch and roll spring travel curves. |
| Output | Starting value1 | What it controls and whySets response at the second pitch-curve point; it is an endpoint only if its input position is full travel. |
| Output | Starting value0.3 | What it controls and whySets response at the second roll-curve point; its input position and other points determine the travel law. |
| 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 whyThe profile uses the trim behaviour configured below. Pitch relief is off, with stored authority 0; roll authority is 0. |
| 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 whyEnables local force trim, separate from aircraft-owned trim and add-on integration qualification. |
| GLoad Enabled | Starting valueDisabled | 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. Separate neutral hold is on at strength 0.28, when a supported autopilot state admits it. |
| Autopilot follow authority | Starting value0.1 | 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 valueEnabled | What it controls and whyPermits centering hold during a supported AP state, separate from following a moving target. |
| Autopilot neutral hold strength | Starting value0.28 | 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.06 | What it controls and whySets stall-buffet strength. Zero removes the cue without changing simulator stalls or warnings. |
| Gain | Starting value0.06 | 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 value3 | What it controls and whySets the final flap index for detent normalization. UP plus three detents uses maximum index3. |
| Minimum flap index | Starting value2 | 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 valueDisabled | What it controls and whyEnables ground effects; each still needs its own strength and contact or motion telemetry. |
| Gain | Starting value0 | What it controls and whySets rolling texture strength, modified by speed, surface and undercarriage configuration. |
| Gain | Starting value0 | What it controls and whySets gear-bump texture during ground motion, separate from touchdown impact. |
| Gain | Starting value0 | 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 valueDisabled | 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 | What it controls and whySets texture from observed gear movement, separate from aerodynamic and touchdown effects. |
Limits and open questions
- Passive sidestick with fixed spring. FBW protections and surface deflections cannot backdrive the inceptor.
- Automatic stabilizer trim does not move passive sidestick neutral. Pitch/roll relief and hydraulic centering disabled.
- Passive sidestick does not motor-follow AP. Follow and hold remain disabled.
- Released MSFS2020 identity only. No MSFS2024 compatibility claim or inherited A339 release/version claim; no A320 input events or custom law forces injected.
- 230 KIAS is an estimated control-feel reference, not cruise TAS, V-speeds or an operating limit.
- Spring 0.55, lateral scale 1, trim relief 0/0; editable estimates, not measured hand forces.
- Physical and installed-aircraft checks are deferred. Save this profile as the aircraft default if telemetry omits its developer or configuration.
- Only actual accessory-position changes drive movement textures. No pressure-dependent failures, guessed servo outputs or input compensation.
- 2026-10-01, Airbus passive sidestick law (docs/poh/a320neo-feel-spec.md, SAE 861801, BEA AF447 3.2): pitch spring 0.55 at master gain 0.85, constant with airspeed, G and trim; roll at 30 % of pitch (published pitch:roll 3-4:1, 10 daN at 16 deg pitch, 2-3.5 daN at 20 deg roll); a 0.03 centre starting force over a 0.01 deadband for the 0.5 daN breakout (5 % of full pitch force); autopilot neutral hold 0.28 for the 5 daN override of the neutral lock; weak stall and Mach buffet (0.06), which the BEA describes as weakly transmitted to the sidestick; no turbulence, overspeed, spoiler, flap, gear, ground, engine, mechanical or drag cues.
- No type-specific sidestick force data is published; the Airbus passive sidestick values apply.
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 ↗
