Airbus A320neo
Airbus A320neo: Fixed centering represents the passive Airbus sidestick.
Aircraft and simulator scope
- Airbus A320neo · MSFS 2020 · Variant starting point
- Airbus A320neo · MSFS 2024 · Variant starting point
- Airbus A320neo · X-Plane 11 · Variant starting point
- Airbus A320neo · X-Plane 12 · Variant starting point
Preserved Microsoft/iniBuilds A320neo and A321LR manuals; A319, ceo, A321neo and XLR distinctions remain family inheritance. · Selected choice: Airbus A320neo. Documentary scope does not establish every variant, add-on revision or simulator binding.
The simulator model and controls
The original A320 first flew in 1987 and entered service in 1988. Airbus subsequently stretched the design into the A321 and shortened it into the A319 and A318. The family made digital fly-by-wire and sidestick controls familiar to a large part of the airline world.
This starting point selects Airbus A320neo. Its aircraft-level settings do not select a particular developer’s custom systems.
How this profile feels
The spring stays independent of airspeed. Directed aerodynamic loading is omitted.
Pitch-trim relief is off. Autopilot following is off.
Controls and trim
Airbus's cockpit description establishes sidesticks and digital fly-by-wire across this family. FlyByWire's A32NX documentation describes passive spring centering, separate sidestick priority and no autopilot backdrive. That A32NX account is mechanism context for the family, rather than an interface specification for Fenix, ToLiss or another add-on. Aircraft autotrim and control-law changes act on aircraft response without creating a new aerodynamic load at a passive stick.
About the values
The gains are normalized profile settings. They describe the chosen effect balance; hand force depends on the device and its output limits. IAS references are tuning values rather than operating limits. Physical acceptance of this revision remains pending.
What the documentation establishes
The preserved A320 manual names the simulator A320 implementation; the companion manual is specifically A321.
The A321 procedure uses autopilot guidance; neutral holding and disabled following are preset choices, not evidence of absent autopilot.
A 250-knot descent example is a procedure-specific value, not the preset's universal control-force reference.
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
ReviewedThis starting point selects Airbus A320neo. Its aircraft-level settings do not select a particular developer’s custom systems.
Flight controls
Not yet reviewedAirbus's cockpit description establishes sidesticks and digital fly-by-wire across this family. FlyByWire's A32NX documentation describes passive spring centering, separate sidestick priority and no autopilot backdrive. That A32NX account is mechanism context for the family, rather than an interface specification for Fenix, ToLiss or another add-on. Aircraft autotrim and control-law changes act on aircraft response without creating a new aerodynamic load at a passive stick.
Trim
Not yet reviewedAutomatic aircraft trim is separate from the passive sidestick centre, so disabled hardware trim relief preserves the selected fixed-centre approximation. Pitch relief is off, with stored authority 0; roll authority is 0.
Autopilot and stability
ReviewedAutopilot 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
Not yet reviewedGear, flap and ground cues follow the selected settings and available simulator-reported states.
Speeds and limits
ReviewedThe indicated-speed references set the profile response scale; they are separate from aircraft operating limits.
Simulator integration
Not yet reviewedThe profile targets msfs2020, msfs2024, xplane11, xplane12. Add-on-specific controls use only the supported references configured by this profile.
Force-feedback settings
Not yet reviewedThe 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 whyFixed centering represents the passive Airbus sidestick. Pitch and roll spring-travel curves may differ without adding direct surface-force feedback. 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.04 | What it controls and whyThe stored 0.04 aerodynamic-load gain is inactive under the fixed-centre control law. |
| Force tuning speed/reference | Starting value260.0 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 value90 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 whyFixed centering represents the passive Airbus sidestick. Pitch and roll spring-travel curves may differ without adding direct surface-force feedback. 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.04 | What it controls and whyThe stored 0.04 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.5 | 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 value20 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 value90 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 value260.0 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. 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 whyAutomatic aircraft trim is separate from the passive sidestick centre, so disabled hardware trim relief preserves the selected fixed-centre approximation. 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.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 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 value4 | 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
- The A321 joystick check documents control-surface response, but the extracted text does not establish the controller's physical feel or force schedule.
- The joystick check does not document autotrim ownership or physical trim feedback; disabled preset trim remains a scoped approximation.
- Much of the manual is image content; exact equipment actuation and all seven variants cannot be newly established from its extracted text.
- Joystick checks and autopilot guidance do not specify external force output or controller-neutral ownership.
- A passive controller approximation does not establish measured A320-family spring force or a zero aerodynamic-feedback requirement.
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.