MKC68F0538

NTSB accident investigation · Douglas A-26 · Kansas City, KS · March 16, 1968

Accident · No injuriesClosed
Date
March 16, 1968
Place
Kansas City, KS · KANSAS CITY, KS
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N61BDouglas A-26
Status
Completed · report May 23, 1968
Report
Brief approved by the director
Case key
111165

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-0830  68/3/16    KANSAS CITY,KANS    DOUGLAS A-26        CR-  0  0  2  NONCOMMERCIAL             PRIVATE, AGE 38, 7642
        TIME - 1630                    N61B                PX-  0  0  2  PRACTICE                  TOTAL HOURS, 820 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - FAIRFAX
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           TAXI: TO TAKEOFF
        PROBABLE CAUSE(S)
           AIRFRAME - LANDING GEAR: MAIN GEAR-SHOCK ABSORBING ASSY,STRUTS,ATTACHMENTS,ETC.
           MISCELLANEOUS ACTS,CONDITIONS - FATIGUE FRACTURE
        REMARKS- RT GEAR TRUNION PIVOT FITTINGS FAILED.

Aircraft

Registration
N61B
Reported as
Douglas A-26
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Fairfax

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.