FTW68F0397

NTSB accident investigation · Beech H35 · Anson, TX · December 11, 1967

Accident · No injuriesClosed
Date
December 11, 1967
Place
Anson, TX · ANSON, TX
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5566DBeech H35
Status
Completed · report February 2, 1968
Report
Brief approved by the director
Case key
112370

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-4453  67/12/11   ANSON,TEX           BEECH H35           CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 58, 2000
        TIME - 1030                    N5566D              PX-  0  0  3  BUSINESS                  TOTAL HOURS, 1589 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - PITTARD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO ASSURE THE GEAR WAS DOWN AND LOCKED
        REMARKS- LNDG GR PARTIALLY RETRACTED.

Aircraft

Registration
N5566D
Reported as
Beech H35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Pittard

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.