# NTSB CHI03LA038: Piper PA28-181, N793MA, Greensburg, IN, December 13, 2002 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: December 13, 2002, 18:45 local (23:45 UTC) - Place: Greensburg, IN - Coordinates: 39.326946, -85.522499 - Nearby events: https://openairdocs.org/map.md?lat=39.3269&lon=-85.5225&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report June 25, 2003 - Report: Approved by Office Director - Parties: FAA -- Indianapolis FSDO - NTSB case key (mKey): 56213 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI03LA038 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/56213/pdf - Page: https://openairdocs.org/ntsb/CHI03LA038 ## 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, takeoff - roll/run - directional control - not maintained, pilot in command (cause) - planning/decision - inadequate, pilot in command (contributing factor) - airport facilities,runway/landing area condition - slush covered (contributing factor) - flight into known adverse weather - attempted, pilot in command - weather condition - snow (contributing factor) - weather condition - icing conditions - On ground/water encounter with terrain/water, takeoff - roll/run - terrain condition - open field ## Analysis 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. ## 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. ## Aircraft - Registration: [N793MA](https://openairdocs.org/deregistered/N793MA-2020-02-03), registration cancelled 2020-02-03, S/N 2843193, built 1998 (OpenAirDocs) - Reported make and model: Piper PA28-181 - Registry model: [Piper PA-28-181](https://openairdocs.org/model/piper-pa-28-181) (registry code 7102807) (OpenAirDocs) - Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 2843193 - Airframe hours: 800 - Engines: Lycoming O-36O Series 180 horsepower reciprocating - Damage: Substantial damage - Flight: Business, Part 91 - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: Annual, September 1, 2002, 48 hours before - Departed: I34, Greensburg, IN - Destination: GGP, Logansport, IN - Flight plan: IFR - Airport: I34, Greensburg-Decatur County, runway 36, 3,433 × 40 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 49; injuries: minor; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, valid medical--no waivers/lim.; last flight review November 20, 2001; seat: left; flight hours: 610 total, 566 in this make and model, 610 as pilot in command, 46 in the last 90 days, 27 in the last 30 days ## Weather - Conditions: Instrument (IMC), Night/dark - Wind: 360° at 10 knots - Visibility: 1.5 statute miles - Lowest ceiling: 500 ft overcast - Temperature: 32 °F - Altimeter: 29.64 inHg - Observed at: BAK, 18 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20021213035659A](https://openairdocs.org/incident/20021213035659A), Dec 13, 2002: Piper PA28181, Greensburg, IN, Substantial damage. (-23) The takeoff was attempted during a heavy snow storm with approximately 1.5" of slush on rwy 36. After rotation, the aircraft skidded and directional… ## Other investigations on N793MA (2) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB CEN17FA258](https://openairdocs.org/ntsb/CEN17FA258), Jul 8, 2017: Piper PA 28-181 (N793MA), Waterford, OH, destroyed, 2 fatal. Probable cause: The pilot's loss of airplane control due to spatial disorientation in instrument meteorological conditions. - [NTSB CHI06CA144](https://openairdocs.org/ntsb/CHI06CA144), Apr 9, 2006: Piper PA-28-181 (N793MA), Logansport, IN, substantial damage. Probable cause: The pilot's improper flare and inadequate recovery from a bounced landing. From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.