Start here
A few places to begin, from the aircraft’s story to the people who fly it.
Meet the aircraft
Testors' speculative 1980s F-19 model-kit concept supplied the shape for VSKYLABS' X-Plane aircraft. The developer assigned the fictional fighter a flight envelope, systems and basic simulated weapons. Its handling is a simulator interpretation without a real F-19 flight-test record.
Aircraft background
VSKYLABS · Read more ↗WLV holds an attitude
Despite its abbreviation, the developer describes WLV as an attitude-hold mode: it keeps the selected pitch and bank instead of levelling the wings. The guide also explains how a newly held attitude becomes the target. This is a feature of the VSKYLABS concept aircraft.
VSKYLABS F-19 concept aircraft · X-Plane 12
VSKYLABS · Read more ↗Into the cockpit
YouTube VSKYLABS · 3 min ·
[Archive-2022] VSKYLABS F-19 Landing demonstration with Aural AOA warning system in VR X-Plane 12
VSKYLABS demonstrates a VR landing with the F-19's audible angle-of-attack warning.
Simulator · VSKYLABS F-19 · X-Plane 12 (2022 footage)
Watch on YouTube ↗Preview images are served by AirframeDB. Videos open on YouTube only when you choose to watch.
Meet VSKYLABS F-19 concept
Testors' speculative 1980s F-19 model-kit concept supplied the shape for VSKYLABS' X-Plane aircraft. The developer assigned the fictional fighter a flight envelope, systems and basic simulated weapons. Its handling is a simulator interpretation without a real F-19 flight-test record.
VSKYLABS F-19 concept
Aircraft type designators
A model-specific ICAO or FAA designator has not been confirmed in the references reviewed for this aircraft.
History & design
The stealth fighter that began as a hypothesis
The project draws on the 1980s Testors F-19 concept and the aircraft imagined by MicroProse. Those origins matter: the F-19 presented here is a speculative design, not a declassified service aircraft.
VSKYLABS · VSKYLABS Aerospace Simulations Aircraft Center: VSKYLABS 'Test-Pilot': F-19 Stealth Fighter ↗VSKYLABS hypothetical F/A-19A; not an operational military aircraft
Turning an outline into an X-Plane aircraft
VSKYLABS dates its development to 2015. The team built systems, propulsion and handling around the concept, modifying the original proposal where its design work required it. Testors/Italeri permitted the project, while the developer identifies it as independent rather than endorsed.
VSKYLABS · VSKYLABS Aerospace Simulations Aircraft Center: VSKYLABS 'Test-Pilot': F-19 Stealth Fighter ↗VSKYLABS hypothetical F/A-19A; not an operational military aircraft
Systems & details
Which specification is being described
The dimensions and weights describe VSKYLABS’ F/A-19A. Its virtual twin afterburning engines and three internal weapon bays form part of this interpretation. The add-on supplies basic air-to-air and air-to-ground capability; the developer does not present it as a detailed combat-systems simulation.
In your simulator
Systems, equipment and documentation for each developer’s aircraft.
X-Plane 12F-19 concept
VSKYLABS · Released
F-19 concept
VSKYLABS · 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.
Simulator documentation
Two different altitude referencesVSKYLABS F-19 concept aircraft · X-Plane 12
The developer distinguishes ALT, which holds barometric altitude, from TER, which uses the radar-altimeter target. Its terrain-following guidance explicitly discusses limitations over flat surfaces and deep canyons. These are documented simulator modes, with different purposes.
ALT and TER mode notes
VSKYLABS · Read the source ↗WLV holds an attitudeVSKYLABS F-19 concept aircraft · X-Plane 12
Despite its abbreviation, the developer describes WLV as an attitude-hold mode: it keeps the selected pitch and bank instead of levelling the wings. The guide also explains how a newly held attitude becomes the target. This is a feature of the VSKYLABS concept aircraft.
Directions for using the WLV mode
VSKYLABS · Read the source ↗The Testors concept in X-Plane 12F-19 concept · VSKYLABS · X-Plane 12
The product makes the speculative Testors F-19 concept flyable in X-Plane 12. Its systems and flight characteristics are developer interpretations of an imagined aircraft.
Official developer / designated-store reference · checked 2026-09-14
VSKYLABS · Read the source ↗Read the original documentation from the people who created it. Manuals open on their publisher’s website.
Developer documentation
VSKYLABS Aerospace Simulations Aircraft Center: VSKYLABS 'Test-Pilot': F-19 Stealth FighterVSKYLABS · Official developer / designated-store reference · checked 2026-09-14 VSKYLABS F-19 Stealth Fighter. Highly Engineered Concept Fighter for X-Plane.VSKYLABS · Official developer / designated-store reference · checked 2026-09-14 F-19 autopilot guideVSKYLABS · Developer reference checked 15 September 2026; applies to the named simulator product.Built-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
VSKYLABS F-19
VSKYLABS · Free and Pro · Revision 3 · Inherited starting point
X-Plane 12
VSKYLABS F-19: The spring supplies the selected hypothetical electronic-control response.
VSKYLABS F-19 concept
Free and Pro · Revision 1 · Partial review
X-Plane 12
VSKYLABS F-19 concept: The spring supplies the selected hypothetical electronic-control response.
VSKYLABS F-19 concept
VSKYLABS F-19 concept: The spring supplies the selected hypothetical electronic-control response.
Aircraft and simulator scope
- VSKYLABS F-19 concept · X-Plane 12 · family starting point
VSKYLABS F-19 concept · Family sources identify only the variants and product versions described above.
The simulator model and controls
Testors' speculative 1980s F-19 model-kit concept supplied the shape for VSKYLABS' X-Plane aircraft. The developer assigned the fictional fighter a flight envelope, systems and basic simulated weapons. Its handling is a simulator interpretation without a real F-19 flight-test record.
This starting point selects VSKYLABS F-19 concept. Its aircraft-level settings do not select a particular developer’s custom systems.
How this profile feels
The spring supplies the selected hypothetical electronic-control response. The spring stays independent of airspeed. Directed aerodynamic loading is omitted.
Mode-dependent aircraft response is separate from hardware centering. Aircraft trim retains the fixed hardware centre. Autopilot following is off.
Controls and trim
The F19 is a developer-designed hypothetical fighter inspired by the Testors model. Normal/Tactical and Emergency/Dogfight modes have different response limits, with automatic flight used in the former context.
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
The recovered developer page identifies the fictional Testors F-19 concept; it was not a built aircraft.
The developer describes a modeled turbofan concept and a dedicated knowledge center; no real-equipment equivalence is claimed.
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 VSKYLABS F-19 concept. Its aircraft-level settings do not select a particular developer’s custom systems.
Flight controls
Not yet reviewedThe F19 is a developer-designed hypothetical fighter inspired by the Testors model. Normal/Tactical and Emergency/Dogfight modes have different response limits, with automatic flight used in the former context.
Trim
Not yet reviewedMode-dependent aircraft response is separate from hardware 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 xplane12. 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 the selected hypothetical electronic-control response. 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 value280.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 value90 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 the selected hypothetical electronic-control response. 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 value20 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 value90 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 value280.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 whyMode-dependent aircraft response is separate from hardware 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.15 | 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.14 | 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.1 | 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.36 | What it controls and whySets rolling texture strength, modified by speed, surface and undercarriage configuration. |
| Gain | Starting value0.3 | 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.44 | 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
- The fictional design cannot supply real-aircraft gearing evidence.
- The concept trim law remains unresolved.
- Follow is off; no demand interface was established.
- Concept speed and Mach estimates are not a measured force schedule.
- Artificial centering is a profile estimate, not implemented concept control laws.
- No real force gradient or supersonic buffet fidelity is claimed for the fictional aircraft.
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 ↗
