LAX01LA255 · Hughes 269C
Hughes 269C · Accident: hard landing
From Stockton Metropolitan Airport (SCK) to New Jerusalem Airport (1Q4)
Event
- NTSB case
- LAX01LA255
- 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
Hughes 269C
- Aircraft type
- Hughes 269
- 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
- N5015V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Stockton Metropolitan Airport (SCK), Stockton, CATo New Jerusalem Airport (1Q4), Tracy, 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 · 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
- Pilot in command › Flare, misjudged
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor stated that he was demonstrating an autorotation to his student when the accident occurred. He said that he initiated a straight in autorotation to runway 30 at 600 feet above ground level (agl). The descent rate was stabilized until 200 feet agl, when he felt a sudden increase in the rate of descent. He began the flare at 50 feet agl. He stated that the vertical speed did not decrease at the rate he was accustomed to, resulting in a hard landing. He stated that the tail boom hit the ground first in a right yawing moment. The helicopter then rolled to the right, crushing the right skid, severing the tail boom, and allowing the rotor blades to contact the ground. He noted that no mechanical problems existed with the helicopter during the flight. He did not notice any mechanical anomalies during the autorotation demonstration. He stated that the engine was running normally during the autorotation and the landing flare. The pilot stated that wind shear may have been a factor. He had observed the winds to be from the northwest at 8 knots, and gusts to 12 knots with light turbulence.
Probable cause
The pilot's misjudgement of the landing flare during an autorotation demonstration. Factors were shifting winds and an excessive descent rate.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA255
- Event ID
- 20010725X01513
- Case number
- LAX01LA255
- 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: 3fa9b59c6bc10517c66a41812884427557ec76f8d2afaebe6234e4de5840edf1; retrieved 2026-09-22T11:44:54.865Z.