The U.S. aircraft register, updated daily
Accidents · NTSB ERA21LA031 · Final report

Sparrowhawk II accident near North Myrtle Beach, South Carolina, October 7, 2020

On October 7, 2020 at about 9:30 pm local time, a 2007 Sparrowhawk II (gyroplane), registered N40380, was substantially damaged in an accident during enroute near North Myrtle Beach, South Carolina (None airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A ruptured fuel line, which resulted in fuel starvation to the engine and a total loss of engine power.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 7, 2020 · about 9:30 pm local time
Place
North Myrtle Beach, South Carolina · None · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Sparrowhawk II NO SERIES, built 2007
Registration
N40380 · registry record · serial 114
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot of the gyrocopter reported that he departed with full fuel tanks for a local flight. While flying along a coastline, the engine lost power, and the pilot navigated to complete a forced landing on a beach. During the landing rollout, the nose wheel dug into soft sand and the gyrocopter rolled over onto its left side, which resulted in substantial damage to the main rotor and empennage. Postaccident examination of the gyrocopter’s engine revealed that a rubber fuel supply line was ruptured. Given this information, it is likely that the fuel leak starved the engine of fuel, which resulted in a total loss of engine power.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Sys/Comp malf/fail (non-power) during enroute
  2. Fuel starvation during enroute defining event

The NTSB's findings

  • Aircraft › Aircraft systems › Fuel system › Fuel distribution › Failure

Pilot

  • Certificate: private
  • Ratings: single-engine land; rotorcraft: gyroplane
  • Flight time: 1,500 hours in all; 575 in this make and model; 23 in the last 90 days; 8 in the last 30 days; 1,500 as pilot in command
  • Last flight review: October 18, 2019
  • Medical certificate: BasicMed (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 566 hours
  • Last inspection: annual inspection, April 20, 2020
  • Maximum gross weight: 1,200 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Subaru 2.5 (piston); 566 hours total

The flight

  • Departed from: SC21 Loris SC at 8:00 pm
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 220° at 10 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 79°F (26°C), dew point 72°F (22°C)
  • Altimeter: 29.95 inHg
  • Observation at 5:53 pm from CRE, 5 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

3 documents, released by the NTSB on June 24, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.