CEN16CA393 · Bell 230
Sanford Health Bell 230 · Accident: collision during takeoff/landing
From Hector International Airport (KFAR) to St. Luke's Hospital Heliport (ND48)
Event
- NTSB case
- CEN16CA393
- 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
- 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
Bell 230
- Aircraft type
- Bell 230
- 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
- N903SH
- Operator
- Sanford Health
- Onboard fatalities
- Unknown
- Route
- From Hector International Airport (KFAR), Fargo, NDTo St. Luke's Hospital Heliport (ND48), Fargo, ND
- Aircraft age
- About 22 years (built 1994)
- 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
- 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
- Collision during takeoff/landing
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Pole
- 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
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Physical environment
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he performed his approach into the wind. On short final he could feel periodic gusts of wind. The pilot executed the standard approach to the helipad and the helicopter encountered another gust that picked the helicopter's nose up as it was moving over the pad. He maneuvered the helicopter to center it over the pad when he heard a sound like "metal on metal as if the tail rotor had hit something a couple times." The pilot felt no initial feedback in the controls, he felt the helicopter yaw to the left, and the helicopter continued to yaw to the left with his full application of right pedal. He lowered the collective and rolled off the throttle to enter a hovering autorotation and attempted to land it as level as possible. The helicopter landed hard. The operator reported substantial ground damage occurred to the tail rotor gearbox and tail rotor blades and a review of images revealed damage to the tailboom. A nearby fence and light were reported to be damaged. The operator's accident report indicated that there were no mechanical malfunctions with the helicopter.
Probable cause
The pilot's failure to maintain clearance from the ground obstacle during the landing with gusting winds present.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16CA393
- Event ID
- 20161005X73536
- Case number
- CEN16CA393
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-09-30.
- API snapshot SHA-256: e23998a19c04cdf011ea2daa89cbd13a6244bb520623b3764c600fe4ec81b16c; retrieved 2026-09-16T04:21:34.244Z.