What Pilot-Next deliberately doesn't do

Every aviation-software vendor eventually hears the same request: can you also do X? Every vendor that says yes to all of them eventually becomes slow, bloated, and bad at the thing they started out good at.

Pilot-Next is deliberately narrow. It handles aircraft operations — scheduling, flight logging at the booking level, invoicing, the pilot account ledger. Everything else is out of scope on purpose. Here's what we don't do, and what we think you should use instead.

We are not a pilot logbook

Your logbook is yours. It has to follow you between aircraft, between clubs, between jobs, and across decades. Tying it to a single club's admin tool is a bad idea — the day you leave the club, your logbook shouldn't leave with them.

Dedicated logbook apps already do this well. ForeFlight, CloudAhoy, MyFlightbook, LogTen, ZuluLog — pick the one that fits. They handle legality, currency calculations, export to FAA/EASA formats, and integration with your charts. Pilot-Next doesn't compete with that layer.

We don't track pilot currency or credentials

Recent takeoffs and landings, flight review, IPC currency, medical class and expiry, instrument proficiency — these are all personal-pilot concerns. They matter to the pilot, the pilot's instructor, and (sometimes) the chief pilot of a commercial operation. They don't usually matter to the club's billing system.

If your club wants to enforce currency before booking — "you need a current flight review to reserve this aircraft" — that's best implemented as a policy question, with a pre-flight checklist or a scheduling rule, not by embedding an entire currency-tracking subsystem into the booking app.

We don't do flight training

If you're running a Part 61 or Part 141 school, you need a lot of things Pilot-Next doesn't have: syllabus tracking, stage check records, ACS/PTS progress, student grade reports, training course outline administration, DPE coordination. That's a whole domain of software, and it's not aircraft management — it's training management.

Schools often run both kinds of tools side by side: Pilot-Next for the aircraft side (bookings, Hobbs/Tacho, rates, invoicing) and a dedicated LMS for the syllabus and progress side. That's the right architecture. Don't make one tool do both badly.

We don't track ADs or airworthiness

Airworthiness Directive compliance, 100-hour and annual inspection status, service bulletin tracking, ICA compliance, CAMO-level maintenance planning — these live closer to the maintenance organization than to the booking app.

Pilot-Next does track aircraft hours (Hobbs and Tacho) and can flag you when an aircraft is approaching a configured interval. That's useful for operational planning — "don't schedule a booking that pushes us past the annual". But we don't replace what your A&P, IA, or CAMO does. For real AD tracking and airworthiness compliance, use a dedicated tool.

What we do is tight

• Scheduling: book the aircraft, no conflicts, no drama.
• Flight logging: Hobbs/Tacho at the booking level. Optional per-leg logs if you want them.
• Invoicing: generate invoices from the flights, PDF, email, file in S3.
• Ledger: every deposit, payment, and invoice tracked against the pilot's account balance.
• Rates: hourly, per-booking, or manual — configurable per aircraft and per pilot.

That's it. That's the product. The more ways we could invent to stretch it, the worse the core experience would get for the clubs and partnerships that just want the above to work.

Integration, not replacement

The right architecture is a focused tool for each domain, connected where it makes sense. Pilot-Next does the aircraft operations layer. Your logbook app, your training LMS, your maintenance tracker, and your currency monitor each do theirs. If you have fifteen aircraft and eighty pilots, you probably want all four — specialized, not merged.

Doing fewer things well is a strategy, not a shortcoming.