Skip to content
Direct2
Book a demo

Safety · SMS & FRAT

The complete Part 5 SMS, sized for a five-tail certificate.

Policy, risk management, assurance and promotion on the same records as your trips and maintenance. A report or FRAT takes under two minutes on a phone, online or off. Every record is inspector-ready the day it's created.

Book a demoExplore the demo operator

Safety at a glance

  • 01

    Every Part 5 element, mapped.

    §5.21 through §5.97, each tied to real evidence from your operation.

  • 02

    Reports and FRATs in under 2 minutes.

    On a phone, started from the trip, with the tail, leg and crew attached.

  • 03

    Works offline.

    Reports, FRATs, audit checklists and sign-offs queue and sync when the phone reconnects.

  • 04

    Anonymous, by how it's built.

    No IP address, no device ID and no account link is stored. Ever.

  • 05

    One-click inspector package.

    Evidence for any date range, organized by Part 5 paragraph.

  • 06

    No per-report fees.

    Fees on reporting kill participation, so there aren't any.

01 · FRAT AND THE DISPATCH GATE

A FRAT with teeth.

Each leg gets its FRAT already filled in from the trip and from maintenance. The pilot confirms, mitigates and submits from the phone, even offline, and the leg can't be released until the FRAT clears.

  • Configurable, versioned models per aircraft type or operation, with templates for single-pilot turboprop, two-pilot light jet and more.
  • Live score as the pilot answers, matching the server. Every auto-filled value shows its source, and the pilot can override it with a reason.
  • Two thresholds. In the caution band, mitigations are required. In the management band, the DO or chief pilot signs off from their phone.
  • Trip-level FRAT for a multi-leg day, with per-leg deltas.
  • Amendment with SIC concurrence. The original FRAT is kept, and the gate re-checks.
  • A gate in the two-party release. An unreadable FRAT shows red, and every override is logged.

  • Auto-filled from the trip.

    Night, crew pairing and experience, duty position, airport, TAF and METAR, and open MEL, CDL and NEF deferrals, with restrictions called out separately.

  • A board for today's legs.

    Not started, complete, pending mitigation and awaiting sign-off, for every leg on the schedule.

  • Works offline.

    The pilot scores and submits at the airplane. It syncs when the phone reconnects.

  • Analytics that feed the SMS.

    Trends by route, aircraft, pilot and season, factor contribution, and completion tracked as an SPI.

A King Air going out with two deferrals doesn't score like a clean airplane.

02 · POLICY AND ACCOUNTABILITY

Safety policy, manual and accountability, signed and on file.

Start from a Part 5-mapped manual and guided questions. The AE e-signs the policy, and the register says exactly who may accept which level of risk.

  • A Part 5-mapped SMS manual template, filled in from guided questions, with revision control. Available as a controlled PDF and as a living document.
  • Safety policy, objectives and a non-punitive code, all e-signed by the accountable executive.
  • An accountability register: AE, management, safety manager, and who may accept which level of risk. Delegations expire.
  • Built for people with several jobs. When the owner is also the AE and the DO, self-approval is allowed and recorded openly.

03 · HAZARD AND OCCURRENCE REPORTING

Reporting, made almost effortless.

One form for everyone, started from the trip. Two lines and a photo, filed in under two minutes, with or without a signal.

  • Under 2 minutes on a phone. Photos and video. Works offline.
  • One form for pilots, mechanics and ground staff. It starts from the trip, with the tail, leg and crew attached.
  • On-behalf entry and external hazard intake under §5.71(a)(8), plus an email-to-report address and transcription of paper reports.
  • A maintenance discrepancy can open a hazard, with links both ways.

04 · CONFIDENTIAL AND ANONYMOUS

Anonymity that comes from how the system is built, not from a policy promise.

The reporter chooses how to report before typing a word, and the system stores only what that choice allows. Confidential reporting is not ASAP; ASAP needs an FAA MOU.

  • The reporter picks the mode before typing: identified, confidential or anonymous, each with a plain explanation.
  • Anonymous stores no IP address, device ID or account link, and the logs are scrubbed.
  • Confidential identity is hidden even in the audit history.
  • Two-way anonymous follow-up through a private reply token.
  • The confidentiality model and its limits are published: subpoena or discovery, and text that identifies the reporter.

