FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX07FA059 · Piper PA-46-350P

21 Dec 2006 · Concord, CA, United States

Piper PA-46-350P · Accident: loss of control in flight on approach

From Montgomery-Gibbs Executive Airport (MYF) to Buchanan Field (CCR)

Report a problem

Event

NTSB case
LAX07FA059
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
4 · 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
Instrument Meteorological Cond

Piper PA-46-350P

Aircraft type
Piper PA-46
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
N1AM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Montgomery-Gibbs Executive Airport (MYF), San Diego, CATo Buchanan Field (CCR), Concord, 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
Approach · circling (IFR)
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
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

  • Airspeed › Not maintained
  • Pilot in command › IFR procedure, not followed
  • Pilot in command › Stall, encountered

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

NTSB narrative

While on an instrument approach for landing, the local tower air traffic controller observed on the BRITE radar repeater scope that the airplane passed the outer marker (OM), 600 feet below the permissible crossing altitude. The controller issued a low altitude alert to the pilot and cleared him to land. The controller also reminded the pilot that the minimum descent altitude for the Localizer Directional Aid (LDA) approach was 440 feet, and provided instructions for the missed approach. At that point the pilot reported that he had the airport in sight and acknowledged the landing instructions. The controller again cleared the pilot to land on the prescribed runway for the instrument approach, and the pilot acknowledged the landing clearance. Shortly thereafter the controller instructed the pilot to execute the missed approach as the radar track showed that the airplane was off course. The pilot was instructed to initiate a climbing left turn to the VOR. The pilot said he had the airport in sight and that he saw one of the cross runways and wanted to land. The controller told the pilot that circling to that runway was not an authorized procedure for the LDA approach and again instructed the pilot to perform the missed approach. A witness stated that he was working on a storage container, about 50 feet in height, when the airplane passed overhead. He estimated the airplane to be about 50 feet higher than the storage container. The airplane made a turn westbound and the witness looked away for a second. When he looked back the airplane was in a nose and left wing down attitude and then it impacted the ground. Another witness located on the airport's north-northeast corner also observed the airplane flying toward the airport. He reported simultaneously hearing the engine power up and observed the left wing stall prior to it impacting the ground. Both witnesses reported that they did not hear anything wrong with the engine. Examination of the airframe, power plant, and propeller revealed no mechanical anomalies that would have precluded normal operation. Internal damage signatures in the engine and propeller were consistent with the production of significant power at the time of impact. A review of the weather in the area revealed that while light rain and mist were occurring near the accident site, no meteorological phenomena existed that would have adversely affected the flight.

Probable cause

Failure of the pilot to follow the prescribed instrument approach procedures and to maintain an adequate airspeed while maneuvering in the airport environment that led to a stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX07FA059
Event ID
20070109X00025
Case number
LAX07FA059
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, 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: 07b1013b88562435dca48dc6968b0a07194b7f094ef1cefb3a0401974d204cae; retrieved 2026-09-20T16:57:15.320Z.