CEN12LA197 · Piper PA-22-150
Piper PA-22-150 · Accident: controlled flight into terrain/object (CFIT) on approach
From James Clements Municipal Airport (3CM) to Gross Airport (52I)
Event
- NTSB case
- CEN12LA197
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-22-150
- Aircraft type
- Piper PA-22
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N2389P
- Operator
- Gerald Walter Pergande
- Onboard fatalities
- Unknown
- Route
- From James Clements Municipal Airport (3CM), Bay City, MITo Gross Airport (52I), Pinconning, MI
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern final
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Controlled flight into terrain/object (CFIT)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s); Wire
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12LA197
- Event ID
- 20120322X83547
- Case number
- CEN12LA197
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: dc4f780a7cf255b1299ce554a41e4cfe343914e474db2cacc019b4084fa9ada4; retrieved 2026-09-15T17:32:03.581Z.