05 · QR AND LINK REPORTING

Scan. Report. Done.

The people who see your hazards first often don't work for you. Give them a way in that needs no login.

  • QR codes for the cockpit, the hangar and the FBO desk. No account needed. Codes can be revoked and are rate-limited.
  • For the people outside your company: contract mechanics, FBO and line staff, fuelers and vendors.
  • Their reports count toward your SPIs and your Part 5 readiness.

06 · TRIAGE, INVESTIGATION AND FEEDBACK

Nothing dead-ends.

Every report has a clock, an owner and a recorded decision. When the safety manager is flying, the report goes to someone who isn't.

  • Every report gets a recorded decision. Nothing sits unread.
  • SLA timers: 24 h for confidential and external reports, 48 h for anonymous fatigue reports, 72 h for FRAT signals. Reports escalate to the DO or chief pilot when the safety manager is flying.
  • Accidents and injuries alert immediately, by push, text and email, to the safety manager, DO and AE.
  • AI-assisted triage suggests a classification and flags duplicates. A person always confirms, and the AI never sees confidential identity.
  • An NTSB Part 830 prompt with the decision recorded. It's decision support, not legal advice.
  • Investigations with 5-Whys and fishbone templates and AI-drafted root-cause summaries that a person reviews.
  • Closure feedback is mandatory. The reporter sees the status, and de-identified “here's what we did” bulletins go out. Legal hold is built in.

07 · HAZARD REGISTER AND RISK

Manage risk, not just reports.

Hazards come from reports, FRATs, audits and maintenance. Each one is scored, owned and accepted by someone with the authority to accept it.

  • Hazards from any source, each with an owner and a lifecycle. Duplicates can be merged, and hazards are re-validated on a schedule.
  • A configurable 5×5 matrix with initial and residual scores.
  • Acceptance enforced against authority. Medium needs the DO and High needs the AE, for example. The AE is notified within a minute.
  • Controls have owners and due dates. A hazard can't close until someone reviews whether its controls work.
  • AE roll-up: top risks, ageing mitigations and overdue reviews on one page.
  • §5.57 notices to FBOs, fuelers, shops and brokers from the contacts you already keep, retained 24 months.

08 · MANAGEMENT OF CHANGE

New tail, new strip, new PIC: the MoC starts itself.

When something new shows up in scheduling or maintenance, the system suggests a Management of Change. A person decides whether to run it.

  • Guided SRM on new systems, revised systems and new procedures.
  • Templates for a new type, a mountain strip, a new PIC and a new maintenance vendor.
  • The system suggests an MoC on its own when a new airport, aircraft, PIC or program change appears.
  • Controls flow out to read-and-sign, training and FRAT factors.

09 · SAFETY ASSURANCE

Prove your SMS works with live numbers.

SPIs calculate themselves from trips, FRATs, reports and maintenance. The management review pack builds itself, covers every 5.73(a) item, and locks when the AE signs.

  • A default SPI set, each tied to a safety objective. Objectives with no SPI are flagged.
  • Signals arrive on their own from scheduling (duty near-misses, overrides, disruptions) and maintenance (repeat items, deferral ageing, reliability).
  • FDM/FOQA event import. Flight data events from your flight data provider feed SPIs, trends and the hazard register.
  • Internal audits and IEP on mobile checklists with a photo per item, offline, for ramp, base, cabin and Part 5 audits. A failed item raises a corrective action on the spot.
  • Corrective actions escalate when overdue and close only when verified effective.
  • Role dashboards and a report library. The AE view is eight tiles or fewer.

10 · SAFETY PROMOTION

Know who signed rev 4, and who's still on rev 3.

