> For the complete documentation index, see [llms.txt](https://fs2crew.gitbook.io/fs2crew-generation-ai-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fs2crew.gitbook.io/fs2crew-generation-ai-documentation/fs2crew-ai-product-guides/fbw-a32nx-edition/aircraft-faqs.md).

# Aircraft FAQs

**Q**: Do you support the Development version of the **FBW A32NX?**

**A**: Yes — we recommend it.\
\
\
**Q:** The FO doesn't start the engines. Why?\
\
**A**: According to official Airbus SOPs, the Captain (you) is responsible for starting the engines, not the FO. Additionally, as the Captain, you must announce when you start the engines. Announcing both engine starts is a necessary condition for the FO's After Start flow to trigger.

**Q:** Why does the FO announce flap changes several seconds after the associated command has been issued?\
\
**A:** In an Airbus, the important factor is not the position of the handle or switch, but what is actually displayed on the ECAM. Therefore, the FO announces the flap position only when the display indicates that the flaps have reached the commanded position, not when they are in transit. For landing gear, the red uplock lights are sufficient to make the call.

**Q:** When commanding a gear or flap change, the FO says "Speed."\
\
**A:** It means you're either too slow or too fast, and the flaps or gear cannot be moved without exceeding a limit. Ensure the MCDU is properly configured to generate accurate flap limit speeds. Do not forget to enter the weights in the MCDU!

\ <br>