ATL89FA200 · Bell 206B
Bell 206B · Accident: loss of engine power en route
From Tuscaloosa, AL to Anniston, AL
Event
- NTSB case
- ATL89FA200
- 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 206B
- 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
- N117V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tuscaloosa, ALTo Anniston, AL
- 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
- En route · holding (IFR)
- 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
- Loss of engine power
- 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 › Emergency procedure, not followed
- Pilot in command › Rotorcraft flight controls, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
REPORTEDLY, THE PILOT EXPERIENCED A COMPLETE ENGINE FAILURE WHILE PATROLLING UTILITY LINES AT 700 FEET AGL. HE ENTERED AN AUTOROTATIVE GLIDE TO AN OPEN FIELD. THE PILOT STATED THAT HE HAD TO AVOID TREES CLOSE TO THE GROUND, AT WHICH TIME MAIN ROTOR RPM DECAYED. THE PILOT COULD NOT LEVEL THE HELICOPTER BEFORE THE TAIL ROTOR STRUCK THE GROUND. THE HELICOPTER EXAMINATION FAILED TO DISCLOSE ANY MECHANICAL PROBLEM. THE ENGINE AND ATTACHED COMPONENTS WERE EXAMINED, AND NO MATERIAL OR SYSTEM MALFUNCTION WAS DETECTED. HOWEVER, THE HELICOPTER WAS CAPABLE OF AUTOROTATING NORMALLY. THE PILOT ALLOWED THE ROTOR RPM TO DECAY BELOW A POINT WHERE HE COULD NOT RECOVER WITHOUT THE HELICOPTER SUSTAINING DAMAGE. THIS WAS THE SECOND ACCIDENT WHERE THIS PILOT WAS INVOLVED AS PILOT IN COMMAND AND AUTOROTATIVE PROCEDURES WERE IN QUESTION.
Probable cause
PILOT'S FAILURE TO MAINTAIN MAIN ROTOR RPM WHILE EXECUTING AN AUTOROTATION WHICH RESULTED IN A HARD LANDING. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT'S FAILURE TO FOLLOW AUTOROTATION PROCEDURES AFTER THE REPORTED ENGINE FAILURE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL89FA200
- Event ID
- 20001213X29029
- Case number
- ATL89FA200
- 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: f2f5321cde19e18896629964ad6a02e4f4cd9bea9681527a3baea4aa04bc6c59; retrieved 2026-09-23T07:15:15.465Z.