Piper PA44 accident near Bowling Green, Ohio, September 3, 2025
On September 3, 2025 at about 4:35 pm local time, a 2024 Piper PA44, registered N447BG, was substantially damaged in an accident during landing near Bowling Green, Ohio (Wood County airport). It was an instructional flight under general aviation rules (Part 91). 2 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 3, 2025 · about 4:35 pm local time · cases in 2025
- Place
- Bowling Green, Ohio · Wood County · cases near this airport · map
- Type
- Accident
- Injuries
- 2 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA44 180, built 2024 · all PA44s on the register
- Registration
- N447BG · registry record · serial 4496581
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On September 3, 2025, about 1135 eastern daylight time, a Piper PA-44-180, N477BG, was substantially damaged when it was involved in an accident near Bowling Green, Ohio. The private pilot and the designated pilot examiner (DPE) received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. According to the private pilot, who was undergoing a checkride for a private pilot airplane multi-engine land rating, the flight departed from Wood County Airport (1G0), Bowling Green, Ohio, without any anomalies. During the checkride, the pilot reported that while at altitude, the right engine was manually shut down to perform single-engine operations. After completing the single-engine maneuvers at altitude, the private pilot reported that the DPE initiated the procedure to restart the engine. The DPE then stated that he believed the engine had restarted because of the increase in manifold pressure indicated on the engine instrument gauges. Both pilots reported that the right engine was not brought back up to full power to ensure the engine was capable of normal operation after the in-flight shutdown. The private pilot reported that they continued the checkride and began an approach back to 1G0 while the DPE controlled the right engine to simulate single engine operations. The private pilot asked the DPE if, in the event of a go-around, he would be able to use both engines, and the DPE confirmed that he could use both engines for a go-around. While on final approach to land at 1G0, the private pilot reported that his approach was unstable and that he decided to execute a go-around. The private pilot advanced both throttles to full power; however, only the left engine responded, and the airplane yawed to the right. The DPE then took control of the airplane, where he reported that he retracted the landing gear and flaps, and then feathered the right propeller. The DPE stated that the airplane was unable to climb, and it continued to descend. The DPE turned the airplane to the right toward a field, and during the turn, the airplane impacted the field. A postaccident examination of the airplane by a Federal Aviation Administration inspector revealed that the airplane sustained substantial damage to both wings and the fuselage. The wreckage was retained for further examination.
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
- Loss of engine power (total) during landing defining event
The aircraft
- Airframe total time: 645.7 hours
- Last inspection: continuous airworthiness programme, August 12, 2025; 52 hours since
- Maximum gross weight: 3,816 lb
- Seats: 4
- Landing gear: retractable
- Operator: Bowling Green Flight Center LLC
The flight
- Flight plan: none
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 240° at 11 knots, gusting 20
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 81°F (27°C), dew point 52°F (11°C)
- Altimeter: 29.80 inHg
- Observation at 12:52 pm from TOL, 14 miles away
Weather report (METAR): KTOL 031652Z 24011G20KT 10SM CLR 27/11 A2980 RMK AO2 SLP089 T02670111 $
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Connections how this case links to the rest of the register
- N447BG on the register today · the tail number may have moved to another aircraft since
- Piper PA-44 Seminole 606 registered today · the model family and its accident history
- Piper 44,844 aircraft on the register
- Wood County Regional · nearest airport
- Accidents and incidents in Ohio 1,884 since 1982 · 253 in the last ten years
- Ohio 8,534 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA25LA333.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
