Safety Performance Indicator (SPI)

Safety Performance Indicators are the measurable layer of a Safety Management System. ICAO Annex 19 (Safety Management) and the supporting Doc 9859 (Safety Management Manual) require every State and every approved aviation organization to define SPIs that quantify safety performance, supported by SPTs that define acceptable levels and trigger management action when breached.

SPIs come in two layered categories. High-consequence / low-probability indicators (sometimes called "reactive" or "lagging") count actual adverse events: accidents, serious incidents, runway excursions, hard landings, controlled-flight-into-terrain near-misses, MOR-reportable occurrences. They are essential for regulatory compliance and historical analysis but, by their nature, signal problems after they have already occurred. Low-consequence / high-probability indicators (sometimes called "proactive" or "leading") count precursor events that statistically correlate with future accidents: unstabilized approaches, altitude busts, ground-proximity warnings, weather-related diversions, fatigue reports, training discrepancies. The proactive indicators give the organization time to act before the lagging ones move.

A mature SPI framework includes both categories, defined per organizational risk profile. A flight school's SPIs typically include training-quality indicators (first-attempt practical test pass rate, stage-check failure rate, instructor standardization variance), operational-safety indicators (squawk rate per flight hour, MEL deferral rate, AD compliance lead-time margin), and safety-culture indicators (number of voluntary safety reports per pilot per quarter, time from report to closure). Each SPI has an SPT — a numerical target — and an alert level at which management investigation is triggered.

Under EASA's Part-ORO ORO.GEN.200 and the SMS-related amendments to Part-ORA and Part-CAO, the operator's SMS Manual must document the SPIs and SPTs the organization has adopted, the data sources feeding each SPI, the review frequency, and the management action sequence triggered by SPT breach. The competent authority audits this documentation against actual practice — an SMS Manual that lists SPIs the organization is not measuring is a finding.

The FAA's SMS framework under Part 5 (for Part 121 operators) and the parallel Voluntary SMS Program for Part 91/135/141 operators imposes a similar SPI/SPT discipline, with the FAA Safety Management Implementation Plan defining acceptable performance levels. The FAA's approach emphasizes data-driven risk management with structured Safety Risk Management (SRM) and Safety Assurance (SA) processes, both of which depend on SPI data to function.

The recurring failure mode of SPI implementation is non-measurement. An organization documents an SPI in its SMS Manual but the data source is not actually feeding any reporting. The lagging indicators are reasonably easy to track because reportable events are externally visible — accidents, regulator-reportable incidents, Hard MOR criteria. The leading indicators are where the discipline collapses: "unstabilized approach rate" requires consistent data capture from every approach across the fleet, and that data either exists in the FDM/FOQA system or it doesn't. Operators with paper-based or partially-digital operations typically cannot supply credible leading-indicator data.

The consequence under audit is significant. EASA's SMS audit posture has tightened materially since 2020, and competent authorities are increasingly unwilling to accept SPI documentation that has no data behind it. Operators that documented SPIs they could not actually measure now face findings that require either acquiring the data infrastructure or redrafting SPIs to match what the organization can actually measure — and the regulator generally prefers the former.

Aviatize's safety management module is built around configurable SPIs as first-class data objects. Each SPI is defined with its data source (which platform module feeds it — training management for first-attempt pass rate, maintenance execution for squawk rate, safety management for voluntary report metrics), its calculation rule, its SPT target, its alert level, and its review cycle. The platform calculates SPI values automatically on the configured cadence and produces the dashboard the safety manager and accountable manager need for the SMS review meeting.

For SPT breach, the platform triggers the documented management-action sequence: notification to the safety manager, an investigation task with target closure date, and an entry in the SMS event log that the regulator audit will sample. The audit trail — when did the breach occur, when was it noticed, when was action taken, when was the SPI returned within target — is captured automatically rather than reconstructed. For combined operations, SPIs can roll up across the ATO and AOC functions or be reported separately, depending on the organization's SMS Manual structure.