SEA67F0077

NTSB accident investigation · Piper PA-24 · Laurel, MT · August 7, 1966

Accident · No injuriesClosed
Date
August 7, 1966
Place
Laurel, MT · LAUREL, MT
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N6593PPiper PA-24
Status
Completed · report March 9, 1967
Report
Brief approved by the director
Case key
121302

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-3779   66/8/7    LAUREL MONT         PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 29, 200
        TIME - 1900                    N6593P              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 50 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - LAUREL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
           PILOT IN COMMAND - EXERCISED POOR JUDGMENT
        REMARKS- PILOT TOOK OFF WITH HEAVY LOAD ON RUNWAY WITH 1.89 PCT. UPSLOPE GRADE, 15 KNOT 105 DEG R.CROSSWIND

Aircraft

Registration
N6593P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Laurel

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.