Pilot Nearly Causes Mid-Air Collision | VFR in IMC Conditions

Advertisement
Timeline
DEPARTURE
DOTCOM 3871 was operating near cloud bases under approach control on 17 April 2026.
1
DEVELOPING
ATC issued an urgent traffic alert for N6994U at about one mile and nearly the same altitude.
2
DECISION / RESPONSE
DOTCOM 3871 reported no visual contact and requested immediate vectors.
3
EMERGENCY
The conflicting aircraft passed behind as ATC worked to maintain separation.
4
FINAL SEQUENCE
N6994U subsequently contacted ATC and requested a pop-up IFR clearance.
5
OUTCOME
ATC advised the pilot of a possible deviation and provided follow-up contact information.
6

Accident facts and aircraft context

On 17 April 2026, DOTCOM 3871 and N6994U came into close proximity near cloud bases under approach control.

The aircraft were reported about one mile apart and at nearly the same altitude, around 4,200–4,300 feet.

The event was a near-midair conflict; no collision occurred.

Purpose of the flight

VFR operation under approach control near cloud bases.

Flight sequence and key events

The crew of DOTCOM 3871 was unable to visually acquire the aircraft (no joy) and requested immediate vectors, highlighting a near mid-air collision scenario in reduced visibility conditions.

DOTCOM 3871 reported that the other aircraft appeared to be in IMC while likely flying under VFR, significantly increasing the risk.

ATC provided heading changes to ensure separation, and the traffic eventually passed behind.

N6994U later contacted ATC and requested a pop-up IFR clearance, which was granted after confirming qualifications.

Due to the severity of the incident, ATC advised the pilot of a possible deviation and provided a contact number for follow-up, emphasizing the danger of operating VFR in cloud conditions at such close proximity.

Investigation findings

contemporary reporting states that the conflicting aircraft, N6994U, was about one mile away and around 4,200–4,300 feet when the traffic alert was issued. DOTCOM 3871 reported no visual contact and requested immediate vectors.

After the traffic passed behind, N6994U contacted ATC and received a pop-up IFR clearance after its qualifications were confirmed. ATC advised the pilot that a possible deviation had occurred and provided a contact number for follow-up.

This was a near-collision, not a crash. The strongest evidence is the ATC sequence: the urgent traffic alert, the lack of visual contact, the vectoring, the eventual passage of the traffic and the later pop-up IFR request. Those facts explain the risk without overstating the outcome.

How the event developed

The two aircraft came into close proximity at nearly the same altitude in reduced visibility. ATC issued traffic alerts and vectors, preventing a collision; the event remained an operational review rather than a fatal accident.

What the record establishes

No final accident probable-cause finding is applicable. The available record documents a near-midair traffic conflict and ATC intervention.

What the evidence shows

This was a near-midair conflict rather than a crash. The available ATC record establishes the proximity, the lack of visual contact and the corrective vectors, but it does not establish a formal accident cause.

Incident date
17 April 2026
Aircraft / registration
Multiple aircraft — DOTCOM 3871 and N6994U
Investigation status
ATC incident record / contemporary operational account

Sources

This is a source-based reconstruction using the incident record, investigation material and publicly available ATC/operational records identified in the Sources section.
Advertisement

The weekly incident