FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA20LA077 · Velocity Elite RG

14 Jan 2020 · St. Petersburg, FL, United States

Velocity Elite RG · Accident: system/component malfunction/failure (non-power) during takeoff

From Albert Whitted Airport (SPG) to Orlando Executive Airport (ORL)

Report a problem

Event

NTSB case
ERA20LA077
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

Velocity Elite RG

Aircraft type
Velocity ELITE RG
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
N78BM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Albert Whitted Airport (SPG), St. Petersburg, FLTo Orlando Executive Airport (ORL), Orlando, FL
Aircraft age
About 23 years (built 1997)
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
Takeoff · rejected takeoff
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
System/component malfunction/failure (non-power)
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

  • Aircraft › Aircraft propeller/rotor
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot of the experimental amateur-built airplane stated that the first part of the takeoff roll was normal, but he noticed a sudden lack of acceleration and that the indicated airspeed was not increasing past 60 knots. He aborted the takeoff, reduced engine power to idle, and applied maximum braking. The airplane departed the end of the runway and came to rest on top of a rock embankment, resulting in substantial damage. Examination of the engine revealed no preimpact anomalies that would have precluded normal operation. Examination of the electrically-controlled variable pitch propeller system revealed that the propeller exhibited signs of inadequate maintenance as the gaps between the three propeller blades were not sealed in accordance with manufacturer guidance. Also, corrosion was present on the propeller slip rings (which would have increased electrical resistance), supercams, and spool. Additional examination revealed that the propeller would not change pitch when the switch lever was operated, though electrical continuity was confirmed from the battery to the carbon brushes that were in contact with the slip rings. Examination of the spool that controlled propeller blade pitch angle indicated that the propeller was not in the fine-pitch, high-rpm takeoff position. The planetary gearbox contained very little lubricant and there were areas that were visibly dry. Examination of the electric motor (gear motor), which powered the propeller pitch mechanism, revealed intermittent operation due to worn carbon brushes. Internal examination of the electric motor revealed a broken end on one of the armature coil windings that surrounded one of the three electromagnetic coils in the electric motor, indicating that the motor needed replacement. Review of propeller system maintenance records revealed no entries regarding preventive maintenance of the system in the approximate 2 years before the accident. The propeller manufacturer’s written guidance regarding operation of the propeller revealed that, before takeoff, the engine should be run at wide open throttle and the propeller blade pitch adjusted to the maximum horsepower rpm. Had the pilot performed this check, it would have been apparent that the propeller was not in the correct takeoff setting. Wind conditions at the time of the accident were consistent with a 9-knot tailwind, which would have increased the distance necessary for takeoff and placed the airplane farther down the runway when the pilot aborted takeoff.

Probable cause

A failure of the propeller pitch change electric motor, which resulted in an improper setting for takeoff and a subsequent runway overrun. Also causal was the inadequate maintenance and inspection of the propeller system and the pilot’s failure to follow the propeller manufacturer’s pretakeoff guidance, which would have indicated that the propeller was not in the takeoff position. Contributing to the accident was the pilot’s decision to depart with a tailwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20LA077
Event ID
20200115X81659
Case number
ERA20LA077
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, cause areas. 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: b2722135dd03a3596a2793fbb13cca93153cdd1205bd28864cb3d6599d75d09c; retrieved 2026-09-16T10:57:02.484Z.