- Date
- June 11, 1972
- Place
- Chico, CA · CHICO, CA
- Injuries
- 1 minor
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N1418ZStitz SA-6B
- Status
- Completed · report September 21, 1972
- Report
- Brief approved by the director
- Case key
- 166778
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-0186 72/6/11 CHICO,CALIF STITZ SA-6B CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 40, 183 TIME - 1200 N1418Z PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 19 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - PATRICK FLD DEPARTURE POINT INTENDED DESTINATION CHICO,CALIF LOCAL TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB COLLIDED WITH: FENCE,FENCEPOSTS LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - MISCALCULATED FUEL CONSUMPTION MISCELLANEOUS ACTS,CONDITIONS - FUEL STARVATION TERRAIN - OTHER COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT. REMARKS- LCL FLT TO CHICO MUNI TO REFUEL AFTR X-COUNTRY.APRX 3GALS ON BOARD,GRAVITY FEED SYST.CEDAR FENCE.
Aircraft
- Registration
- N1418Z
- Reported as
- Stitz SA-6B
- Category
- Airplane, amateur-built
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Patrick Fld
N1418ZRegistered now · William I Rardin STITS SA-6BAirframe modelWilliam I Rardin STITS SA-6BEngine modelContinental C85 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.