Connect with us

Regulations & Safety

NTSB Reports United Airlines Flight 169 Newark Approach Incident

NTSB preliminary report details United Airlines Flight 169 striking a light pole at Newark due to low airspeed and gusty winds during approach.

Published

on

This article is based on an official press release from the National Transportation Safety Board (NTSB).

On June 4, 2026, the National Transportation Safety Board (NTSB) released its preliminary report detailing the May 3 accident involving United Airlines Flight 169 at Newark Liberty International Airport (EWR). The incident highlights the operational challenges of landing heavy widebody aircraft during gusty conditions on constrained runways.

The Boeing 767-400ER, arriving from Venice, Italy, struck a light pole on the New Jersey Turnpike while on short final approach. According to the NTSB’s factual findings, the aircraft crossed the busy highway at an altitude of just 19 feet above the ground after its airspeed decayed during the descent.

The collision caused substantial damage to the aircraft and resulted in minor injuries to a commercial truck driver on the ground. The NTSB has officially classified the event as an accident, prompting immediate safety reviews and procedural updates from the airline.

Flight Details and the Approach

According to the NTSB preliminary report (DCA26FA194), United Airlines Flight 169 was operating from Venice Marco Polo Airport to Newark on May 3, 2026. The 23-year-old Boeing 767-424ER (registration N77066) was carrying 231 individuals, comprising 220 passengers, three flight crew members, and eight cabin crew members.

The flight proceeded normally until the descent phase. The NTSB notes that the flight crew initially planned to land on Runway 4R. However, air traffic control changed the runway assignment twice due to challenging weather conditions. Winds were reported at 19 knots and gusting up to 30 knots, leading controllers to ultimately clear the aircraft for Runway 29.

Cockpit Dynamics and Warnings

The NTSB report provides critical insight into the cockpit environment during the final moments of the flight. The captain was the pilot flying, while the first officer monitored the flight instruments.

As the aircraft descended toward the runway, its airspeed began to decay. The first officer issued verbal warnings to the captain regarding the aircraft’s energy state.

“hey you are slow… you are still slow and a little low”

According to the NTSB, the captain acknowledged hearing the “airspeed slow” callout but stated he felt the airplane remained in a safe position to continue the landing.

The Collision and Aftermath

The decaying airspeed and low glide path culminated in the aircraft crossing the New Jersey Turnpike at an altitude of just 19 feet above the ground. During this low pass, the aircraft’s landing gear and underside struck a light pole located on the highway.

The NTSB report states that the captain recalled hearing a “thump” just before touchdown, while the first officer felt a “mild jolt” as they neared the runway threshold. Despite the impact, the Boeing 767 landed safely and taxied to the gate under its own power.

Ground Impact and Injuries

Debris from the severed light pole fell onto the southbound lanes of the turnpike, striking a commercial tractor-trailer operated by Baltimore-based H&S Bakery, as well as a Jeep traveling on the highway.

While no passengers or crew members on the aircraft were harmed, the NTSB confirmed that the truck driver, Warren Boardley, sustained minor injuries from shattered glass. He was treated at a local hospital and subsequently released. The truck sustained damage to its windshield and aluminum siding.

Post-flight inspections of the Boeing 767 revealed substantial damage, including three punctures on the fuselage and slash marks on one of the landing gear tires. This damage led the NTSB to officially classify the event as an accident.

Industry Response and Safety Measures

Following the accident, United Airlines took immediate administrative and procedural actions. The airline removed the involved flight crew from service pending an internal safety review.

Furthermore, United Flight Operations issued an Operations Alert to its pilots regarding arrivals at EWR’s Runway 29. The alert emphasized the importance of relying on visual glideslope indicators (VGSI/PAPI) to ensure safe obstruction clearance. A subsequent Pilot Bulletin was also issued regarding short runway landing guidance.

AirPro News analysis

We note that Runway 29 is the shortest runway at Newark Liberty International Airport, measuring 6,725 feet. It features a displaced threshold designed specifically to provide a safety buffer from the adjacent, highly congested Interstate 95. Aircraft landing on this runway routinely pass at low altitudes over the highway.

Aviation analysts frequently point out that the Boeing 767-400ER’s extended fuselage can create visual illusions for pilots during the landing flare. Because the pilot’s eye level sits high in the cockpit while the main landing gear hangs significantly lower, precise glide path management is absolutely critical to ensure obstacle clearance. The combination of gusty winds, a late runway change, and the specific ergonomics of the 767 likely compounded the difficulty of this approach.

Frequently Asked Questions (FAQ)

Was anyone injured in the United Airlines Flight 169 accident?
No passengers or crew members on the aircraft were injured. However, a truck driver on the New Jersey Turnpike sustained minor injuries from shattered glass when debris from a struck light pole hit his vehicle.

