Skip to main content
PlaneConnection supports six safety report types. Each type maps to a distinct category of safety-relevant information as defined by the organization’s Safety Management System under 14 CFR Part 5.

Report Type Summary

TypeDatabase ValueDescription
HazardhazardA condition that could foreseeably cause or contribute to an aircraft accident.
IncidentincidentAn occurrence associated with the operation of an aircraft that affects or could affect safety.
Near-missnear_missAn event that could have resulted in an accident or incident but did not.
ConcernconcernA general safety concern about systemic or organizational issues.
ObservationobservationA factual observation about a safety-related condition or practice.
Audit Findingaudit_findingA finding resulting from an internal safety audit.

Detailed Definitions

Hazard

A hazard is a condition, object, activity, or situation that could foreseeably cause or contribute to an aircraft accident as defined in 14 CFR 5.5. Hazard reports initiate the Safety Risk Management (SRM) process and require a risk assessment. When to use: An unsafe condition has been identified that has not yet resulted in an event — for example, a deteriorating runway surface, an inadequate procedure, or a recurring equipment malfunction. Regulatory basis: 14 CFR 5.53 (System analysis and hazard identification)

Incident

An incident is an occurrence, other than an accident, associated with the operation of an aircraft that affects or could affect the safety of operations. Incidents may trigger an investigation workflow. When to use: An event has occurred that affected safety during aircraft operations — for example, a runway incursion, an in-flight equipment failure that was managed without injury, or a fuel discrepancy discovered after flight. Regulatory basis: 49 CFR 830.5 (NTSB immediate notification), ICAO Annex 13

Near-miss

A near-miss (also called a “near hit”) is an event that could have resulted in an accident or incident but did not, due to circumstances or intervention. Near-miss reports are a primary source of proactive safety data. When to use: An event occurred where the outcome was safe, but a slight change in conditions could have resulted in harm — for example, a traffic conflict resolved by TCAS, an aborted takeoff due to a vehicle on the runway, or a go-around triggered by an unstable approach. Regulatory basis: 14 CFR 5.71(a)(4) (Employee safety reporting)

Concern

A concern is a report about a systemic or organizational issue that could erode safety over time. Concerns are typically less event-specific than hazards or incidents and may address culture, workload, training gaps, or procedural drift. When to use: An individual observes a pattern or condition that does not fit a single event — for example, chronic understaffing during peak operations, inadequate training on a new procedure, or pressure to dispatch in marginal weather. Regulatory basis: 14 CFR 5.71(a)(7) (Employee safety concerns)

Observation

An observation is a factual, neutral report about a safety-related condition or practice. Observations do not require that a hazard or risk be identified — they serve as raw data for trend analysis and safety assurance. When to use: Routine safety observations during operations — for example, noting that a checklist step was skipped without consequence, documenting a ramp condition during a walkthrough, or recording a positive safety practice. Regulatory basis: 14 CFR 5.71 (Safety performance monitoring and measurement)

Audit Finding

An audit finding is a result from an internal safety audit that documents a nonconformity, deficiency, or area for improvement. Audit findings are typically linked to specific regulatory requirements or internal procedures. When to use: An internal audit has identified a gap between established procedures and actual practice — for example, expired training records, incomplete maintenance documentation, or non-compliance with an operational specification. Regulatory basis: 14 CFR 5.73 (Safety performance assessment)

Report Type and Workflow Relationships

Report TypeTriggers Risk AssessmentTriggers InvestigationCan Generate CPAs
HazardYesOptionalYes
IncidentYesYesYes
Near-missYesOptionalYes
ConcernOptionalNoYes
ObservationNoNoOptional
Audit FindingOptionalNoYes

Confidentiality

All report types support two submission modes:
  • Identified: The reporter’s identity is recorded and visible to safety management personnel.
  • Confidential: The reporter’s identity is recorded but restricted to the safety manager only.
The non-punitive reporting policy required by 14 CFR 5.21(a)(4) applies to all report types regardless of submission mode.