UNK64X0252

NTSB accident investigation · Cessna 172 · Columbus, OH · January 15, 1964

Accident · FatalClosed
Date
January 15, 1964
Place
Columbus, OH · COLUMBUS, OH
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Approach
Aircraft
N8390BCessna 172
Status
Completed · report December 22, 1964
Report
Brief approved by the director
Case key
116905

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
----------------------------------------------------------------------------------------------------------------------------
2-0017  64/1/15    COLUMBUS OHIO       CESSNA 172          CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 2100                    N8390B              PX-  1  0  0  PRACTICE                  AGE 30, 5115 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            210 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - PORT COLUMBUS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     LANDING: INITIAL APPROACH
        PROBABLE CAUSE(S)
          PILOT-IMPROPERLY EXECUTED SIMULATED INST. APPROACH
           PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT

Aircraft

Registration
N8390B
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Destroyed
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.