- Date
- October 16, 1980
- Place
- Sacramento, CA · SACRAMENTO, CA
- Injuries
- 1 fatal, 1 serious
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N6137BCessna T210
- Status
- Completed · report May 7, 1981
- Report
- Brief approved by the director
- FAA report
- 19801016089849A
- Case key
- 127582
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-3731 80/10/16 SACRAMENTO,CA CESSNA T210 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 51, 1000 TIME - 1353 N6137B PX- 0 1 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 44 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - SAC.EXECUTIVE, DEPARTURE POINT INTENDED DESTINATION BURBANK,CA SACRAMENTO,CA TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: DESCENDING STALL: SPIRAL LANDING: FINAL APPROACH PROBABLE CAUSE(S) PERSONNEL - PRODUCTION-DESIGN-PERSONNEL: POOR/INADEQUATE DESIGN POWERPLANT - FUEL SYSTEM: OTHER MISCELLANEOUS ACTS,CONDITIONS - FUEL STARVATION PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED FACTOR(S) PILOT IN COMMAND - FAILED TO FOLLOW APPROVED PROCEDURES,DIRECTIVES,ETC. COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- FUEL VAPOR RETURN SYSTEM
Aircraft
- Registration
- N6137B
- Reported as
- Cessna T210
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Sac.Executive,
N6137BRegistration cancelled Apr 26, 2013 · Cessna T210MAirframe modelCessna T210MEngine modelContinental TSIO-520 series
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.