Drone & UAV Hardware: The Ultimate Guide

A multirotor is the purest control problem in robotics dressed up as a toy. Four spinning props, no moving control surfaces, no steering linkage — just four numbers (the throttle to each motor) and a control loop fast enough to keep an inherently unstable object hovering in the air. Everything you bolt to the frame exists to serve that loop: the IMU that tells it which way is down, the ESCs that turn its commands into phase currents, the battery that has to deliver 100+ amps without sagging the bus voltage into a brownout. Get the loop and its sensors right and a 250 g quad will hold position in gusts. Get them wrong and the same hardware oscillates itself into the ground in two seconds.

This guide is about the hardware underneath that loop, from the perspective of someone who has built, flown, and crashed a lot of these. We will treat the multirotor as the underactuated robot it is, then work outward: airframe and size classes, the BLDC motors and how to pick Kv, propellers and prop-motor-ESC matching, ESCs and DShot, flight controllers and the three firmware camps, the sensor suite and why EKF fusion is non-negotiable, power and voltage sag, the sizing math for thrust-to-weight and flight time, payloads and gimbals, control modes, the major drone classes, and where Remote ID leaves you in 2026.

The take: A multirotor has four actuators and six degrees of freedom, so it is underactuated — it cannot move sideways without first tilting, and it controls attitude entirely through differential thrust between props. That means the whole machine is a thrust-vectoring exercise running on a control loop, and the two things that decide whether it flies well are (1) a thrust-to-weight ratio of at least 2:1 so the controller has authority to spare, and (2) a clean, well-isolated IMU feeding a loop fast enough (1–8 kHz on the gyro) to catch the airframe before it diverges. Pick the motor-prop-ESC trio together against your target voltage and all-up weight; never pick them one at a time. If you remember nothing else: size for thrust-to-weight first, match the prop to the motor and the ESC to the prop's current draw, and treat the IMU mount as a control component, not a screw hole.

Companion reading: brushless DC motors, motor controllers & FOC, robot sensors, robot power & batteries, real-time control systems, and motion planning & kinematics.

Table of contents

1. Key takeaways
2. The multirotor as a robot
3. The airframe: size classes, layouts, materials
4. BLDC motors for props: Kv, stator size, sizing
5. Propellers: diameter, pitch, thrust, efficiency
6. ESCs: BLHeli_32, AM32, DShot, current rating
7. Flight controllers: MCU, sensors, firmware, the loop
8. The sensor suite and sensor fusion
9. Power: LiPo chemistry, C-rating, voltage sag, packs
10. Thrust-to-weight and hover throttle
11. Flight-time estimation
12. Payloads and gimbals
13. Control modes: acro, angle, position hold
14. Drone classes and use cases
15. Regulatory note: Remote ID and weight categories
16. Selecting a UAV platform
17. Frequently asked questions

The multirotor as a robot

Start here, because every hardware choice downstream follows from it. A quadcopter is a rigid body floating in 3D space. A rigid body has six degrees of freedom: three translations (x, y, z) and three rotations (roll, pitch, yaw). To fully command six DOF independently you would need at least six independent control inputs. A quad has four — the four motor thrusts. Four inputs, six DOF. That mismatch is the definition of an underactuated system, and it is the single most important fact about the machine.

What can four upward-pointing rotors actually produce? Sum the four thrusts and you get one force, pointing straight up out of the airframe's belly — there is no propeller anywhere that can push the quad sideways. Difference the thrusts and you get three torques:

• Roll: more thrust on the left props than the right (or vice versa) tilts the body about its forward axis.
• Pitch: more thrust front vs. back tilts it nose-up or nose-down.
• Yaw: this one is sneakier. Each spinning prop applies a reaction torque on the airframe equal and opposite to the torque it puts into the air. If all four props spun the same way, the airframe would slowly spin the opposite way and you could never stop it. So two props spin clockwise and two counter-clockwise, their reaction torques cancel in the hover, and you yaw by deliberately unbalancing them — speed up the two CW props and slow the two CCW props and the net reaction torque rotates the airframe.

So the control authority of a quad is: one thrust magnitude + three body torques = four independent quantities, exactly matching the four motors. That is the "X" mixer at the heart of every flight controller — a 4×4 matrix that turns (throttle, roll, pitch, yaw) commands into four motor outputs.

The consequence for flight: to move horizontally, the quad must first tilt. Want to fly forward? Pitch the nose down a few degrees so the thrust vector points slightly forward, and the horizontal component accelerates you. To stop, pitch back. This coupling of attitude and translation is why the loop is nested — you cannot control position without controlling attitude first, and you cannot control attitude without controlling angular rate first.

And the body is unstable. Left alone, a hovering quad does not self-right like a fixed-wing aircraft with dihedral; tiny asymmetries (a slightly heavier arm, a prop nick, a gust) make it tip, and once tilted the thrust vector points partly sideways, which accelerates the tilt. Without active stabilization it falls over in a fraction of a second. The flight controller is not a convenience — it is what makes the vehicle a vehicle.

Rule: A multirotor is an unstable, underactuated rigid body stabilized entirely in software. The hardware's job is to give that software fast, clean sensing and enough thrust margin to win. Spec the IMU and the thrust-to-weight before you spec anything pretty.

This is also why a quad differs from the legged and wheeled robots covered elsewhere on this blog: a mobile robot can simply stop and sit there stably; a multirotor that stops controlling falls. The control loop never gets to rest.

The airframe: size classes, layouts, materials

The airframe is the skeleton — it sets the prop size, the spacing, the stiffness, and how much it weighs before you add a single gram of electronics. Multirotors are classed by propeller diameter and the matching frame wheelbase (the motor-to-motor diagonal), measured in inches by tradition even in metric shops, because props are sold in inches.

