SEA66D0030

NTSB accident investigation · Piper PA-22 · Rosalia, WA · June 26, 1965

Accident · No injuriesClosed
Date
June 26, 1965
Place
Rosalia, WA · ROSALIA, WA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N2603PPiper PA-22
Status
Completed · report September 7, 1965
Report
Brief approved by the director
Case key
177652

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-1938  65/6/26    ROSALIA WASH        PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 43, 1200
        TIME - 1900                    N2603P              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 400 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - ROSALIA AIRPORT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: AIRPORT HAZARD                            TAXI: FROM LANDING
           GEAR COLLAPSED                                           TAXI: FROM LANDING
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        REMARKS- NOSE WHEEL STRUCK BADGER HOLE IN TALL GRASS.

Aircraft

Registration
N2603P
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Rosalia Airport

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.