ERA13FA014 · Bell 407
Acs Helicopters Bell 407 · Accident: VFR encounter with IMC en route
From Elmira Corning Regional Airport (ELM) to Westchester County Airport (HPN)
Event
- NTSB case
- ERA13FA014
- 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
- 2 · 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
- Instrument Meteorological Cond
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
- N108MF
- Operator
- Acs Helicopters
- Onboard fatalities
- Unknown
- Route
- From Elmira Corning Regional Airport (ELM), Elmira, NYTo Westchester County Airport (HPN), White Plains, NY
- Aircraft age
- About 5 years (built 2007)
- 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
- En route · cruise
- 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
- VFR encounter with IMC
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The surviving passenger reported that, after taking off, the weather "began to get worse," and the helicopter pilot advised the passengers that they would not be able to make it to their destination airport. The weather worsened, and the pilot decided to divert. When the surviving passenger looked out of the window, it was "misty and dusky." Shortly after, the helicopter struck trees and terrain. A witness reported observing the helicopter flying "very low" along the southbound lane of an interstate with all of its lights on just before the accident. He stated that the visibility was low, that the helicopter was under "low fog," and that it was like "pea soup" around the area.
Review of meteorological and GPS information indicated that dark night instrument meteorological conditions (IMC) existed in the accident area. Light rain was present, and low instrument flight rules conditions existed with vertical visibility of 200 feet and variable visibility of 1/2 mile. Before the accident, the helicopter was flying through this area of weather at a low altitude and an airspeed of about 30 knots. Although the pilot could have returned to the departure airport or landed in a suitable area along his route of flight, he chose to enter IMC despite the availability of safer options and was then forced to divert as the weather worsened. Also, once the helicopter had entered the weather, the sun had already set and minimal ground lighting was present in the heavily wooded area surrounding the interstate. Therefore, it is unlikely that a discernable horizon was present, which would have significantly increased the pilot's workload because it would have required him to reference the helicopter's flight instruments to maintain the helicopter's attitude, flightpath, energy state, and altitude.
Fuel was found onboard the helicopter, and no evidence of any preimpact failure or malfunction of the helicopter, drivetrain, or engine was found that would have precluded normal operation. Review of data recorded by the engine control unit revealed no hard faults or engine operational issues before the beginning of the accident sequence. Recorded data further indicated that the engine was running during the impact sequence and continued to operate for an additional 21 minutes following the accident while the helicopter was resting on its right side, which resulted in reduced oil flow and lubrication to the engine and the eventual postimpact failure of the turbine main line bearings and rotatable parts.
Although the pilot held an airline transport pilot certificate that allowed him to fly under IMC in airplanes, he did not possess an instrument helicopter rating. Review of information provided by the helicopter manufacturer revealed no evidence that the pilot had received any inadvertent IMC or instrument flight rules helicopter training when he was at its training center. Examination of the pilot's flight- and duty-time records also revealed that he was scheduled to fly a round trip for the airline he worked for the day after the accident occurred, which likely resulted in self-imposed pressure to complete the trip he was flying on the day of the accident so that he could return home and make his report time for his assigned trip on the following day.
Probable cause
The pilot’s decision to continue visual flight rules flight into instrument meteorological conditions due to self-imposed pressure to complete the trip, which resulted in impact with trees and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13FA014
- Event ID
- 20121010X63824
- Case number
- ERA13FA014
- 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 2012-10-10.
- API snapshot SHA-256: 3d8b926bb11abaa0e310e2fe1e3f0c2fb8b0a896b2a52d76644ca9fdb0282bfd; retrieved 2026-09-14T15:45:49.293Z.