Skip to main content
A Corrective and Preventive Action (CPA) is a documented action taken to eliminate the cause of an existing deficiency (corrective) or to prevent a potential deficiency from occurring (preventive). CPAs are a core output of Safety Risk Management and Safety Assurance under 14 CFR Part 5. Every CPA follows a defined lifecycle from creation through verified closure.

CPA Types

TypeAPI ValueDescription
CorrectivecorrectiveAddresses an existing deficiency or nonconformity. Eliminates the root cause of a detected problem.
PreventivepreventivePrevents a potential deficiency from occurring. Addresses conditions that could lead to future problems.

CPA Statuses

StatusAPI ValueDescription
OpenopenCPA has been approved, assigned to an owner, and given a due date.
In Progressin_progressWork on the CPA is actively underway.
ImplementedimplementedThe action has been completed and awaits independent verification of effectiveness.
VerificationverificationThe action is being verified for effectiveness by someone other than the owner.
ClosedclosedThe CPA is formally closed. Record is immutable.

Status Lifecycle

Status Transition Rules

FromToPermitted RolesConditions
OpenIn ProgressCPA owner, safety manager, adminNone
In ProgressImplementedCPA owner, safety manager, adminCompletion evidence attached
ImplementedVerificationSafety manager, adminVerifier is not the CPA owner
VerificationClosedSafety manager, adminEffectiveness confirmed
VerificationIn ProgressSafety manager, adminVerification failure reason required

Priority Levels

PriorityAPI ValueDescriptionTarget Response TimeEscalation
CriticalcriticalImmediate safety risk requiring urgent action. Operations may need to be halted or modified.24 — 48 hoursAccountable executive notified immediately.
HighhighSignificant safety concern. Prompt action required to prevent escalation.1 — 2 weeksSafety manager notified daily until resolved.
MediummediumModerate safety concern. Action within normal operational timeframe.30 daysStandard overdue notifications.
LowlowMinor concern. Action at next convenient opportunity.90 daysStandard overdue notifications.

CPA Fields

FieldTypeRequiredDescription
codeStringAutoAuto-generated tracking code (e.g., CPA-2026-0015).
titleStringYesBrief description of the action.
descriptionTextYesDetailed description of what must be done.
typeEnumYescorrective or preventive.
priorityEnumYescritical, high, medium, or low.
ownerUser referenceYes (at Open)The person responsible for completing the action.
due_dateDateYes (at Open)Target completion date.
statusEnumAutoCurrent lifecycle status.
sourceEnumYesOrigin: investigation, risk_assessment, audit, or manual.
linked_reportReport referenceNoThe safety report that triggered this CPA.
linked_investigationInvestigation referenceNoThe investigation that recommended this CPA.
progress_notesArrayNoTimestamped notes documenting work progress.
evidenceArrayNoAttached files demonstrating implementation (documents, photos, records).
effectiveness_criteriaTextNoMeasurable criteria the verifier will use to confirm effectiveness.
verification_dateDateNoDate the CPA was verified as effective.
verified_byUser referenceNoThe person who verified effectiveness.
verification_notesTextNoNotes from the verification review.
created_atTimestampAutoRecord creation timestamp (UTC).
updated_atTimestampAutoLast modification timestamp (UTC).

Verification Process

Verification is an independent confirmation that a CPA has been effectively implemented and that the original deficiency or risk has been adequately addressed.
| Step | Component | Description | |:----:|-----------|-------------| | 1 | Completeness check | Confirmation that all planned actions were carried out as described. | | 2 | Evidence review | Review of attached evidence (documents, photos, training records, procedure revisions) demonstrating implementation. | | 3 | Effectiveness assessment | Evaluation of whether the action has eliminated or adequately mitigated the identified risk against the defined effectiveness criteria. | | 4 | Documentation | Recording of verification notes, date, and verifier identity in the CPA record. |
The verifier must be a different person from the CPA owner. The system enforces this constraint — the Verify action is unavailable to the assigned owner.
A failed verification returns the CPA to in_progress with notes documenting what additional work is required. The due date may be extended. The CPA owner is notified.

Overdue Tracking

CPAs that pass their due date without reaching implemented are flagged as overdue. The system generates notifications as follows:
RecipientNotification Trigger
CPA ownerDue date reached. Repeated at configurable intervals.
Safety managerDue date reached. Daily digest of all overdue CPAs.
Accountable executiveCritical-priority CPAs overdue by more than 48 hours.
Overdue CPAs appear on the safety compliance dashboard and are included in Safety Performance Indicator (SPI) calculations.

CPA Sources

SourceAPI ValueDescription
InvestigationinvestigationGenerated from an investigation’s recommended actions. Links to the investigation record.
Risk Assessmentrisk_assessmentGenerated when a risk assessment identifies the need for controls. Links to the risk assessment.
AuditauditGenerated from an internal safety audit finding. Links to the audit finding report.
ManualmanualCreated directly by the safety manager without a linked source record.

Regulatory Alignment

Part 5 SectionRequirementCPA Component
5.55Safety risk assessment and controlCPA as a risk control mechanism
5.73Safety performance assessmentVerification of CPA effectiveness
5.75Continuous improvementSystemic corrective and preventive actions
5.97SMS recordsCPA records retained as long as control remains relevant

Create a CPA

CPA creation and assignment.

Investigation Workflow

How investigations generate CPA recommendations.

Your First CPA

Tutorial walkthrough of the CPA lifecycle.

Risk Assessment Matrix

Risk assessment criteria that drive CPA creation.
Last modified on April 11, 2026