Cirrus Design CORP SR22 accident near Tredyffin, Pennsylvania, June 1, 2022
On June 1, 2022 at about 7:27 pm local time, a 2008 Cirrus Design CORP SR22, registered N432CP, was substantially damaged in an accident during approach near Tredyffin, Pennsylvania. It was a personal flight under general aviation rules (Part 91). 2 people were seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The loosening of the throttle arm from the throttle body, which resulted in the pilot’s inability to control the engine, and a subsequent forced landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 1, 2022 · about 7:27 pm local time
- Place
- Tredyffin, Pennsylvania · map
- Type
- Accident
- Injuries
- 2 people were seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Cirrus Design CORP SR22, built 2008
- Registration
- N432CP · no longer on the register · serial 3254
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot while approaching the destination airport, the engine did not respond when he advanced the throttle. He also noted that the throttle felt “loose” and further described that the engine was still running, but that the rpm would not change. There was not sufficient engine power being produced in order for the airplane to reach the destination airport, so the pilot elected to perform an off-airport landing to a golf course. The airplane was substantially damaged during the landing, and the pilot and passenger were seriously injured. A postaccident examination of the engine found that the engine’s controls were damaged during the accident sequence and had separated from the engine. Additionally, the throttle arm was found loosely attached to the shaft at the throttle body. The nut needed to be tightened by 1/8-turn in order to fully engage. No other anomalies were noted during the examination that would have precluded normal operation of the engine. Review of the airplane’s maintenance records revealed that the engine controls had been inspected and lubricated about 7 months and 37 flight hours before the accident, with no subsequent maintenance to those components noted. Based on the pilot’s description that the engine did not respond to throttle changes and that it felt “loose,” as well as the finding that the throttle arm was found loosely attached to the throttle shaft, it is likely that the loosening of the securing nut resulted in the pilot’s inability to control the engine, and the subsequent forced landing.
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 (partial) during approach defining event
- Off-field or emergency landing during landing
The NTSB's findings
- Aircraft › Aircraft power plant › Engine fuel and control › Fuel controlling system › Malfunction
Pilot
- Certificate: private, remote
- Ratings: single-engine land; instrument: airplane
- Flight time: 1,932 hours in all; 750 in this make and model
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: serious injuries
Passenger
- Seat: rgt
- Injury: serious injuries
The aircraft
- Airframe total time: 1,330.2 hours
- Last inspection: inspection type not recorded
- Maximum gross weight: 3,600 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental IO-550N (piston); 1,293 hours total
The flight
- Departed from: FMY Fort Myers FL at 12:59 pm
- Destination: 1234 Georgetown SC
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 130° at 8 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 82°F (28°C), dew point 68°F (20°C)
- Altimeter: 29.85 inHg
- Observation at 4:15 pm from KLOM, 9 miles away
Weather report (METAR): METAR KLOM 012015Z AUTO 13008KT 10SM CLR 28/20 A2985 RMK AO2 T02820198
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
12 documents, released by the NTSB on June 20, 2024. 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 | Air Traffic Control Communication Summaries | PDF, 7 pages | View Download |
| 2 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 11 pages | View Download |
| 3 | Memorandum for Record A�� Telephone Interview, Pilot | PDF, 1 page | View Download |
| 4 | Memorandum for Record - FAA Inspector Statement | PDF, 4 pages | View Download |
| 5 | Maintenance Records (Excerpts) | PDF, 3 pages | View Download |
| 6 | Fuel Receipts | PDF, 1 page | View Download |
| 7 | Airplane POH Excerpts | PDF, 4 pages | View Download |
| 8 | Aircraft Performance Study | PDF, 8 pages | View Download |
| 9 | ADS-B Tabular Data | data file | Download |
| 10 | Recoverable Data Module - Specialist's Factual Report | PDF, 3 pages | View Download |
| 11 | Evidence Control Form | PDF, 3 pages | View Download |
| 12 | Investigation Photos | PDF, 4 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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.
