NYC67F0039

NTSB accident investigation · Piper PA28 · Eagles Mere, PA · July 3, 1966

Accident · No injuriesClosed
Date
July 3, 1966
Place
Eagles Mere, PA · EAGLES MERE, PA
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7813WPiper PA28
Status
Completed · report August 12, 1966
Report
Brief approved by the director
Case key
171394

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-1551   66/7/3    EAGLES MERE PENN    PIPER PA28          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 23, 392
        TIME - 1307                    N7813W              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 345 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - EAGLES MERE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N7813W
Reported as
Piper PA28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Eagles Mere

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.