State Safety Programme (SSP)

A State Safety Programme (SSP) is the national-level counterpart to the safety-management system an airline or training organization runs. Where an operator's Safety Management System (SMS) manages the safety of one organization, an SSP is the integrated set of regulations and activities through which a State manages the safety of its entire civil aviation system. The requirement is set out in ICAO Annex 19 (Safety Management), which consolidated the safety-management provisions that had previously been scattered across several Annexes and made the SSP a formal Standard.

An SSP is structured around four components that deliberately mirror the four pillars of an operator SMS. The first is State safety policy, objectives and resources: the legislative framework, the assignment of responsibilities across the authority and other State agencies, and the enforcement policy — including the just-culture principles that determine how occurrence reports are treated. The second is State safety risk management: the process by which the State sets the safety requirements its operators must meet and agrees, where appropriate, on how individual operators' SMS performance is accepted. The third is State safety assurance: the surveillance, oversight, and data-driven monitoring through which the State confirms that its operators and its own system are performing. The fourth is State safety promotion: the training, communication, and dissemination of safety information that build competence and a positive safety culture across the national industry.

A central concept within the SSP is the Acceptable Level of Safety Performance (ALoSP). Annex 19 requires each State to establish, through its SSP, an acceptable level of safety performance to be achieved — expressed through safety performance indicators and targets rather than as a single abstract number. Modern practice has moved away from treating ALoSP as one fixed figure and toward managing a set of indicators and targets that are monitored continuously, so that the State can see whether its safety performance is improving, holding, or degrading.

The relationship between the SSP and an operator's SMS is the point most relevant to the industry. An operator SMS does not float free; it operates inside, and is accepted by, the State's SSP. The State, through its safety risk management and safety assurance components, sets expectations for operator SMS, accepts each operator's safety performance, and monitors it over time. In this sense the SSP is the container and the operator SMS is the contents — the two are designed to interlock.

The SSP also connects to the oversight machinery above it. USOAP audits, among other things, whether a State has established and is implementing its SSP effectively, and Annex 19's SSP requirements are part of what a State is measured against. In the two largest regulatory systems, the SSP concept is implemented through national frameworks — the FAA operates a US SSP, and in Europe the responsibilities are shared between EASA and the Member State authorities — but in both cases the underlying architecture traces back to the same Annex 19 Standard.

For an ATO or AOC operator, the SSP explains why a regulator's expectations of the organization's own SMS keep rising. When a State sharpens its safety performance indicators or tightens its safety assurance activities under its SSP, that pressure flows straight down to the operators it oversees, because the State demonstrates its own performance partly through the aggregated performance of the operators inside its system. An organization that understands it is one data point in the State's SSP can anticipate why its authority asks for particular indicators, reports, and evidence rather than experiencing each request as arbitrary.

The nesting relationship also clarifies what an operator's SMS is really for. A school that treats its hazard register, its safety performance indicators, and its safety assurance activities as boxes to tick misses the point: those outputs are exactly what the State's SSP consumes when it accepts the operator's safety performance and reports upward. Running a genuine, data-driven SMS is therefore not only good practice in itself — it is the mechanism by which the organization contributes to, and stays in good standing within, the national programme that authorizes it to operate.

Aviatize's Safety Management module gives a school or operator the working SMS that its State's SSP expects to find underneath it: hazard reporting from any device, a hazard register with risk scoring and mitigation tracking, and safety performance indicators that make the organization's safety trend visible rather than anecdotal. When the authority — acting through its safety assurance component — asks the operator to demonstrate performance, the data is already structured to answer.

By keeping safety data alongside operational data — flight records, cancellations, squawks, and audit findings — the KPI Reporting & Dashboards module lets safety managers show the indicators and targets that feed the State's monitoring, turning the operator's contribution to the national programme into a reporting task rather than a reconstruction exercise.