What is the recommended process for reporting and documenting an in-flight incident?

• A. Wait until after landing to report.
• B. Only report if there is a major injury.
• C. Complete an incident report with factual details, collect witness statements, preserve evidence, and follow the proper internal process.
• D. Document only the actions you took privately.

Answer: (C)

Prompt, thorough reporting and documentation of in-flight incidents is essential for safety and regulatory compliance. The correct approach is to complete a formal incident report with factual, objective details as soon as possible, collect witness statements, preserve any evidence (photos, logs, recordings, equipment data), and follow the established internal process for escalation and review. This practice creates a reliable record that supports accurate investigations, helps identify root causes, and drives corrective actions to prevent recurrence. Gathering witness statements provides multiple perspectives and strengthens the credibility of what happened, while preserving evidence ensures nothing is lost or altered before review. Following the proper internal process keeps everyone aligned, ensures the right departments are involved (safety, operations, regulatory affairs), and ensures timely, consistent handling of the incident.

Delaying reporting until after landing can hinder the investigation and ongoing safety measures. Only reporting for major injuries overlooks smaller incidents and near-misses that still offer valuable lessons. Documenting only private actions misses the formal record needed for investigation, accountability, and learning across the team. By reporting promptly, documenting comprehensively, and adhering to the official process, you contribute to a safer operation for everyone on board and in the air.