FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA144 · Piper PA28 236

1 Apr 2024 · Muncie, IN, United States

Piper PA28 236 · Accident: loss of control in flight on approach

From Monroe County Airport (BMG) to Delaware County Johnson Field (MIE)

Report a problem

Event

NTSB case
CEN24LA144
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
0
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 PA28 236

Aircraft type
Piper PA28
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
N8438B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Monroe County Airport (BMG), Bloomington, INTo Delaware County Johnson Field (MIE), Muncie, IN
Aircraft age
About 43 years (built 1981)
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 missed 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

  • Environmental issues › Conditions/weather/phenomena
  • Organizational issues › Support/oversight/monitoring
  • Personnel issues › Action/decision
  • Personnel issues › Experience/knowledge
  • Personnel issues › Psychological
  • 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

The instrument-rated pilot was repositioning the airplane to a maintenance facility for a pitot-static test required to complete instrument flight rules (IFR) certification. The pilot initially filed a visual flight rules (VFR) flight plan but later filed an IFR flight plan instead. The airplane departed and proceeded toward the destination airport. The destination airport local control (LC) controller advised the departure radar east (DRE) controller that the destination airport was instrument meteorological conditions (IMC) and the RNAV runway 14 approach was in use. The DRE controller then instructed the pilot to advise when he had the updated weather information for the destination airport and advised him to expect the RNAV runway 14 approach. The pilot responded that he had the updated weather information, and he acknowledged the RNAV runway 14 approach was in use. As the pilot approached the airport, the LC controller cleared the pilot to land on runway 14. According to air traffic control (ATC) surveillance data, the airplane tracked west of the final approach course. The pilot advised that he needed to perform a 360° turn and reported the field in sight, which the LC controller acknowledged. The LC controller then coordinated with the DRE controller and advised that the pilot was performing a 360° turn to realign with the approach. The DRE controller then asked the LC controller if the pilot was going to return to the approach. The LC controller stated that the pilot was doing a “quick 360.” The DRE controller advised the LC controller that he was going to vector an uninvolved airplane that had been following the accident airplane and would re-sequence it for the approach. The DRE controller asked the LC controller to let him know when the accident airplane landed, and the LC controller acknowledged. The LC controller advised the pilot that there was another airplane inbound for the approach behind him and instructed the pilot to advise when he was reestablished on final approach. The pilot acknowledged and stated he would report reestablished. The pilot then completed two clockwise 360° turns and, midway through a third turn, ATC surveillance data stopped approximately 0.8 nautical miles (nm) southwest of the runway 14 threshold. Two pedestrians who were walking together on a public walking trail sustained serious injuries when the airplane impacted wooded terrain. During the impact sequence, the wings and the empennage separated from the fuselage and the airplane was destroyed. Examination of the airframe, engine, and propeller found no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. The flaps were found at the fully extended position. The pitch trim was found in the full nose-down position. The airplane had not had an altimeter test, a pitot static test, or a transponder test performed within the 24 months before the accident, as required for operation under IFR in controlled airspace. A review of the pilot’s logbook showed that he had not met the required instrument experience requirements within the preceding 6 months. There was no record of the pilot obtaining an instrument proficiency check within the preceding 12 months. The owner of the maintenance facility the pilot was departing from reported that the pilot experienced difficulties operating and understanding the onboard navigation system, but that he knew of no issues with the systems. The pilot’s toxicology testing identified diphenhydramine. The quantity of the pilot’s specimen was not sufficient for quantitative testing. The specimen tested was also drawn at the same time as the pilot was receiving a large amount of donated blood products. Therefore, whether the diphenhydramine detected resulted from the pilot’s use or from transfused blood products could not be determined, and its contribution to the accident could not be established. During the post-accident evaluation, the pilot was found to have an intracranial vascular abnormality, or cavernous malformation. Cavernous malformations are common vascular brain lesions in adults. These lesions are increasingly identified due to more frequent use of brain imaging. Without symptoms such as seizures or headaches, the risk of serious effects is low. In this case, the pilot reportedly had no symptoms and was unaware of the lesion’s presence. It is unlikely that the cavernous malformation contributed to the accident. Neither post-accident drug nor alcohol testing were ordered nor conducted with the LC controller. Based on the available evidence, the pilot, who was not instrument current, initiated an IFR flight in an airplane that was not in compliance with required IFR equipment and inspection requirements. During the instrument approach, the pilot likely did not properly configure the onboard navigation system, resulting in the airplane tracking off course. When the pilot initiated a 360° turn during the instrument approach, the LC controller did not issue missed approach instructions in accordance with the tower’s standard operating procedures. Had the appropriate missed approach instructions been provided by the LC controller, the airplane likely would have been resequenced for another approach, rather than continuing the 360° turns. The presence of known IMC at the destination airport at the time of the accident was conducive to the development of spatial disorientation, and the airplane’s flight track is consistent with the known effects of spatial disorientation. The pilot’s 360° turns may have been appropriate in visual meteorological conditions (VMC); however, in IMC, they likely resulted in spatial disorientation and a subsequent loss of control.

Probable cause

The pilot’s spatial disorientation and subsequent loss of control while maneuvering outside established instrument approach procedures in instrument meteorological conditions, which resulted in an impact with terrain. Contributing to the accident was the local control controller’s failure to issue appropriate missed approach instructions due to inadequate procedural knowledge.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA144
Event ID
20240401194014
Case number
CEN24LA144
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, cause areas. 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: abce78d20ee1636c2111daf5d0a3b91129aaf8b52677ceec775085dc12ccee4c; retrieved 2026-09-15T08:12:08.739Z.