Connect with us

Regulations & Safety

NTSB Preliminary Report on Fatal LaGuardia Runway Collision

NTSB’s preliminary report details the 2026 LaGuardia runway collision involving Air Canada Express and a firefighting vehicle, citing communication and system failures.

Published

on

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

NTSB Releases Preliminary Findings on Fatal LaGuardia Runway Collision

The National Transportation Safety Board (NTSB) has issued its preliminary report regarding the tragic runway collision that occurred at New York’s LaGuardia Airport (LGA) on Sunday, March 22, 2026. We have reviewed the agency’s initial findings, which detail the sequence of events leading to the crash between a passenger jet and an airport firefighting vehicle. The collision resulted in the deaths of two pilots and injuries to 41 other individuals, marking the first fatal aviation accident at LaGuardia in 34 years.

According to the NTSB preliminary report (Investigation ID: DCA26MA161), the incident took place at approximately 11:37 p.m. local time. A 20-year-old Bombardier CRJ-900LR, registered as C-GNJZ and operated by Jazz Aviation on behalf of Air Canada Express, was completing Flight 8646 from Montreal–Trudeau International Airport (YUL). The Commercial-Aircraft, carrying 72 passengers and four crew members, collided with an Oshkosh Striker 1500 airport firefighting truck operated by the Port Authority of New York and New Jersey.

The preliminary findings point to a complex chain of systemic issues, including overlapping air traffic control (ATC) communications, the absence of a transponder on the emergency vehicle, and critical failures in the airport’s surface detection systems. While the NTSB does not assign probable cause in preliminary reports, the documented facts provide a clear timeline of the technological and human factors involved.

The Collision Sequence and Communication Breakdown

Divergent Clearances and Radio Frequencies

The NTSB report outlines that the firefighting vehicle, identified as Truck 1 or Truck 35, was leading a convoy of six emergency vehicles. They were responding to an unrelated incident involving a United Airlines Boeing 737 MAX 8, which had reported a cabin odor following two aborted takeoffs. As the convoy mobilized, the Air Canada Express CRJ-900 was cleared to land on Runway 4.

Simultaneously, an air traffic controller cleared the fire truck to cross the same runway at the Taxiway Delta intersection. According to the NTSB timeline, this crossing clearance was issued just 12 to 20 seconds before the aircraft touched down. A critical factor identified in the report is that the aircraft and the emergency convoy were operating on different radio frequencies. Consequently, neither the flight crew nor the fire truck operators heard the conflicting clearances.

The Final Seconds

Upon realizing the impending conflict, the air traffic controller attempted to halt the fire truck. The NTSB report notes that the controller issued rapid, frantic commands over the radio.

“stop, stop, stop, Truck 1 stop”

According to the Investigation, the fire truck’s turret operator heard the initial commands but did not immediately recognize that they were directed at his specific vehicle. By the time the operator realized the command was meant for them and spotted the approaching aircraft’s lights, the truck had already entered the runway. The CRJ-900, traveling at an estimated approach speed of 114 knots (131 mph), struck the side of the firefighting vehicle.

Casualties and Emergency Response

Impact and Fatalities

The high-speed impact destroyed the forward galley and cockpit of the CRJ-900. The NTSB confirmed that both pilots were killed instantly in the collision: Captain Antoine Forest, 24, and First Officer Mackenzie Gunther, 30.

Injuries and Rescue Operations

In addition to the fatalities, 41 people sustained injuries and were transported to local hospitals. This included 39 passengers and crew members from the aircraft, as well as the two occupants of the fire truck. The NTSB report highlights the severe injuries of a flight attendant who was seated in a forward jump seat; she was ejected from the aircraft onto the tarmac, surviving with shattered legs and a fractured spine.

Because the fire truck was already part of an active emergency convoy, rescue crews were immediately present at the scene. Officials cited in the report credit this immediate proximity with preventing further loss of life among the aircraft’s passengers.

Key Findings from the NTSB Preliminary Report

ASDE-X and Transponder Failures

A significant portion of the NTSB’s preliminary report focuses on the failure of LaGuardia’s Airport Surface Detection Equipment, Model X (ASDE-X). This system is specifically designed to track ground movements and alert tower controllers to potential collisions. However, the system failed to generate any audio or visual alerts prior to the crash.

