MKC65F0045

NTSB accident investigation · Cessna 182 · Concordia, KS · February 17, 1965

Accident · No injuriesClosed
Date
February 17, 1965
Place
Concordia, KS · CONCORDIA, KS
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N8590TCessna 182
Status
Completed · report April 23, 1965
Report
Brief approved by the director
Case key
179441

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-0433  65/2/17    CONCORDIA KANS      CESSNA 182          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 33, 93 TOTAL
        TIME - 1535                    N8590T              PX-  0  0  0  BUSINESS                  HOURS, 7 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - BLOSSER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           COLLIDED WITH: SNOWBANK                                  TAKEOFF: ABORTED
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: ICE/SLUSH ON RUNWAY

Aircraft

Registration
N8590T
Reported as
Cessna 182
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Blosser

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.