FTW67A0008

NTSB accident investigation · Brantly 305 · Wichita Falls, TX · July 10, 1966

Accident · Serious injuriesClosed
Date
July 10, 1966
Place
Wichita Falls, TX · WICHITA FALLS, TX
Injuries
1 serious
Damage
Destroyed
Phase of flight
Approach
Aircraft
N2203UBrantly 305
Status
Completed · report March 3, 1967
Report
Brief approved by the director
Case key
171105

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-0573  66/7/10    WICHITA FALLS TEX   BRANTLY 305         CR-  0  1  0  NONCOMMERCIAL             STUDENT, AGE 46, 129
        TIME - 2005                    N2203U              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 57 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            UNK/NR INSTRUMENT RATED.
        NAME OF AIRPORT - KICKAPOO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              LANDING: TRAFFIC PATTERN-CIRCLING
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN ADEQUATE ROTOR R.P.M.

Aircraft

Registration
N2203U
Reported as
Brantly 305
Category
Helicopter
Engine
reciprocating
Damage
Destroyed
Airport
Kickapoo

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.