Piper PA28 N592FL
7 January 2023 · Suffolk, Virginia, United States · Fatal
Summary
On 7 January 2023 at about 17:13 local time, a Piper PA28 registered N592FL was involved in an accident near Suffolk, Virginia, United States. 2 people were on board and 2 died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 17:13
- Classification
- Accident
- Location
- Suffolk, Virginia, United States
- Coordinates
- 36.6022, -76.5981
- Aircraft
- Piper PA28
- Registration
- N592FL
- Category
- Airplane
- Year built
- 1971
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Edenton → Suffolk
- Aircraft damage
- Destroyed
- Weather
- VMC
- Light
- Day
- NTSB number
- ERA23FA103
People
2 people died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 2 | 0 | 0 | 0 |
Probable cause
The pilot’s decision to fly the airplane without confirming it had been released from maintenance, which resulted in a partial loss of engine power due to loose magnetos. Contributing to the outcome was the pilot’s failure to maintain adequate airspeed and his exceedance of the airplane’s critical angle of attack, which resulted in an aerodynamic stall.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The accident occurred about 5 miles from the destination airport near the conclusion of a short cross-country flight. Automatic dependent surveillance - broadcast (ADS-B) data showed that about 2 miles from the accident location the airplane’s descent rate rapidly increased to 500 ft/min with the airspeed staying just above 90 knots. The descent rate slowed to 200 ft/min before it rapidly increased to more than 1,500 ft/min during the final minute of flight. A performance study showed that a steep banked turn would have been required to orient the flight path with the wreckage direction and that the airplane’s final known speed was close to its stall speed in the turn. A witness reported seeing the airplane in a nosedive with two spiral trails of black smoke about 5 to 10 ft behind the airplane; however, she did not observe any fire from the airplane. Six days before the accident, the pilot brought his airplane to a mechanic, as it had an excessive engine rpm drop during a run-up magneto check. The mechanic changed some spark plugs but did not have a chance to run the engine. Three days before the accident, the pilot arrived at the mechanic’s hangar and performed a ground run of the engine on the ramp area near the mechanic’s hangar so the mechanic could listen to the engine. As soon as the pilot ran the engine, the mechanic knew that the new spark plugs did not correct the problem as the engine was “skipping.” The pilot shut down the engine and the mechanic informed the pilot that the airplane was not to be flown until he could investigate further, and he would most likely be able to do it the following week. The mechanic later moved the pilot’s airplane from the ramp in front of his hangar, into the pilot’s hangar, as bad weather was forecast. The mechanic added that he had not completed the maintenance on the airplane and that the pilot did not contact him before departing on the accident flight to see if the maintenance had been completed. Postaccident Examination of the wreckage revealed that the hold-down nuts on both magnetos were only finger tight. Some rotational damage was noted on both propeller blades. No other preimpact mechanical malfunctions were identified. Due to the combination of black smoke that the witness observed trailing the airplane, the limited rotational damage signatures that were observed on the propeller blades, and the only finger tight magneto hold-down nuts that were found during the postaccident engine examination, it is likely that the loose magnetos detrimentally affected ignition, which resulted in a partial loss of engine power. Given that there was a known, unresolved maintenance issue that existed prior to the flight, had the pilot positively affirmed the airplane’s airworthy condition with the mechanic prior to the flight, it is likely the accident would not have occurred. Additionally, the witness description of the airplane’s final descent, the airplane’s calculated speed during it’s final maneuvering, and the lack of a horizontal debris field observed at the accident site suggested that the airplane entered an aerodynamic stall before it impacted the ground.
Quoted verbatim from the NTSB record.
Other Piper PA28 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 12 May 2023 | Piper PA28 | Selma, Alabama, United States | - | No injuries | - |
| 29 Nov 2023 | Piper PA28 | Glencoe, Minnesota, United States | - | No injuries | - |
| 28 Sep 2023 | Piper PA28 | Whitesville, Kentucky, United States | - | Fatal | 2 |
| 26 Dec 2023 | Piper PA28 | Carmo da Cachoeira, Brazil | - | No injuries | - |
| 23 May 2023 | Piper PA28 | Reidsville, North Carolina, United States | - | Minor injuries | - |
| 19 Aug 2023 | Piper PA28 | Preston, Connecticut, United States | - | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 27 Feb 2023 | Cessna 150G | Hillsville, Virginia, United States | - | Fatal | 1 |
| 5 Aug 2023 | Hughes 369 | Elberon, Virginia, United States | Haverfield International Inc | Serious injuries | - |
| 30 Nov 2023 | Stinson 108-2 | Martinsville, Virginia, United States | - | No injuries | - |
| 3 Dec 2023 | Beechcraft C23 | Midland, Virginia, United States | - | Fatal | 1 |
| 11 Jan 2023 | Piper PA-32R-301 | Dayton, Virginia, United States | - | Fatal | 1 |
| 3 Aug 2023 | Boeing 767-322 | Chantilly, Virginia, United States | United Airlines Inc | Unknown | - |