Trim effectivity on ground vs in air

I am curious if other devs have found that trim seems to be much more effective on the ground than in the air. It may be a function of airplane size, with the larger airplanes being affected more. What I mean is that a trim effectiveness that prevents an early autorotation (e.g., before VR) during takeoff with the correct trim setting for the CG condition can result in a higher than desired trim setting on final approach and landing. As such, I’ve found it difficult at times to balance the trim effectivity on the ground vs in the air. I’d be interested in the experience of other devs and any tips they may be willing to share.

I’ve used the elevator trim elasticity table, but since takeoff and approach speeds can overlap, this parameter can’t fully resolve the issue.

Hello Donald,

It’s hard to say offhand without having more specific data, like: longitudinal trim and stability characteristics, CG position, including relative to the main landing gear, trim settings, elevator effectiveness, and so on.

In any case, I have taken note of your observation and will keep this potential issue in mind in future work related to the flight control system and other related areas.

If you are able to provide any specific measurements, test cases, or data illustrating the behavior, that could help us look into the issue more efficiently.

Best regards,
Andrey / Asobo

Hi Andrey,

Thank you for responding to my post. I’m unsure how best to respond in terms of what to present to you. I am most familiar with it in our FBW products but have also seen evidence of it in other developers’ airplanes as well. What I see is, once other areas of the flight model have been tuned to give proper takeoff rotation, in-flight handling characteristics, pitch attitudes, drag, landing flare characteristics, etc., it is very difficult to balance the effect on trim on the ground (e.g., to prevent premature autorotation of the airplane) and still achieve accurate trim values after the airplane leaves the ground.

Below are a couple of example videos of our A32NX. At “normal” loading CGs, it does not prematurely autorotate and also has accurate in-flight trim values, except in the transition from ground to air after takeoff. To prevent premature auto-rotation (for a defined set of critical cases I use), yet still have accurate in-flight trim values, I use the elevator_trim_elasticity table and elevator_trim_effectiveness parameters. You can see in this video that the airplane does not auto-rotate before VR, but the trim value after liftoff must increase quite a bit for the airplane to be in trim during the initial climbout. In other words, if I use the above parameters to set a trim effectiveness to prevent auto-rotation before VR, the resulting trim effectiveness is too low once the airplane is airborne.

A32NX MSFS 2024 Mid CG takeoff.mp4

If I set the CG to the forward limit and use the correct takeoff trim setting for that CG, the airplane not only auto-rotates before VR, it also still needs significantly more trim once airborne.

A32NX MSFS 2024 Fwd CG takeoff.mp4

I can’t speak for other developers, but my impression is that they generally limit the CG range that their airplanes can be loaded to.

The issue for our A380X airplane is much more severe. We are currently using a much more forward empty weight CG within the flight model than would be accurate for the airplane and then displaying a CG to the user for setting trim, etc. that is based on an accurate empty weight CG position. This was found to be needed both to prevent premature auto-rotation and an inability to pitch down in a high pitch-up situation. Because takeoff and landing speeds are very similar, I have been unable to get both an accurate trim position during final approach and prevent premature auto-rotation. The more forward CG position within the MSFS flight model also affects our simulation of the Airbus takeoff rotation law and nosewheel pitch down rate after main gear touchdown during landing.

Other approaches I have tried are to move the center of lift for different flap positions to help achieve the proper trim value at the pitch/drag levels we have for specific conditions of speed, altitude, weight, CG, and flap configuration. But this led to other difficulties. I’ve also played around with tail sizing and positioning, incidence angle, etc., but all of these parameters only move the trim sensitivity/effectiveness in one direction, while I need less sensitivity/effectiveness on the ground and more in the air.

I’ve also noticed that MSFS 2024 runways appear to have more waviness/bumpiness than MSFS 2020 runways and this can affect autorotation. It seems fairly common that the airplane’s nosewheel may initially completely leave the runway surface, but then fairly soon after come back into contact with the runway again one or more times before finally losing contact with the surface for good. I’ve found the reducing the wheel contact point’s static compression coefficient contact can help in this area but cannot eliminate this from happening. And this solution may introduce other issues with accurate simulation of gear compression vs load.