CHI69F0224

NTSB accident investigation · Piper PA-28 · Kilbourne, IL · August 29, 1968

Accident · No injuriesClosed
Date
August 29, 1968
Place
Kilbourne, IL · KILBOURNE, IL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5326LPiper PA-28
Status
Completed · report October 29, 1968
Report
Brief approved by the director
Case key
109055

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-3008  68/8/29    KILBOURNE,ILL       PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 31, 150
        TIME - 0710                    N5326L              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 80 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - KRUSE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: WET RUNWAY

Aircraft

Registration
N5326L
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Kruse

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.