Cessna 305A accident near Rochester, Indiana, November 22, 2009
On November 22, 2009 at about 2:10 pm local time, a Cessna 305A, registered N1172D, was substantially damaged in an accident during landing (flare/touchdown) near Rochester, Indiana (Fulton County Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain directional control during landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 22, 2009 · about 2:10 pm local time
- Place
- Rochester, Indiana · Fulton County Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 305A · all 305As on the register
- Registration
- N1172D · registry record · serial 23220C
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that the accident occurred while he was landing the airplane. He stated that he flared and the stall warning system activated. The airplane then bounced upon touchdown. He stated that he lost directional control and the airplane started going to the left. He attempted to correct using right rudder, but the airplane continued to the left and went off the runway. The right main landing gear was separated from the airplane. The airplane also suffered damage to the right wing, right elevator, fuselage, propeller, and cowl. The pilot stated that there was no mechanical problems with the airplane prior to the accident.
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 on ground during landing (flare/touchdown) defining event
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 1,242 hours in all; 172 in this make and model; 4 in the last 90 days; 3 in the last 30 days; 1,188 as pilot in command
- Last flight review: September 16, 2009
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: frt
- Injury: no injuries
The aircraft
- Airframe total time: 3,025 hours
- Last inspection: annual inspection, August 10, 2009
- Seats: 2
- Landing gear: fixed
- Engine: Cont Motor O-470 SERIES (piston); 0 hours total
The flight
- Departed from: MQJ Indianapolis IN at 1:00 pm
- Destination: RCR Rochester IN
- Flight plan: none
- Runway 29, 5,001 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 110° at 2 knots
- Visibility: 5 statute miles
- Sky: clear
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
- Observation at 1:40 pm from RCR
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 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.