Why I'm rebuilding Quadcopter Garage in 2026

The first Quadcopter Garage ran from 2013 to 2016. I built a Lunchbox Copter out of a plastic storage box and zip ties. I migrated a flight controller from a KK2.0 to an APM 2.5 to a Pixhawk. I sold drone parts imported from China through a WooCommerce store that lost money on every order and taught me an embarrassing amount about fulfillment logistics.

Then DJI won.

The market for “I want to build a drone to fly a drone” evaporated. Phantom 3, then Mavic, then Mini — each one a generation cheaper, more reliable, and more capable than anything a hobbyist could reasonably assemble in a garage. The audience for build logs disappeared with it. I shut the site down in 2016 and went to do other things.

What changed

A decade later, the drone market looks nothing like 2016. DJI owns consumer. Skydio owns commercial inspection. Dronehub and Anduril own the defense-adjacent infrastructure layer. You can buy a perfectly good drone at any weight class for any budget.

But that’s not the interesting part.

The interesting part is what happened underneath. The PX4 flight stack matured. ROS2 went mainstream. Edge AI inference got cheap enough to put on a drone — a Jetson Orin Nano running a vision model costs less than the flight controller it sits next to. Visual SLAM, GPS-denied navigation, real-time obstacle avoidance — these were research topics in 2016. They’re weekend projects in 2026.

And the people who want to learn this stuff have nowhere good to go.

The gap

r/diydrones in 2026 is mostly experienced GNC engineers asking each other about STM32 vs Teensy. The PX4 docs are comprehensive but fragmented. ROS2 tutorials assume you’ve already worked through one ROS1 cycle. There is no single end-to-end resource for the engineer who wants to go from “I have never built a drone” to “I have a drone that flies a waypoint mission with vision-based obstacle avoidance.”

That’s the gap. This site fills it.

The plan

One flagship project. Twelve months. From a pile of parts to a quadcopter that flies a waypoint mission with vision-based obstacle avoidance and GPS-denied fallback navigation.

Q1 — Foundations
  - The autonomous drone stack in 2026
  - Building a ~$1k autonomous quad: BOM deep dive
  - Zero to first flight with PX4 in QGroundControl
  - Companion computers: Jetson Orin Nano vs Pi 5 + Hailo-8L
  - ROS2 Jazzy + MAVROS2 setup for drone control

Q2 — Offboard + simulation
  - Offboard mode with MAVROS2 / MAVSDK-Python
  - Gazebo Garden as your PX4 testbed
  - Isaac Sim 5.x for photorealistic sim
  - Python script that flies a square pattern
  - PID tuning without tears

Q3 — Vision layer
  - OAK-D Pro vs ZED 2i for stereo
  - Depth-based obstacle detection
  - YOLO11 on Jetson for real-time detection
  - Visual obstacle avoidance

Q4 — Advanced autonomy
  - GPS-denied navigation with VINS-Fusion
  - ORB-SLAM3 on a drone
  - The dual-use nature of drone autonomy
  - Year 1 retrospective + Year 2 roadmap

Every post gets a YouTube video. Every video gets a GitHub commit. Every commit gets a newsletter issue. Five hours a week. Real builds, real failures, real fixes. No content calendar gymnastics, no SEO farming, no AI slop.

Why autonomous drones specifically

Three reasons.

One: Autonomous drones sit at the intersection of every robotics domain that matters right now. Edge AI inference. Real-time control loops. ROS2 middleware. Computer vision. Sim-to-real. MLOps for embodied systems. If you can build one, you understand the entire modern robotics stack. There’s no faster way to get there.

Two: The dual-use nature is real and worth being explicit about. The exact same autonomy stack — visual SLAM, GPS-denied nav, obstacle avoidance, edge AI — powers inspection drones, agricultural drones, search-and-rescue drones, mapping drones, and defense-adjacent applications. The technology is the technology. I’ll write about it honestly without picking a side, which is what most engineers in this space actually want.

Three: I want to learn it. The best way for me to learn robotics deeply is to build something publicly and document everything. The audience is a side effect of the learning, not the goal. The goal is becoming someone who can build an autonomous quadcopter from scratch.

What this isn’t

This is not a hobbyist blog about toy drones. The 2013-2016 era was great for that and it had its moment. This era is engineering builds for engineers — or for the engineers who want to become engineers. If you’re looking for FPV freestyle content, racing guides, or cinematic drone photography, this isn’t the site.

If you’re an engineer who’s been meaning to break into autonomy and wants a concrete project to follow, this is the site.

The cadence

• Weekly blog post (~1,500-3,000 words, Friday or Monday morning)
• Weekly YouTube video (10-15 min, mostly build footage + screen recording)
• Weekly newsletter (the post + brief commentary, no upsells)
• GitHub commits throughout the week as the build progresses
• 5 hours/week total. This is a side project run sustainably.

How to follow

• Subscribe to the newsletter — one email per week, no spam
• Star the repo on GitHub — all the code, BOM, and CAD
• RSS feed — for the feed readers still standing
• Reddit — I’ll cross-post major posts to r/diydrones, r/robotics, r/Multicopter, and r/ROS

First technical post drops next week. Subscribe if you want it in your inbox.

— Shane