LAX83FA348 · Cessna T210N
Cessna T210N · Accident: in flight encounter with weather en route
From an unrecorded airport to Sacramento Executive Airport (SAC)
Event
- NTSB case
- LAX83FA348
- 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
- 2 · 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
- Instrument Meteorological Cond
Cessna T210N
- 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
- N5517C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Sacramento Executive Airport (SAC), Sacramento, 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
- En route · climb to 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
- Pilot in command › VFR flight into imc, initiated
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT, WHO WAS A CONTRACTOR, WAS SCHEDULED TO ATTEND A HEAVY EQUIP'T AUCTION IN SACRAMENTO TO BEGIN A 1000. WITNESSES HEARD NORMAL ENG SOUNDS AS THE ACFT DEPARTED RWY 19 & TURNED TO A LEFT DOWNWIND DEPARTURE TURN. THE ACFT WAS OBSERVED PROCEEDING ON A NE HEADING, PARALLELING HWY 152 AT ABOUT 500 FT AGL GOING STRAIGHT TOWARD WHERE IT ENDED UP ON A HILLSIDE. ANOTHER WITNESS OBSERVED THE ACFT FLYING BENEATH THE CLOUDS & THEN ENTER THE CLOUDS IN A CLIMB NEAR THE BASE OF THE HILL. ARPT BASED PLTS DESCRIBED THE DEPARTURE AS ONE OF TWO 'BOOTLEG' IFR CLIMB PROCEDURES COMMONLY USED BY MANY LOCAL PLTS DURING LOW STRATUS CONDITIONS. THE PLT HAD BEEN OBSERVED USING THE 'HIGHWAY 152 CLIMB' MANY TIMES DURING THE PRECEEDING YEARS. THERE IS NO RECORD OF THE PLT ATTEMPTING TO OBTAIN A 'POP-UP' IFR TO VFR CLEARANCE. THE PLT FLEW AN AVERAGE OF 2 HRS EACH WORKING DAY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX83FA348
- Event ID
- 20001214X43777
- Case number
- LAX83FA348
- 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: dda9e1d46f5e87e63031d01ac0ee07895dd094312680732b4f7ad3ed0a5cd1c6; retrieved 2026-09-21T06:27:54.943Z.