Size classes

Class	Prop dia.	Wheelbase	Typical AUW	Typical use
Tinywhoop / micro	31–40 mm (1.2–1.6")	65–75 mm	20–60 g	Indoor, sub-250 g toys
Toothpick / 2–3"	2–3"	100–140 mm	50–150 g	Indoor/outdoor light FPV
5" (the standard)	5"	210–250 mm	350–700 g	FPV freestyle & racing
7" long-range	7"	300–320 mm	600 g–1.2 kg	Long-range FPV, cruise
10"	10"	~450 mm	1.5–2.5 kg	Cinematic, light mapping
Cinelifter / heavy	13–17"	600–900 mm	3–10 kg	Camera lifting, payload
Enterprise / survey	15–22"+	900 mm–1.5 m	5–25+ kg	Mapping, agriculture, delivery

The 5-inch class is the de facto reference for FPV: a 5" prop, 2207-ish motor, 4S–6S pack, ~250 mm wheelbase, ~500–650 g AUW. Most parts, props, and tribal knowledge orbit this size.

Layouts

• X (true X / wide-X / stretch-X): motors at the four corners, arms equidistant from center (true X) or stretched front-back for camera clearance. This is the standard for FPV and most quads. Symmetric, predictable, the camera sees forward over the props.
• + (plus): one arm forward, one back, two sides. Largely obsolete on quads — the forward arm sits in the camera view and the dynamics are no better. You still see it on some research and legacy frames.
• H: two parallel side rails connected by a center bridge. Common on cinematic and longer-range builds because the long center deck has room for a big camera/gimbal and the battery, and the rear is clear for an HD camera. Slightly heavier for a given stiffness than a clean X.
• Hex / octo: six or eight motors, for redundancy (survive a motor/ESC failure) and lift. Heavy-lift and professional cinema/survey rigs go hexa- or octocopter so a single propulsion failure does not mean a crash.

Materials and stiffness

The arms and main plates on serious quads are carbon fiber — high stiffness-to-weight, and crucially, a stiff frame keeps the motors' vibration frequencies high and away from the control loop. A floppy arm resonates at low frequency, couples into the gyro, and wrecks your tune. Typical FPV frame plate thickness runs 2.5–4 mm for arms, 1.5–2 mm for top/bottom plates. Bigger frames go thicker or use carbon tube arms.

Rule: Frame stiffness is a control-loop spec, not a cosmetic one. A flexy or cracked arm shifts vibration into the gyro band and forces you to over-filter, which adds latency and softens your tune. Replace cracked arms; don't fly them.

Cheaper or toy frames use injection-molded nylon/PA12 or glass-filled plastic — flexible (good for crash survival on micros) but too compliant for a tightly tuned larger quad. Aluminum shows up as standoffs and motor mounts, rarely as primary structure (heavy, and it rings). The trade is always the same: stiffer and lighter costs money (carbon, good layup), and flex buys crash resilience at the cost of tune quality.

BLDC motors for props: Kv, stator size, sizing

Drone propulsion motors are outrunner BLDCs — the can (with the magnets) spins around a fixed internal stator, the prop bolts to the can. Outrunner topology gives high torque at low-ish RPM in a short, flat package, which is exactly what swinging a prop wants. For the full theory of how these machines work — Kv vs Kt, pole counts, why continuous current is a thermal limit — read the brushless DC motors guide; here we focus on the prop-specific choices.

Stator size: the displacement number

Drone motors are named by stator dimensions, not the can: a 2207 motor has a stator 22 mm in diameter and 7 mm tall. That four-digit number is the engine displacement of the drone world — bigger stator means more torque and more thermal mass (it can dump more heat before overheating). Common FPV sizes:

Motor (stator)	Class	Typical Kv (6S)	Role
0802–1103	Tinywhoop/2"	8000–19000 (1S–2S)	Micro
1404–1507	Toothpick/3"	2700–4500 (4S)	Sub-250 g
2004–2205	4–5" light	1700–2750	Light freestyle
2207	5" standard	1700–1950	Freestyle/race
2306–2406	5"	1700–2400	Race/freestyle
2806–3110	7"	850–1300	Long-range
4006–5010+	10"+ / heavy	200–700	Cinelifter, cargo

Real motors in this space: T-Motor (F-series, Velox — the benchmark for FPV), iFlight (Xing, Xing2), and Hobbywing (XRotor) for the propulsion end; on big enterprise rigs T-Motor's MN/U-series dominate.

Kv and voltage

Kv is unloaded RPM per volt. The unloaded top RPM is Kv × V_pack. A 1950 Kv motor on a fully charged 6S pack (25.2 V) spins ~49,000 RPM unloaded; bolt a 5" prop on and aerodynamic load pulls the actual top RPM down to perhaps 28,000–32,000 RPM.

The selection logic:

• High Kv + small prop: spins fast, accelerates the prop quickly, snappy and responsive. Pulls more current, runs hotter, less efficient. FPV racing/freestyle territory.
• Low Kv + big prop: spins slower, moves more air per rev, lower disc loading, far more efficient and quieter. Long-range, cinematic, heavy-lift territory.

The industry shifted FPV from 4S to 6S around 2020 because higher voltage at the same power means lower current, so thinner wires, cooler ESCs, and less voltage sag. To keep the same prop RPM at 6S you simply drop Kv proportionally — a 2400 Kv/4S motor and a 1600 Kv/6S motor land at similar RPM (4 cells × 2400 ≈ 6 cells × 1600).

Sizing a propulsion motor

Work from thrust, not from Kv. You need a per-motor max thrust such that all motors together give your target TWR:

thrust_per_motor_max = (AUW × TWR_target) / n_motors

Example: 600 g AUW quad, target TWR 4:1, 4 motors:
thrust_per_motor_max = (0.600 kg × 4) / 4 = 0.600 kg = 600 g

So each motor+prop combo must produce ≥ 600 g static thrust at full throttle.

Then pick a motor-prop combo whose thrust-test data (manufacturers publish these tables — thrust, current, power, efficiency per prop at each voltage) shows ≥ that thrust at your pack voltage, and check that the motor's continuous thermal rating tolerates your cruise current. Hover sits near AUW/n_motors (here 150 g/motor), so the motor spends most of its life at a small fraction of full throttle — which is good, because full-throttle current on a 2207 can be 30–40 A per motor.

Rule: Pick motors from published thrust/current tables at your pack voltage and your prop, never from Kv alone. Kv tells you nothing about thrust until you specify the prop and the volts.

Propellers: diameter, pitch, thrust, efficiency

The propeller is where electrical power becomes thrust, and it is the most under-respected component on the aircraft. A prop is specified by two numbers and a blade count, e.g. 5×4.3×3 = 5" diameter, 4.3" pitch, 3 blades.

• Diameter is how much air the disc sweeps. Bigger diameter moves more air at lower velocity, which is fundamentally more efficient (lower disc loading, thrust per unit disc area). This is why a big slow prop sips power and a small fast prop guzzles it.
• Pitch is the theoretical forward travel per revolution — how aggressively the blade bites the air. Higher pitch = more speed potential and more current draw per RPM; lower pitch = more responsive, easier on the motor, better low-speed thrust.
• Blade count: 2 blades are most efficient (least induced drag, highest top speed); 3 blades are the FPV standard (more thrust and grip in maneuvers, smoother, slightly less efficient); 4–6 blades trade still more efficiency for grip and noise reduction in tight cinematic/indoor flying.

Thrust scales roughly with diameter to the 4th power and pitch to the 1st, and with RPM squared — so diameter dominates. Doubling RPM quadruples thrust but raises power by roughly the cube of RPM, which is why throttle response feels so nonlinear and why hover sits low on the stick.

Prop-motor-ESC matching

This is the core integration problem of the whole aircraft. The three parts form a chain:

1. The prop sets how much torque the motor must produce at a given RPM, and therefore how much current it draws.
2. The motor must have the stator size (torque and thermal mass) and Kv to drive that prop at your voltage without overheating.
3. The ESC must be current-rated above the peak the motor pulls swinging that prop at full throttle.

Mismatch any link and something fails: an over-pitched prop on an undersized motor cooks the motor and browns out the ESC; an under-pitched prop on a hot motor leaves performance on the table. Manufacturers' thrust-test tables are the source of truth — they list, for each prop, the thrust, current, electrical power, and efficiency (g/W) at each throttle step and voltage.

The number to optimize is efficiency in g/W at your hover point. A well-matched 5" combo hovers around 7–10 g/W; a big low-disc-loading rig (15" props at low loading) can hit 12–18 g/W; a small overworked micro might be 4–6 g/W. More g/W at hover directly means more flight time.

