Regulations & Safety
NTSB Preliminary Report on Alaska Airlines Flight 2616 Bird Strike Accident
NTSB details January 2026 bird strike on Alaska Airlines flight 2616 causing engine damage and safe emergency return to CVG airport.

The National Transportation Safety Board (NTSB) has released its preliminary report detailing a significant bird strike event involving an Alaska Airlines cargo flight operated on behalf of Amazon Air. The incident, which occurred on January 28, 2026, resulted in substantial damage to an Airbus A330-300 freighter and the presence of smoke in the cockpit, prompting an emergency return to Cincinnati/Northern Kentucky International Airport (CVG).
According to the NTSB’s findings, the flight crew successfully managed a high-workload emergency immediately after takeoff. Despite the severity of the engine damage and the hazardous environment within the flight deck, both crew members survived without injury. The investigation has formally classified the event as an “accident,” a designation reserved for occurrences involving serious injury or substantial structural damage to the aircraft.
The release of this preliminary report sheds light on the specific sequence of events that turned a routine cargo run into a major safety investigation. It also clarifies the complex operational structure behind the flight, which carried an Alaska Airlines flight number but utilized an aircraft and livery associated with Amazon Air and the recently acquired Hawaiian Airlines fleet.
Sequence of Events: From Takeoff to Emergency Landing
On the afternoon of January 28, 2026, Alaska Airlines flight 2616 (AS2616) departed CVG at approximately 3:05 PM EST, bound for Houston George Bush Intercontinental Airport (IAH). The aircraft, an Airbus A330-300 freighter registered as N5827K, was occupied by two crew members: a Captain and a First Officer.
The NTSB report indicates that the flight proceeded normally through its initial takeoff roll from Runway 27. However, the situation deteriorated rapidly during the initial climb. At an altitude of approximately 3,000 feet, the aircraft encountered a flock of birds. The preliminary data confirms that multiple birds were ingested into the No. 1 (left) engine.
Immediate Impact and Cockpit Environment
The ingestion caused an immediate loss of thrust and severe vibrations in the left engine. The crew received fire indications for the engine, complicating the emergency. More critically, the report notes that smoke began to fill the flight deck shortly after the strike. This development forced the pilots to don supplemental oxygen masks while managing the aircraft’s energy and trajectory.
Declaring a “Mayday,” the crew coordinated with Air Traffic Control (ATC) for an immediate return. ATC vectored the heavy freighter for a visual approach to Runway 36R. The NTSB highlighted the effective coordination between the pilots and controllers, which facilitated a swift return. The aircraft touched down safely at approximately 3:13 PM EST, just 8 to 10 minutes after departure.
Damage Assessment and Evacuation Decisions
Upon landing, the crew made a critical safety decision regarding evacuation. Rather than deploying emergency slides, which could have placed them in proximity to the engine fire or hot brakes, the pilots brought the aircraft to a stop on the runway. They requested a ladder from the airport’s Crash Fire Rescue (CFR) services and evacuated via the right-side door, deliberately avoiding the hazards on the left side of the aircraft.
The NTSB’s post-accident inspection revealed why the event was classified as an accident rather than a standard incident. The No. 1 engine and its surrounding structure sustained “substantial damage.” While modern turbofan engines are designed to contain broken fan blades, the severity of this strike caused damage significant enough to warrant the higher classification.
“The NTSB rated the occurrence as an ‘accident’ rather than an ‘incident,’ a classification reserved for events involving substantial aircraft damage or serious injury.”
The aircraft, N5827K, remains grounded at CVG as technical teams assess the full extent of the structural compromise and the NTSB continues its investigation. Future phases of the inquiry will likely utilize DNA analysis of the organic remains (“snarge”) to identify the bird species and further evaluate the performance of the engine’s containment systems.
Operational Context: The Alaska-Hawaiian-Amazon Connection
To the casual observer, the flight details might appear contradictory: an Alaska Airlines flight number, an Amazon Air paint scheme, and an Airbus A330 aircraft, a type not historically flown by Alaska Airlines. This complexity is a result of the recent merger between Alaska Air Group and Hawaiian Airlines.
Hawaiian Airlines has operated a fleet of Airbus A330-300 freighters for Amazon since 2019. Following Alaska Airlines’ acquisition of Hawaiian, these operations have been brought under the single Alaska Air Group umbrella. Consequently, while the metal and the mission belong to the legacy Hawaiian/Amazon contract, the flight operated under an “AS” code. This incident highlights the operational integration currently underway between the two carriers.
AirPro News Analysis
Crew Resource Management (CRM) Under Pressure
The successful outcome of flight AS2616 serves as a textbook example of effective Crew Resource Management (CRM). Bird strikes are common, but strikes resulting in engine fires and cockpit smoke are rare and highly dangerous. The presence of smoke introduces a physiological threat and obscures vision, significantly increasing the stress load.
We believe the crew’s decision to forego a slide evacuation in favor of a ladder egress is particularly noteworthy. In the heat of the moment, the “standard” reaction might be to blow the slides and get out immediately. However, the pilots assessed the specific threat, fire on the left side, and chose a controlled exit on the right side with ground support. This disciplined decision-making likely prevented secondary injuries during the evacuation phase.
Frequently Asked Questions
Why was this classified as an accident?
The NTSB defines an “accident” as an occurrence associated with the operation of an aircraft where a person suffers death or serious injury, or in which the aircraft receives substantial damage. In this case, the damage to the engine and airframe met the threshold for “substantial damage.”
Was anyone injured?
No. Both crew members evacuated safely without injury.
What happens next in the investigation?
The NTSB will continue to analyze flight data recorders, cockpit voice recorders, and the physical debris. A final report, which includes the probable cause and any safety recommendations, typically takes 12 to 18 months to complete.
Sources
Photo Credit: NTSB
Regulations & Safety
NTSB: Thermal Plugs Caused AA Flight 3023 Tire Failure
NTSB determines melted thermal relief plugs caused tire failure on American Airlines 737-8 at Denver, triggering emergency evacuation.

