Alaska Airlines Flight 700
Boeing 737 9 · Accident: turbulence encounter en route
From Seattle–Tacoma International Airport (SEA) to Phoenix Sky Harbor International Airport (PHX)
Event
- NTSB case
- DCA25FA071
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Ongoing
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Boeing 737 9
- Aircraft type
- Boeing 737
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N958AK
- Operator
- Alaska Airlines
- Onboard fatalities
- Unknown
- Route
- From Seattle–Tacoma International Airport (SEA), Seattle, WATo Phoenix Sky Harbor International Airport (PHX), Phoenix, AZ
- Aircraft age
- About 1 year (built 2023)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Turbulence encounter
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On December 26, 2024, at 1335 pacific standard time, Alaska Airlines flight 700, a Boeing 737-9, N958AK, encountered severe turbulence during cruise flight, near Henderson, Nevada. Of the 181 passengers and crew, two flight attendants received serious injuries, and one received a minor injury. The flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 121 scheduled domestic passenger flight from Seattle-Tacoma International Airport (SEA), Seattle, Washington, to Phoenix Sky Harbor International Airport (PHX), Phoenix, Arizona.
The flight crew reported that during the first half of the flight, the turbulence they experienced was “no worse than light chop”. They were aware that worse turbulence was expected during the second half of the flight, as indicated by weather products and advisories provided in the dispatch paperwork for the flight. Additionally, they monitored a company weather app and had communication with their dispatch while enroute for any updates to weather conditions and turbulence forecasts.
Before the flight, the pilots had briefed the lead flight attendant in advance about when they should perform service and prepare for landing, due to the expected turbulence. As the airplane approached the area of expected turbulence, while at flight level (FL) 330, the first officer made a public address announcement to advise the passengers that the seatbelt sign would be turned on in about 15 minutes, and the flight attendants would then also be seated. The airplane encountered light turbulence 15 minutes later, and the first officer turned on the seatbelt sign and informed the flight attendants that the turbulence was expected to worsen, and that they should prepare the cabin and take their seats. The first officer checked in with air traffic control (ATC) and reported experiencing light with occasional moderate turbulence. ATC advised that there were areas of light chop throughout the Las Vegas area, and that there were no reports of turbulence more intense than the light chop.
About 15 minutes later the airplane encountered severe turbulence. Two flight attendants were seriously injured, and one non-revenue flight attendant passenger sustained a minor injury. All were located in the rear gally area when the turbulence occurred and were not restrained.
The pilots declared a medical emergency and elected to continue to Phoenix, after determining that a diversion to the nearest airport would result in routing through the area of expected turbulence. The remainder of the flight was uneventful. EMS personnel met the airplane at the gate and four flight attendants were subsequently transported to the hospital.
A post accident review of weather data revealed that a Significant Meteorological Information (SIGMET) advisory was issued at 1213 which forecasted occasional severe turbulence between FL270 and FL400 due to wind shear associated with the jetstream in an area surrounding the accident location. A pilot report (PIREP) had previously included such conditions 5 minutes prior to the accident in the general vicinity of the turbulence encounter location. Additionally, an Airman’s Meteorological Information (AIRMET) advisory was issued for the area at 1245, which forecasted moderate turbulence between FL180 and FL400. Satellite and weather radar data for the accident area indicated there was cloud cover above the turbulence encounter locations and no precipitation echoes, respectively.
Qualified parties were invited to participate in the investigation. These included Alaska Airlines, the Federal Aviation Administration (FAA) and National Air Traffic Controllers Association. The following NTSB specialists were assigned to investigate the accident: Air Traffic Control, Meteorology, and Operations. The investigation is continuing.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record DCA25FA071
- Event ID
- 20241227199474
- Case number
- DCA25FA071
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, damage. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 3f850390df7d0033e2928ff593de61c3eda35f05b464f2c3147bd1d82de7670c; retrieved 2026-09-16T19:34:05.459Z.