FTW90LA025 · Beech 95
B & H Aviation Beech 95 · Accident: airframe, component or system failure en route
From F67 · Grand Prairie, TX to Q41
Event
- NTSB case
- FTW90LA025
- 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
Beech 95
- Aircraft type
- Beechcraft 95
- 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
- N17AT
- Operator
- B & H Aviation
- Onboard fatalities
- Unknown
- Route
- From F67 · Grand Prairie, TXTo Q41
- 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
- En route · cruise
- 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
- Propeller system/accessories › Separation
- Propeller system/accessories, prop blade retention › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE THE AIRPLANE WAS AT CRUISE, THE RIGHT PROPELLER SPINNER FELL OFF. THREE OR FOUR MINUTES LATER, THE RIGHT PROPELLER CAME OFF AND CUT INTO THE NOSE OF THE AIRPLANE. WITH NO ELECTRICAL POWER, AND DETERIORATED AIRPLANE CONTROL, THE PILOT MADE A WHEELS-UP LANDING ON THE DESTINATION AIRPORT. THE RIGHT PROPELLER AND THE CENTER OF THE STARTER RING WERE NOT RECOVERED. FIVE OF THE PROPELLER ATTACHMENT BOLTS REMAINED IN THE ENGINE CRANKSHAFT FLANGE. LABORATORY VISUAL INSPECTION INDICATED FOUR OF THESE BOLTS FAILED FROM FATIGUE AND THE FIFTH FAILED FROM OVERLOAD.
Probable cause
FAILURE OF THE PROPELLER ATTACHMENT BOLTS DUE TO FATIGUE IN FOUR OF THE BOLTS AND OVERLOAD IN ANOTHER. A CONTRIBUTING FACTOR WAS THE LOSS OF ELECTRICAL POWER AND THE DETERIORATED AIRPLANE CONTROL/PREFORMANCE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW90LA025
- Event ID
- 20001213X29798
- Case number
- FTW90LA025
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1989-11-11.
- API snapshot SHA-256: 963e3bed2fce0a5bac82c676ce896ee53cb19ea9ea881625a6912b1b74f02da6; retrieved 2026-09-23T06:59:31.626Z.