Kenmore Air Floatplane Crash Near Sucia Island: What We Know and the Questions Investigators Must Answer
by Aviation Law Group
Our hearts are with everyone impacted by Thursday’s crash near Sucia Island. For the ten passengers and the pilot aboard Kenmore Air Flight 140, N704KA, what began as an ordinary summer flight over the San Juans became a terrifying fight for survival, and for their families it brought the kind of news no one is ever ready to receive. That all eleven people survived is a genuine mercy, owed in no small part to the passengers who kept their composure and to the boaters and first responders who rushed to the water. We are holding the injured, and especially the person who remains in critical condition, close in our thoughts as they begin to heal.
Because we care about the people affected, we also believe they deserve honest answers about what happened and why. Here is what has been reported so far:
On the afternoon of Thursday, July 23, 2026, the Kenmore Air floatplane departed Lake Union in Seattle around 4:30 p.m., bound for Roche Harbor on San Juan Island, with ten passengers and one pilot aboard. By early accounts, the pilot was attempting an emergency landing in Shallow Bay, near Sucia Island, when the airplane came down and caught fire at about 5:15 p.m. Four people were injured, with injuries ranging from broken bones to head trauma and lacerations, and at least one was listed in critical condition.
It is far too early for conclusions, and nothing here is an attempt to be one. What follows is context, including a few facts that have not featured in the initial coverage, offered from the perspective of a firm whose attorneys are pilots and aircraft mechanics, who have litigated a strikingly similar accident in these same waters.
The questions now are the ones we hear after every serious accident: What happened? Could it have been prevented? And what should be done to protect the people who were hurt?
The Investigation Is Just Beginning
At this early stage, the cause of the crash is unknown. The investigation will require a careful examination of the aircraft, its maintenance and operating history, weather and visibility conditions, flight-path data, witness accounts, air-traffic-control communications, and the pilot’s actions during the final portion of the flight.
Early reports following an aircraft accident often provide only a limited picture of what occurred. The fact that an aircraft crashed into the water does not, by itself, establish whether the accident resulted from a mechanical failure, a loss of control, weather, an operational decision, a medical event, or another cause.
The National Transportation Safety Board and Federal Aviation Administration will be expected to examine the accident sequence in detail. Investigators will likely seek to determine:
- What type of aircraft was involved and its maintenance history;
- The aircraft’s weight, loading, and center of gravity;
- Weather, visibility, wind, and water conditions at the time of the accident;
- The aircraft’s route, altitude, speed, and flight path;
- Radio communications and available tracking data;
- Whether there were any mechanical or flight-control abnormalities;
- Whether the pilot reported an emergency or other problem;
- The aircraft’s condition before impact; and
- Whether any operational or organizational factors contributed to the accident.
The answers to those questions may not be known for some time.
The Importance of the Aircraft’s Final Flight Path and Weather in the Area
One of the most important aspects of any aviation investigation is reconstructing the aircraft’s final minutes and seconds.
Based on the available ADS-B flight-track data, the airplane appears to have been operating at roughly 500 feet above the water. For a seaplane on a short island route, a cruise altitude that low is not especially unusual, but it is the kind of detail investigators will nonetheless examine closely as they reconstruct the final minutes of the flight.
Investigators in this case will pay close attention to available flight-tracking information, radar data, communications, witness statements, and, where available, aircraft-recorded data leading to the accident site. It has been reported that the aircraft departed from Lake Union in Seattle bound for Roche Harbor on San Juan Island. The site of the accident is not near the anticipated flight path. Thunderstorms were reported in the area, and investigators will examine what role, if any, the convective weather may have played in this accident.
The final flight path is only one part of the investigation, however. A seemingly sudden accident may have its origins much earlier, in maintenance, inspection, dispatch, weather planning, aircraft loading, or other decisions made before takeoff.
That is why experienced aviation investigations look beyond the moment of impact.
Floatplane Operations Present Unique Safety Challenges
Seaplane operations in the Pacific Northwest involve operating in an environment that differs substantially from conventional airport operations.
Pilots must account for changing weather, wind, visibility, water conditions, marine traffic, remote operating locations, and limited options for an emergency landing. The San Juan Islands are a particularly challenging operating environment because of their geography, waterways, islands, terrain, and rapidly changing conditions.
That does not mean that a crash in such an environment was unavoidable. It means the investigation must examine the conditions that existed at the time of the accident and the decisions made in response to those conditions.
Maintenance and Mechanical Issues Must Be Carefully Examined
A thorough investigation will also examine the aircraft’s maintenance history.
Most reporting has described the airplane simply as a Kenmore Air floatplane. The more important detail is the specific type. Flight 140 was a de Havilland DHC-3 Otter, a single-engine turbine-converted floatplane that forms the backbone of Kenmore’s charter and scheduled Part 135 service. Kenmore operates one of the largest de Havilland seaplane fleets in the world, including roughly nine DHC-3 Otters, and it is by reputation one of the most respected seaplane operators anywhere. A strong reputation is meaningful, but it does not answer the question of why this airplane ended up in the water, and it does not exempt the aircraft, its components, or its maintenance from scrutiny.
Investigators will review inspection records, component histories, recent maintenance, deferred or recurring discrepancies, and any work performed on critical systems. That may involve examining maintenance procedures, inspection intervals, component design, prior failures, service information, and the conduct of the aircraft’s owners, operators, maintenance providers, and manufacturers. If a mechanical failure contributed to the accident, investigators will need to determine not only what failed, but why it failed and whether the failure should have been detected earlier.
Here is the piece of context missing from the early coverage. The DHC-3 Otter has a documented, safety-critical failure history that the flying public has largely forgotten but that we have not. In September 2022, a turbine DHC-3 Otter operating a passenger flight crashed in Mutiny Bay, off Whidbey Island, killing all ten aboard. The NTSB determined the probable cause to be the in-flight unthreading of a clamp nut on the horizontal stabilizer trim actuator, caused by a missing lock ring, which drove the airplane into an uncontrollable pitch-down. The finding was serious enough that the FAA issued an emergency airworthiness directive ordering all U.S. DHC-3 operators to immediately inspect that actuator. Aviation Law Group represented families in that case, so we know this aircraft, this failure mode, and the records that reveal it.
We are not suggesting the Sucia accident involved the same failure. Indeed, this accident’s early signature looks quite different. The point is narrower and important: when a specific aircraft type has a known, recognized safety issue, a competent investigation examines the type-specific records first, rather than starting and ending with the pilot. The actuator inspection history, the airworthiness-directive compliance records, and the component logbooks for this airplane are among the first documents that should be secured.
The Human Factors Investigation
After almost every accident, there is a temptation to reduce a complex event to a single human mistake. A proper investigation resists that. It asks what information the pilot actually had at the time, not what is known later with hindsight; what warnings or indications appeared; how much time there was to respond; and whether any system or component malfunction affected the pilot’s ability to control the airplane.
Nevertheless, the pilot’s actions will also be examined as part of the investigation.
Investigators must consider the information available to the pilot at the time—not information learned later with the benefit of hindsight.
Relevant questions may include:
- What weather information was available before and during the flight?
- What information did the pilot receive regarding the aircraft’s condition?
- What options were available if a problem developed?
- How much time was available to respond?
- What warnings or indications were present?
- What training and procedures applied to the flight?
- Did any equipment or system malfunction affect the pilot’s ability to control the aircraft?
Aviation accidents are often the result of multiple contributing factors rather than a single isolated mistake.
What Happens Next
The investigation will proceed in stages. Investigators will first document the accident scene and recover relevant aircraft components and evidence. They will then examine the wreckage, review records and data, interview witnesses, and reconstruct the accident sequence.
A preliminary report may provide basic factual information, but it generally will not identify the final cause of an accident. The NTSB’s final determination can take considerably longer and may identify multiple contributing factors.
For the passengers and families affected by this accident, however, the legal investigation may begin well before the NTSB issues its final report.
Important evidence can be lost quickly. Witness recollections may fade. Maintenance records, electronic data, communications, and other information must be preserved and examined promptly.
Aviation Law Group Is Monitoring the Investigation
Aviation Law Group is closely monitoring the crash near Sucia Island and the ongoing investigation into what caused the aircraft to go down.
At this early stage, it is too soon to reach conclusions about the cause of the accident or responsibility for what occurred. Those conclusions should be based on evidence, not speculation.
But the central questions are clear: What happened? Why did it happen? Could it have been prevented? And did any failure in the design, manufacture, maintenance, operation, or oversight of the aircraft contribute to the accident?
Those questions deserve a complete and independent investigation.
Our thoughts remain with everyone affected by this accident.
This article is based on preliminary, publicly available information and reflects the firm’s analysis as of the date of writing. It is not legal advice, does not create an attorney-client relationship, and is not a conclusion about the cause of, or responsibility for, the July 23, 2026, accident, which remains under investigation. References to the aircraft type, its history, and prior accidents are provided as context and are not allegations of wrongdoing by any person or company. This article will be updated as additional facts become available.
Aviation Law Group, PLLC, is a firm devoted exclusively to aviation accident and injury litigation. Aviation is all we do, and we have done it for decades. What sets us apart is, as far as we know, unmatched anywhere in the world: every one of our attorneys is either a licensed pilot or an aircraft mechanic; and some are both. We do not need an outside expert to explain a logbook entry, an airworthiness directive, or a trim-actuator inspection. We read them ourselves.
That experience is directly on point here. Aviation Law Group represented families in the 2022 Mutiny Bay DHC-3 Otter accident off Whidbey Island, the same aircraft type that went down near Sucia, in the same Puget Sound waters. We know the Otter, its turbine conversion, its control system, and the specific records that reveal whether a known failure mode was addressed. We have handled numerous engine-failure and in-flight-emergency cases, and we understand what it takes to trace a fire or a power loss back to its true source.
Aviation Law Group maintains its main offices in Seattle, Washington, with additional offices in Honolulu, Hawaii, and Jupiter, Florida, and represents clients throughout the country and internationally. If you or a loved one was aboard Flight 140, or was injured in this crash, we would be honored to talk with you confidentially about what happened and what your options are, with no obligation. You can reach us at info@aviationlawgroup.com or at aviationlawgroup.com.