CHI68F0567

NTSB accident investigation · Cessna 172 · Princeton, IL · January 30, 1968

Accident · Serious injuriesClosed
Date
January 30, 1968
Place
Princeton, IL · PRINCETON, IL
Injuries
2 serious, 2 minor
Damage
Destroyed
Phase of flight
Landing
Aircraft
N1121FCessna 172
Status
Completed · report March 19, 1968
Report
Brief approved by the director
Case key
112273

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-0126  68/1/30    PRINCETON,ILL       CESSNA 172          CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 26, 178
        TIME - 1130                    N1121F              PX-  0  1  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 20 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PIPER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: TREES                                     LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N1121F
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Piper

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.