FTW68D0206

NTSB accident investigation · Piper PA-28 · Port Oconnor, TX · August 17, 1967

Accident · No injuriesClosed
Date
August 17, 1967
Place
Port Oconnor, TX · PORT OCONNOR, TX
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N9649JPiper PA-28
Status
Completed · report November 22, 1967
Report
Brief approved by the director
Case key
114710

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-2941  67/8/17    PORT OCONNOR,TEX    PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 45, 1100
        TIME - 1530                    N9649J              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 30 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MATAGORDA ISLAND
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - HIGH VEGETATION
        REMARKS- PLT LANDED ON NARROW SHELL ROAD- WINGS STRUCK HIGH,THICK WEEDS.

Aircraft

Registration
N9649J
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Matagorda Island

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.