Piper PA28 accident near Muncie, Indiana, April 1, 2024
On April 1, 2024 at about 2:27 pm local time, a 1981 Piper PA28, registered N8438B, was destroyed in an accident during approach (IFR missed approach) near Muncie, Indiana (Delaware County Rgnl airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 1, 2024 · about 2:27 pm local time
- Place
- Muncie, Indiana · Delaware County Rgnl · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Piper PA28 236, built 1981 · all PA28s on the register
- Registration
- N8438B · no longer on the register · serial 28-8211002
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Course deviation during approach (IFR final approach)
- Loss of control in flight during approach (IFR missed approach) defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
- Air traffic event during approach (IFR missed approach)
- Explosion (post-impact) during post (impact)
- Fire/smoke (post-impact) during post (impact)
The NTSB's findings
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- Personnel issues › Action/decision › Action › Incorrect action selection › Pilot
- Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Pilot
- Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Contributed to outcome
- Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Compliance w/ procedure
- Organizational issues › Support/oversight/monitoring › Oversight › Oversight of operation › ATC
- Personnel issues › Experience/knowledge › Knowledge › Knowledge of procedures › ATC personnel
- Personnel issues › Action/decision › Action › Incorrect action performance › ATC personnel
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 625 hours in all
- Last flight review: May 17, 2022
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 2,660.6 hours
- Last inspection: annual inspection, March 28, 2024; 0.4 hours since
- Maximum gross weight: 3,000 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming Engines O-540-J3A5D (piston); 660 hours total
- Fire on the ground
The flight
- Departed from: BMG Bloomington IN at 1:37 pm
- Destination: MIE Muncie IN
- Flight plan: IFR
- Runway 14/3, 6,500 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 050° at 10 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 700 ft
- Temperature: 50°F (10°C), dew point 46°F (8°C)
- Altimeter: 29.87 inHg
- Observation at 9:53 am from KMIE
Weather report (METAR): KMIE 011353Z 05010KT 10SM BKN007 10/08 A2987 RMK AO2 CIG 005V011 SLP112 T01000078
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
36 documents, released by the NTSB on May 13, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
Other NTSB records under N8438B the same tail number, which may have belonged to a different aircraft at the time
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
