NTSB Releases Preliminary Report From Ohio Medical Helicopter Accident | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Most Recent Daily Episodes

Episode Date

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday Airborne-Thursday

Airborne-Friday

Airborne On YouTube

Airborne-Unlimited-04.22.24

Airborne-Unlimited-04.16.24

Airborne-FlightTraining-04.17.24 Airborne-AffordableFlyers-04.18.24

Airborne-Unlimited-04.19.24

Join Us At 0900ET, Friday, 4/10, for the LIVE Morning Brief.
Watch It LIVE at
www.airborne-live.net

Fri, Feb 15, 2019

NTSB Releases Preliminary Report From Ohio Medical Helicopter Accident

Aircraft Made Sharp Turns Before Impacting Terrain

The NTSB has released its preliminary report from an accident which occurred on January 29, 2019, at 0650 Eastern standard time in Ohio. The single-engine, turbine-powered, Bell 407 helicopter collided with forested, rising terrain about 4 miles northeast of Zaleski, Ohio. The aircraft was registered to and operated by Viking Aviation, LLC, doing business as Survival Flight, Inc., as a visual flight rules helicopter air ambulance flight under the provisions of 14 Code of Federal Regulations Part 135 when the accident occurred.

The certificated commercial pilot, flight nurse, and flight paramedic were fatally injured, and the helicopter was destroyed. Visual meteorological conditions existed at the departure location, and company flight following procedures were in effect. The flight departed Mt. Carmel Hospital, Grove City, Ohio at 0628, destined for Holzer Meigs Hospital, Pomeroy, Ohio, about 69 miles southeast.

According to the Survival Flight Operations Control Specialist (OCS) on duty at the time of the accident, the night shift pilot had originally accepted the flight. The OCS said that, while he was on the phone with that pilot reviewing flight details about 0612, he was told that, due to the upcoming shift change, the day pilot would be taking the flight.

The OCS said that, while watching the helicopter on flight tracking software in the Operations Control Center, he observed that, about 15 minutes after departure, the helicopter made a turn to the right, then "a sharp left turn," which was immediately followed by a "no-tracking alarm." The emergency action plan was then initiated.

The helicopter wreckage was located on a tree-covered hill and exhibited significant fragmentation. The wreckage and debris path extended about 600 ft downslope on a heading of about 345° magnetic. A portion of the front-left skid tube was found at the start of the wreckage path, followed by the main rotor hub and blades, tail boom and tail rotor, cockpit and cabin, and the engine and transmission deck. Tree branches broken about 30 ft above ground level were observed near the front-left skid tube. Additionally, one main rotor blade had separated from the main rotor hub and was embedded in a tree. The elevation of the wreckage area ranged from 850 to 980 ft above mean sea level (msl). There was no evidence of a postcrash fire, but a strong smell of fuel was reported by first responders when the wreckage was first discovered.

The helicopter was equipped with an Outerlink Global Solutions IRIS flight data monitoring system, which provides real-time flight tracking data. The flight tracking information is relayed via satellites to an internet-based storage location in 10-second intervals. According to the IRIS data, the helicopter's last known location was about 4 miles northeast of Zaleski at an altitude of 1,528 ft msl, traveling at 132 knots across the ground, on a course of 072°. In addition to the transmission of data at 10-second intervals, the IRIS stores flight data in 1-second intervals, along with voice and satellite communications. The equipment was removed and sent to the NTSB Vehicle Recorders Laboratory for voice and data extraction.

(Ohio State Patrol image)

FMI: Report

Advertisement

More News

Airborne 04.16.24: RV Update, Affordable Flying Expo, Diamond Lil

Also: B-29 Superfortress Reunion, FAA Wants Controllers, Spirit Airlines Pulls Back, Gogo Galileo Van's Aircraft posted a short video recapping the goings-on around their reorganiz>[...]

ANN's Daily Aero-Term (04.20.24): Light Gun

Light Gun A handheld directional light signaling device which emits a brilliant narrow beam of white, green, or red light as selected by the tower controller. The color and type of>[...]

Aero-News: Quote of the Day (04.20.24)

"The journey to this achievement started nearly a decade ago when a freshly commissioned Gentry, driven by a fascination with new technologies and a desire to contribute significan>[...]

Aero-News: Quote of the Day (04.21.24)

"Our driven and innovative team of military and civilian Airmen delivers combat power daily, ensuring our nation is ready today and tomorrow." Source: General Duke Richardson, AFMC>[...]

ANN's Daily Aero-Term (04.21.24): Aircraft Conflict

Aircraft Conflict Predicted conflict, within EDST of two aircraft, or between aircraft and airspace. A Red alert is used for conflicts when the predicted minimum separation is 5 na>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2024 Web Development & Design by Pauli Systems, LC