11 Survive Kenmore Air Seaplane Crash in Washington
By: Evgeny Padezhnov
A Kenmore Air seaplane crashed during an emergency landing in Washington. All 11 people aboard got out of the aircraft. One person is reported in critical condition.
The accident happened in the evening. The crew was attempting an emergency landing when the aircraft went down. The cause is not yet public. An official investigation will follow. Early details in accidents like this change often, so the facts below stay close to what is confirmed.
What is known so far
The confirmed facts are limited. A seaplane operated by Kenmore Air was involved. Eleven people were on board. All of them exited the aircraft. One is in critical condition.
The pilot was attempting an emergency landing. That word matters. A routine water landing is normal for a seaplane. An emergency landing means something forced the crew down before plan. The trigger is not yet confirmed.
Key point: everyone got off the aircraft. For a water accident with 11 occupants, that outcome is significant. Getting clear of a floatplane on water is hard, especially if the aircraft flips or takes on water.
No aircraft type has been confirmed in the initial report. Eleven occupants points to a larger single-engine floatplane. Kenmore Air operates de Havilland Canada designs, including the Beaver and the Otter. A turbine Otter can carry roughly ten passengers plus a pilot. The specific airframe here has not been named. Treat any type as unconfirmed until investigators state it.
Who Kenmore Air is
Kenmore Air is a long-established seaplane operator in the Pacific Northwest. It is based in Kenmore, Washington, near the north end of Lake Washington. The company runs scheduled and charter flights across Puget Sound, the San Juan Islands, and coastal British Columbia.
Floatplanes are its core business, not a side service. The fleet centers on de Havilland Canada aircraft built for short takeoff and landing from water. These designs are rugged and suited to lake and harbor operations.
In plain terms: this is not a casual operator. Kenmore Air has flown floatplanes commercially for decades. That track record is part of why the crash stands out.
Why seaplane emergency landings are unusual
Seaplanes land on water by design. That is the normal mode. So a crash during an emergency landing is an uncommon event to see reported.
A seaplane already has floats. If the engine fails over water, the crew has a landing surface below them. That is an advantage a land plane does not have over a lake or sound. The problem is that water landings under stress are not simple.
Water is not a uniform surface. Waves, chop, swell, and glassy conditions each change how the aircraft touches down. Glassy water hides the true height above the surface. Rough water can catch a float and pull it down.
Common mistake: assuming a water landing is always soft. A float that digs in can flip the aircraft forward. Pilots call this a nose-over. It can happen in seconds and can trap occupants. Float handling is treated as a distinct skill for this reason.
An emergency compounds every one of these factors. The crew may have less time, a degraded aircraft, or a poor choice of landing spot. The FAA seaplane and float operations handbook documents these hazards in detail.
The physics of a water touchdown
Two water-landing techniques explain why the surface state is so important. Both are standard in seaplane training.
Glassy water is the first case. A mirror-smooth surface removes depth cues. The pilot cannot judge height above the water by looking at it. The technique is to set a fixed pitch attitude and a known power setting, then descend at a controlled rate until the floats touch. Reaction to the surface itself is too late.
Rough water is the second case. Here the pilot lands along the swell line, not across it. Power cushions the touchdown. The nose stays up to keep the float tips from digging in. A misjudged approach in swell raises the nose-over risk sharply.
An emergency removes margin from both techniques. A failing engine may not deliver the power a cushioned touchdown needs. Fading light removes visual cues over water. In practice, the combination of a forced descent and an imperfect surface is exactly where water landings go wrong.
How the investigation will work
In the United States, the National Transportation Safety Board investigates civil aviation accidents. The Federal Aviation Administration also takes part. The NTSB leads on probable cause. The FAA covers regulation and oversight.
Investigators will examine several areas in parallel:
- Aircraft: engine, controls, floats, maintenance records, and weight and balance.
- Environment: weather, water state, light, and visibility at the time.
- Human factors: crew actions, training, recent hours, and workload during the emergency.
- Operations: the route, the purpose of the flight, and any distress call.
The board typically issues a preliminary report within a few weeks. That report states facts, not cause. A final report with probable cause takes far longer, often more than a year. Complex accidents run longer still.
Recovery of the airframe matters here. A submerged or damaged aircraft holds physical evidence. Fuel, control surfaces, and the engine all get examined. Maintenance history feeds the timeline.
Early reports change. First accounts of occupant counts, injuries, and sequence often get corrected within days. Wait for the NTSB preliminary report before drawing conclusions about cause.
Commercial float operations and the rules
Scheduled and charter passenger flights in the US fall under 14 CFR Part 135. Commuter and on-demand seaplane services operate inside that framework. It sets standards for crew training, maintenance, and dispatch that differ from private flying.
Part 135 operators carry required inspections and recurrent pilot checks. Those records become central evidence in any accident review. Investigators will pull the airframe's logbooks and the crew's currency early.
Regulation does not remove risk. It narrows it. The value of the paper trail is that it lets investigators reconstruct the state of the aircraft and crew before the flight. That reconstruction is where a probable cause usually forms.
Survival and egress
Eleven people leaving the aircraft is the standout detail. It suggests the landing kept the cabin survivable. It also suggests occupants could reach exits and get clear of the aircraft.
Float operations depend on egress readiness. Life vests, accessible exits, and a passenger briefing all matter when an aircraft is on water. The outcome here points to at least some of those factors working under pressure.
One critical injury still underlines the danger. An emergency water landing is violent even when it is not fatal. Impact forces, cold water, and confined egress all threaten occupants at once. Water temperature in the Pacific Northwest adds a further hazard for anyone in the water for long.
What to watch next
Follow the official record, not social media accounts. The first hours after any crash produce conflicting reports. Occupant numbers and injury counts shift as responders confirm them.
Try it: check the NTSB aviation investigation pages for the case entry and preliminary report. Match every claim about cause against that source. If a detail is not in the NTSB or FAA record, treat it as unverified.
Two questions will define this investigation. What forced the emergency landing? And what turned a water landing into a crash? Both answers will come from the recovered airframe and the recorded evidence — not from early speculation. Until the preliminary report lands, the honest position is that the cause is unknown.
Information is accurate as of the publication date. Terms, prices, and regulations may change — verify with relevant professionals.