Just Flight F100
Just Flight F100: The powered-control response approximates the documented actuation arrangement.
Aircraft and simulator scope
- Just Flight F100 · Just Flight · MSFS 2020 · Add-on starting point
- Just Flight F100 · Just Flight · MSFS 2024 · Add-on starting point
The simulator model and controls
The Fokker 100 developed the F28 with a longer fuselage, Rolls-Royce Tay engines and an updated flight deck. The shorter Fokker 70 followed for smaller passenger loads and shorter routes, first flying in 1993. The two regional jets have separate simulator products and variant specifications.
This profile selects Just Flight F100 for MSFS 2020, MSFS 2024.
How this profile feels
The powered-control response approximates the documented actuation arrangement. The spring stays independent of airspeed. Directed aerodynamic loading is omitted.
Automatic stabilizer trim and the F70/F100 actuator differences retain their own source scope. Pitch-trim relief is off. Autopilot following is off.
Controls and trim
The Fokker 70/100 controls use hydraulic actuation with mechanical reversion and servo tabs. Automatic flight normally manages stabilizer trim. The F70 has one stabilizer actuator supplied by both hydraulic systems; the F100 has two separately supplied actuators.
The selected implementation
Just Flight’s F70/F100 manual describes hydraulic primary actuation, mechanical reversion and servo tabs. The F70 has one stabilizer actuator supplied by both systems; the F100 has two separately supplied actuators.
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.
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
InheritedThis profile selects Just Flight F100 for MSFS 2020, MSFS 2024.
Flight controls
InheritedThe Fokker 70/100 controls use hydraulic actuation with mechanical reversion and servo tabs. Automatic flight normally manages stabilizer trim. The F70 has one stabilizer actuator supplied by both hydraulic systems; the F100 has two separately supplied actuators.
Trim
InheritedAutomatic stabilizer trim and the F70/F100 actuator differences retain their own source scope. 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
InheritedJust Flight’s F70/F100 manual describes hydraulic primary actuation, mechanical reversion and servo tabs. The F70 has one stabilizer actuator supplied by both systems; the F100 has two separately supplied actuators.
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.8 | What it controls and whyThe powered-control response approximates the documented actuation arrangement. The baseline spring is 0.8. 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 | What it controls and whyThe stored 0 aerodynamic-load gain is inactive under the zero hydraulic-load factor. |
| Force tuning speed/reference | Starting value230 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.72 | What it controls and whyRoll and pitch aerodynamic scales are 0.72 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.8 | What it controls and whyThe powered-control response approximates the documented actuation arrangement. The baseline spring is 0.8. Low-speed spring blending is off. |
| 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 | What it controls and whyThe stored 0 aerodynamic-load gain is inactive under the zero hydraulic-load factor. |
| 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.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 value230 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 whyThe high-speed spring-stiffening gain is 0. No additional speed-driven stiffening is added; this does not disable independent aerodynamic loading. |
| 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.72 | What it controls and whyRoll and pitch aerodynamic scales are 0.72 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 whyAutomatic stabilizer trim and the F70/F100 actuator differences retain their own source scope. 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 valueEnabled | 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.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 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.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.4 | What it controls and whySets rolling texture strength, modified by speed, surface and undercarriage configuration. |
| Gain | Starting value0.32 | What it controls and whySets gear-bump texture during ground motion, separate from touchdown impact. |
| Gain | Starting value0.9 | 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
- Just Flight F100; msfs2020, msfs2024. Previously observed titles and implementation identifiers are retained; installed matching remains deferred.
- Powered controls with estimated artificial feel; no direct Q-loaded aerodynamic back-drive in normal operation. Manual reversion is documented but not assigned guessed force values.
- FAS stabilizer trim is not proven to move the physical yoke neutral in a fixed ratio. Pitch/roll neutral mapping remains off until the exact feel/trim mechanism and add-on signals are established.
- AFCS drives hydraulic actuators; FAS provides stabilizer trim, yaw damping and turn coordination. This is not a passive Airbus sidestick and is not a generic737 trim relationship. AP servo-follow and neutral hold remain disabled; engagement indicators are not force-demand signals.
- Twin Tay jets with retractable wheels, flaps, lift dumpers and tail speedbrake. Failures distinguish redundant circuits; no global hydraulic-loss multiplier. F100 longer fuselage, two stabilizer actuators; current manual applies to both types.
- 230 KIAS is an estimated feel reference, not cruise TAS or a certified limit. No invented Mach, VNE or weight scheduling.
- Read-only native telemetry for aircraft motion and accessory positions. Custom switches, display animations and mode lamps are not calibrated servo targets. No unverified LVars/datarefs or simulator writes.
- Spring 0.8; lateral scale 0.72; trim authorities 0/0; per-axis output cap 0.55. Editable engineering estimates, not measured hand forces. No body-rate torque, surface following or fabricated hydraulic-failure loads.
- New physical and installed-product checks deferred by owner. Existing separately recorded acceptance retains its original device, simulator, add-on and version limits. Source review does not broaden custom telemetry acceptance.
- Only actual accessory position changes drive movement texture; static drag and command-triggered kicks are disabled. Select and save an aircraft default when telemetry lacks a discriminating developer/configuration identity.
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.