LAX98FA043 · Cessna 172N
Cessna 172N · Accident: in flight collision with terrain/water en route
From Montgomery-Gibbs Executive Airport (MYF) to an unrecorded destination
Event
- NTSB case
- LAX98FA043
- 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 172N
- Aircraft type
- Cessna 172
- 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
- N6463D
- Operator
- Richard Jones
- Onboard fatalities
- Unknown
- Route
- From Montgomery-Gibbs Executive Airport (MYF), 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 · descent
- 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 terrain/water
- 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 › Suicide, intentional
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The tower was tracking radar returns believed to be from the accident aircraft. The track continued north to a point west of the coastline. The altitude returns indicated 3,000 feet, a descent to 1,500 feet, then back to 1,800 feet before radar contact was lost. A lifeguard reported seeing an aircraft complete a loop, level off, and then nose over in a dive until the crashing into the ocean. The pilot's girlfriend contacted the operator asking if the pilot had taken off and expressed concern about a possible attempted suicide. The operator contacted the tower, but the aircraft had already departed. A friend of the pilot reported that he had been despondent recently about the death of his mother and his deteriorating health. The pilot left a hand written will dated the day before the accident. The coroner reported finding evidence of advanced coronary artery disease and a previous heart attack. He ruled the death as suicide.
Probable cause
the pilot's act of suicide by intentionally diving his aircraft into the ocean.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98FA043
- Event ID
- 20001208X09194
- Case number
- LAX98FA043
- 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: d6dc1a7d49e0d26e4f8b4f4e7a4b26372f642d9078f5c41918295f111325d9ab; retrieved 2026-09-20T22:45:26.374Z.