FTW98LA260 · Bell 206B
Bell 206B · Accident: airframe, component or system failure on approach
Event
- NTSB case
- FTW98LA260
- 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
- Charter & commuter
- 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
Bell 206B
- Aircraft type
- Bell 206
- Category
- Helicopter
- 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
- N16814
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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 135: Air Taxi & Commuter
- 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
- Approach · VFR pattern final
- 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
- Miscellaneous, bolt/nut/fastener/clamp/spring › Separation
- Pilot in command › Directional control, not possible
- Reason for occurrence undetermined
- Rotor drive system, tail rotor drive shaft › Failure
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter experienced a tail rotor drive shaft failure while on final approach to landing. Approximately 45 to 50 feet AGL, the pilot heard a 'loud snapping sound,' which was followed by a 'loss of tail rotor control.' An autorotation was initiated, and subsequently, the helicopter landed 'hard' on the grassy staging field and came to a stop upright. Examination of the helicopter revealed that two of the tail rotor drive shaft segments were fractured. Additionally, one of the two bolts connecting the aft end of one of the fractured segments to a disc coupling (Thomas Coupling) was missing. The missing bolt was not recovered, although a nut and two beveled washers were found on top of the tail boom beneath the driveshaft. An examination of the remaining bolt revealed that it exhibited fretting, wear and deformation to only the last two and one-half threads. Review of the maintenance records revealed no entries indicating that any of the tail rotor drive shaft segments were removed in the two years preceding the accident.
Probable cause
The failure of the tail rotor drive shaft due to the separation of a bolt at one of the drive shaft disc couplings for an undetermined reason, which resulted in the pilot's inability to maintain directional control during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA260
- Event ID
- 20001211X10306
- Case number
- FTW98LA260
- 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: 8ffe09e76c812368720c82d4dce1fcdec4dfa9f1446622b1727ac0cc997c1603; retrieved 2026-09-18T17:08:21.477Z.