Hurricane Isaias made its first landfall in the United States on Ocean Isle Beach, North Carolina, at 11:10 p.m. EDT on August 3, 2020, as a Category 1 hurricane with sustained winds near 75 mph. A second landfall followed near the eastern end of Fire Island, New York, and a third on Long Island shortly after, both on August 4. Its final landfall came as a tropical storm near Pointe-à-Pitre, Guadeloupe, but the storm’s U.S. impacts were concentrated in the Carolinas, mid-Atlantic, and Northeast.

Cyclone mechanics that explain Isaias’s landfall sequence

Isaias (pronounced ees-ah-EE-ahs) formed as a tropical wave that the National Hurricane Center first identified near the Cabo Verde Islands around July 24, 2020. The system crossed the Atlantic at low latitude, and warm sea-surface temperatures above 28°C (82°F) along its path supplied latent heat through condensation in the eyewall. That heat engine kept the circulation spinning even as wind shear intermittently disrupted the core.

The storm’s odd multi-landfall pattern comes from geography and track geometry. A hurricane makes “landfall” only where the center of the circulation crosses a coastline. Islands and peninsulas interrupt the coastline, so one storm can make several landfalls as it moves past them. Isaias paralleled the U.S. East Coast from Florida to Maine, which meant the center crossed several coastal segments in quick succession.

Two competing forces steered the track. A deep-layer ridge of high pressure over the western Atlantic pushed the storm northwest toward the Bahamas and Florida early in its life. A mid-latitude trough over the eastern United States then eroded that ridge, turning Isaias north and eventually northeast. This steering shift is why the storm skimmed the Florida coast rather than hitting it squarely, then accelerated up the seaboard at more than 30 mph by August 4.

Isaias never developed a large, symmetric eye. Dry air from the south and moderate wind shear tilted the vortex, which limited intensification and kept the system mostly at Category 1 strength after its Bahamas crossing. The storm also carried forward speed that translated to high wind swaths well ahead of the center. Plain-language translation: Isaias was a fast, lopsided hurricane whose wind field stretched far from its center.

Quantified landfall timeline and track

Date and time (EDT) Landfall point Intensity at landfall Sustained winds
July 30, 2020 Near Cabo Rojo, Puerto Rico (tropical storm) 50 mph 50 mph
July 31, 2020 Eastern Dominican Republic (tropical storm) 50 mph 50 mph
Aug. 1, 2020 Southern Bahamas (Category 1 hurricane) 75 mph 75 mph
Aug. 3, 2020, 11:10 p.m. Ocean Isle Beach, North Carolina 75 mph 75 mph
Aug. 4, 2020, 2:40 a.m. Eastern end of Fire Island, New York 70 mph 70 mph
Aug. 4, 2020, 3:40 a.m. Long Island, New York 70 mph 70 mph

The National Hurricane Center’s tropical cyclone report logged Isaias as a Category 1 hurricane at its North Carolina landfall, with a central pressure near 988 millibars. That pressure is modest by Atlantic record standards, which shows how limited the deepening was relative to the wind field.

The storm’s forward speed mattered far more than its peak wind. At its fastest, Isaias raced northeast at around 35 mph, producing wind damage across 13 states in a single day. That speed also kept rainfall from lingering over a single watershed, which reduced inland flooding risk compared with slower systems.

A useful comparison is Hurricane Irene in 2011, which hit the Northeast as a tropical storm but caused catastrophic inland flooding in Vermont because it moved slowly. Isaias’s quick pace produced a different hazard profile, with the worst damage from wind, tornadoes, and widespread power outages rather than river flooding.

Edge cases that scrambled the official record

The count of Isaias landfalls depends on which coastlines you accept. The National Hurricane Center’s report lists multiple U.S. landfalls, and the Fire Island and Long Island crossings occurred within roughly an hour of each other. Some reference sources list only the first U.S. landfall in North Carolina as the definitive answer, while others describe the New York crossings as separate landfalls. Both are technically correct, but the primary answer is North Carolina.

Puerto Rico was not a state landfall but a humanitarian event. Isaias brought heavy rain and power outages on July 30 before it was formally named, because the circulation lacked a closed center earlier in its life. That timing gap is a real forecasting problem: a system can cause damage before it earns a name.

