Reporting Occurrences and Incidents

Terminology and Phraseology Used in Aviation Incident Reporting

In global aviation, the transition from a “safety event” to a “safety record” relies entirely on the quality of communication. While standard radio phraseology governs the cockpit and the tower, the post-flight report requires a different, yet equally disciplined, application of the English language.

This article serves as a training foundation for pilots, air traffic controllers, and maintenance personnel to master the terminology and structure required for effective occurrence reporting. Accurate reporting is one of the most important responsibilities of every pilot, helping investigators prevent future accidents and improve operational safety.

For many pilots, especially those whose first language is not English, writing an aviation occurrence report can be challenging. Reports must be factual, concise, objective, and written using standard aviation terminology and phraseology.

I. Understanding Aviation Reporting Terminology

1. Defining the Scope: Occurrences vs Incidents

Before writing a report, it is essential to understand the regulatory taxonomy under ICAO Annex 13.

• Occurrence: Any safety-related event which endangers or which, if not corrected or addressed, could endanger an aircraft, its occupants, or any other person. Examples include airspace infringement, bird strikes, or communication failure.
• Incident: An occurrence, other than an accident, associated with the operation of an aircraft which affects or could affect the safety of operation. Examples: runway excursion, loss of separation, or engine malfunction.
• Serious Incident: An event where an accident nearly occurred. The circumstances indicate a high probability of an accident, e.g., near mid-air collision, fire on board extinguished before landing,
• Accident: An occurrence where a person is fatally or seriously injured, the aircraft sustains structural failure, or the aircraft is missing.

Understanding these distinctions ensures that the report is filed under the correct severity category, triggering the appropriate level of investigation.

2. The Language of Precision: Terminology and Phraseology

Aviation reporting sits at the intersection of Standard Phraseology and Plain English.

Standard Phraseology (the ‘What’)

When describing the event, use the vocabulary found in ICAO Doc 4444. Using standardized terms reduces ambiguity for international investigators.

Instead of: “The engine was acting weird.”

Use: “Engine #2 experienced uncommanded power fluctuations.”

Technical Vocabulary

Commonly misused terms can lead to confusion in a global database. Note the precision in these examples:

• Altitude vs. Height: Use Altitude (MSL) or Flight Level (standard pressure) unless specifically referring to distance above the ground (Height/AGL).
• Exceeded vs. Deviated: You exceed a limitation (e.g., airspeed) but deviate from a clearance or procedure.
• Intermittent vs. Continuous: Crucial for maintenance troubleshooting of avionics or mechanical glitches.

3. Structuring the Narrative: The 4-Phase Method

The “narrative” section is where most reports fail. A professional report should follow a chronological, objective sequence. Most aviation reports follow a similar structure.

Phase I: the Setup (Pre-event) – Basic Information

Establish the context – where were you and what were the conditions?

Include:

• Date & time
• Aircraft type and registration
• Flight number or callsign
• Departure and destination
• Flight phase

Example:

On 14 March 2026, at approximately 14:35 UTC, a Cessna 172 registration SP-ABC on a VFR flight from Kraków to Rzeszów experienced a radio communication failure during climb.

Phase II: The Trigger (The Event)

This is the main body of the report. Describe the exact moment the deviation occurred and any possible contributing factors like the weather, fatigue or workload. Keep the chronological order.

Explain what happened and when it happened. Avoid speculation.

Incorrect: “The problem was probably caused by poor maintenance.”

Correct: “The exact cause of the malfunction could not be determined during flight.”

Example:

During climb passing 3,500 feet, the aircraft radio began intermittent transmission. Attempts to contact Kraków Information were unsuccessful.

Phase III: The Action (Mitigation)

Describe actions taken to resolve the situation. What did the crew do? This demonstrates CRM and adherence to SOPs. Include: actions taken, for instance, return to departure airport, use of alternate frequency, checklist completion, diversion.

Examples:

The pilot checked circuit breakers and radio settings with no improvement. The flight continued under VMC conditions to the departure aerodrome.

Phase IV: The Outcome (Post-Event)

How did it end?

Example: “A safe landing was performed without further incident. The aircraft was met by technical services on taxiway Alpha.”

4. Writing Styles in English: Objectivity and the Passive Voice

In aviation English, the goal is to be a “dispassionate observer.” The report is a legal and technical document.

• Be Objective – present the neutral perspective. Reports are not personal opinions. The purpose is safety improvement, not blame. Instead of “The Co-pilot made a mistake,” use “The assigned altitude was inadvertently omitted during the readback”. This focuses on the error rather than the person, which is the heart of a Just Culture.
• Use Past Tense – incident reports normally use the past tense.

Correct: The aircraft entered controlled airspace without clearance.

Incorrect: The aircraft enters controlled airspace without clearance.

• Use Passive Voice Carefully -passive voice is common in technical aviation writing because it focuses on actions rather than individuals.

Example: A TCAS warning was received during climb.

Caution: Avoid excessive passive voice that makes reports unclear.

• Avoid Informal Language – whenever possible, use ICAO-standard terminology and phraseology. Avoid conversational expressions.

Incorrect: “The engine started acting weird”.

Correct: “The engine exhibited abnormal vibration”.

