Radiomaster transmitter RC plane setup: what you need to know
A proper Radiomaster transmitter RC plane setup starts with matching the radio, receiver, and firmware to the aircraft’s control needs.
The details matter because fixed-wing models use different mixes, channel assignments, and failsafe behavior than multirotors.
This guide walks through the practical steps for setting up a Radiomaster radio for a plane, from creating the model and binding the receiver to configuring switches, flight modes, and basic safety checks.
Choose the right Radiomaster transmitter and firmware
Radiomaster radios such as the TX16S, Boxer, Pocket, and Boxer Crush are commonly used for fixed-wing flying because they support OpenTX or EdgeTX, both of which offer flexible model setup.
For most pilots, EdgeTX is the current preferred platform because it has active development, broad transmitter support, and a clean model workflow.
Before building a model, confirm three items:
- The transmitter firmware version
- The receiver protocol supported by your receiver, such as ExpressLRS, FrSky, or Flysky
- Whether your plane uses a standard receiver or a flight controller with stabilization
If you fly small trainers, sport models, or foam park flyers, a Radiomaster setup is usually straightforward.
If you fly FPV fixed-wing or stabilized aircraft, the setup may include more channels and additional arming or mode switches.
Create a new fixed-wing model
Start by creating a new model profile for the aircraft.
In EdgeTX, select a blank model and choose the model type as airplane or fixed-wing if your version includes that option.
This helps keep the model organized, even though most of the real configuration comes from mixers and channel outputs.
Give the model a clear name that matches the aircraft, such as Cessna, FT Old Fogey, or EDF Jet.
Add the battery type, wing type, and a notes screen if your transmitter supports it, especially if you manage multiple aircraft.
Set the internal or external RF module to the correct mode for your receiver.
For example, choose ExpressLRS for an ELRS receiver or ACCST/ACCESS for a compatible FrSky receiver.
Match the region and binding method to the receiver documentation.
Bind the receiver and verify signal
Binding is the link between transmitter and receiver.
The exact procedure depends on the protocol, but the general process is consistent: place the receiver in bind mode, place the transmitter module in bind mode, then confirm that the receiver LED indicates a solid link.
After binding, check the receiver page on the transmitter to confirm telemetry or receiver response if available.
Then move each stick and verify that the receiver outputs are responding correctly.
If the receiver has a range-test or RF power test mode, use it before the first flight.
What to check after binding
- Correct receiver model and protocol
- Stable link indicator on the receiver
- Live channel movement in the transmitter’s monitor
- Telemetry values, if supported
Assign channels for a typical RC plane
Most fixed-wing aircraft use a common channel layout, but the exact order depends on the receiver, flight controller, and servo wiring.
A common arrangement is:
- Channel 1: Aileron
- Channel 2: Elevator
- Channel 3: Throttle
- Channel 4: Rudder
- Channel 5 and above: Flaps, gear, flight modes, or auxiliary functions
Many pilots follow the AETR or TAER order depending on their flight controller or receiver setup.
The key is consistency.
If the aircraft responds incorrectly, you can usually fix it either by rearranging mixer lines or changing channel order in the receiver or flight controller configuration.
Why channel order matters
Channel order determines which stick controls each surface.
If aileron and elevator are swapped, the plane will react unpredictably, so always confirm on the bench with the propeller removed or motor disabled.
Build the mixers for fixed-wing control
OpenTX and EdgeTX use mixers to route inputs to channels.
For a basic plane, each primary control surface gets a direct mixer from its corresponding stick input.
A simple mixer setup often looks like this:
- CH1: Input Aileron
- CH2: Input Elevator
- CH3: Input Throttle
- CH4: Input Rudder
If the aircraft has dual aileron servos, flaps, or elevons, the mix becomes more specific.
Dual ailerons may require a second aileron channel with a reversed output or a differential mix.
Elevons require a special wing mix that combines elevator and aileron inputs into both control surfaces.
Use the transmitter’s wing mix function only if it simplifies the setup and you understand the mapping.
For many pilots, manual mixer lines provide more transparency and are easier to troubleshoot.
Set servo direction, endpoints, and subtrim
Once the channels are assigned, check servo direction.
Move each stick and confirm that the control surface moves in the correct direction.
If not, reverse the channel in the transmitter or reverse the servo in the receiver or flight controller settings, depending on your workflow.
Then adjust endpoints so the servos do not bind mechanically at full stick travel.
Endpoints should provide the required control range without forcing the pushrods or horns.
Subtrim can center the surfaces, but it should not be used to compensate for poor mechanical linkage alignment if that can be corrected on the aircraft.
For best results, set up the linkages mechanically first, then use subtrim only for small corrections.
This reduces servo load and improves consistency.
Configure throttle safety and failsafe
Throttle safety is one of the most important parts of any Radiomaster transmitter RC plane setup.
Always confirm that the throttle channel goes to idle or motor-off when the transmitter is powered up and the throttle stick is low.
Many pilots add a logical switch, throttle cut switch, or arm switch to prevent accidental motor start.
For electric planes, this is especially useful when handling the aircraft on the bench or at the field.
A dedicated throttle cut switch should override the throttle channel and force it to a safe output.
Failsafe is equally important.
If the receiver loses signal, it should not continue outputting the last throttle command.
The safest failsafe behavior for most fixed-wing aircraft is throttle off and control surfaces neutral or slightly configured for glide, depending on the aircraft and setup.
Always follow the receiver manufacturer’s failsafe procedure and test it on the ground.
Add flight modes, rates, and expo
Fixed-wing aircraft often benefit from multiple flight modes or rate settings.
A beginner mode can reduce control travel, while a sport or landing mode can restore full authority.
Exponential helps soften response around center stick without reducing full-stick travel.
A practical starting point is:
- Low rates for takeoff and training
- Medium rates for normal flying
- High rates for aerobatics or recovery
- Expo to reduce sensitivity near center on roll and pitch
If the plane has flaps, add a flap switch with a calibrated deployment range.
Flaps may also need elevator compensation, which can be mixed into the flap channel to reduce pitch changes when flaps are deployed.
Use telemetry and alerts where available
Telemetry adds useful data such as receiver signal strength, battery voltage, current draw, RSSI, and link quality.
ExpressLRS and many modern receivers support telemetry that can be displayed on the transmitter.
For fixed-wing pilots, battery voltage and link quality are especially helpful.
Set voice or vibration alerts for low battery, weak signal, or timer expiration.
Timers are highly effective for electric RC planes, since flight duration is often more limited by battery capacity than by fuel.
A motor-on timer or throttle-based timer can help you avoid over-discharging a pack.
Perform a ground check before the first flight
Before the maiden flight, perform a full bench test.
Remove the propeller if possible, or secure the aircraft safely.
Check stick direction, surface travel, switch functions, throttle cut, and failsafe response.
Ground-check checklist
- Aileron moves correctly left and right
- Elevator moves correctly up and down
- Rudder moves correctly left and right
- Throttle cut works as intended
- Flaps and gear switches function properly
- Receiver remains linked during gentle range checks
- Control surfaces center when sticks are centered
If you use a stabilization flight controller such as a Matek, SpeedyBee, or ArduPilot-compatible board in a fixed-wing aircraft, confirm that the flight controller input order, mixer settings, and output mapping match the transmitter model.
Misalignment between the transmitter and controller is a common source of reversed or missing controls.
Troubleshooting common setup problems
Most Radiomaster transmitter RC plane setup issues come from protocol mismatch, wrong channel order, or inverted servo direction.
If the receiver will not bind, recheck the module type, receiver firmware, and binding procedure.
If the surfaces move but the wrong control affects them, inspect the mixer and output mapping.
If the motor spins unexpectedly, review throttle calibration, throttle cut, and receiver failsafe settings.
For intermittent behavior, inspect antenna placement, receiver power supply, and possible interference from carbon fiber, ESCs, or poorly routed wiring.
Fixed-wing installations are often small, so keeping the receiver antenna away from high-current wiring can improve reliability.
When using ExpressLRS, make sure the transmitter module and receiver run compatible firmware branches and packet rates.
Mismatched firmware settings can cause weak links, poor latency, or inconsistent telemetry.
Keep the setup simple and repeatable
The most reliable fixed-wing transmitter setup is the one you can reproduce across aircraft.
Use consistent channel order, naming, switch assignments, and throttle safety conventions from plane to plane.
That makes it easier to fly different models without re-learning the radio layout each time.
For pilots who own several airplanes, save a model template with your preferred rates, throttle cut, timers, and telemetry alerts.
Duplicating a proven setup is faster and reduces the chance of configuration errors during a busy flying session.