One place for the hangar, the logbook and the field
SpotHub FPV keeps an FPV pilot’s quads, parts, Betaflight configs, flight logs, battery packs and flying spots together — instead of in a spreadsheet, an order history, a laptop folder, a chat and a full SD card.
What is in it
Hangar
A page per quad: what is fitted to it, what it cost, what broke and how it was repaired, and photos. Each build is in planning, active, down or retired.
Parts
The shelf. A part is a kind of thing, a unit is the one in your hand. Fit units to builds and take them off again, so spares are always known. Paste a shop link to fill in the name and picture.
Firmware snapshots
Paste a Betaflight CLI diff or dump and it is kept against the build with a date. Compare two side by side, or download one again as the file Configurator expects.
Flight logbook
Drop the radio’s whole LOGS folder and every flight lands in the logbook, grouped into sessions. Each flight has a timeline of link, sticks and voltage, and a map when there was GPS.
Battery packs
Mark which pack flew which flight and each one builds its own record: cycles, airtime, average sag, and whether the sag is getting worse.
Flying spots
A map of places to fly, with notes, a video and directions. One tap at the field saves where you stand. Keep a spot private, share it by link, or list it for other pilots.
Blog
Build logs, repairs and what the logs turned up, written in Markdown with photos. The one part of the site anyone can read.
Getting started
- Sign in with Google. Your account is keyed to your Google identity; nothing else is asked for.
- Add a build in the Hangar — a name is enough to begin. Add photos from its page.
- Add your parts under Parts, with how many you own, then fit them to the build with “Add part” on its page. Record what you paid and the build’s cost adds itself up.
- Save the firmware. In Betaflight Configurator’s CLI, run
diff all, and paste the output into the build’s Firmware section with “Add capture”. - Import your flights. On the Flights page, drop the radio’s whole
LOGSfolder — only files not seen before are uploaded. Add blackbox.bblfiles and GPX tracks the same way. - Mark your packs. Add batteries as a Battery part with one unit per pack, labelled as written on it, then pick the pack on each flight.
- Save your spots. Click the Spots map to add one, or tap “Add location” at the field.
The logs it reads
| Format | Where it comes from | What it adds |
|---|---|---|
| EdgeTX CSV | the radio’s SD card, LOGS folder | flight times, link quality, sticks, radio battery, and GPS when the quad sends it |
| Betaflight blackbox (.bbl) | the flight controller’s flash, over USB | pack voltage, current and charge used |
| GPX | a phone, goggles or GPS logger | the path flown, joined to the flight it lines up with |
What it never does
- No tracking. There are no analytics, ad scripts or third-party trackers on any page.
- Photos lose their location. Every photo is re-encoded on the server and its metadata dropped before it is stored — a photo taken at a home field is a home address.
- Videos load nothing until played. A spot’s video is a YouTube link, and the player is only fetched when you press play.
- Maps come from OpenStreetMap, and nothing else is ever sent a spot’s coordinates.
- Your hangar is yours. Builds, parts, flights and spots are private to their owner unless shared. Only the blog is public.
Who can join
Anyone can read the blog. Signing in is by invitation for now, while the site is young and the groundwork — backups first — is put in place. It is built so that opening it wider changes a setting, not the code.
Fly and want in, or found something broken? Write to hello@spothubfpv.com.