Training, bulletins, meetings and read-and-sign live where your crews already are: on their phones, tied to the document revision.

  • SMS training on the phone, assigned automatically to new hires and on role changes. SCORM support, and one training view per person.
  • Targeted bulletins. Safety-of-flight items are pushed.
  • Read-and-sign for any controlled document: GOM, training manual, OpSpecs notices. Overdue sign-offs escalate.
  • Safety meetings whose agenda builds itself from live data. A meeting can also count as the §5.73 review.
  • A lessons-learned library. Searchable by the whole crew.

11 · EMERGENCY RESPONSE PLAN

The real test of an ERP is the first hour.

Activate the plan and the right checklist appears, every action is timestamped, and the contact tree is called until people acknowledge.

  • The ERP is a controlled document, with contact trees ready on mobile.
  • Live activation. The right checklist appears, actions are timestamped, and the contact tree is notified by push, text and voice with acknowledgements tracked.
  • Drills are scheduled and recorded. Built in, not an add-on.

12 · RECORDS AND AUDIT TRAIL

Safety history must never be hostage.

  • §5.97 minimums are locked. You can make them longer, never shorter.
  • Legal hold. Every purge is logged.
  • The audit log can't be changed.
  • Full self-service export, any time.

13 · ASAP AND NASA ASRS

ASAP when you have an MOU. ASRS for every pilot.

  • ASAP workspace with separate permissions and the ERC workflow. It switches on only after your MOU is recorded.
  • NASA ASRS pre-fill from the pilot's own report. It shows the 10-day window, and the pilot files it personally.

14 · WORKS WITH ANY SCHEDULER

Native with ours. Standalone with yours.

  • Native with Direct2 Scheduling: the FRAT is a release gate and trips fill it in.
  • With any other scheduler, the SMS stands on its own, and a public API and webhooks connect it.
  • An outage on one link never blocks a FRAT or a report.
Part 5 declaration
May 28, 2027

Know where you stand on every element.

A live readiness tracker maps §5.21 through §5.97 to real evidence. It's an indicator, not an FAA determination, and it can't be gamed by setup alone.

Check your readiness

Who it's for

One report, start to finish

Slush on the KEGE ramp, from a 90-second report to a closed loop.

Every step happens in the same record. The reporter hears what happened.

Watch it in the demo operator
  1. 09:12

    A 90-second report, filed offline.

    At KEGE, Captain Ruiz finds slush packed around the ramp. They tap Report on the trip in the crew app, choose Identified, write two lines and add a photo. There's no signal, so it queues. The tail, leg and crew are already attached.

  2. 09:40

    Triage from a phone.

    The report syncs as they taxi in and the SLA clock starts. The safety manager is mid-trip and triages from their phone. AI suggests “ground ops / FBO”, and they confirm it. The NTSB 830 prompt comes up, and they record “not reportable”.

  3. 09:46

    HZ-017, rated 3C High.

    The report becomes a hazard. High is above the safety manager's authority, so the AE is notified within a minute and accepts the plan.

  4. Same day

    A §5.57 notice and a corrective action.

    A notice goes to the FBO and the fuel vendor from contacts already in the vendor list. A corrective action opens with an owner and a due date, and it escalates as it ages.

  5. Day 12

    Verified, then closed.

    Someone checks that the control worked. Residual risk is scored 2B and accepted, and Captain Ruiz gets the closure feedback.

More from the demo operator

Three more ways a safety program actually runs.

Anonymous fatigue report

Anonymous, and still a conversation.

  1. 01A first officer worried about back-to-back early shows chooses Anonymous before typing a word, and gets a reply token.
  2. 02The fatigue SLA is 48 h. The safety manager is on a three-day trip, so the report escalates to the DO.
  3. 03The DO sees that scheduling's duty-limit near-miss signals point the same way, and opens a scheduling hazard.
  4. 04The safety manager asks a follow-up. The FO answers through the token, still anonymous. A de-identified bulletin tells the crew what changed.

FBO report by QR code

A line lead with no login.

  1. 01A line lead sees a fuel truck back within feet of a parked PC-12. They scan the QR sticker on the FBO desk and choose Confidential.
  2. 02The report lands tagged “interfacing person · KEGE FBO desk” with a 24 h SLA.
  3. 03An investigation follows and the DO signs off. A hazard is created and a §5.57 notice goes to the FBO and the fuel vendor.
  4. 04The line lead gets a thank-you.

