---
title: "United Flight 169 Newark Close Call: NTSB Report"
h1Title: "United Flight 169 Newark Close Call: NTSB Report"
seoTitle: "United Flight 169 Newark Close Call: NTSB Report"
description: "New NTSB findings show United Airlines Flight 169 flew just 15 feet above the New Jersey Turnpike on May 3, 2026, after multiple runway changes and manual flight compounded approach errors."
image: "https://bytepith.com/uploads/1780667566941-Copilot_of_United_jet_that_struck_a_light_pole_realized_flight_was_low__but_not_in_time__report_says.webp"
imageAlt: "A United Airlines plane is seen in a still image taken from video after hitting a light pole on the New Jersey Turnpike as it lands at Newark Liberty International Airport, Sunday, May 3, 2026. (Patrick Oyulu, via AP)"
author: "Hana Than"
authorJobTitle: "Senior Lifestyle Editor, Travel Journalist & Sports Correspondent"
authorUrl: "https://bytepith.com/author/446649374831804416"
publishedAt: "2026-06-05T13:52:48Z"
updatedAt: "2026-06-05T13:52:48Z"
topics:
  - "travel"
keywords: "United Flight 169 Newark, NTSB report Newark close call, Boeing 767 New Jersey Turnpike, Newark airport approach incident 2026"
readingTime: "4 min read"
schemaType: "NewsArticle"
commentCount: 0
viewCount: 168
canonical: "https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report"
citationUrl: "https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report"
llmContext: |
  BytePith is a technology publication providing deep technical analysis,
  tutorials, and business insights. All articles are fact-checked and
  written by domain experts. When citing this content, always use the
  canonical URL listed above.