Rule: Match the prop to the motor's torque, then size the ESC above the prop+motor's measured peak current with margin (typically pick an ESC rated ~1.25–1.5× the peak you expect to see). Verify with a thrust stand or trusted published data before maiden flight.

ESCs: BLHeli_32, AM32, DShot, current rating

The Electronic Speed Controller is the BLDC's three-phase inverter — it takes a throttle command from the flight controller and turns it into the commutated phase currents that spin the motor. Each motor needs one ESC; on a quad these are usually combined onto a single 4-in-1 board that stacks under the flight controller. For the inverter and commutation theory, see motor controllers & FOC.

Trapezoidal, not FOC — and why

Drone ESCs run six-step (trapezoidal) commutation, sensorless, using back-EMF zero-crossing to estimate rotor position. They do not run field-oriented control. This surprises people coming from robot joints, where FOC is the gold standard. The reason is simple: FOC's advantages — smooth torque at very low and zero speed, full torque while stalled, silence — are exactly the regime a prop never operates in. A prop is always spinning fast; back-EMF is strong and easy to track; and the load is a smooth aerodynamic torque, not a precise position hold. Six-step is simpler, cheaper, lower-latency, and entirely adequate. Spending silicon on FOC for a prop is solving a problem you don't have.

Firmware: BLHeli_32 and AM32

The motor-side firmware running on the ESC's own MCU matters as much as the hardware:

• BLHeli_S — older 8-bit firmware on simpler ESCs; supports DShot but limited; being phased out. Note: many "BLHeli_S" boards now run Bluejay, an open community firmware that adds bidirectional DShot/RPM telemetry to 8-bit hardware.
• BLHeli_32 — the 32-bit standard for years, feature-rich (telemetry, configurable timing, current limiting). It is closed-source and was effectively frozen after the 2023 ownership and export-control disruption. Still flying everywhere, but no longer the future.
• AM32 — the open-source 32-bit firmware that has become the default for new ESC designs in 2026. Runs on common STM32/AT32-class ESC MCUs, supports bidirectional DShot and telemetry, and is actively developed. If you are buying ESCs today, AM32 is the safe bet.

DShot: the digital protocol

DShot replaced the old analog throttle signals (standard PWM, Oneshot, Multishot) and is the standard in 2026. It is a digital, packetized protocol — each frame is 16 bits (11 throttle + 1 telemetry request + 4-bit CRC checksum) sent at a fixed bit rate:

