Piper PA28 accident near Preston, Connecticut, August 19, 2023
On August 19, 2023 at about 10:00 pm local time, a 1963 Piper PA28, registered N7463W, was substantially damaged in an accident during enroute (cruise) near Preston, Connecticut. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A failure of the No. 2 connecting rod, which resulted in a total loss of engine power.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 19, 2023 · about 10:00 pm local time
- Place
- Preston, Connecticut · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA28 180, built 1963 · all PA28s on the register
- Registration
- N7463W · registry record · serial 28-1353
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
During a cross-country flight the pilot noticed the oil pressure decreased to zero. Seconds later, he noticed oil flowing up the windscreen and then the engine then lost total power. The pilot successfully landed the airplane in a field but, during the landing rollout, the right wing struck a metal pipe that was hidden in brush, separating it from the airplane. Postaccident examination of the engine revealed a portion of the engine crankcase above the No. 2 cylinder was fractured and separated from the engine. The crankshaft end of the No. 2 connecting rod was separated from the crankshaft’s No. 2 connecting rod journal. A review of the aircraft maintenance logbook revealed that the most recent annual inspection was completed 3.5 operating hours before the accident. The maintenance log entry documenting the annual inspection noted in part that the oil filter was replaced, and that the old oil filter was cut open and inspected, with no contamination noted. The most recent engine overhaul was completed almost 25 years before the date of the accident (the engine manufacturer recommended that the engine be overhauled within 12 calendar years of having entered service). Based on the available information, the loss of engine power was most likely the result of a deterioration of the engine’s internal mechanical components that had been occurring over the time since the engine was last overhauled. This ultimately resulted in the failure of the No. 2 connecting rod, and the total loss of engine power.
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 enroute (cruise) defining event
- Off-field or emergency landing during landing (landing roll)
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Failure
Pilot
- Certificate: private
- Ratings: single-engine land; rotorcraft: helicopter
- Flight time: 130 hours in all; 33 in this make and model
- Last flight review: May 24, 2022
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,504 hours
- Last inspection: annual inspection, May 12, 2023; 3.5 hours since
- Maximum gross weight: 2,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-360-A3A (piston); 3,504 hours total
The flight
- Departed from: MVY Vineyard Haven MA at 9:05 pm
- Destination: FWN Sussex NJ
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 240° at 10 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 6,000 ft
- Temperature: 73°F (23°C), dew point 57°F (14°C)
- Altimeter: 29.93 inHg
- Observation at 5:56 pm from GON, 12 miles away
Weather report (METAR): KGON 192156Z 24010KT 10SM BKN060 23/14 A2993 RMK AO2 SLP134 T02330144
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
11 documents, released by the NTSB on July 24, 2024. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 11 pages | View Download |
| 2 | Memorandum for Record A�� Pilot Statement | PDF, 2 pages | View Download |
| 3 | Memorandum for Record A�� Passenger Statement | PDF, 3 pages | View Download |
| 4 | Maintenance Records | PDF, 4 pages | View Download |
| 5 | Additional Maintenance Log Excerpts | PDF, 4 pages | View Download |
| 6 | Lycoming Services Instructions | PDF, 2 pages | View Download |
| 7 | Lycoming Tbo Schedules | PDF, 8 pages | View Download |
| 8 | Investigative Photographs | PDF, 4 pages | View Download |
| 9 | Wreckage Examination Summary | PDF, 7 pages | View Download |
| 10 | Statement of Party Representatives to NTSB Investigation | PDF, 1 page | View Download |
| 11 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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.
