Drone Build: Parts Selection Guide

Building a drone is one of the most rewarding student projects — and one of the easiest to get wrong at the parts-selection stage. Buy motors too weak for your frame and it will not lift off. Buy a battery too small and it flies for ninety seconds. Mix incompatible protocols and nothing talks to anything.

This guide walks through every major component, how to size it, and how the parts relate to each other — so your first build order is right the first time.

The parts list

Every quadcopter needs: frame, 4 motors, 4 propellers, 4 ESCs (electronic speed controllers), flight controller, battery, radio transmitter + receiver, and optionally FPV camera/vTX, GPS, and telemetry.

Frame: size dictates everything

Frame size (motor-to-motor diagonal, in mm) determines the class of every other part:

Frame	Class	Typical use	All-up weight
150–250mm	Micro/mini	Indoor, learning	250–500g
350–450mm	Standard	General purpose, most student builds	800–1500g
500mm+	Heavy lift	Payload, mapping cameras	2kg+

For a first student build, 450mm is the sweet spot: parts are cheap and plentiful, it is stable enough to learn on, and it lifts a small camera. Carbon fiber is stiffer and lighter than plastic but pricier and more brittle in crashes — beginners on a budget often start with a sturdy plastic/glass-fiber frame and upgrade later.

Note: Check your country's drone regulations before building. In India, drones above 250g need registration on the Digital Sky platform, and flying zones have restrictions. A sub-250g micro build avoids most paperwork — a genuine factor in frame choice.

Motors and propellers: the thrust equation

The fundamental requirement: total maximum thrust should be at least 2× the all-up weight. A 1kg drone needs 2kg+ of combined thrust — the extra margin is what lets it climb, fight wind, and maneuver instead of barely hovering.

• Motor size notation (e.g. 2212): first two digits = stator diameter (mm), last two = stator height. Bigger = more torque, more weight.
• KV rating = RPM per volt with no load. High KV (2000+) = small props, fast, agile. Low KV (800–1000) = large props, efficient, more lift. A 450mm build typically uses ~900–1000KV motors with 10-inch props.
• Propellers: match prop size to motor KV and frame. Larger props are more efficient but need low-KV motors and clearance from the frame. Balance props before flight — unbalanced props cause vibration that confuses the gyro.

The compatibility chain: frame size → prop size → motor KV/size → ESC current rating → battery. Size in that order; each choice constrains the next.

ESCs: matched to motors

The ESC converts battery DC into the three-phase signal brushless motors need, varying speed thousands of times per second on flight-controller command.

• Current rating: ESC amps ≥ motor max current × 1.2. A motor pulling 20A at full throttle wants a 25–30A ESC.
• Protocol: modern builds use DShot (digital, no calibration needed). Older PWM/OneShot ESCs need throttle calibration.
• 4-in-1 vs individual: a 4-in-1 ESC board is cleaner wiring; individual ESCs on arms are easier to replace after a crash.

Flight controller: the brain

The flight controller (FC) runs the stabilization loop — reading the gyro/accelerometer thousands of times per second and adjusting motor speeds (this is PID control in action).

Firmware	Style	Good for
Betaflight	Acro/racing focused, huge community	FPV and learning
ArduPilot	Autonomous missions, GPS waypoint	Mapping, autonomous student projects
INAV	GPS + fixed wing/multirotor middle ground	Long-range cruising

For autonomous student projects (waypoint missions, the classic final-year demo), ArduPilot on a board like a Pixhawk-class controller is the standard choice. For learning to fly FPV, Betaflight. The FC must include or pair with a gyro/accel IMU, barometer (altitude hold), and optionally compass + GPS.

Battery: the flight-time equation