The investigation revealed that the ASDE-X system failed to alert because the fire truck was not equipped with a transponder. Without an active transponder, the large emergency vehicle was virtually invisible to the airport’s automated proximity warning system. NTSB Chair Jennifer Homendy emphasized in public remarks that controllers must be equipped with the proper tools and accurate information to maintain Safety.

Runway Entrance Lights and Environmental Factors

The NTSB also examined the runway entrance lights, which function as stoplights for crossing ground traffic. The report indicates these lights remained illuminated until approximately three seconds before the collision. The system is designed to extinguish these lights two to three seconds before an aircraft reaches an intersection, a margin that proved entirely insufficient to prevent the accident.

Environmental and staffing factors further compounded the situation. Weather conditions at the time included moderate winds (050 degrees at 7 knots), broken ceilings at 9,000 feet, and roughly 4 miles of visibility in mist and rain. These nighttime, low-visibility conditions likely hindered the pilots’ ability to spot the dark-colored fire truck. Furthermore, the NTSB noted that LaGuardia’s ATC was operating with 33 controllers that night, falling short of the airport’s staffing target of 37.

AirPro News analysis

The preliminary findings from the NTSB illustrate a classic “Swiss cheese model” of accident causation, where multiple layers of defense fail simultaneously. The most glaring systemic vulnerability highlighted in this report is the operation of an active emergency vehicle within the Airport Operations Area (AOA) without a transponder. While ASDE-X is a robust system, its reliance on transponder data means it is only as effective as the equipment installed on ground vehicles. We anticipate that the FAA and airport authorities nationwide will not wait for the NTSB’s final report to mandate transponder usage for all critical ARFF vehicles. Additionally, the documented ATC staffing shortage, operating with 33 controllers instead of the targeted 37, underscores a persistent, nationwide vulnerability in air traffic infrastructure that continues to erode safety margins during high-stress, low-visibility operations.

Frequently Asked Questions (FAQ)

What is an NTSB preliminary report?

An NTSB preliminary report outlines the verified, factual information gathered in the early stages of an aviation investigation. It does not assign blame or determine the probable cause of an accident. Those conclusions are reserved for the final report.

When will the final investigation report be released?

According to the NTSB, a final report determining the probable cause and contributing factors of the March 22 collision is expected to take 12 to 24 months to complete.

What is ASDE-X?

Airport Surface Detection Equipment, Model X (ASDE-X) is a surveillance system used at major Airports to track the surface movement of aircraft and vehicles. It uses radar, satellite data, and transponder signals to warn air traffic controllers of potential ground collisions.

Sources: National Transportation Safety Board (NTSB)

Photo Credit: Reuters

Continue Reading
Click to comment

Leave a Reply

Regulations & Safety

Cessna 172S Crashes in Pacoima Near Whiteman Airport

A Cessna 172S crashed upside-down in Pacoima, CA, causing power outages and evacuations. Pilot hospitalized; FAA and NTSB investigating.

Published

on

This article summarizes reporting by NBC Los Angeles and Jonathan Lloyd, supplemented by comprehensive incident research data.

A small single-engine airplane crashed upside-down into a commercial auto parts store parking lot in Pacoima, California, on Monday morning. The incident downed high-voltage power lines and prompted immediate emergency responses, though it miraculously spared bystanders and parked vehicles.

The crash occurred just blocks from Whiteman Airport, a general aviation facility that has been the subject of intense community scrutiny following a series of aviation accidents in recent years. The sole occupant of the aircraft, a 70-year-old male pilot, survived the impact and was hospitalized.

According to initial reporting by NBC Los Angeles, the Los Angeles Fire Department (LAFD) responded to the downed plane near the intersection of Ralston Avenue and Van Nuys Boulevard, where they encountered significant electrical hazards caused by the damaged infrastructure.

Details of the Pacoima Crash and Emergency Response

The Aircraft and the Pilot

Incident research reports identify the aircraft as a 2007 Cessna 172S Skyhawk, which is reportedly registered to a local flight school. The crash was reported to authorities at approximately 11:08 a.m. local time on Monday, April 20, 2026. The plane came to rest inverted in the parking lot of an O’Reilly Auto Parts store located on the 10800 block of N. San Fernando Road, sustaining heavy damage to its nose.

