CHI68F0690

NTSB accident investigation · Cessna 172F · Denver, IL · April 10, 1968

Accident · Serious injuriesClosed
Date
April 10, 1968
Place
Denver, IL · DENVER, IL
Injuries
2 serious
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N8269UCessna 172F
Status
Completed · report May 23, 1968
Report
Brief approved by the director
Case key
111228

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-0888  68/4/10    DENVER,ILL          CESSNA 172F         CR-  0  1  0  NONCOMMERCIAL             COMMERCIAL, AGE 56, 4449
        TIME - 0810                    N8269U              PX-  0  1  0  BUSINESS                  TOTAL HOURS, 8 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CLARK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS

Aircraft

Registration
N8269U
Reported as
Cessna 172F
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Clark

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.