FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI98LA272 · Cessna 140

23 Jul 1998 · Falls City, NE, United States

Cessna 140 · Accident: airframe, component or system failure during landing

From Neubrandenburg Trollenhagen Airport (FNB) to Neubrandenburg Trollenhagen Airport (FNB)

Report a problem

Event

NTSB case
CHI98LA272
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 140

Aircraft type
Cessna 140
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N76601
Operator
Unknown
Onboard fatalities
Unknown
Route
From Neubrandenburg Trollenhagen Airport (FNB)To Neubrandenburg Trollenhagen Airport (FNB)
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Landing gear, main gear strut › Fractured

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During the tailwheel airplane's landing roll, its left landing gear leg fractured and separated where the entrance step bolt hole goes through the leg. The airplane ground looped to the left. During the ground loop event the pilot's seat belt mounting bracket separated and the pilot was ejected through the left door. The seat belt mount was made from aluminum rather than the steel the manufacturer said it should have been made from. Fracture surfaces on the separated gear leg show a grainy surface texture. All 4 edges had shear lips on them. There was a series of small arrowhead shapes originating from the gear's leading edge and progressing aft to a point about midway between the bolt hole and leading edge.

Probable cause

the main landing gear leg fracturing and separating from the portion mounted to the fuselage for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI98LA272
Event ID
20001211X10523
Case number
CHI98LA272
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 4e3018f4589c4a77aafa3510d21b87401c12c0b775b5b5dac71c5d7f96dba3fd; retrieved 2026-09-21T20:45:25.530Z.