FTW66F0116

NTSB accident investigation · Cessna 182 · Amarillo, TX · June 26, 1965

Accident · No injuriesClosed
Date
June 26, 1965
Place
Amarillo, TX · AMARILLO, TX
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8896TCessna 182
Status
Completed · report August 18, 1965
Report
Brief approved by the director
Case key
177511

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-1621  65/6/26    AMARILLO TEX        CESSNA 182          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 51, 68 TOTAL
        TIME - 2000                    N8896T              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  HOURS, 3 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - PALO DURO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N8896T
Reported as
Cessna 182
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Palo Duro

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.