OAK71FVM58

NTSB accident investigation · Zlin 526F · Hollister, CA · June 12, 1971

Accident · FatalClosed
Date
June 12, 1971
Place
Hollister, CA · HOLLISTER, CA
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N34VMZlin 526F
Status
Completed · report December 14, 1971
Report
Brief approved by the director
Case key
161696

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-0924  71/6/12    HOLLISTER,CALIF     ZLIN 526F           CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, AGE 28, 334
        TIME - 1540                    N34VM               PX-  0  0  0  PRACTICE                  TOTAL HOURS, 88 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - HOLLISTER
        DEPARTURE POINT             INTENDED DESTINATION
          HOLLISTER,CALIF             SAN CARLOS,CALIF
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: ACROBATICS
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INCAPACITATION
        REMARKS- OBS SAW ACFT FALL FROM 4 PT ROLL ABOUT 2500 FT AGL. PLT INCAPACITATED FOR UNDETERMINED REASON.

Aircraft

Registration
N34VM
Reported as
Zlin 526F
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Hollister

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.