Climb performance
Reported climb rate in the V1 3,000-SHP-target build, worse than the stock turbine.
A transparent look at how the X-90T is being tested. A disciplined, nine-phase plan adapted from experimental-aircraft practices for Microsoft Flight Simulator 2020.
No owner-published checklist snapshot yet.
Each card defines a repeatable check. The program begins on the ground, proceeds through engine and propeller behavior, then expands to flight handling, altitude, speed, fuel and reliability.
These are planned checks, not certifications or evidence that the X-90T passed them. Any published outcomes appear with a clear date and status.
V1 was substantially slower than the stock turbine, climbed at roughly 1,000 ft/min and exhibited governor malfunction and high ITT. V4 now removes the experimental fuel limiter and stages output down for repeat testing. Its performance has not yet been independently confirmed by a new submitted flight report.
Review X-90T V2 changes ↗These are reported simulator observations, not completed pass/fail statuses for the individual test cards.
Reported climb rate in the V1 3,000-SHP-target build, worse than the stock turbine.
ITT reportedly exceeded 850°C during testing. This is not an approved operating limit.
The pilot reported that the governor was not functioning, with poor propeller power transfer.
Reported indicated torque exceeded 2,500 on the rescaled V1 instrument. Actual shaft ft-lb were not verified.
Open a phase to inspect every individual test. These are read-only records. An empty status means no official result has been published.
Freeze a reproducible baseline, define simulation limits and a stop plan.
Simulator closed; V1 installer complete.
Known configuration recorded and test-day limits selected.
Select X-90T V1 in MSFS; ensure the stock turbine and piston X-90 remain separate.
Record simulator version, X-90T build, weather preset, assistance settings and active mods.
Confirm engine and turbine cockpit XML replacements were installed in the X-90T only.
Use a long runway, calm/clear weather and generous virtual terrain clearance; avoid AI traffic.
Record weight, CG position, fuel aboard and payload in the MSFS weight-and-balance interface.
Write down the stock displayed limits and conservative test-day caps before attempting high power.
Choose when to reject a run, reduce power, land, reload and note a failure.
Decide which values come from cockpit instruments versus DevMode/debug tools; note any gauge scaling doubts.
Confirm engine response, propeller control, fuel delivery and safe simulated handling.
P0 complete; parking brake and runway environment suitable.
Repeatable ground response without unexplained exceedances.
Start from cold-and-dark and capture start time, peak ITT, Ng behavior and stabilization.
Record stabilized idle ITT, Ng, Np, oil indications and fuel flow.
At the appropriate stock procedure power settings, confirm prop control and beta/reverse behave predictably.
Record torque/ITT/Ng/Np/FF at idle, low, intermediate and higher settings; advance gradually.
Compare digital and analog turbine indications, watching for pegged or misleading needles.
Make small power changes and record delay, overshoot and oscillation.
Verify tanks/selector/quantity, alternator, annunciators and fuel-flow behavior.
Check brakes, steering, ground idle thrust, turning, and stopping margin.
Check orderly shutdown, spool-down, restart ITT response and repeatability.
Establish basic controllability and a predictable return to landing.
P1 passed. Calm daylight, conservative weight, moderate power and no high-speed experimentation.
Normal takeoff, climb, turns, approach and landing documented without unexpected behavior.
Record runway/weather, takeoff weight/CG, power target and virtual abort/return plan.
Use a conservative power setting and log directional control, liftoff IAS and surprises.
Record IAS, VSI, torque, ITT, Ng, Np and whether engine parameters stay stable.
Check level flight, trim range, pitch stability and any unexplained control input.
Check shallow left/right turns, coordination and control feel at comfortable IAS.
Reduce/reapply moderate power; record pitch and yaw changes and governor behavior.
Check gear/flaps under stock operating limits, speed stability and sink-rate response.
Document touchdown IAS, braking and all anomalies before starting another test card.
Check whether the 3,000 SHP target is actually delivered and controllable.
F-01 clean; known test-day instrument limits and enough altitude to recover from anomalies.
Engine map and governor response recorded with no unexplained runaway.
Record pressure altitude, OAT, KIAS, TAS, weight and fuel before each point.
At a stable condition, record torque, ITT, Ng, Np, FF and acceleration.
Repeat at same reference condition; record turbine response and prop RPM.
Check increasing torque, fuel flow and ITT; note whether prop absorbs power.
Only after earlier points are normal, briefly test the highest planned *sim-only* setting; back out on instability.
Record RPM droop, overshoot, hunting and recovery during controlled power changes.
Record peak/stabilized ITT and whether simulated cooling recovers after reducing power.
Compare observed GPH to model output and indicate units; note whether FF is capped.
If true shaft torque (ft-lb) and RPM are available, compute SHP; a normalized cockpit torque gauge is not a direct ft-lb reading.
Characterize stability, trim authority and power-induced handling changes.
F-01/F-02 acceptable; operate within the known low/mid-speed region.
Repeatable behavior in common configurations with no unexplained control reversal.
Document pitch and rudder trim at stable IAS and different power settings.
Apply small elevator inputs and record overshoot/settling.
Perform gentle control inputs; note asymmetric behavior or unusual coupling.
Record required rudder and bank corrections as torque increases.
Record gear/flap changes only within the aircraft’s displayed limits.
Perform simulated approach and go-around at conservative weight/power.
At generous altitude, observe low-speed trim/handling without forcing unapproved stall/spin testing.
Adjust loading in MSFS and confirm a second weight/CG combination remains controllable.
Measure a reproducible power-speed-altitude relationship.
Stable engine and normal handling. One variable at a time.
Climb and level-flight data points recorded and repeatable.
Choose a fixed altitude, weight, weather and power setting.
Record start/end altitude, elapsed time, IAS, weight, ITT, torque, Ng, Np and FF.
Repeat at higher altitude if engine and aircraft remain stable; compare rate of climb.
At each cruise altitude, allow airspeed and engine readings to settle.
Log KIAS, KTAS, Mach, FF and torque at a repeatable moderate setting.
Log the same quantities at a higher *approved test-day* setting.
Repeat only at altitudes already shown to be controllable; do not assume 35,000 ft is achievable.
Fly the same point again; note performance drift, temperature sensitivity or inconsistent engine data.
Identify speed-dependent behaviors without confusing simulation survivability with structural validation.
Engine, low/mid-speed handling and flight model reviewed. Any beyond-stock-limit test is explicitly simulator-only.
A documented maximum simulated speed with stability and instrument observations.
Identify the stock airspeed/structural limits and distinguish them from the fictional X-90T limits.
Start in a previously demonstrated speed range, not at a maximum-speed attempt.
At a steady point, record KIAS, KTAS, Mach, altitude, power, controls, trim and fuel.
Use small IAS changes with a distinct data point at each step; stop on abnormal behavior.
Record trim shifts, oscillations, buffet and unexpected control sensitivity.
Watch Np, Ng, torque, ITT and fuel flow at high flight speed.
Report all three: dynamic pressure, speed through air and compressibility are not interchangeable.
Stop the session at the first questionable point; record limit exceedances rather than calling them cleared.
Characterize fuel burn, mass/CG changes and sustained operation.
Reliable engine and predictable handling at conservative cruise.
Fuel-use and endurance data documented across loading conditions.
Record actual X-90T capacity and locations; do not assume it inherited the piston X-90’s 600-gallon modification.
Compare cockpit gauges with the MSFS fuel/weight menu at full, intermediate and low quantities.
Record start fuel, end fuel, elapsed time, power and simulator-reported fuel flow.
Calculate gallons used per hour; log any large difference from indicated GPH.
Use different virtual loadouts and recheck takeoff/landing trim and handling.
Observe ITT, oil and torque stability over a controlled longer cruise segment.
Check lights, electric bus, navigation/autopilot and turbine-related cockpit controls.
Look for failures or changing behavior after extended operation.
Convert observations into tracked issues and a controlled next build.
At least one ground or flight card conducted.
Test result exported, issues prioritized, and the next build decision documented.
Export JSON and CSV before modifying aircraft files.
For each anomaly, record reproduction steps and whether it is intermittent.
Separate stop-testing engine/control failures from indication errors and cosmetic issues.
Repeat a known-good point before changing any CFG or XML.
Document exact file changes and new build ID for each tuning iteration.
After each modification, repeat start, idle, torque/gov test and reference cruise.
Summarize demonstrated simulated performance; distinguish tested limits from targets and guesses.
Record pass / hold / revise decision for X-90T V2, not a real-world airworthiness declaration.
Previous test objectives met; predictable turbine and propeller response; credible measurements and documented test limits.
Incomplete prerequisites, uncertain torque-gauge calibration or unexplained engine behavior. Resolve before expanding the simulator envelope.
Runaway governor, uncontrollable oscillation, rising ITT, uncommanded control response or repeatable model failure. Terminate the test point and document the condition.
Estimated shaft horsepower requires independently meaningful shaft torque and RPM, not simply the indicated Black Square torque value.
In V1, the torque display was rescaled. Until that scaling is validated, a cockpit indication cannot establish actual shaft horsepower.
Methodology: Inspired by FAA AC 90-89C and task-based experimental flight testing. This is not an airworthiness approval or an operating manual for a real aircraft.
Governor response, stabilized ITT, torque, propeller RPM, climb rate and cruise performance remain the key measurements for the V4 evaluation. Results will be added as testing progresses.