Aviation Safety Reporting demo
Reads, classifies and routes every employee safety report for airline safety analysts 1:32
What the demo shows
Reads, classifies and routes every employee safety report for airline safety analysts
Eight agents read every report the moment it is filed. One reads and de-duplicates, one proposes the event type, and a second reader classifies and scores it blind and must agree. Another links earlier reports, tech log entries and deferrals on the same aircraft and system, so the risk score moves with the history and says why. A notice checker tests six regulations, asks the one question that decides a notice and starts the clock, and a router proposes owners and drafts the reporter's thank-you. The analyst works one report at a time on a tray, asks the agents anything, settles disagreements with a reason code and signs; corrections become rules only the Manager approves.
Transcript
- Aviation Safety Reporting Reads, classifies and routes every employee safety report for airline safety analysts.
- Big airlines get hundreds a week read by hand, so repeats look new.
- Overnight, agents read 71 Corvain reports.
- Thirteen need Dana. A purser on Flight 66 smelled burning at Galley Oven 3.
- Agents proposed the event type, citing the reporter's own words.
- They link two earlier reports on the same oven, both scored low.
- With that history, the risk moves from medium to high.
- A blind second reader disagrees.
- Dana decides a repeat on one unit.
- An FAA report is due Monday.
- Agents ask about flame and start the clock.
- Dana signs. It goes to technical operations and cabin safety.
- Every proposal cited, every decision signed, every step logged.
- Every report routed the same day, and no notice clock missed.
- Built on Botminds: agents, data, screens, and governance on one platform.
Transcribed from the film’s narration. Captions are on the player.