CHI67D0636

NTSB accident investigation · Cessna 172 · Pittsfield, IL · October 20, 1966

Accident · No injuriesClosed
Date
October 20, 1966
Place
Pittsfield, IL · PITTSFIELD, IL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3891LCessna 172
Status
Completed · report June 28, 1967
Report
Brief approved by the director
Case key
120498

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-4381  66/10/20   PITTSFIELD,ILL      CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 30, 185
        TIME - 1620                    N3891L              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 130 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SHUSTER
        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
N3891L
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Shuster

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.