Morning Overview

A seaplane carrying 11 people caught fire after an emergency landing off Washington’s coast

A de Havilland DHC-3 seaplane carrying 11 people made an emergency landing in the water off Sucia Island in Washington State after diverting around a thunderstorm, then caught fire, injuring everyone on board. The aircraft was flying from Kenmore Air Seaplane Base to Roche Harbor Seaplane Base when it went down around 5:20 p.m. local time, according to federal records. The National Transportation Safety Board is now examining how a weather avoidance decision on a short island hop ended with a burning aircraft in a remote state park area.

Why a burning seaplane off Sucia Island matters now

The basic sequence is clear: a de Havilland DHC-3 took off from Kenmore Air Seaplane Base bound for Roche Harbor Seaplane Base, diverted to avoid a thunderstorm, then crashed in the Sucia Island state park area around 5:20 p.m. local time with 11 people on board, according to the Federal Aviation Administration. The operator, Kenmore Air, has said the pilot changed course to steer around a weather system, according to a separate account that also places the crash near Sucia Island state park. That combination of a weather diversion, a remote water landing and a post-impact fire raises immediate safety questions for a popular regional route.

The San Juan Islands rely heavily on short seaplane hops for tourism and local travel, and this flight followed a standard corridor between Kenmore Air Seaplane Base and Roche Harbor Seaplane Base, according to the same federal summary. When a routine leg on that corridor ends with all 11 occupants injured and the aircraft on fire, it forces regulators and operators to confront how quickly conditions can change even on familiar routes. It also focuses attention on how pilots balance the need to avoid intense thunderstorms with the hazards that can exist around the edges of those systems.

The working hypothesis for many observers is that the diversion placed the DHC-3 into an area of unstable air near Sucia Island, possibly involving wind shear or downdrafts that left the aircraft with little margin to recover at low altitude. The sources on record do not describe the precise wind patterns near Sucia Island at the time of the crash, and neither the Federal Aviation Administration nor the National Transportation Safety Board has released a detailed weather analysis. What is documented is that the pilot altered course specifically to avoid a thunderstorm, according to Kenmore Air’s account cited in a major wire report that also confirms the location in the Sucia Island state park area. That link between deliberate storm avoidance and a subsequent loss of control or hard water impact is the central tension investigators now have to sort out.

For passengers, the stakes are straightforward: a flight marketed as a relatively quick hop between Kenmore Air Seaplane Base and Roche Harbor Seaplane Base ended with injuries for all 11 people on board, according to both the federal incident summary and the narrative account from the operator. For the wider flying public, the incident raises questions about how much time and altitude seaplane pilots have to work with when rerouting around fast-building summer storms over cold, open water. Those choices can define whether an emergency water landing remains controlled or becomes a crash with a fire that threatens everyone on board.

The evidence behind the emergency landing and fire

On the record, the clearest factual anchor comes from the Federal Aviation Administration’s incident listing for Sucia Island. That entry identifies the aircraft as a de Havilland DHC-3 seaplane, notes that the approximate crash time was about 5:20 p.m. local, and lists the route as Kenmore Air Seaplane Base to Roche Harbor Seaplane Base, with the National Transportation Safety Board designated as the lead investigative authority, according to the Federal Aviation Administration. Those details confirm the aircraft type, timing, route and jurisdiction that frame the investigation.

A separate narrative account adds that the operator, Kenmore Air, said the pilot changed course to avoid a thunderstorm or weather system before the aircraft came down near Sucia Island state park, according to a major wire report that also confirms that 11 people on board were injured and that the crash occurred in the Sucia Island state park area. That report states that Kenmore Air attributed the route change directly to the thunderstorm, and it situates the accident geographically in the waters around Sucia Island, which is designated as a state park. Taken together, the federal listing and the operator’s account align on the flight’s origin and destination, the approximate time, the number of occupants and the general location.

