ERA14LA279 · Frederick Hays-Roth VELOCITY TWIN
Bay Area Air Frederick Hays-Roth VELOCITY TWIN · Accident: hard landing
From Sebastian Municipal Airport (X26) to Sebastian Municipal Airport (X26)
Event
- NTSB case
- ERA14LA279
- 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
Frederick Hays-Roth VELOCITY TWIN
- Aircraft type
- Frederick Hays Roth VELOCITY TWIN
- 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
- N360VT
- Operator
- Bay Area Air
- Onboard fatalities
- Unknown
- Route
- From Sebastian Municipal Airport (X26), Sebastian, FLTo Sebastian Municipal Airport (X26), Sebastian, FL
- Aircraft age
- Built the same year (2014)
- 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14LA279
- Event ID
- 20140604X02612
- Case number
- ERA14LA279
- 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. 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: d6ef952a378a4e70efa8935b1b66e4dc9da8e1a045638ff73aa87330bbcd1d07; retrieved 2026-09-15T23:44:20.564Z.