CEN21FA130 · Velocity Vtwin
Velocity Vtwin · Accident: powerplant system/component malfunction/failure during initial climb
From Southern Wisconsin Regional Airport (KJVL) to Sebastian Municipal Airport (X26)
Event
- NTSB case
- CEN21FA130
- 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
- 2 · 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 Vtwin
- Aircraft type
- Velocity VTWIN
- 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
- N13VT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Southern Wisconsin Regional Airport (KJVL), Janesville, WITo Sebastian Municipal Airport (X26), Sebastian, FL
- Aircraft age
- About 1 year (built 2020)
- 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
- Initial climb
- 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
- Powerplant system/component malfunction/failure
- 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 oper/perf/capability
- Aircraft › Aircraft systems
- Personnel issues › Experience/knowledge
- 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 two pilots were conducting a cross-country ferry flight under a special flight permit in the experimental, twin-engine, pusher configuration airplane. The purpose of the flight was to relocate the airplane to have maintenance performed on the landing gear system. The provisions of the special flight permit indicated that the airplane be operated with the retractable landing gear extended and authorized a co-pilot even though the airplane did not require more than one crewmember.
Just after departure on the second leg of the flight, the pilot reported an engine issue to the tower controller and stated that they wanted to return to the airport but did not require any assistance. He was instructed by the controller to report turning final to the runway, an instruction he acknowledged. There was no further communication from the pilot. The controller reported that he saw the airplane just before impact in a turn consistent with maneuvering for landing when its bank angle increased until he lost sight of it behind trees. The airplane impacted trees and came to rest inverted in a river about 1 mile south of the airport, with substantial damage to the fuselage, both wings, and both canards.
Data recovered from onboard avionics and a performance study indicated that, about the same time as the pilot reported the engine problem, the airplane’s climb performance decreased similar to flight on a single engine. Indicated airspeed increased to about 16 knots above the maximum airspeed for flight with the landing gear extended (VLE), consistent with a transition from a climb pitch attitude to a level pitch attitude. Data from the onboard avionics indicated a loss of right engine power about 1 minute later, and the airplane entered a descent that continued until impact. Data from the left engine were not recorded.
The right main landing gear door separated from the airplane and was not located. Additionally, all three propeller blades from the right engine separated about 18” outboard from the propeller hub, and only one was recovered. Both the left and right engine remaining propeller sections appeared in the feathered position at the accident site. The left engine oil pressure sending unit wiring harness contained broken wires that were not consistent with impact damage. The left throttle, propeller, and mixture cockpit controls were found in a further aft position than the right controls, consistent with an intentional engine shutdown.
Based on the available information, it is likely that the damaged wiring harness resulted in the pilots receiving a red “X” on the primary flight display left engine oil pressure indication. This likely prompted the pilot’s initial call to the tower controller of an engine anomaly and the subsequent precautionary shutdown of the left engine.
As the pilots continued back toward the runway and accelerated the airplane past VLE, the right main landing gear door likely departed the airplane and impacted the right propeller, as evidenced by impact damage to the metal leading edge of the recovered propeller blade, consistent with screw or bolt threads This impact resulted in a total loss of right engine power. With both engines inoperative, the airplane likely did not have the energy available to glide back to the runway.
Recovered onboard data from the previous flight revealed that the airplane had been operated well above VLE, despite the ferry permit limitation. It is possible that the right landing gear door attachment points may have been weakened by the higher air loads associated with airspeeds exceeding VLE on the previous flight and the accident flight, as well as higher-than-normal sideslip angles that would have been required with the left engine shut down.
Toxicology testing of the left seat pilot revealed the presence of potentially impairing medications; however, whether the effects of the medications or underlying medical conditions contributed to the accident could not be determined. Although it is likely that the right seat pilot was acting as pilot-in-command, since he had previously flown the accident airplane; the pilot flying at the time of the accident could not be determined based on the available information.
Probable cause
The exceedance of the maximum airspeed for flight with the landing gear extended, which resulted in a separation of the right main landing gear door that subsequently impacted the right propeller and resulted in a total loss of right engine power. Contributing to the accident was the damaged wiring harness of the left engine oil pressure sending unit, which gave a false indication of an engine malfunction that resulted in the precautionary shutdown of the left engine.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN21FA130
- Event ID
- 20210216102636
- Case number
- CEN21FA130
- 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, 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: 7e9d149a504a8060675d92ac3c7c939aafbb6c782775db6e49bdca96e2eada36; retrieved 2026-09-15T07:25:26.525Z.