The National Transportation Safety Board (NTSB) has determined that melted thermal relief plugs caused the left main landing gear tires to fail on an American Airlines Boeing 737-8 during a July 2025 takeoff roll at Denver International Airport (DEN), prompting a high-speed rejected takeoff and emergency evacuation.
The final aviation investigation report, published on August 26, 2026, officially closes the inquiry into American Airlines Flight 3023. The document details the mechanical sequence that led to the tire failure while highlighting significant passenger noncompliance during the subsequent evacuation, as travelers ignored crew commands and retrieved carry-on baggage.
Mechanical sequence and rejected takeoff
The incident occurred on July 26, 2025, involving a Boeing 737-8, registration N306SW, equipped with CFM International LEAP-1B28 engines. According to the NTSB, the flight experienced an approximate 25-minute delay while awaiting departure at runway 34L.
During the subsequent takeoff roll, as the aircraft reached an indicated airspeed between 90 and 100 knots, the captain reported hearing a loud pop accompanied by a noticeable bump. The flight crew initiated a rejected takeoff at speeds above 80 knots.
The NTSB determined the probable cause of the incident was the melting of thermal relief plugs in the left main landing gear. This melting released tire pressure and caused the tires and wheels to fail during the takeoff roll. The agency noted that this failure resulted in abnormal airplane handling characteristics, which prompted the flight crew to reject the takeoff. Debris from the fractured wheels caused minor damage to the aircraft, including a three-inch dent on the lower skin of the left wing.
Emergency evacuation and passenger behavior
Following the rejected takeoff, the flight crew initially instructed the cabin to remain seated. Between 30 and 45 seconds later, after identifying smoke and fire originating from the left main landing gear, the crew ordered an emergency evacuation.
The aircraft carried 175 occupants, comprising 169 passengers and six crew members. The NTSB final report confirms that zero injuries occurred during the event. This official casualty figure supersedes preliminary media reports from July 2025 that had indicated minor injuries and hospital evaluations.
The investigation report draws specific attention to passenger behavior during the emergency egress. The NTSB stated that the cabin crew described the evacuation as rapid but hindered by significant passenger confusion and noncompliance. Despite flight attendants repeatedly commanding passengers to leave their belongings behind, multiple individuals retrieved their carry-on baggage. The NTSB concluded that this noncompliance directly slowed the flow of egress from the aircraft.
AirPro News analysis
The NTSB findings regarding American Airlines Flight 3023 add to a well-documented and growing safety concern within the commercial aviation sector. Passenger retrieval of carry-on baggage during emergency evacuations is a recurring issue that compromises the 90-second evacuation standard mandated by the Federal Aviation Administration (FAA).
When passengers stop to open overhead bins and carry luggage down escape slides, they not only slow the egress rate for those behind them but also introduce the risk of puncturing the evacuation slides or injuring fellow passengers. We continue to see official accident reports cite passenger noncompliance as a negative factor in evacuation efficiency. This recurring behavioral pattern has prompted safety advocates and lawmakers to question whether current FAA evacuation certification tests, which rely on compliant participants, accurately reflect real-world human behavior during an emergency.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
Marine One Loss of Separation at DCA: NTSB Preliminary Report
NTSB cites radio line-of-sight failure after Marine One and Envoy Air E-170 came within 0.82 NM at Reagan National.

