FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX96LA048 · Cessna 150H

18 Nov 1995 · Imperial, CA, United States

Cessna 150H · Accident: in flight collision with object on approach

From Palm Springs International Airport (PSP) to Imperial County Airport (IPL)

Report a problem

Event

NTSB case
LAX96LA048
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
1 · 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 150H

Aircraft type
Cessna 150
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
N23102
Onboard fatalities
Unknown
Route
From Palm Springs International Airport (PSP), Palm Springs, CATo Imperial County Airport (IPL)
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
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
In flight collision with object
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
Utility pole
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 › Altimeter, misread

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airport elevation is 56 feet below sea level. In the pilot's navigation logs under the destination airport field elevation column, '-56' was entered with '(950alt)' written next to it. The traffic pattern altitude is listed as '944 msl (1,000 agl)' in the airport facility directory. The FBO line person who communicated with the pilot observed the first landing approach and reported that it appeared to be a little high. The aircraft then initiated a go-around and made right traffic for runway 32. Ground witnesses reported that during the aircraft's traffic pattern following the go-around, the aircraft flew an extremely low pattern estimated at 100 feet agl. The pilot then contacted the FBO line person on the radio a second time. The witness stated that the pilot seemed confused about the traffic pattern altitude and airport elevation. She reportedly ask what the field elevation was, and the witness responded with 60 feet below sea level. The witness stated that the pilot responded, 'I thought it was about 900 feet.' The pilot then terminated the second approach with another go-around. According to the witnesses, the third traffic pattern was flown about the same agl altitude as the second one. Shortly after the pilot reported turning base, the power went off at the airport. A ground witness near the accident site saw the aircraft turn at a very low altitude and collide with a 40-foot-tall power pole about 1/2 mile southeast of the airport. Detailed examination of the aircraft revealed no discrepancies in any system. Review of the sun's location revealed that as the pilot turned from downwind to base, she would have been looking almost directly into the sun.

Probable cause

the student pilot's misreading of the altimeter while in the traffic pattern, which put the aircraft in dangerous proximity to the ground and obstructions. A factor in the accident was the pilot's inability to see the power pole due to sun glare as the aircraft turned onto base from downwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX96LA048
Event ID
20001207X04878
Case number
LAX96LA048
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: 38b70e404a37fcfa6f896056c1671d97ef18512d5e24727b3ad8fa519189b98e; retrieved 2026-09-20T23:31:44.781Z.