LAX03CA279 · Bell 206B
Bell 206B · Accident: loss of control in flight while maneuvering
From Corona Municipal Airport (KAJO) to an unrecorded destination
Event
- NTSB case
- LAX03CA279
- 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
- Unknown
- 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
- N59506
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Corona Municipal Airport (KAJO), Corona, CATo 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
- Maneuvering
- 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 › Loss of tail rotor effectiveness, encountered
- Pilot in command › Remedial action, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot lost directional control of the helicopter while maneuvering and the helicopter impacted water and sank. The pilot was manuevering over a boat race and was flying over the start line about 400 feet agl, on a magnetic heading between 235 to 240. He felt the helicopter drifting north and east. A turn was initiated; however, simultaneously, the helicopter "shuddered and snapped into a rapid right yaw." Left antitorque pedal was applied but the helicopter continued to turn 360 degrees repeatedly while losing altitude. Just prior to impact, the pilot pulled up on the collective and pushed the cyclic into a forward right position intending to assist the main rotor blades in stopping. The Rotorcraft Flying Handbook states that a loss of tail rotor effectiveness (LTE) is the occurrence of an uncommanded yaw rate that does not subside on its own accord, which can result in the loss of helicopter control. The recovery technique for LTE is full left pedal while simultaneously moving cyclic control forward to increase airspeed. If altitude permits, reduce power.
Probable cause
the pilot's inadequate remedial action in response to a loss of tail rotor effectiveness.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03CA279
- Event ID
- 20031010X01709
- Case number
- LAX03CA279
- 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, coordinates. 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: 338cf324947f9f497945370e2901aa815aa2de8518b2b38114b5380db42d3228; retrieved 2026-09-22T08:35:43.121Z.