FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23FA103 · Piper PA28 140

7 Jan 2023 · Suffolk, VA, United States

Piper PA28 140 · Accident: loss of engine power (partial) on approach

From Northeastern Regional Airport (EDE) to Suffolk Executive Airport (SFQ)

Report a problem

Event

NTSB case
ERA23FA103
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
Completed
API-reported fatalities
2 · 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
Visual Meteorological Cond

Piper PA28 140

Aircraft type
Piper PA28
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
N592FL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Northeastern Regional Airport (EDE), Edenton, NCTo Suffolk Executive Airport (SFQ), Suffolk, VA
Aircraft age
About 52 years (built 1971)
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
Approach
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
Loss of engine power (partial)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23FA103
Event ID
20230108106549
Case number
ERA23FA103
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, coordinates, cause areas. 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: cd5b42d63ccaf332bb75ca30dc1922e3a12d5904f63fb03583b92606f8283cf3; retrieved 2026-09-15T07:55:52.748Z.