MIA69D0459

NTSB accident investigation · Brantly B-2B · Naples, FL · April 26, 1969

Accident · No injuriesClosed
Date
April 26, 1969
Place
Naples, FL · NAPLES, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Uncontrolled descent
Aircraft
N1175KBrantly B-2B
Status
Completed · report June 24, 1969
Report
Brief approved by the director
Case key
189219

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-1083  69/4/26    NAPLES,FLA          BRANTLY B-2B        CR-  0  0  1  INSTRUCTIONAL             PRIVATE, AGE 51, 4000
        TIME - 1830                    N1175K              PX-  0  0  0  SOLO                      TOTAL HOURS, 4 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - NAPLES
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN ADEQUATE ROTOR R.P.M.
           PERSONNEL - FLIGHT INSTRUCTOR: INADEQUATE TRAINING OF STUDENT
        REMARKS- CRASHED FROM HOVERING FLT.PREMATURE SOLO.

Aircraft

Registration
N1175K
Reported as
Brantly B-2B
Category
Helicopter
Engine
reciprocating
Damage
Substantial damage
Airport
Naples

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.