Safety management in aviation rests on discipline, and discipline sounds like the opposite of ignoring things. Yet small flight departments and training organisations often find that their safety management system, or SMS, works best when somebody has decided in writing what the team will not spend attention on. This article tests six common myths about that idea. It is informational only. Mandatory reporting, regulatory duties and the instructions of your authority and accountable manager are never optional, and nothing below suggests setting them aside.
Myth one: a serious SMS pays attention to everything
The intuition is understandable: safety is serious, so every input must matter. The reasoning does not hold up under analysis. Attention is finite, and a team that treats every item as equal ends up treating none well. Human factors teaching in aviation makes a related point: a person flooded with signals has a harder time noticing the one that counts.
What follows from this is not that some inputs are unimportant, but that a team should choose which categories get its limited review time and state the rest as out of scope. A written scope is a safety tool in its own right, because it makes gaps visible instead of leaving them to chance.
Myth two: declining a task means lowering the standard
Consider a quality meeting with a long agenda of administrative side issues: stationery requests, formatting disputes, minor cosmetic complaints. A manager who removes those items from the safety forum has not lowered a standard. The standard concerns hazards, controls and occurrences, and the forum protects its time for those. The administrative items still have a home elsewhere.
The test is simple. Ask whether the item could affect an operational hazard or a required duty. If yes, it stays on the agenda. If no, it moves to a different channel, and the safety forum does not chase it.
Myth three: more reading material equals a stronger culture
Organisations sometimes circulate every bulletin, article and incident summary they can find, hoping a flood of information builds awareness. Reasoned analysis suggests the opposite risk. When staff receive far more than they can read, they stop reading carefully, and the bulletins that truly matter are lost among the rest.
A more defensible approach is a curated feed. Choose a short list of trusted sources, such as your authority’s notices and your own occurrence reports, and agree openly that other material is optional. The team knows what is expected of it, and the expectation is realistic.
Myth four: ignoring outside opinion makes a team insular
This myth deserves a fair hearing. Closed teams can indeed miss lessons. But refusing to chase every opinion is different from refusing to learn. A safe pattern is to route outside ideas through one person or one meeting, where they are judged against your own hazards and procedures. Adoption happens through that gate, not through casual conversation in the crew room.
In other words, a team can be open and selective at the same time. Ideas are welcome, and each one must earn its place by connecting to something your organisation actually does.
Myth five: the not-doing list belongs only in the safety office
Staff outside the safety function, such as administrators, schedulers and trainers, also face a stream of low-value demands. They answer repeated queries, join optional meetings and compare equipment for the office. When these demands crowd their day, the hours that remain for their safety-relevant tasks shrink.
That is why a shared not-doing list works best when each role writes its own. A scheduler might decide not to reopen a settled roster rule. A trainer might decide not to review every new app released for exam preparation. Practical side shopping in particular, such as software, devices and local services for the office, can be narrowed to a single trusted reference. True Review Now offers reviews and articles to people weighing up phones, programs and neighbourhood providers, and a team that settles on one such reference avoids a week of scattered comparison.
Myth six: once written, the list never changes
The last myth confuses a policy with a verdict. A not-doing list reflects what was true when it was written. New aircraft, new regulations, a change of staff or an occurrence can all alter what deserves attention. A responsible team schedules a review, perhaps each quarter, and asks two questions. Did anything we excluded turn out to matter? Is there something new that should be excluded?
If an excluded item mattered, it returns to the agenda and the team notes why it was missed. That practice is a form of learning, and it fits naturally into a healthy reporting culture where mistakes are examined without blame.
Why the six beliefs fail together
Each rests on an unspoken assumption that watching more never costs anything. The reality is the reverse. Every added input displaces another, and in a safety context displacement can be costly. The practical answer is not to care less but to care on purpose. In a small organisation this might look like a single page pinned in the briefing room, signed by the accountable manager, listing the categories the safety forum will not take up and where each of them goes instead. Staff then know that a declined item has been routed, not forgotten, and the forum keeps its time for hazards, controls and occurrences.
- Define scope in writing, including what is excluded.
- Keep regulatory duties and occurrence reporting outside the exclusion list entirely.
- Route outside ideas through one gate.
- Give every role its own short not-doing list.
- Review the list on a fixed schedule and record why items move.
Putting the principles to use
A reasonable first step is a short working session with the people who run your safety system. Bring a list of everything that currently reaches the forum: reports, bulletins, requests and recurring meetings. Sort each into three groups: required by regulation or by your own approved procedures, directly connected to a known hazard, and everything else. The third group is where the conversation about ignoring begins, and the accountable manager should sign off the result so the decision is visible and owned.
Handled this way, deciding what to ignore stays firmly inside a safety culture rather than outside it. The list is explicit, reviewed and approved, and it protects the attention that hazard identification and risk control need. Always confirm specific requirements with your authority and with qualified safety professionals, because this article describes general principles and not the rules that apply to your organisation.
