LAX06CA219
2006-06-28 · Vacaville, California, United States · Minor · 1 aircraft · Status: Completed
Airport VCB
Aircraft involved
Probable cause & findings
the pilot's failure to maintain directional control. A contributing factor was pilot fatigue.
Factual narrative
On June 28, 2006, about 0335 Pacific daylight time, a Cessna 170B, N2924D, veered off the side of the runway and ground looped at Nut Tree Airport, Vacaville, California. Monterey Bay Aviation, Inc., was operating the airplane under the provisions of 14 CFR Part 91. The renter commercial pilot and two passengers were not injured, and one passenger sustained minor injuries; the airplane sustained substantial damage. The cross-country personal flight was departing with a planned destination of Watsonville Municipal Airport, Watsonville, California. Visual meteorological conditions prevailed, and no flight plan had been filed. The pilot submitted a written report. He flew 2.7 hours from Watsonville to Little River for fuel and then to Ukiah where he and his family ate dinner and spent the night. On the day of the accident they departed Ukiah at 0800, stopped at Shelter Cove at 0900, and then flew to Brookings, Oregon, for fuel. They flew to North Bend where they refueled and added oil to the airplane, ate lunch, and shopped. At 1400, they departed North Bend, flew up the mouth of the Columbia River Gorge, and landed at Astoria for fuel and coffee. They departed Astoria and flew to Myrtle Creek, arriving there at about 2015. The pilot's family exited the airplane, and he performed three full-stop solo landings for night currency. The family boarded and the flight proceeded to Crescent City, California, where the airplane was refueled. The flight departed Crescent City airport with full fuel and the pilot navigated by pilotage to the Nut Tree airport. The Automated Surface Observing System (ASOS) for Vacaville reported the winds to be calm, and the pilot landed the airplane on runway 20 without incident. He decided to refuel the airplane at idle power, because he had experienced difficulty in starting the engine in Crescent City. The pilot then taxied to runway 2 for takeoff. He raised the tail of the airplane at a lower airspeed than normal. The airplane yawed to the left and the pilot immediately applied full right rudder. The airplane veered off the left side of the runway and bounced hard on a dirt berm. It spun around 180 degrees before coming to rest beside the runway. After exiting the airplane, the pilot noticed a steady 1- to 2-knot wind from 200 degrees. The pilot stated that the airplane and engine had no mechanical failures or malfunctions during the flight. The wind conditions at Vacaville, at 0353, were reported to be from 200 degrees at 5 knots. The pilot flew a total of 17.4 hours in 2 days with little sleep. When he signed out the airplane, the Hobbs read 34.3. The airport manager reported the Hobbs and tachometer at the time of the accident to be 51.7 and 2823.3, respectively. The airplane veered off the side of the runway and ground looped. The pilot flew 2.7 hours from Watsonville to Little River for fuel, and then to Ukiah where he and his family ate dinner and spent the night. They departed Ukiah at 0800, and flew to Brookings, Oregon, for fuel. They then flew to North Bend where they refueled and added oil to the airplane, ate lunch, and shopped. At 1400, they departed North Bend, flew up the mouth of the Columbia River Gorge, and landed at Astoria, Oregon, for fuel and coffee. They departed Astoria and flew to Myrtle Creek, arriving there about 2015. The pilot's family exited the airplane, and he performed three full-stop solo landings for night currency. The family boarded and they proceeded to Crescent City, California, where the airplane was refueled. They departed Crescent City airport with full fuel and flew to the Nut Tree Airport, Vacaville, California. The Automated Surface Observing System (ASOS) for Vacaville reported the winds to be calm, and the pilot landed on runway 20 without incident. The pilot refueled the airplane at idle power because he had experienced difficulty in starting the engine in Crescent City. He then taxied to runway 2 for takeoff. He raised the tail of the airplane at a lower airspeed than normal. The airplane yawed to the left and the pilot applied full right rudder. The airplane veered off the left side of the runway and bounced hard on a dirt berm. It spun around 180 degrees before coming to rest beside the runway. After exiting the airplane, the pilot noticed a steady 1- to 2-knot wind from 200 degrees. The pilot stated that the airplane and engine had no mechanical failures or malfunctions during the flight. The wind conditions at Vacaville, at 0353, were reported to be from 200 degrees at 5 knots. The pilot flew a total of 17.4 hours in 2 days with little sleep. On the day of the accident, the pilot had been awake about 21 hours and had flown 15 hours. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2006_LAX06CA219.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 (pilot fatigue). All research papers
- Semantic Scholar 2025 · Article (Italian National Conference on Sensors) ASFT-Transformer: A Fast and Accurate Framework for EEG-Based Pilot Fatigue Recognition
Objective evaluation of pilot fatigue is crucial for enhancing aviation safety. Although electroencephalography (EEG) is regarded as an effective tool for recognizing pilot fatigue, the direct applica…
- SKYbrary (Eurocontrol) 2023 · SKYbrary article Pilot Fatigue — SKYbrary Knowledge Base
SKYbrary pilot fatigue review — circadian biology, biomathematical models (SAFE/FAID), commuting impacts, regulatory frameworks (FAR 117 + EU 83/2014).
- NASA NTRS 2023 · Presentation Nasa Pilot Fatigue Research: Past, Present & Future
Pilot fatigue research at NASA Ames has a long history, initiated by a Congressional request to investigate the magnitude of fatigue, sleep loss and circadian disruption in flight operations, and how …
- Semantic Scholar 2023 · Article (Frontiers in Public Health) Pilot fatigue survey: A study of the mutual influence among fatigue factors in the “work” dimension
Background Fatigue risk management for pilots has received increasing attention. The existing fatigue management systems have detailed descriptions of the factors and the mutual influences among the f…
- FAA CAMI 2022 · CAMI technical report Pilot Fatigue and Sleep Patterns in Long-Range and Ultra-Long-Range Operations
Field study of crew sleep and alertness during ultra-long-range commercial operations. Combines actigraphy, sleep diaries, and PVT-B reaction tests.
- NASA NTRS 2019 · Technical Memorandum (TM) San Francisco Bar Pilot Fatigue Study
The purpose of this study was to evaluate the extent of fatigue among San Francisco Bar Pilots (Maritime Pilots) and its potential impact on safety, and to make recommendations concerning how the risk…