DEN07IA048 · Raytheon B300
Central Missouri Aviation Raytheon B300 · Incident: airframe, component or system failure during landing
From Columbia Regional Airport (COU) to Centennial Airport (APA)
Event
- NTSB case
- DEN07IA048
- 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
- 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
Raytheon B300
- Aircraft type
- Beechcraft 300
- 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
- N945SH
- Operator
- Central Missouri Aviation
- Onboard fatalities
- Unknown
- Route
- From Columbia Regional Airport (COU), Columbia, MOTo Centennial Airport (APA), Englewood, 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
- Landing · flare/touchdown
- 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
- Landing gear, nose gear assembly › Fractured
- Pilot in command › Directional control, not possible
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane landed, drifted left, and struck a snowbank. The wind was from 130 degrees at 6 knots and braking action was "good." A portion of the nose landing gear upper torque knee was found on the runway. The remainder of the upper torque knee and the entire lower torque knee remained attached to the nose landing gear. These items were sent to NTSB's Materials Laboratory for metallurgical examination. According to the metallurgist's factual report, the lower torque knee was fractured in overstress at two locations: on the forward and on the aft sides of the pivot fastener bore. The aft fracture was consistent with the lower knee being loaded in tension. The forward fracture was more extensively deformed, indicating it was secondary to the aft fracture. The smaller, separated piece of the lower knee showed significant elongation and deformation of the pivot bore, consistent with the forward end of the lower knee moving downward and forward relative to the upper knee. Deformation at the fracture through the grease-fitting hole at the forward fracture location was indicative of bending and twisting out of the plane of pivot. There was no evidence of preexisting cracking, corrosion, or damage.
Probable cause
THIS CASE WAS MODIFIED 10/30/2007
Failure of the nose landing gear upper torque knee due to overstress, and the pilot's inability to maintain aircraft control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN07IA048
- Event ID
- 20070129X00098
- Case number
- DEN07IA048
- 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: b089dde9e4d38a1f03986c0e6fbc2ad1442694aef3804f3210b994c4fe5f6a2f; retrieved 2026-09-22T04:05:40.692Z.