Viking Aviation Bell 407 accident
Bell 407 · Accident en route
From Grove City, OH to Pomeroy, OH
Event
- NTSB case
- CEN19FA072
- 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
- 3 · 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Unknown
Bell 407
- Aircraft type
- Bell 407
- 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
- N191SF
- Operator
- Viking Aviation
- Onboard fatalities
- Unknown
- Route
- From Grove City, OHTo Pomeroy, OH
- Aircraft age
- About 23 years (built 1996)
- 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
- En route
- 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
- Unknown or undetermined
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Physical environment
- Organizational issues › Management
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
NTSB investigators traveled in support of this investigation and used data obtained from various sources to prepare this aircraft accident report.
The NTSB's full report is available at http://www.ntsb.gov/investigations/AccidentReports/Pages/AccidentReports.aspx. The Aircraft Accident Report number is NTSB/AAR-20/01.
On January 29, 2019, about 0650 eastern standard time, a single-engine, turbine-powered Bell 407 helicopter, N191SF, being operated as a helicopter air ambulance (HAA) flight, collided with forested terrain about 4 miles northeast of Zaleski, Ohio. The certificated commercial pilot, flight nurse, and flight paramedic died, and the helicopter was destroyed. The helicopter was registered to and operated by Viking Aviation, LLC, doing business as Survival Flight Inc., under Title 14 Code of Federal Regulations Part 135. Company flight-following procedures were in effect for the visual flight rules (VFR) flight, which departed Mount Carmel Hospital, Grove City, Ohio, about 0628 and was destined for Holzer Meigs Emergency Department, Pomeroy, Ohio, about 69 nautical miles southeast, to pick up a patient. Night visual meteorological conditions existed at the departure location, but available weather information indicated that snow showers and areas of instrument meteorological conditions (IMC) existed along the route of flight.
Probable cause
The NTSB determines that the probable cause of this accident was Survival Flight's inadequate management of safety, which normalized pilots' and operations control specialists' noncompliance with risk analysis procedures and resulted in the initiation of the flight without a comprehensive preflight weather evaluation, leading to the pilot's inadvertent encounter with instrument meteorological conditions, failure to maintain altitude, and subsequent collision with terrain. Contributing to the accident was the Federal Aviation Administration's inadequate oversight of the operator's risk management program and failure to require Title 14 Code of Federal Regulations Part 135 operators to establish safety management system programs.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19FA072
- Event ID
- 20190129X14921
- Case number
- CEN19FA072
- 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: 4e562bc8230abbdb59567802ae76710bf4c95587062709d38aa6b4d4c4596cb0; retrieved 2026-09-15T06:53:23.647Z.