WPR26FA224 · Piper PA-24-250
Piper PA-24-250 · Accident
From Youngstown Warren Regional Airport (YNG) to Geauga County Airport (7G8)
Event
- NTSB case
- WPR26FA224
- 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
- Ongoing
- API-reported fatalities
- 3 · 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
- Not recorded
Piper PA-24-250
- Aircraft type
- Piper PA-24
- 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
- N6403P
- Operator
- Diemand Larry L
- Onboard fatalities
- Unknown
- Route
- From Youngstown Warren Regional Airport (YNG), Youngstown, OHTo Geauga County Airport (7G8), Middlefield, OH
- Aircraft age
- About 67 years (built 1959)
- 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
- Unknown
- 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
- Unknown or undetermined
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On June 20, 2026, about 1535 eastern daylight time, a Piper PA-24-250, N6403P, was substantially damaged when it was involved in an accident near Middlefield, Ohio. The pilot and two passengers sustained fatal injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. A surveillance camera showed the airplane taxiing from an airport ramp at Youngstown/Warren Regional Airport (YNG), Youngstown/Warren, Ohio at 1520. Witnesses reported that the airplane’s intended destination was Geauga County Airport (7G8), Middlefield, Ohio, which was about 21 nm northwest of YNG (see figure 1).
Figure 1. Preliminary overhead view of accident flight track. Preliminary ADS-B data revealed that the airplane departed runway 23 at YNG about 1524 and maneuvered to the northwest. The airplane then climbed to a cruise altitude of about 2,300 ft mean sea level (msl). About 5 nm west of 7G8, the airplane turned to the west and initiated a descent from about 2,700 ft msl for a straight in approach for runway 29 at 7G8. About two miles from the departure end of runway 29, about 1,520 ft msl, the airplane started a descending right turn (see figure 2). The flight track data ceased about 1 nm east of runway 29, at an altitude of 1,345 ft msl, and at a groundspeed of approximately 63 knots.
Figure 2. Preliminary profile view of final segment of accident flight track. A review of preliminary air traffic control (ATC) audio revealed that the airplane was receiving visual flight rules (VFR) flight following services from ATC. Shortly after the airplane established cruise flight, ATC issued the pilot an advisory for an area of depicted moderate weather 4 miles northwest of YNG, extending about 7 miles northwest, moving to the southeast. The pilot received further instructions to deviate as necessary to avoid weather and subsequently responded to the controller that they could see through the precipitation, which appeared to be light. About 9 miles east of 7G8, ATC advised the location of their destination airport. The pilot responded that they did not have the airport environment in sight and requested to cancel flight following. Radar services were then terminated at 1529, and the pilot was advised to set his transponder to 1200 and change to the advisory frequency. At 1535, about 1,400 ft msl, the airplane dropped off radar coverage. No further communication with the airplane was noted after this time. A witness reported that the she saw the airplane cross above the tree line into her property from east to west in a straight and level attitude. Shortly after, she noted that the right wing dipped, while descending slightly, then she observed the airplane briefly return to a level roll attitude. She stated that the airplane made a sharp right turn followed by a steep, nose down descent into a field. The airplane was located 1 nautical mile east of 7G8 in an area of open cow pasture at an elevation of about 1,130 ft msl. The debris path was 50 ft long by 40 ft wide and was oriented on a northeast heading. All major components of the airplane were found within the debris path. The first identified point of contact (FIPC) was a ground scar with blue transfer mark, consistent with impact of the right tip tank, which was found separated about 30 ft northwest of the FIPC. A larger ground scar, consistent with impact of the engine was located about 23 feet northeast of the FIPC. The main wreckage was about 50 feet from the FPIC and consisted of the fuselage, wings, empennage and engine (see figure 3).
Figure 3. View of the accident airplane at rest in a grassy cow pasture. The fuselage exhibited impact damage from the firewall to the lower cabin. All windows, including the windscreen, were separated from the airframe. Flight control cable continuity for the rudder, elevator, and ailerons was confirmed from the cockpit to each of the respective flight control surfaces. The left wing was partially attached to the fuselage with chordwise wrinkles and crush damage from midspan to the wing tip. The damage extended from the left wing leading edge to the trailing edge. The flap and aileron both remained attached to the wing at their respective hinges. The right wing remained partially attached to the fuselage and had been torn chordwise about midspan. Chordwise wrinkles and crush damage were observed along the midspan of the wing which extended from the leading edge to the trailing edge. The flap and aileron both remained attached to the wing by their respective hinges. The empennage remained mostly intact with the vertical stabilizer attached to the tailcone and the rudder remained attached to the vertical stabilizer by its hinges. No damage was observed to the vertical stabilizer or the rudder. The stabilator remained attached to the tailcone bulkhead at its hinges. The engine remained attached to the fuselage. All components and accessories remained secured to their respective mounting pads, with exception of the right magneto, carburetor, and airbox, which were all found within the engine compartment. The three-blade, aluminum, constant speed propeller remained attached to the crankshaft propeller flange. Two blades appeared intact and undamaged. The third blade was dislodged in the hub and bent aft. The airplane and engine were recovered to a secured facility for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record WPR26FA224
- Event ID
- 20260621203204
- Case number
- WPR26FA224
- 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. 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: f0ef7c57601aad2d3b8491649c5558aca61a18080078c76bed610e7b22589364; retrieved 2026-09-15T09:17:11.516Z.