FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Alaska Airlines Flight 135

13 Nov 2000 · Anchorage, AK, United States

Boeing 737-790 · Accident: in flight encounter with weather en route

From Chicago O'Hare International Airport (ORD) to Ted Stevens Anchorage International Airport (ANC)

Report a problem

Event

NTSB case
ANC01LA018
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
Completed
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-790

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
N611AS
Onboard fatalities
Unknown
Route
From Chicago O'Hare International Airport (ORD), Chicago, ILTo Ted Stevens Anchorage International Airport (ANC), Anchorage, AK
Aircraft age
Not recorded
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 · descent
First occurrenceThe 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
In flight encounter with weather
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

  • Weather condition › Turbulence, clear air

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The captain of a Boeing 737-700 reported that prior to starting a descent, he received reports of moderate turbulence in the area of the arrival airport. He said that he instructed the cabin attendants to secure the cabin early in anticipation of turbulence during the approach. The injured flight attendant related that before the flight crew initiated the descent, the attendants were asked to ready the cabin early in anticipation of turbulence. She said that as she walked to the back of the airplane, and just before she was to be seated, she noticed that a few remaining service carts located in the aft galley were not locked down. She stated that as she locked down one of the last remaining service carts, 'the floor just fell out from under my feet, my head hit the ceiling, and I landed back on the floor, on my right leg.' The flight attendant sustained a broken right ankle.

Probable cause

An in-flight encounter with clear air turbulence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC01LA018
Event ID
20001226X45475
Case number
ANC01LA018
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: 1c3366ce093cc37c545fdd73bbaa907abd64a7200c1688a3913ce915cc926177; retrieved 2026-09-18T16:20:31.352Z.
  • The NTSB's operator name is blank for N611AS; the operator shown is the name the NTSB records it doing business as.