• LiPo 3S (11.1V) vs 4S (14.8V): 4S gives more power and efficiency for 450mm builds; 3S is gentler for smaller/learning builds. Match to what your motors and ESCs are rated for.
• Capacity (mAh): more capacity = more flight time but more weight — diminishing returns past a point. A 450mm build typically flies 10–15 minutes on a 5000mAh 4S.
• C-rating: max safe discharge current = capacity × C-rating. Four 20A motors can demand 80A bursts — your battery must supply it. Undersized C-rating = voltage sag, brownouts, falling out of the sky.
• Connector and balance lead: standardize on XT60 for this size class; always balance-charge.

LiPo safety is non-negotiable: charge on a fireproof surface, never punctured or puffed packs, storage-charge at ~3.8V/cell when not flying for days, and keep a LiPo-safe bag. A damaged LiPo is a fire waiting for an excuse.

Radio link

Transmitter (your handheld controller) + receiver (on the drone):

• Protocol match matters: the receiver must speak your transmitter's protocol (ELRS, Crossfire, FrSky...). ELRS (ExpressLRS) is the current community favorite for range and price.
• Channels: 6+ channels for a basic quad (throttle, yaw, pitch, roll, mode switch, arm switch).
• Failsafe: configure what the drone does on signal loss (usually: disarm and drop, or return-to-launch with GPS). Test it on the bench with props OFF.

Putting it together: compatibility checklist

• Thrust-to-weight ≥ 2:1 at full throttle
• Prop size fits frame with clearance; props balanced
• ESC current ≥ 1.2× motor max current; protocol matches FC
• Battery voltage within motor/ESC ratings; C-rating covers peak draw
• Receiver protocol matches transmitter; failsafe configured and bench-tested
• All-up weight estimated before ordering (spreadsheet it)
• LiPo charger, fireproof bag, and basic tools budgeted

Build order wisdom: assemble the frame, mount motors/ESCs, wire the FC, configure firmware with props OFF, verify motor directions and gyro orientation, then — and only then — first hover test in a large open space, low altitude, over grass.

Maiden flight: the safe sequence

Parts selected and assembled — the first flight decides whether the build was right. The safe order:

1. Props off, bench test. Power up, verify in the configurator that the gyro responds correctly to tilts, motors spin the right direction in the right order, and the arm switch plus failsafe behave. Every one of these is fixable on the bench; none is fixable mid-air.
2. Pre-arm checks. ArduPilot refuses to arm with unresolved issues (compass, GPS, battery, RC calibration) — do not bypass these checks; they exist because someone learned the hard way.
3. First hover: Stabilize mode, low altitude, over grass, no wind. Small stick movements. The goal is not flying — it is confirming the drone hovers roughly level and responds correctly.
4. Autotune. ArduPilot's autotune flies aggressive maneuvers to learn your frame's dynamics and sets PID gains far better than hand-tuning. Run it once the basics are confirmed — it is the single highest-value tuning step for a student build.
5. Expand gradually. Altitude hold, then position hold with GPS, then simple waypoint missions. Each new mode in a big empty field before anywhere interesting.

Log every flight (ArduPilot logs by default) — when something behaves oddly, the log shows what the sensors saw, which beats guessing every time.

Common mistakes

• Skipping the thrust math. "These motors look strong enough" is how drones get built that cannot take off.
• Props on during bench testing. Every year, someone loses a fingertip. Props go on last, after all configuration is verified.
• No failsafe configured. Signal loss without failsafe = flyaway.
• Cheap no-name batteries with inflated C-ratings. Buy from reputable sellers; a sagging battery causes the most mysterious crashes.
• Ignoring vibration. Unbalanced props and loose frames feed noise into the gyro — the flight controller then fights ghosts. Fix mechanics before tuning PIDs.
• Flying first in a crowded place. Regulations, people, and property — first flights happen in empty fields.

Where to go from here

• Stabilization tuning: PID Control Tuning: A Practical Guide.
• Telemetry and video links: LoRa vs NB-IoT vs WiFi for IoT.
• Onboard camera setup: ESP32-CAM complete setup guide.
• Buying parts in India: buy electronics components in India.
• Debug electronics safely: how to use a multimeter for circuit debugging.
• More hardware topics in the IoT & Embedded branch hub.