FTW68F0150

NTSB accident investigation · Alon A-2 · Fabens, TX · August 8, 1967

Accident · Minor injuriesClosed
Date
August 8, 1967
Place
Fabens, TX · FABENS, TX
Injuries
1 minor, 1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6599QAlon A-2
Status
Completed · report October 30, 1967
Report
Brief approved by the director
Case key
115111

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-2671   67/8/8    FABENS,TEX          ALON A-2            CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 34, 192
        TIME - 1400                    N6599Q              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 140 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FABENS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - FAILED TO INITIATE GO-AROUND

Aircraft

Registration
N6599Q
Reported as
Alon A-2
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Fabens

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.