FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA20LA261 · Cessna 177RG

24 Jul 2020 · Salinas, PR, United States

Cessna 177RG · Accident: fuel starvation en route

From Mercedita International Airport (TJPS) to José Aponte de la Torre Airport (TJRV)

Report a problem

Event

NTSB case
ERA20LA261
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 177RG

Aircraft type
Cessna 177
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
N1813Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mercedita International Airport (TJPS), Ponce, PRTo José Aponte de la Torre Airport (TJRV), Ceiba, PR
Aircraft age
About 49 years (built 1971)
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
Fuel starvation
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 systems
  • Aircraft › Fluids/miscellaneous hardware

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

NTSB narrative

The pilot/owner and the instructor were conducting an instructional flight. The pilot reported finding no water contamination of the fuel during his preflight inspection of the airplane. They departed, performed airwork, and flew to an airport where several landings were performed. The flight then proceeded toward another airport, and during cruise flight at 1,100 ft mean sea level, the engine lost power. The pilot attempted to restore power but was unsuccessful. During the subsequent off-airport forced landing in soft terrain, the airplane nosed over during the landing roll.

After the airplane was recovered, small amounts of water were found in samples taken from each fuel tank, the reservoir tank assembly, and the airframe fuel strainer. The fuel tanks were then drained and found to contain about 29 gallons of fuel; the drained fuel did not contain water or contaminants. Postaccident examination of the engine revealed severe contamination of the servo fuel injector inlet screen by ferrous material, as well as evidence of corrosion and water. Additionally, evidence of foreign debris contamination, water, and/or corrosion were found in the fuel strainer, the internal steel valves of the engine-driven fuel pump, and components of the fuel flow divider. No issues were otherwise noted with the engine powertrain, ignition, induction, or exhaust systems. During postaccident testing, leakage was noted from the right fuel cap.

The most recent annual inspection was completed about 8 months before the accident. Following the first flight after the annual inspection, the pilot reported discrepancies to maintenance personnel regarding water in the fuel tanks, a rough running engine (which was later attributed to water ingestion), and a slow draining right fuel tank sump drain valve. The discrepancies were addressed by removing fuel tank sealant from the right-wing fuel tank drain valve boss ports and resealing the right inlet plate to the upper wing skin. According to the pilot, resealing the plate corrected the water intrusion issue. Given this information it is likely that the fuel system had been exposed to water for a period that was long enough for significant amounts of corrosion to develop. Ultimately, this resulted in the accumulation of corrosion and debris throughout the fuel system that most likely resulted in a blockage of the fuel injector inlet screen and/or fuel flow divider, fuel starvation, and the total loss of engine power during the accident flight. While the blockage of the servo fuel injector inlet screen occurred over time, it likely did not exist at the time of the airplane’s last annual inspection. The undetected blockage of the right wing fuel tank sump drain valve boss likely existed at the time of the last annual inspection, and may have contributed to the long-term water exposure and on-going water contamination issues after the annual inspection was completed.

Probable cause

Contamination and corrosion within the fuel system that resulted in a blockage, starvation of fuel to the engine, and the total loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20LA261
Event ID
20200724X30720
Case number
ERA20LA261
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, cause areas. 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: cf9d080140b9287a80c6702358e36a0943de372b6bde6e9b7a3f6c5ff5fa9bae; retrieved 2026-09-16T12:15:56.027Z.