# NTSB CEN12LA197: Piper PA-22-150, N2389P, Pinconning, MI, March 21, 2012 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: March 21, 2012, 19:16 local (23:16 UTC) - Place: Pinconning, MI - Coordinates: 43.846942, -84.01139 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=43.8469&lon=-84.0114&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed, report October 9, 2012 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration, Grand Rapids FSDO - NTSB case key (mKey): 83189 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN12LA197 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/83189/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=83189 - Page: https://openairdocs.org/ntsb/CEN12LA197 ## Probable cause The pilot's failure to properly align his airplane with the runway during final approach. Contributing to the accident was the sunglare that obscured the pilot's view of the runway. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Piper PA-22-150, 5 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7102210), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Light condition: glare](https://openairdocs.org/ntsb-findings/03036030): Environmental issues › Conditions/weather/phenomena · Effect on operation (probable cause); cases with it: [Piper PA-22-150, 1 case](https://openairdocs.org/ntsb-findings/03036030/cases.md?model=7102210), [All aircraft, 109 cases](https://openairdocs.org/ntsb-findings/03036030/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Awareness of condition; cases with it: [Piper PA-22-150, 4 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=7102210), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) - [Object/animal/substance: wire](https://openairdocs.org/ntsb-findings/03022032): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper PA-22-150, 1 case](https://openairdocs.org/ntsb-findings/03022032/cases.md?model=7102210), [All aircraft, 588 cases](https://openairdocs.org/ntsb-findings/03022032/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [Piper PA-22-150, 4 cases](https://openairdocs.org/ntsb-events/120/sequence.md?model=7102210), [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md) ## Analysis The pilot reported that after turning onto final approach, he encountered an "intense glare" from the setting sun in the west, which obscured his view of the runway and the threshold markers. He stated that after he had verified that the airplane was properly aligned with the runway, there was insufficient runway remaining to make a safe landing. He performed a go-around and reentered the traffic pattern. During the go-around he put on his sunglasses and installed a windshield sun-screen in an attempt to reduce the sun glare. He reported that although the glare was reduced during his second landing approach, he still could not identify the runway or the threshold markers. He aligned the airplane with what he thought was the runway and continued to descend until he unexpectedly saw trees ahead of the airplane's flight path. He immediately applied full engine power, but the airplane impacted the trees and then the ground. The pilot noted that there were no preimpact mechanical malfunctions or failures that would have precluded normal operation of the airplane. Global positioning system position data, obtained from a handheld device found in the main wreckage, confirmed that the pilot had made two approaches to runway 27. The first approach was roughly aligned with the northern edge of the runway. The second approach was aligned about 300 feet north of the runway. The pilot's account of the accident, the recorded flight track data, and the physical evidence found at the accident site is consistent with the airplane being misaligned with the runway during final approach. Astronomical data confirmed that the sun was setting at the time of the accident and would have contributed to the pilot's inability to correctly identify the runway. ## Factual narrative On March 21, 2012, at 1916 eastern daylight time, a Piper PA-22-150 airplane, N2389P, was substantially damaged while landing at Gross Airport (52I), Pinconning, Michigan. The pilot sustained serious injuries. The airplane was registered to and operated by a private individual, under the provisions of 14 Code of Federal Regulations Part 91 without a flight plan. Day visual meteorological conditions prevailed for the personal flight. The flight departed James Clements Municipal Airport (3CM), Bay City, Michigan, about 1858 with 52I as the intended destination. The pilot reported that he entered the traffic pattern for runway 27 (2,565 feet by 100 feet, grass/turf) on a left downwind. After turning onto final approach, he encountered an "intense glare" from the setting sun in the west, which obscured his view of the runway and the threshold markers. He stated that after he had verified that the airplane was properly aligned with the runway there was insufficient runway remaining to make a safe landing. He performed a go-around and reentered the traffic pattern. During the go-around he put-on his sunglasses and installed a windshield sun-screen in an attempt to reduce the glare of the sun. The pilot reported that although the glare was reduced during his second landing approach, he still could not identify the runway or the threshold markers. He aligned the airplane with what he thought was the runway and continued to descend until he unexpectedly saw trees ahead of the airplane's flight path. He immediately applied full engine power, but the airplane impacted the trees and then the ground. The pilot noted that there were no preimpact mechanical malfunctions or failures that would have precluded normal operation of the airplane. The airport manager reported that his attention was drawn to the airplane when he heard the engine suddenly power up during final approach. Although he did not recall seeing the airplane impact trees, he did witness the airplane crash in the residential property located immediately north of the airport. He noted that after the accident the pilot told him that the glare of the setting sun obscured his vision during his initial landing approach, requiring a go-around and reentering the traffic pattern. An on-site examination was completed by inspectors with the Federal Aviation Administration. Their examination revealed that the airplane had collided with trees before encountering a north/south power line that ran parallel to a nearby road. Several broken tree branches were found on the ground between the tree line and the main wreckage. Tree bark material was found embedded in the outboard portion of the left wing leading edge. A portion of the power/utility line was found wrapped around the upper portion vertical stabilizer and rudder. The observed wreckage debris path was consistent with the airplane traveling westbound when it collided with the obstacles. A global positioning system (GPS) handheld device was found at theaccident site. The plotted GPS data was consistent with the pilot and airport manager descriptions of the accident flight path. The data confirmed that the pilot had made two approaches to runway 27. The first approach was roughly aligned with the northern edge of the runway. The second approach was aligned about 300 feet north of the runway. The closest weather observing station was at Jack Barstow Airport (KIKW), located about 18 miles southwest of the accident site. At 1914, the KIKW automated surface observing system reported the following weather conditions: wind 220 degrees at 6 knots; visibility 10 miles; scattered clouds at 8,000 feet above ground level; temperature 29 degrees Celsius; dew point 10 degrees Celsius; altimeter setting 30.06 inches of mercury. Astronomical data obtained from the United States Naval Observatory indicated that the local sunset was at 1950, about 34 minutes after the accident. The end of civil twilight was listed at 2019. ## Aircraft - Registration: [N2389P](https://openairdocs.org/deregistered/N2389P-2014-09-03), registration cancelled 2014-09-03, S/N 22-2780, built 1955 (OpenAirDocs) - Reported make and model: Piper PA-22-150 - Registry model: [Piper PA-22-150](https://openairdocs.org/model/piper-pa-22-150) (registry code 7102210) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 22-2780 - Airframe hours: 3271 - Engines: Lycoming O-320-A2A 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Gerald Walter Pergande - Registered owner: Gerald Walter Pergande - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 11, 2011, 25 hours before - Departed: 3CM, Bay City, MI - Destination: 52I, Pinconning, MI - Airport: 52I, Gross Airport, runway 27, 2,565 × 100 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 68; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review September 11, 2011; seat: left; flight hours: 697 total, 22 in this make and model, 8 in the last 90 days, 3 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 220° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 84 °F, dew point 50 °F - Altimeter: 30.05 inHg - Observed at: KIKW, 15 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 20120321003749A](https://openairdocs.org/incident/20120321003749A), Mar 21, 2012: Piper PA-22-150, Pinconning, MI, Destroyed. N March 21, 2012, at 1918 eastern daylight time, a Piper PA-22-150 airplane, N2389P, wassubstantially damaged while landing at Gross Airport (52I), Pinconning,… ## Docket (13 files) The files NTSB released with the investigation on August 1, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=83189. 3.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371655&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - FAA Summary of Airport Manager Interview (item 2, .PDF, 92 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371656&FileExtension=.PDF&FileName=FAA%20Summary%20of%20Airport%20Manager%20Interview-Redacted.PDF - Memorandum of Conversation with FAA Inspector Marc Webber (item 3, .PDF, 59 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371657&FileExtension=.PDF&FileName=Memorandum%20of%20Conversation%20with%20FAA%20Inspector%20Marc%20Webber-Master.PDF - Michigan State Police Incident Report (item 4, .PDF, 406 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371658&FileExtension=.PDF&FileName=Michigan%20State%20Police%20Incident%20Report-Redacted.PDF - Plots of Global Positioning System (GPS) Data (item 5, .PDF, 384 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371659&FileExtension=.PDF&FileName=Plots%20of%20Global%20Positioning%20System%20(GPS)%20Data-Master.PDF - Global Positioning System (GPS) Data Source Data (item 6, .PDF, 41 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371660&FileExtension=.PDF&FileName=Global%20Positioning%20System%20(GPS)%20Data%20Source%20Data-Master.PDF - Weather Reports (item 7, .PDF, 83 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371661&FileExtension=.PDF&FileName=Weather%20Reports-Master.PDF - Astronomical Sun and Moon Data (item 8, .PDF, 37 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371662&FileExtension=.PDF&FileName=Astronomical%20Sun%20and%20Moon%20Data-Master.PDF - Delivery Confirmation of the Return of the Pilot's Handheld Global Positioning System (GPS) Device (item 9, .PDF, 264 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371663&FileExtension=.PDF&FileName=Delivery%20Confirmation%20of%20the%20Return%20of%20the%20Pilot%27s%20Handheld%20Global%20Positioning%20System%20(GPS)%20Device-Redacted.PDF - Photo 01. Main Wreckage Overview (item 10, .PDF, 271 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371664&FileExtension=.PDF&FileName=Photo%2001.%20Main%20Wreckage%20Overview-Master.PDF - Photo 02. Main Wreckage Overview (item 11, .PDF, 250 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371667&FileExtension=.PDF&FileName=Photo%2002.%20Main%20Wreckage%20Overview-Master.PDF - Photo 03. Vertical Stabilizer and Rudder (item 12, .PDF, 275 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371669&FileExtension=.PDF&FileName=Photo%2003.%20Vertical%20Stabilizer%20and%20Rudder-Master.PDF - Photo 04. Accident Flight Path (item 13, .PDF, 203 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371668&FileExtension=.PDF&FileName=Photo%2004.%20Accident%20Flight%20Path-Master.PDF 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.