botminds.aiRequest a demo

Aviation Safety Action Program (ASAP) demo

Prepares each ASAP report for the Event Review Committee, for ASAP managers and the ERC 1:32

Book a demoExplore the solution

What the demo shows

Prepares each ASAP report for the Event Review Committee, for ASAP managers and the ERC

The next Event Review Committee meeting as a docket built by agents. A report reader removes names on arrival and pairs crewmates' reports into one event; an eligibility checker tests each event against the agreement and AC 120-66C criterion by criterion and flags, never excludes, a possible exclusion; an event investigator builds the timeline and likely causes from the reports, ATIS, charts and the navigation database; a pattern finder links similar reports and asks the FOQA gatekeeper for counts only; a precedent finder brings the committee's own decisions and whether they worked; an action drafter proposes corrective actions, systemic first; a packet checker re-checks every packet for identifying details and every consent item, and says when it disagrees; an action tracker writes the minutes, assigns actions, reminds owners, drafts feedback letters and measures the effect at 90 days. The three seats read the same six-step packet with their own private notes, take positions with a reason and a signature, and decide by consensus, or the FAA member decides when there is none.

Transcript

  1. Aviation Safety Action Program.
  2. Agents prepare pilot reports for the Event Review Committee.
  3. 62 of 94 U.S.
  4. airlines run one, with dozens of reports a week.
  5. Today, 76 reports, 61 events, 12 to discuss.
  6. First, CV-1280 into Denver, an altitude deviation.
  7. Eligibility is checked against the agreement.
  8. Every criterion cited. names removed.
  9. Three earlier reports describe the same chart note, and the counts agree.
  10. A chart fix worked in Phoenix.
  11. Retraining crews did not.
  12. The agents propose a chart change in a bulletin and add training on request.
  13. At 9, the meeting opens, and the three seats state their positions.
  14. Consensus is recorded, for actions go to their owners.
  15. Every statement cited, every position signed, every step logged.
  16. 61 packets ready two days early, every action tracked until it works.
  17. Built on Botminds: agents, data, screens, and governance on one platform.

Transcribed from the film’s narration. Captions are on the player.