LAX04LA058
2003-12-04 · San Diego, California, United States · None · 1 aircraft · Status: Completed
Airport KMYF
N15C has since been reassigned. It is now registered to a different aircraft (CIRRUS DESIGN SF50, built 2024), which was not involved in this event.
Aircraft involved
Probable cause & findings
The pilot's failure to maintain directional control and to initiate a timely go-around when visual contact with the runway was lost.
Factual narrative
On December 4, 2003, about 2015 Pacific standard time, a Cessna 525, N15C, experienced a loss of control during landing and sheared the nose gear off in a collision with a taxiway pavement lip edge at Montgomery Field Airport, San Diego, California. Polestar Labs Inc., was operating the airplane under the provisions of 14 CFR Part 91. The private pilot and two passengers were not injured; the airplane sustained substantial damage. The flight departed the Mahlon Sweet Field Airport, Eugene, Oregon, about 1800, with a planned destination of San Diego. Instrument meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan had been filed. In a telephone interview, the pilot stated he was able to see the field while intercepting the instrument approach course at 3,000 feet mean sea level (msl). Using instruments for the approach, he was still able to maintain visual contact through the 100-200 feet of fog, when he reached 200 feet above ground level (agl). After descending, he lost visual contact with the runway, and everything became black. He started to move the levers up for a go-around, but noticed two red lights to his left. He thought he was too close to the ground and too slow, so he decided to land. The airplane touched down on the runway a second or two later. The pilot did not maintain directional control and the airplane veered to the left. It crossed an unpaved area, then hit and crossed a taxiway. The pavement lip edge broke the nose wheel off. The airplane continued onto another unpaved area and came to rest. It was about 50 feet to the left of runway 28R, and about 100 feet to the right of runway 5. The airplane also incurred damage to the nose gear fork assembly, pressure vessel, and to frame members. A routine aviation weather report (METAR) for Montgomery Field Airport was issued at 2018. It stated: skies partially obscured with fog; vertical visibility of 100 feet; visibility less than 1/4 mile; winds from 350 degrees at 3 knots; temperature 52 degrees Fahrenheit; dew point 52 degrees Fahrenheit; and altimeter 30.06 inHg. The pilot stated that the accident could have been prevented had he initiated a go-around when he lost visual contact with the runway. He reported no preimpact mechanical malfunctions or failures with the airplane. The airplane veered off the runway during a night landing in instrument conditions and collided with ground obstructions. The weather conditions included a visibility of less than 1/4-mile in fog, with a vertical visibility of 100 feet. The pilot stated he was able to see the field while intercepting the instrument approach course at 3,000 feet msl. Using instruments for the approach, he was still able to maintain visual contact through the 100- to 200-foot-thick layer of fog, when he reached 200 feet agl. After descending, he lost visual contact with the runway, and everything became black. He started to move the levers up for a go-around, but noticed two red lights to his left. He thought he was too close to the ground and too slow, so he decided to land. The airplane touched down on the runway a second or two later. The pilot did not maintain directional control and the airplane veered to the left. It crossed an unpaved area, then hit and crossed a taxiway. The pavement lip edge broke the nose wheel off. The airplane continued onto another unpaved area and came to rest. It was about 50 feet to the left of runway 28R, and about 100 feet to the right of runway 5. The airplane also incurred damage to the nose gear fork assembly, pressure vessel, and to frame members. The pilot stated that the accident could have been prevented had he initiated a go-around when he lost visual contact with the runway. He reported no preimpact mechanical malfunctions or failures with the airplane. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_LAX04LA058.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (loss of control, go-around). All research papers
- NTSB Safety Studies 2019 · Safety study Bell 525 Relentless In-Flight Breakup
Investigation report and safety study on the 6 July 2016 in-flight breakup of a Bell 525 Relentless helicopter prototype during a developmental flight test near Italy, Texas.
- NTSB Aircraft Accident Reports 2019 · Accident report In-Flight Breakup of Bell 525 Relentless Helicopter
Bell 525 prototype helicopter in-flight breakup near Italy, TX, July 6, 2016 — 2 fatalities. Investigation of the developmental-flight-test in-flight breakup of a Bell 525 Relentless prototype.
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER) A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.