SEO Title
NTSB's Graham: Safety management System Scalability a Must for Smaller Aircraft Operators
Subtitle
NTSB member Michael Graham stressed the importance that all small Part 135 operators adopt SMS, but said the program must be scalable.
Subject Area
Teaser Text
NTSB member Michael Graham stressed the importance that all small Part 135 operators adopt SMS, but said the program must be scalable.
Content Body

National Transportation Safety Board (NTSB) member Michael Graham stressed his belief that there should be no exceptions for size from the FAA’s safety management system (SMS) rulemaking but did say the final regulation must be scalable for small operators. During the Air Charter Safety Foundation’s Safety Symposium on Wednesday in Daytona Beach, Florida, Graham noted that the NTSB has been pushing for the FAA to mandate SMS for Part 135 since 2016, following the Hawker 700A crash in Akron, Ohio.

“The voluntary days are over with. We didn't hit enough people,” he said, adding that about 10 to 12 percent of Part 135 operators have adopted SMS. “We’re talking out of 2,000 operators. You can do the math and that's not many. The time is over. The safety benefits are there. We all need to get there.”

He said the NTSB was pleased that the FAA had released the notice of proposed rulemaking to extend SMS requirements to Part 135 and air-tour operators. While some have asked about alternatives for the smallest operators, Graham said the answer should be: “Nope. You don’t have an SMS if you don’t have all four components [safety policy, risk management, assurance, and promotion].”

However, he has been pushing for guidance and scalability. “It has to be scalable. If it’s not, it’s never going to work.” Graham pointed to an NTSB recommendation that the FAA provide guidance on specific examples, methods, and techniques for small operators.

Thus far, the FAA’s draft guidance has not done that, he noted. “I read it. There’s nothing in there.” He said it only repeats language that it should be scalable. “It’s just like everything else: ‘scalable.’ Good luck. Good to go.”

Graham also expressed concern over the associated oversight. NTSB has asked the agency to require SMS and then verify the effectiveness. “We already see issues with oversight in a lot of our accidents with [Part] 135s. Now add SMS to it.”

Graham opened his discussion at ACSF talking about the “elephant in the room. Let’s face it. We’re all wondering what is going on with aviation right now.”

He pointed to the meltdown of the notam system, turbulence incidents, and the half-dozen near collisions that they’ve counted so far this year—but there are a couple of others the Safety Board is looking at right now, but still categorizing them.

The average for Category “A” and “B” close calls is about 17 to 18 per year. “Now we’ve got six of those in two months. That’s not good.”

Frustrating to the NTSB is the number of cockpit voice recording readouts it has been able to get out of these six events: “zero,” Graham said, noting that most get overwritten every two hours. NTSB has called for a 25-hour time on them, he stated. “We've got the technology out there. This is ridiculous. We’ve got to have this.”

Adding to this, he said, NTSB has received pushback on its efforts to interview crews afterward. As for reasons behind these incidents, he said “I don’t think it’s going to be one smoking gun. We’re investigating.”

He noted air traffic control procedures are among the areas being reviewed, but emphasized the importance of data and SMS. He pointed to the strong safety record of the airlines. “They earned it. They worked really hard, but I’m concerned,” Graham said. “Are we putting on the autopilot here? Are we just letting things run? Are we putting that SMS up on the shelf now? Because we all know you have to work continuously and manage risk and safety assurance. If you're not, you don't know when the next big one's going to happen.”

Expert Opinion
False
Ads Enabled
True
Used in Print
False
Writer(s) - Credited
Publication Date (intermediate)
AIN Publication Date
----------------------------