FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00FA209 · Cessna 152

31 May 2000 · Palm Springs, CA, United States

The FLT School At Palm Springs Cessna 152 · Accident: loss of control in flight on approach

From Jacqueline Cochran Regional Airport (TRM) to Palm Springs International Airport (PSP)

Report a problem

Event

NTSB case
LAX00FA209
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 152

Aircraft type
Cessna 152
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N5538M
Onboard fatalities
Unknown
Route
From Jacqueline Cochran Regional Airport (TRM), Thermal, CATo Palm Springs International Airport (PSP)
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern base
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/spin
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command(cfi) › Airspeed, not maintained

Approximate · Estimated position: the centre of Palm Springs, CA, the place the record names. Not the accident site.

NTSB narrative

While on base leg turning to final approach at the desert airport, the instructional flight was authorized by the air traffic control tower to perform s-turns for spacing due to another aircraft stopped in position on the runway and starting the takeoff roll. Witnesses observed the aircraft's wings rock steeply right and left and then the aircraft dove nose-first to the ground from about 250 feet agl. The recently certificated flight instructor had worked as an instructor for about 1 month and had 363 total flight hours. The flight was the student's first fixed-wing aircraft instructional flight, although he had about 60 hours experience in helicopters and the foreign equivalent of a private pilot certificate. Witnesses said that surface wind varies greatly in the area near the accident site. Two witnesses, one located 1/2 block south of the accident site and the other located two blocks east of the accident site, reported the surface wind was calm. A third witness, located two blocks north of the accident site, reported the wind was blowing about 40 knots. This third witness reported that when she arrived at the accident site, soon after it happened, and got out of her car, the wind blew her hat off and across the street. Ten minutes later the wind stopped and it became completely still. At the airport, about 1 mile southeast of the accident location, the surface wind remained less than 12 knots in the period from 2 hours before the accident to about 2 hours after it. Several pilots reported that wind shear is common in the area due to terrain induced eddies from nearby mountains. The airport did not have a low-level wind shear alert system. One witness reported the engine was 'sputtering' and another said it was silent; however, at the accident site the propeller exhibited deep leading edge damage, torsional twisting, and chordwise striations on the front face. No mechanical anomalies were found.

Probable cause

The failure of the pilot/flight instructor to maintain sufficient airspeed to prevent the aircraft stalling and spinning. Factors in the accident were terrain induced windshear and sudden wind shift and the pilot/flight instructor's lack of total experience.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00FA209
Event ID
20001212X21029
Case number
LAX00FA209
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 76ae70dbeee5be2515bc3376d0813fd1471c0e4140c89d245f97badef4095d06; retrieved 2026-09-20T21:11:16.362Z.