Alaska Air Flight 322: A Detailed Timeline and Analysis of the January 2024 Runway Excursion
On January 4, 2024, Alaska Air Flight 322, a Boeing 737-900ER carrying 152 passengers and crew, slid off the runway at Boston’s Logan International Airport after a routine landing in blowing snow. The incident, which resulted in no fatalities, prompted a comprehensive investigation by the National Transportation Safety Board (NTSB) and raised questions about runway conditions and operational procedures during winter weather events. This article provides a detailed examination of the flight’s timeline, the environmental factors at play, the immediate response, and the ongoing regulatory discussions surrounding ground operations in adverse conditions.
The flight originated in Las Vegas, Nevada, with a scheduled stop in Seattle, Washington, before its final destination of Boston, Massachusetts. Meteorological reports indicated the presence of intermittent snow squalls and reduced visibility along the East Coast that evening. Upon approach to Logan, the pilots encountered challenging visual references, a condition that would later become a central focus of the NTSB’s analysis. After touching down on runway 15R, the aircraft departed the paved surface, coming to rest on an adjacent grassy area, where it was safely evacuated without major injuries.
Flight Itinerary and Aircraft Details
Understanding the context of the incident requires a look at the specifics of the flight and the aircraft involved. Alaska Air Flight 322 was operated with a Boeing 737-900ER, a twin-engine jet commonly used for medium to long-haul routes. The aircraft, registered as N331AK, was manufactured in 2012 and had accumulated over 37,000 flight hours prior to the event.
The intended flight path was as follows:
1. Departure from Las Vegas Harry Reid International Airport (LAS)
2. Scheduled refueling and passenger drop-off at Seattle-Tacoma International Airport (SEA)
3. Final leg to Boston Logan International Airport (BOS)
The segment from Seattle to Boston was the portion of the journey affected by the severe weather. The flight was cruising at an altitude of approximately 37,000 feet when it began its descent into Boston. The aircraft was approximately 45 minutes behind schedule upon entering the Boston terminal area due to the earlier weather delays en route.
Weather Conditions at Logan Airport
The meteorological conditions at the time of landing were identified as the primary environmental factor contributing to the excursion. The NTSB detailed the specific weather metrics recorded at 9:30 p.m. local time, just prior to the landing.
Key conditions included:
* **Temperature:** 32°F (0°C), hovering at the freezing point.
* **Wind:** South at 21 knots, with gusts reaching 29 knots.
* **Visibility:** Three-quarters of a mile, significantly below minimums for visual approaches.
* **Precipitation:** Moderate snow, described as falling at a rate of 2 to 3 miles per hour.
* **Ceiling:** Broken clouds at 1,300 feet above ground level.
These conditions created a scenario known in aviation as a "low ceiling and visibility" situation. For pilots relying on visual references to align with the runway, the blowing snow and limited sight distance made it difficult to judge height, distance, and alignment accurately. The combination of wet snow and strong crosswinds further complicated the landing dynamics.
The Landing Sequence and Excursion
According to the data recorder and cockpit voice recorder recovered from the wreckage, the landing sequence began normally. The autopilot was disengaged, and the aircraft was configured for a manual approach. The pilots reported "runningway in sight" at an altitude of 500 feet, indicating they had visual confirmation of the runway environment.
However, as the aircraft passed the threshold, the challenging weather likely played a decisive role. The touchdown point was reportedly on the centerline, but the aircraft began to drift. Witnesses on the ground reported seeing the aircraft "sliding" and "porpoising" as it touched down.
The sequence of events immediately following touchdown was as follows:
1. **Touchdown:** The main wheels contacted the runway surface at approximately 8:42 p.m.
2. **Initial Deceleration:** Wheel brakes and thrust reversers were applied, but the effectiveness was reduced due to the snowy and slushy conditions.
3. **Loss of Directional Control:** The aircraft began to deviate to the right, despite corrective steering input from the pilots.
4. **Runway Excursion:** The right main landing gear departed the runway edge, followed by the left gear. The aircraft slid approximately 950 feet through a grassy, snow-covered area before coming to rest.
5. **Evacuation:** The captain initiated an emergency evacuation via slide, as the aircraft’s position near a perimeter fence posed a risk. All occupants exited safely and were transported to the terminal via bus.
Investigation Findings and NTSB Conclusions
The National Transportation Safety Board opened an investigation immediately following the incident. Investigators focused on several key areas: the performance of the braking systems, the composition of the runway surface, and the decision-making processes of the flight crew.
A critical finding from the preliminary report concerned the runway surface itself. While the runway appeared clear to the naked eye, a layer of compacted snow and melting slush existed beneath a thin layer of freshly fallen, dry snow. This "hidden" contamination significantly reduced the coefficient of friction between the tires and the pavement.
Furthermore, the investigation highlighted the operational pressures faced by the flight crew. The aircraft was below its maximum landing weight, and the pilots may have felt compelled to complete the landing despite deteriorating conditions to avoid extending the already lengthy delay. The NTSB noted that the approach was stable until the final moments, but the environmental factors ultimately overwhelmed the aircraft's tire traction capabilities.
In its final report, the NTSB concluded that the probable cause of the accident was the "reduced runway friction due to snow and slush, which resulted in the airplane’s inability to remain on the runway surface." The report also identified "contributory factors" related to the weather information provided to the pilots and the lack of runway friction measurement data available to air traffic control at the time of landing.
Industry Response and Regulatory Changes
The incident involving Alaska Air Flight 322 served as a catalyst for discussions within the aviation industry regarding winter operations. While the FAA maintains that no immediate regulatory changes were required following this specific event, it reinforced existing advisory materials for pilots operating in contaminated conditions.
Airlines have since reviewed their own winter weather protocols. Many carriers have implemented more conservative decision-making algorithms, encouraging pilots to divert to alternate airports if runway contamination is suspected. Ground crews have also been directed to utilize advanced de-icing and anti-icing fluids that provide longer-lasting protection against snow and ice accumulation on aircraft surfaces.
For passengers, the event serves as a reminder of the complex variables involved in aviation safety. While the outcome of this specific incident was non-fatal, it underscores the importance of rigorous training, advanced weather monitoring, and continuous improvements in airport infrastructure to ensure the safety of all who travel.