What caused the aircraft to fly so low?
The NTSB’s preliminary report indicates that the aircraft’s airspeed decayed during a gusty approach, leading to a low glide path. The first officer warned the captain that they were “slow and a little low.” The investigation is still ongoing to determine the official probable cause.

What is the current status of the investigation?
The NTSB has released its preliminary report (DCA26FA194) and officially classified the event as an accident due to substantial aircraft damage. A final report detailing the probable cause will be released at a later date.

Sources: National Transportation Safety Board (NTSB)

Photo Credit: NTSB

Continue Reading
Click to comment

Leave a Reply

Regulations & Safety

Missouri Skydive Plane Crash Kills 12 at Butler Airport

A Pacific Aerospace 750XL crashed after takeoff from Butler Memorial Airport on June 14, 2026, killing a pilot and 11 skydivers.

Published

on

This is a developing story. Information may change as official details are released.

This article summarizes reporting by CBS News, The Washington Post, SFGATE, KEYT, and Fox 10 Phoenix.

A Pacific Aerospace 750XL operated by Skydive Kansas City crashed shortly after takeoff from Butler Memorial Airport (BUM) on June 14, 2026, resulting in 12 fatalities.

The Missouri State Highway Patrol confirmed that the pilot and 11 skydivers died when the single-engine turboprop impacted a field adjacent to the airport and caught fire. The NTSB and the FAA have deployed investigators to the site, located approximately 65 miles south of Kansas City.

Accident sequence and emergency response

The aircraft departed BUM at approximately 11:20 a.m. local time. According to preliminary reports cited by SFGATE, the aircraft made a left turn shortly after takeoff. Emergency responders received a 911 call around 11:30 a.m. reporting that the aircraft had crashed into a field approximately 300 yards from the runway and was engulfed in flames.

Dennis Jacobs, acting airport manager and Bates County Emergency Management Agency director, told reporters that the aircraft appeared to lose power before stalling and impacting the ground nose first. The NTSB has not yet verified this sequence of events, and the official cause of the accident remains under investigation.

The Missouri State Highway Patrol, alongside the Butler Police Department and Bates County Sheriff’s Office, secured the scene. A statement from the highway patrol confirmed that all 12 occupants perished in the crash. The identities of the victims are being withheld pending family notification.

Aircraft and operator background

The aircraft involved was a Pacific Aerospace 750XL manufactured in 2010. The 750XL is a single-engine turboprop frequently utilized in commercial skydiving operations due to its climb rate and payload capacity. The flight was operated by Skydive Kansas City, a commercial skydiving center based at BUM.

This accident follows a previous skydiving-related aviation occurrence near the same airport. On May 25, 2024, a Cessna U206C experienced an in-flight emergency near BUM. In that incident, the pilot and six skydivers successfully evacuated the aircraft via parachute before it crashed into a hayfield, resulting in no fatalities.

AirPro News analysis

We note that the NTSB investigation will likely focus on engine performance, weight and balance, and environmental factors at the time of departure. The Pacific Aerospace 750XL is a specialized utility aircraft, and investigators will examine maintenance records and the operator’s procedures as part of their standard protocol. Until the NTSB releases its preliminary report, usually within 30 days, any statements regarding a loss of power remain unconfirmed eyewitness observations.

Sources: CBS News

Photo Credit: NZAero

Continue Reading

Regulations & Safety

FAA Investigates Southwest Airlines Near Miss at Nashville

Two Southwest Boeing 737s came within 500 vertical feet near Nashville on April 18, 2026, after an ATC error during a go-around.

Published

on

This is a developing story. Information may change as official details are released.

This article summarizes reporting by CNN, Fox News, and The Washington Post.

Two Southwest Airlines (WN) Boeing 737 aircraft passed within 500 vertical feet of each other near Nashville International Airport (BNA) on April 18, 2026, after air traffic control instructions placed an aborting arrival into the path of a departing flight.

The incident, which occurred at approximately 5:30 p.m. local time, prompted both flight crews to execute evasive maneuvers following onboard Traffic Collision Avoidance System (TCAS) alerts. The Federal Aviation Administration (FAA) has launched an investigation into the airspace separation loss, which highlights ongoing scrutiny over air traffic control protocols and collision avoidance effectiveness.

Sequence of events and evasive maneuvers

According to statements provided to CNN and Fox News, Southwest Airlines Flight 507 was arriving from Myrtle Beach, South Carolina, when the flight crew initiated a precautionary go-around due to gusty wind conditions at BNA. During this maneuver, air traffic controllers instructed the crew to turn right.

The FAA confirmed in a statement that these instructions placed Flight 507 directly into the departure path of Southwest Airlines Flight 1152, which was taking off from a parallel runway bound for Knoxville, Tennessee. As the aircraft converged, TCAS resolution advisories activated in both cockpits. Flight tracking data from Flightradar24 indicates the two Boeing 737s came within 500 vertical feet of one another before the crews successfully altered their trajectories.

