OAK67D0019

NTSB accident investigation · Piper PA28 · Sacramento, CA · June 18, 1966

Accident · No injuriesClosed
Date
June 18, 1966
Place
Sacramento, CA · SACRAMENTO, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N132SFPiper PA28
Status
Completed · report August 10, 1966
Report
Brief approved by the director
Case key
171368

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-1522  66/6/18    SACRAMENTO CALIF    PIPER PA28          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 29, 96 TOTAL
        TIME - 1300                    N132SF              PX-  0  0  0  PRACTICE                  HOURS, 12 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SACRAMENTO MUNICI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N132SF
Reported as
Piper PA28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sacramento Munici

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.

Other investigations on N132SF · 2

Matched to the same aircraft by N-number and date.