United Airlines Flight Veers Off Runway at Newark, Sources Say; Details Remain Sparse

An aircraft operated by United Airlines reportedly collided with a ground vehicle and a light pole while landing at Newark Liberty International Airport in New Jersey on Sunday afternoon, according to wire reports from Mehr News and PressTV with timestamps between 05:05 and 06:27 UTC on 4 May 2026. The reports, citing what appears to be initial incident footage, describe a Boeing 767 carrying 231 passengers. No confirmed casualty figures from independent sources were available as this article went to press.

The account emerging from these initial reports describes a landing sequence that went wrong near a New Jersey highway, with the aircraft striking a light pole and what was described as a truck. Footage circulated on Telegram, attributed to Mehr News, shows the aftermath of the collision. PressTV, the English-language service of Iranian state media, carried a report characterised as a "horrific incident" at Newark.

At this stage, the reporting is thin. The sources in the thread are all from Iranian state-linked outlets — Mehr News, PressTV, and Tasnim — and while the imagery appears to document a real aviation event, no major Western wire service has been cited in the available feed. Reuters, the Associated Press, and the Federal Aviation Administration have not appeared in the source cluster as it stands. This matters: a runway excursion at a major US hub involving 231 passengers would generate a flood of simultaneous reporting from domestic and international wires. Its absence is notable.

What the Sources Say — and What They Don't

The thread provides four items from three sources, all timestamped within a two-hour window on 4 May. The Mehr News Telegram channel posted footage labelled as the moment of the collision, with a caption referencing 231 passengers and a United Airlines Boeing 767. A second Mehr News item, posted fourteen minutes later, describes the aircraft striking a light pole near the New Jersey highway. Tasnim, another Iranian news service, carries a parallel report. PressTV's English-language wire ran a brief item labelled "horrific incident."

None of these sources specify fatalities, injuries, or the condition of the aircraft. None cite an FAA statement, a Port Authority of New York and New Jersey spokesperson, or a United Airlines press release. The absence of those primary institutional sources — standard for any aviation incident of this scale — is a gap the available feed has not yet filled.

The Sourcing Asymmetry Worth Noting

It is worth flagging that the first and most detailed public accounts of an incident at a major American international airport are coming, in this feed, from Iranian state-adjacent media. That is not inherently suspicious — wire services pick up footage from multiple sources, and Telegram is a common aggregation point — but it is a structural observation worth making. American aviation incidents are, in normal circumstances, first reported by domestic wires, confirmed by the FAA, and carried by Reuters and AP within minutes. Here, the confirmed timeline starts with sources whose editorial posture leans toward a specific geopolitical framing.

This publication is not suggesting the incident did not occur. The footage is visually consistent with an aircraft accident. But the evidentiary weight rests, at time of publication, on a narrow sourcing base that does not include the institutional accounts that would normally constitute the backbone of such reporting. Readers should treat the specifics — the 231-passenger figure, the reference to a Boeing 767, the "truck" collision — as reported claims awaiting independent confirmation.

The Underlying Pattern

Aviation incidents at major US hubs are high-significance events that generate intense media scrutiny and institutional response. Newark Liberty International Airport is one of the busiest in the United States, handling hundreds of daily operations. A runway incursion resulting in a collision with ground infrastructure would normally trigger an NTSB investigation, an FAA statement, and a rapid cascade of official confirmation.

That cascade has not yet appeared in the available feed. The thread does not include a Reuters file, an FAA press release, a Port Authority statement, or a United Airlines corporate communication. This could be a timing issue — the feed may simply not have captured those items yet. Or it could reflect the fact that the incident is still being assessed and official confirmation has not been issued. Either way, the absence is part of the record.

What Happens Next

If the incident is confirmed, the regulatory and operational fallout at Newark will be significant — runway closures, investigation timelines, passenger compensation obligations, and a post-incident review process that typically spans months. The FAA and NTSB response, when it arrives, will be the authoritative account of what happened, why, and who bears responsibility.

Until then, this publication will treat the available sourcing for what it is: initial wire reports from a limited set of sources, capturing footage and preliminary captions, but lacking the institutional corroboration that would normally accompany an event of this scale. The footage suggests something happened. The specifics remain open.

Monexus covers this incident against a sourcing cluster dominated by Iranian state-linked wires; the wire contrast with typical domestic-first aviation reporting is noted.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/mehrnews/99999
• https://t.me/presstv/88888
• https://t.me/mehrnews/99998
• https://t.me/tasnimplus/77777