# NTSB CHI08CA032: Piper PA-28-151, N5733W, Alliance, OH, November 1, 2007 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: November 1, 2007, 17:10 local (21:10 UTC) - Place: Alliance, OH - Coordinates: 40.9708333333333, -81.0997222222222 - Nearby events: https://openairdocs.org/map.md?lat=40.9708&lon=-81.0997&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report January 31, 2008 - Report: Approved by Office Director - Parties: Federal Aviation Administration - Cleveland FSDO - NTSB case key (mKey): 67208 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI08CA032 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/67208/pdf - Page: https://openairdocs.org/ntsb/CHI08CA032 ## Probable cause The pilot's inadvertent activation of the parking brake which resulted in the toe brakes becoming ineffective. Contributing to the accident was the airport perimeter fence, the ditch, and the vehicle. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Airframe/component/system failure/malfunction, landing - roll - parking brakes - inadvertent activation, pilot in command (cause) - landing gear,parking brake - engaged (cause) - landing gear,normal brake system - inoperative (cause) - Overrun, landing - roll - On ground/water collision with object, landing - roll - object - fence (contributing factor) - On ground/water encounter with terrain/water, landing - roll - terrain condition - ditch (contributing factor) - On ground/water collision with object, landing - roll - object - vehicle (contributing factor) ## Analysis The private pilot reported that the airplane's approach and touchdown on runway 27 (2,088 feet by 130 feet, turf) were uneventful. The airplane did not decelerate as he depressed the toe brake pedals, although he felt pressure through the pedals. He repositioned his feet and attempted to apply brake pressure again without any effect on braking performance. The pilot realized that the airplane was going to run off the end of the runway and decided to shutdown the engine and turnoff the master electrical switch. He was "standing on the brakes as hard as possible" when the airplane impacted an airport perimeter fence, traveled through a ditch, and onto a nearby road. The airplane was subsequently struck by a vehicle traveling on the road. The airplane received substantial damage to both wings and the engine firewall. Examination of the turf runway after the accident failed to reveal any skid markings that could be associated with the airplane's ground track. Local law enforcement surveyed the accident site and determined that the airplane touched down with 1,072 feet of runway remaining. According to the airplane's operating handbook, at maximum gross weight the airplane required about 600 feet to stop on a paved, level, and dry runway. The operating handbook did not provide landing performance data for a turf runway. Local weather observations indicated that the surface wind was from the west-northwest at 9 knots. The airplane was equipped with a hand brake and dual toe brakes. The hand brake can also be used as a parking brake in conjunction with a locking ratchet system. Once the hand brake lever is engaged, the use of toe brakes becomes ineffective. With the hand brake fully disengaged, the left brake system functioned properly when its corresponding toe brakes (pilot and co-pilot positions) were depressed during a postaccident examination. The right brake assembly had impact damage that prevented a functional test. The pilot stated that he had used the parking brake earlier in the day, but he had alternatively used the toe brakes during the engine run-up before departing on the accident flight. He concluded that the parking brake must have "partially engaged" sometime during the flight. ## Factual narrative The private pilot reported that the airplane's approach and touchdown on runway 27 (2,088 feet by 130 feet, turf) were uneventful. The airplane did not decelerate as he depressed the toe brake pedals, although he felt pressure through the pedals. He repositioned his feet and attempted to apply brake pressure again without any effect on braking performance. The pilot realized that the airplane was going to run off the end of the runway and decided to shutdown the engine and turnoff the master electrical switch. He was "standing on the brakes as hard as possible" when the airplane impacted an airport perimeter fence, traveled through a ditch, and onto a nearby road. The airplane was subsequently struck by a vehicle traveling on the road. The airplane received substantial damage to both wings and the engine firewall. Examination of the turf runway after the accident failed to reveal any skid markings that could be associated with the airplane's ground track. Local law enforcement surveyed the accident site and determined that the airplane touched down with 1,072 feet of runway remaining. According to the airplane's operating handbook, at maximum gross weight the airplane required about 600 feet to stop on a paved, level, and dry runway. The operating handbook did not provide landing performance data for a turf runway. Local weather observations indicated that the surface wind was from the west-northwest at 9 knots. The airplane was equipped with a hand brake and dual toe brakes. The hand brake can also be used as a parking brake in conjunction with a locking ratchet system. Once the hand brake lever is engaged, the use of toe brakes becomes ineffective. With the hand brake fully disengaged, the left brake system functioned properly when its corresponding toe brakes (pilot and co-pilot positions) were depressed during a postaccident examination. The right brake assembly had impact damage that prevented a functional test. The pilot stated that he had used the parking brake earlier in the day, but he had alternatively used the toe brakes during the engine run-up before departing on the accident flight. He concluded that the parking brake must have "partially engaged" sometime during the flight. ## Aircraft - Registration: [N5733W](https://openairdocs.org/deregistered/N5733W-2015-05-20), registration cancelled 2015-05-20, S/N 28-7415081, built 1973 (OpenAirDocs) - Reported make and model: Piper PA-28-151 - Registry model: [Piper PA-28-151](https://openairdocs.org/model/piper-pa-28-151) (registry code 7102805) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-7415081 - Airframe hours: 2621 - Engines: Lycoming O-320 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: 512 Flyers, LLC. - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 1, 2007 - Departed: 8W2, New Market, VA - Destination: 2D1, Alliance, OH - Flight plan: VFR - Airport: 2D1, Barber Airport, runway 27, 2,088 × 130 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 44; injuries: none; private; airplane ratings: multi-engine land, single-engine land; medical: class 3, without waivers/limitations; last flight review March 1, 2006; seat: left; flight hours: 473 total, 35 in this make and model, 437 as pilot in command, 13 in the last 90 days, 7 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 290° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 52 °F, dew point 27 °F - Altimeter: 30.20 inHg - Observed at: CAK, 16 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 20071101827579A](https://openairdocs.org/incident/20071101827579A), Nov 1, 2007: Piper PA28151, Alliance, OH, Substantial damage. (-23) Aircraft failed to stop after brakes were applied, resulting in collision with ditch, road, and passing vehicle at the end of the runway approximately… 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.