# Accident 20020403007139A: Cessna 172S, Palm Springs, CA, April 3, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 3, 2002, 10:30 local time
- Place: Palm Springs, CA
- Airport: Palm Springs Regional Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 33.8297° N, 116.5067° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.8297&lon=-116.5067&mi=10
- Aircraft: N627SP, registered now (https://openairdocs.org/aircraft/N627SP) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- NTSB investigation: [NTSB LAX02LA130](https://openairdocs.org/ntsb/LAX02LA130) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020403007139A

## Narrative

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

(.19) ON APRIL 3, 2002, ABOUT 1030 PACIFIC STANDARD TIME, A CESSNA 172S, N627SP, COLLIDED WITH A TAXIWAY SIGN DURING THE LANDING ROLL AT PALM SPRINGS, CALIFORNIA. THE FLIGHT SCHOOL AT PALM SPRINGS WAS OPERATING THE RENTAL AIRPLANE UNDER THE PROVISIONS OF 14 CFR PART 91. THE STUDENT PILOT, THE SOLE OCCUPANT, WAS NOT INJURED; THE AIRPLANE SUSTAINED SUBSTANTIAL DAMAGE. THE PERSONAL LOCAL FIGHT DEPARTED ABOUT 1000. DAY VISUAL METEOROLOGICAL CONDITIONS PREVAILED, AND NO FLIGHT PLAN HAD BEEN FILED. THE STUDENT WAS PRACTICING LANDINGS ON HIS SECOND SUPERVISED SOLO. HE COMPLETED FIVE TOUCH-AND-GO LANDINGS AND THE SIXTH WAS TO BE A FULL STOP LANDING.  DURING THE LANDING ROLL, THE AIRPLANE SUDDENLY VEERED TO THE LEFT.  THE AIRPLANE DEPARTED THE RUNWAY, BUT THE STUDENT PILOT WAS ABLE TO GUIDE IT BACK ONTO THE RUNWAY. DURING THE EXCURSION, THE AIRPLANE COLLIDED WITH A RUNWAY EDGE LIGHT AND TAXIWAY SIGN, WHICH RESULTED IN SUBSTANTIAL DAMAGE TO THEAIRFRAME.                                                                  THE SAFETY BOARD WAS NOTIFIED OF THE ACCIDENT ON APRIL 8, 2002.                                                                                                                  (-23) STUDENT PILOT WAS FLYING SOLO, LANDED AIRCRAFT AND AT THAT TIME WAS GOING TO APPLY RUDDER CONTROL HE INADVERTENTLY APPLIED THE BRAKES. THIS CAUSED THE AIRCRAFT TO VEER INTO SOME RUNWAY LIGHTS AND SIGN. THE DAMAGE TO THE AIRCRAFT WAS SUBSTANTIAL. LOWER ENGINE COMPARTMENT AND FIRE WALL WERE DAMAGED, ALONG WITH NOSE WHEEL COVER.

## 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 LAX02LA130](https://openairdocs.org/ntsb/LAX02LA130), Apr 3, 2002: Cessna 172S (N627SP), Palm Springs, CA, substantial damage. Probable cause: The pilot lost directional control and collided with a runway edge light and taxiway sign.

## Other reports on N627SP (2)

Matched to the same aircraft by N-number and date.

- [Incident 20240813017469I](https://openairdocs.org/incident/20240813017469I), Aug 13, 2024: Cessna 172S (N627SP), Fort Lauderdale, FL, No damage. Aircraft was cleared to land on runway 9. Upon landing the right-side tire went flat causing the aircraft to pull towards the right. More left brake was…
- [Incident 20200213002649I](https://openairdocs.org/incident/20200213002649I), Feb 13, 2020: Cessna 172S (N627SP), Fort Lauderdale, FL, No damage. On climb out after a touch and go on runway 9 at approximately 600 AGL the engine started to shake accompanied with burnt smell in the cockpit. The pilot…

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.