Kicking the Tires on Boeing's Safety Program

I used Boeing in another class before, so I already know a few things about them.

For my final research paper I want to figure out if Boeing's safety program actually works, or if it is mostly paperwork covering the same gaps that got them in trouble with the MAX crashes and the door plug on Alaska 1282. The organization I am assessing is Boeing Commercial Airplanes, specifically how they structure and monitor safety through SMS.

Boeing is huge. Over 140,000 employees across commercial aircraft, defense, and space. Their safety program uses the FAA's four pillar framework: Safety Policy, Safety Risk Management, Safety Assurance, and Safety Promotion (Federal Aviation Administration, 2024). Their website says all the right things. Safety first. Transparency. Protecting the flying public (Boeing, n.d.). But after the FAA grounded the MAX 9 fleet and the Department of Justice started breathing down their necks, those words hit different. Every company says they care about safety. The question is whether the system catches problems before they leave the factory.

That is where assessment comes in. The FAA describes SMS as a formal top down organization wide approach to managing safety risk (Federal Aviation Administration, 2024). Stroeve, Smeltink, and Kirwan (2022) hit the nail on the head. SMS is often seen as bureaucratic and separate from actual operations. Too focused on catching people breaking rules instead of supporting real safety where the work happens. That is the trap I worry Boeing fell into. When your SMS becomes a compliance exercise you get missing bolts and undocumented removals.

I have seen that gap on the flight line. Management thinks a procedure works because it is in the manual. Ten hours into a shift when the jet needs to launch, that procedure might get skipped. Assessment forces you to look at actual behavior instead of intended behavior. For Boeing that means asking whether their quality inspections catch missing bolts and production errors, or if those things still slip through like they did with Alaska 1282. Adjekum (2016) found that SMS needs both policy implementation and process engagement to actually work. 

Another reason assessment matters is the numbers. Johnson and Avers (2012) showed that one maintenance organization spent $205,000 on fatigue training and got a 312 percent ROI over six quarters with nearly 30 percent less aircraft damage. When you can show leadership that safety spending pays for itself, safety stops being the first thing cut. At Boeing's scale even a small improvement means millions saved and lives protected.

Fancy safety charts do not mean much when a door plug blows out at sixteen thousand feet.

References

Adjekum, D. K. (2016). An evaluation of the relationships between safety management system initiatives, transformational safety leadership, self-efficacy, safety behavior, and safety-related events mediated by safety motivation in collegiate aviation [Doctoral dissertation, University of North Dakota]. ProQuest Dissertations Publishing. https://www.proquest.com/dissertations-theses/evaluation-relationships-between-safety/docview/1862014153/se-2?accountid=27203

Boeing. (n.d.). Safety. https://www.boeing.com/safety

Federal Aviation Administration. (2024). Safety Management System (SMS). https://www.faa.gov/about/initiatives/sms

Johnson, W. B., & Avers, K. (2012). Return on investment tool for assessing safety interventions. Federal Aviation Administration. https://www.faa.gov/sites/faa.gov/files/about/initiatives/maintenance_hf/fatigue/2012-10_return_on_investment_examples.pdf

Stroeve, S., Smeltink, J., & Kirwan, B. (2022). Assessing and advancing safety management in aviation. Safety, 8(2), Article 20. https://doi.org/10.3390/safety8020020

Too Tired to Fly

 

I used to think fatigue just meant needing more coffee. Then I read the aeromedical chapter for this class and realized it's way worse than yawning through a lecture. The FAA handbook says fatigue can seriously mess with your ability to focus and perform (Federal Aviation Administration, 2016). What stuck with me is how sneaky it is. You dont feel dangerous. You feel normal, just slower.

Fatigue isn’t just lack of sleep. Sure, all-nighters are bad. But it also builds up from stress, long shifts, dehydration, hot flight lines. Symptoms creep in slow. Reaction time drops. You miss details. Decision-making gets sloppy. The handbook mentions you start accepting risks you normally wouldnt because thinking through alternatives feels like too much work (Federal Aviation Administration, 2016).

Heres the scary part. Fatigue hits experienced mechanics and pilots just as hard as new ones. Maybe worse, because veterans trust their skills to carry them. But skills don’t help when your brain cant process info right. The FAA says heavy fatigue is more debilitating than three alcoholic drinks (Federal Aviation Administration, 2016). Nobody would work on a plane after three drinks. But people show up fatigued all the time.

After fourteen years on the flight line I get it. Sometimes you’re on hour ten of a twelve-hour shift and the jet still needs fixing. Thats when mistakes happen. You torque a bolt wrong. Skip a step. Let someone else sign off on something you didn’t fully check. Fatigue turns good techs into risky ones and nobody notices until its too late.

The Dirty Dozen lists fatigue as a main contributor to human error (FAA, n.d.). I’ve seen guys push through because the mission matters, because admitting you’re tired feels like letting the team down. But thats exactly when stuff breaks.

For me this means actually checking how I feel before work. Not just grabbing an energy drink and pushing through. Because the alternative is finding out I was too tired when something goes wrong.

References

Federal Aviation Administration. (2016). Pilot's handbook of aeronautical knowledge (2023): FAA-H-8083-25B. Aviation Supplies & Academics, Incorporated.

FAA. (n.d.). Dirty Dozen [Knowledge check module]. Aviation Maintenance Technician General Handbook.

When Everyone Knows Something and No One Knows Enough

I read a lot of accident reports in my job but the final report on the LATAM A320 collision in Lima really stuck with me. It shows how fast things go wrong when departments just stop talking to each other.

The crash happened when an airport fire truck drove onto the active runway while the plane was taking off. No clearance, nothing. Two firefighters died. What bugs me isn't just the crash itself. It's all the little organizational failures that made it possible.

The investigation showed the airport authority, emergency services, and air traffic control never actually met up to plan this response time exercise. Controllers didn't even know about new taxiways. The emergency crews thought their exercise clearance meant they could use the runway too. Nobody used proper radio phraseology. And get this, the tower found out about the exercise like ten minutes before it started. Everyone knew something but nobody knew enough. That breakdown is what let a runway incursion happen.

From where I sit in safety management, this crash is a wake up call. Safety culture isn't about being the smartest person in your department. It's about actually communicating with the other departments. Operations, emergency response, the tower, everyone needs to know what everyone else is doing. When one group changes something or starts a drill without telling the others, the whole system loses track of what's happening. That's why these safety publications actually matter. They give us real stories we can use to check ourselves. Are we really sharing information like we think we are?

If I could get my organization to remember one thing from this report, it's that sharing information isn't optional. It's basically the whole thing. Using this publication in our meetings helps show that we're all part of the same safety net. And that net only works if every department stays connected.

AirlineRatings. (n.d.). LATAM A320 collision with truck. https://www.airlineratings.com/articles/latam-a320-collision-with-truck