CHI66F0600

NTSB accident investigation · Piper PA-22 · Naperville, IL · January 29, 1966

Accident · No injuriesClosed
Date
January 29, 1966
Place
Naperville, IL · NAPERVILLE, IL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4785APiper PA-22
Status
Completed · report April 4, 1966
Report
Brief approved by the director
Case key
178688

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-0250  66/1/29    NAPERVILLE ILL      PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 34, 265
        TIME - 1300                    N4785A              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 4 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - NAPERVILLE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SNOW ON RUNWAY

Aircraft

Registration
N4785A
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Naperville

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.