FTW69D0018

NTSB accident investigation · Cessna 310 · Daisy, OK · May 12, 1968

Accident · No injuriesClosed
Date
May 12, 1968
Place
Daisy, OK · DAISY, OK
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1715HCessna 310
Status
Completed · report July 29, 1968
Report
Brief approved by the director
Case key
110441

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-1617  68/5/12    DAISY,OKLA          CESSNA 310          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 46, 750
        TIME - 0700                    N1715H              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 610 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: WET RUNWAY
        REMARKS- IMPROPER SHORT FLD PROCEDURE.

Aircraft

Registration
N1715H
Reported as
Cessna 310
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.