IAD02LA022
2001-12-30 · Tappahannock, Virginia, United States · None · 1 aircraft · Status: Completed
Airport W79
N10MS has since been reassigned. It is now registered to a different aircraft (BELL 206B, built 1980), which was not involved in this event.
Aircraft involved
Probable cause & findings
The pilot's inadequate compensation for the gusty wind conditions. Factors in the accident were the gusty wind conditions and the total loss of left engine power due to the alternate air valve becoming disconnected and embedded in the fuel injector servo.
Factual narrative
On December 30, 2001, about 1110 eastern standard time, a Cessna 310H, N10MS, was substantially damaged while landing at the Tappahannock Airport (W79), Tappahannock, Virginia, following a total loss of left engine power, during cruise flight. The certificated commercial pilot and two passengers were not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the flight, between Asheville Regional Airport (AVL), Asheville, North Carolina, and Laurence G. Hanscom Field (BED), Bedford, Massachusetts. The personal flight was conducted under 14 CFR Part 91. According to the pilot, he departed Asheville about 0900. The flight was "uneventful" until about 30 miles northeast of Richmond, Virginia, when the left engine lost power. The pilot attempted to restart the engine, but was unsuccessful. He secured the engine, and contacted Richmond Approach Control for information on the closest airport. The pilot was informed that Tappahannock Airport was 10 miles ahead, and he prepared for a landing on runway 02, a 2,785-foot-long, 75-foot-wide runway. After a "normal" approach to the runway, during the landing flare, a gust of wind forced the left wing down. The wing struck the runway, and the airplane slid to a stop off the left side, coming to rest in the grass area. The pilot stated that Richmond Approach reported the winds from 330 degrees at 6 knots, gusting to 22 knots. An examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed substantial damage to the left wing and engine firewall. Examination of the engine revealed that the alternate air valve had broken off and was observed embedded in the fuel injector servo. The aluminum hinge which connected the alternate air valve to the airbox assembly remained attached to the valve and appeared worn where a steel cotter pin had connected the two pieces. The steel cotter pin remained attached to the airbox assembly and the holes in which it was housed appeared elongated. A review of the airplane and engine logbooks by the FAA inspector revealed that the last annual inspection was performed in May 2001. No work entries pertaining to the alternate air valve were observed in the logbooks. The pilot reported 5,117 hours of total flight time, 10 of which were in make and model. He additionally reported 38 hours of multi-engine flight experience. The winds reported at 1055, at Patuxent Naval Air Station, located 30 miles to the northeast, were from 230 degrees at 8 knots. The winds reported at 1155, were from 230 degrees at 9 knots, gusting to 14 knots. The winds reported at 1054, at Richmond International Airport (RIC), Richmond, Virginia, 30 miles to the southwest, were variable at 5 knots. Richmond International Airport consisted of 6 runways, one of which was oriented on a heading of 340 degrees. According to the Cessna 310H Pilot Operating Handbook, the last item under the Engine Failure During Flight Checklist was to "land at the nearest suitable airport." While in cruise flight, the airplane's left engine lost total power. The pilot elected to perform a single-engine landing at the nearest airport, on runway 02. During the landing flare, a gust of wind forced the left wing down and it struck the runway. The airplane continued off the left side of the runway and came to rest in the grass area. The winds reported by an air traffic controller from an airport 30 miles to the southwest, were from 330 degrees at 6 knots, gusting to 22 knots. The airport where the winds were reported from had six runways, one of which was oriented on a heading of 340 degrees. Examination of the engine revealed that the alternate air valve had broken off and was observed embedded in the fuel injector servo. According to the Cessna 310H Pilot Operating Handbook, the last item under the Engine Failure During Flight Checklist, was to land at the nearest suitable airport. The pilot reported 5,117 hours of total flight experience, 10 of which were in make and model. He additionally reported 38 hours of multi-engine flight experience. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2001_IAD02LA022.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 (engine failure). All research papers
- arXiv 2022 · arXiv preprint Multi-level Adaptation for Automatic Landing with Engine Failure under Turbulent Weather
This paper addresses efficient feasibility evaluation of possible emergency landing sites, online navigation, and path following for automatic landing under engine-out failure subject to turbulent wea…
- NASA NTRS 2019 · Conference Paper Simulation of Liquid Rocket Engine Failure Propagation Using Self-Evolving Scenarios
Traditional probabilistic risk assessment approaches often require failure scenarios to be explicitly defined through event sequences that are then quantified as part of the integrated analysis.
- NASA NTRS 2019 · Conference Paper Rocket engine failure detection using system identification techiques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
- NASA NTRS 2019 · Conference Paper Rocket engine failure detection using system identification techniques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
- NASA NTRS 2019 · Technical Memorandum (TM) A simulator investigation of engine failure compensation for powered-lift STOL aircraft
A piloted simulator investigation of various engine failure compensation concepts for powered-lift STOL aircraft was carried out at the Ames Research Center.
- Semantic Scholar 2019 · Article (AIAA Scitech 2019 Forum) Impact of Engine Failure Constraints on the Initial Sizing of Hybrid-Electric GA Aircraft
Potential advantages of hybrid-electric aircraft are fuel savings, lower emissions, and reduced noise. Since these aircraft generally apply multiple power sources, they can also be designed to sustain…