- Date
- November 5, 1972
- Place
- Santa Ynez, CA · SANTA YNEZ, CA
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N6211ECessna 172
- Status
- Completed · report March 16, 1973
- Report
- Brief approved by the director
- Case key
- 168949
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-3201 72/11/5 SANTA YNEZ,CALIF CESSNA 172 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 35, 500 TIME - 1930 N6211E PX- 0 0 1 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 40 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - SANTA YNEZ DEPARTURE POINT INTENDED DESTINATION MONTEREY,CALIF SANTA BARBARA,CALIF TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION LANDING: GO-AROUND COLLIDED WITH: FENCE,FENCEPOSTS LANDING: FINAL APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PILOT IN COMMAND - LACK OF FAMILIARITY WITH AIRCRAFT PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - MISCALCULATED FUEL CONSUMPTION MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION PILOT IN COMMAND - EXERCISED POOR JUDGMENT TERRAIN - HIGH OBSTRUCTIONS COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- PILOT RAN OUT OF FUEL ON GO-AROUND FROM LOW PASS AT AIR FIELD.
Aircraft
- Registration
- N6211E
- Reported as
- Cessna 172
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Santa Ynez
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.