Near Miss at Newark Hawker 800XP Ignores ATC, United 787 Goes Around

A Hawker and a 787 Converge in Newark Airspace

On July 8, 2026, a Hawker 800XP registered N58DH departed Teterboro Airport for Mérida, Mexico while United Airlines Flight UA1981, a Boeing 787-10, was arriving at Newark. A breakdown in heading and altitude compliance brought the two aircraft into an unsafe conflict in one of the busiest pieces of terminal airspace in the United States.

The Hawker was initially instructed to fly heading 260 and climb to 6,000 feet. The readback was correct at first, but the following exchange became increasingly confused. Controllers issued repeated instructions to stop the climb and turn away from the developing conflict. The pilot's subsequent questions and readbacks showed that the intended path was not being maintained.

The United 787 was approaching runway 22L when its traffic-alert and collision-avoidance system generated a Resolution Advisory. The crew responded to the RA and initiated a go-around after the conflict developed. ATC then separated the aircraft and continued working both flights.

The event was not a collision, but the safety margin became small enough that the airborne collision-avoidance system became an active part of the defense. TCAS is designed to provide an independent last line of protection when the separation provided by ATC is no longer sufficient.

The radio exchange also shows why readbacks matter. An incorrect heading readback can be corrected before the aircraft moves into another traffic stream. In this case, the initial misunderstanding was not fully resolved, and subsequent instructions became progressively more urgent.

Both aircraft ultimately continued safely. The incident nevertheless provides a clear picture of how quickly a communication problem can become a traffic conflict in New York's terminal airspace.

The first significant error was not necessarily the closest point of approach; it was the failure to correct the aircraft's trajectory when the communication problem first became apparent. The New York departure environment is built around precise headings and altitude restrictions because small deviations can move an aircraft into another arrival or departure stream.

The radio recording shows the controller becoming increasingly direct as the Hawker continued to diverge from the intended path. Instructions to stop the climb and turn were repeated because the aircraft's movement was becoming inconsistent with the clearance.

At the same time, the United crew was flying an instrument approach into Newark. The 787's collision-avoidance system provided an independent warning when the geometry became unsafe. The RA was not a suggestion; it was the aircraft's last-resort collision-avoidance command and the crew responded by following it and going around.

The event also illustrates the difference between an ATC clearance and an aircraft's actual position. A clearance can be perfectly clear on the controller's screen while the aircraft executes something else. Readback errors exist precisely so that both sides can catch that divergence early.

Language and workload were also part of the communication environment described by contemporary reporting. The private-jet pilot appeared to have difficulty following rapid instructions, while the controller continued to issue detailed corrections on a busy frequency. In such circumstances, short, unambiguous instructions and accurate readbacks become especially important.

After the conflict, both aircraft remained under control and were separated by ATC. There was no collision and no reported injury. The seriousness of the event lies in how many independent protections had to activate: controller intervention, the United crew's response and the TCAS RA all contributed to keeping the two aircraft apart.

The United crew's response also deserves attention. A go-around during an approach is not a failure of the landing; it is an established safety maneuver. In this case, it created additional spacing after the TCAS warning and allowed the aircraft to be resequenced.

Once the conflict had passed, the aircraft did not require an emergency landing. That outcome should not obscure the severity of the preceding loss of separation. Collision-avoidance systems are designed to prevent exactly this kind of event from becoming a midair collision, but they are a final protective layer rather than a substitute for accurate ATC clearances and pilot compliance.

New York terminal airspace leaves little room for ambiguity. Teterboro departures, Newark arrivals and nearby traffic streams interact in a compact area. A heading that is only slightly different from the intended one can put an aircraft in a completely different traffic flow within minutes.

“On 08 July 2026 at approximately 7:07 PM local time, a serious loss of separation occurred near Newark Liberty International Airport, New Jersey.”

Accident Facts

Sources

• Video source (ATC/audio reconstruction)
• One Mile at a Time, 12 July 2026.
• Aviation A2Z, 13 July 2026.
• Omni Flights, 13 July 2026.
• Video/ATC recording