MKC68D0176

NTSB accident investigation · Cessna 150 · Severance, KS · June 2, 1967

Accident · Serious injuriesClosed
Date
June 2, 1967
Place
Severance, KS · SEVERANCE, KS
Injuries
1 serious, 1 minor
Damage
Destroyed
Phase of flight
Landing
Aircraft
N6259TCessna 150
Status
Completed · report November 9, 1967
Report
Brief approved by the director
Case key
116929

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-0637   67/6/2    SEVERANCE,KANS      CESSNA 150          CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 23, 72 TOTAL
        TIME - 2100                    N6259T              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 60 IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - RUSH
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N6259T
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Rush

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.