CHI66F0322

NTSB accident investigation · Cessna 182 · Columbus, OH · September 26, 1965

Accident · No injuriesClosed
Date
September 26, 1965
Place
Columbus, OH · COLUMBUS, OH
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N9019XCessna 182
Status
Completed · report November 10, 1965
Report
Brief approved by the director
Case key
175642

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-2827  65/9/26    COLUMBUS OHIO       CESSNA 182          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 22, 220
        TIME - 2130                    N9019X              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 20 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PORT COLUMBUS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        REMARKS- NIGHT OPERATION ON LIGHTED RUNWAY

Aircraft

Registration
N9019X
Reported as
Cessna 182
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Port Columbus

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.