Schweizer 269C accident near Gary, South Dakota, July 23, 2013
On July 23, 2013 at about 8:20 pm local time, a Schweizer 269C (helicopter), registered N7507A, was substantially damaged in an accident during approach near Gary, South Dakota. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries; 2 others were unhurt. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The failure of the engine connecting rod due to fatigue.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 23, 2013 · about 8:20 pm local time
- Place
- Gary, South Dakota · map
- Type
- Accident
- Injuries
- 1 person had minor injuries; 2 others were unhurt.
- Weather
- visual conditions (good weather)
- Aircraft
- Schweizer 269C · all 269Cs on the register
- Registration
- N7507A · no longer on the register · serial S1297
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was descending the helicopter from about 1,000 feet above ground level (agl) and setting up for a landing at an off-airport location. At 300 to 500 feet agl, the pilot felt a major vibration in the helicopter. He immediately initiated an autorotation and landed the helicopter. During the forced landing, the helicopter rolled over on its right side and sustained substantial damage. Examination of the engine revealed that the No. 3 connecting rod had failed. Material examination of the connecting rod showed the rod failed due to multiple fatigue cracks.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Powerplant sys/comp malf/fail during approach defining event
- Autorotation Collision with terrain or object (not controlled flight into terrain)
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Failure
- Environmental issues › Physical environment › Terrain › Sloped/uneven › Contributed to outcome
Pilot
- Certificate: private
- Ratings: single-engine land; rotorcraft: helicopter
- Flight time: 1,095 hours in all; 250 in this make and model; 37 in the last 90 days; 15 in the last 30 days
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,891 hours
- Last inspection: annual inspection, October 29, 2012; 15 hours since
- Maximum gross weight: 2,050 lb
- Seats: 3
- Landing gear: fixed
- Engine: Lycoming HIO-360-D1A (piston); 0 hours total
The flight
- Departed from: CNB Canby MN at 8:00 pm
- Destination: CNB Canby MN
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 0°F (-18°C)
- Altimeter: 30.00 inHg
- Observation at 8:00 pm from CNB, 10 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.