NTSB Preliminary Report on Alaska Airlines Flight 2616 Bird Strike Accident

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

• NTSB Preliminary Report (DCA26WA/202360)
• FAA