Live FRAT gate

27, then 36, then released.

  1. 01At 06:00 the PIC opens tomorrow's leg. The FRAT is filled in, including one Cat C MEL item from maintenance, and each value shows its source.
  2. 02The score is 27, Moderate. The PIC enters a mitigation, and the chief pilot approves from their phone with a one-line rationale.
  3. 03A delay pushes the arrival later and the TAF worsens. The PIC amends to 36, High, with SIC concurrence. The original is kept, and the DO signs.
  4. 04The gate clears, the DO authorizes, the PIC accepts, and the leg goes. If the FRAT couldn't be read, the gate would show red.

Questions

What safety managers and AEs ask first.

All FAQs
Is my anonymous report really anonymous?

Yes, by design. We store no name, account, IP address or device ID, and the logs for the anonymous form are scrubbed. You can still get answers through a private reply token.

We can't protect what you type yourself, and in a small company the details of a report may identify you. Records can also be reached by subpoena or discovery. If that's a concern, confidential mode keeps your name visible only to the people your company designates.

What's the difference between confidential and anonymous?

Part 5 requires a confidential system: your identity is known to a few people and protected from everyone else, even in the audit history. Anonymous is an extra mode your company can turn on or off. Confidential mode is always available.

Is confidential reporting the same as ASAP?

No. ASAP requires an FAA MOU. Once you record your MOU, the ASAP workspace switches on, with its own permissions and ERC workflow. If your ASAP runs through an outside administrator, you can link its outcomes in.

Pilots can also pre-fill their own NASA ASRS report from their safety report. They file it personally.

Does the FRAT really fill itself in?

Yes. Night, crew pairing and experience, duty position, airport, weather and open MEL deferrals come from the trip and from maintenance, and each value shows its source. The pilot confirms, overrides with a reason if something is wrong, mitigates if needed and submits, usually in under two minutes.

What if there's no signal at the airplane?

FRATs, reports, audit checklists and acknowledgements all work offline and sync when the phone reconnects. If dispatch can't read a FRAT result, the gate shows red, never a stale green. Your override procedure applies, and every override is logged with a reason.

Can we use it with another scheduler?

Yes. Every SMS workflow, including the FRAT, works on its own. A public API and webhooks connect other systems, and an outage on one link never blocks a FRAT or a report.

We have a binder or another SMS platform. Can we bring our history?

Yes. There are import mappings for common SMS platform exports, and CSV templates for spreadsheets and binders. You preview the mapping and fix errors before you commit, a batch can be rolled back, and a reconciliation report shows exactly what came over.

Do you charge per report or per FRAT?

No. Fees on reporting kill participation. For pricing, talk to sales.

Can our SMS consultant work in it?

Yes. Consultants get their own login, with permissions per client and clean switching between clients.

What does an FAA inspector see?

Whatever you give them. That can be a one-click evidence package for any date range, organized by Part 5 paragraph, with confidential identities and ASAP content removed. Or it can be a time-limited, read-only guest login with its own activity log, which expires on its own.

How long do you keep records?

At least the §5.97 minimums: safety assurance records, including FRATs, for 5 years; training records for the duration of employment; safety communications and §5.57 notices for 24 months; and risk controls for as long as they're relevant.

You can make these periods longer, never shorter. Legal hold stops all purging, and every purge is logged.

Can people outside our company report?

Yes. Print a QR code for the FBO desk, the hangar or the cockpit. Outside reporters don't need an account, and they can still report identified, confidential or anonymous.

Does it help with NTSB reporting?

Yes. Occurrence reports are checked against the Part 830 immediate-notification criteria, and your decision is recorded. This is decision support, not legal advice.

See your SMS run between legs.

Book a walkthrough, or explore a fully populated sample operator with live FRATs, reports in triage and a Part 5 readiness score.

Book a demoExplore the demo operator