The post-tropical phase is another edge case. By the time Isaias reached Maine and Canada the next day, the storm had lost tropical characteristics. The final landfall in Guadeloupe matters for the storm’s overall record but not for the U.S. impacts most people are searching for. Recent research published in 2023 also suggested Isaias would have been classified as a Category 2 at landfall under updated intensity frameworks, which underscores how classification depends on measurement methodology.

Misconceptions about Isaias and landfall

Landfall location is not the same as impact location. Isaias produced 89 tornado warnings across the mid-Atlantic and Northeast, more than any other Atlantic hurricane recorded in a single day up to that point. Tornadoes and damaging wind gusts occurred hundreds of miles from the landfall point, which is why the coast crossing alone understates the storm’s reach.

Category does not encode every hazard. A Category 1 designation describes maximum sustained wind in a small radius, not storm surge, rainfall, or the number of people affected. Isaias’s 75 mph wind at landfall was strong enough to topple trees in waterlogged soil, and power outages exceeded two million customers across multiple states.

The term “hurricane” also has a timing trap. A storm becomes a hurricane only when sustained winds reach 74 mph, and it stops being a hurricane when it leaves that range or becomes post-tropical. Isaias was downgraded to a tropical storm just before reaching Canada, yet some sources refer to “Hurricane Isaias’s landfall in New York,” which conflates a 70 mph tropical storm with a 74 mph hurricane threshold.

A final misconception concerns the Bahamas. Isaias hit the Bahamas as a hurricane on August 1, and that landfall occurred before the U.S. landfalls, not after. The sequence matters for anyone reconstructing the storm’s intensity history.

What the landfall record means for safety decisions

The key lesson from Isaias is that landfall timing is a planning variable, not an academic footnote. Emergency managers use the projected crossing point to time evacuation orders and pre-position resources. The margin of error on Isaias’s North Carolina landfall was tight, and the storm struck just before midnight, so overnight timing amplified risk for coastal residents caught without evacuees’ lead time.

Landfall location also shapes surge and river-flood forecasts. A track that stays offshore still pushes water onshore through the Right Front quadrant, and Isaias generated storm surge of 2 to 4 feet along parts of the Carolinas coast. The National Hurricane Center’s small-craft and rip-current advisories extended far beyond the cone of uncertainty before the center reached the coast.

For anyone assessing their own exposure, the practical thresholds are measurable. Shielded or inland windows survive when sustained winds stay below roughly 50 mph, but debris becomes a projectile risk above that. If a forecast projects 74 mph or more at your location, the storm qualifies as a hurricane at that point. If your area has a high proportion of shallow-rooted trees and saturated soil, 60 mph gusts can cause outages even in a tropical storm.

The most counterintuitive operational caveat is that landfall maps do not predict where people will need help. Post-storm assessments after Isaias showed disproportionate outages in communities far from the crossing point, especially in areas with overhead power lines and older tree canopies.

Limitations of the landfall record and how to read it

Hurricane landfall databases are constructed afterward from a blend of aircraft reconnaissance, satellite intensity estimates, and surface observations. Isaias was observed by reconnaissance aircraft several times, but gaps between flights left room for error in assigned wind speeds. The National Hurricane Center formally assigns a best track during post-storm analysis, and those values can differ from the operational values issued in real time.

Position uncertainty matters as much as intensity uncertainty. At landfall, the center’s position can be uncertain by several miles, and that uncertainty propagates into local storm-surge and rainfall forecasts. For Isaias, the actual center crossing near Ocean Isle Beach was later refined in the tropical cyclone report, which is why the exact beach name is important rather than just “coastal North Carolina.”

Report times may appear as UTC or UTC-4, which shifts date labels by hours. U.S. operations use EDT or EST, while hurricane records often publish UTC, so a late-evening EDT landfall can appear on the next calendar date in UTC. This article uses U.S. Eastern time.

Weather datasets also change. Reanalysis projects can revise historic wind estimates, and changes in intensity classification frameworks can retroactively affect how storms are labeled. Any answer to where Isaias made landfall should specify whether it refers to the operational record or the revised best track.

None of these limitations changes the primary answer: Ocean Isle Beach, North Carolina, is the official first U.S. landfall point for Hurricane Isaias. The secondary crossings near Fire Island and Long Island are separate verified landfalls, and they do not replace the North Carolina answer.

For hurricane-zone residents, the Florida Division of Emergency Management and local National Weather Service offices remain the authoritative sources during active storms. Forecast advisories update every few hours, and landfall projections can shift by tens of miles. The historical record is a teaching tool; the operational advisory is what should drive decisions.