FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16LA135 · Pinkston Randy T RV-7 A

18 Feb 2016 · Tavernier, FL, United States

Pinkston Randy T RV-7 A · Accident on approach

From Marco Island Executive Airport (MKY) to Tavernaero Park Airport (FA81)

Report a problem

Event

NTSB case
GAA16LA135
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Pinkston Randy T RV-7 A

Aircraft type
Pinkston Randy RV-7
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N705RP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Marco Island Executive Airport (MKY), Marco Island, FLTo Tavernaero Park Airport (FA81), Tavernier, FL
Aircraft age
About 11 years (built 2005)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern final
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Miscellaneous/other
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire; Pole
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Experience/knowledge
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

The pilot's misidentification of a parallel roadway for the runway and the airplane's subsequent collision with numerous objects during landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16LA135
Event ID
20160222X31119
Case number
GAA16LA135
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 3a5bef98d2b7dc5aec5514986f8aee4d92b7a94c7a8c48a1d919812550df22e8; retrieved 2026-09-16T03:10:18.531Z.