CHI68F0278

NTSB accident investigation · Beech 35-33 · Grove City, OH · September 20, 1967

Accident · No injuriesClosed
Date
September 20, 1967
Place
Grove City, OH · GROVE CITY, OH
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N607VBeech 35-33
Status
Completed · report December 13, 1967
Report
Brief approved by the director
Case key
114329

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-3366  67/9/20    GROVE CITY,OHIO     BEECH 35-33         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1710                    N607V               PX-  0  0  3  PLEASURE/PERSONAL TRANSP  AGE 25, 900 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            40 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - MONTONEY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - PREMATURE LIFT-OFF
        REMARKS- ACFT NEAR GROSS WT,TEMP 73 DEG,NO WIND.

Aircraft

Registration
N607V
Reported as
Beech 35-33
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Montoney

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.