DEN67F0213

NTSB accident investigation · Bellanca 14-19 · Albuquerque, NM · February 28, 1967

Accident · No injuriesClosed
Date
February 28, 1967
Place
Albuquerque, NM · ALBUQUERQUE, NM
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8835RBellanca 14-19
Status
Completed · report August 10, 1967
Report
Brief approved by the director
Case key
118456

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-0644  67/2/28    ALBUQUERQUE,N MEX   BELLANCA 14-19      CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 45, 134
        TIME - 1245                    N8835R              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 11 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CORONADO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N8835R
Reported as
Bellanca 14-19
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Coronado

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.