How Aviation Teams Build Trust for Early Safety Reporting

Small concerns get raised when the first person to raise one gets thanked, visibly and quickly. That is the leadership response I learned the hard way and have used since playing football and now running Simply Noted.

In football, a player who says "my read was off on that play" in the film room either gets respect or gets embarrassed, and the whole team watches which one happens. Coaches who responded with a simple "good catch, thank you" got more honesty the next week. Coaches who reacted with irritation got silence.

I apply the same rule as a founder. When someone on my team flags a small problem, like a note that looks off or a process step that feels risky, my first words are always thanks, before any questions about why it happened. I also share the story with the team, with that person's permission, so they see that speaking up is valued.

Small concerns are cheap to fix and expensive to ignore. If the person raising them feels safe, you hear about them early. The response that builds that trust is not complicated, it is just consistent.

1. Stop depending on courage to report problems. Make reporting problems as routine as pulling the squawk box and completing the squawk sheet for each aircraft before leaving the cockpit for the day. List all items that are not functioning 100% such as a slightly loose trim wheel or an alternator light flickering. Attach the completed sheet to the cockpit bulkhead with a sticky note. All problems noted by subsequent pilots are listed on the same sheet and problems noted by several pilots with only vague descriptions start to form into a pattern or trend.

2. Close the loop fast. I remember a low-time pilot report a slight nosewheel shimmy on landing. The plane was pulled off the schedule the next afternoon and a worn shimmy damper was found. The worn shimmy damper was then taped to the front of the clipboard with a note that said "Good catch. Replaced. Thanks". None of us gave a speech to the pilot but every time that cockpit was opened for the next month or so the clipboard was pulled down and the old shimmy damper seen. People do not stop reporting because they are afraid. People stop reporting because after they report nothing seems to happen. Silence is worse than a bad accident. Show the fix and show it fast.

In aviation, a strong safety culture starts when people can speak up, regardless of their role or experience. Whether you're an airline executive, a pilot, or a crew member, you should address your concerns, especially when they involve passenger safety and welfare. Leaders should respond to those observations with curiosity and an open mind rather than taking them as criticism. Watch for potential risks flagged by anyone on the team. I'd rather take false alarms than miss the real one, so be thankful if someone notices something.

Teams gain confidence when they can see that reports lead to real improvements. Aviation organizations can share grouped findings without naming the people who submitted them. Updates can show what risks were found, what changes were approved, and whether those changes are complete.

This feedback proves that reporting is useful rather than ignored. Simple dashboards, brief meetings, and safety bulletins can keep progress visible across the organization. Share regular safety progress updates so reporters can see the value of speaking up.

Safety reporting works better when safety investigations are kept separate from disciplinary reviews. The safety team should focus on finding causes, system gaps, and ways to prevent a repeat event. A disciplinary process should only address deliberate rule breaking or unsafe behavior that was clearly reckless.

This separation helps employees share facts without fearing that every report will become a punishment case. Managers should explain the boundary between these processes before an incident occurs. Set clear investigation boundaries and communicate them to every team member.

Early reporting is more likely when the process is quick and easy to use during any shift. Employees should be able to report through simple digital tools, phone options, or paper forms when needed. The reporting method should work for flight crews, maintenance staff, dispatchers, and ground teams.

Forms should ask for useful facts without creating a long burden during a busy workday. Training should show workers how to submit a report and where to get help. Make reporting tools available and simple for every worker today.

Aviation teams build trust by offering confidential reporting channels that do not punish people for honest mistakes. Staff need to know that reporting a hazard will not automatically harm their job or reputation. Clear written rules should explain when confidentiality applies and what rare situations require further action.

Leaders must follow these rules every time to make the promise believable. When employees see fair treatment after a report, they are more likely to speak up early. Create and clearly explain a non-punitive reporting channel today.

Independent oversight can protect reporter identities and strengthen trust in the safety process. A neutral safety office or outside reviewer can receive reports and control access to identifying details. This reduces the risk that a direct supervisor will learn who raised a concern.

Strong data rules should limit who can view reports and how long personal details are kept. Employees also need a safe way to report if they believe their identity was not protected. Establish independent identity protections to encourage honest safety reporting.