Scheduling & Dispatch
Build the trip once, check it all the way, bill from what flew.
- AI email-to-quote, a person approves
- Duty & rest engine 135.267
- Two-party release, DO then PIC
On-demand Part 135 · 3–8 aircraft
Scheduling, safety and maintenance. One system, built for Part 135.
Quote, dispatch, risk-assess, maintain and bill every trip from the same record. Built for charter operators flying 3 to 8 aircraft.
Month-to-month · Live in weeks · Your data, exportable any time
The patchwork
Three systems, five logins, and a spreadsheet holding it together.
Every handoff between them is a place where something gets re-keyed, missed or seen too late.
Why one platform →- Squawks phoned in and re-keyed.The pilot calls, someone writes it down, someone else types it in.
- Deferrals that dispatch can't see.The MEL clock runs in one system and the trip is sold in another.
- Hours typed twice.Once for billing, once for the due list, and they rarely match.
- A FRAT in a separate tool that can't stop a release.The score is filed. The trip goes anyway.
- Duty math in the DO's head.Until the leg slips an hour and nobody re-runs it.
Three modules · one record
Run one module or all three. They already talk to each other.
Safety · SMS + FRAT
The complete Part 5 SMS, sized for a five-tail certificate.
- 2-minute FRAT and hazard reports
- Part 5 readiness tracker
- One-click inspector evidence
Maintenance
The due list your dispatcher can actually see.
- MEL clocks on the ops board
- AD alerts within 1 business day
- Keep your tracker or move in, one tail at a time
How it connects
Entered once. Seen everywhere it matters.
A squawk, a deferral or a FRAT score isn't copied between products. It's the same record, and each module reads it.
SchedulingSafetyMaintenance
Flow: Squawk (Maintenance), then Maintenance (Maintenance), then MEL deferral (Maintenance), then Ops board (Scheduling), and FRAT (Safety).
The crew reports it in the app. The deferral and its clock show on the trip before it's dispatched.
Flow: Close-out (Scheduling), then DOM reviews hours (Maintenance), then Due list (Maintenance).
Flight times arrive as proposals the DOM approves. They're never pushed blindly.
Flow: FRAT (Safety), then Release gate (Scheduling), then Safety indicators (Safety).
One FRAT engine, shared by dispatch and safety, that actually gates the release.
Flow: Discrepancy (Maintenance), then Hazard register (Safety).
Maintenance trends become safety signals without anyone filing a second report.
Crew & technician apps
Everything a crew member needs before engine start, even with no signal on the ramp.
Native apps for iPhone, iPad and Android. FRAT, W&B, OOOI times, squawks and receipts work offline and sync when the signal comes back. The DO authorizes the same trip from an iPad.
- iPhone
- iPad
- Android
Stale data shows red, never green.
Every outside value shows its source and age. Unknown or stale blocks release.
The software flags. Your people decide.
A named, qualified person releases, accepts risk and returns aircraft to service. Every override needs a reason.
Your records, your export button, any time.
Append-only history and a full export whenever you want it, with no exit fee.
Who it's for
On-demand Part 135.
3–8 tails. 10–25 pilots.
King Air, PC-12, Caravan, CJ3, XLS, Phenom 300. Big enough to need real Part 135 logic, small enough that nobody wants an enterprise rollout.
Switching
Live in weeks.
We reconcile your history pilot by pilot before you cut over. Keep your current tracker for any tail you're not ready to move.
How switching works →Pricing
A fraction of what competitors charge.
- month-to-month
- no multi-year lock-in
- no per-report fees
- priced per module
Built by pilots and operators who got tired of the status quo
See your whole certificate on one screen.
Book a 30-minute walkthrough, or explore a fully populated sample operator before you connect anything.