NYC67F0088

NTSB accident investigation · Piper PA-24 · Chester, MD · July 10, 1966

Accident · Minor injuriesClosed
Date
July 10, 1966
Place
Chester, MD · CHESTER, MD
Injuries
1 minor, 2 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N8361PPiper PA-24
Status
Completed · report August 22, 1966
Report
Brief approved by the director
Case key
170855

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-1748  66/7/10    CHESTER MD          PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 55, 1300
        TIME - 1310                    N8361P              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 502 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CARROLLS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - PREMATURE LIFT-OFF
        FACTOR(S)
           PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND
        REMARKS- WIND VARIABLE TO QUARTERING TAILWIND.

Aircraft

Registration
N8361P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Carrolls

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.