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

Amateur-built VELOCITY TWIN accident near Sebastian, Florida, June 2, 2014

On June 2, 2014 at about 9:00 pm local time, a 2014 amateur-built VELOCITY TWIN, registered N360VT, was substantially damaged in an accident during landing (flare/touchdown) near Sebastian, Florida (Sebastian Muni 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

The pilot’s improper landing flare, which resulted in a bounced landing. Also causal to the accident were the pilot’s subsequent delayed decision to abort the landing and his improper execution of the aborted landing, which resulted in the airplane exceeding its critical angle-of-attack and experiencing an aerodynamic stall.

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

What the record shows

Date
June 2, 2014 · about 9:00 pm local time
Place
Sebastian, Florida · Sebastian Muni · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Amateur-built VELOCITY TWIN, built 2014
Registration
N360VT · registry record · serial VT004
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot/owner reported that he accompanied the chief pilot of the airplane kit manufacturer on operational ground and flight tests of the airplane following the installation of a rebuilt left propeller. The tests were "normal," and the chief pilot deplaned. The pilot then serviced the airplane with fuel and departed to perform three solo takeoffs and landings. On the third takeoff, the airplane pulled left and required hard right rudder to maintain runway alignment. When the airplane was about traffic pattern altitude, the pilot noted a 1,200-rpm difference between the left and right engines; the left engine was producing 1,400 rpm, and the right engine was producing 2,600 rpm. While flying the remainder of the traffic pattern, the pilot attempted to troubleshoot and get the rpm on the two engines to match until he was on final approach to the runway. The pilot reduced the engine power to idle as the airplane crossed the runway threshold, and the airplane "floated awhile" before touching down and subsequently bouncing again. The pilot stated that, during the second touchdown, the left wing lifted "due to the crosswind from the left" and that he had inadequate speed to control the airplane. The pilot chose to abort the landing after the second bounce when the airplane was at a 45-degree, nose-high attitude. Both engines accelerated to full power, but the airplane collided with the runway, and both main landing gear and propellers were separated. Examination of the propeller assembly revealed no preimpact mechanical anomalies, and all noted damage was consistent with impact and overstress.

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. Unknown or undetermined during approach (VFR pattern downwind)
  2. Hard landing during landing (flare/touchdown) defining event
  3. Runway excursion during landing (landing roll)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft propeller/rotor › Propeller system › (general) › Not specified
  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane
  • Flight time: 1,470 hours in all; 15 in this make and model; 18 in the last 90 days; 4 in the last 30 days
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 55 hours
  • Last inspection: condition inspection, February 7, 2014; 55 hours since
  • Maximum gross weight: 3,200 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine 1: Lycoming IO-320 (piston); 55 hours total
  • Engine 2: Lycoming IO-320 (piston); 55 hours total
  • Operator: Bay Area Air LLC

The flight

  • Departed from: X26 Sebastian FL at 8:30 pm
  • Destination: X26 Sebastian FL
  • Flight plan: none
  • Runway 10, 3,199 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 080° at 12 knots, gusting 15
  • Visibility: 10 statute miles
  • Sky: overcast at 3,600 ft
  • Temperature: 79°F (26°C), dew point 66°F (19°C)
  • Altimeter: 30.09 inHg
  • Observation at 8:53 pm from VRB, 11 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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.