FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI06LA074 · Bell 206L-1

2 Feb 2006 · Chesterfield, IN, United States

Bell 206L-1 · Accident: in flight encounter with weather while maneuvering

From Anderson Municipal Darlington Field (AID) to Kokomo, IN

Report a problem

Event

NTSB case
CHI06LA074
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
Instrument Meteorological Cond

Bell 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
N593AE
Operator
Unknown
Onboard fatalities
Unknown
Route
From Anderson Municipal Darlington Field (AID), Anderson, INTo Kokomo, IN
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
Maneuvering
First occurrenceThe 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
In flight encounter with weather
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC); Tree(s); Wire, transmission
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The emergency medical service (EMS) flight was dispatched at night to pickup a patient from a hospital. The pilot reported that after receiving the dispatch orders he went outside to assess the current weather conditions, which he described as being a "little hazy." The pilot then obtained the local weather radar depiction and surface weather conditions. The pilot determined the weather at the departure and destination was suitable for visual flight rules (VFR) operations. The pilot did not listen to the airport's automated weather observing system (AWOS) broadcast before departure. The helicopter departed and almost immediately entered instrument meteorological conditions. He elected to terminate the flight and began a right turn back toward the departure airport. The pilot stated that he had difficultly maintaining level flight and felt that the helicopter was climbing slightly during the turn. He thought the attitude indicator was giving a false indication because it was not moving and was "cocked off center about 30 degrees." The pilot verified that the circuit breaker for the attitude indicator was not tripped. He saw some ground lighting to the left of the helicopter and started a left turn toward the lights. The pilot remembered seeing two houses before impact and attempted to steer the helicopter between them. Global positioning system (GPS) data showed the helicopter departing to the north, and then it made a climbing right turn, followed by a climbing left turn. The helicopter's maximum recorded altitude during the left turn was about 1,035 feet above ground level (agl). The helicopter impacted two pine trees, utility lines, a residential structure, a tree, and a garage before coming to a stop. The helicopter traveled about 325 feet from the initial contact with the two pine trees to its final position. The local weather conditions were continually broadcast and accessible using a telephone or radio. About one hour before the accident, the airport's AWOS indicated that the sky was overcast at 400 feet agl and the surface visibility was 3 sm with mist. About two minutes after the accident, the airport's AWOS indicated that the sky was overcast at 400 feet agl and the ground visibility was 2 1/2 sm. During the accident flight, the helicopter was operating in instrument meteorological conditions (IMC). The pilot held an instrument rating, but the accident helicopter was not certified for flight in IMC. According to company documentation, the pilot had logged 26 hours of instrument experience since being hired in 1989. He had flown 13 hours during the prior 90 days, none of which were in IMC. The attitude indicator was bench-tested and no discrepancies were noted with its operation.

Probable cause

The pilot's failure to maintain aircraft control after becoming spatially disorientated shortly after departure. Contributing to the accident was the pilot's inadequate preflight weather evaluation, his inadvertent flight into night instrument meteorological conditions, and the ground objects that the helicopter impacted during the descent.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI06LA074
Event ID
20060210X00193
Case number
CHI06LA074
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: eed0214a6b5e6880c3eacb20a549649f44ac998c21ac967313e3df5f2768cf8c; retrieved 2026-09-21T09:00:19.658Z.