FTW68D0300

NTSB accident investigation · Bellanca 17-30 · Van Horn, TX · October 21, 1967

Accident · No injuriesClosed
Date
October 21, 1967
Place
Van Horn, TX · VAN HORN, TX
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6664VBellanca 17-30
Status
Completed · report January 3, 1968
Report
Brief approved by the director
Case key
113267

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-3774  67/10/21 NR.VAN HORN,TEX       BELLANCA 17-30      CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 42, 1000
        TIME - 1000                    N6664V              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 128 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        REMARKS- LEFT GEAR STRUCK LARGE ROCK ON COUNTRY ROAD.

Aircraft

Registration
N6664V
Reported as
Bellanca 17-30
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.