You power up your new quad, push the throttle stick up, and instead of climbing, the drone rolls hard to the left. Sound familiar? This is one of the most confusing moments for any FPV pilot, and in almost every case the cause comes down to one setting: the AETR vs TAER channel map mismatch between your radio and Betaflight.
I have rebuilt, reflashed, and reconfigured more flight controllers than I can count, and channel map issues still catch me off guard after years in the hobby. The good news is that once you understand how stick inputs travel from your gimbals to your flight controller, the fix takes less than two minutes.
In this guide to AETR vs TAER, we will walk through what channel map actually means, why Betaflight cares about the order of your stick inputs, how to diagnose a mismatch, and the exact steps to fix it in both Betaflight and your radio. By the end, you will have a clear mental model of how your FPV drone sticks talk to your flight controller.
Table of Contents
What Is a Channel Map in FPV?
A channel map is the translation rule that tells your flight controller which radio channel carries which control input. Every time you move a stick on your radio transmitter, that movement is sent to the receiver as a numbered channel. The flight controller then needs to know whether channel 1 means roll, pitch, throttle, or yaw.
Without a channel map, your flight controller would have no way of interpreting the stream of numbers coming from the receiver. The four primary control channels are Aileron (roll), Elevator (pitch), Throttle, and Rudder (yaw). These terms come from fixed-wing RC aircraft, which is why drone pilots still use them today.
When you open the Betaflight Configurator and head to the Receiver tab, you will see a small preview window showing four bars that move as you wiggle your sticks. Those bars are labeled CH1 through CH4. The channel map setting tells Betaflight what each of those channels actually controls.
Think of the channel map as a decoder ring. Your radio speaks one dialect, your receiver hands the message to the flight controller, and the channel map is what allows the flight controller to understand the message correctly. Get the decoder ring wrong, and every command gets scrambled.
AETR vs TAER Explained
AETR and TAER are the two most common channel orderings used in FPV. The letters stand for the four control axes, and the order tells you which channel each axis is assigned to.
What AETR Means
AETR stands for Aileron, Elevator, Throttle, Rudder. In this channel map, channel 1 carries Aileron (roll), channel 2 carries Elevator (pitch), channel 3 carries Throttle, and channel 4 carries Rudder (yaw). Written out as a full eight-channel map in Betaflight, this becomes AETR1234.
AETR is the default channel order in Betaflight, and it matches what most FrSky receivers output by default. If you are using an FrSky X-series receiver with an FrSky radio, there is a good chance AETR is already working for you out of the box.
What TAER Means
TAER stands for Throttle, Aileron, Elevator, Rudder. Here, channel 1 carries Throttle, channel 2 carries Aileron (roll), channel 3 carries Elevator (pitch), and channel 4 carries Rudder (yaw). In Betaflight CLI this is written as TAER1234.
TAER is the default for many Spektrum receivers and some older Futaba systems. If you switched from a Spektrum radio to a Radiomaster or Jumper radio but kept your old receiver, you may suddenly need TAER where you used AETR before.
AETR vs TAER Side by Side
Here is a quick comparison of how each channel maps to a control axis. This is the cheat sheet I wish someone had handed me on my first build.
- AETR: CH1 = Roll, CH2 = Pitch, CH3 = Throttle, CH4 = Yaw
- TAER: CH1 = Throttle, CH2 = Roll, CH3 = Pitch, CH4 = Yaw
Notice that yaw always lands on channel 4 in both systems. The shuffle happens between the first three channels. This is why a mismatch usually shows up as throttle controlling roll, or roll controlling pitch, while yaw often still feels correct.
Why Channel Map Matters for FPV Drone Control
When your channel map in Betaflight does not match what your radio is actually sending, every stick input gets routed to the wrong axis. This is not a minor calibration issue. It can make your quad completely unflyable or prevent it from arming at all.
I once watched a friend spend an entire afternoon trying to figure out why his new 5-inch build would flip the instant he touched the throttle. The motor directions were right, the props were on correctly, the receiver was bound, but every throttle input was being interpreted as a roll command. The fix was changing a single dropdown from AETR to TAER.
A mismatched channel map can also be dangerous. If your drone interprets a throttle input as a yaw command, it can spin up the motors unexpectedly or arm in an unpredictable state. This is why you should always verify your channel map with props off before the first flight of any new build.
The channel map also affects how your arm switch, mode switches, and other auxiliary channels behave. If the primary four channels are scrambled, your arming switch may end up on a channel that also carries part of your stick input, which can cause intermittent arming or surprise disarm in flight.
Default Channel Order in Betaflight
The default channel map in Betaflight is AETR1234. This means Aileron on channel 1, Elevator on channel 2, Throttle on channel 3, Rudder on channel 4, and channels 5 through 8 reserved for arm, modes, and other auxiliary functions.
If you have never touched the channel map setting and your radio is outputting AETR, everything will work without any configuration. This is why many pilots flying FrSky or ExpressLRS setups never run into channel map issues at all.
You can verify the current channel map in Betaflight Configurator by going to the Receiver tab and looking at the Channel Map dropdown near the bottom. If you prefer the CLI, type get map and look for the line that reads map = AETR1234.
Note that some receiver protocols, particularly SPI receivers built into whoop flight controllers, may output a fixed channel order that you cannot change from the radio. In those cases you must change the Betaflight side to match the receiver, not the other way around.
How to Fix Wrong Channel Map in Betaflight
Fixing a wrong channel map in Betaflight takes about two minutes once you know where to look. The key is to confirm what your radio is actually sending before you change anything.
Step 1: Connect and open the Receiver tab. Plug your flight controller into your computer, open Betaflight Configurator, and click on the Receiver tab. Power on your radio and make sure your receiver is bound and showing a solid connection.
Step 2: Watch the channel bars. In the Receiver tab you will see a set of bars labeled CH1 through CH8. Slowly move each stick one at a time and watch which bar responds. If you move the throttle stick and CH3 moves, you are on AETR. If CH1 moves, you are on TAER.
Step 3: Note what your radio is sending. The bar that moves when you move the throttle stick tells you which channel your radio has assigned to throttle. Do the same for roll (aileron), pitch (elevator), and yaw (rudder). Write down the order you observe.
Step 4: Change the channel map dropdown. Find the Channel Map dropdown near the bottom of the Receiver tab. Select the option that matches what your radio is actually sending. If your radio sends Throttle on CH1, pick TAER1234. If your radio sends Aileron on CH1, pick AETR1234.
Step 5: Save and reboot. Click Save and Reboot, then re-test by moving each stick and confirming that the labels under the bars (Roll, Pitch, Yaw, Throttle) now match the stick you are moving.
Step 6: Verify with props off. Always do a props-off test before flying. Move each stick and confirm the motor response matches the command. Roll right should spin the right-side motors in the expected direction, throttle up should increase all four motors evenly.
If you prefer the CLI, you can also set the channel map by typing set map = TAER1234 followed by save. The CLI method is faster once you are comfortable, but the Receiver tab is more visual for first-timers.
How to Change Channel Order in Your Radio (EdgeTX and OpenTX)
Instead of changing Betaflight to match your radio, you can also change your radio to match Betaflight. This is the cleaner long-term approach because you only configure the radio once, and every new quad you build will work on the default AETR setting.
The channel order in EdgeTX and OpenTX is controlled from the Mixer page of your model. Each input is routed to a channel, and you can shuffle the order to whatever you want. Here is how to do it step by step.
Step 1: Open your model. Turn on your radio, long-press the Enter button or the model name, and select the model you want to edit. Then navigate to the Mixer page, usually the second icon from the left.
Step 2: Identify the four input lines. You will see lines labeled CH1, CH2, CH3, CH4 and so on. Each line shows which input source feeds that channel. For example, CH1 might show I1 which maps to the aileron input.
Step 3: Reorder the channels. To switch from AETR to TAER, you need to make CH1 carry throttle instead of aileron. The cleanest way is to swap the input sources between CH1 and CH3. Highlight CH1, press Enter, and change the source from Ail to Thr. Then do the same for CH3, changing it from Thr to Ail.
Step 4: Save and verify. Press Exit to save, then run the same Receiver tab test in Betaflight to confirm the new order is landing where you expect.
If you are using a Radiomaster TX16s, Boxer, or Pocket with EdgeTX, the process is identical. The menu layout is slightly different on smaller screens, but the Mixer page logic is the same. On older OpenTX radios like the FrSky X9D, the steps are also essentially identical.
One common gotcha: some radios come with a default channel order set at the system level, separate from the model mixer. If you change the mixer and the channel order does not seem to stick, check the radio setup page for a system-wide channel order setting.
Mode 1 vs Mode 2: Does It Affect Channel Map?
Mode 1 and Mode 2 refer to which stick controls which function on your radio, not to the channel map itself. In Mode 2 (the most popular in North America and Europe), the left stick controls throttle and yaw, while the right stick controls roll and pitch. In Mode 1, the sticks are swapped so the right stick carries throttle and yaw.
This is a separate concept from AETR vs TAER, but the two get confused because a Mode 1 pilot moving the right stick up expects to see throttle increase, while a Mode 2 pilot expects the same motion on the left stick. The channel map tells the flight controller which channel is throttle, while the mode tells the radio which physical stick feeds the throttle channel.
I mention this because I have seen pilots tear apart their Betaflight configuration chasing a channel map bug that was actually a Mode 1 vs Mode 2 mismatch in the radio settings. Before you touch the channel map, double-check that your radio is set to the correct stick mode for your flying style.
In EdgeTX and OpenTX, the stick mode is set per model on the Model Setup page. The default for most new radios sold in Western markets is Mode 2, but if you bought a used radio or imported one from Asia, it may ship in Mode 1.
Troubleshooting: Why Your Drone Responds to Wrong Sticks
If you have made it this far and your drone is still reacting strangely to stick inputs, work through this troubleshooting checklist. Each item catches a different common cause of wrong stick response.
Check 1: Confirm the channel map matches. Open the Betaflight Receiver tab and move each stick. Confirm the labeled bars (Roll, Pitch, Yaw, Throttle) match the stick you are moving. If they do not, change the Channel Map dropdown to match what your radio sends.
Check 2: Verify your stick mode. Make sure your radio is set to Mode 1 or Mode 2 to match your muscle memory. A Mode 2 pilot on a Mode 1 radio will feel like every input is wrong even though the channel map is technically correct.
Check 3: Look for reversed channels. Sometimes the channel map is correct but individual channels are reversed. In Betaflight this is fixed on the Receiver tab with the Channel checkboxes, or in the CLI with set roll_pitch_cam_angles-style reversing commands.
Check 4: Confirm your receiver protocol. SBUS, CRSF, ExpressLRS, PPM, and SPI receivers can all output different default channel orders. If you recently swapped receivers or reflashed firmware, the protocol may have changed and reset the channel order to a different default.
Check 5: Reset defaults after firmware flash. Flashing new Betaflight firmware often resets the channel map to AETR1234. If your radio sends TAER and you just updated Betaflight, you may need to re-apply the TAER setting.
Check 6: Test with props off. Never diagnose a channel map issue with props on. Always remove props and confirm motor response matches stick input before flying.
Quick Reference: Radio Defaults Cheat Sheet
Here is a quick reference for the most common radio and receiver combinations and their typical default channel orders. Use this as a starting point, but always verify in the Betaflight Receiver tab.
- FrSky X-series receivers (X4R, X4R-SB, XSR, R-XSR): Default AETR
- FrSky D-series receivers (D4R-II): Default AETR
- Spektrum DSMX receivers: Default TAER
- Futaba FHSS receivers: Default AETR (some older models use TAER)
- ExpressLRS receivers (any brand, CRSF protocol): Usually AETR
- SPI receivers built into whoop boards: Varies by board, check manufacturer docs
If your setup is not on this list, do not panic. Run the Receiver tab test described earlier and let the moving bars tell you exactly what your radio is sending.
What is the default channel map in Betaflight?
The default channel map in Betaflight is AETR1234, which means channel 1 carries Aileron (roll), channel 2 carries Elevator (pitch), channel 3 carries Throttle, and channel 4 carries Rudder (yaw). This matches what most FrSky and ExpressLRS receivers output by default.
What is the difference between AETR and TAER?
AETR assigns Aileron to channel 1, Elevator to channel 2, Throttle to channel 3, and Rudder to channel 4. TAER assigns Throttle to channel 1, Aileron to channel 2, Elevator to channel 3, and Rudder to channel 4. The difference is which channel carries throttle and roll. AETR is common with FrSky and ExpressLRS, while TAER is common with Spektrum.
How do I fix wrong channel map in Betaflight?
Open the Betaflight Configurator Receiver tab, move each stick, and watch which channel bar responds. Then change the Channel Map dropdown at the bottom of the Receiver tab to match what your radio is sending. Click Save and Reboot, then verify with props off that each stick controls the correct axis.
Why is my FPV drone responding to the wrong sticks?
The most common cause is a mismatch between the channel order your radio sends and the channel map Betaflight expects. Other causes include a Mode 1 vs Mode 2 radio setting that does not match your muscle memory, individual channels being reversed, or a channel map that reset to default after a firmware flash.
How do I change channel order in EdgeTX radio?
Open your model, go to the Mixer page, and reorder the input sources on CH1 through CH4. To switch from AETR to TAER, change CH1 source from Ail to Thr and CH3 source from Thr to Ail. Save and verify in the Betaflight Receiver tab before flying.
Conclusion
The AETR vs TAER confusion is one of those FPV hurdles that feels overwhelming until the concept clicks, and then it feels obvious forever after. Your radio sends four channels of stick data, and the channel map is just the lookup table that tells the flight controller which channel is which.
If your drone reacts wrong to the sticks, start by opening the Betaflight Receiver tab, moving each stick one at a time, and matching the Channel Map dropdown to what your radio actually sends. That single fix resolves the vast majority of stick mismatch problems in under two minutes.
For a long-term clean setup, consider changing your radio to output AETR so every new quad you build works on the Betaflight default without extra configuration. And whenever you flash new firmware or swap receivers, always re-check the channel map with props off before the first flight.