MKC68F0534

NTSB accident investigation · Cessna 182E · Omaha, NE · April 26, 1968

Accident · No injuriesClosed
Date
April 26, 1968
Place
Omaha, NE · OMAHA, NE
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N3295YCessna 182E
Status
Completed · report May 23, 1968
Report
Brief approved by the director
Case key
111273

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-0928  68/4/26    OMAHA,NEBR          CESSNA 182E         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 46, 500
        TIME - 0932                    N3295Y              PX-  0  0  1  BUSINESS                  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - EPPLEY FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           AIRFRAME - LANDING GEAR: NOSEWHEEL ASSEMBLIES
           MISCELLANEOUS ACTS,CONDITIONS - PREVIOUS DAMAGE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - VIBRATION,EXCESSIVE
        REMARKS- NOSE WHEEL FORK FAILED.

Aircraft

Registration
N3295Y
Reported as
Cessna 182E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Eppley Field

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.