MIA67F0157

NTSB accident investigation · Piper J3C-65 · Sanford, NC · September 5, 1966

Accident · No injuriesClosed
Date
September 5, 1966
Place
Sanford, NC · SANFORD, NC
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N91998Piper J3C-65
Status
Completed · report October 19, 1966
Report
Brief approved by the director
Case key
121049

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-2306   66/9/5    SANFORD NC          PIPER J3C-65        CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 21, 18 TOTAL
        TIME - 1000                    N91998              PX-  0  0  0  SOLO                      HOURS, 3 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SANFORD MUNI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: PARKED AIRCRAFT                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        REMARKS- PARKED AIRCRAFT BEECH 65A80 N38V SUBSTANTIAL DAMAGE.

Aircraft

Registration
N91998
Reported as
Piper J3C-65
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sanford Muni

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.