NTSB CAROL · Event
Event CHI03LA038
Aircraft involved
Probable cause & findings
Failure of the pilot to maintain directional control during the takeoff roll. Contributing factors included inadequate planning/decision by the pilot for attempting to depart from the slush covered runway, the slush covered runway itself, and the falling snow.
Factual narrative
On December 13, 2002, at 1845 eastern standard time, a Piper PA28-181, N793MA, piloted by a private pilot, was substantially damaged when it departed the runway and came to rest in a plowed field adjacent to the airport. The airplane was attempting to takeoff from runway 36 (3,433 feet x 40 feet, asphalt) at the Greensburg-Decatur County Airport (I34), Greensburg, Indiana. Instrument meteorological conditions prevailed at the time of the accident. The business flight was operated under the provisions of 14 CFR Part 91, on an instrument flight rules (IFR) flight plan. The pilot reported minor injuries. The intended destination was the Logansport Municipal Airport (GGP), Logansport, Indiana. The pilot noted in his written statement that when he arrived at the airport for his IFR flight there was snow present on the ground, as well as on the aircraft. He reported that he conducted a preflight inspection and cleared the snow from the aircraft. He stated that after start-up, he back taxied to runway 36, announced his intentions on the common traffic advisory frequency (CTAF), and began the takeoff. He reported, "As I started to lift off, suddenly the plane skid" and started to go toward the east side of the runway. He went on to note that to avoid a collision, " I turned the plane to the west and tried to reduce speed, but the plane was out of control... ." The aircraft impacted two fences and came to rest approximately 130 feet off the west side of the runway in an adjacent field. The airport manager, who witnessed the accident aircraft attempting to takeoff, stated: "It was snowing fairly heavy, with a couple of inches of slush on the runway". He reported that it was almost a "white out" condition, and estimated visibility as approximately 1/4 mile. "As I was watching him go past the intersection, which is about 2/3 down the runway, it appeared he didn't have much airspeed. I could see the aircraft's nose bouncing up and down like he was trying to get it out of ground effect." He noted that there were continuous main gear tracks in the snow from the point where the takeoff run began to the point where the aircraft came to a stop. Documentation supplied by the FAA inspector on-scene, indicated the aircraft accurately tracked the runway centerline for less than one-tenth of a mile. At the point the nose wheel lifted off the ground, the aircraft's path drifted toward, and subsequently off, the left side of the runway. The tracks then turned back toward the runway centerline. However the aircraft's path continued across and departed the right side of the runway. Again, the tracks turned back toward the runway centerline. The aircraft crossed the runway and came to a rest off of the left side of the runway. The departure airport did not have weather reporting capability. Conditions at the Columbus Municipal Airport (BAK), located 18 miles west of I34, at 1850 est, were reported as: overcast at 500 feet agl, 1-1/2 miles visibility in light snow, wind from 360 degrees at 10 knots, and temperature at 0 degrees Celcius. The pilot stated that there were no abnormalities with the controls, and no malfunctions with the aircraft. A post-accident examination also revealed no anomalies. The airplane was substantially damaged when it departed the runway surface while attempting to takeoff. It came to rest in a plowed field adjacent to the airport. In his statement, the pilot reported: "As I started to lift off, suddenly the plane skid" and started to go toward the side of the runway. He went on to note that to avoid a collision, " I turned the plane to the west and tried to reduce speed, but the plane was out of control... ." The airport manager, who witnessed the accident aircraft attempting to takeoff, stated: "It was snowing fairly heavy, with a couple of inches of slush on the runway". He reported that it was almost a "white out" condition, and estimated visibility as approximately 1/4 mile. The pilot stated that there were no abnormalities with the controls, and no malfunctions with the aircraft. A post-accident examination also revealed no anomalies. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2002_CHI03LA038.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.