# NTSB CHI08CA206: Piper PA-28-235, N8942W, Lowell, MI, July 23, 2008 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: July 23, 2008, 18:10 local (22:10 UTC) - Place: Lowell, MI - Coordinates: 42.953609, -85.34333 - Nearby events: https://openairdocs.org/map.md?lat=42.9536&lon=-85.3433&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff-rejected takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300) - Highest injury: Minor injuries - Injuries: 1 minor, 1 uninjured - Status: Completed, report August 28, 2008 - Report: Approved by Office Director - NTSB case key (mKey): 68643 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI08CA206 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/68643/pdf - Page: https://openairdocs.org/ntsb/CHI08CA206 ## Probable cause The inadequate preflight planning/preparation and the short field takeoff procedure not followed by the pilot. An additional cause was the delayed aborted takeoff by the pilot. A contributing factor was the trees. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Planning/preparation: flight planning/navigation](https://openairdocs.org/ntsb-findings/02061025): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-28-235, 2 cases](https://openairdocs.org/ntsb-findings/02061025/cases.md?model=7102810), [All aircraft, 179 cases](https://openairdocs.org/ntsb-findings/02061025/cases.md) - [Use of equip/info: use of policy/procedure](https://openairdocs.org/ntsb-findings/02063032): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-28-235, 1 case](https://openairdocs.org/ntsb-findings/02063032/cases.md?model=7102810), [All aircraft, 191 cases](https://openairdocs.org/ntsb-findings/02063032/cases.md) - [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-28-235, 2 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=7102810), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome (probable cause); cases with it: [Piper PA-28-235, 2 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=7102810), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff-rejected takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Piper PA-28-235, 14 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102810), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Takeoff-rejected takeoff: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-28-235, 35 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102810), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot had performed 56 flights in the accident airplane from the airport in "similar" atmospheric conditions at airplane weights that equaled or exceeded the accident flight takeoff. The pilot stated that the "numerous" trees surrounding the airport and the departure end of each runway are "extremely dangerous" and provide "few, if any, options" for an uneventful aborted takeoff. During the accident takeoff on runway 30 (2,394 feet by 48 feet, dry asphalt), the airplane performed within the pilot’s expectations, but after rotation, the airplane was not climbing "normally" nor was it accelerating to best angle climb speed at the rate he previously experienced. The pilot then aborted the takeoff while the airplane was within a "few" feet above the runway because he did not want to risk hitting the trees at the departure end of the runway. The pilot was uninjured and the passenger received minor injuries. The airplane overran the runway with the application of "full" braking and impacted the trees. A post crash fire then ensued consuming the airplane. The pilot stated that he can only "speculate" that something changed after takeoff rotation that affected airplane performance. The airplane flight manual states that the takeoff distance over a 50-foot obstacle is about halfway down the runway and the calculated landing ground roll is within the remaining runway distance. The pilot stated that he used 10 degrees of flaps for the takeoff rather than 25 degrees of flaps cited in the airplane flight manual for a short field takeoff. There is no takeoff performance data based upon a 10-degree flap setting cited in the airplane flight manual. ## Factual narrative The pilot had performed 56 flights in the accident airplane from the airport in "similar" atmospheric conditions at airplane weights that equaled or exceeded the accident flight takeoff. The pilot stated that the "numerous" trees surrounding the airport and the departure end of each runway are "extremely dangerous" and provide "few, if any, options" for an uneventful aborted takeoff. During the accident takeoff on runway 30 (2,394 feet by 48 feet, dry asphalt), the airplane performed within the pilot’s expectations, but after rotation, the airplane was not climbing "normally" nor was it accelerating to best angle climb speed at the rate he previously experienced. The pilot then aborted the takeoff while the airplane was within a "few" feet above the runway because he did not want to risk hitting the trees at the departure end of the runway. The pilot was uninjured and the passenger received minor injuries. The airplane overran the runway with the application of "full" braking and impacted the trees. A post crash fire then ensued consuming the airplane. The pilot stated that he can only "speculate" that something changed after takeoff rotation that affected airplane performance. The airplane flight manual states that the takeoff distance over a 50-foot obstacle is about halfway down the runway and the calculated landing ground roll is within the remaining runway distance. The pilot stated that he used 10 degrees of flaps for the takeoff rather than 25 degrees of flaps cited in the airplane flight manual for a short field takeoff. There is no takeoff performance data based upon a 10-degree flap setting cited in the airplane flight manual. ## Aircraft - Registration: [N8942W](https://openairdocs.org/deregistered/N8942W-2009-05-28), registration cancelled 2009-05-28, S/N 28-10511, built 1964 (OpenAirDocs) - Reported make and model: Piper PA-28-235 - Registry model: [Piper PA-28-235](https://openairdocs.org/model/piper-pa-28-235) (registry code 7102810) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-10511 - Engines: Lycoming O-540-B4B5 reciprocating - Damage: Substantial damage - Fire: On-Ground - Flight: Personal, Part 91 - Operator: Pilot - Registered owner: Harp Air, LLC - Airworthiness certificate: Standard, Normal - Departed: 24C, Lowell, MI - Destination: CLI, Clintonville, WI - Flight plan: IFR ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 33; commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2; flight hours: 847 total, 549 in this make and model, 107 in the last 90 days, 33 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 360° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 82 °F, dew point 48 °F - Altimeter: 30.04 inHg - Observed at: GRR ## 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 20080723844229A](https://openairdocs.org/incident/20080723844229A), Jul 23, 2008: Piper PA28235, Lowell, MI, Destroyed. (-23) Pilot stated that on run up engine appeared normal, but after rotation engines did not appear to be producing proper rate of climb so pilot aborted… 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.