- Date
- August 31, 1972
- Place
- Petaluma, CA · PETALUMA, CA
- Injuries
- 1 fatal, 1 serious
- Damage
- Destroyed
- Phase of flight
- Approach
- Aircraft
- N4233TPiper PA-28
- Status
- Completed · report March 20, 1973
- Report
- Brief approved by the director
- Case key
- 168391
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-3337 72/8/31 PETALUMA,CALIF PIPER PA-28 CR- 0 1 0 NONCOMMERCIAL PRIVATE, AGE 36, 84 TOTAL TIME - 2030 N4233T PX- 1 0 0 PLEASURE/PERSONAL TRANSP HOURS, 78 IN TYPE, NOT DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - PETALUMA SKY RNCH DEPARTURE POINT INTENDED DESTINATION PETALUMA,CALIF LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: UNCONTROLLED LANDING: GO-AROUND PROBABLE CAUSE(S) PILOT IN COMMAND - SPATIAL DISORIENTATION FACTOR(S) PILOT IN COMMAND - FAILED TO USE OR INCORRECTLY USED MISC.EQUIPMENT WEATHER - FOG TERRAIN - OTHER WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - UNKNOWN/NOT REPORTED MISSING AIRCRAFT - LATER RECOVERED SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 300 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 3 MILES OR LESS NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE WIND VELOCITY-KNOTS FOG CALM TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE REMARKS- LDG LIGHTS,ROTATING BEACON ON.UNLIGHTED TERRAIN.RCVRD 9/1/72.
Aircraft
- Registration
- N4233T
- Reported as
- Piper PA-28
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Petaluma Sky Rnch
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.