## 1 Purpose 

This guidance outlines a process consistent with the Air Traffic Organization (ATO) Safety Management System (SMS) for preparing and implementing Program Safety Plans (PSPs) for systems that may be fielded in the National Airspace System (NAS) and that are acquired under the  Federal Aviation Administration (FAA) Acquisition Management System (AMS). 

## 2 Applicable Policy and Related Documents 

This guidance does not constitute a change to any requirements contained in FAA orders. It reflects updates to the ATO SMS Manual, which provides guidance on fulfilling requirements set forth in the current version of FAA Order JO 1000.37, Air Traffic Organization Safety Management System . This guidance also supplements the AMS. 

## 3 Background 

A PSP is the government’s integrated management plan for conducting the System Safety Program (SSP) for a particular project or program. By executing this plan, the government ensures compliance with the provisions of the SMS Manual, the Safety Risk Management Guidance for System Acquisitions (SRMGSA), and the AMS. Use of a PSP also ensures that an acceptable level of safety consistent with mission requirements is designed into the system. 

## Guidance for Preparing and Implementing Program Safety Plans 

The Program Office (PO) $^{1}$ (using a Program Safety Team, as appropriate) must develop and tailor a PSP that details the specific safety needs and Safety Risk Management (SRM) requirements of the program and update the PSP as the program matures and information changes. This PSP forms the basis of the prime contractor’s corresponding System Safety Program Plan (SSPP), which is typically required as a contract deliverable. The prime contractor’s SSPP, when approved by the government, binds the contractor to an SSP that should be consistent with the government’s PSP. 

The PSP also stands as the PO’s agreement with Safety and Technical Training (AJI) (or more specifically, the ATO Chief Safety Engineer) to conduct a safety program that is consistent and compliant with the ATO SMS. It defines the roles and responsibilities of the PO / Safety Team members as they implement the SSP. As such, the PSP must describe: 

• The safety program that applies to each project, sub-system, and interface to support program activities and SMS/SRM requirements; 

• The SRM responsibilities of the PO / Safety Team; 

• Planned SRM efforts; and 

• A summary of the development assurance program (either as proposed or as documented in the program’s Plan for Software Aspects of Approval (PSAA)). 

## 4 System Safety Considerations 

System safety must be planned as an integrated and comprehensive safety engineering effort that is sequential and continual. It is essential that the developer’s SSPP as required by the Statement of Work in the developer’s contract aligns and is consistent with the government’s 