• Avoid Emotional Language – reports must remain professional. Words like “scary,” “frantic,” or “luckily” have no place in a report. Use “critical,” “rapid,” or “successfully”.

Incorrect: “The situation became terrifying”.

Correct: “The crew experienced high workload during the event”.

• Focus on the Aircraft/System

Subjective: “I couldn’t see the runway because the fog was bad”.

Objective: “Visual reference was lost due to a rapid reduction in RVR (Runway Visual Range) below CAT I minima”.

5. Clarity and Conciseness (Plain English)

While technical terms are necessary, the connective tissue of your report should be Plain English. ICAO defines this as being “efficient in communication”.

• Be clear: Keep sentences short, simple, and direct. Long, rambling sentences lead to grammatical errors and misunderstanding. Aim for 15–20 words per sentence.

• Avoid Jargon/Slang: While “The bird was heavy” makes sense to a pilot, “The aircraft was at Maximum Takeoff Weight (MTOW)” is the required professional standard.

• Be accurate: Report only confirmed facts. Avoid assumptions or unnecessary details.

Incorrect: “The controller was careless”.

Correct: “ATC issued a descent clearance to FL090 while another aircraft was maintaining FL100.”

6. The Importance of “Human Factors” in Reports

Modern reporting systems, such as SMS (Safety Management Systems), seek to understand why something happened. If a mistake was made, describe the contributing factors clearly:

• Environmental: Glare, noise, cockpit temperature.

• Physiological: Fatigue, high workload, or “channelized attention”.

• Organizational: Vague SOPs or time pressure.

Example: “The distraction caused by a non-pertinent cockpit conversation resulted in a failure to set the landing flaps”.

7. Checklist for Reviewing Your Report

Before hitting “submit,” use the C.A.P. rule to ensure quality:

Concise: Have I removed unnecessary words?

Accurate: Are the times (UTC), flight levels, and coordinates exact?

Professional: Is the tone objective and free of blame?

II. Useful Terminology in Aviation Reporting

The following expressions are commonly used in aviation reports.

1. Aircraft operations

Example:

The aircraft vacated runway 27 via taxiway Bravo.

2. Communication

Example:

Due to frequency congestion, the pilot was unable to obtain taxi clearance immediately.

3. Weather Terminology

Example:

The flight encountered moderate turbulence during descent through FL120.

4. Technical Issues

Example:

The crew observed abnormal oil pressure indications during cruise.

5. Common Aviation Report Verbs

These verbs are frequently used in occurrence reports:

When quoting radio communication, use standard phraseology whenever possible. This ensures that technical actions are recorded accurately.

Operational Example:

ATC instructed the aircraft to “go around due to traffic on the runway.”

Note: Avoid rewriting radio calls into informal language.

Example of a Short Incident Report: Bird Strike

Analyzing a practical example helps to understand the application of professional reporting standards.

On 5 February 2026 at approximately 0815 UTC, a Boeing 737 operating flight ABC123 departed Warsaw Chopin Airport runway 29 under VMC conditions. During initial climb passing 2,000 feet, the crew heard a loud impact followed by engine vibration indications on engine No. 1.

The crew suspected a bird strike and informed ATC immediately. Engine parameters remained within operational limits; however, vibration levels increased slightly. The crew decided to discontinue the climb and requested vectors for return to the departure airport.

An uneventful landing was completed approximately 15 minutes later. Post-flight inspection confirmed bird remains on the engine inlet and minor fan blade damage. No injuries were reported.

This example demonstrates:

• Chronological structure
• Objective tone
• Standard terminology
• Clear operational details

Frequent Mistakes Made by Student Pilots

To improve the quality of documentation, avoid these common errors:

1. Writing Too Much: Reports should be concise. Include relevant operational facts only.

2. Adding Personal Opinions: Avoid assigning blame or making assumptions.

3. Incorrect Aviation Vocabulary: Use standard aviation terminology instead of everyday language.

Incorrect: “The plane almost crashed.”

Correct: “Loss of separation occurred between the two aircraft.”

4. Poor Chronology: Events should be presented in sequence.

Why Reporting Matters

Some pilots hesitate to report incidents because they fear punishment or criticism. However, modern aviation safety culture encourages open reporting. Occurrence reports help to:

• Identify safety trends

• Improve training

• Prevent accidents

• Enhance procedures

• Improve communication

Many aviation authorities operate confidential or non-punitive reporting systems designed to improve safety rather than assign blame. A professional report demonstrates good airmanship, responsibility, and safety awareness.

Final Advice for Student Pilots

Developing good reporting skills early in training is extremely valuable. Student pilots should:

• Read real aviation safety reports

• Learn ICAO phraseology

• Practice technical writing in English

• Focus on facts, not emotions

• Keep reports clear and chronological

Conclusion

Writing a report in English is more than a linguistic task; it is a safety task. Every accurate report provides information that may help prevent a future incident or accident. A well-written report allows the industry to identify trends, fix mechanical flaws, and improve training.

By mastering the terminology and adopting a structured, objective narrative style, you contribute directly to the “Gold Standard” of global aviation safety. Good pilots are not only skilled in the cockpit — they are also effective communicators on the ground.

Text powered by AI