# Accident 20241117019779A: Cirrus SR22T, Palm Springs, CA, November 17, 2024

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 17, 2024, 19:56 local time
- Place: Palm Springs, CA
- Damage: Substantial damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 33.8291° N, 116.5073° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.8291&lon=-116.5073&mi=10
- Aircraft: N828PS, registered now (https://openairdocs.org/aircraft/N828PS) (OpenAirDocs)
- Registry model: Cirrus Design SR22T (registry code 2130004, https://openairdocs.org/model/cirrus-design-sr22t) (OpenAirDocs)
- Registry engine: Continental TSIO-550-K (registry code 17410, https://openairdocs.org/engine/continental-tsio-550-k) (OpenAirDocs)
- Reported make and model: CIRRUS SR22T
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 1,316 total
- NTSB investigation: [NTSB WPR25LA041](https://openairdocs.org/ntsb/WPR25LA041) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20241117019779A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON 11-17-2024 A CIRRUS SR-22 APPROACHED PALM SPRINGS INTERNATIONAL AIRPORT FROM THE NORTHEAST UNDER VISUAL FLIGHT RULES FOR THE PURPOSE OF LANDING. AIR TRAFFIC CONTROL (ATC) SEQUENCED THE AIRCRAFT FOR LANDING TO RUNWAY 31R FROM A POSITION WESTBOUND OVER THE INTERSTATE 10. THE AIRCRAFT WAS INSTRUCTED TO PROCEED DIRECT TO THE POINT OF LANDING ON RUNWAY 31R RATHER THAN TO FLY A SQUARED BASE LEG TO FINAL APPROACH, AND ADVISED 3 TIMES BY ATC OF THE BOEING 737 ARRIVING TO PARALLEL RUNWAY 31L. DURING THE THIRD ATC TRAFFIC ADVISORY, ATC ISSUED THE SR-22  A WAKE TURBULENCE ADVISORY FOR THE ARRIVING 737 THAT THE SR-22 PILOT ACKNOWLEDGED BY REPORTING THE OTHER AIRCRAFT "IN SIGHT." THE SR-22 CONTINUED ON THE DIRECT FLIGHT PATH. THE 737 TOUCHED DOWN ON RUNWAY 31R, AFTER WHICH THE SR-22 PILOT BEGAN A RIGHT TURN TO ALIGN WITH RUNWAY 31R DURING SHORT-FINAL APPROACH. THE SR-22 PILOT STATED THAT DURING THE TURN, THE SR-22 ENCOUNTERED WAKE TURBULENCE, THAT THE SR-22 BANK ANGLE INCREASED TO "NEARLY 90 DEGRESS," AND THAT CONTROL OF THE SR-22 WAS LOST "DESPITE FULL AILERON DEFLECTION TO THE LEFT." THE SR-22 IMPACTED THE GROUND IN THE VICINITY OF RUNWAY 31R, RESULTING IN A RUNWAY EXCURSION TO THE NORTH PRIOR TO THE 1,000' TOUCHDOWN ZONE MARKINGS. PHOTO EVIDENCE INDICATED SUBSTANTIAL DAMAGE TO THE AIRCRAFT PROPELLER, NOSE WHEEL LANDING STRUCTURE (WHICH DEPARTED THE AIRCRAFT STRUCTURE), THE RIGHT MAIN LANDING GEAR ASSEMBLY, AND RIGHT AILERON. THE RIGHT AILERON APPEARED TO BE SEPARATED FROM THE RIGHT WING AT  THE AILERON'S INBOARD ATTACHMENT POINT, AND THE CONTROL SURFACE CAME TO REST PARTIALLY ON THE GROUND. THE SR-22 PILOT REPORTED 2 AIRCRAFT OCCUPANTS WHO SUSTAINED NO INJURIES.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB WPR25LA041](https://openairdocs.org/ntsb/WPR25LA041), Nov 17, 2024: Cirrus Design SR22T (N828PS), Palm Springs, CA, substantial damage. Probable cause: The pilot’s failure to maintain clearance from a commercial airliner which resulted in an encounter with wake turbulence and subsequent loss of control resulting in impact with terrain.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.