Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

December 13, 2002 · Piper PA28-181 · N793MA

Greensburg, IN

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
December 13, 2002
Injury Outcomes
1 injury (1 minor injury)
Location
Greensburg, IN
Aircraft
Piper PA28-181
Tail Number
N793MA
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
CHI03LA038

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.

NTSB Probable Cause

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.

Full 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.

Flight

Event TypeAccident
Event Time18:45 EST
Nearest AirportGreensburg-Decatur County (0nm)
Runway36
Runway Length3433 ft
Runway Width40 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA28-181
Tail NumberN793MA
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-36O Series · Reciprocating · 180
Seats4

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 49 · Third Class · Minor

Conditions

ConditionsIMC
LightDark Night
Wind360° @ 10 kt
Visibility1.5 sm
CeilingOvercast 500 ft
Temperature / Dew Point32 C / 0 C
Altimeter29.64 inHg
Observation Time23:50
Weather SourceWFAC

Appendix: Source Data