FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03LA253 · Bell 206B

5 Aug 2003 · Merced, CA, United States

Bell 206B · Accident: abrupt maneuver during landing

From Modesto City Co-Harry Sham Field (MOD) to Merced, CA

Report a problem

Event

NTSB case
LAX03LA253
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
N9254Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Modesto City Co-Harry Sham Field (MOD), Modesto, CATo Merced, CA
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
Landing · aborted
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
Abrupt maneuver
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 › Aircraft control, excessive
  • Pilot in command › Dynamic rollover, inadvertent

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 reported he was landing on a concrete pad at a construction site. The helicopter was not positioned completely on the concrete landing pad, and the aft section of the skids were hanging off the pad. While lowering the collective, the helicopter rocked back and the tail rotor skid touched the ground. The pilot abruptly attempted to pull the helicopter back into a hover, and the helicopter moved forward and started to roll to the right. The pilot was unable to stop the rolling movement, and the helicopter struck the ground, coming to rest on its right side.

Probable cause

The pilot's excessive movement of the helicopter's controls during an aborted landing, which resulted in a loss of control (dynamic rollover) and an in-flight collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03LA253
Event ID
20030808X01296
Case number
LAX03LA253
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: c3ddfea7da7fc39a3e9b3ca82b0918025c77f840b943772aa3be4be62f0bca32; retrieved 2026-09-22T08:49:43.253Z.