DIA67A0001

NTSB accident investigation · Brantly 305 · Manassas, VA · November 23, 1966

Accident · Minor injuriesClosed
Date
November 23, 1966
Place
Manassas, VA · MANASSAS, VA
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Uncontrolled descent
Aircraft
N2204UBrantly 305
Status
Completed · report May 24, 1967
Report
Brief approved by the director
Case key
120050

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-1039  66/11/23   MANASSAS VA         BRANTLY 305         CR-  0  0  1  MISCELLANEOUS             COMMERCIAL, FL.INSTR.,
        TIME - 1400                    N2204U              PX-  0  0  0  TEST                      AGE 41, 5000 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            25 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - HARRY P DAVIS
        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.

Aircraft

Registration
N2204U
Reported as
Brantly 305
Category
Helicopter
Engine
reciprocating
Damage
Substantial damage
Airport
Harry P Davis

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.