Both aircraft continued to safe landings without further incident. Flight 507 completed its arrival into Nashville on a subsequent approach, while Flight 1152 proceeded to its destination in Knoxville.

Regulatory investigation and safety context

The FAA is currently investigating the circumstances that led to the loss of separation. Southwest Airlines issued a statement emphasizing that the pilots of Flight 507 were complying with air traffic control directives when the conflict occurred, and that the crews responded professionally to the onboard traffic alerts to maintain safety.

The Nashville incident occurs against a backdrop of heightened national attention on mid-air collision risks. The Washington Post notes that aviation safety systems have faced intense public and regulatory scrutiny following a January 29, 2025, collision between an American Airlines aircraft and a military helicopter near Washington, D.C., which resulted in 67 fatalities. While the circumstances of the two events differ, the 2025 accident has amplified focus on the reliability of TCAS and air traffic control coordination in congested airspace.

AirPro News analysis

The activation of TCAS resolution advisories in this incident demonstrates the critical role of automated safety nets when procedural separation fails. While the FAA investigation will ultimately determine the root cause of the controller instructions, the event underscores the vulnerability of the go-around phase. Go-arounds are dynamic maneuvers that rapidly alter an aircraft’s energy state and expected flight path. These maneuvers require immediate and precise coordination between the flight deck and air traffic control, particularly when parallel runway operations are active.

Sources: CNN (via KESQ)

Photo Credit: Flightradar24 – Google Earth via CNN Newsource

Continue Reading

Regulations & Safety

FAA Investigates Southwest Airlines Ground Collision at PVD

Two Southwest Boeing 737s collided during pushback at Rhode Island T.F. Green Airport on June 11, 2026. FAA investigation opened.

Published

on

This is a developing story. Information may change as official details are released.

This article summarizes reporting by WPRI, NBC 10, Daily Voice, and CBS News Baltimore.

The Federal Aviation Administration (FAA) has opened an investigation after two Southwest Airlines Boeing 737 aircraft collided during pushback at Rhode Island T.F. Green International Airport (PVD) late on June 11, 2026.

The ground collision resulted in no reported injuries but forced the cancellation of both flights and the grounding of the involved aircraft for mandatory safety inspections. According to reporting by the Daily Voice and NBC 10, the incident highlights ongoing operational challenges on airport ramps, occurring just weeks after a similar event involving the same carrier at another East Coast facility.

Details of the ground collision

At approximately 10:45 p.m. local time, Southwest Airlines Flight 3515, bound for Ronald Reagan Washington National Airport (DCA), was pushing back from its gate. During the maneuver, the aircraft’s wing made contact with the tail of Southwest Airlines Flight 3409, which was scheduled to depart for Chicago Midway International Airport (MDW).

Both aircraft returned to their respective gates following the contact, allowing passengers to deplane normally. Southwest Airlines confirmed that no injuries occurred among passengers or crew members. The carrier subsequently canceled both flights and reaccommodated the affected travelers.

“Southwest Airlines is aware of an incident involving two of our aircraft at Rhode Island T. F. Green International Airport. We are investigating further and will be thoroughly inspecting the two aircraft,”

the airline stated in remarks provided to local media, adding that safety remains its highest priority.

Local media outlets, including NBC 10, reported passenger accounts suggesting that Flight 3515 continued to move briefly after the initial impact. These accounts claim passengers verbally alerted the flight crew to the collision. Neither Southwest Airlines nor the FAA has officially verified these specific passenger narratives, and the official sequence of events remains under investigation.

Regulatory response and recent precedent

The FAA confirmed on June 12, 2026, that it is investigating the circumstances surrounding the collision. Ground operations during pushback rely heavily on coordination between flight crews and ground personnel, particularly in ramp areas where air traffic controllers do not maintain direct communication with the aircraft.

This event follows a comparable occurrence on May 4, 2026, at Baltimore/Washington International Thurgood Marshall Airport (BWI). In that instance, two Southwest Airlines Boeing 737s clipped wings during pushback operations. The FAA investigated the BWI incident, noting the specific communication dynamics between ground crews and the flight deck in non-controlled ramp sectors.

AirPro News analysis

We note that while ground collisions during pushback rarely pose a severe threat to passenger safety, they represent a significant operational and financial burden for carriers. Ramp incidents require immediate grounding of the involved airframes, triggering mandatory structural inspections and potential repairs. The recurrence of pushback-related contact within a single airline’s network over a short period may prompt internal reviews of ground handling procedures, wingwalker positioning, and ramp communication protocols. Until the FAA concludes its investigation, the specific cause of the PVD collision remains undetermined.

Sources: WPRI

Photo Credit: Zachary Reis

Continue Reading
Every coffee directly supports the work behind the headlines.

Support AirPro News!

Advertisement

Follow Us

newsletter

Latest

Categories

Tags

Every coffee directly supports the work behind the headlines.

Support AirPro News!

Popular News