ERA13CA181 · Cessna 172 K
Ryans Dream Cessna 172 K · Accident: windshear or thunderstorm while taxiing
From Miami Executive Airport (TMB) to Deland Municipal Sidney H Taylor Field (DED)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA13CA181
- 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
- Instrument Meteorological Cond
Cessna 172 K
- Aircraft type
- Cessna 172
- 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
- N7113G
- Operator
- Ryans Dream
- Onboard fatalities
- Unknown
- Route
- From Miami Executive Airport (TMB), Miami, FLTo Deland Municipal Sidney H Taylor Field (DED), DeLand, 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
- Taxi · from runway
- 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
- Windshear or thunderstorm
- 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
- Environmental issues › Conditions/weather/phenomena
- 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
According to the pilot, he elected to land because there were thunderstorms between his location and the destination airport. He landed the airplane without incident and was taxiing to a parking area when the wind increased. The wind lifted the tail of the airplane; it nosed over and came to rest inverted, resulting in substantial damage to the wings and empennage. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The weather reported at an airport located 6 miles east of the accident location indicated thunderstorm activity and wind from 240 degrees at 14 knots, gusting to 19 knots; peak wind gusts of 52 knots were recorded repeatedly during a 30 minute period around the time of the accident.
Probable cause
The pilot's loss of airplane control while taxiing in gusting wind conditions associated with nearby thunderstorm activity.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13CA181
- Event ID
- 20130325X21729
- Case number
- ERA13CA181
- 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: 651c6c0586320ae62184078fc1671f77e23b11a90dbad9d90a3033a2787e4ff3; retrieved 2026-09-15T21:09:27.905Z.