ATL05CA127 · Schweizer 269C-1
Schweizer 269C-1 · Accident: loss of control on ground/water during takeoff
From Fairview Airport (33A) to Greenville Downtown Airport (GMU)
Event
- NTSB case
- ATL05CA127
- 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
Schweizer 269C-1
- Aircraft type
- Schweizer 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
- N301MG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fairview Airport (33A), Landrum, SCTo Greenville Downtown Airport (GMU), Greenville, SC
- 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
- Takeoff
- 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 on ground/water
- 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 › Collective, improper use of
- Pilot in command › Cyclic, improper use of
- Pilot in command › Dynamic rollover, encountered
- Pilot in command › Flight controls, improper use of
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 stated he made an approach to the sod area adjacent to runway 32 and he was not aware of the fact that the sod area was wet and soft. He applied collective pitch abruptly as he was taking off to a hover. The left skid became airborne and the right skid remained on the ground. The helicopter encountered dynamic roll over before the pilot could apply collective pitch and lateral cyclic. The helicopter rolled over on its right side. The pilot stated there were no anomalies with the airframe, flight controls, engine assembly and accessories.
Probable cause
The pilot's improper use of the flight controls (collective pitch and cylic controls) during a take off to a hover resulting in the helicopter encountering dynamic roll over and rolling over on its right side.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL05CA127
- Event ID
- 20050816X01249
- Case number
- ATL05CA127
- 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: 17f6c59ceb295d267b4c590f7776bf3a57bafd7957b9a2033120c37383cdb097; retrieved 2026-09-22T05:39:57.209Z.