Amateur-built TWINSTAR accident near Greencastle, Indiana, July 16, 2025
On July 16, 2025 at about 5:10 pm local time, a 1996 amateur-built TWINSTAR (gyroplane), registered N45CL, was substantially damaged in an accident during takeoff near Greencastle, Indiana (Putnam County airport). It was a flight test under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to maintain pitch control during takeoff. Contributing to the accident was the pilot’s inexperience in the accident gyroplane.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 16, 2025 · about 5:10 pm local time · cases in 2025
- Place
- Greencastle, Indiana · Putnam County · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built TWINSTAR, built 1996
- Registration
- N45CL · registry record · serial 004
- Damage
- Substantial damage
- Flight
- Flight test · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was performing a post inspection test flight of the gyroplane. Prior to the flight, the pilot noticed the control stick pressures were greater than he had experienced with other gyroplanes he had previously flown. The gyroplane’s owner and a mechanic explained the gyroplane’s trim system to the pilot who then adjusted the trim to a setting he assumed would be sufficient to maintain control when the gyroplane was airborne. During takeoff, the gyroplane pitched up and when the pilot attempted to arrest the motion, the backstick forces on the control stick were greater than expected. The pilot lost control of the gyroplane as it continued to pitch upwards, so he reduced the engine power. The gyroplane had pitched to about 60° nose high, rolled left, and impacted the ground resulting in substantial damage. The pilot had flown several models of gyroplanes but had no flight experience in the accident gyroplane. After the accident, the pilot further learned that the gyroplane’s trim had previously been modified with a heavier trim spring which made this gyroplane respond differently than other gyroplanes.
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 control in flight during takeoff defining event
The NTSB's findings
- Personnel issues › Experience/knowledge › Experience/qualifications › Total experience w/ equipment › Pilot
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Pitch control › Not attained/maintained
Pilot
- Certificate: flight instructor, private, sport pilot
- Ratings: instructor: gyroplane; instructor: sport pilot; rotorcraft: gyroplane
- Flight time: 561 hours in all; 0.3 in this make and model; 62 in the last 90 days; 12.8 in the last 30 days; 501 as pilot in command; 28 on instruments
- Last flight review: March 26, 2025
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: frt
- Injury: minor injuries
The aircraft
- Airframe total time: 551 hours
- Last inspection: condition inspection, July 16, 2025
- Maximum gross weight: 1,320 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-320 (piston); 0 hours total
The flight
- Flight plan: none
- Runway 18, 5,002 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 200° at 8 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 1,200 ft
- Temperature: 79°F (26°C), dew point 77°F (25°C)
- Altimeter: 29.95 inHg
Weather report (METAR): METAR KGPC 161715Z AUTO 20008KT 10SM BKN012 BKN017 OVC027 26/25 A2995 RMK AO2 T02610248=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 2 pictures from the NTSB's docket, as the NTSB released them
The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on November 8, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | Photos | PDF, 3 pages · our copy | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N45CL on the register today · the tail number may have moved to another aircraft since
- Engine: Lycoming O-320 27,304 aircraft carry this series today · as the NTSB recorded it
- Putnam County Regional · nearest airport
- Accidents and incidents in Indiana 1,367 since 1982 · 179 in the last ten years
- Indiana 5,705 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN25LA256.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.


