MIA05CA053 · Lee Harold Swarthout Velocity XLRG
Lee Harold Swarthout Velocity XLRG · Accident: loss of control on ground/water during landing
From Spruce Creek Airport (7FL6) to Spruce Creek Airport (7FL6)
Event
- NTSB case
- MIA05CA053
- 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
Lee Harold Swarthout Velocity XLRG
- Aircraft type
- Lee Harold Swarthout VELOCITY XLRG
- 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
- N121HS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Spruce Creek Airport (7FL6), Daytona Beach, FLTo Spruce Creek Airport (7FL6), Daytona Beach, 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 · landing roll
- First occurrenceThe 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/water
- 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
- Pilot in command › Directional control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that during the landing roll on runway 23, he applied brakes to slow but his left foot slipped off the brake while the right foot was still on the brake causing the airplane to veer right. He attempted to straighten out the plane by applying left rudder but was unable and the airplane traveled off the runway and collided with a fence and a ditch. He further stated at the time of the accident, the wind was from the south at about 5-10 knots, with wind gusts of 5-10 knots and light turbulence. No mechanical failure was reported by the pilot. The accident flight was the pilot's second flight test in the accident aircraft.
Probable cause
The failure of the pilot-in-command to maintain directional control of the airplane during the landing roll resulting in the on-ground collision with a fence and a ditch.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA05CA053
- Event ID
- 20050209X00163
- Case number
- MIA05CA053
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 4bad7afe18424f7e12cb9b1fd3ddfbe0ae1fe8c25f30f193b0174f9c8c8c9457; retrieved 2026-09-22T06:20:16.857Z.