FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR25LA198 · Republic RC-3

28 Jun 2025 · Coolin, ID, United States

Republic RC-3 · Accident: loss of control in flight during takeoff

From Tanglefoot Seaplane Base (D28) to an unrecorded destination

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR25LA198
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
Event fatalities
Unknown
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

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
N6759K
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From Tanglefoot Seaplane Base (D28), Cavanaugh Bay, IDTo not recorded
Aircraft age
About 78 years (built 1947)
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
Takeoff
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 control in flight
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 oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

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

NTSB narrative

The pilot of the amphibious airplane reported that during takeoff from a lake in windy conditions, the airplane encountered windshear, stalled, and landed hard on the water surface, which resulted in the right float to separate. A video of the accident sequence showed the airplane veer right on the water during takeoff from the lake and became airborne. Once airborne, the airplane rolled right and then left before it landed hard on the water. A short time later, the airplane became submerged under the water surface. The right wing was substantially damaged. There were no preaccident mechanical malfunctions or failures that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain control of the airplane and exceedance of the critical angle of attack during takeoff in windy conditions which resulted in a subsequent hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR25LA198
Event ID
20250707200468
Case number
WPR25LA198
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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: e88a9be3ccccf43956a508de5b8bc455106e62c37db60ff67715a3cf46824f72; retrieved 2026-09-16T20:02:47.036Z.