T Bird Golden Circle Air INC II accident near Clara City, Minnesota, April 14, 2012
On April 14, 2012 at about 8:50 pm local time, a T Bird Golden Circle Air INC II, registered N5654N, was substantially damaged in an accident during initial climb near Clara City, Minnesota. It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The airplane's loss of engine power for reasons that could not be determined because postaccident examination did not reveal any malfunctions or anomalies that would have precluded normal operation.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 14, 2012 · about 8:50 pm local time
- Place
- Clara City, Minnesota · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- T Bird Golden Circle Air INC II
- Registration
- N5654N · registry record · serial 615 352
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The non-certificated pilot changed the airplane's fuel and then conducted several high-speed taxi runs to check engine operation in preparation for the airplane’s first flight after several months of inactivity. Shortly after the subsequent takeoff, the airplane's engine began to run rough and then lost power. The pilot elected to conduct a forced landing in a vacant field. A postaccident examination confirmed flight and engine control continuity and did not detect any preimpact mechanical malfunctions or anomalies. Although review of a carburetor icing probability chart indicated that the weather conditions at the time of the accident were conducive to serious carburetor icing at glide power, the investigation was unable to determine the cause of the loss of engine power.
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
- Loss of engine power (total) during initial climb defining event
- Collision with terrain or object (not controlled flight into terrain) during landing (flare/touchdown)
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Medical certificate: None
- Seat: unk
- Injury: serious injuries
The aircraft
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 582ULDCDI-99 (piston); 0 hours total
The flight
- Departed from: Clara City MN
- Destination: Clara City MN
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 180° at 3 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 72°F (22°C), dew point 43°F (6°C)
- Altimeter: 29.72 inHg
- Observation at 8:55 pm from KBDH, 14 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 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.
Other NTSB records under N5654N the same tail number, which may have belonged to a different aircraft at the time
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.