JustFlight PA-28-161 Warrior II (Marketplace)

ISSUE DESCRIPTION

Description of the issue: Flight control surface - elevator does not move when pitching down. Gets locked into position after only about 20% of yoke push movement. Makes the plane impossible to nose down beyond certain airspeed (it will actually nose up at full yoke pitch down) and makes it absolutely awful to fly in-game.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Permanent issue - Always.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Load plane into free flight at any airport so that the plane is stationary on the ground.

  2. Go to external cockpit view of the plane so that Elevator is clearly visible.

  3. Pull yoke all the way towards pilot seat for pitch up, elevator can clearly be seen to keep moving all the way until you hit maximum pull back on yoke.

  4. Push yoke all the way towards aircraft dash for pitch down, after about 20% of movement the elevator gets locked into place and will not move any further.

  5. Push all the way until 100% movement of yoke towards dash, and then pull back a little and push forward again until 100% and you can see that the elevator never moves.
    I would estimate around 70-80% of the elevator pitch down potential of this plane simply doesn’t exist because there is something wrong with the flight model files of the plane.

  6. Take the plane for a flight, then while flying, push yoke in for 100% pitch down and the plane will barely nose down at all.

  7. Reach above 120 knots and then push yoke in for 100% pitch down and the plane will actually begin to nose up as too much lift is being generated which counteracts the tiny amount of actual elevator movement being applied.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant: not relevant as issue occurs on keyboard/mouse/controller/moza ay210 ffb yoke.

[PC Only] Are you using Developer Mode or have you made any changes to it? No

[PC, MSFS 2020 Only] Are you using DX11 or DX12? DX12

[PC Only] What GPU (Graphics Card) do you use? NVIDIA RTX 5090

[PC Only] What other relevant PC specs can you share? Ryzen 9800X3D, 64GB DDR5 6000MT/s memory. Windows 11 25H2.

MEDIA

Also worth noting: Someone developed an addon specifically to address this issue and it can be found here - However, because I have purchased this plane directly through the Microsoft Flight Simulator 2024 marketplace in game, I am unable to apply this patch to fix this very clear bug. And so this plane is essentially unusable from the in game Marketplace because it does not behave well enough in game to warrant using.

Hi @Neejrow ,

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

Why have you moved this to the User Support Hub, when it’s an issue with a Marketplace plane provided by Microsoft? This should not be a 3rd party problem when Microsoft is selling this product to the end user.

I understand your concern but even if the addon has been acquired through the Marketplace the Bug Reporting Hub is to report issues only with the base sime & 1st party contents. If not already done, you should report the issue to just-flight .

I did report this issue to JustFlight, that was the very first thing I did. I spoke with Dermot Stapleton in an email chain across many exchanges, who informed me I was wrong and that their flight model was working as intended. Right up until yesterday when I showed a video of the behavior and he said he would pass it onto his dev team.

So I have had to escalate the issue to this forum, a month later. Because I am wholly unsatisfied with this plane and this is my only next avenue to report to. This plane has a major bug, and I want to report it to Microsoft, because I have spent the money on the plane via Microsofts marketplace and have no way of getting a refund from the marketplace because as per their rules no refunds are allowed.

Ideally I would get a refund, spend the money purchasing the same plane via JustFlights website, then applying this crucial patch made by a smart community member to make the plane perform correctly. But because I have purchased the plane via the marketplace it is locked behind encrypted archives in my game files and so I cannot apply the patch necessary to fix this glaring issue.

So I have to come here to this forum to post a bug report on an item Microsoft is selling, in the hopes someone does something about it.

Just look at the video I provided, clearly something is wrong with this plane. Anyone who has flown this plane IN REAL LIFE would agree that if you are flying it and push the yoke to maximum pitch down, you are basically going to risk death. Yet in MSFS2024 if you do this, essentially nothing happens and your plane simply acts as if you are maybe doing some light elevator trimming, because it’s a major bug.

