LAX96LA172 · Bell 206B III
Bell 206B III · Accident: hard landing
From Montgomery-Gibbs Executive Airport (MYF) to an unrecorded destination
Event
- NTSB case
- LAX96LA172
- 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 III
- 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
- N2750F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Montgomery-Gibbs Executive Airport (MYF)To 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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
- Dual student › Distance/altitude, misjudged
- Dual student › Planned approach, misjudged
- Dual student › Rotor RPM, not maintained
- Pilot in command(cfi) › Remedial action, delayed
- Pilot in command(cfi) › Supervision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While practicing touchdown autorotations, the helicopter landed hard on uneven terrain short of the intended touchdown point. The commercial pilot-rated student was demonstrating a autorotation with a turn to the runway. As he completed the turn and was aligning with the runway, the helicopter rotor rpm dropped to 70 percent. Halfway into the maneuver the flight instructor realized the helicopter was too low and slow to accomplish a power recovery and took control. The helicopter landed short of the runway in rough terrain. A postflight inspection of the helicopter revealed wrinkles in the tail boom. The pilot under instruction held a rotorcraft helicopter rating.
Probable cause
the student's failure to maintain adequate main rotor rpm and airspeed during a practice autorotation, and the instructor's inadequate supervision of the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96LA172
- Event ID
- 20001208X05616
- Case number
- LAX96LA172
- 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: 6b1e5d966ab7da05f78a883e7c50aa967bff1d6b93cb71f919f08a89c29405b7; retrieved 2026-09-22T22:37:53.481Z.