LAX90LA117 · Cessna T210L
Cessna T210L · Accident: loss of control in flight during initial climb
From an unrecorded airport to Bakersfield, CA
Event
- NTSB case
- LAX90LA117
- 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
- 3 · 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
- General aviation
- 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
Cessna T210L
- Aircraft type
- Cessna 210
- 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
- N94302
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Bakersfield, 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 91: General Aviation
- 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
- Initial climb
- 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Checklist, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE STRUCK A TREE AND DESCENDED UNCONTROLLED AFTER TAKEOFF. THE AIRPLANE WAS OBSERVED SETTLING TO THE RUNWAY AFTER INITIALLY BECOMING AIRBORNE. WITNESSES INDICATED THE AIRPLANE THEN BECAME AIRBORNE AGAIN, BUT NEVER CLIMBED HIGHER THAN 50 FEET. ACCORDING TO WITNESSES, THE AIRPLANE ENGINE SOUNDED NORMAL AND IT APPEARED THAT THE AIRPLANE WAS OVER GROSS WEIGHT. A SURVIVING PASSENGER STATED THAT THE AIRPLANE WAS 'STOL' EQUIPPED AND 20 DEGREES OF FLAPS WERE SELECTED FOR THE DEPARTURE. EXAMINATIN OF THE WRECKAGE CONFIRMED THE 20 DEG FLAP SETTING. THE ELEVATOR TRIM WAS SET FULL NOSE UP. THE AIRPLANE TAKEOFF GROSS WEIGHT WAS CALCULATED TO BE 58 POUNDS OVER MAXIMUM GROSS WEIGHT.
Probable cause
THE FAILURE OF THE PILOT TO FOLLOW THE AIRPLANE CHECKLIST AND PROPERLY CONFIGURE THE AIRPLANE FOR TAKEOFF. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT'S POOR PREFLIGHT PREPARATION AND THE FAILURE OF THE PILOT TO COMPUTE THE AIRCRAFT WEIGHT BEFORE TAKEOFF.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90LA117
- Event ID
- 20001212X22743
- Case number
- LAX90LA117
- 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: investigation status. 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: 70d9f1672886103329d35fcbb05cebca4c453bc3f2eadee4f8b6de48e6af994a; retrieved 2026-09-21T02:54:01.448Z.