LAX72DUQ03

NTSB accident investigation · Piper PA-18 · Rosamond, CA · July 5, 1971

Accident · No injuriesClosed
Date
July 5, 1971
Place
Rosamond, CA · ROSAMOND, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8079DPiper PA-18
Status
Completed · report March 3, 1972
Report
Brief approved by the director
Case key
162541

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-2516   71/7/5    ROSAMOND,CALIF      PIPER PA-18         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 34, 116
        TIME - 1830                    N8079D              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 47 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - ROSAMOND
        DEPARTURE POINT             INTENDED DESTINATION
          PORTERVILLE,CALIF           ROSAMOND,CALIF
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL

Aircraft

Registration
N8079D
Reported as
Piper PA-18
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Rosamond

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.