MKC66D0393

NTSB accident investigation · Piper PA-28 · Mcpherson, KS · January 17, 1966

Accident · No injuriesClosed
Date
January 17, 1966
Place
Mcpherson, KS · MCPHERSON, KS
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6485WPiper PA-28
Status
Completed · report June 10, 1966
Report
Brief approved by the director
Case key
172685

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-0915  66/1/17    MCPHERSON KANS      PIPER PA-28         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 36, 23 TOTAL
        TIME - 1445                    N6485W              PX-  0  0  0  SOLO                      HOURS, 3 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - MCPHERSON
        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
N6485W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Mcpherson

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.