Start here
A few places to begin, from the aircraft’s story to the people who fly it.
Meet the aircraft
Douglas introduced the DC-9 in 1965 to serve short routes. Its rear-mounted twin-engine layout and two-crew flight deck helped make the many DC-9 versions economical for airlines. The simulator products below cover different members of that family and have their own edition details.
McDonnell Douglas DC-9
Smithsonian National Air and Space Museum · Read more ↗Meet McDonnell Douglas DC-9
Douglas introduced the DC-9 in 1965 for short-range routes. Its rear-mounted twin engines and two-crew flight deck supported economical airline operation. The family developed through numerous versions, several of which appear in separate simulator products.
McDonnell Douglas DC-9
McDonnell Douglas → · Explore the family →
McDonnell Douglas DC-9
Smithsonian National Air and Space Museum · Trans-Texas Airlines Douglas DC-9 ↗Aircraft type designators
No type designator selected for this reference.
History & design
Jet service for shorter routes
Delta introduced daily scheduled DC-9 service in December 1965, bringing jet transport to routes previously served by propeller aircraft. The short original DC-9 filled a different role from the airline’s larger DC-8 and Convair 880.
Delta Flight Museum · Douglas DC-9 1965-1993, 2008-2014 ↗Delta Flight Museum: family history and DC-9-14 technical summary
The stretched nine
Delta received its first DC-9-32 in April 1967. Its fuselage was fifteen feet longer than the original model. The figures here are explicitly the earlier DC-9-14 reference; they do not describe the longer -32, -41 or -51.
Delta Flight Museum · Douglas DC-9 1965-1993, 2008-2014 ↗Delta Flight Museum: family history and DC-9-14 technical summary
Systems & details
Retirement was not the end of Delta’s story
The airline retired its early DC-9 fleet in 1993, then acquired more through the 2008 Northwest merger. Ceremonial farewell flights took place in January 2014, followed by a final service flight later that month. The MD-80, MD-90 and 717 continued the design’s broader lineage.
In your simulator
Systems, equipment and documentation for each developer’s aircraft.
Compare simulator versions →MSFS 2020 · MSFS 2024DC-9-10 / -30 Passenger and Freighter
Sky Simulations · Released
DC-9-10 / -30 Passenger and Freighter
Sky Simulations · Released
MSFS 2024DC-9-21 / -41 / -51
Sky Simulations · Released
DC-9-21 / -41 / -51
Sky 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.
Developer documentation
Sky Simulations McDonnell Douglas DC-9DC-9-10 / -30 Passenger and Freighter · MSFS 2020 · MSFS 2024
Read the developer document for this specific product and simulator edition.
Product listing captured 28 September 2026; DC-9-10/30, MSFS 2020 and 2024
Sky Simulations / Just Flight · Read the source ↗Sky Simulations DC-9 release changesDC-9-10 / -30 Passenger and Freighter · MSFS 2020 · MSFS 2024
Read the developer document for this specific product and simulator edition.
Release notes captured 28 September 2026; v3.2.5 and v3.3.0
Sky Simulations / Just Flight · Read the source ↗Sky Simulations DC-9 Series 21, 41 and 51DC-9-21 / -41 / -51 · MSFS 2024
Read the developer document for this specific product and simulator edition.
Separate product listing captured 28 September 2026; MSFS 2024
Sky Simulations / Just Flight · Read the source ↗Read the original documentation from the people who created it. Manuals open on their publisher’s website.
Museum aircraft history
Trans-Texas Airlines Douglas DC-9Smithsonian National Air and Space Museum · Museum aircraft-history caption captured 29 September 2026; Douglas DC-9 design and 1965 introductionDeveloper documentation
Sky Simulations McDonnell Douglas DC-9Sky Simulations / Just Flight · Product listing captured 28 September 2026; DC-9-10/30, MSFS 2020 and 2024 Sky Simulations DC-9 release changesSky Simulations / Just Flight · Release notes captured 28 September 2026; v3.2.5 and v3.3.0 Sky Simulations DC-9 Series 21, 41 and 51Sky Simulations / Just Flight · Separate product listing captured 28 September 2026; MSFS 2024Aircraft reference
Douglas DC-9 1965-1993, 2008-2014Delta Flight Museum · Delta Flight Museum: family history and DC-9-14 technical summaryBuilt-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-20261022-v1 · 2 profile choices
Sky Simulations DC-9-10 / DC-9-30
Sky Simulations · Free and Pro · Revision 2 · Inherited starting point
MSFS 2020 · MSFS 2024
Douglas developed the DC-9 as a short-range jet in the 1960s, with engines mounted at the rear of the fuselage.
Sky Simulations DC-9-21 / DC-9-41 / DC-9-51
Sky Simulations · Free and Pro · Revision 2 · Inherited starting point
MSFS 2024
Douglas developed the DC-9 as a short-range jet in the 1960s, with engines mounted at the rear of the fuselage.
Sky Simulations DC-9-10 / DC-9-30
Douglas developed the DC-9 as a short-range jet in the 1960s, with engines mounted at the rear of the fuselage.
Aircraft and simulator scope
- Sky Simulations DC-9-10 / DC-9-30 · Sky Simulations · MSFS 2020 · Add-on starting point
- Sky Simulations DC-9-10 / DC-9-30 · Sky Simulations · MSFS 2024 · Add-on starting point
The simulator model and controls
Sky Simulations DC-9-10 / DC-9-30 is the selected Sky Simulations configuration.
How this profile feels
Spring resistance builds with the selected airspeed response. A separate aerodynamic term adds speed-dependent control load.
Pitch-trim relief is off. Autopilot following is off.
Aircraft and configuration
Douglas introduced the DC-9 in 1965 for short-range routes. Its rear-mounted twin engines and two-crew flight deck supported economical airline operation. The family developed through numerous versions, several of which appear in separate simulator products.
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
InheritedSky Simulations DC-9-10 / DC-9-30 is the selected Sky Simulations configuration.
Flight controls
InheritedDouglas developed the DC-9 as a short-range jet in the 1960s, with engines mounted at the rear of the fuselage.
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.
Equipment
InheritedDouglas introduced the DC-9 in 1965 for short-range routes. Its rear-mounted twin engines and two-crew flight deck supported economical airline operation. The family developed through numerous versions, several of which appear in separate simulator products.
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, msfs2024. 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 whyThis profile uses reversible-control loading for McDonnell Douglas DC-9. The baseline spring is 0.55. Its low-speed blend reaches baseline strength at 65 KIAS. |
| 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.3 | What it controls and whyThe aerodynamic-load gain is 0.3 with an indicated-speed reference of 250 KIAS. This supplies speed-dependent loading alongside the spring. |
| Force tuning speed/reference | Starting value250 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 value0.8 | What it controls and whyRoll and pitch aerodynamic scales are 0.8 and 1, respectively. They set the aerodynamic axis balance. 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.55 | What it controls and whyThis profile uses reversible-control loading for McDonnell Douglas DC-9. The baseline spring is 0.55. Its low-speed blend reaches baseline strength at 65 KIAS. |
| Spring deadband | Starting value0.035 | What it controls and whySets travel around the centre before the baseline spring resists. Smaller values engage it sooner. |
| Profile force gain | Starting value0.3 | What it controls and whyThe aerodynamic-load gain is 0.3 with an indicated-speed reference of 250 KIAS. This supplies speed-dependent loading alongside the spring. |
| 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 valueEnabled | 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 value250 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.12 | What it controls and whyThe high-speed spring-stiffening gain is 0.12. It strengthens the permitted spring response above 65 KIAS, with the squared-speed ratio capped at 5. |
| 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 value0.8 | What it controls and whyRoll and pitch aerodynamic scales are 0.8 and 1, respectively. They set the aerodynamic axis balance. 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 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. |
| 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 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 value0 | 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.9 | 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.16 | What it controls and whySets rolling texture strength, modified by speed, surface and undercarriage configuration. |
| Gain | Starting value0.12 | What it controls and whySets gear-bump texture during ground motion, separate from touchdown impact. |
| Gain | Starting value0.3 | 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.06 | 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.12 | What it controls and whySets texture from observed flap movement; a command without movement does not establish the cue. |
| Gain | Starting value0.12 | What it controls and whySets texture from observed gear movement, separate from aerodynamic and touchdown effects. |
Limits and open questions
- Documentary starting point; installed-title capture and physical force acceptance are pending.
- Force amplitudes, damping and speed response are editable engineering estimates, not measured hand forces.
- No verified custom servo-target, trim geometry or hydraulic-failure interface. Autopilot follow, neutral hold, trim relief and hydraulic-loss forces remain off.
- Developer-qualified matching is based on documented product names. Save an aircraft default if live telemetry omits the developer.
- MSFS editions have different product versions; no equality of their systems or telemetry is assumed.
- The included operations and speeds PDFs were not acquired. Tab gearing, conditional boost and trim-neutral calibration remain unqualified.
- Inherited force magnitudes remain editable estimates; aircraft-specific settings for speed response, controls, trim, autopilot and enabled effects are retained. New physical feel acceptance is pending.
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 ↗