FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA273 · Bell Helicopter Textron 206L-1

6 Jun 2013 · Manchester, KY, United States

Air Evac EMS Bell Helicopter Textron 206L-1 · Accident: loss of control in flight on approach

From St Joseph - London Heliport (5KY9) to Manchester, KY

Report a problem

Event

NTSB case
ERA13FA273
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
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 Helicopter Textron 206L-1

Aircraft type
Bell 206
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
N114AE
Operator
Air Evac EMS
Onboard fatalities
Unknown
Route
From St Joseph - London Heliport (5KY9), London, KYTo Manchester, KY
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
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
Approach · VFR pattern final
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
Loss of control in flight
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 propeller/rotor
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The air ambulance repositioning flight was en route to base following a patient transfer. Weather information forecast about 3 hours before the accident indicated a moist environment; however, visual conditions were anticipated around the time of the accident. An updated forecast was published about 10 minutes before the accident, and it indicated that fog or low stratus cloud development was possible and that visibility could decrease to near or below airport weather minimums in the early morning hours. Witness statements and the reported weather conditions indicated that patchy fog had developed near the helipad at the time of the accident and that visibility at the accident site was 1/4 mile; however, the specific visibility conditions encountered by the helicopter during its approach could not be determined. A witness reported seeing the helicopter "flying lower than normal" and then spinning before impact. Another witness reported seeing the helicopter in a nose-down attitude and then impact the ground.

The wreckage was located in a school parking lot, which was about 750 feet from the landing pad and at an elevation of about 900 feet mean sea level (msl). The wreckage distribution was consistent with an in-flight separation of the main rotor and tailboom. An examination of the helicopter airframe, engine, and related systems revealed no preimpact anomalies that would have precluded normal operation. Both the main rotor assembly and tailboom separated in overload.

Review of GPS data showed the accident helicopter descending in three right circuits near the landing pad just before the accident. The final recorded data were in the immediate vicinity of the accident location and indicated an altitude of 1,437 feet msl. The maneuvering flightpath of the helicopter before the accident was consistent with an attempt to avoid fog followed by a loss of control. Although the pilot was instrument rated, he had not logged recent instrument time. Further, although the pilot had recent training in night vision goggle usage and had night vision goggles available during the flight, it could not be determined if he was using them at the time of the accident. Given the reports of fog in the area and the accident circumstances, it is likely that the pilot entered instrument meteorological conditions during the approach to the helipad, which resulted in spatial disorientation and loss of control.

Probable cause

The pilot’s loss of helicopter control due to spatial disorientation when he inadvertently encountered night, instrument meteorological conditions, which resulted in the in-flight separation of the main rotor and tailboom.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA273
Event ID
20130607X04715
Case number
ERA13FA273
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 2013-06-07.
  • API snapshot SHA-256: 28ffbb6c4dc051e7f99c9ef779d14ab536e5763c153bc6adee48f1ef4e38c16c; retrieved 2026-09-14T15:58:07.780Z.