OAK66A0041

NTSB accident investigation · Piper J4 · Healdsburg, CA · March 25, 1966

Accident · FatalClosed
Date
March 25, 1966
Place
Healdsburg, CA · HEALDSBURG, CA
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Uncontrolled descent
Aircraft
N26807Piper J4
Status
Completed · report July 20, 1966
Report
Brief approved by the director
Case key
174124

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-0122  66/3/25    HEALDSBURG CALIF    PIPER J4            CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1540                    N26807              PX-  1  0  0  BUSINESS                  AGE 45, 2306 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            52 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - HEALDSBURG MUNI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
        REMARKS- PILOT HAD RECENTLY EXPERIENCED SEVERE CHEST PAINS.

Aircraft

Registration
N26807
Reported as
Piper J4
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Healdsburg Muni

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.