FTW02LA176 · Bell 206L-3
Air Evac EMS Bell 206L-3 · Accident: in flight collision with object on approach
From Paris Municipal Airport (7M6) to Dover, AR
Event
- NTSB case
- FTW02LA176
- 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
- Visual Meteorological Cond
Bell 206L-3
- 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
- N103AE
- Operator
- Air Evac EMS
- Onboard fatalities
- Unknown
- Route
- From Paris Municipal Airport (7M6), Paris, ARTo Dover, AR
- 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
- 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 collision with object
- 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
- Tree(s)
- 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
- Pilot in command › Clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The helicopter over flew the landing zone, and the pilot initiated an approach from the south. The pilot determined the helicopter was too high for the approach and initiated a go-around. On the second approach, while using the landing light, the pilot was leaning forward and scanning the area ahead when he "felt the aircraft shudder," and then realized the helicopter was in a high sink rate. The pilot applied power to arrest the descent. The helicopter had "just turned 90 degrees when it stabilized; however, not before striking a tree or trees." The pilot applied additional power to climb above the tree line. "Control response was normal except for excessive vibration in the foot pedals, resonating through the fuselage." Due to rough terrain, low illumination, and obstacles, the pilot elected to fly the helicopter to an airport south of the landing zone. The helicopter landed at the airport without further incident. Examination of the helicopter revealed that the tail rotor gearbox was partially separated from its mount, and both tail rotor blades were damaged.
Probable cause
The pilot's failure to maintain clearance with trees during the approach. A contributing factor was dark night light conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02LA176
- Event ID
- 20020613X00878
- Case number
- FTW02LA176
- 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: 734e88a926f253847775f9a8efe10c02d1b7dbb7d9cedae70bad0ddac49943a8; retrieved 2026-09-22T10:51:25.851Z.