Operational control you can prove, on every leg.
You carry the certificate's risk for every release. Direct2 puts every gate, every override and every sign-off on one record, so the proof is already there when someone asks.
- 135.77 two-party release
- 135.263(d)
- 135.267
Sound familiar?
The release is yours. The evidence is scattered.
Decisions made over text
A pilot texts at 05:50 asking if the trip is a go. You say yes. That decision carries your name and your certificate, and it lives in a phone.
Control you can't prove
You did exercise operational control. Showing it means rebuilding a timeline from a schedule, a FRAT spreadsheet and a maintenance status someone read to you.
A weekend per records request
Your inspector asks for one pilot's duty records for a quarter. You spend Saturday stitching logs, trips and training into something that holds up.
What you get
Every leg released on the record, every exception in front of you.
Two-party release
You authorize, then the PIC accepts. Both signatures sit on the trip with the gate results they saw at that moment. If anything changes after you sign, the release goes back to "re-authorization required".
Never falsely green. If maintenance or crew data is stale or unknown, the gate blocks. It doesn't guess.
One exception dashboard
Not a wall of green. Just what needs you today: blocked releases, overrides, overrun alerts, high-band FRATs and maintenance items coming due, across all three modules.
Operational control without chasing maintenance. Groundings, deferrals and restrictions show up on the release. You don't have to call the DOM.
- Scheduling
Overrides need a reason
Anyone with the authority can override a soft check. Nobody can do it silently. Who, when, what and why go on an append-only trail.
- Scheduling135.263(d)
Overrun alerts
A legally planned leg runs long for reasons outside your control. The reason is recorded, extended rest goes on the pilot's next assignment, and you're told.
- Safety
FRAT board and phone sign-off
See every leg's risk band on one board. High-band legs come to your phone with the factors and a required mitigation.
- SchedulingSafety
Inspection export
Pick a crewmember and a date range. Duty records with the rule version used, flight logs, training, trips and manifests, in minutes.
A day with Direct2
Ground stop at Eagle.
Same trip, same morning, from the Director of Operations' seat.
See how dispatch handles it06:44
FRAT comes in at 37. You add a mitigation, day arrival only, and sign from your phone before you leave the house.
07:10
Ground stop at Eagle. Dispatch delays leg 1 by 1 h 20 m. The system shows the positioning leg home would put the SIC at 14:20 of duty, so dispatch plans an overnight instead.
07:12
The release drops back to re-authorization required. You see what changed, sign again, and the PIC accepts.
Six months later
Your inspector asks about that trip. You export it: both signatures, the FRAT, the change, the reason. Done before the coffee's cold.
Across the three modules
See your own trips released on the record.
Bring a real week of trips. We'll walk through the release, the exception dashboard and an inspection export with a Part 135 specialist.