SEA08FA022 · Hughes 269C
Baker Aircraft Hughes 269C · Accident: loss of control in flight while maneuvering
From Baker City Municipal Airport (KBKE) to Baker City Municipal Airport (KBKE)
Event
- NTSB case
- SEA08FA022
- 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
- 1 · 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
- N381MC
- Operator
- Baker Aircraft
- Onboard fatalities
- Unknown
- Route
- From Baker City Municipal Airport (KBKE), Baker City Muni, ORTo Baker City Municipal Airport (KBKE)
- 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 › Rotor RPM, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to witnesses, after departing the airport, the helicopter turned to the north, climbed to an altitude that was reported to be as low as 100 above ground level (agl) and as high as 800 feet agl. As it approached the accident site location, the helicopter's tail reportedly lowered, it slowed, rotated or turned slightly to the east, and then descended rapidly toward the terrain. Witnesses reported that near the beginning of the descent, the main rotor blades either slowed their rotation significantly or "stopped turning." One witness stated that almost immediately after observing the change in rotation speed of the main rotor blades, "…the helicopter just dropped out of the sky." Examination of the wreckage disclosed evidence of coning of the main rotor blades. No evidence was found of any flight control malfunction or loss of engine power.
Probable cause
The pilot’s failure to maintain main rotor rpm while maneuvering.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA08FA022
- Event ID
- 20071121X01829
- Case number
- SEA08FA022
- 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: c64cd69bbf3eccf6983f8b148c781d6ba51a5e99d22e9fc468d2fe248c739429; retrieved 2026-09-20T16:07:26.199Z.