Launch of Pilotflows
Building a tool to fix the daily frustrations we lived with as pilots.
Why we built Pilotflows
Today we quietly launched Pilotflows — something Ted Staggs and I have been working on together for a while now.
We’re both commercial pilots. Ted is currently flying the B737 for Luxair , and I’ve spent my own share of years in cockpits, flight schools, and dropzones. Over time we kept running into the same set of annoyances that never seemed to get properly solved by the tools available.
Logbooks were the obvious one. Paper ones get lost or soaked. Digital ones are often half-baked: missing proper EASA/FAA currency tracking, analytics that tell you nothing useful. Then there’s the skydiving side — tracking jumps, gear inspections, canopy progression — usually done in scattered notes or basic spreadsheets. Flight schools juggle student progress, scheduling, and endorsements across WhatsApp groups, Google Calendar, and folders of signed PDFs. Aircraft owners and operators fight endless battles with maintenance due dates, tech logs, mass & balance calcs, and making sure everything stays compliant without duplicating effort.
The worst part? None of these things talk to each other. A student finishes a lesson — you still have to manually update their logbook. An aircraft gets booked — maintenance reminders don’t know about it. You export data from one app only to re-enter it somewhere else. It wastes time, introduces errors, and adds stress on days when you’re already tired.
We didn’t want to build another shiny app that solves one narrow problem. We wanted one place where the flow actually makes sense:
- A pilot logbook that shows you real currency & recency at a glance, with automatic time calculations and meaningful analytics.
- Skydiving logs that track not just jumps but gear history and license steps.
- Flight school tools where lessons feed directly into logbooks and progress reports.
- Fleet management that ties scheduling to maintenance, tech logs, and document expiry alerts.
- Digital signatures, shared team views, and even a simple member shop for clubs/dropzones.
Everything is connected so information moves forward instead of sideways. We built it under TEGI, starting small with real use cases (Ted kicked off early mass & balance experiments years ago), then iterated constantly with feedback from other pilots, instructors, and operators who were willing to test broken versions and tell us exactly what sucked.
It’s not perfect yet — mobile experience still needs love, import from other loggers (ForeFlight, Garmin, etc.) will get better, and there are more integrations coming. But it already removes a surprising amount of the quiet friction we used to accept as normal.
If any of this sounds familiar from your own flying — whether you’re logging hours, running a school, jumping, or managing a few aircraft — take a look at https://pilotflows.com. Try it for free (30 days, no card needed). We’re genuinely interested in hearing what still feels off or what we missed.
Thanks to everyone who gave input along the way. Flying is hard enough without fighting your tools.