{"id":149668,"date":"2026-07-13T20:34:00","date_gmt":"2026-07-13T15:04:00","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=149668"},"modified":"2026-07-13T19:09:40","modified_gmt":"2026-07-13T13:39:40","slug":"private-jet-flies-into-united-787-path-triggering-collision-alert","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2026\/07\/13\/private-jet-flies-into-united-787-path-triggering-collision-alert\/","title":{"rendered":"Private Jet Flies Into Path of United Boeing 787, Triggering Collision Alert"},"content":{"rendered":"\n

NEW YORK-<\/strong> A private jet departing Teterboro Airport (TEB) flew directly into the path of a United Airlines (UA)<\/a> widebody on approach to Newark Liberty International Airport (EWR), forcing the airliner’s crew to react to a collision alert.<\/p>\n\n\n\n

The aircraft involved was a Hawker 800XP registered N58DH, operating from Teterboro to Merida (MID) in Mexico. The other aircraft was United flight UA1981, a Boeing 787-10 Dreamliner arriving from Los Angeles (LAX).<\/p>\n\n\n\n

The conflict developed on the evening of July 8, 2026, and was captured in air traffic control audio published by the YouTube channel You can see ATC<\/a>, which also released a visualization of the encounter.<\/p>\n\n\n\n

\"Private
Photo: avgeekwithlens\/ Harsh Tekriwal<\/figcaption><\/figure>\n\n\n\n

Private Jet Came Close to United 787<\/h2>\n\n\n\n

The recording covers roughly eight minutes of repeated miscommunication between the private jet pilot and the departure controller. The pilot failed to comply with a series of instructions and appeared to lack situational awareness of his position relative to the arrival traffic around him.<\/p>\n\n\n\n

The controller summarized the situation bluntly near the end of the exchange, telling the pilot he had “disregarded every single instruction.”<\/p>\n\n\n\n

English was clearly not the pilot’s first language, which added friction to an already congested frequency. The audio does not indicate any mechanical problem with the aircraft. The confusion centered entirely on headings, altitudes, and readbacks.<\/p>\n\n\n\n

\"Private
Photo: Dylan T | Flickr<\/figcaption><\/figure>\n\n\n\n

United 787 Receives a TCAS Resolution Advisory<\/h2>\n\n\n\n

As the Hawker drifted off its assigned track, it entered the path of the arriving United Dreamliner. The situation escalated to the point where the Boeing 787-10 received a TCAS resolution advisory, requiring the flight crew to take avoidance action to prevent a possible collision.<\/p>\n\n\n\n

A resolution advisory is not a caution. It is a command from the onboard collision avoidance system that pilots must follow immediately. Its activation confirms the two aircraft came uncomfortably close.<\/p>\n\n\n\n

The United crew handled the event professionally and complied with the alert without incident. Both aircraft continued safely.<\/p>\n\n\n\n

\"United
Photo: jpellgen | Flickr<\/figcaption><\/figure>\n\n\n\n

Where Air Traffic Control Contributed to the Problem<\/h2>\n\n\n\n

The private jet pilot carries the bulk of the responsibility, but the controller’s handling of the situation also allowed the problem to grow. Several specific points stand out from the audio, as flagged by OMAAT,<\/a> are as follows:<\/p>\n\n\n\n

Incorrect readback went uncorrected.<\/strong> The controller instructed the pilot to fly a heading of 260. The pilot read back a heading of 200. The controller did not catch the error. Correcting that single readback would have prevented most of what followed.<\/p>\n\n\n\n

Delivery did not match the pilot’s ability.<\/strong> Given the language barrier, the controller’s fast speech and lengthy instructions increased the chance of misunderstanding rather than reducing it.<\/p>\n\n\n\n

Frequency management was poor.<\/strong> An extended conversation between the controller and the United crew took place on the same busy frequency while the Hawker pilot was still visibly confused. That discussion could have been moved off frequency.<\/p>\n\n\n\n

A direct question went unanswered.<\/strong> The pilot asked whether he should climb to 15,000 feet instead of the 6,000 feet he had been assigned. The controller did not respond to that question.<\/p>\n\n\n\n

\n