NTSB CAROL · Event
Event GAA16LA135
Aircraft involved
Probable cause & findings
The pilot's misidentification of a parallel roadway for the runway and the airplane's subsequent collision with numerous objects during landing.
Factual narrative
HISTORY OF FLIGHTOn February 18, 2016 about 1815 eastern standard time, an experimental amateur-built Van's RV-7A airplane, N705RP, landed on a roadway and nosed over near the Tavernaero Park Airport (FA81) in Tavernier, Florida. The private pilot sustained no injuries. The airplane was registered to BBK Aircraft LLC, Sherrills Ford, North Carolina, and operated by the pilot as a dusk, visual flight rules personal flight under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed at the time of the accident, and no flight plan was filed. The flight originated from the Marco Island Airport (MKY) in Marco Island, Florida, about 1745. The pilot reported he was conducting an approach to runway 8 when he noticed a car off the side of the runway on a parallel access road. He reported that he was concerned with the proximity of the car to his intended landing area and he executed a go-around. With dusk approaching, he made the decision to make an "abbreviated" traffic pattern and "circle back around" to land on the runway. He applied full power, began the turn, and reported that the engine "backfired." He reported that the airplane was not "climbing normally" and as he made his turn, he was unable to gain sufficient altitude to maintain sight of the runway. The pilot reported that he circled back to the runway heading and viewed what he believed were the homes along the side of the runway threshold. He reported that the airplane was still unable to climb, but he anticipated that the runway would appear after he had cleared a small block of homes. He further reported that when the runway did not appear, and without the airplane being able to climb, he committed to landing on a road which was two blocks south of and parallel to the runway. During the landing roll, the airline impacted a three mail boxes, a basketball hoop, a couple of residential telephone lines, and a car and then came to rest upside-down in a bush. The airplane sustained substantial damage to both wings, the fuselage, the rudder, the firewall, and the engine mounts. In a written statement to the National Transportation Safety Board, a Florida State Trooper who responded to the scene of the accident reported in part that, about 6:38 pm, he was dispatched to an aircraft crash on Plantation Ave in Tavernier. Upon his arrival, he observed a yellow and white airplane bearing the tail number N705RP upside down in a driveway. He identified the pilot by his pilot license. The pilot was standing by a crowd of people uninjured, and the pilot reported that he had been the only person on the airplane. The trooper reported that he asked the pilot what happened, and the pilot responded ,"This is my first time down here at this landing strip and I thought that the side road (Plantation Ave) was the runway". The pilot further told the trooper that there were no mechanical or weather issues as he was attempting to land. WRECKAGE AND IMPACT INFORMATIONThe photographs of the wreckage provided by the Federal Aviation Administration showed that the airplane came to rest upside-down in a bush in a residential area. Both wings and the rudder sustained substantial damage from impact. The airframe and engine were not examined by the National Transportation Safety Board. The private pilot was landing the experimental, amateur-built airplane at a residential airpark. Immediately following the accident, a state trooper interviewed the pilot, who stated that the landing was his first one at the residential airpark and that he thought that the side road was the runway. The pilot reported that there were no mechanical or weather issues as he was attempting to land. The airplane struck three mailboxes, a basketball hoop, phone lines, and a car and then came to rest inverted. In a later statement, the pilot reported that, during landing, he noticed a car off the side of the runway on a parallel access road. He was concerned with the proximity of the car to his intended landing area, and he executed a go-around. With dusk approaching, he decided to make an "abbreviated" traffic pattern and "circle back around" to land on the runway. He applied full power, began the turn, and reported that the engine "backfired." The airplane did not climb normally, and as the pilot turned the airplane, it was unable to gain sufficient altitude for the pilot to maintain sight of the runway. Given the pilot's statement, it is likely that he misidentified the parallel access road for the runway and, upon landing, hit multiple obstacles. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Experience/knowledge-Knowledge-Knowledge of geographic area-Pilot - C
- C Personnel issues-Psychological-Perception/orientation/illusion-Situational awareness-Pilot - C
- C Personnel issues-Task performance-Planning/preparation-Flight planning/navigation-Pilot - C
- — Environmental issues-Conditions/weather/phenomena-Light condition-Low light-Effect on personnel
- — Environmental issues-Physical environment-Object/animal/substance-Wire-Contributed to outcome
- — Environmental issues-Physical environment-Object/animal/substance-Pole-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2016_GAA16LA135.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 ↗