CHI68F0215

NTSB accident investigation · Piper PA-23 · Grand Haven, MI · July 15, 1967

Accident · No injuriesClosed
Date
July 15, 1967
Place
Grand Haven, MI · GRAND HAVEN, MI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N4634PPiper PA-23
Status
Completed · report October 11, 1967
Report
Brief approved by the director
Case key
115474

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-2349  67/7/15    GRAND HAVEN, MICH   PIPER PA-23         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1130                    N4634P              PX-  0  0  0  PRACTICE                  AGE 26, 2225 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            1125 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - GRAND HAVEN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR RETRACTED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INADVERTENTLY RETRACTED GEAR
        REMARKS- PLT SHOOTING TOUCH AND GO LNDGS.

Aircraft

Registration
N4634P
Reported as
Piper PA-23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Grand Haven

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.