CEN22FA080 · Piper PA-32R-300
Piper PA-32R-300 · Accident: loss of control in flight on approach
From Indianapolis Metropolitan Airport (UMP) to Monroe County Airport (BMG)
Event
- NTSB case
- CEN22FA080
- 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
- 1 · 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
- Instrument Meteorological Cond
Piper PA-32R-300
- Aircraft type
- Piper PA-32
- 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
- N5677V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Indianapolis Metropolitan Airport (UMP), Indianapolis, INTo Monroe County Airport (BMG), Bloomington, IN
- Aircraft age
- About 44 years (built 1977)
- 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 · IFR final approach
- 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
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After departure, the flight proceeded on course and was issued radar vectors for an instrument landing system (ILS) approach at the intended destination airport. The flight tracked inbound along the ILS localizer; however, after it passed the final approach fix the airplane’s flight path appeared to become unstable. The airplane subsequently entered a right turn about 2.25 miles from the runway and impacted a wooded hillside absent of ground lighting about 2 miles south of the airport. The impact path was oriented nearly perpendicular to the runway extended centerline. Postaccident airframe and engine examinations did not reveal any anomalies consistent with a preimpact malfunction or failure. Airplane airspeed varied from about 90 knots to 155 knots as the flight neared and then intercepted the ILS approach course. Airplane vertical speed during this timeframe ranged from a 1,500 feet-per-minute (fpm) climb to a 1,000-fpm descent. The airplane’s airspeed was about 128 knots as it crossed the final approach fix and during the final 60 seconds of the flight was about 118 knots. The airplane remained in a descent that exceeded 1,000 fpm over the final 30 seconds of the flight. A review of available weather data indicated the pilot was likely in instrument meteorological conditions and precipitation and likely encountered turbulence with moderate or greater low-level wind shear during the approach. The Pilot’s Operating Handbook recommended an indicated airspeed of 75 knots on final approach. When established on a 3° glideslope with a 90-knot groundspeed, an airplane will descend at 450 fpm. The FAA defined a stabilized approach as one that maintains a constant angle glidepath toward a predetermined point on the landing runway. It is likely that an inadvertent encounter with turbulence and low-level wind shear resulted in an unstable approach and subsequent loss of control. The presence of instrument meteorological conditions and dark night lighting conditions when the airplane did emerge from the clouds further hindered the pilot’s efforts to remain on the approach or to execute a missed approach.
Probable cause
The pilot’s failure to follow the instrument landing system (ILS) course guidance, which resulted in the pilot’s loss of airplane control during the instrument approach. Contributing to the accident was the presence of turbulence and low-level wind shear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22FA080
- Event ID
- 20211218104420
- Case number
- CEN22FA080
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2021-12-18.
- API snapshot SHA-256: df5d537f6834c15e34720512bfe1bb675ffd9f7fbea8e70c16b01f6f518d13d6; retrieved 2026-09-15T07:39:23.459Z.