FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17LA010 · Piper PA 28-180

2 Oct 2016 · Clarendon, TX, United States

Coyote Flight Piper PA 28-180 · Accident: loss of engine power (total) en route

From Rick Husband Amarillo International Airport (AMA) to Childress Municipal Airport (CDS)

Report a problem

Event

NTSB case
CEN17LA010
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 28-180

Aircraft type
Piper PA-28
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
N5196L
Onboard fatalities
Unknown
Route
From Rick Husband Amarillo International Airport (AMA), Amarillo, TXTo Childress Municipal Airport (CDS), Childress, TX
Aircraft age
About 49 years (built 1967)
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
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

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

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

NTSB narrative

The student pilot was conducting a cross-country personal flight. The student pilot reported that, while in cruise flight, the single-engine airplane lost power. He then performed a forced landing to a field, during which the wings and firewall were damaged.

Examination of the engine revealed damage consistent with lubrication distress. Further, a cylinder piston pin was found broken, and metal was found in the oil pickup screen and in the oil filter, which had recently been changed. It is likely that the degraded piston pin was the source of the metal in the oil, which clogged the oil inlet screen and reduced the amount of oil available to the engine and resulted in the loss of engine power. A nonmechanic had performed preventative maintenance and changed the oil and oil filter shortly before the accident. He reported that he noticed the metal in the filter but did not consider it to be an indication of a problem.

Probable cause

The failure of a cylinder piston pin, which resulted in an obstructed oil inlet screen, reduced the amount of oil available to the engine, and led to the subsequent loss of engine power. Contributing to the accident was the failure of the nonmechanic, who had recently changed the oil and oil filter, to recognize that metal in the filter was indicative of a problem.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17LA010
Event ID
20161005X54209
Case number
CEN17LA010
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: 97fea88fa6cc73c5a0322a92c7198ff3521ef5e335ad54b85f26a42662787ff5; retrieved 2026-09-16T04:21:27.879Z.