SEA01LA044 · Bell 206B
Bell 206B · Accident: hard landing
From Aurora State Airport (UAO) to McMinnville Municipal Airport (MMV)
Event
- NTSB case
- SEA01LA044
- 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
- N58WW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aurora State Airport (UAO), Aurora, ORTo McMinnville Municipal Airport (MMV), McMinnville, OR
- 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(cfi) › Throttle/power control, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a telephone interview and a subsequent written statement, the instructor pilot reported that she and the student pilot were practicing power recovery autorotations. During the fifth practice autorotation, while descending through an altitude of approximately 200 feet AGL, the instructor pilot increased throttle and collective in an effort to slow the helicopter's decent rate and recover from the autorotation. Shortly thereafter, the pilot noted that the main rotor RPM was not increasing and that she had inadvertently applied only partial power for the recovery. The instructor pilot lowered collective, increased power and performed a straight-in run-on landing. The helicopter touched down 3-4 feet beyond the numbers on runway 35. During the run-on landing, the helicopter encountered a rough/uneven spot on the runway surface and came to an abrupt stop.
Probable cause
The pilot's failure to apply adequate power during a practice autorotation. A factor contributing to the accident was a rough/uneven area on the asphalt landing surface.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA01LA044
- Event ID
- 20010206X00407
- Case number
- SEA01LA044
- 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: 99380948a926e7be1e431bc849d74c98bb684ea7e74efaec07808c3e71c45556; retrieved 2026-09-22T12:13:52.931Z.