Procedures 101

A government and industry workshop tries to untangle the web of technical information and regulations and make it easier to follow procedures.


We hear it every day: “They did not follow procedures.”

As a result, an aircraft is damaged ... someone is injured ... the baggage is lost ... the flight is delayed. The outcome is varied and infinite, but the overriding cause is that a procedure was not followed. The challenge is as old as aviation and the solutions seem to be elusive. Or are they?

A panel of aviation industry and government officials recently spent two days trying to get their hands and heads around the issue of following procedures.

The invited group was composed of OEMs (Boeing, Airbus, Gulfstream, and General Electric), airline and independent maintenance organizations, FAA inspectors, CEOs and organized labor leaders. All agreed that we have a problem.

Today, safety management approaches these problems not by merely looking for who or what to blame. Instead, proper safety management identifies and corrects the hazards that contributed to the risk.

The workshop participants decided that the word “documentation” is too limiting. The focus must be on “information.” It can range from traditional written text to graphics to animations and more.

Carol Daniels, CEO of Aircraft Technical Publishers and chairman of the General Aviation Manufacturers Association, emphasized that “information must be delivered in a usable format, at the right time, on the appropriate device.”

According to Daniels: “Users should specify their information requirements. What works for an airline on the Atlanta ramp may not be suitable for a helicopter operator in Alaska. If we do our job right, mechanics are more likely to access the information.”

John Goglia, former NTSB member and long-time airline mechanic, talked about the culture that heralds safety as “No. 1,” but then drives decisions, actions and rewards with on-time performance.

According to Goglia: “When a crew is rewarded for meeting the schedule rather than for reading the instructions, the technical information availability and access lose priority.”

Many of the FAA inspectors lamented the fact that they are forced to take administrative action against individual mechanics who fail to use the technical documentation. These inspectors were once mechanics themselves so they know that the individual is faced with inadequate documentation systems in a “hurry-up” culture. The mechanics are often victims of documentation, corporate culture, and uncompromising FAA regulations.

The workshop broke into five working groups that focused on quantifying the challenges and possible solutions. Here’s a quick look at the top challenges and solutions from each of the five groups:.

Human issues

The group identified a lack of involvement by mechanics to create and validate written procedures. The members suggested the OEMs and the airline engineers must do more field-testing of the written procedures. The process must be streamlined to modify poor procedures identified by on-the-job users. Either this must improve or mechanics will continue to bypass or ignore procedures.

Information quality

This group said the greatest challenge was the government’s inconsistency and nonstandardized requirements. The members called for new FARs and internal training that is matched to current technologies and user requirements. Government acknowledged that they are traditionally understaffed in the offices that oversee technical documentation.

Industry responsibility

While industry responsibility and measurement are two separate groups, the members were like-minded in their conclusion. According to both, there is not a sufficient business case to improve technical information. In the trade-offs among production, quality, and compliance, the technical information is seldom top priority. The solution is to provide additional detailed error data when “failure to follow instructions” is the cause of a loss. More information related to root cause analysis is necessary.

Regulatory

This content continues onto the next page...

We Recommend