- Date
- January 1, 1967
- Place
- Earlimart, CA · EARLIMART, CA
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N4195ZPiper PA-18
- Status
- Completed · report February 10, 1969
- Report
- Brief approved by the director
- Case key
- 119511
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 ---------------------------------------------------------------------------------------------------------------------------- 2-1200 67/1/1 EARLIMART,CALIF PIPER PA-18 CR- 1 0 0 INSTRUCTIONAL STUDENT, AGE 55, 63 TOTAL TIME - 1700 N4195Z PX- 0 0 0 TRAINING HOURS, ALL IN TYPE, NOT DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: CONTROLLED IN FLIGHT: DESCENDING PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - IMPROPER IN-FLIGHT DECISIONS OR PLANNING FACTOR(S) WEATHER - LOW CEILING WEATHER - FOG PERSONNEL - TRAFFIC CONTROL PERSONNEL: ISSUED IMPROPER OR CONFLICTING INSTRUCTIONS PILOT IN COMMAND - BECAME LOST/DISORIENTED WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION 0 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE ZERO NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS FOG IFR TYPE OF FLIGHT PLAN NONE REMARKS- PLT BECAME LOST,RECD ERRONEOUS DF STEER FROM FSS. PLT DESCENDED INTO FOG. OVERFLEW SUITABLE AFLDS.
Aircraft
- Registration
- N4195Z
- Reported as
- Piper PA-18
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.