Grumman Acft Eng Cor-Schweizer G-164B accident near Edison, Georgia, October 19, 2012
On October 19, 2012 at about 5:00 pm local time, a Grumman Acft Eng Cor-Schweizer G-164B, registered N6670K, was substantially damaged in an accident near Edison, Georgia. It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). 1 person had minor injuries. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
The total loss of engine power due to the fatigue failure of the k-pin associated with the No. 1 cylinder.
Source: NTSB aviation accident database, copy made September 29, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 19, 2012 · about 5:00 pm local time
- Place
- Edison, Georgia · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Grumman Acft Eng Cor-Schweizer G-164B · all G-164Bs on the register
- Registration
- N6670K · registry record · serial 413B
- Damage
- Substantial damage
- Flight
- Aerial application (crop spraying) flight · agricultural flying rules (Part 137)
The NTSB's narrative final · quoted from the NTSB record
The pilot stated that he had completed an aerial application run in the airplane and began a left turn to return for another aerial application run. However, shortly after he began the maneuver, the airplane’s engine lost total power. The pilot performed a forced landing to a field, during which the airplane nosed over. Examination of the radial engine revealed that the No. 1 cylinder k-pin had failed, resulting in significant internal engine damage and the loss of power. Further examination of the failed k-pin revealed that it had fractured near its center oil journal, and the k-pin fracture marks exhibited damage consistent with fatigue.
The NTSB's narratives can run to many pages; this is the opening. Read the full report at the NTSB.
About this page
Everything above comes from the NTSB's public accident database and is rewritten in plain English only where the NTSB used codes; the probable cause and narrative are the NTSB's own words. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA13LA029.