OAK68D0187

NTSB accident investigation · Piper PA-28 · Vacaville, CA · August 30, 1967

Accident · No injuriesClosed
Date
August 30, 1967
Place
Vacaville, CA · VACAVILLE, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6072WPiper PA-28
Status
Completed · report December 12, 1967
Report
Brief approved by the director
Case key
114225

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-3268  67/8/30    VACAVILLE,CALIF     PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 36, 148
        TIME - 1920                    N6072W              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 21 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - VACA VALLEY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: PARKED AIRCRAFT                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - BECAME LOST/DISORIENTED
           MISCELLANEOUS ACTS,CONDITIONS - NOT ALIGNED WITH RUNWAY/INTENDED LANDING AREA
        REMARKS- PKD ACFT N3105A-N617F,SUBSTANTIAL DAMAGE.N2968V,MINOR DAMAGE.

Aircraft

Registration
N6072W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Vaca Valley

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.