Piper PA28R accident near Meriden, Connecticut, April 11, 2019
On April 11, 2019 at about 10:54 pm local time, a 1977 Piper PA28R, registered N38658, was substantially damaged in an accident during approach (VFR pattern base) near Meriden, Connecticut (Meriden Markham Muni airport). It was a personal flight under general aviation rules (Part 91). 2 people were seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The loss of engine power for undetermined reasons.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 11, 2019 · about 10:54 pm local time
- Place
- Meriden, Connecticut · Meriden Markham Muni · map
- Type
- Accident
- Injuries
- 2 people were seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA28R 201, built 1977 · all PA28Rs on the register
- Registration
- N38658 · no longer on the register · serial 28R-7737106
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot stated that he intended to fly in the airport traffic pattern after routine maintenance work. He noted no anomalies in the preflight inspection of the airplane or the engine runup and noted that the fuel was "to the tabs." He flew the normal traffic pattern and extended the downwind leg to allow time for another airplane in the traffic pattern. After reaching an altitude of about 500 ft above ground level on the base leg, he attempted to add power to maintain altitude. The engine did not respond, and the pilot noted that the tachometer indicated 2,000 rpm and was decreasing. The pilot attempted to restart the engine, but it did not respond, and the airplane continued to descend. During the forced landing to a baseball field, the airplane impacted power lines and subsequently impacted the ground tail-first. Postaccident examination of the engine revealed no evidence of any preimpact mechanical failures or malfunctions that would have precluded normal operation, and the reason for the loss of engine power could not be determined.
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 approach (VFR pattern base) defining event
- Collision with terrain or object (not controlled flight into terrain) during approach
- Off-field or emergency landing during landing
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 353.5 hours in all; 29.3 in this make and model; 21.3 in the last 90 days; 5.5 in the last 30 days; 151.8 as pilot in command
- Last flight review: January 15, 2019
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: serious injuries
Pilot-Rated Passenger
- Certificate: private
- Ratings: single-engine land
- Flight time: 200 hours in all; 40.7 in this make and model
- Last flight review: June 11, 2018
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: rgt
- Injury: serious injuries
The aircraft
- Airframe total time: 1,586.5 hours
- Last inspection: annual inspection, July 20, 2018; 63 hours since
- Maximum gross weight: 2,750 lb
- Seats: 4
- Landing gear: retractable
- Engine: Lycoming IO-360-C1C6 (piston); 1,649 hours total
- Operator: Westchester Flying Club Inc
The flight
- Departed from: MMK Meriden CT at 10:50 pm
- Destination: MMK Meriden CT
- Flight plan: none
- Runway 18, 3,100 ft by 75 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 170° at 6 knots
- Visibility: 10 statute miles
- Sky: overcast at 9,500 ft
- Temperature: 46°F (8°C), dew point 23°F (-5°C)
- Altimeter: 30.25 inHg
- Observation at 10:53 pm from MMK, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
15 documents, released by the NTSB on October 25, 2019. 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, 9 pages | View Download |
| 2 | Pilot Statements | PDF, 3 pages | View Download |
| 3 | Witness Statements | PDF, 2 pages | View Download |
| 4 | Fuel Record | PDF, 1 page | View Download |
| 5 | FAA Inspector's Statement | PDF, 1 page | View Download |
| 6 | Pilot Logbook Excerpts | PDF, 4 pages | View Download |
| 7 | Engine Logbook Excerpts | PDF, 8 pages | View Download |
| 8 | Area Weather Report | PDF, 1 page | View Download |
| 9 | Flying Club Log Entry | PDF, 1 page | View Download |
| 10 | Investigative Photographs | PDF, 9 pages | View Download |
| 11 | Accident Area Overview | PDF, 1 page | View Download |
| 12 | Memorandum for Record - Wreckage Examination | PDF, 9 pages | View Download |
| 13 | Memorandum for Record - Fuel System Examination | PDF, 2 pages | View Download |
| 14 | Statement of Party Representatives to NTSB Investigation | PDF, 9 pages | View Download |
| 15 | Release of Aircraft Wreckage and Retained Evidence | PDF, 4 pages | 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.
