FTW77FQG16

NTSB accident investigation · Beech V35B · Lubbock, TX · March 20, 1977

Accident · No injuriesClosed
Date
March 20, 1977
Place
Lubbock, TX · LUBBOCK, TX
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4096ABeech V35B
Status
Completed · report May 18, 1977
Report
Brief approved by the director
FAA report
19770320007679A
Case key
157281

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-0600  77/3/20    LUBBOCK,TX          BEECH V35B          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 30, 371
        TIME - 1255                    N4096A              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 216 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - LUBBOCK REGIONAL
        DEPARTURE POINT             INTENDED DESTINATION
          MIDLAND,TX                  LUBBOCK,TX
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO ASSURE THE GEAR WAS DOWN AND LOCKED

Aircraft

Registration
N4096A
Reported as
Beech V35B
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Lubbock Regional

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.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.