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

Vulcanair V1 accident near Salisbury, Maryland, July 22, 2022

On July 22, 2022 at about 7:45 pm local time, a 2019 Vulcanair V1, registered N979DS, was substantially damaged in an accident during landing (flare/touchdown) near Salisbury, Maryland (Salisbury Regional Airport). It was an instructional 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

The student pilot’s improper flare, which resulted in a hard landing.

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

What the record shows

Date
July 22, 2022 · about 7:45 pm local time
Place
Salisbury, Maryland · Salisbury Regional Airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Vulcanair V1 0, built 2019
Registration
N979DS · registry record · serial 1024
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The student pilot reported that he was completing his first solo cross-country flight. At the destination airport, he performed one go-around because the airplane was too high. He performed a second go-around as the airplane was not aligned with the runway. During the third attempt, he flared too high. The airplane subsequently landed hard and bounced four times before coming to rest on the runway. The student pilot added that there were no preimpact mechanical malfunction. Examination of the airplane by a Federal Aviation Administration inspector revealed that it was substantially damaged due to two fractured engine mounts. Damage to the nosegear and propeller was also observed.

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. Abnormal runway contact during landing (flare/touchdown)
  2. Hard landing during landing (flare/touchdown) defining event

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation

Dual student

  • Certificate: student
  • Flight time: 28 hours in all; 25 in this make and model; 28 in the last 90 days; 8 in the last 30 days; 3 as pilot in command
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 430 hours
  • Last inspection: annual inspection, March 23, 2022; 37 hours since
  • Maximum gross weight: 2,546 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360 (piston); 430 hours total
  • Operator: Delaware State University

The flight

  • Departed from: 33N Cheswold DE at 7:30 pm
  • Flight plan: none
  • Runway 23, 5,000 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 250° at 11 knots, gusting 15
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 91°F (33°C), dew point 72°F (22°C)
  • Altimeter: 29.94 inHg
  • Observation at 3:54 pm from KSBY

Weather report (METAR): METAR KSBY 221954Z 25011G15KT 10SM CLR 33/22 A2994

Injuries

FatalSeriousMinorNone
Flight crew1

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

4 documents, released by the NTSB on December 5, 2022. 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.