The flight controller is a €100–400 part that everything else depends on. The good news: thanks to open standards, choosing one is less about finding a unicorn and more about matching a checklist to your aircraft class — then not undermining it with a bad mechanical installation.
Anatomy of a modern FC
A professional flight controller is an STM32-class microcontroller (H7 generation is current mainstream) surrounded by sensors: multiple IMUs (gyro + accelerometer), barometers, magnetometer, and sockets for GNSS — plus power management, and a forest of interfaces: UARTs, CAN, I²C, SPI, PWM outputs, Ethernet on newer designs. The flight stack runs the estimator and control loops here; heavier autonomy belongs on a companion computer.
Buy standard: the Pixhawk ecosystem
Pixhawk-standard autopilots (FMUv5/v6 generations and successors) give you multi-vendor supply, documented pinouts, and guaranteed PX4/ArduPilot support. For a startup this is mostly a supply-chain decision: when your FC vendor has a 26-week lead time hiccup — and one day they will — a standard footprint means a second source instead of a redesign. Proprietary FCs earn their place only when they bundle something you need (integrated ESCs at small scale, specific certification artefacts).
The checklist that separates hobby from industrial
| Feature | Why it matters | Minimum for commercial ops |
|---|---|---|
| Redundant IMUs | Estimator votes out a failing gyro in flight | 3× on independent buses, ideally mixed models |
| IMU heating | Gyro bias drifts with temperature; cold-morning launches | Heated, temperature-calibrated IMUs |
| Dual barometer | Baro failure = altitude estimate failure | 2×, one away from prop wash pressure fields |
| Redundant power inputs | Power brick failure shouldn't be a crash | 2× supplies with diode-OR or ideal-diode |
| CAN buses | Robust long-run comms to ESCs, GNSS, sensors (see ESC guide) | 2× CAN |
| Locking connectors | Vibration + friction-fit = intermittent everything | JST-GH or better throughout |
| Documented update path | Bootloader security, firmware provenance | Signed/controlled firmware process |
Vibration: where good FCs go to die
Most "flight controller problems" are mechanical. Gyros and accelerometers live in the FC; propellers manufacture vibration at exactly the frequencies that alias into the estimator. Practice that works:
- Mount per vendor guidance — modern internally-damped FCs often want rigid mounting; adding foam to an internally-isolated IMU can create resonance instead of curing it.
- Balance props and motors first (see propeller guide) — isolation is the second line of defence, source reduction the first.
- Check vibration metrics and clip counts in logs after every airframe change; both stacks expose them. Rising vibe trends predict failures.
- Keep the FC away from high-current wiring — magnetometer interference from power leads corrupts heading; twist pairs, route power away from the sensor deck, and consider mast-mounted compass/GNSS units.
Interfaces: count twice, buy once
List every device on the aircraft — telemetry radio, RTK GNSS ×2, companion computer link, gimbal, rangefinder, ESC telemetry, ADS-B receiver, remote ID module — then map each to a port with its bandwidth and voltage. UARTs run out embarrassingly fast; Ethernet between FC and companion is becoming the sane default for anything with a real payload. Leave one UART and one CAN spare for the sensor you haven't met yet.
Cheap clones of open-hardware designs often substitute sensor part numbers, skip temperature calibration and use unshielded oscillators. The board boots, flies on a calm day, and produces unreproducible field failures thereafter. Buy from manufacturers who publish schematics, sensor part numbers and calibration processes — the €150 delta is one saved debugging afternoon.
Practical picks by aircraft class
- Prototype / sub-2 kg: any current H7 Pixhawk-standard board from a reputable vendor.
- Commercial multirotor 2–25 kg: industrial Pixhawk-standard FC with triple heated IMUs, dual CAN, Ethernet, redundant power — this class is the workhorse for a reason.
- Certification-track / high-assurance: vendors offering DO-178/DO-254-adjacent evidence or triplex architectures; expect four-figure prices and an engagement, not a shopping cart. Your SORA level tells you when this becomes necessary.
Frequently asked questions
What is the Pixhawk standard?
Pixhawk is an open hardware standard family (connector pinouts, form factors, autopilot bus specifications) maintained under Dronecode. Buying Pixhawk-standard hardware means multiple vendors, predictable pinouts, and PX4/ArduPilot support out of the box.
Do I need a flight controller with redundant IMUs?
For commercial operations, yes — triple IMUs on separate buses with independent power let the estimator vote out a failing sensor in flight. It is one of the cheapest reliability upgrades available, typically the difference between a €90 and a €250 controller.
Can I run a commercial drone on a racing flight controller?
For prototypes, yes. For a product: racing FCs trade sensor redundancy, connector robustness, temperature stability and documentation for size and price. Field failures and debugging time quickly cost more than the industrial-grade hardware you avoided buying.