First responders from the LAFD and the Los Angeles Police Department (LAPD) arrived swiftly to find the 70-year-old pilot trapped inside the wreckage. Crews successfully extricated the man, who was able to speak with responders at the scene. He was transported to a local hospital and is reported to be in critical but stable condition.

Public Safety Measures

NBC Los Angeles reported that high-voltage power lines were damaged during the incident. Research data confirms that the aircraft snapped a power pole upon descent. Due to the severe electrical hazard, police and fire crews shut down Van Nuys Boulevard from Ralston Avenue to San Fernando Road.

Authorities also initiated temporary evacuations of nearby businesses and residences as a safety precaution while utility crews worked to neutralize the downed lines. Fortunately, the aircraft did not strike any bystanders or parked cars during its descent.

The Shadow of Whiteman Airport

A History of Aviation Incidents

This latest crash contextualizes ongoing safety concerns regarding Whiteman Airport (WHP), located just a short distance from the crash site. The airport caters to general aviation, hobbyists, and flight schools, but its placement within a densely populated San Fernando Valley neighborhood has made it a flashpoint for controversy.

Over the past decade, the area has seen over a dozen crashes associated with the airport. Historical incident data highlights several severe accidents, including a fatal November 2020 crash of a Cessna 182 into a residential street, a dramatic January 2022 incident where a Cessna 172 lost power and was struck by a Metrolink train, and a fatal April 2022 crash of a Cessna Skymaster near the 210 Freeway.

Political and Community Pushback

Following previous crashes, local residents and community advocacy groups, such as Pacoima Beautiful, have mounted heavy pressure to close the 1940s-era airport. Elected officials, including U.S. Representative Tony Cárdenas and L.A. City Councilmember Monica Rodriguez, have been vocal critics of the facility’s safety record.

“The surrounding community is literally afraid for their lives. There are way too many crashes coming in and out of Whiteman Airport.”
, U.S. Representative Tony Cárdenas, in previous public statements regarding the airport.

The Los Angeles County Board of Supervisors previously approved a $1.9 million study to explore alternative land uses for the 184-acre airport property. However, aviation advocates maintain that the airport provides local jobs, serves as a crucial emergency hub, and is protected by federal grant obligations.

Looking Ahead: Investigations and Airport Future

AirPro News analysis

We anticipate that the Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) will lead the official investigation into Monday’s crash to determine the exact cause. Given that the Cessna is reportedly registered to a local flight school, investigators will likely scrutinize the school’s maintenance protocols, aircraft logs, and the pilot’s training records.

Furthermore, this highly visible incident, where an airplane fell into a commercial parking lot on a Monday morning, will almost certainly accelerate political momentum against Whiteman Airport. Because the crash resulted in downed high-voltage lines and evacuations, it serves as a stark reminder of the inherent risks of operating a general aviation hub in a densely populated urban zone. We expect renewed legislative efforts and heightened community mobilization regarding the future of the 184-acre site in the coming weeks.

Frequently Asked Questions (FAQ)

  • Were there any casualties on the ground? No. Miraculously, no bystanders were injured, and no vehicles were struck when the plane crashed into the parking lot.
  • What is the condition of the pilot? The sole occupant, a 70-year-old man, was extricated by first responders and is currently in critical but stable condition.
  • What caused the plane to crash? The official cause of the crash is currently unknown. The FAA and NTSB typically lead investigations into such aviation incidents.
  • Did the crash cause power outages? The aircraft snapped a power pole and downed high-voltage power lines, prompting street closures and temporary evacuations while utility crews neutralized the hazard.

Sources: NBC Los Angeles

Photo Credit: KTLA

Continue Reading

Regulations & Safety

Southwest Airlines Jets Near-Miss at Nashville Airport on April 18

Two Southwest Airlines jets narrowly avoided a midair collision near Nashville Airport, prompting evasive action and an FAA investigation.

Published

on

This article summarizes reporting by NewsChannel 5 and Phil Williams.

Two Southwest Airlines jets narrowly avoided a midair collision near Nashville International Airport on Saturday afternoon, prompting immediate evasive maneuvers. According to reporting by NewsChannel 5, the aircraft were forced to take sudden action just north of the airport to prevent a disaster.

The incident, which occurred late Saturday, highlights ongoing concerns regarding air traffic control and runway safety. We are closely monitoring the developments as federal aviation authorities and the airline review the flight data.

Details of the Nashville Close Call