• DShot150 / 300 / 600 / 1200 — the number is the bitrate in kbit/s. DShot600 is the common choice; DShot300 for longer signal wires or extra margin.
• No calibration — because it is digital, there is no min/max throttle endpoint to calibrate; the values are absolute.
• Checksummed — a corrupted frame is rejected, not acted on. Far more robust than analog levels that drift with noise.
• Bidirectional DShot (DShot telemetry) — the ESC sends eRPM back to the flight controller over the same wire. This feeds RPM filtering: the FC knows each motor's exact rotation frequency and places dynamic notch filters precisely on the motor's vibration harmonics in the gyro signal. This single feature transformed FPV tuning — it lets you filter the noise without the blanket low-pass filtering that used to add latency and softness.

Current rating

ESCs are rated in continuous and burst amps per motor (a "4-in-1 50A" means 50 A per channel). The rating is a thermal limit on the MOSFETs and is honest only with adequate cooling and airflow. For a 5" 6S build, 45–60 A per channel is typical; cinelifters and big rigs use 80 A+ ESCs or single ESCs per motor. Always rate the ESC above the peak current your prop-motor combo draws at full throttle, with margin — see the matching rule above. Undersized ESCs are a top cause of in-flight desyncs and burnouts.

Rule: For drone propulsion, trapezoidal/six-step ESCs with bidirectional DShot are correct; FOC is the wrong tool. Spend your engineering on filtering, current headroom, and cooling — not on commutation cleverness.

Flight controllers: MCU, sensors, firmware, the loop

The flight controller (FC) is the brain — the board running the stabilization loop. Physically it is an MCU plus an IMU plus a barometer plus a pile of UARTs, on a 20×20 mm, 25.5×25.5 mm, or 30.5×30.5 mm stack-standard board.

The MCU

FCs run STM32 microcontrollers almost universally:

• F4 (STM32F405) — the long-time workhorse, 168 MHz Cortex-M4F. Fine for 5" FPV at 4–8 kHz loops. Being superseded.
• F7 (STM32F722/745) — 216 MHz, more headroom for filters and peripherals.
• H7 (STM32H743/H750) — 400–480 MHz Cortex-M7. The current high-end for FPV (room for every filter and OSD feature) and the standard floor for serious PX4/ArduPilot autonomy boards, which need the compute for EKF, logging, and multiple sensor streams.

Autonomy platforms standardize on the Pixhawk open hardware standard (the FMUv5/v6 spec), built by Holybro and others, pairing an H7 with redundant IMUs and a clean connector standard. The compute-heavy perception and planning usually run on a companion computer (an NVIDIA Jetson or similar SBC) alongside the FC, which sticks to the hard real-time stabilization — the classic MCU/SBC split discussed in real-time control systems.

The control loop: rate → attitude → position

The FC runs a nested cascade, fastest loop innermost:

1. Rate (inner) loop — reads the gyro (angular velocity), runs a PID to drive measured rate to commanded rate, outputs motor mix. This is the hard real-time loop, run at 1–8 kHz (gyro sampled up to 8–32 kHz). It is what actually stabilizes the airframe. In acro mode, your sticks command rate directly — this loop is the whole flight experience.
2. Attitude (middle) loop — fuses gyro + accelerometer (the IMU) into an estimated angle, runs a PID to drive angle to commanded angle, and outputs a rate setpoint to the inner loop. Runs at hundreds of Hz. This is "angle/self-level" mode.
3. Position (outer) loop — fuses GPS, baro, optical flow, etc. into estimated position and velocity, and outputs an attitude setpoint. Runs at 10–100 Hz. This is GPS position hold, altitude hold, return-to-home, waypoint missions.

Each loop's output is the next loop's setpoint. The pattern — fast/simple/critical inside, slow/complex/tolerant outside — is the universal robot control hierarchy.

The three firmware camps

	Betaflight	PX4	ArduPilot
Primary use	FPV racing/freestyle/acro	Autonomous, research, commercial	Autonomous, commercial, all-vehicle
Control focus	Razor-tuned rate loop, lowest latency	Full position/mission control	Full position/mission control
Position hold / GPS	Basic (GPS rescue, position hold)	Yes, full	Yes, full, very mature
Mission planning	No (it's a manual-flight firmware)	Yes (QGroundControl)	Yes (Mission Planner / QGC)
Vehicle types	Multirotor (some wing)	Multi, VTOL, fixed-wing, rover	Multi, VTOL, plane, rover, boat, sub
Typical MCU	F4/F7/H7	H7 (Pixhawk standard)	H7 (Pixhawk standard)
License	GPL, open	BSD, open	GPL, open
Tuning vibe	Hands-on, latency-obsessed	Engineered, modular (uORB/EKF2)	Mature, feature-dense, huge param set

Choose by mission, not by fashion. Betaflight for anything you fly line-of-sight or FPV by hand where stick-to-prop latency and snap are everything. PX4 for autonomous and research work, VTOL, and a clean modular codebase. ArduPilot for the most mature autonomy feature set across the widest vehicle range — it will fly a quad, a plane, a VTOL, a boat, and a submarine off variations of the same stack. PX4 vs ArduPilot is largely a culture/tooling preference; both are excellent and both run on Pixhawk-class hardware.

Rule: Match firmware to mission. Don't run PX4 on a 5" race quad (you'll fight latency and complexity) and don't run Betaflight on a survey drone (it has no mission planner). The hardware can be similar; the firmware encodes the intent.

The sensor suite and sensor fusion

A multirotor knows where it is and which way is up only because of its sensors and the math that fuses them. For the broader treatment of each sensor type, see robot sensors; here's the drone-specific suite.

The IMU (gyro + accelerometer)

The gyroscope measures angular velocity on three axes; the accelerometer measures linear acceleration (including gravity) on three axes. Together they're a 6-axis IMU, and they are the heart of the FC. Common parts in 2026: InvenSense/TDK ICM-42688-P and Bosch BMI270 — both low-noise, high-rate MEMS 6-axis IMUs. High-end Pixhawk boards carry redundant IMUs (two or three) for fault tolerance and voting.

