SpotHub FPV: the hangar, the logbook and the field

Every FPV pilot I know keeps their hobby in five places at once. The parts list is a spreadsheet, or an AliExpress order history. Which pack sagged last week lives in somebody's head. The Betaflight dump is a .txt on a laptop that may or may not still exist. The good field near town is a pin in a chat from two summers ago. And the logs sit on the radio's SD card until it fills up.

SpotHub FPV is my attempt to put all of that in one place. It started as a private hangar for my own quads, and this blog is the first part of it that anyone can read.

What it does today

A hangar of builds. Each quad has its own page: what is fitted to it, what it cost, what broke and how it was repaired, and photos of it. A build is in planning, flying, down waiting on a part, or retired, and the hangar shows which at a glance.

A parts inventory. A part is a kind of thing — a T-Motor Velox 2550KV — and you own units of it, four motors, two receivers. Units are fitted to builds and taken off again, so the shelf always knows what is spare and what is in the air. Paste a shop link and it fills in the name and picture; record what you paid and the build's cost adds itself up.

Firmware snapshots. Paste a Betaflight CLI diff or dump and it is kept against the build with a date. Two snapshots compare side by side, so "what did I change before it started oscillating?" has an answer. Any snapshot downloads again as the file Configurator expects.

A flight logbook. Drop the radio's whole LOGS folder — EdgeTX CSV — and every flight in it lands in the logbook, grouped into sessions, matched to the quad it was flown on. Only new files are uploaded. Betaflight blackbox .bbl files come in the same way and add what the radio never sees: pack voltage, current and charge used. A GPX track from a phone or goggles adds the path. Each flight then has a timeline — link quality, sticks, voltage, altitude — and a map of where it went.

Packs, tracked by flying. Mark which battery flew which flight and each pack builds up its own record: cycles, airtime, average sag, and whether that sag is getting worse. A tired pack shows up before it puffs.

Flying spots. A map of places to fly, with notes, a video, and directions. At the field, one tap saves where you are standing and you name it later. A spot can stay private, be shared by link, or be listed for other pilots, who can ask questions about it.

What it does not do

It does not track you. There are no analytics and no ad scripts. Photos have their location data stripped on the server before they are stored, because a photo taken at a home field is a home address. Videos are YouTube links that load nothing from Google until you press play. Map tiles come from OpenStreetMap, and nothing else ever sees a spot's coordinates.

Who it is for

Right now, me and a few pilots I fly with. Signing in is by invitation while the rough edges get found, and while the boring but essential parts — backups first — are put in place. Everything you are reading here is public; the hangars, logbooks and spots behind it are private to their owners unless they choose to share them.

What comes next

Posts here will be about builds, repairs and the things the logs turn up — the kind of write-up I wish I had found when I was choosing parts. If you fly and this sounds useful, the comments are open to anyone signed in, and I would like to hear what you keep track of that I have missed.

See you at the field.