According to flight tracking data cited by aviation outlet Paddle Your Own Kanoo, the near-miss happened around 5:45 p.m. on April 18. Southwest Airlines Flight 507, arriving from Myrtle Beach, was attempting to land in gusty conditions. The pilots initiated a precautionary go-around, climbing to an altitude of 2,000 feet.

During this maneuver, air traffic controllers reportedly instructed Flight 507 to turn right. This vector placed the Boeing 737 MAX 8 directly into the departure path of Southwest Airlines Flight 1152, which was taking off for Knoxville from an adjacent runway.

Evasive Action and Safety Systems

To avoid a catastrophic impact, the crews had to react swiftly. NewsChannel 5 Investigates discovered that the two jets were forced into evasive action just north of the airfield.

“Two Southwest Airlines jets were forced to take evasive action late Saturday afternoon… to avoid a potential midair collision,” NewsChannel 5 reported.

Flight tracking data analyzed by Flightradar24 and reported by Paddle Your Own Kanoo suggests the two aircraft came within 500 feet of each other vertically. Aviation safety experts note that such incidents often trigger the Traffic Alert and Collision Avoidance System (TCAS), a critical cockpit alarm that provides pilots with last-resort instructions to climb or descend when aircraft paths converge.

AirPro News analysis

We note that this incident adds to a growing list of runway incursions and near-misses at major U.S. airports over the past two years. While the aviation system remains statistically highly safe, the frequency of these close calls has placed increased scrutiny on air traffic control staffing and pilot adherence to vector instructions. The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) will likely launch a formal investigation to determine whether controller error or weather-related miscommunication was the primary factor in Saturday’s event.

Frequently Asked Questions

When did the Southwest Airlines near-miss occur?

The incident took place late Saturday afternoon, April 18, 2026, at approximately 5:45 p.m., according to industry reports.

Which flights were involved?

The close call involved Southwest Airlines Flight 507, arriving from Myrtle Beach, and Flight 1152, departing for Knoxville.

How close did the planes get?

Flight tracking data indicates the two jets passed within 500 feet of each other vertically before safely diverging.

Sources

Photo Credit: flightradar24

Continue Reading

Regulations & Safety

Airborne Aviation Helicopter Crash Off Kauai Hawaii Investigated

NTSB reports a Hughes 369D helicopter crash off Kauai, Hawaii, with 3 fatalities and mechanical failure suspected in a sightseeing flight.

Published

on

This article is based on an official preliminary report from the National Transportation Safety Board (NTSB), supplemented by AirPro News research.

On March 26, 2026, a Hughes 369D sightseeing Helicopters operated by Airborne Aviation crashed into the ocean off the Na Pali Coast of Kauai, Hawaii. The accident, which occurred at approximately 3:39 p.m. Hawaii Standard Time (HST), resulted in three passenger fatalities and serious injuries to the pilot and one surviving passenger. The aircraft was conducting a Title 14 Code of Federal Regulations Part 135 revenue sightseeing flight.

The National Transportation Safety Board (NTSB) has released its preliminary report detailing the sequence of events. The findings point to a sudden in-flight emergency characterized by severe vibrations and a loss of directional control, prompting an emergency autorotation into the water.

As federal investigators continue to examine the recovered wreckage, the crash brings renewed attention to the Safety of air tour operations in Hawaii. The incident raises specific questions concerning “doors-off” flight profiles, over-water equipment regulations, and the mechanical reliability of aging sightseeing fleets.

Sequence of the Fatal Flight

Departure and In-Flight Emergency

According to the NTSB preliminary report, the helicopter, bearing tail number N715KV, departed Lihue Airport (LIH) at approximately 3:12 p.m. HST. It was scheduled for a local sightseeing tour, marking its sixth and final flight of the day. The flight proceeded uneventfully until it reached the northern shore of the island near Haena, roughly 20 miles northeast of the airport.

The pilot told investigators that upon reaching Kalalau Beach, he initiated a standard left turn away from the shoreline. It was during this maneuver that the aircraft experienced a severe mechanical anomaly.

“Upon entering the turn, the pilot experienced a high frequency vibration throughout the helicopter that came in waves and became stronger each time.”

, NTSB Preliminary Report

Loss of Control and Water Impact

Following the onset of the vibrations, the helicopter began an un-commanded right yaw. The NTSB notes that the pilot attempted to correct the spin using the left anti-torque pedal, but the input was ineffective. The aircraft quickly rotated clockwise, completing approximately two full rotations.