What the official records do not yet provide are technical details about the fire itself. The Federal Aviation Administration’s summary confirms the basic event pattern and aircraft type but does not describe how or when the seaplane caught fire after the emergency landing. The major wire account confirms that the aircraft changed course to avoid a thunderstorm and that the crash resulted in injuries to all 11 occupants near Sucia Island, according to reporting from Sucia Island, but it does not cite any official statement on the ignition source or whether the fire started on impact or after passengers had begun to evacuate.

The investigative structure is straightforward. The National Transportation Safety Board is leading the inquiry into the accident, with support from the Federal Aviation Administration, according to the federal incident listing. That means NTSB investigators will typically examine the wreckage of the de Havilland DHC-3, collect maintenance and operational records from Kenmore Air, and analyze weather data for the time window around 5:20 p.m. local in the Sucia Island area. They will also attempt to reconstruct the pilot’s decision-making as the thunderstorm developed and the route changed between Kenmore Air Seaplane Base and Roche Harbor Seaplane Base.

From the passenger perspective, the verified data points are stark: 11 people on the aircraft, all injured, according to the major wire report that cites Kenmore Air and responders. The federal listing confirms that the incident involved a single de Havilland DHC-3 seaplane on that route at that approximate time, which aligns with the narrative of a single high-impact accident in a relatively confined area. Those matching numbers and locations give investigators a solid starting point, even as many finer details remain absent from public records.

What remains unresolved and what to watch next

Key technical questions remain open. Neither the Federal Aviation Administration incident summary nor the major wire account identifies the source of the fire that followed the emergency landing off Sucia Island. There is no public data yet on whether the blaze began in the engine compartment, the fuel system, or another part of the de Havilland DHC-3, and there is no official timeline for how quickly flames spread after the aircraft hit the water. Without that information, it is impossible to say from the current record whether design factors, maintenance issues or the dynamics of the impact played the largest role in the fire.

The hypothesis that localized wind shear or downdrafts near Sucia Island overwhelmed the seaplane after it diverted around the main thunderstorm remains just that: a hypothesis. The sources on record confirm that the pilot changed course to avoid a thunderstorm and that the aircraft then crashed in the Sucia Island state park area, according to both the federal listing and the major wire report, but they do not provide measured wind data or cockpit recordings that would allow anyone outside the investigation to draw firm conclusions about the exact trigger. Until the National Transportation Safety Board releases a preliminary or final report, any effort to pinpoint the immediate aerodynamic cause goes beyond the available evidence.

There are also gaps around the human toll and emergency response. The major wire account states that 11 people on board were injured and that responders reached the Sucia Island area, but it does not provide a breakdown of injury types or long-term medical impact. The Federal Aviation Administration summary confirms the number of occupants and the basic fact of the crash but does not elaborate on rescue timelines, survival equipment use or how passengers escaped a burning seaplane in open water. Those details will matter for any future changes to safety equipment or training on similar routes.

For now, the practical consequence for readers and travelers is heightened attention to weather on short seaplane flights in the San Juan Islands. Passengers booking trips between Kenmore Air Seaplane Base and Roche Harbor Seaplane Base can ask operators how they handle sudden thunderstorms, what safety briefings they provide about emergency water landings, and what equipment is carried on de Havilland DHC-3 aircraft on that route. Operators, for their part, will be watching the National Transportation Safety Board’s work closely, because any findings about the role of weather diversion, low-altitude maneuvering near Sucia Island, or post-impact fire behavior could lead to changes in procedures or equipment requirements on similar flights.

The next concrete milestone will likely be a preliminary report from the National Transportation Safety Board that builds on the Federal Aviation Administration’s initial confirmation of the aircraft type, route, and approximate crash time. That document should clarify at least some of what happened between the decision to avoid the thunderstorm and the moment the de Havilland DHC-3 hit the water near Sucia Island with 11 people on board. Until then, the verified record shows a weather diversion, a crash in a state park area, and a seaplane that caught fire after an emergency landing off Washington’s coast, with many of the most important technical answers still to come.

More from Morning Overview

*This article was researched with the help of AI, with human editors creating the final content.