Some Truths About SMS

Don't shoot me, I'm just the messenger.


By Robert Baron

I have been reading a plethora of articles of late that have been presenting SMS in a candy-coated, cure-all solution to aviation’s problems. While I agree that an operational SMS can be an effective brain center for the safe operation of an aviation service provider I think we also need to frame the realities of what could be a bumpy ride en route to the SMS destination for many companies. What follows is a brief list of some SMS realities and challenges that you are likely to face as SMS slowly becomes a reality for your aviation organization.  

Size and scope

In these preliminary stages of SMS implementation in the United States there seems to be much ado concerning what a fully operational SMS should “look like.” The so-called Four Pillars of Safety, the framework of SMS, are based on standards and recommended practices that have been developed and time-tested in some of the more proactive aviation safety cultures (i.e., United Kingdom, Australia, and Canada). Regardless, there have been wide variations of opinions regarding the size and scope of an SMS program.

There appears to be much consternation among safety managers of both large and small companies as they try to ensure that their SMS is fitted properly to their operation. Large companies argue that an SMS will create the need for additional departments and human resources in order to manage the myriad of safety data that will need to be collected, analyzed, and acted upon. In turn, these companies may view SMS as an additional expenditure with difficulty selling the program to the CEO from an ROI perspective. On the other hand, small companies argue that most of the information available for SMS implementation is geared toward large operators and for the most part wholly inapplicable to a small flight department such as a one aircraft, two pilot Part 135 operation. In the case of the latter it’s easy to understand this concern. However, it should be kept in mind that the SMS framework that is applicable to the large operator is still applicable to the small operator. The major difference is that there will be fewer people involved in fewer positions related to the SMS. There will also be a much more compact risk management system and data collection/analysis process.  

We already have an SMS

I hear this all the time. Many companies claim they have an SMS by virtue of the fact that they have a flight operations manual, follow the regulations, provide training, etc. The logic makes sense and to a certain extent these companies do have a quasi-SMS. However, the difference between a quasi and a true SMS is that the latter, in addition to a few extra requirements, ties all of your safety components together to become your formal safety management system.

Interface Issues with the FAA

Have you ever experienced a situation where there was a difference of opinion between POIs, PMIs, PAIs, or even entire FSDOs regarding a safety or approval issue? An example would be your maintenance company moving from one FSDO jurisdiction to another. Your original FSDO had no problem with the way you conducted your Part 145 repair business yet the new FSDO finds many discrepancies in your paperwork and issues a temporary suspension of your certificate. Although this would raise a good fundamental question — was the old FSDO just too lax or is the new FSDO really sharp? — I’ll save that topic for another article.   

The point is, just like the example above, companies appear to be experiencing interface issues with the FAA regarding their SMS. Invariably there will be different interpretations of SMS requirements across PMIs. In fact, there can be significant amount of variance. This lack of standardization can be frustrating but it likely will not get better any time soon. Venting your anger at your PMI or FSDO will not help to implement your SMS any quicker. You should work closely with your PMI to fully understand his or her requirements and expectations and develop your SMS as such.   

This content continues onto the next page...

We Recommend