Björn Strey · CC BY-SA 2.0 · McDonnell Douglas MD-11 picturedThe MD-11 developed the DC-10 with a longer fuselage, winglets and a two-pilot electronic flight deck. It retained the trijet arrangement, including the centre engine at the base of the fin. Passenger and freighter versions served different markets.
Automated systems and fuel management formed part of the new design. Each simulator developer documents the systems, failures and variants included in its implementation.
More about this aircraft on AirframeDB
KLM’s final scheduled MD-11 passenger flight arrived in Amsterdam from Montreal on 26 October 2014. Three special sightseeing flights over the Netherlands were planned for 11 November. Keeping those events separate explains why accounts of the aircraft’s passenger-service farewell give different dates.
NASA’s history records Gordon Fullerton’s first MD-11 propulsion-controlled landing at Edwards on 29 August 1995. Special software translated commands into engine-thrust changes while the usual control surfaces remained still. It was an experimental backup-control programme, distinct from an ordinary airline flight or a real emergency.
First flight: January 10, 1990
Developed from: McDonnell Douglas DC-10
Schouten had grown up around the MD-11 because his father flew it. Reaching the same aircraft after jobs in smaller island transports and the MD-80 fulfilled a long-held ambition. By the time of the interview, the freighter was taking him around the world with Western Global Airlines.
The work did not follow a predictable airline pattern. Within a normal stretch of seventeen working days, destinations and schedules could change daily. He found it demanding, but valued visiting places outside the usual scheduled network. During the pandemic, busy cargo flying brought a complicated sense of good fortune: his part of aviation still needed crews while many other pilots faced unemployment.
Asked whether the MD-11’s approach speeds made it difficult, Bokomoko drew on earlier experience flying the 737 into high-altitude La Paz. That work had already made fast ground speeds familiar. The contributor regarded the MD-11’s speed as manageable and spoke positively about its braking and reverse thrust, while noting that conditions and equipment still mattered.
Other answers stressed the planning behind what passengers saw. Fuel remaining at arrival varied with the route and airline decisions, while takeoff flap selection followed prepared performance data. The replies offered a working pilot’s context for features that could seem unusual to an enthusiast, without treating every flight or operator as identical.
Miller’s view of propulsion-controlled flight changed when he saw the experimental MD-11 system working in the air. On its first attempt, its steady behaviour convinced him that the engineering team had achieved something significant. He subsequently pressed management to allow the programme to progress towards actual landings and further exploration of the test envelope.
That support mattered when the team considered switching off the hydraulic systems during a later experiment. Holding control surfaces still for a test was different from allowing them to move after hydraulic power disappeared. Miller helped obtain permission to investigate that uncertainty.
The MD-11 developed the DC-10 with a longer fuselage, winglets and a two-pilot electronic flight deck. It retained the trijet arrangement, including the centre engine at the base of the fin. Passenger and freighter versions served different markets.
This profile selects Rotate MD-11 for X-Plane 12.
Artificial feel accompanies the hydraulically powered controls. The spring stays independent of airspeed. Directed aerodynamic loading is omitted.
Automatic pitch trim and CWS are separate from a fixed hardware-centre choice. Pitch-trim relief is off. Autopilot following is off.
The MD-11 documentation describes automatic pitch trim, CWS/RCWS and multiple hydraulic systems. Passenger/freighter and GE/PW fits retain their own configuration, while dial-a-flap and autoflight are specific cockpit mechanisms.
Rotate’s XP12 passenger/freighter products have their own flight-control and automatic-flight systems.
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.
The final overall output scale applied to everything the model produces, before the device cap.
More: everything (spring, loads, effects) gets stronger together.
Less: everything softens together.
Why here: Scales overall profile strength while preserving effect balance, subject to device and output limits.
The base centring force that pulls the stick back to centre. Every other force stacks on it. Too low and the stick feels limp in normal flight; too high and it fights your hand and masks the smaller cues layered above it.
More: firmer centring that resists your hand at all times.
Less: a limper stick that leans on aerodynamic load alone.
Why here: Artificial feel accompanies the hydraulically powered controls. The baseline spring is 0.8. Low-speed spring blending is off.
MD-11 FreighterMD-11 PassengerSky Simulations MD-11 version 3 productMD-11 passenger/freighterA small neutral zone around centre where the spring stays quiet, so tiny movements at rest don't chatter. Wider is calmer but looser; narrower is more precise but can twitch around centre.
More: a calmer but looser centre with more free play.
Less: a tighter centre that may chatter at rest.
Why here: Sets travel around the centre before the baseline spring resists. Smaller values engage it sooner.
A master scale over both sustained axis loads, applied before their independent balance. Profiles normally leave this alone and tune the two axis loads instead.
More: both axes load up harder.
Less: both axes lighten together.
Why here: The stored 0 aerodynamic-load gain is inactive under the zero hydraulic-load factor.
Enables the low-speed spring engagement window (start/full knots above). Off, the spring is constant at all speeds.
Why here: Allows baseline spring strength to rise with indicated airspeed where the control law permits it.
How much of the spring survives at a standstill, before airspeed can build any aerodynamic force. A high floor keeps the parked stick firm; a low floor gives the loose, cable-slack feel of a parked light aircraft.
More: a firmer stick while parked and taxiing.
Less: a floppier parked stick that only wakes up with airspeed.
Why here: Sets low-speed spring strength as a fraction of baseline when blending is enabled. One keeps full strength.
The airspeed where the spring begins climbing from its low-speed floor toward full strength: the controls "coming alive" on the takeoff roll.
Why here: Sets the IAS where the low-speed spring blend starts rising. This is a feel threshold, not a flight limit.
The airspeed where the spring reaches full strength. Between the start and this point, centring firms up progressively as airflow builds over the controls.
Why here: Sets the IAS where the low-speed blend reaches baseline strength; high-speed stiffening also uses it.
The indicated airspeed where aerodynamic load reaches its designed full level. It anchors the whole load curve to the aircraft's real speed range: a 172 loads up by 110 knots, a jet much later.
More: loads arrive later; the stick stays light up to a higher speed.
Less: loads arrive earlier and cruise feels heavier.
Why here: Sets the IAS reference for aerodynamic loading. It is an estimate, not published cruise TAS or a flight limit.
How much the centring itself stiffens with speed, on top of the deflection loads. Zero keeps centre feel constant; more makes the stick centre harder at cruise and looser in the pattern.
More: a centre that hardens noticeably as you go faster.
Less: constant centre feel at every speed.
Why here: The high-speed spring-stiffening gain is 0. No additional speed-driven stiffening is added; this does not disable independent aerodynamic loading.
The upper limit on speed-driven centre stiffening, so very fast flight can't wind the spring up without bound.
More: more total stiffening allowed at high speed.
Less: stiffening clamps off sooner.
Why here: Limits the squared airspeed ratio used for high-speed spring stiffening; it is not a device-force cap.
The sustained roll load from aileron deflection and airspeed, balanced independently of pitch. Together with the elevator load it sets the control-harmony ratio reviewers talk about.
More: heavier roll forces.
Less: lighter, quicker-feeling ailerons.
Why here: Roll and pitch aerodynamic scales are 0.8 and 1, respectively. These stored weights do not create directed aerodynamic loading while that term is inactive. No custom spring-travel curve is enabled.
The sustained pitch load from elevator deflection and airspeed, balanced independently of roll. This is the main lever behind a type's pitch weight. It does not touch aileron, spring, trim, or buffet forces.
More: heavier sustained pitch forces at speed.
Less: a lighter elevator that takes less muscle to hold.
Why here: Scales pitch aerodynamic loading; pitch spring travel and trim responses are separate settings.
A cap on each steady pitch or roll force before it reaches the device, guarding against slamming or saturating the hardware in strong maneuvers.
More: stronger peak steady forces before clipping.
Less: a gentler ceiling; hard maneuvers flatten out sooner.
Why here: Caps directed-force output. Native spring effects and device limits remain separate.
How strongly elevator trim relieves held pitch force and shifts where the stick settles. At 100%, a properly trimmed aircraft needs no held pressure, the trim-away-the-load workflow of real flying.
More: trim removes more of the held pitch force; at 100% full trim zeroes it.
Less: you keep holding force even when trimmed.
Why here: Automatic pitch trim and CWS are separate from a fixed hardware-centre choice. Pitch relief is off, with stored authority 0; roll authority is 0.
MD-11 FreighterMD-11 PassengerSky Simulations MD-11 version 3 productMD-11 passenger/freighterThe same relief for roll trim. Most GA types have no real aileron trim, so this stays at zero; types with roll trim get a matching value.
More: roll trim removes more held roll force.
Less: roll trim does less.
Why here: Scales supported roll-trim relief and permitted centre movement. Zero removes roll response.
Rolling surface vibration from wheel speed and surface type: pavement, grass, or gravel under the gear.
More: louder surface texture through the stick.
Less: a smoother taxi.
Why here: Sets rolling texture strength, modified by speed, surface and undercarriage configuration.
Short discrete bumps from expansion joints, ruts, and rough surface, punctuating the continuous rumble.
More: sharper hits from joints and ruts.
Less: softer ground detail.
Why here: Sets gear-bump texture during ground motion, separate from touchdown impact.
Airframe shake approaching the stall and while the stall warning is active: how loudly this wing announces it is unhappy. Types with a crisp break get modest buffet and let the horn carry the warning.
More: a louder pre-stall shake.
Less: a quieter wing; the horn carries the warning.
Why here: Sets stall-buffet strength. Zero removes the cue without changing simulator stalls or warnings.
Transonic buffet approaching the Mach limit. Meaningful for jets near MMO, zero for pistons and turboprops that never get there.
More: stronger transonic buffet near the Mach limit.
Less: a smoother high-Mach ride.
Why here: Sets high-Mach buffet strength; onset and full-strength thresholds are separate.
Low-frequency airframe vibration with flaps extended into the airflow, in the speed window where they actually work the air.
More: a rougher ride with flaps working the air.
Less: smoother approach flap.
Why here: Sets flap buffet at the configured position and speed gates. Flap movement texture is separate.
Airframe drumming from retractable gear hanging in the airstream. Zero for fixed-gear types, where the airframe never changes shape.
More: more drumming with the wheels hanging out.
Less: cleaner gear-down flight.
Why here: Sets gear aerodynamic buffet; movement and ground-contact cues are separate.
The dedicated stall stick-shaker buzz, fired by the aircraft's own stall-warning system. Only types with a real shaker get a value; everything else relies on aerodynamic buffet and the horn.
More: a harder stick-shaker buzz.
Less: a subtler shaker.
Why here: Sets triggered shaker strength; inactive while the shaker feature is disabled.
The one-shot kick when the wheels meet the runway, scaled by sink rate: a greaser whispers, a firm arrival thumps.
More: a harder kick at touchdown.
Less: softer arrivals.
Why here: Sets landing-impact strength; landing telemetry and response shape determine the pulse.
Rollout vibration while reverse thrust or beta-range props are working. Zero for types without reverse.
More: a rougher rollout under reverse.
Less: quieter reverse.
Why here: Sets reverse-thrust vibration with valid reverser and engine conditions. Zero removes the cue.
Continuous powerplant vibration following RPM between idle and full power, the ever-present reminder that something is burning fuel up front.
More: more engine through the stick.
Less: a quieter powerplant.
Why here: Sets estimated engine vibration using configured telemetry and response, not measured cockpit vibration.
Continuous vibration only while the sim reports the flap surfaces actually travelling. It follows real actuator motion and failures, not an estimated timer.
More: more vibration while the flap surfaces travel.
Less: quieter flap runs.
Why here: Sets texture from observed flap movement; a command without movement does not establish the cue.
How far autopilot commands may physically move the stick. Kept tiny in MSFS, where a moved axis can read back as pilot input; zero disables following entirely.
More: the autopilot visibly moves your stick further.
Less: a barely perceptible follow.
Why here: Sets admitted AP-follow gain, not a percentage of travel. Runtime ownership and input limits still apply.
Whether this feature is active in this profile.
Why here: Retained for compatibility and group membership. Trim relief, rather than this flag, controls centre movement.
Whether this feature is active in this profile.
Why here: Allows trim relief with supported control law and valid telemetry. Axis authorities set its amount.
Whether this feature is active in this profile.
Why here: Enables local force trim, separate from aircraft-owned trim and add-on integration qualification.
Whether this feature is active in this profile.
Why here: Allows load-factor changes to modify permitted spring laws. Passive fly-by-wire feel can suppress it.
Whether this feature is active in this profile.
Why here: Enables rate damping with the configured coefficients and control law.
Whether this feature is active in this profile.
Why here: Autopilot following is off; the configured spring and load retain the hardware feel.
Whether this feature is active in this profile.
Why here: Permits centering hold during a supported AP state, separate from following a moving target.
Why here: Sets admitted AP neutral-hold strength; inactive while neutral hold is disabled.
Whether this feature is active in this profile.
Why here: Enables aerodynamic cues; each still needs nonzero strength and its simulator conditions.
Where this effect reaches full strength (or has fully faded, for washouts).
More: a more gradual build to a later peak.
Less: a quicker build.
Why here: Sets the final flap index for detent normalization. UP plus three detents uses maximum index3.
Where this effect begins fading in.
More: the effect begins later.
Less: it begins earlier.
Why here: Sets the first flap detent that admits buffet; this is a handle index, not degrees.
Whether this feature is active in this profile.
Why here: Permits shaker at supported warning conditions; the switch does not establish aircraft equipment.
Whether this feature is active in this profile.
Why here: Enables ground effects; each still needs its own strength and contact or motion telemetry.
Whether this feature is active in this profile.
Why here: Enables engine cues with nonzero settings and valid running-engine telemetry.
Whether this feature is active in this profile.
Why here: Enables accessory cues with configured strengths and observed accessory movement.
The strength of this effect.
More: a stronger effect.
Less: a weaker one.
Why here: Sets texture from observed gear movement, separate from aerodynamic and touchdown effects.
| Parameter | Value | What it controls and why |
|---|---|---|
| Spring strength | 0.8 | Artificial feel accompanies the hydraulically powered controls. The baseline spring is 0.8. Low-speed spring blending is off. |
| Spring deadband | 0.035 | Sets travel around the centre before the baseline spring resists. Smaller values engage it sooner. |
| Force gain | 0 | The stored 0 aerodynamic-load gain is inactive under the zero hydraulic-load factor. |
| Master gain | 0.85 | Scales overall profile strength while preserving effect balance, subject to device and output limits. |
| Dynamic-pressure blend | False | Allows baseline spring strength to rise with indicated airspeed where the control law permits it. |
| Minimum spring factor | 0.55 | Sets low-speed spring strength as a fraction of baseline when blending is enabled. One keeps full strength. |
| Spring wake-up speed | 8 kt | Sets the IAS where the low-speed spring blend starts rising. This is a feel threshold, not a flight limit. |
| Spring full-strength speed | 65 kt | Sets the IAS where the low-speed blend reaches baseline strength; high-speed stiffening also uses it. |
| Force tuning speed | 270 kt | Sets the IAS reference for aerodynamic loading. It is an estimate, not published cruise TAS or a flight limit. |
| Airspeed spring stiffening | 0 | The high-speed spring-stiffening gain is 0. No additional speed-driven stiffening is added; this does not disable independent aerodynamic loading. |
| Airspeed stiffening cap | 5 | Limits the squared airspeed ratio used for high-speed spring stiffening; it is not a device-force cap. |
| Aileron force scale | 0.8 | Roll and pitch aerodynamic scales are 0.8 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 | 1 | Scales pitch aerodynamic loading; pitch spring travel and trim responses are separate settings. |
| Maximum output force | 0.55 | Caps directed-force output. Native spring effects and device limits remain separate. |
| StickFeel · Trim feel enabled | False | Retained for compatibility and group membership. Trim relief, rather than this flag, controls centre movement. |
| StickFeel · Trim relief enabled | False | Allows trim relief with supported control law and valid telemetry. Axis authorities set its amount. |
| StickFeel · Elevator authority | 0 | Automatic pitch trim and CWS are separate from a fixed hardware-centre choice. Pitch relief is off, with stored authority 0; roll authority is 0. |
| StickFeel · Aileron authority | 0 | Scales supported roll-trim relief and permitted centre movement. Zero removes roll response. |
| StickFeel · Force trim enabled | False | Enables local force trim, separate from aircraft-owned trim and add-on integration qualification. |
| StickFeel · G load enabled | True | Allows load-factor changes to modify permitted spring laws. Passive fly-by-wire feel can suppress it. |
| StickFeel · Rate damping enabled | True | Enables rate damping with the configured coefficients and control law. |
| Autopilot · Follow enabled | False | Autopilot following is off; the configured spring and load retain the hardware feel. |
| Autopilot · Follow authority | 0.1 | Sets admitted AP-follow gain, not a percentage of travel. Runtime ownership and input limits still apply. |
| Autopilot · Neutral hold enabled | False | Permits centering hold during a supported AP state, separate from following a moving target. |
| Autopilot · Neutral hold strength | 0.6 | Sets admitted AP neutral-hold strength; inactive while neutral hold is disabled. |
| Aero · Enabled | True | Enables aerodynamic cues; each still needs nonzero strength and its simulator conditions. |
| Aero · Gain | 0 | Sets stall-buffet strength. Zero removes the cue without changing simulator stalls or warnings. |
| Aero · Gain | 0 | Sets high-Mach buffet strength; onset and full-strength thresholds are separate. |
| Aero · Gain | 0 | Sets flap buffet at the configured position and speed gates. Flap movement texture is separate. |
| Aero · Max flap index | 5 | Sets the final flap index for detent normalization. UP plus three detents uses maximum index3. |
| Aero · Min flap index | 2 | Sets the first flap detent that admits buffet; this is a handle index, not degrees. |
| Aero · Gain | 0 | Sets gear aerodynamic buffet; movement and ground-contact cues are separate. |
| Aero · Shaker enabled | False | Permits shaker at supported warning conditions; the switch does not establish aircraft equipment. |
| Aero · Amplitude | 0.9 | Sets triggered shaker strength; inactive while the shaker feature is disabled. |
| Ground · Enabled | True | Enables ground effects; each still needs its own strength and contact or motion telemetry. |
| Ground · Gain | 0.4 | Sets rolling texture strength, modified by speed, surface and undercarriage configuration. |
| Ground · Gain | 0.32 | Sets gear-bump texture during ground motion, separate from touchdown impact. |
| Ground · Gain | 0.9 | Sets landing-impact strength; landing telemetry and response shape determine the pulse. |
| Ground · Gain | 0 | Sets reverse-thrust vibration with valid reverser and engine conditions. Zero removes the cue. |
| Engine · Enabled | True | Enables engine cues with nonzero settings and valid running-engine telemetry. |
| Engine · Gain | 0.06 | Sets estimated engine vibration using configured telemetry and response, not measured cockpit vibration. |
| Mechanical · Enabled | True | Enables accessory cues with configured strengths and observed accessory movement. |
| Mechanical · Gain | 0.12 | Sets texture from observed flap movement; a command without movement does not establish the cue. |
| Mechanical · Gain | 0.12 | Sets texture from observed gear movement, separate from aerodynamic and touchdown effects. |
If your time in the type says this page got something wrong, correct it here.
This page is built from cited references, and real time in the type beats a citation. Quote the claim that reads wrong and tell us what the actual aircraft does. Corrections go to the maintainer for review and feed the next revision of this research.
Open conversation about flying and tuning the McDonnell Douglas MD-11, in the community forum. Corrections above go privately to the maintainer; hangar talk is public.