FTW68D0471

NTSB accident investigation · Piper PA-28 · Lubbock, TX · February 27, 1968

Accident · No injuriesClosed
Date
February 27, 1968
Place
Lubbock, TX · LUBBOCK, TX
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N8236WPiper PA-28
Status
Completed · report April 3, 1968
Report
Brief approved by the director
Case key
111966

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-0449  68/2/27    LUBBOCK,TEX         PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 51, 6000
        TIME - 1545                    N8236W              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 60 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - LUBBOCK SOUTH
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - SUNGLARE
        REMARKS- LANDED SUCCESSFULLY.

Aircraft

Registration
N8236W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Lubbock South

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.