# NTSB CHI01LA096: Piper PA-30, N8196Y, Appleton, WI, February 27, 2001 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: February 27, 2001, 17:01 local (23:01 UTC) - Place: Appleton, WI - Coordinates: 44.279457, -88.380432 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=44.2795&lon=-88.3804&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report November 23, 2001 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 53250 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI01LA096 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/53250/pdf - Page: https://openairdocs.org/ntsb/CHI01LA096 ## Probable cause The misjudged glidepath and the intentional engine shutdown by the pilot. Factors were the false indication of the landing gear down light and the approach light. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Undershoot, landing - landing gear,gear indicating system - false indication (contributing factor) - proper glidepath - misjudged, pilot in command (cause) - engine shutdown - intentional, pilot in command (cause) - object - approach light/navaid (contributing factor) - In flight collision with object, landing - In flight collision with terrain/water, landing ## Analysis The aircraft undershot the runway during a precautionary landing, struck a runway approach light and came to rest about 10 feet from the end of the runway. The flight was being conducted to practice instrument approaches. During an approach, the landing gear down indicator light did not illuminate on gear extension. The pilot attempted to troubleshoot the problem and ultimately decided to land the aircraft. The pilot decided to shut down the engines on final approach in an attempt to minimize engine and propeller damage in the event of a landing gear collapse. The pilot said, "I cut the power too soon." ## Factual narrative On February 27, 2001, at 1701 central standard time, a Piper PA-30, N8196Y, piloted by a private pilot, was substantially damaged during a precautionary landing, to runway 29 (6,501 feet by 150 feet, concrete), at the Outagamie County Regional Airport, Appleton, Wisconsin. The aircraft undershot the runway striking a runway approach light and came to rest about 10 feet from the approach end of the runway. The flight was conducted under 14 CFR Part 91 and was not on a flight plan. Visual meteorological conditions prevailed. The pilot and pilot rated passenger were not injured. The local flight originated at 1630. In a written statement, the pilot stated that the flight was conducted to practice instrument approaches. He said that on one of the approaches, the green landing gear down indicator light did not illuminate. He said that he attempted to troubleshoot the problem but could not get a gear down indication. He said that he performed the emergency gear extension procedures and opened the gear actuator panel, located in the cockpit floor, and the actuator mechanism appeared to be "properly positioned." He said that he decided to land and, when on short final, he "cut the engines in order to minimize propeller/engine damage in the event of gear collapse." He said that. "the aircraft mushed in shortly after that, contacting the ground in a level attitude." He stated that , "factors leading to this outcome were: The approach was flown down the glideslope at 3 degree slope, which left insufficient altitude for a dead stick landing; there were moderate headwinds; the aircraft had full fuel and a 200# safety pilot on board, whereas I usually fly alone; half flaps were used to reduce stalling speed and consequent damage in the event of a gear collapse, thus increasing drag over what it is with my normal routine to land without flaps; in retrospect, I cut the power too soon." ## Aircraft - Registration: [N8196Y](https://openairdocs.org/deregistered/N8196Y-2006-07-21), registration cancelled 2006-07-21, S/N 30-1314, built 1966 (OpenAirDocs) - Reported make and model: Piper PA-30 - Registry model: [Piper PA-30](https://openairdocs.org/model/piper-pa-30) (registry code 7103002) (OpenAirDocs) - Registry engine: [Lycoming IO-320 series](https://openairdocs.org/engine/lycoming-io-320-series) (registry code 41509, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 30-1314 - Airframe hours: 4490 - Engines: Lycoming IO-320-B1A 160 horsepower reciprocating; Lycoming IO-320-B1A 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Thomas H. Burrows - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 19, 2000, 30 hours before - Departed: ATW, Appleton, WI - Airport: ATW, Outagamie County, runway 29, 6,501 × 150 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 65; injuries: none; private; airplane ratings: single-engine land, single-engine sea, multi-engine land; instrument ratings: airplane; medical: class 3, valid medical--w/ waivers/lim; last flight review October 4, 1999; seat: left; flight hours: 1,030 total, 310 in this make and model, 830 as pilot in command, 4 in the last 90 days, 3 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 270° at 9 knots - Visibility: 15 statute miles - Lowest ceiling: none - Temperature: 16 °F, dew point 1 °F - Altimeter: 30.35 inHg - Observed at: ATW ## 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 20010227003809A](https://openairdocs.org/incident/20010227003809A), Feb 27, 2001: Cvac 30, No damage. (-19) On February 27, 2001, at 1702 CST, a Piper PA-30, N8196Y, piloted by a private pilot, was substantially damaged during a precautionary landing to runway… 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.