FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99FA003 · Bell 222

4 Oct 1998 · Las Vegas, NV, United States

Bell 222 · Accident: in flight collision with terrain/water during takeoff

Report a problem

Event

NTSB case
LAX99FA003
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 222

Aircraft type
Bell 222
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
N213ML
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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
Takeoff
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 terrain/water
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

  • Pilot in command › Throttle/power control, improper use of

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

NTSB narrative

The pilot was departing from a confined area surrounded by tall obstacles from 50 to 60 feet in height. The direction the helicopter faced put the prevailing winds from the rear quadrants. Witnesses saw the helicopter liftoff to the north, barely missing nearby palm trees. The eyewitnesses said the helicopter was hovering erratically, and that the tail of the helicopter was moving side to side, as if the pilot was fighting the wind. The helicopter did not climb above the height of the three-story administration building. The helicopter bounced landed, bounced, rolled over, and came to rest on its left side. The left engine throttle was found rolled to the full on position, while the right engine throttle was less than the full on position. Postaccident tests of both engines revealed no abnormalities with their performance. An attempt was made to duplicate the takeoff conditions using a 222 simulator, with a throttle split and tailwind condition set up in the simulator. In two of the scenarios the pilot was unable to successfully fly out of the condition and crashed with a high rate of descent. The pilot's training records indicated that he had not attended a proficiency or emergency procedure course in the Bell 222. All previous training flights were conducted in a Bell 206. Each engine was calculated to be capable of producing 494 SHP. An engineering analysis concluded that in a single engine situation, insufficient power would be available to hover; with the power output of one engine reduced, out-of-ground-effect hover capability was not available.

Probable cause

The pilot's failure to ensure that both throttles were in the takeoff position. Factors were the pilot's decision to takeoff with a tailwind, and his lack of recurrent emergency procedure training in this helicopter.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99FA003
Event ID
20001211X11279
Case number
LAX99FA003
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: 0660bfa36e92ef237efa8d8b5e41f83221ecc20767bbce971865019b47b49738; retrieved 2026-09-21T20:40:51.404Z.