DEN84IA241 · de Havilland DHC-7-100
de Havilland DHC-7-100 · Incident: airframe, component or system failure during initial climb
From Casper-Natrona County International Airport (CPR) to Denver International Airport (DEN)
Event
- NTSB case
- DEN84IA241
- 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
- Incident
- 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
de Havilland DHC-7-100
- Aircraft type
- de Havilland DHC-7
- 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
- N9058P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Casper-Natrona County International Airport (CPR), Casper, WYTo Denver International Airport (DEN), Denver, CO
- 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
- Minor
Cause areas
- Company maintenance personnel › Maintenance, installation, improper
- Landing gear, main gear shock absorbing strut › Separation
- Landing gear, main gear › Separation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE LEFT MAIN LANDING GEAR WAS DISASSEMBLED & REASSEMBLED BY COMPANY MAINTENANCE PERSONNEL & THE ACFT WAS BEING FERRIED TO ANOTHER BASE FOR PERMANENT LANDING GEAR REPAIRS. DURING TAKEOFF, THE LEFT MAIN LANDING GEAR AND SHOCK STRUT SEPERATED FROM THE ACFT. THE PLT MADE AN EMERG LANDING WITHOUT THE LEFT MAIN GEAR WHEELS. AN EXAM OF THE GEAR REVEALED THAT THE UPPER BEARING HALVES & PISTON DAMPING RING WERE INSTALLED USING THE MAINTENANCE MANUAL. REVIEW OF THE MAINTENANCE MANUAL REVEALED THAT THE LANDING GEAR ASSEMBLY PROCEDURES WERE MISLEADING. THE MANUFACTURER ISSUED A TEMP REVISION TO THE MANUAL FOR LANDING GEAR ASSEMBLY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN84IA241
- Event ID
- 20001214X40270
- Case number
- DEN84IA241
- 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: 6dfa3a224215033285023767ebf00a751a6d3b85434e3dc74c585a76f8926907; retrieved 2026-09-23T20:02:15.357Z.