> For the complete documentation index, see [llms.txt](https://docs.miltechsimulations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miltechsimulations.com/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/aircraft-jitters-jerky-movements-on-deck-and-elevators.md).
# Aircraft Jitters/Jerky movements on Deck & Elevators
**Aircraft Jitter on Elevators**\
This effect is most noticeable when the aircraft is positioned on static platforms. Moving carriers tend to mitigate the issue to some extent. The behavior results from a core simulator limitation: the physics engine in MSFS is not fully designed to handle this type of movement smoothly.
**Aircraft Jitter in Other Conditions**\
Outside of elevators, similar jitter can occur across MSFS 2024 due to wind effects. The updated wave simulation interacts poorly with ships, causing exaggerated sway that impacts aircraft. Reducing the wind speed usually resolves the problem. This behavior has been reported to Asobo.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.miltechsimulations.com/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/aircraft-jitters-jerky-movements-on-deck-and-elevators.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.