NYC93GA082 · Bell 206B
Ohio State Police Bell 206B · Accident: loss of control in flight on approach
From an unrecorded airport to No airport
Event
- NTSB case
- NYC93GA082
- 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
- N72HP
- Operator
- Ohio State Police
- Onboard fatalities
- Unknown
- Route
- From not recordedTo No airport
- 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
- 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 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 performance › Deteriorated
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS ON APPROACH AT ABOUT 150-200 FT AGL WHEN THE HELICOPTER BEGAN ROTATING CLOCKWISE ABOUT THE NOSE IN A NOSE-DOWN ATTITUDE. IT DESCENDED TO THE GROUND AND LANDED HARD IN A LEVEL ATTITUDE COLLAPSING THE LANDING SKIDS. THE HELICOPTER THEN ROLLED OVER ON ITS RIGHT SIDE, AND THE MAIN ROTOR BLADES STRUCK THE GROUND. ACCORDING TO THE PILOT, HE MADE A WIDE RIGHT TURN TO ALIGN WITH THE LANDING AREA WHEN THE NOSE YAWED RIGHT ABOUT 45 DEG. THE HELICOPTER ROTATED TWICE DESPITE THE PILOT'S ATTEMPT TO CORRECT WITH FULL LEFT PEDAL AND LESS COLLECTIVE. HE STATED THE ENGINE APPEARED TO BE OPERATING AT FULL POWER AFTER THE COLLISION. THE INVESTIGATION DID NOT DISCLOSE EVIDENCE OF MECHANICAL MALFUNCTION. BASED ON ARMY AND BELL HELICOPTER DATA, THE AIRSPEED AND WIND COMBINATION WERE CONDITIONS CONDUCIVE FOR THE OCCURENCE OF THE LOSS OF TAIL ROTOR EFFECTIVENESS.
Probable cause
LOSS OF TAIL ROTOR EFFECTIVENESS WHICH RESULTED IN THE LOSS OF AIRCRAFT CONTROL. A FACTOR WHICH CONTRIBUTED TO THE ACCIDENT WERE UNFAVORABLE WINDS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC93GA082
- Event ID
- 20001211X12213
- Case number
- NYC93GA082
- 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: 32ad29409d29e722ca669605659aa30e7f296af253c02e92f4ef791c6cf18c4a; retrieved 2026-09-21T22:59:29.033Z.