WPR22LA177 · Piper PA-12
Piper PA-12 · Accident: powerplant system/component malfunction/failure during takeoff
Event
- NTSB case
- WPR22LA177
- 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
- 0 · 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-12
- Aircraft type
- Piper PA-12
- 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
- N3960M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 75 years (built 1947)
- 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
- Takeoff
- 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
- Powerplant system/component malfunction/failure
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that shortly after departure, about 700 ft above ground level (agl), the windshield was sprayed with oil. He turned and entered the downwind leg of the traffic pattern and attempted to land on the runway. He reported that he was too high during the approach and aborted the landing. On the second attempt to land on runway 30, the oil spray was getting worse, and the pilot made a precautionary landing resulting in substantial damage to the fuselage. The postaccident examination of the airplane and interview with the mechanic revealed that the expansion plug was improperly installed and had separated from the end of the crankshaft, causing oil to exit through the propeller spinner resulting in the oil spray on the windshield.
Probable cause
The inadequate maintenance and inspection of the crankshaft expansion plug, which resulted in the separation of the expansion plug from the crankshaft and the subsequent loss of oil and windshield obstruction during departure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22LA177
- Event ID
- 20220517105088
- Case number
- WPR22LA177
- 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: 9291ee24d57705d71ebad0a1f8eb3aadbd368b775142b98916ba902621a0a36e; retrieved 2026-09-16T15:13:44.484Z.