Corrective action tracking for aviation: what the register must show and how to close items

The corrective action register is the document that proves an aviation safety program is functioning rather than just existing. It is what separates an organization that identifies hazards from one that actually does something about them.

An FSDO examiner or insurance underwriter reviewing a Part 135 SMS does not expect a clean record — they expect a complete one. An organization with 20 corrective actions opened and 19 closed is demonstrating a functioning safety assurance process. An organization with zero corrective actions is either the safest operation in aviation history or one that is not looking.

What goes in the register

Every corrective action entered in the register should capture:

• ID number. Sequential. CA-001, CA-002, etc. Makes referencing easy and prevents items from getting lost in a spreadsheet.
• Source. Where the finding came from — hazard report (with report ID), near-miss, incident investigation, audit finding, FSDO observation, internal review. Tracking source helps identify which channels are generating actionable findings.
• Date opened. The date the corrective action was created, not the date of the original event.
• Description of finding. What the hazard or deficiency is, stated specifically enough that someone unfamiliar with the incident can understand it without additional context. "Crew reported fatigue" is not sufficient. "Crew reported cumulative fatigue on day 4 of a 5-day rotation — duty periods averaged 12.5 hours across the week" is.
• Risk severity. The risk level of the finding — typically HIGH / MEDIUM / LOW — assessed at the time the CA is opened. High-severity items should have shorter closure timelines.
• Root cause. Not the symptom, but the underlying cause. "Crew was tired" is a symptom. "Scheduling practice allows accumulation of consecutive long duty days without a mandated break" is a root cause. Corrective actions aimed at symptoms recur; those aimed at root causes do not.
• Corrective action description. What specifically will be done to address the root cause. Named action, not a vague intention.
• Owner. The person responsible for implementing the corrective action. One person, not a committee.
• Due date. A specific date, not "ASAP" or "ongoing." Due dates create accountability; open-ended items drift.
• Status. OPEN / IN-PROGRESS / CLOSED. Updated as the item progresses.
• Date closed. The date the corrective action was verified complete.
• Closure notes. What was actually done, and evidence that it was done. "Scheduling policy updated to require a minimum 24-hour break after 3 consecutive duty days exceeding 10 hours — policy revision Rev 4.2 dated [date], distributed to all dispatch staff."

Closure rate — the metric that matters most

The closure rate is the percentage of corrective actions opened in a given period that have been closed within their due date. It is the single most important metric in the corrective action register.

A closure rate below 70% indicates a systemic problem: either items are being opened that cannot realistically be completed (unrealistic due dates, insufficient resources, wrong owners), or the organization is opening items as a documentation exercise without genuine intent to close them.

A closure rate of 90%+ indicates a functioning process. The remaining 10% of open items should be actively managed — not forgotten — with current status and revised due dates if the original timeline could not be met.

For insurance submission purposes, the closure rate is one of the items in a loss-control summary. An underwriter who sees a 95% closure rate over 12 months is seeing evidence of an organization that follows through. One who sees 40% is seeing evidence of a reporting theater.

Severity tiering and timelines

Corrective actions should have different response timelines based on risk severity:

A HIGH-severity item that is open at 60 days without a documented status update and a revised timeline is a finding in itself. If a high-severity item cannot be closed in 30 days, the register should reflect the reason and the interim mitigation in place while the permanent fix is being implemented.

Root cause analysis — why it matters

The most common corrective action failure mode is treating the symptom. A corrective action that says "retrain crew on duty time rules" in response to a duty time violation addresses what the crew did — not why the organization's process allowed it to happen. The crew probably knew the rules. The issue was that the scheduling process created conditions where the violation was likely.

The "5 Whys" technique is useful here. For a duty time finding:

1. Why did the crew exceed duty limits? Because they accepted a late add-on trip.
2. Why did they accept the trip? Because dispatch requested it and the crew felt pressure to say yes.
3. Why did they feel pressure? Because the dispatch process does not require a duty time check before requesting the trip from crew.
4. Why does dispatch not check duty time first? Because the scheduling tool does not show duty time status at the trip-request stage.
5. Why not? Because that feature was never configured.

Root cause: the scheduling process does not enforce a duty time gate before trip requests reach crew. Corrective action: configure the dispatch tool to show duty time status and require a check before issuing a crew request. That action addresses the root cause. Retraining the crew does not.

The register as an audit artifact

The corrective action register, exported as a PDF or spreadsheet, is one of the primary artifacts in an SMS audit and an insurance loss-control review. The reviewing party will look at:

• Volume — are findings being captured at a realistic rate for the size and complexity of the operation?
• Sources — are findings coming from multiple channels (hazard reports, audits, crew feedback) or only one?
• Closure rate — are items actually being resolved?
• Median time to close — how long does it actually take to implement a fix?
• Open high-severity items — is anything critical sitting unresolved?
• Recurrence — are the same findings appearing more than once? Recurrence is evidence that root causes are not being addressed.

Clearspar's pre-dispatch compliance record surfaces the corrective action metrics — total, closure rate, median days to close, overdue count — in the trailing-12-months loss-control summary. The numbers in that summary come directly from the register; they are not curated for presentation.