MIA68F0533

NTSB accident investigation · Cessna 150 · Montgomery, AL · May 15, 1968

Accident · No injuriesClosed
Date
May 15, 1968
Place
Montgomery, AL · MONTGOMERY, AL
Injuries
1 uninjured
Damage
Destroyed
Phase of flight
Landing
Aircraft
N7126XCessna 150
Status
Completed · report July 2, 1968
Report
Brief approved by the director
Case key
111031

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-1393  68/5/15    MONTGOMERY,ALA      CESSNA 150          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 30, 18 TOTAL
        TIME - 1340                    N7126X              PX-  0  0  0  TRAINING                  HOURS, 8 IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - GUNTER AFB
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           AIRFRAME - LANDING GEAR: NOSEWHEEL ASSEMBLIES
           MISCELLANEOUS ACTS,CONDITIONS - FATIGUE FRACTURE
         FIRE AFTER IMPACT
        REMARKS- OLD CRACKS FOUND ON LFT AND RT SIDE OF NOSE WHEEL FORK. NOSE GEAR BROKE GASCOLATOR BOWL.

Aircraft

Registration
N7126X
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Gunter Afb

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.