# Flight modes Flight modes in OpenTX are simple compared to most radios. A name (displayed on the main views), a switch to activate them, a trim setting and 2 fade in/out settings. Yet they are very powerful, because the main settings are actually just located somewhere else: in the D/Rs and mixers. Each of these has a flight mode selection list, that will determine in which one(s) they are active. Most everything is controlled through dedicated mixers. The mixers that are controlled by a flight mode will see their activation fade in/out according to the mode's settings. As the trims can be made flight-mode specific (they are by default), using flight modes to activate things like gear or flaps allows using the separate set of trims to counter the extra drag that often causes an effect on pitch. As a contrived example, here is what you might see on your Flight Modes page on the radio. ![](/files/-MRzpO7mKo-5mIr04GOr) The currently active Flight mode is FM0 (the default). FM0 behaves a little differently because it always active unless a flight mode below it sets itself active via a switch. The settings for FM1 are as follows: * There is no name (10 characters are allowed). * It will be active when Switch A is in the top position * For the Rudder, it will add trims from Flight Mode 0 (FM0 trims + FM1 trim) * For the Elevator, it will only use trims set in Flight Mode 1 * For the Throttle, it will add the trims from Flight Mode 2 * For the Ailerons, it will disable the trims all together * There is no Fade In * There is no Fade out If you set the switch to SA on FM1 and FM2, it will use FM1 settings. This is the first one it encounters. --- # Agent Instructions: 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: ``` GET https://doc.open-tx.org/manual-for-opentx-2-2/advanced-features/flight_modes.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.