NTSB CAROL · Event
Event NYC08LA061
Aircraft involved
Probable cause & findings
The pilot's failure to maintain aircraft control during a go-around.
Factual narrative
On December 13, 2007, about 1500 eastern standard time, a Cessna 310J, N310RV, was substantially damaged during a go-around from Hilton Head Airport (HXD), Hilton Head Island, South Carolina. The certificated commercial pilot and passenger were not injured. Visual meteorological conditions prevailed for the flight, which departed Orlando Executive Airport (ORL), Orlando, Florida, about 1330. No flight plan was filed for the personal flight conducted under 14 Code of Federal Regulations Part 91. The pilot stated that he obtained his multiengine rating about 3 months prior to the accident, and the purpose of the accident flight was to build multiengine flight experience. The airplane departed ORL about 90 minutes prior to the accident, with approximately 110 gallons of aviation gasoline. The pilot was attempting to land on runway 21, a 4,300-foot-long, 100-foot-wide, asphalt runway. During the flare, the airplane "ballooned" and floated beyond approximately two-thirds of the runway. The pilot further stated that he "briskly" advanced the throttles to initiate a go-around; however, the airplane rolled and yawed right, and then contacted the ground off the right side of the runway. The airplane came to rest upright in a ditch, and sustained damage to the wings, fuselage, and landing gear. The pilot added that at the time of the go-around, the airplane was below the minimum single engine maneuvering speed (Vmc), and the right engine either lost all power or failed to attain full power. The pilot could not recall the exact airspeed or engine rpm at the time of the accident. The passenger was also a certificated pilot. The passenger stated that at the time of the go-around, the airplane was "very slow," about 80 knots. The passenger further stated that the accident sequence happened very quickly, and he remembered hearing an increase in engine noise, but he could not be sure if it was an increase in one or both engines. He was also uncertain if the right engine lost partial or total power. The airplane had accumulated 4,724 total hours of operation. The airplane's most recent annual inspection was completed on August 25, 2007, and it accumulated 80 hours of operation from that date, until the accident. Review of a make and model airplane owner's manual revealed that the Vmc speed was 87 miles per hour (mph). The recommended safe single engine speed was 102 mph. On February 14, 2008, a Federal Aviation Administration (FAA) inspector examined the airplane's right engine. The propeller was rotated by hand, and crankshaft, camshaft, and valve train continuity were confirmed. Thumb compression was attained on all cylinders, and the magnetos rotated freely, with detents noted. In addition, the fuel distribution valve was inspected, and a fuel odor was noted on the diaphragm. No preimpact mechanical malfunctions were identified during the examination. The pilot reported a total flight experience of 379.5 hours; of which, 93.4 hours were in multiengine airplanes, with 81.9 hours in the same make and model as the accident airplane. The reported weather HXD, 1457, was: winds from 160 degrees at 5 knots; visibility 10 miles; few clouds at 3,000 feet; temperature 23 degrees Celsius; dew point 18 degrees Celsius; altimeter 30.18 inches of mercury. The pilot was attempting to land on a 4,300-foot-long, 100-foot-wide, asphalt runway. During the flare, the airplane "ballooned" and floated beyond approximately two-thirds of the runway. The pilot "briskly" advanced the throttles to initiate a go-around; however, the airplane rolled and yawed right, and then contacted the ground off the right side of the runway. The pilot stated that at the time of the go-around, the airplane was below the minimum single engine maneuvering speed (Vmc), and the right engine either lost all power or failed to attain full power. The pilot could not recall the exact airspeed or engine rpm at the time of the accident. The pilot-rated passenger stated that at the time of the go-around, the airplane was "very slow," about 80 knots. The passenger further stated that he remembered hearing an increase in engine noise, but he could not be sure if it was an increase in one or both engines. He was also uncertain if the right engine lost partial or total power. The published Vmc for the accident airplane was 87 miles per hour (mph), and the published recommended safe single engine speed was 102 mph. The pilot obtained his multiengine rating about 3 months prior to the accident. He reported a total flight experience of 379.5 hours; of which, 93.4 hours were in multiengine airplanes, with 81.9 hours in the same make and model as the accident airplane. Examination of the wreckage did not reveal any preimpact mechanical malfunctions. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2007_NYC08LA061.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- 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…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