FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA149 · Cessna 172N

6 Mar 2009 · Oceanside, CA, United States

Golden Wings Flying Club Cessna 172N · Accident en route

From Montgomery-Gibbs Executive Airport (MYF) to Montgomery-Gibbs Executive Airport (MYF)

Report a problem

Event

NTSB case
WPR09LA149
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
Unknown
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
N726RJ
Onboard fatalities
Unknown
Route
From Montgomery-Gibbs Executive Airport (MYF), San Diego, CATo Montgomery-Gibbs Executive Airport (MYF), San Diego, CA
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
Defining eventThe 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
Unknown or undetermined
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During a local flight, radar data identified for the accident airplane indicated that approximately 1 hour into the flight, the airplane climbed above 12,500 feet. About 15 minutes later it climbed above 14,000 feet, and stayed above 14,000 for 42 minutes. At this point, the target was descending, and began turning to the right (west). It lost 13,000 feet in the last minute. Boaters reported seeing the airplane going nose low into the ocean. They maneuvered their boats to the site, and observed debris and an oil slick. The Coast Guard recovered several pieces of debris including a seat, which fell within the serial number range of the accident airplane. The remainder of the wreckage and the pilot were not recovered.

Probable cause

A loss of aircraft control for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA149
Event ID
20090310X30501
Case number
WPR09LA149
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 87f4b838965a9da4d1f982d35d6208db4493080201087f4ec4640920f228e854; retrieved 2026-09-13T19:59:22.699Z.