What is the purpose of the risk register example provided in GM4 to ORA.GEN.200(a)(3)?

The risk register example is provided as a means for the ATO to record the results of the assessment of the potential adverse consequences or outcome of each hazard.

Which EASA regulation and decision is associated with the guidance on the management system risk register?

The guidance is associated with GM4 ORA.GEN.200(a)(3) Management system, under ED Decision 2013/008/R.

What columns are included in the risk register example for recording pre-mitigation and post-mitigation risk?

The risk register example includes columns for Hazard (No, Description), Incident Sequence Description, Existing Controls, Outcome (Pre-Mitigation) with Severity, Likelihood, and Risk, Additional Mitigation required, Outcome (Post-Mitigation) with Severity, Likelihood, and Risk, Actions and Owners, and Monitoring and Review Requirements.

In the risk register example, what is recorded under 'Outcome (Pre-Mitigation)'?

Under 'Outcome (Pre-Mitigation)', the risk register records the severity, likelihood, and risk of the hazard before additional mitigation is applied.

What does the risk register example require to be documented after additional mitigation is identified?

After additional mitigation is identified, the risk register requires documentation of the post-mitigation outcome, including severity, likelihood, and risk, as well as the actions and owners and monitoring and review requirements.

GM4 ORA.GEN.200(a)(3) Management system

Navigate / EASA

Ask question Discover more Add to collection

GM4 ORA.GEN.200(a)(3) Management system

ED Decision 2013/008/R

SAFETY RISK ASSESSMENT – RISK REGISTER

The results of the assessment of the potential adverse consequences or outcome of each hazard may be recorded by the ATO in a risk register, an example of which is provided below.

Hazard		Incident Sequence Description	Existing Controls	Outcome (Pre-Mitigation)			Additional Mitigation required	Outcome (Post-Mitigation)			Actions and Owners	Monitoring and Review Requirements
No	Description	Incident Sequence Description	Existing Controls	Severity	Likelihood	Risk	Additional Mitigation required	Severity	Likelihood	Risk	Actions and Owners	Monitoring and Review Requirements

Details

Source-Title: GM4 ORA.GEN.200(a)(3) Management system View latest amendments

Erulesid: ERULES-1963177438-10998 Compare versions

Domain: Aircrew

Applicabilitydate: 23 April, 2013

Entryintoforcedate: 23 April, 2013

Regulatorysource: ED Decision 2013/008/R Navigate

Regulatorysubject: Part-ORA

Typeofcontent: GM to IR (Guidance material to implementing rule)

Parentir: ORA.GEN.200 Management system

Origin: EASA

Category: EAR