MIA67F0486

NTSB accident investigation · Piper PA-28 · Brooksville, FL · April 2, 1967

Accident · No injuriesClosed
Date
April 2, 1967
Place
Brooksville, FL · BROOKSVILLE, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N7001RPiper PA-28
Status
Completed · report August 30, 1967
Report
Brief approved by the director
Case key
117457

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-1071   67/4/2    BROOKSVILLE,FLA     PIPER PA-28         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 24, 13 TOTAL
        TIME - 1030                    N7001R              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - BROOKSVILLE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           GEAR COLLAPSED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N7001R
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Brooksville

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.