Hopefully they’ll be able to replicate the issue and identify the root cause or provide you some guidance on how to fix it.

Personal comments: this aircraft is quite popular and used by many users. If there was a bug with the elevator as shown on your video I would assume many users would already have reported it.
Have you tried to test the aircraft without all your controls connected ?. If you have a simple joystick available or if not using the keyboard to move the elevator ?
Also test with the Transversal 2024 default controller profile. It could be a binding issue.

If it wasn’t an issue, this addon would not exist. PA-28-161 Warrior II Flight Model Improvement for MSFS2024. (Real Pilot) - MSFS Add-on - Flightsim.to

Elevator limit – now behaves like in real life: the elevator no longer locks halfway through pitch down travel

If someone had to make an addon to correct this issue specifically, then that should be proof enough that this is not an issue with my controls. I already stated the issue happens with any other control types. And here is a video of me using the same controls on the Cessna 172 Skyhawk included in the game, to prove that I can move the elevator correctly using my setup.

Your feedback was passed to me (Head of Development) and I can confirm that the PA28 Warrior II flight model developer is busy looking into the information that you provided on the issue. We will be back in touch via email ASAP.

Martyn - Just Flight

FWIW, I just tried using this aircraft in 2020; the yokes don’t move in the roll axis (flight surfaces do) and the avionics won’t turn on. Feels like it could be related.

Sorry to come here, but I have this VERY SAME problem that manifests exactly as @Neejrow is reporting. For some combinations of speed/ CG position/ trim inputs this is not something that you could live with. I would like also to apply the solution already provided by the original A/C designer (JustFlight) but am unable to because of the hidden files system.

Please, either ypu patch it, or you allows us to patch it, or we are refunded to apply the patch on our own through the method provided above.

Thank you

P.S.- just in case it is relevant, @Neejrow reports this and he has a Monza FFB yoke. Mine is not Monza, but it s a Flitesim CLS-60 but already as he did I also tried with different joysticks (X-56 HOTAS from ThrustMaster) and issue keeps happening 100% of the time regardless of the joystick. I guess people won´t report this is that they might not know how the actual real life PA28 behaves, but I do and it is clearly not working as necessary. Sometimes it is necessary to fully trim down to obtain a slight pitch down attitude change.

Same problem here. Feel free to ask me also about this. Hope some fix is soon found,

So they didn’t fix it yet after 4 months?

Unfortunately they never got back to me via email. I have just been waiting patiently for an update and checking in occasionally for any updates at PA-28-161 Warrior II (MSFS) Changelog : The Spirit of Flight Simulation

At least it’s nice to have another person posting with the same issue months later. @DanielBeards

Hi Martin, have you considered giving for free the PA28 warrior to those in our situation (people who actually bought your product but unable to solve it through the workaround method explained by @Neejrow )? It would be probably fairly easy to demonstrate that we acquired the warrior through MSFS marketplace. And that would also help lower our frustration.

Thank you

Edit: I don’t know looking at the maintenance manual for PA-28-161’s it dose show that is only -2’ +/-1’

What is relevant is how the plane performs in real life, and clearly as per multiple Warrior II pilots IRL have mentioned, it does not handle this way. Hence why that pilot made the addon I have listed multiple times, so that the plane performs as it does in real life.

A Piper Warrior II in MSFS2024 shouldn’t be unable to nose down at all at maximum elevator pitch down.

Ok. Have you posted this on the JF own forum? I could not see any mention when I looked earlier from anyone PA-28 Warrior II | Just Flight Community

Yes, the very first thing I did originally was post to the JF forums on February 23rd 2026 and my post was deleted and then I was emailed to say that my post was removed for discussing file structures.

I was instructed via that same email to contact them privately instead of posting to the forum, which I did a back and forth with that person over a few weeks.

I feel like I tried to go through the right channels, and now I am just waiting patiently for some sort of update. I am not the one that bumped this thread, and I only responded again after I was asked a question by DanielBeards.