Cessna 172S accident near Palm Springs, California, April 3, 2002
On April 3, 2002 at about 6:30 pm local time, a Cessna 172S, registered N627SP, was substantially damaged in an accident near Palm Springs, California (Palm Springs International airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot lost directional control and collided with a runway edge light and taxiway sign.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 3, 2002 · about 6:30 pm local time · cases in 2002
- Place
- Palm Springs, California · Palm Springs International · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172S · all 172Ss on the register
- Registration
- N627SP · registry record · serial 172S8621
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane collided with a runway edge light and taxiway sign after the pilot loss directional control due to unintentionally hitting the brakes during his landing. The pilot was able to regain control and guide the airplane back onto the runway.
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
Dual student
- Certificate: student
- Flight time: 30 hours in all; 30 in this make and model; 30 in the last 90 days; 15 in the last 30 days; 4 as pilot in command
- Medical certificate: Class 3
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,211 hours
- Last inspection: 100-hour inspection, April 3, 2002
- Maximum gross weight: 2,200 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-360-L2A (piston); 0 hours total
The flight
- Departed from: PSP Palm Springs CA at 6:00 pm
- Flight plan: none
- Runway 13, 4,800 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 82°F (28°C), dew point 39°F (4°C)
- Altimeter: 29.87 inHg
- Observation at 6:53 pm from PSP
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 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.
Connections how this case links to the rest of the register
- N627SP on the register today · the tail number may have moved to another aircraft since
- Cessna 172 Skyhawk 20,692 registered today · the model family and its accident history
- Cessna 72,677 aircraft on the register
- Engine: Lycoming IO-360-L2A 2,651 aircraft carry this series today · as the NTSB recorded it
- Palm Springs International · nearest airport
- Accidents and incidents in California 9,080 since 1982 · 1,094 in the last ten years
- California 28,286 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/LAX02LA130.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.
