CHI67D0053

NTSB accident investigation · Piper PA-24 · Put-In-Bay, OH · June 25, 1966

Accident · No injuriesClosed
Date
June 25, 1966
Place
Put-In-Bay, OH · PUT-IN-BAY, OH
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6483PPiper PA-24
Status
Completed · report August 15, 1966
Report
Brief approved by the director
Case key
170800

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-1614  66/6/25    PUT-IN-BAY OHIO     PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 46, 550
        TIME - 1630                    N6483P              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 487 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PUT-IN-BAY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N6483P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Put-In-Bay

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.