Skip to content
FRSign inBook a walkthrough
Regulation guideEASA and international

EASA Part-145 SMS Requirements: What an MRO Must Have in Place

Since the transition ended on 2 December 2024, every EASA Part-145 approved maintenance organisation must operate a safety management system as a standing condition of its approval. This guide covers what the mandate means inside a maintenance environment: maintenance-error hazards, occurrence reporting under EU 376/2014, human factors, and the interfaces with the operators and Part-CAMO organizations you serve. It also covers the retrofit reality of folding SMS into the quality system you already run, rather than standing up a second one.
Mounir OuafiFounder and CEO of eAvioraPublished 11 min read

01What Part-145 now requires

EASA does not publish a single standalone SMS regulation. Instead it embeds management-system requirements inside the implementing rules for each part of the industry. Air operators carry them through ORO.GEN.200; the maintenance-organization rules carry the equivalent obligation for Part-145. The headline for maintenance is simple: after the transition period ended on 2 December 2024, every approved Part-145 organisation must have a safety management system in place. There is no size threshold that exempts a small shop, and there is no grace for treating it as a plan on paper.

Underneath the rule text, the framework is ICAO Annex 19. That gives you the four components every aviation SMS shares (safety policy, safety risk management, safety assurance and safety promotion) and the twelve elements that sit inside them. If your organization also holds a Part-CAMO approval, you were already carrying management-system requirements, so in many groups Part-145 SMS is an extension of a system that already exists rather than a brand-new build. What changed on 2 December 2024 is that the maintenance approval now stands on the same footing as the rest: the safety management system is a condition of the approval, and your competent authority oversees it as part of continued approval.

02SMS inside a maintenance organization

An SMS designed around flight operations does not transfer cleanly to a hangar. The hazard picture in a maintenance organization is its own: incomplete or incorrectly performed tasks, incorrect installation of a part, tooling or foreign objects left inside a structure, a certification sign-off recorded before the task is actually finished, wrong or contaminated parts, and the slow drift of deferred defects. These are maintenance-error hazards, and they are what a Part-145 SMS exists to manage.

Human factors is not an optional module here, it is the core. Shift handovers, time pressure before a delivery, fatigue on a night shift, and documentation errors are the recurring contributors behind maintenance error, and safety risk management has to treat them as live hazards rather than annual training content. The mechanics of managing them are the same as anywhere in aviation: identify the hazard, assess it on a risk matrix, put preventive and recovery barriers in place, and monitor whether those barriers hold. A bow-tie model makes a maintenance-error hazard legible, with the threats on the left, the top event in the centre, the consequences on the right, and the barriers that are supposed to stop each path.

This is also where a maintenance organization feels the cost of a blank tool most sharply. Building a credible maintenance hazard library (the bow-ties, the barriers, the scenarios and the indicators) from an empty screen is months of work before any risk is actually being managed. A library that ships ready gives you a starting point to adapt rather than invent.

03Occurrence reporting under EU 376/2014

Occurrence reporting is where the Part-145 SMS meets a hard legal obligation. EU Regulation 376/2014 makes occurrence reporting mandatory across European aviation, and a maintenance organization is squarely inside it. A person reports within 72 hours of becoming aware of an occurrence, and the organization transfers its reports onward to the national competent authority.

The regulation is specific about format, because the data has to be poolable across Europe. Reporting databases are ECCAIRS-compatible and use the ADREP taxonomy, the E5X format is the zipped XML used to transfer reports, and ECCAIRS 2 is the current European platform. Article 16 provides the just-culture protections that shield the person who reports, which is the single most important condition for keeping the reports coming.

For the SMS this creates a clear set of moving parts: an intake channel a technician can actually use in a couple of minutes, a triage and classification step that decides reportability and severity, and a transfer workflow that produces the report in a form the authority can ingest. It also creates a confidentiality obligation, because a reporting culture collapses the first time a report is used against the reporter. The EU 376/2014 reporting guide and ECCAIRS 2 and E5X articles go deeper on the mechanics; the closed just-culture loop covers the protection side.

04The CAMO and operator interfaces

A Part-145 organisation never operates alone. It sits between the operator that flies the aircraft and the Part-CAMO that manages continuing airworthiness, and often it subcontracts specialist work to other approved organizations. Hazards and occurrences cross those boundaries constantly. A recurring defect the maintenance organization keeps seeing is airworthiness data the CAMO needs; a maintenance error can surface later as an operational event the operator has to report; a corrective action can only work if the organization that owns the affected process actually carries it out.

This is why the SMS rules put weight on interfaces. The management system has to define who owns which hazard, how occurrence and reliability data flows between the maintenance organization, the CAMO and the operator, and how a corrective action that touches more than one organization is tracked all the way to closure. When those interfaces live in email threads and re-keyed spreadsheets, the hand-offs are where risk goes to disappear.

On a single operational graph the interface is a link rather than a re-keyed message. An occurrence, its investigation, the corrective action it generates, the procedure it changes and the safety indicator it moves are connected records, so when a hazard crosses from maintenance into continuing airworthiness, the receiving side sees the same record with its full history rather than a summary someone retyped.

05The retrofit reality and one system

Almost every Part-145 organisation was already running a compliance-monitoring function long before SMS became mandatory: scheduled audits, findings, and corrective actions, the quality system the approval always required. The retrofit reality of the 2 December 2024 deadline is that SMS is being added on top of that, and the tempting mistake is to stand up a second, parallel system: a safety process that does not talk to the quality process it sits beside.

EASA points the other way. An integrated management system is explicitly encouraged: one system that satisfies both the compliance-monitoring obligation and the safety-management obligation, sharing its audits, findings, risk assessments and corrective actions. The practical test is whether a finding from a quality audit and a hazard from a safety report feed the same corrective-action process and move the same risk picture. If they do, you have one system. If the safety side is a binder assembled for the inspection while the real work happens in the quality process, a regulator can tell, and so can your own managers.

When you are ready to see what that looks like in software for a maintenance organization specifically, the SMS software for MRO and Part-145 guide is the criteria-led walkthrough.

Questions

The transition period ended on 2 December 2024. From that date, every EASA Part-145 approved maintenance organisation must have a safety management system implemented, and it is a standing condition of holding the approval rather than a future milestone. The requirement is not a bolt-on certificate: it means safety policy, safety risk management, safety assurance and safety promotion are actually operating in the organization and can be shown to work. Part-CAMO organizations already carried management-system requirements before this, so many groups that hold both approvals were extending an existing system rather than starting from nothing. If your organization still runs SMS as a binder produced for the audit, that is the gap regulators are now looking for.

Mounir OuafiFounder and CEO of eAviora, the aviation safety intelligence platform.

Related reading

See a hangar occurrence go from the report to the E5X file.

Book a walkthrough on your own operation, or keep reading in all the insights.