LAX66D0383

NTSB accident investigation · Piper PA-18 · Round Mountn, NV · May 15, 1966

Accident · No injuriesClosed
Date
May 15, 1966
Place
Round Mountn, NV · ROUND MOUNTN, NV
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N2781PPiper PA-18
Status
Completed · report November 25, 1966
Report
Brief approved by the director
Case key
171979

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-2696  66/5/15    ROUND MOUNTN NEV    PIPER PA-18         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 40, 5000
        TIME - 0900                    N2781P              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 1000 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - J BAR K RANCH
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    TAXI: FROM LANDING
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        REMARKS- DURING SHARP TURN OFF RUNWAY TAIL WHEEL STRUCK RUTS AND ROCKS.

Aircraft

Registration
N2781P
Reported as
Piper PA-18
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
J Bar K Ranch

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.