Built for pilots by an operator who lived the ramp.
HangarOS exists because the operating layer of a flight school — dispatch, maintenance, training, billing — has been duct-taped together with software written by people who’ve never seen a dispatch desk. We’re fixing that.
- Student Pilot · Working on PPL
- Software Engineer
- Founder · OrangeTree Technologies
A school running on three browser tabs and a paper logbook.
Leo started flight training and saw a Part 61 school in North Carolina running on three browser tabs and a paper logbook. The school was great. The software wasn’t.
Dispatch lived in Google Calendar. Maintenance lived in an Excel file. Training records lived in a binder. Invoices lived in QuickBooks. When a student didn’t show, four tools needed to be reconciled by hand.
HangarOS is what would have made that school’s ops team go home at 5pm. It’s what we now build for every flight school that wants the same.
Three rules we don’t bend.
Operators shape the product.
Every screen is shaped by feedback from working CFIs, dispatchers, and instructors using HangarOS. We don't guess what dispatchers, instructors, or students need — we ask, then build, then watch them use it.
Restraint over decoration.
Approach plates have two colors and rigorous layout. Our software does too. No gradients chasing fashion. Tail numbers, METARs, Zulu times — the data carries the visual identity.
Modular over monolith.
You shouldn't pay for a Maintenance module when your spreadsheet works fine. Pick the modules you need today; add the next one when you actually need it.