Every earlier lesson explained one subsystem. This one assembles them, because a quadcopter is not the sum of good parts but the result of connecting them in the right order and checking each connection before it can do harm. A build gone wrong announces itself with smoke, a flip on takeoff, or a motor that will not spin, and almost all of these trace to a step skipped or done out of order. The discipline that separates a first flight from a first crash is patience: power nothing until it has been checked, spin nothing with propellers on until it has been checked without them, and fly nothing until it has hovered on the bench.
Assembly, and the order that keeps checks possible
The craft goes together from the frame outward. The motors bolt to the arms first, their wires routed to where the electronics will sit. The flight controller and the four ESCs, or the increasingly common single board that holds all four, mount in the centre on soft standoffs that isolate the vibration the frame lesson warned about. Then the wiring: the battery leads to the power input, the ESC phase wires to the motors, the motor signal and ground to the flight controller, and the receiver and video transmitter to their ports. The order matters because each connection should be inspectable when it is made, and a board buried under later parts cannot be checked. Almost every joint is soldered, and a good solder joint is shiny and slightly concave where the metal has flowed and wetted both surfaces, made by heating the joint itself and feeding solder to it, not by melting a blob onto a cold junction. A cold joint, dull and rounded, conducts intermittently and is the source of the maddening fault that comes and goes with vibration, so the time to find it is on the bench with a gentle tug on every wire, not in the air.
The first power-up, without propellers
The most dangerous moment in a build is the first time the battery is connected, because a single reversed wire or a stray whisker of solder bridging two pads dumps the whole pack through the short in an instant, and the result is smoke and dead electronics. Two habits prevent it. First, the propellers stay off for everything in this section, so that no check can turn into a spinning-blade injury. Second, the first connection is made through a smoke stopper, a simple device that limits the current on the first power-up so that a short trips it harmlessly instead of destroying the board. If the craft powers up without heat, smell or smoke, the gross faults are ruled out and configuration can begin. A builder who connects a fresh board straight to a full pack and hopes is, sooner or later, buying a new board.
Configuration, telling the software what it is wired to
The flight controller runs firmware, most commonly Betaflight on a racing or freestyle craft, and out of the box it knows nothing of this particular build. Configuration is telling it the truth about its own wiring. The receiver's protocol from the radio lesson, CRSF or SBUS, is selected so the controller understands the channels arriving. The ESC protocol, DShot, is set so the motors are commanded digitally. The channels are mapped, so that the arm switch arms, the mode switch selects self-levelling or acro, and the sticks move the right axes. The failsafe is set to cut the motors on link loss and then tested by switching the transmitter off, propellers still absent, and confirming the craft would disarm. None of this is flying; it is making the software's picture of the craft match the solder joints, and a mismatch here is a craft that fights its pilot for reasons no tuning can cure.
The two checks that prevent the takeoff flip
Two specific errors cause the classic first-flight flip, and both are caught on the bench. The first is motor direction: recall from the opening lesson that two motors must spin clockwise and two counter-clockwise in the correct corners. With propellers off, each motor is spun from the configuration software and its direction watched, and any that turn the wrong way are reversed, which is now a setting rather than a rewiring. The second is propeller handedness: a clockwise motor takes a clockwise propeller, pushing air down, and fitting the mirror-image propeller makes that corner suck air up. The propellers are fitted only after directions are confirmed, each matched to its motor's spin, and this pairing is checked twice because getting one wrong is invisible on the bench and catastrophic at takeoff.
Example. On the bench with propellers off, the front-left motor is commanded to spin and turns clockwise, but the build's layout calls for it to turn counter-clockwise. What is the fix, and what would have happened if it were flown as is?
The fix is to reverse that motor's direction in the ESC configuration, a software setting, no rewiring needed. Flown as is, that corner's reaction torque and, once a propeller is fitted, its thrust would be wrong, and the craft would spin up hard and flip the instant it was armed with throttle.
Now you. Directions are all correct, but a builder fits a clockwise propeller to a motor that spins counter-clockwise. With the craft armed and throttle raised, what happens at that corner and to the craft?
Answer
That corner pushes air upward instead of downward, so it pulls down instead of lifting. The craft cannot balance, tips violently toward that corner, and flips. The propeller must match the motor's spin direction.
The first hover
With directions and propellers right, the failsafe tested, and the battery charged, the first flight is deliberately dull. It happens outdoors in a clear open space with nothing and no one nearby, the pilot standing well back. The craft is armed, and the throttle is raised slowly until the craft just becomes light on the ground and lifts a few centimetres into a low hover. The single question being asked is whether it holds roughly level and steady with the sticks centred. If it does, the control loop, the sensor fusion, the mixer and the power system are all working together, and the craft is flying. If it drifts hard to one side or oscillates, the throttle comes straight back down, because the first hover is a test and not a flight, and the fault is diagnosed on the ground.
Tuning, and why the craft is never quite finished
A craft that hovers is not yet a craft that flies well. The PID gains of the control lesson are set to safe defaults that fly any build gently, and getting the crisp, locked-in feel a pilot wants is tuning: raising each gain until the craft shows the misbehaviour that gain causes, the fast buzz of too much proportional or the hot twitch of too much derivative, then backing off. Modern firmware does much of this automatically now, but the reasoning is the same one from the control lesson, and a builder who understands what each term is failing to do can finish by hand what the automatic pass leaves rough. The craft that results is the whole course made real: weight balanced against thrust, a propeller matched to a motor matched to a battery, a stiff quiet frame carrying a fast loop that reads two flawed sensors and holds the machine steady, flown over one radio link and seen over another. Built in that order and checked at every step, it flies, and the reader who followed the argument from the first lesson now knows not just that it flies but why, and could design the next one from scratch.