MIA05CA089 · Aerostar, S.A Yak-52TW
Aerostar, S.A Yak-52TW · Accident: loss of control on ground/water during landing
From Space Coast Regional Airport (KTIX) to Spruce Creek Airport (7FL6)
Event
- NTSB case
- MIA05CA089
- 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
Aerostar, S.A Yak-52TW
- Aircraft type
- Aerostar YAK-52
- 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
- N610RG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Space Coast Regional Airport (KTIX), Titusville, 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 · flare/touchdown
- 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 stated, during approach he encountered rough air. He noted the windsock was swinging from side to side. He decided to make a three-point landing, in order to have more control of the airplane on the runway. During the flare the tail wheel touched first, and the airplane ballooned slightly. A wind gust hit the right wing, which veered the plane to the left. He saw a number of people standing in the Windsock Park next to runway. His concern was to avoid the group of observers. He added some power to gain rudder control and corrected to the right. The right wing tip touched the runway, which jammed the controls. At that point, control of the airplane was lost. The airplane skidded off the left side of the runway, shearing both main landing gears and impacting trees before coming to a stop.
Probable cause
Pilot's failure to maintain directional control in a variable wind condition during landing resulting in the airplane departing the runway subsequent landing gear separation and impact with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA05CA089
- Event ID
- 20050510X00582
- Case number
- MIA05CA089
- 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: 679fcdcf3e8365f88184785dfb3c1c0e362c3af39afc0dfbdefb5ca3013308be; retrieved 2026-09-21T19:03:03.977Z.