Flight 1669 · Boeing 757-232
Boeing 757-232 · Accident: abrupt maneuver en route
From CVG · Cincinnati, OH to San Francisco International Airport (SFO)
Event
- NTSB case
- LAX01LA307
- 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
- Unknown
- 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 757-232
- Aircraft type
- Boeing 757
- 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
- N644DL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From CVG · Cincinnati, OHTo San Francisco International Airport (SFO), San Francisco, CA
- 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
- Abrupt maneuver
- 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
- Pilot in command › Flight controls, excessive
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The air carrier transport airplane experienced an abrupt maneuver during its initial descent. The first officer reported that the flight crew had been cleared to descend from FL 390 to FL 330. The captain initiated the descent and the first officer began programming the flight management system. The first officer looked up as the airplane was flying past FL330 and queried the captain. The captain then immediately pulled the aircraft out of the descent and leveled off at FL330. Shortly thereafter, the flight crew was notified of a passenger injury resulting from the event. The captain reported to the passengers that they encountered turbulence. All of the flight attendants reported a smooth flight prior to the event. The captain had illuminated the fasten seat belt sign, but no one could remember an announcement accompanying the sign illumination. All of the flight attendants and an injured passenger, who was in the lavatory at the time of the event, described being pushed downward during the occurrence. There were no flight data recorders, cockpit voice recorders, or air traffic control recordings to review, because the Safety Board was not notified of the accident until almost 1 year after the event.
Probable cause
the captain's excessive use of the flight controls to level off from a descent, which resulted in a passenger injury.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA307
- Event ID
- 20020814X01387
- Case number
- LAX01LA307
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2001-07-12.
- API snapshot SHA-256: 7c0760d60fc507f8bfc1832adfd70fb145313be8ea66cbbff8dfb806c2a59525; retrieved 2026-09-18T16:11:52.647Z.