
FPV drone beginner checklist
Print this mentally. Tick it before you spend. Most first-year regret in Indian FPV is not a bad motor - it is buying a 5-inch with nowhere to fly, or a whoop with three batteries and zero spare props.
This checklist is the path FPV Grind recommends for apartment and terrace pilots: sim first, whoop-first hardware, then field upgrades when access is real.
Before you buy

□ Tried a free FPV simulator (fpvgrind.in/sim) - at least a few hover sessions
□ Know where you can fly THIS month (room / terrace / open ground)
□ Chose whoop-first, not 5-inch-first, unless you already have a club field
□ Read kit vs BNF once so you know what is missing from the box
□ Budget crash tax: props, 1–2 motors, and 4+ battery packsIf you cannot name a place you will fly three times this month, stop shopping and fix access first. Spec sheets do not create airspace. Deeper framing: how to learn FPV and what to buy first.
Decision: kit vs BNF vs radio-first
| Path | Best when | Watch-outs |
|---|---|---|
| Full kit (radio + goggles + whoop) | Zero gear, want one parcel | Kit radio/goggles may be “good enough,” not forever |
| ELRS BNF + real radio | You already like sims and will stick | Still need goggles + matched charger |
| Radio only first | Waiting on whoop stock | Practice Mode 2 in /sim while you wait |
India note: match protocol (buy ELRS BNF for an ELRS radio) and battery connector (PH2.0 vs BT2.0) before you add packs to cart. Connector mismatch is a silent cart killer.
In the cart (minimum viable starter)
□ Whoop kit OR ELRS BNF + ELRS radio
□ Goggles that match video system (kit goggles OK for week one)
□ Extra props - 2+ full sets minimum
□ Extra batteries - 4+ packs (three is how you quit after one afternoon)
□ Charger that matches your connector
□ LiPo bag / fire-safe charge spot
□ Small hex drivers / tweezers for field fixesBuying flow and stock reality: how to buy FPV drone parts. Paperwork and shipping surprises: buying checklist for India.
First-week flight checklist

Do not open the PID tab. Hardware health and muscle memory beat tuning on day three.
□ Bind radio - confirm stick moves in Betaflight or OSD
□ Know which switch is ARM - practice disarm twice before first hover
□ Props clear, pets/kids out of the room
□ Hover packs indoors carefully (angle mode is fine)
□ Land, storage-charge packs when done for the day
□ Replace chipped props immediately - do not “finish the pack”
□ Log one failure: crash cause, spare used, lessonSetup help: Betaflight for beginners · hover drills: how to hover.
Common beginner failures
| Failure | Why it hurts | Fix |
|---|---|---|
| 5" first, terrace only | Noise + nowhere to practice | Whoop or club field first |
| Three packs, zero spare props | One crash ends the session | Props before fancy goggles |
| Wrong connector charger | Packs sit unused | Buy charger with the packs |
| Skip sim | Expensive furniture tax | /sim before open props |
| Arm without a plan | Finger vs prop | Arm switch + props-off bench |
India-specific notes
- Apartment / terrace politics beat gear envy: flying in apartments and terraces.
- Summer heat kills packs left in a hot scooter bag - shade and storage voltage matter.
- Domestic stock for whoop props and 1S packs is usually better than exotic HD stacks on week one.
- This is not legal advice; check local rules and society bylaws before you fly outdoors.
Eight-week milestone map
| Weeks | Goal |
|---|---|
| 1–2 | Bind, arm/disarm, soft hover, soft land |
| 3–4 | Figure-eights indoors, fewer prop replacements |
| 5–6 | Calm outdoor whoop if weather allows |
| 7–8 | Decide kit upgrade (radio, goggles) from real stick time |
Still stuck on class? Cinewhoop vs whoop vs 5" is the honest matrix.
Bottom line
Tick airspace and sim time before you tick HD goggles. A beginner cart that survives eight weeks of crashing is worth more than a perfect unboxing photo.
Bench
Build the cart on the Bench or shape a parts list in Grind Lab. Keep crashing free on /sim until the whoop arrives.
Discussion
Comments aren't open on this post yet. Share it with your build group, or start a thread on X.