The Rule, Stated Plainly
A crew noticeboard is not a reporting system. If something happened, it belongs in your operator's safety report and, where applicable, in the confidential national reporting scheme — not in a post. There are three reasons and all of them are practical.
First, only a formal report reaches the people who can change anything: the safety department, the regulator, the aerodrome, the handling agent, the manufacturer. Second, formal schemes are protected and de-identified by design, and an informal post is neither. Third, an informal account is usually incomplete in exactly the ways that matter, because it is written from one seat and from memory.
How the Real Systems Work
Aviation's safety record rests on a reporting culture that was built deliberately over decades: report freely, get protection from punitive use of the report, and let the aggregate data reveal the patterns no single event shows.
- NASA Aviation Safety Reporting System — the US confidential scheme, run by NASA rather than by the regulator precisely so that it is not an enforcement channel. Reports are de-identified, and the database is public and searchable. If you read one thing about how this works, read the ASRS programme description.
- Operator safety management systems — every commercial operator runs one, and the internal report is the first step for anything that happened on your aircraft.
- Mandatory occurrence reporting — in the EU and elsewhere, certain occurrence categories must be reported to the authority under protected conditions. EASA publishes the framework.
- NTSB and the other national investigators — for accidents and serious incidents, with published findings.
- ICAO's safety programme — the international framework the national schemes sit inside.
What Makes a Report Useful
Written from the crew room rather than from a textbook:
- Write it soon. Detail decays within hours, and the details that decay first are the ones about your own state and reasoning.
- Describe what you saw and did, not what you concluded. The analysis is someone else's job and your interpretation is the least reliable part of the account.
- Include the boring context — how long you had been awake, what the weather was, how many sectors, who else was involved, what the time pressure was. That context is what turns one event into a pattern.
- Report near misses. The events with no consequence are the cheapest possible source of information and are massively under-reported.
- Report ground events too. Ramp damage, near misses with equipment, lighting failures and handling problems are exactly the category this industry loses people in, and they are the least reported of all.
Reading Other People's
The best use of a layover hour. CALLBACK collects short de-identified ASRS reports by theme every month and is written to be read rather than studied. The value is not in the outcomes — most of them are nothing — but in recognising your own last week in somebody else's account of theirs.
What Stays Off This Site
No operator names, no station-identifiable events, no individuals, no dates and no photographs. The section exists to make the case for reporting properly and to point at where the real material lives. See Safety Corner for the ground rules this whole section runs under.