FPV drones

The 5-inch freestyle list I would order tomorrow

Eleven parts, every pairing checked by the rules, and the two places where the obvious choice is not the right one.

What this is written from: Written from the curated build in the Buildlas catalogue: every pairing run through the published compatibility rules, prices as the retailer stated them on the date shown. Not a flight review.

Why a list at all

Ask a forum what to buy for a first real freestyle quad and you get forty answers, each one a different decade of somebody's habits. Ask a video and you get whatever arrived free that month. What I actually wanted, back when I started reading about this, was one list with the reasoning attached, where somebody had checked that the parts fit each other rather than assuming it.

So that is what this is. Eleven parts, chosen so that every pairing passes the compatibility rules this site publishes, with the two spots where I think the obvious pick is wrong called out below. The full list with prices is linked at the bottom.

Where the obvious choice is wrong, part one: motor KV

The classic mistake in a first parts list is a high-KV motor on a 6S battery, because the motor was reviewed on 4S and the battery advice came from a different thread. The combination does not merely run hot: it asks the ESC for more current than anything in the build was chosen to supply, and the failure arrives mid-air.

This is exactly the kind of pairing a rule catches and a shopping cart does not. The build below pairs an 1855KV motor with 6S, which is the boring, correct middle of the range.

Part two: the frame decides more than it seems

A frame looks like the least technical purchase in the list, a carbon plate with holes. The holes are the product. They decide which motors bolt on, which stack fits inside, and how big a propeller clears the arms, and a frame that gets one of those wrong quietly vetoes three other choices.

If you swap the frame in this list, the planner re-checks those three pairings the moment you do. That is the whole argument for planning a build in something that knows the rules rather than in a notes app, which is how I did my first one, and it went the way you would expect.

What Buildlas checks for you here

Every rule is published, with what it reads and what it does when a specification is missing.