WPR26FA233 · Cessna 195
Cessna 195 · Accident while maneuvering
Event
- NTSB case
- WPR26FA233
- 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
- Ongoing
- API-reported fatalities
- 2 · 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 195
- Aircraft type
- Cessna 195
- 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
- N3877V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 77 years (built 1949)
- 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
- Maneuvering · low-altitude flying
- 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
- Miscellaneous/other
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On June 24, 2026, about 1428 Pacific daylight time, a float equipped Cessna 195, N3877V, was substantially damaged when it was involved in an accident near Pasco, Washington. The pilot and passenger were fatally injured. The airplane was operated under Title 14 Code of Federal Regulations as a Part 91 personal flight. Preliminary recordings from the Tri-Cities Airport (PSC) Air Traffic Control Tower (ATCT) indicated that the accident pilot transmitted to the ATCT about 1421, when they were about 15 miles south of PSC and stated that they were a float plane with the intent to land on the Columbia River. The controller stated that landing would be at their own risk and requested that they report when their landing was assured. The pilot responded that they would report when their landing was assured. The controller transmitted PSC’s current wind and altimeter setting to the accident pilot, with no further transmissions received from the pilot. According to multiple witness accounts and videos received, the accident airplane overflew the Ed Hendler Bridge from east to west and crossed the bridge between the north tower and the river’s eastern shoreline. It continued over the river on a westerly heading for about 9 seconds, then abruptly pitched nose down for 1 second before it struck a high tension transmission line, about 1,040 ft west of the bridge. Subsequently, the accident airplane descended vertically into the Columbia River and came to rest in the river inverted, about 100-200 ft from the river’s eastern shoreline. (see Figure 1.)
Figure 1. Accident sequence over river. According to personnel at the Port of Kennewick, located on Clover Island in Kennewick, Washington, the pilot of the accident airplane contacted the Port by telephone, prior to the date of the accident and inquired about fuel availability at the Port’s marina. Employees at the Port communicated with the accident pilot regarding fueling options via the Port’s dock side fueling station and offered additional information for a local company who offered mobile fueling services for the same type of fuel, should the airplane need more fuel than the Port could provide. According to the passenger’s family members, the flight originated from the airplane’s base of operations on the Napa River, near Napa, California, on the morning of the accident. The intended destination was the Tanglefoot Seaplane Base (D28), Cavanaugh Bay, Idaho. The airplane was removed from the river by crane and set down on its right side, about 1,500 ft downriver from the impact site. Examination of the wreckage revealed that the floats and float struts, the empennage, engine and propeller assembly all remained attached to the fuselage. Both wings were observed separated from the fuselage at their roots and displayed leading edge crushing and denting. The left wing displayed tearing, crushing, and scraping at mid span, from the leading edge to the trailing edge. The left aileron was not observed with the recovered wreckage. Both wing flaps were observed in the extended position. Members of the Benton County Sheriff’s Office Marine Unit and Columbia Basin Dive Rescue team conducted a search for the aileron, however, it was not located. The wreckage was recovered to a secure location for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record WPR26FA233
- Event ID
- 20260625203243
- Case number
- WPR26FA233
- 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: f5c7c6269bce08c34ea3a7ccb957024bd54a7cc852e8595feecce822b9cd3d9f; retrieved 2026-09-15T09:17:32.586Z.