FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16LA333 · Ryan NAVION B

27 Sept 2016 · Hurt, VA, United States

Ryan NAVION B · Accident: powerplant system/component malfunction/failure en route

From Culpeper Regional Airport (CJR) to Long Island Airpark (NC26)

Report a problem

Event

NTSB case
ERA16LA333
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
0
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

Ryan NAVION B

Aircraft type
Ryan NAVION
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
N5327K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Culpeper Regional Airport (CJR), Culpeper, VATo Long Island Airpark (NC26), LONG ISLAND, NC
Aircraft age
About 66 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
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
  • Personnel issues › Task performance

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

NTSB narrative

During cruise flight, the private pilot felt the engine suddenly begin to vibrate. He then heard a loud bang; the engine vibration increased, smoke and oil emanated from the engine compartment, and the engine lost total power. The pilot was unable to glide the airplane to a nearby airport and performed a forced landing in a field, during which the airplane struck and rolled through a fence, which resulted in substantial damage to the right wing. Examination of the engine revealed that its crankcase was absent of oil, and there were holes in the crankcase near cylinder Nos. 2, 4, and 6. Subsequent teardown examination revealed that the internal engine components exhibited heat distress consistent with a lack of lubrication. Further examination revealed that the oil temperature probe port was safety wired but could be moved by hand and that the crush washer between the probe and the cooler was installed backwards. This evidence is likely indicative that the probe had not been properly installed, although it could not be determined when that may have occurred. Air pressure applied to the oil cooler showed a leak between the oil temperature probe and the cooler. Oil residue noted on the exterior of the cooler indicated that the oil leak had likely been present for some time and that it was likely where the engine's oil had leaked out, ultimately resulting in the engine failure due to oil starvation. Had the leak been noted and addressed, by correctly installing the oil temperature probe, during the airplane's most recent annual inspection, which was completed 11 days before the accident, it is likely that the engine would not have been starved of oil.

Probable cause

Incorrect installation of the oil temperature probe and an inadequate annual inspection that failed to detect leaking oil around the loose probe, which resulted in a catastrophic engine failure due to oil starvation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16LA333
Event ID
20161014X34716
Case number
ERA16LA333
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: cf3ebbc8910d5a58f5f0ee18d794ea823c6804ffd04055cd527d63a75bc16cd7; retrieved 2026-09-16T04:24:01.067Z.