Start here
A few places to begin, from the aircraft’s story to the people who fly it.
Aircraft and configuration
NHAdrian designed NH Acro as a fictional manned multicopter for X-Plane. An electronic flight controller stabilises the aircraft, while variable-pitch propellers provide its aerobatic capability. The simulation models individual motors, electronic speed controllers and batteries, along with a ballistic recovery system.
NH Acro
X-Plane.org authorized store · Read more ↗Meet NH Acro
NHAdrian designed NH Acro as a fictional manned multicopter for X-Plane. An electronic flight controller stabilises the aircraft, while variable-pitch propellers provide its aerobatic capability. The simulation models individual motors, electronic speed controllers and batteries, along with a ballistic recovery system.
History & design
An aerobatic drone idea scaled for a pilot
NHAdrian developed NH Acro from experience with acrobatic drones. The concept uses reversible thrust through variable-pitch propellers to explore upright and inverted flight in a crewed multicopter simulation. A tail propeller supplies yaw control.
X-Plane.org authorized store · NH Acro — simulator documentation ↗NH Acro fictional multicopter, developer history
A virtual battery assumption
The design assumes future battery technology rather than documenting an existing manned aircraft with this performance. The developer’s version history begins in December 2021 and records an X-Plane 12 update in November 2022. Its origin is an experimental software project, with the energy-storage assumption remaining part of the fiction.
X-Plane.org authorized store · NH Acro — simulator documentation ↗NH Acro fictional multicopter, developer history
Systems & details
Controls and equipment
The developer requires a stable minimum of 30 frames per second and suggests 45 or more for aerobatics. These requirements apply to the simulated multicopter.
In your simulator
No released simulator product is listed for this aircraft in the developers reviewed. Announced products are excluded.
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.
Simulator documentation
Controls and equipmentNH Acro
The developer requires a stable minimum of 30 frames per second and suggests 45 or more for aerobatics. These requirements apply to the simulated multicopter.
Flight controller, battery and performance requirements
X-Plane.org authorized store · Read the source ↗Read the original documentation from the people who created it. Manuals open on their publisher’s website.
Simulator documentation
NH Acro — simulator documentationX-Plane.org authorized store · Flight controller, battery and performance requirementsBuilt-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
NHAdrian NH Acro
NHAdrian · Free and Pro · Revision 1 · Inherited starting point
X-Plane 12
A fictional aerobatic multicopter with electronic stabilisation.
NHAdrian NH Acro
A fictional aerobatic multicopter with electronic stabilisation.
Aircraft and simulator scope
- NHAdrian NH Acro · NHAdrian · X-Plane 12 · Add-on starting point
The simulator model and controls
NHAdrian NH Acro is the selected NHAdrian configuration.
How this profile feels
The spring stays independent of airspeed. Directed aerodynamic loading is omitted.
Local force trim is off. Autopilot following is off.
Aircraft and configuration
NHAdrian designed NH Acro as a fictional manned multicopter for X-Plane. An electronic flight controller stabilises the aircraft, while variable-pitch propellers provide its aerobatic capability. The simulation models individual motors, electronic speed controllers and batteries, along with a ballistic recovery system.
Controls and equipment
The developer requires a stable minimum of 30 frames per second and suggests 45 or more for aerobatics. These requirements apply to the simulated multicopter.
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
InheritedNHAdrian NH Acro is the selected NHAdrian configuration.
Flight controls
InheritedA fictional aerobatic multicopter with electronic stabilisation.
Trim
InheritedLocal force trim is off. Autopilot following is off.
Autopilot and stability
InheritedAutopilot following is off; the configured spring and load retain the hardware feel.
Equipment
InheritedNHAdrian designed NH Acro as a fictional manned multicopter for X-Plane. An electronic flight controller stabilises the aircraft, while variable-pitch propellers provide its aerobatic capability. The simulation models individual motors, electronic speed controllers and batteries, along with a ballistic recovery system.
Speeds and limits
InheritedThe indicated-speed references set the profile response scale; they are separate from aircraft operating limits.
Simulator integration
InheritedThe profile targets xplane12. 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.35 | What it controls and whyThe developer requires a stable minimum of 30 frames per second and suggests 45 or more for aerobatics. The baseline spring is 0.35. Low-speed spring blending is off. |
| Master force gain | Starting value0.8 | 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 0 gain omits sustained directed airspeed loading. Spring resistance remains independent. |
| Force tuning speed/reference | Starting value60 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 value30.0 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.35 | What it controls and whyThe developer requires a stable minimum of 30 frames per second and suggests 45 or more for aerobatics. The baseline spring is 0.35. Low-speed spring blending is off. |
| Spring deadband | Starting value0.02 | What it controls and whySets travel around the centre before the baseline spring resists. Smaller values engage it sooner. |
| Profile force gain | Starting value0 | What it controls and whyThe 0 gain omits sustained directed airspeed loading. Spring resistance remains independent. |
| Master force gain | Starting value0.8 | 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 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 value30.0 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 value60 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 | What it controls and whyScales supported pitch-trim relief and permitted centre movement. Zero removes pitch response. |
| 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 whyThe profile uses the trim behaviour configured below. Local force trim is off. The stored latch parameters are inactive; the profile does not supply a local hold-where-left neutral. |
| 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 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 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.2 | 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
- Modest fixed centering for electronic inceptor. No manual aerodynamic loading, conventional helicopter rotor torque or invented propeller-frequency vibration.
- The aircraft flight controller owns stabilization. Bridge local FTR/beep trim and automatic neutral shift remain off.
- No calibrated AP servo target is published. AP-follow and neutral hold remain disabled; mode indicators are not servo demand.
- Read-only motion and accessory telemetry. No guessed custom servo outputs, input compensation or hardware writes outside the production Armed force path. Installed identity remains unobserved. Public source does not publish force-neutral or custom rotor RPM signals; no guessed datarefs.
- 60 KIAS is an estimated control-feel reference, not cruise TAS, V-speeds or an operating limit.
- Spring 0.35, 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.
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 ↗