# NTSB CHI05LA086: Piper PA-28-151, N56715, Waunakee, WI, April 3, 2005 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: April 2, 2005, 22:22 local (Apr 3, 2005, 04:22 UTC) - Place: Waunakee, WI - Coordinates: 43.178611, -89.451385 - Nearby events: https://openairdocs.org/map.md?lat=43.1786&lon=-89.4514&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report September 13, 2005 - Report: Approved by Office Director - Parties: Milwaukee, WI FAA FSDO - NTSB case key (mKey): 61250 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI05LA086 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/61250/pdf - Page: https://openairdocs.org/ntsb/CHI05LA086 ## Probable cause The pilot's inadequate preflight planning and the delay in aborting the landing which resulted in the subsequent insufficient airspeed. Factors associated with the accident were the night light conditions, the fence, and the pole which the airplane contacted. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with object, landing - aborted - preflight planning/preparation - inadequate, pilot in command (cause) - light condition - dark night (contributing factor) - aborted landing - delayed, pilot in command (cause) - airspeed - inadequate, pilot in command (cause) - climb - not possible, pilot in command - object - fence (contributing factor) - object - pole (contributing factor) ## Analysis The airplane collided with a fence and a pole during an aborted landing. The pilot reported he remotely activated the runway lights during the landing. He stated he did not know that the runway lights did not illuminate the runway and that they did not start at the end of the runway. He stated that during his previous night landings at the airport he was able to see the outline of the runway and lights would not have been needed. He stated that this time he could not see the runway until he was on it and that all he could see is what the landing light was illuminating. The pilot stated he touched down further down the runway than he intended, so he decided to initiate a go-around. He stated he added 20 degrees of flaps, applied full throttle, and rotated at 65 miles per hour. He stated the airplane traveled off the end of the runway prior to lifting off. The pilot stated that after lifting off, the stall horn sounded so he descended back into ground effect to accelerate. He stated the stall horn sounded again when he attempted to climb, so he decided to climb more slowly. The pilot reported he was nearing a house at the end of the runway, so he turned to the left and pushed the yoke forward in an attempt to "crash into the ground and skid between two houses." He stated the airplane contacted a fence and a permanent basketball hoop pole prior to the airplane coming to a stop. The Airport/Facility Directory states the airport has nonstandard low intensity runway lights located 155 feet from the west end of runway 09/27. The directory also indicates that 1,910 feet of the runway is lit and that the lights are located approximately 60 feet from the edge of the pavement. ## Factual narrative On April 2, 2005, at 2222 central standard time, a Piper PA-28-151, N56715, collided with a fence and a pole during an aborted landing on runway 09 (2,223 feet by 30 feet, dry asphalt) at the Waunakee Airport, Waunakee, Wisconsin. The private pilot and passenger were not injured. The airplane was substantially damaged. The 14 Code of Federal Regulations Part 91 personal flight was operating in visual meteorological conditions without a flight plan. The flight originated from Green Bay, Wisconsin, at 2120. The pilot reported the weather was clear, calm, and dark since there was no visible moon. He stated he remotely activated the runway lights and was landing from west to east. The pilot stated he did not know that the runway lights do not illuminate the runway and that they did not start at the end of the runway. He stated, "Every time I had landed here at night, you could see the outline of the runway and lights would not have been needed." He stated that this time he could not see the runway until he was on it and that all he could see was what the landing light was illuminating. The pilot also reported the end of the runway on which he was landing sloped down. The pilot stated that after touching down, he realized he was further down the runway than he intended, so he decided to initiate a go-around. He stated he added 20 degrees of flaps, applied full throttle, and rotated at 65 miles per hour. He stated the airplane traveled off the end of the runway prior to it lifting off. The pilot stated that after lifting off, the stall horn sounded so he descended back into ground effect to accelerate. He stated, "When I climbed again, the horn went off again and so I climbed more slowly." The pilot reported he was nearing a house at the end of the runway, so he turned to the left and pushed the yoke forward in an attempt to "crash into the ground and skid between two houses." He stated the airplane contacted a fence and a permanent basketball hoop pole prior to the airplane coming to a stop. The Airport/Facility Directory states the airport has nonstandard low intensity runway lights located 155 feet from the west end of runway 09/27. The directory also indicates that 1,910 feet of the runway is lit and that the lights are located approximately 60 feet from the edge of the pavement. ## Aircraft - Registration: [N56715](https://openairdocs.org/deregistered/N56715-2013-09-16), registration cancelled 2013-09-16, S/N 28-7415006, 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-7415006 - Engines: Lycoming O-320-E3D 160 horsepower reciprocating - Damage: Destroyed - Flight: Personal, Part 91 - Registered owner: John B. VanHollen - Airworthiness certificate: Standard, Normal - Last inspection: Annual, December 15, 2004 - Departed: GRB, Green Bay, WI - Destination: 6P3, Waunakee, WI - Airport: 6P3, Waunakee, runway 9, 2,223 × 30 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 39; injuries: none; private; airplane ratings: single-engine land; medical: class 3, valid medical--no waivers/lim.; last flight review October 2, 2003; seat: left; flight hours: 163 total, 150 in this make and model, 107 as pilot in command, 15 in the last 90 days, 11 in the last 30 days, 5 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night - Wind: 0° at 0 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 37 °F, dew point 30 °F - Altimeter: 29.98 inHg - Observed at: MSN, 7 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 20050402006919A](https://openairdocs.org/incident/20050402006919A), Apr 2, 2005: Piper PA28151, Waunakee, WI, Substantial damage. (-23) On April 2, 2005 at 1024 CST a Piper, PA-28-151, N56715, landed 500 feet off the end of the 9/27 runway, Waunakee, Wisconsin. The private pilot and… 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.