Category: Regulation

Part 2

Make “challenging” better. It’s generally better to have more than one set of eyes on an issue.

The classical challenge is to perform an audit. To take a sample of the work being performed and check that its everything that it’s said to be. This can be done at any stage: design, development, test, production, and in-service. Unfortunately, audits can get bogged down in process, procedures, customs, and practice that get so heavy as to distract from the essences of the task.

There’s a focus on the tangible aspects of work too. How many reports? How many corrective actions? Show me the measurements. Nevertheless, well focused auditing is a powerful tool.

It would be wise not to discount the intangible benefits of an audit. Such activities provide a chance to view the more intangible aspects of work. Here’s a few anecdotes.

Often when being taken for an official guided tour around a design or production facility there time to look beyond what the hosts want you to see. I often found a moment to look at notice boards around a factory, or office and they gave a hint as to the culture in that organisation. Cartoons and jokes of good humour led me to put a “normal” tick in the box. But if they strayed into harsh lampooning of the management or the way of working then there was something to note.

Siting in a manager’s office being briefed as to the timetable for an audit it’s as well to take in the whole scene. All those certificates displayed on the wall. Were they pertinent? Were they there to show off? Or were they showing genuine pride in the achievements of the organisation?

Timetables for an audit are necessary but can be a menace if every second is filled. But an auditor should never be intimidated by a timetable. On occasion, I’ve walked past a pile of records only to turn back and say – and what about this one? Then being told we must hurry on. To which my reaction was to dig in and follow the trail.

It’s true that the environment has changed. Digitisation has made the random selection of a sample more difficult. Digital records lend themselves to more pre-prepared situations.

Mealtimes can be a revelation on organisational culture too. This doesn’t happen anymore, I’m sure. The factory canteen that serves alcohol is truly a thing of the past. However, an auditor being taken out for lunch is still commonplace. It’s possible to get moralistic about such invitations only to miss out on getting a sense of those intangibles that might help understanding.

Additionally, I will warn that there’s the small danger of vexatious challenge. It’s a rarity but obsessions can follow even the most capable of people around. There’s a risk too that focusing on one pet subject can mean gapping great holes are missed. Each subject needs to be taken proportional to its potential impact.

Reading the commentary, deep and wide, that has flowed from the saga of the certification and introduction to service of the Boeing 737 MAX there’s palpable frustration. A large volume of analysis and evidence is now in the public domain. It has taken a long time and the persistence of many good people to bring out the results of investigation to the fore.  Frustration stems from knowing that the factors involved in the MAX saga are not new or unique. They have been seen far too often in fatal accidents and serious incidents right across the globe.

One common reaction is to place all the blame on the corrupting effect of large amounts of money. The line “follow the money” became common usage as a result of the 1976 movie “All The President’s Men[1]” despite the theory that it came from elsewhere.

“Follow the money” is good advice for investigators whether they be journalists, air accident investigators or police detectives. It’s certainly one of the known motivators for people to circumvent or disregard rules and regulations.

I could go on to talk about corporate liability[2]. There’s often a distinct lack of capability or inclination to hold large corporations, and the individuals running them liable for gross negligence and unethical behaviours. Another problem with this is that this is the button to press after the event. Yes, strong corporate liability laws rigorously applied can have a deterrent effect. However, the calculation made by those people at the source of the problem is often that of slim likelihood of failure or getting caught or, as with banks during the financial crisis, being too big to fail.

Although all the lessons learned from the analysis of organisational accidents is a good route to prevention of future accidents, that just one part of the puzzle.

Another common reaction is to reach for the human factors’ textbooks. There’s absolutely no doubt that human action is at the root of the events discussed. It takes people, and groups of people to choose to do the wrong thing knowing of the risks they take. Indefensible actions done with the awareness of an organisation are more than just process or procedural failure.

I started writing with the assumption that organisational accidents are preventable and must be prevented. This is to say that zero accidents are achievable. Yet, organisational accidents keep happening and prevention keeps failing. All be it, relative to the volume of global activity, a rare occurrence in civil aviation.

Maybe it’s better to accept that the motivations of a minority of people are to act unethically for personal gain and to take unacceptable risks. The larger problem is the failure of a greater number of people to act when they become aware of that behaviour.

In the cockpit pilots are taught to challenge bad decisions. Maybe we need to teach people how to challenge effectively.

[1] The movie takes protagonists Bob Woodward and Carl Bernstein through their quest to figure out the suspicious acts around US President Richrd Nixon.

[2] https://www.cps.gov.uk/legal-guidance/corporate-prosecutions

The latest innovations in aircraft design are, without question, highly integrated systems. We have departed from the days when every aircraft system was a box. An autopilot, a display computer, a power controller may all sit in one cabinet of equipment. Each one interdependent upon the other.

The other day, I saw advertised as an antique a British P8 aircraft compass. Maybe, 80 years old, it was claimed to be still working. This bit of kit was fitted to the Spitfire, Hawker Hurricane and Mosquito. Truly, a discreet equipment. One basic function and independent of all other aircraft systems except cockpit lighting. Afterall, a compass isn’t much use if you cant see it.

One reflection of mine from times past is the real difficulty of getting people to take an aircraft level view. Some might say this is aerospace design history. It certainly was a major struggle in the mid-1990s. It was a message that was not always well received.

Without mentioning any names, I’d roll up at an aircraft manufacture and be confronted with a hanger sized office divided up into cubicles. Sound absorbing partition walls of shoulder hight stretching far into the distance. This is where the Scott Adams[1] got the idea for the Dilbert cartoons.

In one corner of the engineering building would be a venerable grey-haired gentleman who had spent his entire life working on toilet flush motors. At another corner would be a gaggle of whizz kids developing software specifications for the latest computing hardware.

Everything was the same placid light green with only a few signs to give identity to groups of people working together. Segregation and segmentation were a part of the process. Each functional group developed their skills to the highest degree in their chosen specialisation.

My role in all this was to sit in a rectangular meeting room receiving briefings from each technical team. The certification task had been divided up and everyone was doing their part. Certification plans for an autopilot, a display computer or a power controller were all competently presented. Preliminary safety assessments were dutifully described.

After a while it became all to clear to me that everyone was dedicated to their assignment but that communication between different teams was sketchy to say the least. So, questions like, where did you get that number from, when talking about a failure probability number taken from someone else’s analysis wasn’t always convincingly answered. As a result, I got to hammer on about the need to take an aircraft level view to the point of great irritation. It’s not that people didn’t want to hear the message. It was more that the means to look at interdependencies between aircraft systems was fragile and underdeveloped. We changed and progressively the challenge of integration was met.

Today, I sit and wonder if the new entrants in the aerospace world, rapidly putting together advanced new forms of air mobility, have taken on-board the lessons we learned in the 1990s. It’s not as easy to learn the above lessons unless the reason why is abundantly clear.

[1] https://www.scottadamssays.com/