FTW02LA189 · Beech BE-58
Beech BE-58 · Accident: airframe, component or system failure during initial climb
From Four Corners Regional Airport (FMN) to Four Corners Regional Airport (FMN)
Event
- NTSB case
- FTW02LA189
- 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
- Unknown
- 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
Beech BE-58
- Aircraft type
- Beechcraft BE-58
- 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
- N8245H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Four Corners Regional Airport (FMN), Farmington, NMTo Four Corners Regional Airport (FMN), Farmington, NM
- 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
- Initial climb
- 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, nose gear assembly › Failure
- Landing gear, nose gear assembly › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the takeoff/initial climb, when the main landing gear retracted a "pop-bang was heard." The two green main landing gear indicator lights and the red in-transit indicator light remained illuminated. The pilot's recycled the landing gear; however, they could not get a down and locked indication for the nose landing gear. During a low approach over the runway, company personnel observed that the nose landing gear was not locked in the down position and was at a 45 degree angle. Subsequently, the nose landing gear collapsed during the landing roll. The nose landing gear plunger assembly, part number 35-825094-4, had accumulated 10,872.5 hours. Stereoscopic and metallurgical examination of the component revealed a fatigue fracture.
Probable cause
The failure of the nose landing gear plunger assembly due to fatigue.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02LA189
- Event ID
- 20020626X00975
- Case number
- FTW02LA189
- 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, coordinates. 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: d74198159d0f74e646cbe537606dc37114278c14292e6c0cbd1ce6192ac01abf; retrieved 2026-09-22T10:48:34.636Z.