In response, the pilot entered an autorotation, rolling the throttle to idle to stop the spinning and attempting to increase airspeed for better directional control. He subsequently broadcasted a Mayday radio call. Unable to glide to the beach, the helicopter nosedived and impacted the water roughly 75 to 100 yards from the shoreline. The aircraft rolled onto its right side and became partially submerged.

Witness accounts detailed in the NTSB report corroborate the sequence. One witness flying nearby observed the helicopter impact the water and come to rest upright, tilted slightly to the right. The surviving passenger reported hearing a distinct change in the aircraft’s sound before it slowed down, rotated, and nosedived into the ocean.

Aircraft, Operator, and Rescue Efforts

Airborne Aviation and the Hughes 369D

The aircraft involved was a 1979 Hughes 369D, commonly referred to as an MD 500D, equipped with a Rolls-Royce M250 series engine. Federal Aviation Administration (FAA) records indicate the helicopter was registered to AA Leasing LP in Kilauea, Kauai. AirPro News research confirms the aircraft previously operated in Canada, where it was equipped with flotation tanks for water landings. However, it was operating its Hawaii tours without this over-water setup.

The operator, Airborne Aviation, is a Lihue-based company known for offering “doors-off” adventure tours. Following the accident, the company suspended all tour operations. Local authorities identified the three deceased passengers as Margaret Rimmler, 65; Patrick Haskell, 59; and Oksana Pihol, 40.

Emergency Response

The remote location of Kalalau Beach necessitated a rapid and complex rescue operation. According to local emergency response data, campers and Good Samaritans on the beach immediately swam out to the sinking wreckage to pull the five occupants from the water and administer aid.

A large-scale official response followed, involving the Hanalei Fire Station, the Kauai Fire Department, the U.S. Coast Guard, and the Department of Land and Natural Resources (DLNR). The two survivors were medically evacuated to Wilcox Medical Center in Lihue for treatment of serious injuries.

Investigation and Broader Context

Flight Data and Weather Conditions

The NTSB has recovered the helicopter’s fuselage and main rotor blades, which sustained substantial damage, to a secure facility for further examination. Alongside the physical wreckage, investigators will likely scrutinize flight tracking data.

Public ADS-B flight data analyzed in AirPro News research revealed unusual speed fluctuations during the fatal flight. At 3:30 p.m., the helicopter’s speed abruptly dropped from 110 knots to 30 knots at an altitude of 3,500 feet before recovering. Similar sharp slowdowns were recorded on the helicopter’s previous flights that day. Additionally, an AIRMET Tango advisory for aviation turbulence was active across the Hawaiian islands at the time of the crash.

AirPro News analysis

While weather has historically played a significant role in Hawaiian air tour accidents—such as the December 2019 Safari Helicopters crash that killed seven people in low-visibility conditions—the circumstances of the Airborne Aviation crash point strongly toward a catastrophic mechanical failure. The pilot’s description of wave-like, high-frequency vibrations and a total loss of anti-torque control is highly indicative of a failure within the tail rotor drive system.

Furthermore, this incident highlights ongoing regulatory tensions regarding over-water helicopter operations. The fact that this single-engine aircraft was conducting “doors-off” flights over the ocean without emergency pop-out floats exposes a persistent loophole in safety mandates. Despite the FAA implementing a new authorization process in 2023 for Hawaii air tour operators, the industry continues to balance the economic demands of tourism against the inherent risks of low-altitude flying over rugged, maritime terrain.

Frequently Asked Questions

What caused the Airborne Aviation helicopter crash?

The exact cause is currently under Investigation by the NTSB. However, preliminary reports indicate the pilot experienced severe vibrations and a loss of tail rotor effectiveness, suggesting a mechanical failure rather than a weather-related event.

What type of helicopter was involved?

The aircraft was a Hughes 369D, often referred to as an MD 500D, manufactured in 1979. It was operating a “doors-off” sightseeing tour at the time of the Accident.

Were there any survivors?

Yes. The pilot and one female passenger survived the crash with serious injuries and were medically evacuated to a local hospital. Three other passengers were fatally injured.

Sources

Sources: National Transportation Safety Board (NTSB), AirPro News Internal Research Report.

Photo Credit: US Coast Guard

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