FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW97LA270 · Bell 206L-1

17 Jul 1997 · Amelia, LA, United States

Bell 206L-1 · Accident: partial loss of engine power (non-mechanical) during initial climb

From 7R3 to SHIP SHOAL 214, GM

Report a problem

Event

NTSB case
FTW97LA270
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
0
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-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
N3892R
Operator
Unknown
Onboard fatalities
Unknown
Route
From 7R3To SHIP SHOAL 214, GM
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
Initial climb
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
Partial loss of engine power (non-mechanical)
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

  • Miscellaneous, engine compressor stall/surge
  • Turboshaft engine › Foreign object
  • Turboshaft engine › Ingested

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

NTSB narrative

After completing hover checks, the pilot initiated a takeoff through a cut in the trees. At about 60 feet AGL and 40 knots, a 'loud bang' occurred. The helicopter 'yawed left and the rotor rpm began to decay.' The pilot initiated an autorotation and made a 'hard/steep right turn' towards the only available landing area 75 yards to his right rear. The helicopter landed hard on its right skid and rolled over coming to rest on its right side. The engine was test run, and its performance exceeded new engine specifications. Following the test run, the engine was partially disassembled and inspected. Indications of blood and flesh were found in the impeller and through the compressor air discharge tubes. This finding was consistent with other engines that had been examined and found to have ingested green tree frogs. The pilot also reported that during his preflight inspection, he did not observe any green tree frogs.

Probable cause

partial loss of engine power due to frog(s) being ingested into the engine. Factors relating to the accident were: the lack of altitude and lack of suitable terrain for a forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW97LA270
Event ID
20001208X08382
Case number
FTW97LA270
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. 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: 4bf950f7742d9364f8303f138b1970805cd94c00449cc502b890dd3b143bc8e6; retrieved 2026-09-22T19:07:45.333Z.