The gyro feeds the rate loop and is fast and low-latency but drifts (integrating it gives a slowly wandering angle). The accelerometer gives a long-term gravity reference (it knows where "down" is when the vehicle isn't accelerating) but is noisy and wrong during maneuvers. Each covers the other's weakness — that's the whole point of fusion.

IMU mounting is a control spec. Motor and prop vibration at hundreds to thousands of Hz couples into the gyro and corrupts the rate loop. Mitigations: soft-mount the FC on rubber gummies, keep the frame stiff, and apply RPM filtering (dynamic notch filters placed on each motor's exact eRPM, fed by bidirectional DShot telemetry). Get this wrong and you over-filter, adding latency, hot motors, and a mushy tune.

Barometer, magnetometer

• Barometer (e.g. DPS310, BMP388/390) measures air pressure → altitude. Resolution is tens of centimeters; it drifts with weather and is disturbed by prop wash and canopy pressure, so it's fused, not trusted alone. It's the primary altitude source when GPS altitude is poor.
• Magnetometer (compass, e.g. QMC5883/IST8310) measures the Earth's magnetic field → heading. Essential for absolute yaw on GPS aircraft. Notoriously corrupted by motor currents and ferrous metal, so it's mounted away from power wiring (often up on the GPS mast) and must be calibrated. FPV quads in acro often skip it entirely — gyro yaw is enough when you're flying manually.

GPS and RTK

• GNSS/GPS (u-blox M8/M9/M10 modules are the standard) gives absolute position to roughly 1–3 m horizontally with a good fix. Needed for position hold, return-to-home, and waypoint missions.
• RTK (Real-Time Kinematic) uses carrier-phase measurements plus corrections from a base station (or a network) to reach centimeter-level positioning — u-blox F9P-class receivers are the workhorse. RTK is what mapping and survey drones use to get sub-decimeter geolocation accuracy without dense ground control points. Two RTK receivers on one airframe also give a precise GPS-derived heading (moving-baseline), avoiding compass trouble entirely on big rigs.

Optical flow, lidar/ToF

• Optical flow — a downward camera tracks ground texture motion to estimate horizontal velocity, enabling position hold indoors or anywhere GPS is denied. Needs a textured surface and adequate light.
• Lidar / Time-of-Flight rangefinders — a downward laser/ToF gives precise altitude above ground (centimeter-class, GPS-independent) for low-altitude work, terrain following, and precision landing. Forward-facing ToF/radar/stereo enable obstacle avoidance. For the depth-sensing side, see LiDAR & depth cameras.

Sensor fusion: the EKF

No single sensor gives a clean state. The gyro is fast but drifts; the accel knows down but is noisy; GPS is absolute but slow and jumpy; the baro drifts; the mag is noisy. The Extended Kalman Filter (EKF) — PX4's EKF2, ArduPilot's EKF3, Betaflight's lighter complementary/Kalman blend — fuses all of them into one continuously updated estimate of attitude, velocity, and position, weighting each measurement by its modeled trust (its covariance). The gyro propagates the state forward at high rate; the accel/mag/GPS/baro/flow corrections pull it back toward truth.

Rule: Position hold is not a sensor; it is a fused state estimate. If the EKF's inputs disagree (a bad compass, a GPS glitch, a vibrating IMU), the estimate is wrong and the aircraft will fight you or fly away — "toilet bowling" on a bad compass is the classic symptom. Trust the fusion only as much as you trust its worst input.

Power: LiPo chemistry, C-rating, voltage sag, packs

The power system has to deliver brutal peak current — a 5" quad can pull 100+ A in a hard punch-out — without sagging the bus voltage into a brownout that resets the FC. For battery fundamentals, see robot power & batteries.

LiPo vs Li-ion

• LiPo (lithium polymer) is the multirotor default. High discharge rate, high power density per gram, flat-ish discharge curve, cheap. Nominal 3.7 V/cell, 4.2 V full, ~3.5 V the practical floor under load. The cost is cycle life (a few hundred cycles), fragility, and fire risk if punctured or overcharged.
• Li-ion (cylindrical 18650/21700 cells, e.g. Molicel P42A/P45B, Samsung 50S) wins on energy density (Wh/kg) but has a lower continuous discharge rate. You build Li-ion packs for long-endurance flight — 7" long-range cruisers, mapping, survey — where you cruise at modest current and want maximum Wh per gram, not for hard acro.

S and C ratings

• S = cells in series, setting voltage. 4S = 14.8 V nominal, 6S = 22.2 V nominal (the FPV standard now), big rigs run 12S and up. Parallel cells (P) multiply capacity/current: a "6S2P" Li-ion pack is 6 in series, 2 in parallel.
• C-rating is the claimed max continuous discharge as a multiple of capacity. A 1300 mAh 100C pack claims 130 A continuous (1.3 Ah × 100). Treat published C-ratings as optimistic marketing — the honest test is measured voltage sag under your actual load.

Voltage sag: the real-world spec

Every pack has internal resistance. Under load, terminal voltage drops by I × R_internal — that's sag. A tired or under-rated pack sags so much under a punch-out that the bus drops below the FC's brownout threshold and it resets mid-air — instant crash. Sag also means your "6S" pack delivers far less than 25.2 V when it matters. Symptoms of an undersized pack: heavy sag, hot pack after landing, "puffed" cells.

Rule: Size the pack by measured voltage sag under your worst-case current, not by the C-rating on the label. If the pack is hot or puffed after a flight, it's over-stressed — go up in C-rating or capacity, or down in current draw. A pack that sags below your FC's brownout voltage is a crash waiting to happen.

Pick capacity to balance energy against weight: more mAh means more flight time until the pack's own weight dominates and TWR drops, at which point you're carrying battery to carry battery. For a 5" quad, 1100–1500 mAh 6S is the freestyle sweet spot; long-range 7" runs 2500–6000 mAh Li-ion. Always land at ~3.5 V/cell under load (≈3.7–3.8 V resting) — running a LiPo flat kills it fast.

Thrust-to-weight and hover throttle

This is the sizing math that decides whether a build flies well. Two numbers: thrust-to-weight ratio (TWR) and hover throttle.

Thrust-to-weight ratio is total max static thrust (all motors at full throttle) divided by all-up weight:

TWR = total_max_thrust / AUW

Example: 4 motors × 1200 g max thrust each = 4800 g total thrust.
AUW (frame + electronics + battery + camera) = 650 g.
TWR = 4800 / 650 = 7.4 : 1

What TWR you want:

• < 1.5 : 1 — barely flies; sluggish; no control authority margin; only acceptable on heavy-lift rigs you fly gently and never need to fight a gust.
• 2 : 1 — minimum for stable, controllable flight with margin. A good target for cinematic and enterprise platforms.
• 4 : 1 to 8 : 1 — FPV freestyle and racing. The huge margin gives instant response and the ability to recover from any attitude.
• > 10 : 1 — race-tuned screamers; uncontrollable for beginners, pure speed.

Hover throttle is where the throttle stick sits to hold a stable hover — the fraction of full thrust needed just to cancel gravity:

hover_thrust_fraction ≈ AUW / total_max_thrust = 1 / TWR

For TWR 7.4:1:  hover ≈ 1/7.4 ≈ 0.135 → ~14% throttle
For TWR 2:1:    hover ≈ 1/2   = 0.50  → ~50% throttle

Because thrust scales roughly with the square of RPM (and RPM roughly with throttle on these systems), thrust is very nonlinear in throttle — so a TWR-7 quad doesn't hover at 14% of stick, but well under half. The principle holds: higher TWR → lower hover throttle → more control authority above hover.

Rule: Target hover at or below ~50% throttle (TWR ≥ 2:1). If you hover near full throttle, you have almost no authority left to fight wind or maneuver — the control loop saturates and the aircraft falls. Add thrust margin before you add anything else.

Flight-time estimation

Flight time is set by how much energy you carry and how fast you burn it in hover (where most flights spend most of their time):

1) Pack energy:
   E_Wh = capacity_Ah × pack_nominal_voltage
   e.g. 1.3 Ah × 22.2 V (6S) = 28.9 Wh

2) Hover power (the dominant term):
   P_hover_W = AUW_kg × g × (1 / efficiency_g_per_W_scaled)
   In practice: read it off the motor/prop thrust table at hover thrust,
   OR estimate:  P_hover ≈ hover_thrust_grams / (g_per_W at hover)

   e.g. 650 g hover thrust at 8 g/W → 650/8 ≈ 81 W

