LAX03LA276
2003-09-02 · Novato, California, United States · None · 1 aircraft · Status: Completed
Airport DVO
Aircraft involved
Probable cause & findings
The pilot's decision to attempt VFR flight into instrument meteorological conditions during the dark early morning takeoff, which resulted in spatial disorientation and lead to a collision with trees off the departure end of the runway.
Factual narrative
On September 2, 2003, at 0545 Pacific daylight time, a Mooney M20K, N252AK, collided with trees shortly after takeoff from Gnoss Field Airport (DVO), Novato, California. The airplane was operated by the pilot/owner under the provisions of 14 CFR Part 91, and sustained substantial damage. The private pilot, the sole occupant, was not injured. Instrument meteorological conditions prevailed for the local area flight that was scheduled to terminate at Oakland International Airport (OAK), Oakland, California. An instrument flight rules (IFR) flight plan had been filed, but had not been activated. The pilot was interviewed by the Safety Board Investigator-in-Charge. The pilot stated he had received a weather briefing from a direct user access terminal (DUAT) service and there was no significant weather for the flight from Novato to Oakland. He reported the flight was to take place in the early morning, 0545, so it was dark outside. On the takeoff roll out, some jackrabbits passed in front of the airplane. The pilot stated that the rotation was normal, but he forgot to retract the landing gear. While he was trying to figure out why the airplane would not climb, it impacted trees off the departure end of the runway. The pilot was interviewed by a Federal Aviation Administration (FAA) inspector. The pilot stated that he filed an IFR flight plan, but decided to depart using visual flight rules (VFR). The weather report he received indicated clear weather along the route, and the sky was clear at DVO with visibilities greater than three miles. During the takeoff roll jackrabbits ran across the runway and caused a minor distraction. The pilot reported that after rotation there were no ground lights, and no visible horizon. At that point he engaged the autopilot. After he engaged the autopilot, he noted that the airplane was not climbing as expected. Before he was able to determine what the problem was the stall warning activated. He disengaged the autopilot and attempted to lower the nose. The pilot reported that the airplane then entered the trees. He also noted his airspeed approached 95 knots. Numerous attempts to obtain a written statement from the pilot were unsuccessful. According to the United States Naval Observatory sunrise for the date of the accident was at 0541. Weather obtained from the Federal Aviation Administration for the DVO area at the time of the accident was reported as 1/8-mile visibility and overcast clouds at 100 feet. Napa, California, elevation 35 feet mean sea level (msl), is located about 060 degrees at 14 nautical miles from the accident location. At 0454, reported weather conditions were: winds from 230 degrees at 4 knots; visibility 8 miles; a broken cloud layer at 500 feet; temperature 53 degrees Fahrenheit; dew point 53 degrees Fahrenheit; and altimeter setting 29.88 inches Hg. At 0554, the weather was reported as calm winds; visibility 7 miles; a scattered cloud layer at 500 feet; temperature 53 degrees Fahrenheit; dew point 51 degrees Fahrenheit; and altimeter setting 29.89 inches Hg. The airplane was inspected at Plain Parts in Pleasant Grove, California on November 3, 2003. No discrepancies were noted with the airframe or engine.
PERSONNEL INFORMATION
A review of Federal Aviation Administration (FAA) airman records revealed the pilot held a private pilot certificate with a rating for instrument airplane. The private pilot certificate, with the airplane single-engine land rating, was issued on January 27, 1997. The pilot held a third-class medical certificate that was issued on August 13, 2003. It had the limitation that the pilot must have available glasses for near vision.
ADDITIONAL INFORMATION
The airplane was released to the owner's representative on December 18, 2003. During the initial climb-out the airplane collided with trees off the departure end of the runway. The pilot had filed an instrument Flight Rules flight plan, but decided to fly according to Visual Flight Rules to his destination airport. He indicated that it was still dark outside for the early morning flight. The pilot said that during the initial climb-out he lost visual reference with the ground due to the lack of ground lights and a visible horizon. He activated the autopilot; however, the airplane was not climbing as expected. As he was trying to figure out what the problem was the stall warning activated, he disengaged the autopilot, and attempted to lower the nose. The airplane simultaneously collided with trees. Weather in the accident site at the time of the accident was reported by witnesses to be 1/8-mile visibility with overcast clouds at 100 feet. The pilot stated that there were no mechanical anomalies noted with the airplane. According to the US Naval Observatory, sunrise for the date and location of the accident was at 0541. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_LAX03LA276.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 (stall, spatial disorientation, autopilot). All research papers
- NASA NTRS 2026 · Conference Paper Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- arXiv 2025 · arXiv preprint ROSflight 2.0: Lean ROS 2-Based Autopilot for Unmanned Aerial Vehicles
ROSflight is a lean, open-source autopilot ecosystem for unmanned aerial vehicles (UAVs). Designed by researchers for researchers, it is built to lower the barrier to entry to UAV research and acceler…
- arXiv 2025 · arXiv preprint ROSplane 2.0: A Fixed-Wing Autopilot for Research
Unmanned aerial vehicle (UAV) research requires the integration of cutting-edge technology into existing autopilot frameworks.
- Embry-Riddle Scholarly Commons 2025 · Journal article (IJAAA) Design, Implementation, and Testing of Spatial Disorientation Scenarios in a Modified Hexapod Motion Simulator
Abstract Investigations into aviation accidents aim to identify root causes and enhance safety. Despite advancements in safety measures, technology, and education, general aviation accident rates rema…
- arXiv 2024 · arXiv preprint A Data-Driven Autopilot for Fixed-Wing Aircraft Based on Model Predictive Control
Autopilots for fixed-wing aircraft are typically designed based on linearized aerodynamic models consisting of stability and control derivatives obtained from wind-tunnel testing.
- arXiv 2023 · arXiv preprint Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.