# NTSB CHI97LA169: Piper PA-38-112, N2455F, Minneapolis, MN, June 17, 1997 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 16, 1997, 20:55 local (Jun 17, 1997, 01:55 UTC) - Place: Minneapolis, MN - Coordinates: 44.879131, -93.220703 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=44.8791&lon=-93.2207&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report October 31, 1997 - Report: Approved by Office Director - NTSB case key (mKey): 10596 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI97LA169 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/10596/pdf - Page: https://openairdocs.org/ntsb/CHI97LA169 ## Probable cause the student pilot's improper recovery from a bounced landing and failure to maintain proper runway alignment during a go-around (aborted landing). Factors relating to the accident were: the pilot's improper flare for landing, the reduced light conditions at dusk, and the obstruction (static wire) that was encountered during the go-around. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - flare/touchdown - flare - improper, pilot in command (contributing factor) - recovery from bounced landing - improper, pilot in command (cause) - directional control - not maintained, pilot in command (cause) - go-around - initiated, pilot in command - In flight collision with object, go-around (vfr) - light condition - dusk (contributing factor) - object - wire,static (contributing factor) - object - fence - object - tree(s) ## Analysis The student pilot said that the airplane bounced during landing. 'To avoid continued bounces, I decided to go-around. When I added power, the plane turned, heading off the runway. I tried to regain airspeed with full power.' The student pilot said that he did not have sufficient altitude to clear some buildings on the northwest side of the airport. He flew the airplane between two buildings. 'It [the airplane] appears to have caught a wire drawn between the buildings. The plane pitched down, hitting two fences. The airplane came to rest in a group of trees.' Examination of the wreckage revealed no anomalies. ## Factual narrative On June 16, 1997, at 1938 central daylight time (cdt), a Piper PA-38-112, N2455F, operated by a student pilot, sustained substantial damage when on a go-around from a bounced landing, the airplane struck a wire. The airplane subsequently impacted into a field. Visual meteorological conditions prevailed at the time of the accident. The personal flight was being conducted under 14 CFR Part 91. A flight plan was not on file. The student pilot reported no injuries. The local flight originated at Minneapolis, Minnesota, at 1930 cdt. In his written statement, the student pilot said that the airplane bounced during landing. "To avoid continued bounces, I decided to go-around. When I added power, the plane turned, heading off the runway. I tried to regain airspeed with full power." The student pilot said that he did not have sufficient altitude to clear some buildings on the northwest side of the airport. He flew the airplane between two buildings. "It [the airplane] appears to have caught a wire drawn between the buildings. The plane pitched down, hitting two fences. The airplane came to rest in a group of trees." The Federal Aviation Administration (FAA) inspector who examined the wreckage at the site found the airplane resting in a field on the west side of an airport perimeter road. The inspector observed several propeller strikes in the road crossing from east to west. Damage was observed to a 3/8-inch rusted static wire located 150 feet east of the accident site. Both of the airplane's wings had broken off at the wing roots. The aft fuselage and empennage were twisted to the left. The airplane's nose gear was bent aft and upward. The airplane's firewall was bent aft. The propeller fittings were sheared at the flange. Both propeller blades were pealed rearward, and showed torsional bending and chordwise scratching. Flight control continuity was confirmed. Examination of the engine, engine controls and other airplane systems revealed no anomalies. ## Aircraft - Registration: [N2455F](https://openairdocs.org/deregistered/N2455F-1999-01-30), registration cancelled 1999-01-30, S/N 38-79A0456, built 1979 (OpenAirDocs) - Reported make and model: Piper PA-38-112 - Registry model: [Piper PA-38-112](https://openairdocs.org/model/piper-pa-38-112) (registry code 7103812) (OpenAirDocs) - Registry engine: [Lycoming 0-235 series](https://openairdocs.org/engine/lycoming-0-235-series) (registry code 41505, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 38-79A0456 - Airframe hours: 5378 - Engines: Lycoming O-235-L2C 112 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Thunderbird Aircraft Co. - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: Annual, April 25, 1997, 85 hours before - Departed: MIC - Airport: MIC, Crystal, runway 31L, 3,266 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 46; student; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 19 total, 19 in this make and model, 19 as pilot in command, 19 in the last 90 days, 9 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Dusk - Wind: variable at 3 knots - Visibility: 20 statute miles - Lowest ceiling: none - Temperature: 75 °F - Altimeter: 29.00 inHg - Observed at: MIC ## 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 19970616014249A](https://openairdocs.org/incident/19970616014249A), Jun 16, 1997: Piper PA38112, Minneapolis, MN, Destroyed. Second solo bounced landing. Tried go around full flaps. Exited runway through fence in residential yard. (-23) during student pilot's second solo. Student… 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.