Near-Midair Collision Followed by Unsafe Pilot Maneuvers

The event in context

The available the reconstruction material for this near-midair event is primarily the ATC recording sequence rather than a completed accident investigation. That matters editorially: the article should describe what the radio record demonstrates without assigning a definitive cause that an official investigation has not established.

Reconstructing this flight

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.

What the evidence establishes

The ATC recording is therefore the strongest primary-style source available for the page. The reconstruction should place the aircraft on the map, identify the conflicting tracks and show the point at which the controller and pilots recognized the conflict. The value is in reconstructing the sequence rather than labeling one pilot ‘dismissive’ without a documented finding.

How the Traffic Conflict Developed

The reconstructed sequence can be read as a chain of six decision points: Traffic conflict develops → Aircraft converge → ATC recognizes conflict → Avoidance window shrinks → Near-midair → ATC recording sequence / review. Each step changed the aircraft’s available options. The important analytical point is not to isolate the final impact from the preceding events; the final outcome was produced by the accumulation of the earlier changes in aircraft state, position, workload and available escape options.

The ATC/radar perspective is most useful when it is synchronized with the aircraft evidence. In this case the critical transition is the move from traffic conflict develops to ATC recording sequence / review. Once the aircraft reached the later stages of the sequence, the crew had fewer safe alternatives than they had at the beginning. That is the operational value of reconstructing the event rather than describing it only from the final crash scene.

Additional evidence and analysis

Because this is a near-midair rather than a completed crash investigation, the article should focus on the geometry and the communications. 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 high-quality article should not adopt that label as fact. 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. If the available data do not support precise distances or altitudes, the graphic should be clearly labeled as a schematic rather than presented as a measured reconstruction.

A near-midair reconstruction should also identify the defenses that did work. 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 article should also avoid treating the absence of a collision as proof that there was no risk. Near-midair events are valuable precisely because they expose a safety barrier before it fails. The flight-path diagram should therefore show the conflict point and the avoidance point, making clear that the aircraft were close enough for the event to become consequential even though both ultimately remained airborne.

The final reconstruction should therefore preserve the uncertainty. It can describe the traffic conflict, the radio exchange and the avoidance maneuver with confidence, while reserving judgment about the underlying pilot decision-making until a formal finding exists.

The Shrinking Avoidance Window

The decisive safety issue in this incident was specific to the sequence: Aircraft converge; ATC recognizes conflict; Avoidance window shrinks. Treating those events as isolated anomalies would miss the way they interacted.

Sources and investigation material

• https://www.faa.gov/airports/runway_safety

Accident Facts