FTW67D0478

NTSB accident investigation · Piper PA-32 · Longview, TX · February 18, 1967

Accident · No injuriesClosed
Date
February 18, 1967
Place
Longview, TX · LONGVIEW, TX
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N4048WPiper PA-32
Status
Completed · report July 27, 1967
Report
Brief approved by the director
Case key
119006

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-0528  67/2/18    LONGVIEW,TEX        PIPER PA-32         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 25, 294
        TIME - 0700                    N4048W              PX-  0  0  2  BUSINESS                  TOTAL HOURS, 8 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - GREGG COUNTY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: PARKED AIRCRAFT                           TAXI: TO TAKEOFF
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - TAXIED/PARKED WITHOUT PROPER ASSISTANCE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - CONGESTED TRAFFIC-PATTERN
        REMARKS- PARKED AIRCRAFT N6239Y,SUBSTANTIAL DAMAGE.

Aircraft

Registration
N4048W
Reported as
Piper PA-32
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Gregg County

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.