WPR10TA318 · Bell UH-1H
Santa Barbara County Fire Bell UH-1H · Accident: system/component malfunction/failure (non-power) while maneuvering
From Santa Barbara, CA to Santa Barbara, CA
Event
- NTSB case
- WPR10TA318
- 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
- Government
- 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 UH-1H
- Aircraft type
- Bell UH-1
- 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
- N205KS
- Operator
- Santa Barbara County Fire
- Onboard fatalities
- Unknown
- Route
- From Santa Barbara, CATo Santa Barbara, CA
- 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
- Public Aircraft
- 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
- Maneuvering · hover
- Defining eventThe 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
- System/component malfunction/failure (non-power)
- 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
- Aircraft › Aircraft structures
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter experienced a structural failure in one of the tailboom attach fittings while hovering near a cliff, about 200 feet above ground level (agl). The pilot heard a loud sound and felt the helicopter yaw slightly. He made a precautionary landing without incident. A postaccident examination of the helicopter revealed the left tailboom upper attachment fitting had fractured as a result of fatigue. The fatigue origin most likely emanated from fretting and/or corrosion pits at the fastener to fitting interface. There was no engineering data showing how the combination of the multiple STC modifications of the helicopter affected the helicopter's structural integrity.
Probable cause
The failure of left tailboom upper attachment fitting as a result of fatigue.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10TA318
- Event ID
- 20100630X10303
- Case number
- WPR10TA318
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 36b4ffca1eb7cde680f526f89d518df47486041fca6f2971f622c21702dadc2c; retrieved 2026-09-15T14:33:32.992Z.