FTW67F0041

NTSB accident investigation · Cessna 182 · Oklahoma City, OK · June 14, 1966

Accident · No injuriesClosed
Date
June 14, 1966
Place
Oklahoma City, OK · OKLAHOMA CITY, OK
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2090XCessna 182
Status
Completed · report August 12, 1966
Report
Brief approved by the director
Case key
171359

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-1514  66/6/14    OKLAHOMA CITY OKL   CESSNA 182          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 48, 1144
        TIME - 1125                    N2090X              PX-  0  0  3  BUSINESS                  TOTAL HOURS, 1020 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - DOWNTOWN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: DIRT BANK                                 LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED

Aircraft

Registration
N2090X
Reported as
Cessna 182
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Downtown

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.