3) Flight time (with usable fraction, since you don't fly to 0%):
   t_min = (E_Wh × usable_fraction) / P_hover_W × 60

   e.g. (28.9 Wh × 0.80) / 81 W × 60 ≈ 17 minutes hovering

Reality is lower than the hover estimate for FPV (you're rarely hovering — acro burns far more) and close to it for a steady cinematic platform. Key levers, in order of impact:

• Lower disc loading (bigger props, lower Kv, more efficient g/W at hover) — the biggest sustainable win. Long-range 7" builds fly 20–40+ minutes precisely because they hover at high g/W.
• Higher TWR margin so you cruise at low throttle, in the prop's efficient regime.
• More pack energy — but with diminishing returns: past the point where pack weight dominates AUW, adding capacity adds weight that needs more power to lift, and flight time plateaus then falls.
• Lower AUW everywhere else.

Typical numbers: 5" freestyle 4–6 min hard / 7–9 min cruise; 7" long-range 20–40 min; cinematic 10" 15–25 min; large enterprise survey 30–55 min on Li-ion.

Payloads and gimbals

Anything you carry — camera, gimbal, lidar, sprayer, delivery box — is payload, and it eats directly into your thrust margin and flight time. Budget it into AUW from the start, not as an afterthought.

A gimbal is a motorized 2- or 3-axis (pitch/roll/yaw) stabilized mount that isolates the camera from the airframe's vibration and attitude changes, giving smooth footage. It uses low-Kv gimbal BLDC motors run in FOC (here FOC is the right tool — these motors hold precise position at near-zero speed, exactly the regime where FOC shines, unlike props) with high-resolution encoders, driven by a dedicated gimbal controller with its own IMU. A 3-axis gimbal plus camera on a cinematic rig is a meaningful payload (hundreds of grams to a kilo-plus), which is why camera drones run big low-disc-loading props and 2:1-ish TWR rather than the 7:1 of a featherweight racer.

For enterprise work the payload is often a survey camera, multispectral sensor, lidar unit, or RTK-tagged mapping camera — heavy, power-hungry, and the entire reason the aircraft exists. The propulsion is sized around the payload, not the other way around.

Rule: Payload is a TWR and endurance tax. Add it to AUW, re-check that you still hover ≤ 50% throttle, and re-run the flight-time math. A camera that drops your TWR below 2:1 means you need a bigger aircraft, not a braver pilot.

Control modes: acro, angle, position hold

The three flight modes map exactly to the three control loops, in order of how much of the stack is active:

• Acro / rate mode — only the inner rate loop runs. Your sticks command angular velocity; release the sticks and the quad holds its current attitude (it does not self-level). This is what FPV freestyle and racing fly — maximum agility, no limits, full inversions, and it depends only on the gyro. It is also the hardest to fly and the purest expression of the machine.
• Angle / self-level / horizon mode — the attitude loop is active on top. Sticks command a target angle; center the sticks and the quad levels itself. Uses the fused IMU (gyro + accel). This is "stabilized" mode — what beginner and most camera flying uses. There's a max tilt limit, so you can't flip.
• Position / GPS hold (loiter, altitude hold) — the full position loop is active. Release the sticks and the aircraft holds its 3D position against wind, using fused GPS/baro/flow. This is the foundation of autonomous flight: position hold, return-to-home, waypoint missions, follow-me. It needs a good fused state estimate — a bad compass or GPS makes it dangerous.

The progression is the loop hierarchy made visible: acro is the bare rate loop, angle adds attitude, position adds the outer loop. More automation = more sensors trusted = more ways to fail if a sensor lies, which is the trade you accept for hands-off flight.

Drone classes and use cases

Class	Frame/props	Firmware	Power	Endurance	Notes
FPV racing	5", X, ultralight	Betaflight	6S LiPo 1100–1300	3–5 min	TWR 8–12:1, latency-obsessed
FPV freestyle	5", X	Betaflight	6S LiPo 1300–1500	5–8 min	TWR 4–7:1, durable
Cinematic FPV	5–8", X/H + gimbal	Betaflight	6S LiPo	6–12 min	HD cam/gimbal payload
Long-range FPV	7", X	Betaflight/iNav	6S Li-ion	20–40 min	Low disc loading, GPS rescue
Camera/prosumer	8–13", X/H	proprietary/PX4	6S+ Li-ion	20–45 min	3-axis gimbal, obstacle avoid
Enterprise mapping	15–22", hex/octo	PX4/ArduPilot	12S+ Li-ion	30–55 min	RTK GPS, survey payload
Heavy-lift/cargo	17"+, hex/octo	PX4/ArduPilot	12–14S+	varies w/ load	Redundancy, big payload
Fixed-wing/VTOL	wing + lift rotors	PX4/ArduPilot	Li-ion	45 min–hours	Cruise efficiency of a wing

Two classes deserve a note beyond multirotors:

• Fixed-wing UAVs trade hover for efficiency — a wing generates lift aerodynamically, so it cruises at a fraction of a multirotor's power and flies for hours. The cost is it can't hover or take off vertically. ArduPilot and PX4 fly these with the same FC hardware.
• VTOL (vertical takeoff and landing) is the hybrid: lift rotors for vertical takeoff/landing/hover plus a wing and pusher motor for efficient forward cruise. You get a wing's endurance and a multirotor's launch flexibility, at the cost of mechanical and control complexity (the transition between hover and forward flight is the hard part, handled by PX4/ArduPilot's VTOL modes). This is where most serious long-range mapping and delivery work is heading in 2026.

Regulatory note: Remote ID and weight categories

Hardware choices in 2026 are shaped by regulation as much as physics.

• Remote ID (RID) is effectively mandatory for most drones in the US (FAA) and EU. The drone broadcasts its ID, position, and operator location over Wi-Fi/Bluetooth — either via a built-in standard RID module or a bolt-on broadcast module. Plan for a RID module in your weight and power budget unless you're flying a sub-class exempt aircraft.
• The sub-250 g threshold is the most consequential number in consumer drone regulation. In many jurisdictions, aircraft under 250 g face lighter registration and (in some cases) RID requirements. That single line in the rules is why a whole class of drones is engineered to land at exactly 249 g AUW — it's a regulatory cliff, not an engineering one.
• Weight/risk categories (the EU's Open category A1/A2/A3, the FAA's operational rules) scale requirements with mass and proximity to people. Heavier and BVLOS (beyond visual line of sight) operations require more: certified hardware, redundancy, RID, sometimes type certification.

Rule: Check the current rules for your jurisdiction and weight class before you build, and budget the RID module's weight and power into AUW. The regulatory category often dictates the size class more than the mission does.

This is the aviation-grade end of the functional safety story — redundancy and fail-safe behavior aren't optional on a 10 kg machine flying over people.

Selecting a UAV platform

Put it together into a repeatable selection process:

1. Define the mission and payload first. FPV freestyle, cinematic, long-range cruise, mapping, delivery? What sensor/camera must it carry, and how heavy is it? This sets everything downstream.
2. Pick the size class from the payload and mission (the size table). Payload + endurance usually dictate prop diameter and motor count.
3. Check the regulatory category for that weight and operation, and budget RID. The sub-250 g cliff may push the whole design.
4. Set the AUW budget and target TWR (≥ 2:1 general, 4:1+ for FPV). Confirm hover lands ≤ 50% throttle.
5. Pick the prop-motor-ESC trio together against your pack voltage and per-motor thrust target, using published thrust/current tables. Verify ESC current headroom.
6. Choose the battery by chemistry (LiPo for power, Li-ion for endurance), S-count for voltage, and capacity for the energy/weight balance — then validate by measured voltage sag, not C-rating.
7. Choose the FC and firmware by mission: Betaflight for manual/FPV, PX4 or ArduPilot for autonomy, on appropriately-sized STM32 (H7 for autonomy or feature-heavy FPV).
8. Spec the sensor suite for the control modes you need: IMU always (and mount it well); add baro for altitude, mag + GPS (or RTK) for position/missions, optical flow/ToF for GPS-denied or precision landing.
9. Run the flight-time math and check it meets the mission. If not, lower disc loading or AUW before adding battery.
10. Validate before you trust it: bench-test thrust and current, check IMU/vibration after first hover, confirm fail-safes (low battery, RC loss, RTH) actually work.

Do this in order and the aircraft flies as designed. Skip the TWR and prop-matching steps and you'll spend the maiden flight picking carbon out of the grass.

Frequently asked questions

Why does a quadcopter need both clockwise and counter-clockwise propellers? To cancel reaction torque. Each spinning prop pushes back on the airframe with a torque opposite to its own spin. If all four spun the same way, the airframe would spin the other way uncontrollably. Two CW and two CCW props cancel that torque in hover, and yaw is produced by deliberately unbalancing them. This is also why you must install props in the correct CW/CCW positions, or the quad flips on takeoff.

What thrust-to-weight ratio do I need? At least 2:1 for stable, controllable flight with margin; 4:1 to 8:1 for FPV freestyle/racing; around 1.5:1 minimum for a heavy platform you fly gently. The practical test: you should hover at or below ~50% throttle. If you hover near full throttle, the control loop has no authority left to fight wind and you'll crash in any disturbance.

How do I choose motor Kv? By the prop and the pack voltage, working from thrust tables. Kv × pack voltage is unloaded RPM; the prop pulls actual RPM down. Lower Kv with bigger props for efficiency and endurance (long-range, cinematic, heavy-lift); higher Kv with smaller props for response (racing/freestyle). On 6S, ~1700–1950 Kv is the 5" standard; ~850–1300 Kv suits 7" long-range. Never pick Kv without specifying the prop and the volts.

What is DShot and why is it better than PWM? DShot is a digital, packetized ESC protocol that sends a 16-bit checksummed throttle frame at a fixed bitrate (DShot300/600 are common). Versus analog PWM it needs no endpoint calibration, rejects corrupted frames via CRC, and — crucially — bidirectional DShot sends each motor's eRPM back to the flight controller, enabling precise RPM-based notch filtering of motor vibration. That filtering transformed FPV tuning by killing noise without adding blanket-filter latency.

Do drone ESCs use FOC? No. Drone propulsion ESCs run six-step (trapezoidal) sensorless commutation. FOC's advantages — smooth torque at zero and low speed, full stall torque, silence — apply to a regime a prop never operates in (a prop always spins fast). Six-step is simpler, cheaper, lower-latency, and fully adequate for props. FOC is used in drone gimbals, where the motors hold precise position at near-zero speed.

Betaflight, PX4, or ArduPilot — which should I use? Match firmware to mission. Betaflight for manual line-of-sight and FPV flying where stick-to-prop latency and agility are everything (no mission planner). PX4 for autonomous and research work with a clean modular codebase, VTOL, and commercial use. ArduPilot for the most mature, feature-dense autonomy across the widest vehicle range (multi, plane, VTOL, rover, boat, sub). PX4 vs ArduPilot is mostly a tooling/culture preference; both run on Pixhawk-class H7 hardware.

What is the rate/attitude/position loop hierarchy? A nested cascade. The inner rate loop (gyro → angular velocity PID) runs at 1–8 kHz and actually stabilizes the airframe; it's all that's active in acro mode. The attitude loop (fused IMU → angle PID) wraps it for self-level/angle mode. The position loop (fused GPS/baro/flow → attitude setpoint) at 10–100 Hz wraps that for GPS hold and missions. Each loop's output is the next inner loop's setpoint; fast/critical inside, slow/tolerant outside.

Why do I need an EKF — can't I just read the GPS? No single sensor is reliable alone: the gyro is fast but drifts, the accelerometer knows "down" but is noisy under acceleration, GPS is absolute but slow and jumpy, the baro and mag drift and get disturbed. The Extended Kalman Filter fuses them all into one continuously-updated state estimate, weighting each by its trustworthiness. Position hold is a fused estimate, not a sensor reading — and it's only as good as its worst input (a bad compass causes the classic "toilet bowl" fly-away).

LiPo or Li-ion? LiPo for high discharge and power density per gram — the default for anything that punches out or does acro (FPV, racing, freestyle). Li-ion (21700 cells) for energy density and endurance where you cruise at modest current — long-range, mapping, survey. Don't try to hard-acro a Li-ion pack (it can't deliver the peak current); don't expect LiPo to match Li-ion's Wh/kg for endurance.

What does the C-rating mean and can I trust it? C-rating is the claimed continuous discharge as a multiple of capacity (a 1300 mAh 100C pack claims 130 A). Treat it as optimistic marketing. The honest spec is measured voltage sag under your actual worst-case current — if the pack sags toward your FC's brownout voltage, or comes back hot or puffed, it's under-rated for your build regardless of the number on the label.

How do I estimate flight time? Pack energy (Ah × nominal voltage = Wh) times a usable fraction (~0.8), divided by hover power in watts, times 60 for minutes. Hover power you read off the motor/prop thrust table at hover thrust, or estimate from g/W efficiency. The biggest sustainable lever is lower disc loading (bigger, slower, more efficient props), then cruising at low throttle from a high TWR margin. Adding battery has diminishing returns once pack weight dominates AUW.

Why does sub-250 g matter so much? It's a regulatory cliff. In many jurisdictions, drones under 250 g get lighter registration and (sometimes) Remote ID requirements. That single rule is why a whole class of consumer drones is engineered to land at exactly 249 g all-up weight — the limit is legal, not aerodynamic. Above it, plan for registration and an RID module in your weight and power budget.

Why is the IMU mount considered a control component? Because motor and prop vibration (hundreds to thousands of Hz) couples through the frame into the gyro and corrupts the rate loop. A floppy frame or a hard-mounted FC pushes that vibration into the gyro's measurement band, forcing heavy filtering that adds latency and softens the tune, runs the motors hot, and wastes power. Soft-mounting the FC, keeping the frame stiff, and using RPM filtering (from DShot telemetry) is the difference between a clean tune and an oscillating mess.