Regulations & Safety
CommuteAir Flight 4339 Runway Excursion and NTSB Preliminary Findings
NTSB preliminary report on CommuteAir Flight 4339 runway overrun at Roanoke highlights crew decisions and EMAS safety role.
CommuteAir Flight 4339 Runway Excursion: A Breakdown of the NTSB Preliminary Report
On the night of September 24, 2025, CommuteAir flight 4339, operating as a United Express service, ended its journey from Washington Dulles not at the terminal, but in an engineered materials arresting system (EMAS) at Roanoke-Blacksburg Regional Airport (ROA). The Embraer EMB-145XR, carrying 50 passengers and 3 crew members, overran runway 34 during a rainy landing. Fortunately, the incident resulted in no injuries and only minor damage to the aircraft, a testament to the effectiveness of modern runway safety technology. However, the events leading up to this runway excursion, as detailed in the National Transportation Safety Board’s (NTSB) preliminary report, raise important questions about crew coordination, decision-making under pressure, and adapting to rapidly changing weather.
The flight was already under a degree of stress before it even left the ground. It was the second leg of the fourth day of a long rotation for the crew. Passengers had been deplaned twice due to maintenance issues, leading to a departure approximately two and a half hours behind schedule. While pre-flight delays are not uncommon, they can contribute to a cascading series of events. This incident serves as a critical case study for the aviation industry, highlighting the razor-thin margins that separate a routine landing from a serious incident and the layers of safety that are in place to mitigate the consequences when things go wrong.
The NTSB’s investigation is ongoing, and this initial report provides a factual, unvarnished look at the sequence of events. It lays the groundwork for a deeper analysis of operational factors, human performance, and air traffic control communications. As we dissect the available information, we get a clearer picture of the dynamic challenges the flight crew faced and the critical decisions made in the final moments of the flight. The data from the cockpit voice recorder and flight data recorder will be crucial in piecing together the complete narrative.
From Clear Skies to a Rainy Approach
The flight’s journey from Washington to Roanoke began with a weather forecast that suggested a routine arrival. The initial Automatic Terminal Information Service (ATIS) report for ROA indicated calm winds, no rain, and runway 6 in use. Based on this, the captain, who was the pilot flying, briefed for a localizer approach to that runway. The first officer, acting as pilot monitoring, proactively suggested reviewing landing performance for a wet runway, but the captain declined, citing the clear conditions reported by ATIS. This initial interaction sets the stage for a developing situation where crew communication and differing perspectives on risk would become a central theme.
As the aircraft began its descent, the weather picture changed dramatically. Approach control alerted the crew to precipitation near the airport and advised that other aircraft were now using runway 34 for landing. This prompted a change in plan. The captain requested the first officer set up and brief the ILS (Instrument Landing System) approach for runway 34, a more precise approach suitable for deteriorating weather. The crew was now actively adapting to a new set of circumstances, a standard procedure in the dynamic environment of aviation.
The situation continued to evolve rapidly on the final approach. The crew overheard a report from a preceding aircraft that mentioned marginal visibility and bumpy conditions. The rain intensified, leading the first officer to perform a landing calculation for a wet runway. The calculation showed a safety margin of about 200 feet more than required, even without the use of thrust reversers. This data point suggested the landing was feasible, but the conditions were far from the calm, dry scenario anticipated at the start of the flight.
The Final Moments: Go-Around Calls and a Captain’s Decision
The intensity of the rain increased to “heavy” on the short final, prompting the captain to request the windshield wipers be set to high speed. As the aircraft descended below 500 feet, a critical phase of flight, the first officer noted they were high on the precision approach path indicator (PAPI), a visual aid that helps pilots maintain the correct glidepath. A high indication means the aircraft is above the ideal descent profile, which can lead to touching down too far down the runway and not having enough distance to stop.
Recognizing the unstable nature of the approach, the first officer made a critical callout: “go-around.” This is a standard call for discontinuing a landing approach that is not proceeding as planned. The call was made as the aircraft crossed the runway threshold, but the captain continued with the landing. The first officer repeated the “go-around” call about halfway down the runway, but again, the captain continued the landing attempt. This divergence in crew action is a significant point of interest for the NTSB’s human factors investigation.
The NTSB report states, “After crossing the runway markings, the FO called for a go-around, but the captain continued. About halfway down the runway, the FO called for a go-around a second time, but the captain continued.”
After touchdown, the crew applied maximum braking and deployed the engine thrust reversers. Despite these actions, the aircraft could not be stopped on the remaining runway. It overran the pavement and came to a safe stop in the EMAS. The successful deployment and function of the EMAS bed prevented a potentially far more serious outcome, containing the aircraft and protecting everyone on board. Following the event, airport rescue and firefighting personnel boarded the aircraft and assisted passengers in evacuating via a ladder.
The Investigation and the Role of Safety Systems
The NTSB is leading a comprehensive investigation into the incident, with participation from the Federal Aviation Administration (FAA), CommuteAir, the Air Line Pilots Association (ALPA), and Brazilian authorities, as the aircraft was manufactured by Embraer. Specialists in various fields, including flight recorders, meteorology, air traffic control, and human factors, have been assigned to the case. The cockpit voice and flight data recorders were recovered and sent to the NTSB’s lab in Washington, D.C., for detailed analysis. The data from these recorders will provide investigators with precise details about the aircraft’s parameters, crew conversations, and actions throughout the flight.
A key takeaway from this incident is the undeniable success of the Engineered Materials Arresting System (EMAS). This technology, installed at the end of runways where safety areas are limited, is designed to crush under the weight of an aircraft, decelerating it safely. The images from the report show the aircraft’s main landing gear embedded in the EMAS, illustrating exactly how the system is designed to work. This event serves as a powerful, real-world example of how investment in runway safety infrastructure pays dividends by preventing injuries and major aircraft damage.
The investigation will undoubtedly focus heavily on Crew Resource Management (CRM). CRM is the practice of using all available resources, both human and technological, to ensure safe and efficient flight operations. The differing actions of the captain and first officer in the final moments of the landing will be scrutinized. Investigators will seek to understand the decision-making process, communication dynamics, and any potential factors that may have influenced the captain’s choice to continue the landing despite the first officer’s calls to go around. The findings will likely contribute to ongoing training and procedural refinements across the airline industry.
Concluding Thoughts
The runway excursion of CommuteAir flight 4339 is a stark reminder of the complexities of commercial aviation. It underscores how quickly a routine flight can encounter unforeseen challenges, demanding rapid and accurate decision-making from the flight crew. The preliminary NTSB report provides a factual, dispassionate account of the events, laying the groundwork for a thorough investigation that will ultimately aim to enhance aviation safety for everyone.
While the absence of injuries is a relief, the incident highlights critical areas for review, particularly concerning crew coordination in unstabilized approaches and the persistent challenge of landing in rapidly deteriorating weather. The successful outcome, in terms of passenger and crew safety, can be directly attributed to the effectiveness of the EMAS, reinforcing the importance of such safety systems. The final NTSB report will provide the industry with valuable lessons to prevent similar occurrences in the future.
FAQ
Question: What is a runway excursion?
Answer: A runway excursion is an incident where an aircraft veers off or overruns the runway surface. This can occur during takeoff or landing and can be caused by various factors, including unstable approaches, contaminated runways (with water, ice, or snow), mechanical issues, or pilot error.
Question: What is an EMAS?
Answer: EMAS stands for Engineered Materials Arresting System. It is a bed of crushable, energy-absorbing material placed at the end of a runway. When an aircraft overruns the runway, the EMAS collapses under the weight of the aircraft’s tires, safely decelerating it and preventing it from causing more significant damage or injuries.
Question: Why did the first officer call for a “go-around”?
Answer: A “go-around” is a standard procedure where a landing is aborted. Pilots are trained to initiate a go-around if the approach is not “stabilized”, meaning the aircraft is not at the correct speed, descent rate, or on the correct flight path. In this case, the first officer observed the aircraft was too high on the approach path and called for a go-around to discontinue the unstable landing attempt.
Sources
Photo Credit: X
Regulations & Safety
Airborne and Partners Develop ADS-B In Retrofit for Boeing 757 and 767
Airborne, Innovative Aerosystems, and ACSS collaborate on ADS-B In retrofit for Boeing 757 and 767 to meet ALERT Act mandates by 2031.
This article is based on an official press release from Airborne Maintenance & Engineering Services.
Airborne Maintenance & Engineering Services, a subsidiary of Air Transport Services Group (ATSG), announced a strategic Partnerships on April 20, 2026, with Innovative Aerosystems (IA) and Aviation Communication & Surveillance Systems (ACSS). The coalition aims to develop and certify an ADS-B In retrofit solution specifically designed for Boeing 757 and 767 aircraft, with an expected entry into service in early 2027.
According to the official press release, this initiative arrives at a critical juncture for aviation safety and regulatory compliance. Just days prior to the announcement, on April 14, 2026, the U.S. House of Representatives overwhelmingly passed the Airspace Location and Enhanced Risk Transparency (ALERT) Act. This sweeping aviation safety bill mandates the implementation of ADS-B In technology across the industry by December 31, 2031.
We note that this retrofit program represents a proactive industry response to impending federal mandates. It offers operators of legacy Boeing 757 and 767 fleets a cost-effective pathway to modernize their flight decks, ensuring compliance with future airspace requirements while enhancing operational efficiency.
The Regulatory Catalyst and the ALERT Act
Tragic Origins and Legislative Action
The legislative push for ADS-B In technology gained intense momentum following a tragic midair collision on January 29, 2025. The incident, involving a PSA Airlines CRJ700 and a U.S. Army UH-60 Black Hawk Helicopters near Ronald Reagan Washington National Airports (KDCA), resulted in 67 fatalities. Subsequent investigations by the NTSB revealed that the helicopter was not broadcasting an ADS-B signal, exposing a critical gap in cockpit situational awareness.
In direct response to the NTSB’s 50 safety recommendations, lawmakers introduced the ALERT Act. The legislation requires all aircraft currently mandated to have ADS-B Out to be equipped with ADS-B In and corresponding collision prevention technology by the end of 2031. A competing Senate bill, the ROTOR Act, pushes for a similar mandate.
“Any safety requirement that routes implementation through negotiated processes… creates opportunities for delay that cost lives. This is how modern aviation operates. ADS-B In is proven technology that can be deployed now to save lives,” stated U.S. Rep. Rob Bresnahan, Jr., co-sponsor of the ADS-B In amendment to the ALERT Act.
Technological Integration and Key Partnerships
Upgrading the Legacy Fleet
While ADS-B Out, mandated in the U.S. since 2020, broadcasts an aircraft’s position, speed, and altitude, ADS-B In allows the flight deck to receive this data from other aircraft and ground stations. This provides pilots with a real-time, 180-nautical-mile display of surrounding traffic. The retrofit program leverages the ACSS SafeRouteâ„¢ system, which includes features like Airborne Traffic Situational Awareness (AIRB), CDTI Assisted Visual Separation (CAVS/CAS), Interval Management (IM), In-Trail Procedures (ITP), and runway surface alerting (SURF-A).
Each partner brings specific expertise to the integration. Airborne will lead the aircraft integration, Supplemental Type Certificate (STC) certification, and installation. Innovative Aerosystems (IA), which rebranded from Innovative Solutions & Support in October 2025, will provide the retrofit Flat Panel Display System. ACSS, a joint venture between Acron Aviation and Thales, supplies the core SafeRouteâ„¢ software and TCAS 3000SP platform.
“This program focuses on integrating ADS-B In capabilities into existing flight deck environments with minimal disruption,” noted Mike Glover, VP of Business Development at Innovative Aerosystems, in the press release.
Operational Efficiency and Fleet Modernization
Minimizing Downtime for Cargo Operators
ATSG is the world’s largest lessor of converted Boeing 767 freighter aircraft, operating a fleet of over 114 converted Cargo-Aircraft jets. These aircraft serve as the backbone for major e-commerce logistics providers. By synchronizing the ADS-B In installation with scheduled heavy maintenance, ATSG aims to minimize aircraft downtime, a crucial factor for cargo operators relying on tight schedules.
“They need integrated capabilities that can be executed efficiently and at scale… Airborne’s technical expertise, combined with ATSG’s broader platform, allows us to deliver programs like this in a way that reduces complexity, minimizes downtime, and creates immediate and long-term value,” said Todd France, Chief Commercial Strategy Officer at ATSG.
AirPro News analysis
At AirPro News, we view this partnership as a highly strategic alignment of capabilities that addresses a “perfect storm” of safety mandates and operational efficiency. The Boeing 757 and 767 remain vital to the global e-commerce cargo network. This retrofit allows these legacy workhorses to operate in modernized, NextGen airspace without requiring operators to invest in entirely new airframes. Furthermore, while safety mandates typically introduce new costs, the fuel efficiency and optimized routing enabled by ADS-B In’s Interval Management and In-Trail Procedures offer a tangible return on investment for cargo airlines.
Frequently Asked Questions
What is the difference between ADS-B Out and ADS-B In?
ADS-B Out broadcasts an aircraft’s GPS location, speed, and altitude to air traffic control and other aircraft. ADS-B In allows an aircraft to receive this broadcasted data, providing pilots with a real-time display of surrounding air traffic and enhancing situational awareness.
When does the ADS-B In mandate take effect?
Under the ALERT Act passed by the U.S. House of Representatives on April 14, 2026, aircraft currently required to have ADS-B Out must be equipped with ADS-B In technology by December 31, 2031.
Which aircraft are covered in this specific retrofit program?
The partnership between Airborne, Innovative Aerosystems, and ACSS is specifically developing and certifying an ADS-B In retrofit solution for Boeing 757 and 767 aircraft.
Sources
Photo Credit: Aventure Aviation
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.
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.
Photo Credit: Reuters
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.
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
-
Airlines Strategy4 days agoJetBlue Secures $500M Aircraft-Backed Financing to Support Turnaround
-
Technology & Innovation5 days agoDubai Completes World’s First Commercial Vertiport at DXB Airport
-
Regulations & Safety6 days agoCirrus SR22 Safely Lands with Parachute After Power Loss in New Mexico
-
UAV & Drones6 days agoAIR’s Cargo-Heavy Lift UAS Achieves First Flight and Production Status
-
Regulations & Safety6 days agoUnauthorized Animal Noises Disrupt Emergency Aviation Frequency at Reagan Airport