Start here
A few places to begin, from the aircraft’s story to the people who fly it.
Meet the aircraft
An electric multicopter represented in both MSFS 2020 and MSFS 2024. Microsoft lists VoloCity in the Standard tier. Aviator includes the lower edition tiers. The simulator edition is recorded separately from the real aircraft’s development or certification status.
Volocopter VoloCity
Microsoft · Read more ↗Meet Volocopter VoloCity
VoloCity is an electric multicopter represented in MSFS 2020 and MSFS 2024. Microsoft's MSFS 2024 roster includes it in Standard and the higher edition tiers, including Aviator.
Volocopter VoloCity
Aircraft type designators
No type code selected for this entry yet.
History & design
Several generations lead to VoloCity
Volocopter’s development passed through the VC200 proof of concept and the 2X before VoloCity. The company’s April 2022 retrospective places VoloCity’s maiden flight in December 2021 at Bruchsal, Germany.
Volocopter · VoloCity maiden flight retrospective, April 2022 ↗Volocopter retrospective, 13 April 2022
The first flight was remotely initiated
The first VoloCity lift-off described in that account began with a remote switch. It demonstrated the new aircraft’s integrated system after earlier prototype testing; it should not be confused with the first crewed flight or the start of passenger service.
Volocopter · VoloCity maiden flight retrospective, April 2022 ↗Volocopter retrospective, 13 April 2022
Systems & details
A multicopter designed for short urban trips
Eighteen fixed-pitch rotors surround a two-seat composite cabin. The design uses lithium-ion batteries that can be exchanged and charged externally. Its approximately twenty-kilometre operational range is an expected figure with margins, dependent on weather and other conditions, not a demonstrated range guarantee.
In your simulator
Systems, equipment and documentation for each developer’s aircraft.
Compare simulator versions →MSFS 2024VoloCity
Microsoft Flight Simulator · Released
VoloCity
Microsoft Flight Simulator · Released
MSFS 2020VoloCity
Microsoft Flight Simulator · Released
VoloCity
Microsoft Flight Simulator · Released
Manuals & resources
Read the original documentation from the people who created it. Manuals open on their publisher’s website.
Resource
MSFS 2024 official aircraft rosterMicrosoft · Official catalogue reviewed 15 September 2026 MSFS 2020 official aircraft rosterMicrosoft · Official catalogue reviewed 15 September 2026Manufacturer documentation
VoloCity design specifications, 2024Volocopter · VoloCity Design Specification SCD-21-010-PS01 A00, 2024, p. 1Aircraft history
VoloCity maiden flight retrospective, April 2022Volocopter · Volocopter retrospective, 13 April 2022Built-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 · 1 profile choice
Volocopter VoloCity
Free and Pro · Revision 1 · Partial review
MSFS 2024 · MSFS 2020
Volocopter VoloCity: The spring supplies a fixed electronic-control centre.
Volocopter VoloCity
Volocopter VoloCity: The spring supplies a fixed electronic-control centre.
Aircraft and simulator scope
- Volocopter VoloCity · MSFS 2024 · family starting point
- Volocopter VoloCity · MSFS 2020 · family starting point
Volocopter VoloCity · Family sources identify only the variants and product versions described above.
The simulator model and controls
VoloCity is an electric multicopter represented in MSFS 2020 and MSFS 2024. Microsoft's MSFS 2024 roster includes it in Standard and the higher edition tiers, including Aviator.
This starting point selects Volocopter VoloCity. Its aircraft-level settings do not select a particular developer’s custom systems.
How this profile feels
The spring supplies a fixed electronic-control centre. The spring stays independent of airspeed. Directed aerodynamic loading is omitted.
Aircraft stabilization remains independent of hardware trim centering. Aircraft trim retains the fixed hardware centre. Autopilot following is off.
Controls and trim
The VoloCity is an electric multicopter represented in MSFS 2020 and 2024. Its electronically coordinated propulsion supplies the aircraft response around a simplified control interface.
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
Volocopter's 2019 announcement identifies the electric VoloCity concept.
The manufacturer identifies electric vertical flight; combustion texture is inapplicable.
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 Volocopter VoloCity. Its aircraft-level settings do not select a particular developer’s custom systems.
Flight controls
Not yet reviewedThe VoloCity is an electric multicopter represented in MSFS 2020 and 2024. Its electronically coordinated propulsion supplies the aircraft response around a simplified control interface.
Trim
Not yet reviewedAircraft stabilization remains independent of hardware trim centering. Pitch relief is off, with stored authority 0.3; roll authority is 0.3.
Autopilot and stability
Not yet reviewedAutopilot following is off; the configured spring and load retain the hardware feel.
Equipment
ReviewedGear, flap and ground cues follow the selected settings and available simulator-reported states.
Speeds and limits
Not yet reviewedThe indicated-speed references set the profile response scale; they are separate from aircraft operating limits.
Simulator integration
Not yet reviewedThe profile targets msfs2024, msfs2020. 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 whyThe spring supplies a fixed electronic-control centre. The baseline spring is 0.55. The electronic-control law keeps centering independent of airspeed. |
| 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 value55.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 value27.5 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.55 | What it controls and whyThe spring supplies a fixed electronic-control centre. The baseline spring is 0.55. The electronic-control law keeps centering independent of airspeed. |
| Spring deadband | Starting value0.04 | What it controls and whyThe spring deadband is 0.04. It defines the central interval before added centering resistance builds; the centre preload is 0. |
| 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 value7.7 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 value27.5 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 value55.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. 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.3 | What it controls and whyAircraft stabilization remains independent of hardware trim centering. Pitch relief is off, with stored authority 0.3; roll authority is 0.3. |
| Aileron Authority | Starting value0.3 | 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 valueEnabled | 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 | 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.88 | 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 | What it controls and whySets texture from observed gear movement, separate from aerodynamic and touchdown effects. |
Limits and open questions
- The announcement does not establish inceptor forces or the current control law.
- Conventional trim relief is off; no inceptor trim behavior was established.
- Follow is off; no servo-demand interface was established.
- Performance figures do not establish an indicated-airspeed force curve.
- Concept identity does not qualify multicopter signals in MSFS.
- Passive centering is estimated; fly-by-wire profile semantics suppress the stored directed gain, which is not a measured inceptor load.
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 ↗
