Run your SMS from the FBO lounge.
You do an SMS job between trips, often on top of the chief pilot's. Direct2 brings reports to your phone, escalates them when you're flying, and builds the agenda and the review pack from what already happened.
- Part 5
- 5.71
- 5.73
- NTSB 830 prompt
Sound familiar?
The SMS happens between trips. The reports don't wait.
Reports ageing while you fly
A fatigue report comes in on day one of a three-day trip. By the time you're home, it's a week old and the pilot thinks nobody read it.
Meetings built from scratch
Every safety meeting starts with an empty document and an afternoon of pulling hazards, corrective actions and SPIs from three places.
Audit week panic
An auditor asks to see the management review. You know it happened. Finding the minutes, the sign-off and the data behind it takes days.
What you get
Every report moving, every review ready, wherever you are.
Reports escalate while you fly
Each report type has a service-level clock. If you can't get to one in time, it escalates to the DO or your named backup, with the report and its history attached. You see the hand-off when you land.
Confidential and anonymous, with a reply channel. Anonymous reporters get a reply token, so you can ask a follow-up question and they can answer without being identified. Confidential reporting is not ASAP.
A readiness tracker that counts what's operating
Every Part 5 element is mapped, and each one is scored from what's actually running: reports triaged, reviews held, training completed. Not just what's configured. Every gap says why.
An indicator, not a determination. The tracker shows where you stand. The FAA acknowledges a Declaration; it doesn't approve it.
- Safety
Agendas that build themselves
Open hazards, ageing corrective actions, SPI trends and new reports go straight onto the next safety meeting's agenda.
- Safety5.73
Review packs in minutes
Flag the meeting as the management review and the pack covers every required item. The AE signs, and the record is locked.
- Safety
Corrective actions that prove themselves
Each action has an owner and a due date, escalates as it ages, and closes only when someone verifies it worked.
- Safety
Mobile audits and ramp checks
Run an audit or ramp check offline on a phone, with photos. A finding opens a corrective action before you leave the ramp.
A day with Direct2
Slush on the Eagle ramp.
One hazard report, closed loop, from the safety manager's seat.
See the Safety module09:12
A captain reports slush packed around the KEGE ramp from the crew app, with no signal. It queues, then syncs as they taxi in. The tail, leg and crew are already attached.
09:30
You're mid-trip. You triage from your phone, and AI suggests ground ops / FBO. The NTSB 830 prompt comes up and you record not reportable.
09:34
You promote it to hazard HZ-017, scored 3C High. That's above your authority, so the AE is notified within a minute.
09:40
A 5.57 notice goes to the FBO and the fuel vendor from the vendor list. A corrective action opens with an owner and a due date.
Three weeks later
The fix is verified, residual risk is scored 2B and accepted, and the captain gets the closure feedback.
Across the three modules
See your SMS run from a phone.
Bring a report you triaged last month. We'll take it from intake to verified corrective action, then build the next meeting's agenda, with a safety specialist.