FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00LA296 · Cessna 150

12 Aug 2000 · Carlsbad, CA, United States Possible conflict

Cessna 150 · Accident: total loss of engine power (mechanical failure) en route

From Gillespie Field (SEE) to an unrecorded destination

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
LAX00LA296
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
0 · 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
Instrument Meteorological Cond

Cessna 150

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
N6500T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gillespie Field (SEE), San Diego, CATo not recorded
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
En route · cruise
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
Total loss of engine power (mechanical failure)
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

  • Reason for occurrence undetermined

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

NTSB narrative

The aircraft ditched in the Pacific ocean about 20 miles west of Carlsbad, California, following a loss of engine power while on fish spotting operations. The airplane sank and is presumed to be destroyed. The pilot said that about 40 miles offshore the engine rpm's began a slow decay accompanied by a loss of oil pressure and an increase in oil temperature. The pilot reversed course and headed toward Carlsbad, the closest airport. About 20 miles out from shore the engine lost all power with a loud bang and the pilot ditched the airplane at 33 degrees 10 minutes north latitude by 117 degrees 45 minutes west longitude. A passing fishing boat picked up the pilot. The pilot was unable to reconstruct the maintenance history of the aircraft.

Probable cause

A catastrophic internal engine failure for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00LA296
Event ID
20001212X21772
Case number
LAX00LA296
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: b13404b1f01636d0c8a81c406bfcf90b5455a139c823779580b9ff33c70398a1; retrieved 2026-09-21T20:07:20.017Z.