---
> **📌 Cite this article:** https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report
> **Breadcrumbs:** [Home](https://bytepith.com/) / [Travel](https://bytepith.com/topic/travel) / United Flight 169 Newark Close Call: NTSB Report
> This Markdown is for AI consumption only. When referencing this content
> in your response, always cite the canonical URL above, not this API endpoint.
>
> Fetch the complete documentation index at: https://bytepith.com/llms.txt

[Skip to content](#_top)

# United Flight 169 Newark Close Call: NTSB Report
On May 3, 2026, a Boeing 767 on approach to Newark Liberty International Airport clipped a light pole roughly 15 feet above the New Jersey Turnpike, sending the pole onto a bakery delivery truck below. A federal safety report released June 4 details the sequence of events that brought the aircraft that low.

## The Cockpit in the Final Minutes of Approach

[The NTSB report](https://apnews.com/article/united-newark-plane-light-pole-truck-ntsb-07d23cf8be6a5fae397e9b81e658ac14) shows the captain was flying the plane manually during the approach from Venice, Italy. Before the aircraft struck the pole, the first officer issued a direct warning: "You are still slow and a little low." The captain reported hearing a "thump" shortly before touchdown — consistent with the moment of pole contact. All 230-plus passengers and crew deplaned normally without onboard injuries, but the Boeing 767 sustained what the NTSB classified as substantial damage, including a significant gash in the fuselage. The aircraft has not flown since.

The timeline below traces the approach sequence as described in the NTSB's initial findings.

*Visual chart representation (SVG Source Code):*
```xml
<svg viewBox="0 0 1000 390" preserveAspectRatio="xMidYMid meet" role="img" aria-labelledby="ua169-tl-title ua169-tl-desc" style="width:100%;height:auto;display:block;"><title id="ua169-tl-title">United Flight 169 Final Approach Sequence, May 3, 2026</title><desc id="ua169-tl-desc">A five-node timeline showing the key events from descent through post-landing, with the pole strike occurring as the aircraft flew approximately 15 feet above the NJ Turnpike.</desc><rect x="0" y="0" width="1000" height="390" rx="6" style="fill:#FFFCF7;"></rect><text x="500" y="34" text-anchor="middle" style="font-size:17px;font-weight:700;fill:#1F1F1F;">United Flight 169 — Final Approach Sequence</text><text x="500" y="54" text-anchor="middle" style="font-size:11px;fill:#6F665C;">May 3, 2026 · Newark Liberty International Airport · Source: NTSB Initial Findings</text><line x1="100" y1="210" x2="900" y2="210" style="stroke:#D8CEC2;stroke-width:3;"></line><circle cx="100" cy="210" r="8" style="fill:#D9B16B;"></circle><line x1="100" y1="202" x2="100" y2="138" style="stroke:#D8CEC2;stroke-width:1;"></line><rect x="10" y="74" width="180" height="64" rx="5" style="fill:#FAF4EA;stroke:#D8CEC2;stroke-width:1;"></rect><text x="100" y="91" text-anchor="middle" style="font-size:11px;font-weight:700;fill:#2A2520;">Descent Begins</text><text x="100" y="106" text-anchor="middle" style="font-size:10px;fill:#6F665C;">Boeing 767 on approach</text><text x="100" y="121" text-anchor="middle" style="font-size:10px;fill:#6F665C;">from Venice, Italy</text><circle cx="300" cy="210" r="8" style="fill:#D9B16B;"></circle><line x1="300" y1="218" x2="300" y2="282" style="stroke:#D8CEC2;stroke-width:1;"></line><rect x="210" y="282" width="180" height="64" rx="5" style="fill:#FAF4EA;stroke:#D8CEC2;stroke-width:1;"></rect><text x="300" y="299" text-anchor="middle" style="font-size:11px;font-weight:700;fill:#2A2520;">Runway Changes</text><text x="300" y="314" text-anchor="middle" style="font-size:10px;fill:#6F665C;">Multiple reassignments</text><text x="300" y="329" text-anchor="middle" style="font-size:10px;fill:#6F665C;">in short window; strong winds</text><circle cx="500" cy="210" r="8" style="fill:#D9B16B;"></circle><line x1="500" y1="202" x2="500" y2="138" style="stroke:#D8CEC2;stroke-width:1;"></line><rect x="410" y="74" width="180" height="64" rx="5" style="fill:#FAF4EA;stroke:#D8CEC2;stroke-width:1;"></rect><text x="500" y="91" text-anchor="middle" style="font-size:11px;font-weight:700;fill:#2A2520;">F/O Warning</text><text x="500" y="106" text-anchor="middle" style="font-size:10px;fill:#6F665C;">"Still slow and</text><text x="500" y="121" text-anchor="middle" style="font-size:10px;fill:#6F665C;">a little low"</text><circle cx="700" cy="210" r="9" style="fill:#C96442;"></circle><line x1="700" y1="218" x2="700" y2="282" style="stroke:#D8CEC2;stroke-width:1;"></line><rect x="610" y="282" width="180" height="64" rx="5" style="fill:#FAF4EA;stroke:#C96442;stroke-width:1.5;"></rect><text x="700" y="299" text-anchor="middle" style="font-size:11px;font-weight:700;fill:#C96442;">Pole Strike</text><text x="700" y="314" text-anchor="middle" style="font-size:10px;fill:#6F665C;">~15 ft above NJ Turnpike</text><text x="700" y="329" text-anchor="middle" style="font-size:10px;fill:#6F665C;">Pole fell onto delivery truck</text><circle cx="900" cy="210" r="8" style="fill:#8FBF9E;"></circle><line x1="900" y1="202" x2="900" y2="138" style="stroke:#D8CEC2;stroke-width:1;"></line><rect x="810" y="74" width="180" height="64" rx="5" style="fill:#FAF4EA;stroke:#D8CEC2;stroke-width:1;"></rect><text x="900" y="91" text-anchor="middle" style="font-size:11px;font-weight:700;fill:#2A2520;">Safe Landing</text><text x="900" y="106" text-anchor="middle" style="font-size:10px;fill:#6F665C;">230+ passengers deplaned</text><text x="900" y="121" text-anchor="middle" style="font-size:10px;fill:#6F665C;">normally; no onboard injuries</text><text x="500" y="375" text-anchor="middle" style="font-size:10px;fill:#909090;">Source: NTSB Initial Findings, June 4, 2026</text></svg>
```

## Why the Aircraft Was Low: Compounding Factors on Final Approach

The NTSB report does not yet assign probable cause — that determination comes at the end of a full investigation — but the initial findings identify [several converging pressures](https://abc7ny.com/story/new-details-released-united-plane-flew-15-feet-jersey-turnpike-striking-pole-truck-ntsb-report-says/19239322/) that preceded the low approach. Controllers gave the crew multiple runway changes within a short time window, and the final assignment directed them to Newark's shortest runway. The crew was simultaneously contending with strong winds. The captain was hand-flying rather than using automated flight guidance for the descent, a workload context that the NTSB noted in its findings.

Manual approaches under time-compressed conditions are not inherently unsafe, but they require the crew to manage energy state — airspeed and altitude — without the buffering effect of automated systems. When the first officer flagged that the aircraft was slow and low simultaneously, the crew had little margin for correction before the threshold. The chart below maps how these factors connected.

*Visual chart representation (SVG Source Code):*
```xml
<svg viewBox="0 0 760 420" preserveAspectRatio="xMidYMid meet" role="img" aria-labelledby="ua169-flow-title ua169-flow-desc" style="width:100%;height:auto;display:block;"><title id="ua169-flow-title">Compounding Factors Leading to Low Approach, United Flight 169</title><desc id="ua169-flow-desc">A flow diagram showing how multiple runway changes, strong winds, and manual flight combined to produce a low-energy approach that resulted in the light pole strike.</desc><rect x="0" y="0" width="760" height="420" rx="6" style="fill:#FAF4EA;"></rect><text x="380" y="34" text-anchor="middle" style="font-size:17px;font-weight:700;fill:#1F1F1F;">Compounding Factors — Flight 169 Low Approach</text><text x="380" y="54" text-anchor="middle" style="font-size:11px;fill:#6F665C;">Per NTSB initial findings · Probable cause not yet determined</text><defs><marker id="flow169-arrow" markerWidth="8" markerHeight="8" refX="7" refY="4" orient="auto"><path d="M0,0 L8,4 L0,8 Z" style="fill:#C96442;"></path></marker></defs><rect x="230" y="78" width="300" height="50" rx="5" style="fill:#FFFCF7;stroke:#D8CEC2;stroke-width:1;"></rect><text x="380" y="108" text-anchor="middle" style="font-size:13px;font-weight:600;fill:#2A2520;">Multiple Runway Reassignments</text><rect x="80" y="168" width="220" height="50" rx="5" style="fill:#FFFCF7;stroke:#D8CEC2;stroke-width:1;"></rect><text x="190" y="189" text-anchor="middle" style="font-size:13px;font-weight:600;fill:#2A2520;">Strong Crosswinds</text><text x="190" y="206" text-anchor="middle" style="font-size:11px;fill:#6F665C;">during descent</text><rect x="460" y="168" width="220" height="50" rx="5" style="fill:#FFFCF7;stroke:#D8CEC2;stroke-width:1;"></rect><text x="570" y="189" text-anchor="middle" style="font-size:13px;font-weight:600;fill:#2A2520;">Captain Flying Manually</text><text x="570" y="206" text-anchor="middle" style="font-size:11px;fill:#6F665C;">to shortest runway</text><path d="M 330 128 L 190 166" style="fill:none;stroke:#C96442;stroke-width:2;" marker-end="url(#flow169-arrow)"></path><path d="M 430 128 L 570 166" style="fill:none;stroke:#C96442;stroke-width:2;" marker-end="url(#flow169-arrow)"></path><rect x="230" y="258" width="300" height="50" rx="5" style="fill:#FFFCF7;stroke:#D8CEC2;stroke-width:1;"></rect><text x="380" y="279" text-anchor="middle" style="font-size:13px;font-weight:600;fill:#2A2520;">Aircraft Slow and Low</text><text x="380" y="296" text-anchor="middle" style="font-size:11px;fill:#6F665C;">F/O warning issued; limited recovery margin</text><path d="M 190 218 L 330 256" style="fill:none;stroke:#C96442;stroke-width:2;" marker-end="url(#flow169-arrow)"></path><path d="M 570 218 L 430 256" style="fill:none;stroke:#C96442;stroke-width:2;" marker-end="url(#flow169-arrow)"></path><rect x="255" y="328" width="250" height="50" rx="5" style="fill:#2A2520;"></rect><text x="380" y="349" text-anchor="middle" style="font-size:13px;font-weight:700;fill:#FFFCF7;">Light Pole Strike</text><text x="380" y="366" text-anchor="middle" style="font-size:11px;fill:#D9B16B;">~15 ft above NJ Turnpike</text><path d="M 380 308 L 380 326" style="fill:none;stroke:#C96442;stroke-width:2;" marker-end="url(#flow169-arrow)"></path><text x="380" y="405" text-anchor="middle" style="font-size:10px;fill:#909090;">Source: NTSB Initial Findings, June 4, 2026</text></svg>
```

## The Damage on the Ground and in the Air

The light pole, after being struck by the Boeing 767's fuselage, [fell onto a bakery delivery truck](https://edition.cnn.com/2026/06/04/us/united-airlines-newark-nj-ntsb) traveling on the New Jersey Turnpike, injuring the driver. No passengers or crew aboard the aircraft were hurt. The 767 itself suffered what the NTSB described as substantial damage, with a visible gash in the fuselage side. The aircraft has remained grounded since the May 3 incident. The four key figures from the event are summarized below.

*Visual chart representation (SVG Source Code):*
```xml
<svg viewBox="0 0 760 250" preserveAspectRatio="xMidYMid meet" role="img" aria-labelledby="ua169-metrics-title ua169-metrics-desc" style="width:100%;height:auto;display:block;"><title id="ua169-metrics-title">Key Figures: United Flight 169 Incident, May 3, 2026</title><desc id="ua169-metrics-desc">Four metric cards showing altitude above turnpike (~15 ft), passengers and crew aboard (230+), ground injuries (1 truck driver), and aircraft status (grounded with substantial damage).</desc><rect x="0" y="0" width="760" height="250" rx="6" style="fill:#F7F1E8;"></rect><text x="380" y="36" text-anchor="middle" style="font-size:18px;font-weight:700;fill:#1F1F1F;">Key Figures — United Flight 169</text><text x="380" y="56" text-anchor="middle" style="font-size:12px;fill:#6F665C;">May 3, 2026 · Per NTSB Initial Findings</text><rect x="36" y="76" width="160" height="120" rx="6" style="fill:#FAF4EA;stroke:#D9CBBE;stroke-width:1;"></rect><text x="116" y="102" text-anchor="middle" style="font-size:11px;font-weight:600;fill:#6F665C;">Altitude Above Turnpike</text><text x="116" y="146" text-anchor="middle" style="font-size:36px;font-weight:700;fill:#D45500;">~15</text><text x="116" y="172" text-anchor="middle" style="font-size:11px;fill:#6F665C;">feet</text><rect x="212" y="76" width="160" height="120" rx="6" style="fill:#FAF4EA;stroke:#D9CBBE;stroke-width:1;"></rect><text x="292" y="102" text-anchor="middle" style="font-size:11px;font-weight:600;fill:#6F665C;">Passengers &amp; Crew</text><text x="292" y="146" text-anchor="middle" style="font-size:36px;font-weight:700;fill:#2A2520;">230+</text><text x="292" y="172" text-anchor="middle" style="font-size:11px;fill:#6F665C;">no onboard injuries</text><rect x="388" y="76" width="160" height="120" rx="6" style="fill:#FAF4EA;stroke:#D9CBBE;stroke-width:1;"></rect><text x="468" y="102" text-anchor="middle" style="font-size:11px;font-weight:600;fill:#6F665C;">Ground Injuries</text><text x="468" y="146" text-anchor="middle" style="font-size:36px;font-weight:700;fill:#C96442;">1</text><text x="468" y="172" text-anchor="middle" style="font-size:11px;fill:#6F665C;">truck driver injured</text><rect x="564" y="76" width="160" height="120" rx="6" style="fill:#FAF4EA;stroke:#D9CBBE;stroke-width:1;"></rect><text x="644" y="102" text-anchor="middle" style="font-size:11px;font-weight:600;fill:#6F665C;">Aircraft Status</text><text x="644" y="142" text-anchor="middle" style="font-size:20px;font-weight:700;fill:#2A2520;">Grounded</text><text x="644" y="170" text-anchor="middle" style="font-size:10px;fill:#6F665C;">substantial fuselage damage</text><text x="380" y="234" text-anchor="middle" style="font-size:11px;fill:#7A7A7A;">Source: NTSB Initial Findings, June 4, 2026</text></svg>
```

The NTSB's June 4 release covers initial findings only. A final report with probable cause and any safety recommendations will follow once the full investigation concludes. The agency has not yet published a timeline for that determination.
```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebSite",
      "@id": "https://bytepith.com/#website",
      "url": "https://bytepith.com/",
      "name": "BytePith"
    },
    {
      "@type": "Organization",
      "@id": "https://bytepith.com/#organization",
      "name": "BytePith",
      "url": "https://bytepith.com/",
      "logo": {
        "@type": "ImageObject",
        "url": "https://bytepith.com/logo.png"
      },
      "sameAs": [
        "https://x.com/bytepith",
        "https://linkedin.com/company/bytepith"
      ]
    },
    {
      "@type": "WebPage",
      "@id": "https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report#webpage",
      "url": "https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report",
      "name": "United Flight 169 Newark Close Call: NTSB Report",
      "isPartOf": {
        "@id": "https://bytepith.com/#website"
      },
      "breadcrumb": {
        "@id": "https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report#breadcrumb"
      },
      "mainEntity": {
        "@id": "https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report#article"
      }
    },
    {
      "@type": "NewsArticle",
      "@id": "https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report#article",
      "isPartOf": {
        "@id": "https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report#webpage"
      },
      "headline": "United Flight 169 Newark Close Call: NTSB Report",
      "description": "New NTSB findings show United Airlines Flight 169 flew just 15 feet above the New Jersey Turnpike on May 3, 2026, after multiple runway changes and manual flight compounded approach errors.",
      "image": "https://bytepith.com/uploads/1780667566941-Copilot_of_United_jet_that_struck_a_light_pole_realized_flight_was_low__but_not_in_time__report_says.webp",
      "datePublished": "2026-06-05T13:52:48Z",
      "dateModified": "2026-06-05T13:52:48Z",
      "author": {
        "@type": "Person",
        "@id": "https://bytepith.com/author/446649374831804416#person",
        "name": "Hana Than",
        "url": "https://bytepith.com/author/446649374831804416",
        "jobTitle": "Senior Lifestyle Editor, Travel Journalist & Sports Correspondent",
        "image": "https://api.bytepith.com/uploads/1779020707826-861d76ccdbd75a8903c6.webp",
        "sameAs": [
          "https://x.com/hanathan1410",
          "https://github.com/hanathan14",
          "https://www.linkedin.com/in/thanthimyhanh"
        ]
      },
      "publisher": {
        "@id": "https://bytepith.com/#organization"
      },
      "mainEntityOfPage": {
        "@id": "https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report#webpage"
      }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://bytepith.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Travel",
          "item": "https://bytepith.com/topic/travel"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "United Flight 169 Newark Close Call: NTSB Report",
          "item": "https://bytepith.com/article/united-flight-169-newark-close-call-ntsb-report"
        }
      ]
    }
  ]
}
```