FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12LA343 · Cessna 195A

18 May 2012 · Tipton, PA, United States

Cessna 195A · Accident: powerplant system/component malfunction/failure en route

From Old Bridge Airport (3N6) to Zelienople Municipal Airport (PJC)

Report a problem

Event

NTSB case
ERA12LA343
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

Cessna 195A

Aircraft type
Cessna 195
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
N9859A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Old Bridge Airport (3N6), Old Bridge, NJTo Zelienople Municipal Airport (PJC), Zelienople, PA
Aircraft age
About 62 years (built 1950)
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
Powerplant system/component malfunction/failure
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Pole
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

  • Aircraft › Aircraft power plant
  • Aircraft › Fluids/miscellaneous hardware

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that, during cruise flight, he noticed that the engine rpm began fluctuating and that, about 20 seconds later, the rpm dropped. The pilot immediately looked at the oil pressure gauge and observed that it was "reading zero." He then declared an emergency with air traffic control, and a controller informed him that the nearest airport was 15 miles south of his location. He brought the engine back to idle to keep it from seizing in case power would be needed later to avoid terrain, which was primarily mountain ridges with hills and narrow valleys, and set the propeller to low rpm. The pilot realized that he could not make it to the nearest airport and chose to land on a road in an industrial park. The landing was uneventful, but, during the landing roll, the airplane was substantially damaged when the left wing struck a standpipe and the airplane subsequently nosed over.

Examination of the engine revealed that a 1/2-inch metal oil line had fractured at the rocker's scavenge oil tube adjacent to the coupling sleeve and nut. Further examination revealed that the metal oil line had failed in fatigue in the manufactured bend adjacent to the coupling sleeve, that it was at least 34 years old, and that it had probably been reused many times. The oil tube assembly also displayed a distinctive bend and compression at the bead end and a slight bend at the nut end that were not specified on the manufacturer's drawings and were consistent with the oil tube assembly being significantly bent to fit on the engine. The manufactured bends also displayed oval cross-sections not specified in the drawings. The oval cross-sections may have been produced by the original manufacturing process but were likely produced by bending at each reuse, which would have initiated bending fatigue. Cracks propagating from the fracture face at the centerline of the tube were also present. Hardness testing revealed that the tubing at the fractured bend was harder than a sample of tubing that had not been subjected to any bending and that it exceeded the specified maximum hardness. This testing indicated that the increased hardness of the tubing in the bend had been produced by the original manufacturing process and/or by subsequent work hardening (that is, the undesirable strengthening of a metal such as copper by plastic deformation).

Probable cause

A fatigue failure of a copper oil line, which resulted in a partial loss of engine power due to oil starvation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12LA343
Event ID
20120521X02548
Case number
ERA12LA343
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. 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: 90434fb2d90066063d463301b5865233e8f92b0a87ce1332a068feada09335c1; retrieved 2026-09-15T18:11:50.638Z.