FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

BFO94LA105 · Robinson R22 BETA

17 Jun 1994 · Elizabethtown, KY, United States

J R Aviation Robinson R22 BETA · Accident: loss of control in flight during initial climb

From No airport to an unrecorded destination

Report a problem

Event

NTSB case
BFO94LA105
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

Robinson R22 BETA

Aircraft type
Robinson R22
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
N2346J
Onboard fatalities
Unknown
Route
From No airportTo not recorded
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
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
Substantial

Cause areas

  • Pilot in command › Directional control, not maintained

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

NTSB narrative

THE PILOT AND PASSENGER WERE DEPARTING FROM A LOT THAT WAS SURROUNDED BY OBSTRUCTIONS. ACCORDING TO THE PILOT, HE TOOK OFF IN A HOVER, THEN AS THE HELICOPTER WAS PASSING TREES AT ABOUT 70 FEET AND 30 TO 35 KNOTS, IT BEGAN SPINNING TO THE RIGHT. HE SAID HE TRIED TO STOP THE TURNING WITH LEFT PEDAL, WHICH DID NOT CORRECT THE PROBLEM. HE ENTERED AN AUTOROTATION TO A ROAD. DURING THE AUTOROTATIVE LANDING, THE HELICOPTER TOUCHED DOWN HARD, DAMAGING THE UNDERSIDE OF THE AIRFRAME. ACCORDING TO WITNESSES, THE MAIN ROTOR BLADES CLIPPED A TREE, BUT NO BLADE DAMAGE WAS REPORTED. POST-ACCIDENT EXAMINATION REVEALED NO PREIMPACT MECHANICAL DISCREPANCIES. ACCORDING TO THE HEIGHT-VELOCITY DIAGRAM IN THE R22 OPERATING HANDBOOK, DIRECTIONAL CONTROL WAS LOST WHEN THE HELICOPTER WAS OUTSIDE THE AREA FOR THE 'RECOMMENDED TAKE-OFF PROFILE' (AIRSPEED/ALTITUDE ENVELOPE FOR A SUCCESSFUL AUTOROTATION).

Probable cause

THE PILOT'S FAILURE TO MAINTAIN DIRECTIONAL CONTROL. A FACTOR RELATED TO THE ACCIDENT WAS: THE HELICOPTER WAS OUTSIDE THE HEIGHT-VELOCITY ENVELOPE (FOR A SUCCESSFUL AUTOROTATION), WHEN LOSS OF DIRECTIONAL CONTROL OCCURRED.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record BFO94LA105
Event ID
20001206X01465
Case number
BFO94LA105
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: 0beb1480516d864904171f1afa9496ffe5b3cd341811e386c0027f37ab762e28; retrieved 2026-09-23T01:00:33.319Z.