CEN12FA586 · Piper PA-23-150
Piper PA-23-150 · Accident: loss of engine power (total) en route
From Pinckneyville Du Quoin Airport (PJY) to Blakesburg, IA
Event
- NTSB case
- CEN12FA586
- 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 PA-23-150
- Aircraft type
- Piper PA-23
- 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
- N1486P
- Operator
- John R. Johnson · private individual
- Onboard fatalities
- Unknown
- Route
- From Pinckneyville Du Quoin Airport (PJY), Pinckeneyville, ILTo Blakesburg, IA
- Aircraft age
- Not recorded
- 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
- En route · cruise
- 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 (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A witness, who was a private pilot, stated that he observed a twin-engine airplane flying overhead on a northerly heading. He reported that the airplane was about 2,000 feet above ground level in level flight and that the left propeller blades were not rotating. The accident site, located in an open field with obstacles, including rolling hills, woods, and roads, was about 6.5 miles from the private pilot's location. Evidence indicated that the airplane struck a tree in a near wings-level attitude. Larger fields and flatter terrain with fewer obstacles were located northwest of the apparent route of flight (the airplane's actual flight route was unknown), and, if the pilot had landed in one of these areas, he would have had a greater opportunity for a successful forced landing. However, the airplane was near or exceeded its maximum takeoff weight upon departure. According to the accident airplane's climb chart, the airplane was unable to maintain altitude when the left engine lost power due to its excessive weight and single-engine performance, the existing high-density altitude (2,963 feet), and, possibly, the pilot's execution of single-engine flight procedures, which left the pilot fewer options to reach a more suitable landing location.
Evidence indicates that the left engine experienced a total loss of power. The spark plugs in the Nos. 1, 2, and 4 cylinders, which had fuel primer lines attached, exhibited carbon-fouling, indicating that a rich-fuel mixture existed at the time of the accident and that the pilot most likely unsuccessfully attempted to regain the left engine's power by using the fuel primer to prime the cylinders.
The left wing gascolator bowl was removed and a blue silicon jell-type sealant was found covering about two-thirds of the area of the bowl's circumference and the area where a gasket is typically placed; however, no gasket was found in the gascolator. The blue silicon jell was consistent with Permatex Blue Silicon Gasket Maker, which has the following note in its directions: "NOTE: Not recommended for use on head gaskets or parts in contact with gasoline." If the gascolator seal is breached, air can enter the fuel system and possibly unport the carburetor, which would cause an uncommanded engine shutdown due to fuel starvation. The pilot was also an airframe and powerplant mechanic with inspection authorization. He performed the last annual maintenance inspection of the airplane and subsequent aircraft maintenance. He likely improperly used the blue silicon sealant during maintenance operations.
Although the autopsy and toxicological examinations revealed that the pilot possibly had significant health issues, no evidence was found indicating that the pilot was incapacitated during the flight.
Probable cause
The pilot's improper decision to attempt to execute a forced landing to an open field with obstacles. Contributing to the accident was the left engine’s total loss of power due to fuel starvation as a result of the introduction of air into the fuel system through a gascolator seal breach and the pilot’s use of an improper substance on the left wing gascolator bowl during maintenance operations, which led to the gascolator seal breach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12FA586
- Event ID
- 20120830X73434
- Case number
- CEN12FA586
- 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. 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: 3257400ea6185c42d4119f79c25fd65fb746d557f93c7ec028cfcbe4eefc32a1; retrieved 2026-09-14T01:26:21.329Z.