FTW65F0011

NTSB accident investigation · Cessna 182 · Dallas, TX · March 12, 1965

Accident · No injuriesClosed
Date
March 12, 1965
Place
Dallas, TX · DALLAS, TX
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5317BCessna 182
Status
Completed · report June 7, 1965
Report
Brief approved by the director
Case key
184237

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-0798  65/3/12    DALLAS TEX          CESSNA 182          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 23, 150
        TIME - 1435                    N5317B              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 30 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - HIGHLAND PARK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND

Aircraft

Registration
N5317B
Reported as
Cessna 182
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Highland Park

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.