LAX05FA132 · Cessna T210L
Cessna T210L · Accident: in flight encounter with weather en route
From Charles M. Schulz Sonoma County Airport (KSTS) to Scottsdale Airport (KSDL)
Event
- NTSB case
- LAX05FA132
- 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
- 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
- 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
- N8126L
- Operator
- Karl F. Esposti · private individual
- Onboard fatalities
- Unknown
- Route
- From Charles M. Schulz Sonoma County Airport (KSTS), Santa Rosa, CATo Scottsdale Airport (KSDL), Scottsdale, AZ
- 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
- En route · cruise
- 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
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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
- Horizontal stabilizer › Overload
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Design stress limits of aircraft, exceeded
- Pilot in command › VFR flight into imc, continued
- Wing › Overload
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
About 1 hour into the flight the airplane entered an uncontrolled descent and broke up in flight. The pilot, who did not possess an instrument flight rating, had received a standard weather briefing from a flight service station prior to departure. The briefer advised the pilot that a cold front existed perpendicular to the airplane's route of flight that produced multiple cloud layers to 30,000 feet, overcast conditions, rain, nimbostratus clouds, moderate turbulence, and moderate icing conditions along the frontal boundary. The airplane's radar track depicted the airplane cruising at 13,400 feet mean sea level (msl) on a steady southeasterly course. Analysis of the weather conditions showed that the flight encountered instrument meteorological conditions and ice as it approached the frontal boundary. Weather radar imagery depicted an encounter with the western edge of two bands of radar echoes, which could be associated with strong up- or downdrafts that could result in an upset to the airplane. If the autopilot system were engaged it would have masked the trim and heading changes that usually accompanies ice accumulation, and upon disengagement of the autopilot system, the airplane would be in an unbalanced flight condition. Recorded radar data showed that the last radar return in line with the southeasterly course occurred at 0901:54, with a mode C reported altitude of 13,400 feet msl. The next three radar returns occurred between 0901:59 and 0902:14, and depicted the track in a right-hand turn and a descent to 12,400 feet msl, which was the last identified altitude. This change in altitude corresponded to a 3,000- to 4,000-feet-per-minute rate of descent. Numerous primary targets in patterns indicative of an in-flight breakup were identified in the same vicinity from 0902:14 to 0903:08. Examination of the wreckage revealed permanent set deformation of the structural elements of the wings and horizontal stabilizers that was indicative of positive aerodynamic loading beyond the structures yield point. All fractures were overload in character. The wreckage was widely scattered over a distance in excess of 1,600 yards.
Probable cause
the pilot's in-flight loss of control due to spatial disorientation and a likely accumulation of airframe ice that led to a high speed descent and a structural breakup once the aerodynamic forces exceeded the strength limits of the structure. A factor in the accident was the pilot's lack of experience and training in instrument flight conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05FA132
- Event ID
- 20050413X00450
- Case number
- LAX05FA132
- 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, coordinates. 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: 42a85918ed817ca8d25026a4932fac1071d8fd6597fd4e88d6dbccb6e152aed1; retrieved 2026-09-20T18:05:06.210Z.