For the submitter
Visibility into what happened to the report, from receipt to closure.
Safety Programs
Connects an employee's report to review, root-cause analysis, corrective action and verification.
ASAP and MSAP workflows follow the operator's program agreement (the memorandum of understanding), with access controlled to the event review committee. Submitters see progress; the safety team owns the response.
Anchor 14 CFR 5.71 employee reporting; ASAP/MSAP program agreements.
For the people doing the work
Visibility into what happened to the report, from receipt to closure.
Clear ownership of triage, analysis and corrective action, with due dates that are tracked.
De-identified trends that show where the same hazard keeps appearing, so leaders act on patterns instead of anecdotes.
This is the confidential employee reporting system 14 CFR Part 5 requires, connected to the safety risk management and safety assurance it feeds.
ASAP and MSAP
Non-punitive safety reporting under the operator's FAA-accepted program agreement. Employees report hazards and their own errors, so the operator can correct the conditions behind them.
The pilot employee group's ASAP. Reports from the flight deck reach that program's event review committee in confidence, so a hazard one crew meets can be fixed before the next crew meets it.
The maintenance employee group's ASAP. Reports from the hangar and the line reach that program's event review committee in confidence, so an error in one task can be fixed before it repeats on the next aircraft.
What the operator gets
Whether a report is accepted, and any protection that follows, is decided under the operator's program agreement by its event review committee, not by Centragen.
ASAP and MSAP
Tell us about your program agreements, your event review committees and the reports you receive today.