Skip to main content
PlaneConnection implements a Just Culture framework as part of the non-punitive reporting policy required by 14 CFR 5.21(a)(4). Just Culture provides a structured method for evaluating human behavior involved in safety events, distinguishing between honest mistakes, at-risk choices, and reckless conduct. The framework is grounded in ICAO Doc 9859 guidance and the FAA’s emphasis on organizational learning over individual blame.

Governing Principle

Accountability is applied based on the nature of the behavior, not the severity of the outcome. Just Culture is not blame-free; an honest error that leads to a serious event is treated differently from a reckless action that happens to have no consequence.

Behavior Categories

CategoryDefinitionOrganizational ResponseIndividual Accountability
Human ErrorAn inadvertent action or decision — the individual did not intend to deviate from expected behavior. The error arose from system design, environmental factors, or cognitive limitations.Console. Investigate system factors.No disciplinary action. Focus on system improvement.
At-Risk BehaviorA conscious choice to deviate from established procedure, where the individual did not recognize or underestimated the risk. Often driven by normalization of deviance, time pressure, or perceived operational benefit.Coach. Address the risk perception gap.Coaching and remedial training. Remove incentives for the behavior.
Reckless BehaviorA conscious, unjustifiable disregard of a substantial and known risk. The individual chose to act despite knowing the behavior was unsafe.Discipline. Proportionate to the severity of the disregard.Disciplinary action per organizational policy. May include removal from safety-sensitive duties.

Decision Tree

The following decision tree guides the behavior classification process. It is applied by the safety manager (or designee) during or after an investigation.

Decision Criteria Detail

If no documented procedure existed for the situation, the individual cannot be held to a standard that was not defined. The absence of a procedure is itself a system deficiency to be addressed.If No: Classify as Human Error. Investigate why the procedure was missing.
Determine whether the deviation was intentional (the person chose to act differently) or inadvertent (the person did not realize they were deviating).If No (inadvertent): Classify as Human Error. Investigate system factors — training adequacy, procedure clarity, workload, fatigue, interface design.
Evaluate whether a reasonable person in the same position would have recognized the risk. Consider the individual’s training, experience, and the information available at the time.If risk was not recognized or was underestimated: Classify as At-Risk Behavior. The gap between actual risk and perceived risk indicates a need for coaching and system review.
Determine whether the individual had a justifiable reason for the deviation (e.g., responding to a competing safety priority, following a supervisor’s direction) or whether the choice reflected conscious, unjustifiable disregard.If justifiable reason existed: Classify as At-Risk Behavior. Investigate the systemic conditions that created the conflict.If no justification: Classify as Reckless Behavior.

Response Actions

BehaviorPrimary ResponseSupporting ActionsDocumentation
Human ErrorConsole the individual. Acknowledge the error without blame.System review to identify contributing factors. Procedure improvement. Training reinforcement if needed.Case log entry with system improvement recommendations.
At-Risk BehaviorCoach the individual. Explain the actual risk and close the perception gap.Remove incentives for the behavior. Review procedures for clarity. Assess whether the behavior is normalized across the organization.Case log entry with coaching record and system change recommendations.
Reckless BehaviorDiscipline proportionate to the severity of the disregard.Review whether the behavior pattern is isolated or systemic. Assess fitness for duty.Case log entry with disciplinary action and follow-up plan.

Case Log

Every Just Culture evaluation is recorded in the case log. Each entry includes:
FieldTypeDescription
case_codeStringAuto-generated tracking code (e.g., JC-2026-0012).
linked_reportReferenceThe safety report that triggered the evaluation.
linked_investigationReferenceThe investigation associated with the event (if applicable).
individualUser referenceThe person whose behavior is being evaluated. Restricted visibility — accessible only to the safety manager and accountable executive.
behavior_categoryEnumhuman_error, at_risk, or reckless.
decision_rationaleTextDocumented reasoning for the classification, including answers to the decision tree questions.
response_actionTextDescription of the organizational response taken.
statusEnumCurrent case status (see below).
follow_up_dateDateDate for follow-up review, if applicable.
created_atTimestampCase creation timestamp (UTC).
closed_atTimestampCase closure timestamp (UTC).

Case Statuses

StatusAPI ValueDescription
OpenopenEvaluation in progress. Behavior classification pending.
ClassifiedclassifiedBehavior category assigned. Response action being determined.
Action Takenaction_takenOrganizational response has been implemented (console, coach, or discipline).
Follow-Upfollow_upResponse implemented; follow-up review scheduled to confirm effectiveness.
ClosedclosedCase complete. All actions and follow-ups resolved.

Quarterly Statistics

PlaneConnection generates quarterly Just Culture statistics for safety committee review and safety performance monitoring. These metrics support compliance with 14 CFR 5.71 (safety performance monitoring and measurement).
MetricDescription
Total casesNumber of Just Culture evaluations initiated in the quarter.
By behavior categoryBreakdown of cases by human error, at-risk behavior, and reckless behavior.
By departmentDistribution of cases across operational departments.
Response distributionCount of console, coach, and discipline responses applied.
Open case ageAverage and maximum age of cases not yet closed.
Repeat casesIndividuals with more than one case in the trailing 12 months.
System improvementsNumber of system changes (procedure revisions, training updates, equipment modifications) initiated from Just Culture cases.

Confidentiality and Access Control

Just Culture case data contains sensitive personnel information. Access is restricted as follows:
RoleAccess Level
Safety ManagerFull access to all case data including individual identity.
Accountable ExecutiveFull access to all case data.
InvestigatorsAccess to linked investigation data only. Individual identity redacted unless authorized by safety manager.
All other usersNo access to Just Culture case data.

Regulatory Alignment

RegulationSectionRequirementFramework Component
14 CFR Part 55.21(a)(4)Non-punitive reporting policyJust Culture decision tree ensures fair, consistent treatment.
14 CFR Part 55.21(a)(3)Code of ethicsBehavior standards that define expectations.
14 CFR Part 55.91Competencies and trainingCoaching and remedial training responses.
ICAO Doc 9859Ch. 2Safety culture — just culture componentThree-category behavior model and organizational response.
49 USC 42121AIR 21Whistleblower protectionNon-punitive policy for good-faith safety reporting.

Use the Just Culture Tool

Conduct a Just Culture evaluation.

Just Culture Concepts

Explanation of Just Culture principles and organizational safety culture.

Investigation Workflow

How investigations connect to Just Culture evaluations.

Report Types

Safety report types that may trigger Just Culture review.
Last modified on April 11, 2026