NTSB CAROL · Event
Event MIA02LA097
Aircraft involved
Probable cause & findings
The pilot's failure to maintain compensation for surface wind conditions resulting in excessive taxi speed, a loss of control while taxiing, an excursion off the taxiway, collision with a concrete pad, and a nose over.
Factual narrative
On May 22, 2002, about 0542 eastern daylight time, a Cessna 206H, N24013, registered to Air Carriers, Inc., operating as a Title 14 CFR Part 91 positioning flight, sustained a taxi accident on the Sarasota/Bradenton International Airport, Sarasota, Florida. Visual night meteorological conditions prevailed and an instrument flight plan had been filed for Saint Petersburg-Clearwater International Airport. The aircraft received substantial damage, and the airline transport-rated pilot, the sole occupant, was not injured. The flight was taxiing for takeoff when the accident occurred. According to the FAA Form 8020-9, "Aircraft Accident/Incident Preliminary Notice", that was sent from Sarasota tower personnel to the FAA, Tampa FSDO, the following was noted, "Pilot reported that he ran off the end of taxiway "D" due to excessive tailwind". According to the pilot's statement to the Manatee Airport Authority, he noticed an animal out of the corner of his eye and slammed on his brakes, causing him to lose control and leave the taxiway, hitting an electrical vat, and causing the aircraft to flip. According to the pilot's statement to the FAA, as he was taxiing southwest on taxiway "D" for takeoff from runway 04, he became distracted, (possibly by an animal that barely caught his eye off the left side of the aircraft) in the darkness, and missed the turn onto the runway. The aircraft ran off the end of the taxiway into the sand and grass airport infield area, the nose gear and propeller collided with a square concrete wiring junction box, and the aircraft sustained a nose over. The pilot said there were no mechanical malfunctions of his aircraft at the time of the accident interview. According to an FAA inspector, the pilot was taxiing down taxiway "D". There are tire skid marks where the taxiway starts to turn to the runway. The left main tire mark was measured at over 102 feet. The right main tire mark was measured at over 77 feet, and there are marks left by the nose wheel of over 68 feet. Following the excursion off the taxiway, the skid marks continue for another 29 feet until impact between the nose wheel and a concrete junction box, where the nose wheel was found separated from the nose gear strut. The aircraft was found inverted about a plane-length beyond the junction box, having flipped over 180 degrees, heading in the opposite direction from the original taxi direction. An FAA certified Aircraft Inspector examined the wreckage, post accident. Brake pad thickness measured over twice the minimum thickness required by Cessna maintenance specifications. There were no indications of hydraulic fluid leakage, except that the aircraft was still in an inverted position on a flat-bed trailer, and hydraulic fluid had leaked out of the master cylinders through the vent holes. According to the pilot's written statement sent to the NTSB, he was taxiing the aircraft to runway 04 on taxiway "D" at a normal taxi speed, and as he approached the hold short line to runway 04, he applied brakes, but the brakes grabbed, and the aircraft did not decelerate. The aircraft exited the taxiway into the grass, made contact with the cement slab, pitched down, and had just enough energy to flip inverted. During a subsequent telephone conversation with the NTSB on June 12, 2002, the pilot stated that he was, "going fast" and that he, "might have unconsciously picked up speed because [his direction of taxi was] directly downwind, and it was pitch black." He further mentioned being distracted by either an animal or lights to his left about 200 yards. That location would have corresponded to the ramp area and terminal across runway 04, and the pilot mentioned observing an aircraft in that area being either catered or loaded. He stated his scheduled departure time was 0530 and that engine start was 0538 for the empty ferry flight to Saint Petersburg-Clearwater. He stated the taxiways were not particularly wet, as with morning dew. The reported surface winds at 0553 for the airport were from 030 degrees at 10 knots. The pilot stated he was taxiing in a 10 knot tail wind in "pitch black" night conditions. An animal or lights off the left side of the aircraft distracted his attention. Near the end of the taxiway he left 102 feet of left main tire skid marks, (77 feet for right tire) prior to running into the grass, colliding with a concrete pad, shearing off the nose wheel, and sustaining a nose over. He was not injured. Postaccident examination by a mechanic revealed no evidence of preaccident brake abnormalities. The pilot stated to an FAA Inspector that he encountered no mechanical malfunctions during a post accident interview. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2002_MIA02LA097.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (loss of control, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NTSB Aircraft Accident Reports 2002 · Accident report
Loss of Control and Impact with Pacific Ocean — Alaska 261
Alaska Airlines Flight 261 (MD-83) Pacific Ocean, January 31, 2000 — 88 fatalities. Definitive investigation of the Alaska 261 pitch-runaway-and-loss-of-control crash.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
Browse the full corpus — academia portal ↗