This is a developing story. Information may change as official details are released.
This is original reporting and analysis by AirPro News.
A loss of separation occurred on August 4, 2026, between a Sikorsky VH-3D operating as Marine One and an Envoy Air Embraer E-170 departing Ronald Reagan Washington National Airport (DCA). The incident took place approximately two miles north of the airport at 14:34 EDT and prompted an immediate Federal Aviation Administration (FAA) relocation of radio equipment after investigators identified a communication failure.
According to a preliminary report released on August 27, 2026, by the National Transportation Safety Board (NTSB), air traffic controllers at DCA did not receive a required three-minute pre-departure warning from the helicopter. The event triggered a review of strict Safety protocols implemented following a fatal midair collision in the same airspace in January 2025.
Incident timeline and separation data
The loss of separation occurred when Marine One departed The Ellipse simultaneously with Envoy Air flight 3742 departing runway 1 at DCA. Preliminary FAA estimates indicate the aircraft came within 0.82 nautical miles (NM) laterally and 700 feet vertically. The NTSB is currently analyzing surveillance data to establish the exact closest point of approach.
President Donald Trump was on board the Sikorsky VH-3D at the time of the incident. In a statement provided to CBS News, White House spokesman Kush Desai confirmed the President was never in danger.
Marine One flights are piloted by the finest aviators in the world, and the White House maintains the utmost confidence in these patriots and other security officials who are responsible for ensuring the President’s safety.
No injuries were reported among the occupants of either aircraft, and both flights continued to their respective destinations without further incident.
Communication failure and FAA response
The NTSB preliminary report points to inadequate radio line-of-sight coverage between The Ellipse and the DCA tower as the primary factor in the missed pre-departure warning. A DCA tower controller reported that the transmission attempt from the helicopter was “broken and unreadable,” according to CBS News.
Following the August 4 incident, FAA technicians evaluated the infrastructure and confirmed the line-of-sight deficiency. To resolve the issue, the agency relocated the helicopter-control radio equipment to the top of the DCA control tower. Subsequent communication checks were successful.
CBS News also reported that recent construction at the White House may have contributed to the radio line-of-sight degradation, though the NTSB has not yet issued a final determination on the cause.
Regulatory context and prior airspace changes
The airspace surrounding DCA operates under highly specific procedural rules designed to deconflict fixed-wing airline traffic from frequent VIP helicopter movements. These procedures were significantly tightened following a fatal midair collision on January 29, 2025, involving an airliner and an Army Black Hawk helicopter near the airport.
Following the 2025 accident, regulators instituted a requirement for a ground stop at DCA anytime a Helicopters passes on a conflicting route. The failure of the three-minute warning on August 4 prevented controllers from initiating this required ground stop for the Envoy Air departure.
Air traffic controllers and Marine One pilots had previously met on July 28, 2026, exactly one week prior to the incident, to discuss ongoing communication challenges in the sector.
AirPro News analysis
The August 4 loss of separation highlights the fragility of procedural deconfliction in the Washington, D.C. airspace. While the FAA characterized the event as a momentary loss of separation, the failure of a critical communication link reveals a single point of failure in the safety protocols established after the 2025 collision. We note that the rapid relocation of the radio equipment by the FAA demonstrates an acknowledgment of the infrastructure gap. As the NTSB continues its Investigation, we will monitor the docket for potential systemic recommendations regarding how VIP helicopter movements integrate with high-volume Commercial-Aircraft traffic at DCA, particularly concerning redundant communication systems.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
FAA Moves to Fire Two LaGuardia Controllers After Fatal Collision
FAA initiates termination proceedings against two LaGuardia controllers for early shift departures on the night of the March 22, 2026 runway collision.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by Reuters by David Shepardson and Doyinsola Oladipo.
The FAA has initiated termination proceedings against two air traffic controllers accused of leaving their shifts early on the night of a fatal runway collision at LaGuardia Airport (LGA) in March 2026. The agency is classifying the unauthorized early departures as timecard fraud amid a broader national crackdown on the practice.
The disciplinary action follows the March 22, 2026, accident in which Air Canada Express Flight 8646, operated by Jazz Aviation LP, collided with an aircraft rescue firefighting (ARFF) vehicle while landing on Runway 4. According to Reuters, the two controllers allegedly departed the facility approximately one hour before their scheduled shifts ended, a practice colloquially known as an “early shove.”
Disciplinary actions and union response
The FAA stated its commitment to holding employees accountable, emphasizing that it will not compromise the safety or efficiency of the national airspace system. U.S. Secretary of Transportation Sean Duffy condemned the practice, stating that while most controllers complete their full shifts, the department will not tolerate fraud from individuals who unfairly burden their colleagues and impact the airspace.
The National Air Traffic Controllers Association (NATCA) confirmed it is actively discussing the allegations with FAA leadership. The union indicated that these internal discussions are the appropriate forum for addressing the matter. Reuters reports that the FAA is currently conducting a nationwide enforcement effort targeting employees who leave on break at the end of their shifts and fail to return.
The March 22 collision and investigation
The NTSB continues to investigate the March 22 collision under investigation ID DCA26MA161. The official cause of the accident remains undetermined. The aircraft involved was an MHI RJ Aviation CRJ-900, and the ground equipment was an Oshkosh Striker 1500 ARFF vehicle.
Official NTSB figures confirm that 76 people were on board the aircraft, including 72 passengers, two flight attendants, and two pilots. The captain and first officer sustained fatal injuries. Thirty-nine individuals were transported to local hospitals, with six reported to have serious injuries.
It remains unverified whether the controllers’ early departure directly influenced the events leading to the collision. Speaking in March 2026, NTSB Chair Jennifer Homendy noted that operating with two controllers in the tower cab during a midnight shift is common practice across the national airspace system, suggesting the facility may have been operating at standard staffing levels at the time of the accident.
Regulatory response to surface safety
Following the LaGuardia accident, the FAA accelerated initiatives to improve surface visibility at airports. On May 13, 2026, the agency announced a $16.5 million investment to equip all airport vehicles with transponders.
These vehicle movement area transponders (VMATs) are designed to provide ATC with better situational awareness of ground equipment operating on runways and taxiways.
AirPro News analysis
We note that the FAA’s decision to pursue termination for timecard fraud rather than operational errors highlights a strict administrative approach to facility management. By focusing on the unauthorized absence, the agency addresses the “early shove” culture directly without preempting the NTSB’s ongoing safety investigation into the collision’s root causes. The distinction between administrative violations and operational fault will likely remain a focal point as NATCA engages with FAA leadership.
Photo Credit: Mike Segar – Reuters
-
Technology & Innovation6 days agoSkyband Systems M100 LRU Validates GNSS Jamming Protection
-
MRO & Manufacturing5 days agoBoeing SPEEA Engineers Reject Contract, Authorize Strike
-
Military Technology6 days agoSaab Unveils A3-001 Supersonic Stealth Drone Concept
-
Business Aviation5 days agoFTAI Aviation Closes $2B Warehouse Financing for 2026 SPV
-
Business Aviation6 days agoSyberJet SJ30-2 Sets Transcontinental Speed Record
