FTW66D0616

NTSB accident investigation · Alon A-2 · Tulsa, OK · April 14, 1966

Accident · No injuriesClosed
Date
April 14, 1966
Place
Tulsa, OK · TULSA, OK
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N6561QAlon A-2
Status
Completed · report June 14, 1966
Report
Brief approved by the director
Case key
172094

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-0948  66/4/14    TULSA OKLA          ALON A-2            CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 44, 84 TOTAL
        TIME - 1800                    N6561Q              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 4 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - RIVERSIDE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           NOSE OVER/DOWN                                           TAKEOFF: ABORTED
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
           MISCELLANEOUS ACTS,CONDITIONS - GUST LOCKS ENGAGED

Aircraft

Registration
N6561Q
Reported as
Alon A-2
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Riverside

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.