FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX84LA229 · Republic RC-3

22 Mar 1984 · Lakeport, CA, United States

Republic RC-3 · Accident: partial loss of engine power (mechanical failure) during initial climb

From 102 · Lakeport, CA to CLEAR LAKE, CA

Report a problem

Event

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

Republic RC-3

Aircraft type
Republic RC-3
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
N6470K
Operator
Unknown
Onboard fatalities
Unknown
Route
From 102 · Lakeport, CATo CLEAR LAKE, CA
Aircraft age
Not recorded
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
Initial climb
First occurrenceThe 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
Partial loss of engine power (mechanical 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

  • Engine assembly, cylinder › Low compression
  • Engine assembly, piston › Worn
  • Engine assembly, valve, intake › Movement restricted
  • Ignition system, spark plug › Contamination
  • Other maintenance personnel › Maintenance, inadequate
  • Pilot in command › Operation with known deficiencies in equipment, intentional

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

NTSB narrative

THE PLT REPORTED THAT ON HIS PREFLIGHT HE FOUND THE ENG COMPRESSION & OIL LEVEL TO BE LOW BUT AFTER SERVICING THE OIL TO THE PROPER LEVEL HE DEPARTED & ON INITIAL CLIMB, AFTER REACHING ABOUT 100 FT AGL, THE ENG STARTED POPPING & LOSING RPM. THE PLT MADE A LEFT TURN TO AVOID OBSTACLES & LANDED IN A SMALL GRAPE VINEYARD. POST CRASH EXAMINATION OF THE ENG REVEALED LOW COMPRESSION & EXCESSIVE OIL CONSUMPTION DUE TO WEAR. THE ACFT HAD BEEN OPERATED WITH AUTOMOTIVE FUEL.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX84LA229
Event ID
20001214X39075
Case number
LAX84LA229
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 055d637c174537413ab34a2c7be5ff4c34b38b830b4842093fe1a8903b501034; retrieved 2026-09-22T02:20:33.961Z.