RASE: Anonymous Safety Reporting That Turns Incidents Into Learning
Aviation safety improves when people speak up early—before a “minor” issue becomes a major accident. But in the real world, many professionals and even passengers hesitate to report what they saw: fear of blame, fear of retaliation, or simply the feeling that “nothing will change.”
That’s why RASE (Anonymous Report) exists on the Safety Matters Foundation website: a simple, structured way to share safety experiences without naming anyone, so patterns can be seen and risks can be fixed.
What is RASE?
RASE is an anonymous safety reporting portal that allows anyone connected to aviation to submit a safety occurrence or concern—whether you are:
Pilot
Cabin Crew
ATC
Ground staff
Maintenance
Passenger
Or “Other”
It’s designed to capture “what happened” and “what it means,” not “who did it.”
Why anonymous reporting matters
Most safety failures are not “one bad person.” They are system failures: pressure, fatigue, weak SOPs, confusing documentation, poor communication, unclear accountability, or broken compliance checks.
Anonymous reporting helps in three important ways:
People report sooner and more honestly
Recurring patterns become visible (same airport, same phase, same type of error, same workflow breakdown)
Safety learning becomes public, not buried
RASE is aligned with a “just culture” approach: reduce fear, increase truth, and focus on prevention.
How RASE works (simple step-by-step)
Step 1: You submit a report anonymously
The form is deliberately structured so the report is useful—not just a story. You enter:
Date of occurrence
Your category (pilot/crew/ATC/ground/maintenance/passenger/other)
Movement (Flight or Taxi)
Phase of operation/flight (pre-flight, takeoff, climb, cruise, approach, landing, etc.)
Airport (IATA code)
Aircraft type
Weather conditions
Description of what happened
Most importantly, the form clearly asks you to write the description without names or personal identifiers. The goal is to protect people and preserve safety learning.
Step 2: The report is reviewed
Not every submission is published automatically. RASE follows a review-before-publication approach.
Why review?
To remove accidental identifiers
To ensure the report is a genuine safety-related submission
To keep the database clean, credible, and useful
This is where “anonymous” meets “responsible.”
Step 3: Approved reports enter the RASE Safety Database
Once approved, the report appears in the RASE Safety Database, where it can be read by others and filtered by key fields like:
category
phase
airport
aircraft type
weather
The database format makes it easier to spot trends—because safety improvement is driven by patterns, not isolated anecdotes.
Step 4: Patterns drive awareness and advocacy
As the database grows, it becomes a practical safety resource. Repeated themes—fatigue pressures, unstable approaches, maintenance documentation gaps, dispatch errors, ground-handling risks—start to stand out.
This is the real purpose of RASE:
Convert scattered experiences into organized safety intelligence.
What to report on RASE (examples)
You can report anything that represents a safety risk or learning point, such as:
unstable approach pressures
runway/taxiway confusion
SOP deviations driven by time pressure
fatigue-related events
tech/logbook/documentation failures
maintenance workflow issues
communication breakdowns (crew/ATC/ground)
repeated hazards at a specific airport
near-misses, not just accidents
RASE is most valuable for near misses—because that’s where prevention lives.
One simple rule: report the risk, not the person
RASE is not a complaint portal. It is a safety learning tool.
