NYC08CA166 · Wim J Huisman Velocity 173 Fixed
Wim J Huisman Velocity 173 Fixed · Accident: loss of control on ground during landing
From Williston Municipal Airport (X60) to Jumbolair-Greystone Airport (17FL)
Event
- NTSB case
- NYC08CA166
- 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
Wim J Huisman Velocity 173 Fixed
- Aircraft type
- Wim J Huisman VELOCITY 173
- 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
- N127DH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Williston Municipal Airport (X60), Williston, FLTo Jumbolair-Greystone Airport (17FL), Ocala, FL
- Aircraft age
- Not recorded
- 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
- 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
- Loss of control on ground
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After landing on runway 18, the airplane rolled out for a few feet when the right wing "abruptly raised." The pilot tried to correct with right aileron input and applied full power to execute a go-around. The airplane went off the side of the runway and all three landing gear wheels were still on the ground. The pilot elected to continue the go-around and the airplane continued to roll along the ground as the pilot waited for it to reach the rotation speed of 65 knots. He did not however, see a drainage gully. The nose gear impacted the gully, the main landing gear impacted a second gully and was sheared off, and the airplane came to rest in a grassy area on the airport surface. The airplane was substantially damaged having received damage to its nose, canard, fuselage, landing gear, propeller, flight control surfaces, and wings. Runway 18 was 7,550 feet long, 210 feet wide, and consisted of asphalt. The reported wind at an airport located approximatley 8 miles southwest of the accident site, about the time of the accident, was from 230 degrees at 13 knots, gusting to 19 knots.
Probable cause
The pilot's failure to maintain directional control during the landing. Contributing to the accident was the wind gusts.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08CA166
- Event ID
- 20080515X00682
- Case number
- NYC08CA166
- 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. 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: 894f468b8724abc9e19c55eb6124a2d310461b1ec5b29e955cfdeba19ce18a71; retrieved 2026-09-15T09:39:35.075Z.