CHI67F0047

NTSB accident investigation · Piper PA28 · St Clairsvil, OH · July 4, 1966

Accident · No injuriesClosed
Date
July 4, 1966
Place
St Clairsvil, OH · ST CLAIRSVIL, OH
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6292WPiper PA28
Status
Completed · report August 15, 1966
Report
Brief approved by the director
Case key
171620

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-1630   66/7/4    ST CLAIRSVIL OHIO   PIPER PA28          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 23, 37 TOTAL
        TIME - 0945                    N6292W              PX-  0  0  0  PRACTICE                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - ALDERMAN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N6292W
Reported as
Piper PA28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Alderman

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.