Home / Case Files / Near-Midair Collision Followed by Unsafe Pilot Maneuvers

Near-Midair Collision Followed by Unsafe Pilot Maneuvers

🏷️Midair / Near miss▪️5:51
Advertisement
Accident timeline for Near-Midair Collision Followed by Unsafe Pilot Maneuvers
Accident-specific timeline reconstructed from the documented sequence; diagram not to scale.
Timeline
Traffic conflict develops
1.
Aircraft converge
2.
ATC recognizes conflict
3.
Avoidance window shrinks
4.
Near-midair
5.
ATC reconstruction / review
6.

What the ATC Recording Shows, Without a Completed Investigation

The primary evidence for this near-midair is the ATC recording sequence rather than a completed accident investigation. What follows therefore describes what the radio record demonstrates, without assigning a cause no official investigation has established.

The Geometry of a Closing Near-Midair

The important evidence is the convergence itself. A near-midair is not merely a moment when two aircraft are ‘close’; it is a geometry problem in which relative motion determines how quickly the separation disappears. A controller can issue a correction, but the pilots still have to recognize the traffic and respond in time.

Reconstructing the Sequence Rather Than Assigning Blame

The value is in reconstructing the sequence rather than labeling one pilot ‘dismissive’ without a documented finding.

What the Radio Record Can and Can't Support

Because this is a near-midair rather than a completed crash investigation, the geometry and the communications are what the record can support. The useful questions are: where were the aircraft when the conflict became visible, what information had each pilot received, what did the controller know, and how much time remained between recognition and avoidance? Those questions can be answered from the ATC recording sequence without assigning a legal or investigative finding.

The word ‘dismissive’ in the incident title is an editorial characterization, not an investigation finding. A pilot can sound abrupt, dismissive or frustrated on the radio without that proving why the conflict developed. The more valuable approach is to identify the exact transmission, the aircraft’s track and the resulting separation, then let the reader see where the defenses failed.

This is also why a flight-path graphic adds value here. A verbal description of a near-midair can make the event sound abstract. Showing two tracks converging, the controller’s intervention point and the eventual separation makes the event measurable.

The conflict was recognized, the pilots avoided an actual collision, and the controller’s intervention became part of the recovery. The fact that an accident did not occur is not evidence that the system worked perfectly; it is evidence that the final barrier still had enough time to succeed. That is precisely why the event is worth documenting.

The absence of a collision is not proof that there was no risk. Near-midair events are valuable precisely because they expose a safety barrier before it fails. The conflict point and the avoidance point together show that the aircraft came close enough for the event to matter, even though both remained airborne.

Research and reconstruction

Flight Follower Editorial Team

This reconstruction was researched from official investigation records where they exist, the original air traffic control recording, and contemporary reporting. The aircraft movement, timeline and written account were assembled independently by Flight Follower. Where an investigation is open or no probable cause has been published, the account says so rather than offering one.

About the Flight Follower team · Editorial policy · Corrections

Sources and investigation material

Accident Facts

Category
Midair / Near miss
Reconstruction
5:51
Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

The weekly incident