Middle School NGSS Resource Hub
Three-dimensional breakdowns, phenomenon ideas, misconceptions, and engagement activities for every NGSS middle school standard.
๐ Jump to Your Discipline
-
๐งช
โPhysical ScienceMS-PS1 to MS-PS4 โข 19 standards
-
๐งฌ
โLife ScienceMS-LS1 to MS-LS4 โข 21 standards
-
๐
โEarth & SpaceMS-ESS1 to MS-ESS3 โข 15 standards
-
๐ ๏ธ
โEngineeringMS-ETS1 โข 4 standards
Middle School NGSS Standards
Pick any standard. Each page is your full lesson-planning workspace for that standard.
Forecasting Natural Hazards: Reading Patterns in Data to Predict and Prepare
"Analyze and interpret data on natural hazards to forecast future catastrophic events and inform the development of technologies to mitigate their effects."
"Emphasis is on how some natural hazards, such as volcanic eruptions and severe weather, are preceded by phenomena that allow for reliable predictions, but others, such as earthquakes, occur suddenly and with no notice, and thus are not yet predictable. Examples of natural hazards can be taken from interior processes (such as earthquakes and volcanic eruptions), surface processes (such as mass wasting and tsunamis), or severe weather events (such as hurricanes, tornadoes, and floods). Examples of data can include the locations, magnitudes, and frequencies of the natural hazards. Examples of technologies can be global (such as satellite systems to monitor hurricanes or forest fires) or local (such as building basements in tornado-prone regions or reservoirs to mitigate droughts)."
NGSS does not list an explicit assessment boundary for this standard.
The three dimensions packed into this standard
Every standard bundles a DCI (the content), a SEP (the science practice), and a CCC (the crosscutting lens). They run in the same task, not in sequence.
"Mapping the history of natural hazards in a region, combined with an understanding of related geologic forces can help forecast the locations and likelihoods of future events."
Natural hazards leave fingerprints. Earthquakes cluster along plate boundaries. Hurricanes spin up over warm ocean water in seasonal windows. Volcanoes give off gas and small quakes before they erupt. When you map where hazards have happened and understand the geologic or atmospheric forces driving them, you can forecast where and when they're likely to happen again. Forecasting isn't fortune-telling. It's pattern reading.
"Analyze and interpret data to determine similarities and differences in findings."
Students aren't memorizing hazard facts. They're pulling data (maps, magnitudes, dates, tracks) and looking for similarities and differences. Where do earthquakes cluster? Which months do hurricanes hit? What signals showed up before Mt. St. Helens blew? The data is messy on purpose. Finding the pattern is the science.
"Graphs, charts, and images can be used to identify patterns in data."
Patterns are the whole game here. A single earthquake is a data point. A map of a thousand earthquakes is a story about plate boundaries. The CCC pushes students to stop seeing hazards as random and start seeing them as patterned, repeatable, and forecast-able to a degree.
๐ Where This Standard Fits in the K-12 Progression
Use this to plan the year. Knowing what students should already know and what they're heading toward keeps the lesson focused.
""
Forecasting Natural Hazards: Reading Patterns in Data to Predict and Prepare
""
๐ Phenomena for MS-ESS3-2
Anchor the lesson in one puzzling phenomenon kids keep coming back to. Use the two investigative phenomena to sharpen specific facets.
Two Mountains, Two Endings: Mt. St. Helens, 1980
On March 20, 1980, a magnitude 4.2 earthquake hit Mt. St. Helens. Over the next eight weeks, the north flank of the mountain bulged outward by more than 450 feet. Gas emissions climbed. Small quakes swarmed under the summit. On May 18, the mountain exploded sideways and the eruption killed 57 people. Scientists had been watching the whole time and had already restricted access. The hazard was unstoppable. The disaster was partly reduced because the data was being read.
"If a volcano shows weeks of warning signs, why don't we get the same kind of warning from an earthquake?"
- "What signs were the scientists watching for, and how did they know which ones mattered?"
- "Could the death toll have been zero if people listened?"
- "Do all volcanoes give this much warning, or was Mt. St. Helens unusual?"
The 2004 Indian Ocean Tsunami and the Sirens That Weren't There
On December 26, 2004, a magnitude 9.1 earthquake off Sumatra sent a tsunami racing across the Indian Ocean. Over 230,000 people died across 14 countries. At the time, the Indian Ocean had no tsunami warning system. The Pacific had one. The technology existed. After 2004, a network of deep-ocean buoys and coastal sirens was built across the Indian Ocean. Use this one to sharpen the mitigation lens the anchor opens up: same kind of hazard data, completely different outcome when the warning system is there.
"If the science to predict a tsunami already existed, why didn't every ocean have a warning system?"
- "How fast does a tsunami actually travel, and how much warning time can you really get?"
- "Who decides whether a region gets an early warning system?"
- "Are there other hazards where the tech exists but the system isn't built yet?"
The Building That Stayed Standing in Tokyo, 2011
The March 11, 2011, Tลhoku earthquake hit magnitude 9.0. Skyscrapers in Tokyo, 230 miles from the epicenter, swayed for several minutes. Most of them stayed standing. Many newer Japanese high-rises are built on base isolators, rubber and steel pads that let the building rock slightly while the ground shakes underneath. Same kind of pattern reading as the anchor, only this time the data shaped engineering, not just monitoring. Decades of earthquake data told Japanese engineers what their buildings had to survive.
"If we can't predict when an earthquake will happen, how do we engineer for the one that's coming anyway?"
- "How can a building be flexible AND safe at the same time?"
- "Why don't all earthquake-prone places use the same building codes?"
- "If the next quake is bigger than any in the data, are these buildings still safe?"
โ ๏ธ Misconceptions Your Students Will Walk In With
These come up almost every year. Knowing them in advance lets you head them off in the first lesson.
"Scientists can predict the exact day and place of an earthquake"
They can't, and that's not what this standard claims. Earthquakes happen suddenly with no reliable warning signs. What scientists CAN do is estimate the likelihood of an earthquake in a region over a long time window. The U.S. Geological Survey estimates there's a 72% chance of a magnitude 6.7 or greater earthquake in the San Francisco Bay Area in the next 30 years. That's a probability, not a date.
"Hurricanes always happen in summer"
Atlantic hurricane season is June 1 through November 30, with peak activity in August and September. So most are late summer or early fall, not midsummer. The Pacific season runs slightly different. The reason hurricanes need a season at all is that they need ocean surface temperatures above about 80ยฐF (26.5ยฐC) to form, and that's only the case during certain months.
"Tornadoes only happen during big visible storms"
Tornadoes almost always form inside a parent thunderstorm called a supercell, but the tornado itself can drop with little warning even from a storm that looked routine on radar a few minutes earlier. The bigger point: a storm doesn't have to look catastrophic from a distance to produce one. That's why tornado warnings rely on Doppler radar signatures, not just on what the sky looks like.
"Volcanoes erupt without warning"
Most volcanoes give multiple warning signs before they erupt. Increased gas emissions (sulfur dioxide, carbon dioxide), ground deformation (the mountain literally bulges as magma rises), and swarms of small earthquakes below the volcano. Mt. St. Helens in 1980 had two months of warning signs before the May 18 eruption. The U.S. Geological Survey Cascade Volcano Observatory was already monitoring it.
๐ Common Student Questions and How to Respond
These come up almost every time this standard gets taught. Plan a response and you'll keep the lesson focused.
Because the where and the when are two different questions, with different kinds of evidence. Where comes from mapping fault lines and plate boundaries, which barely move on human time scales. When comes from the buildup and release of stress inside the rock, which we can't see directly. The rock stores stress for decades or centuries, then snaps. The snap moment is what makes earthquakes nearly impossible to time.
They don't know exactly. They track the storm by satellite and aircraft, then run multiple forecast models that produce a cone of possibility. The center line is the most likely path, and the cone shows where the storm could realistically end up. As the storm gets closer, the cone narrows because there's less time for the path to change. Even one day before landfall, the exact spot can shift by 50 to 100 miles.
Because tsunamis travel slower than the signals that warn about them. A tsunami in deep ocean moves at jet speed, but the earthquake that caused it sends seismic waves through Earth even faster. Sensors detect the quake first. Buoys detect the tsunami forming. A warning can race ahead of the wave by minutes to hours, depending on distance from the coast. Earthquakes give no comparable lead time because the shaking itself is the first signal.
No. The forces driving hazards (plate tectonics, atmospheric energy, gravity on a slope) are way bigger than anything humans can shut off. What we can do is mitigate. Build buildings that bend instead of breaking. Move people out of the way before a hurricane lands. Build levees and reservoirs. Design tsunami evacuation routes. The hazard still happens. The disaster doesn't have to.
๐ Vocabulary Students Need for MS-ESS3-2
Twelve terms students need to access this standard. Definitions in plain-English, classroom-ready language.
A natural event with the potential to cause damage. Earthquakes, hurricanes, tornadoes, floods, droughts, wildfires, volcanic eruptions, tsunamis, landslides.
A prediction about a future event based on patterns in past data. Forecasts give likelihoods, not certainties.
The chance that something will happen, often given as a percentage or a range. "72% chance of a major quake in 30 years" is a probability statement.
A number that measures the size or strength of a hazard. Earthquakes have the Richter or moment magnitude scale. Hurricanes have the Saffir-Simpson scale (Category 1 through 5). Tornadoes have the Enhanced Fujita scale (EF0 through EF5).
How often a hazard happens in a given region over time. "Three major hurricanes per decade" is a frequency statement.
A regular, repeating feature in data. Patterns are what make forecasting possible.
The edge where two of Earth's tectonic plates meet. Most earthquakes and volcanoes happen along plate boundaries.
An instrument that detects and records ground motion. Networks of seismometers around the world locate earthquakes within seconds.
A radar system that detects motion in the atmosphere. Used to spot rotation inside thunderstorms and issue tornado warnings.
Action taken to reduce the damage a hazard causes. Includes engineering (earthquake-resistant buildings), planning (evacuation routes), and warning systems (tsunami sirens).
Technology that detects a hazard and sends alerts in time for people to take action. Examples: ShakeAlert for West Coast earthquakes, tsunami buoy networks, hurricane satellite tracking.
A long-lived thunderstorm with a deeply rotating updraft. The kind of storm that produces most strong tornadoes.
๐ก Free Engagement Ideas for MS-ESS3-2
Earthquake Mapping Lab
Groups get a printed world map and a data set of the last 100 earthquakes over magnitude 5.5 (date, location, magnitude). They plot each one with stickers or markers scaled to magnitude. After plotting, students circle the visible clusters and label them. The Ring of Fire emerges without anyone telling them what to look for. They then predict the next region likely to have a major quake.
Hurricane Tracking from the Inside
Each group is assigned one major Atlantic hurricane (Katrina, Sandy, Harvey, Ian, Helene, Milton). They get the track data (latitude, longitude, wind speed, pressure) and a blank Atlantic map. They plot the storm's path day by day. After plotting, they compare their hurricane to the other groups' storms. Where did they form? Where did they intensify? Where did they land? They use the patterns to forecast the next likely landfall region.
Design a Mitigation on a Budget
Students get a fictional town with a known hazard (earthquake zone, hurricane coast, tornado alley, flood plain). They have a $1 million budget. Choices include earthquake retrofitting ($300K per major building), tsunami warning sirens ($75K each), levees ($400K per mile), evacuation route signage ($25K per district), and a community early-warning text system ($150K). They build a mitigation plan and defend their priorities using the hazard data.
Read the Volcano Signals
Students get four time-series data sets from real monitored volcanoes (gas emissions, small earthquake counts, ground deformation, surface temperature) for the weeks leading up to an eruption. The data is unlabeled. They identify which volcano is "warming up" and which is dormant. They then write a forecast statement: which one is most likely to erupt in the next two weeks, and what data supports the call.
๐ Assessment Ideas for MS-ESS3-2
Three short tasks that hit all three dimensions. Doable in one class period each.
Students get a regional hazard data set (their choice: earthquakes for California, hurricanes for the Gulf Coast, tornadoes for Oklahoma) and a blank regional map. They mark the area most likely to be hit by the next major event in the next 10 years and write a 4-5 sentence defense citing specific data points (frequency, magnitude pattern, location cluster).
Students pick one hazard type (earthquake, hurricane, tornado, tsunami, volcanic eruption, wildfire, flood, drought) and design one mitigation technology for it. The pitch includes: what hazard pattern in the data justifies the mitigation, how the technology works in 3-4 sentences, and one limitation of the mitigation. Diagram required.
Students are given two hazard scenarios. One is a volcano showing two months of warning signs. The other is a sudden magnitude 6.5 earthquake on a known fault. They write a comparison explaining why one can be reliably forecast in the short term and the other cannot, using evidence from the standard's data types (location patterns, monitoring tools, advance signals).
๐ฏ What Proficient Student Work Looks Like
Same prompt, three student responses at different proficiency levels. Use as anchor papers when scoring.
"Use the earthquake data set to forecast where the next major earthquake in the United States is most likely to occur, and explain how the patterns in the data support your forecast."
- A specific claim backed by data, observation, or model
- Use of standard-specific vocabulary in context
- Connection between the visible and the underlying explanation
- A question they're still wondering about (curiosity stays alive)
The next earthquake will probably happen in California because California has a lot of earthquakes. The map shows lots of dots in California, so it's most likely there. Earthquakes happen because of plates moving.
Names the right region but doesn't cite specific data points. Doesn't use probability language. Doesn't explain why California has the pattern it does. Stops at "lots of dots."
The next major earthquake in the United States is most likely to occur along the San Andreas Fault in California or in the Cascadia Subduction Zone in the Pacific Northwest. The data shows that 87 out of the last 100 earthquakes over magnitude 5 happened along these two zones. Both zones are at plate boundaries, where pressure builds up between plates and is released as shaking. The Cascadia zone hasn't had a major quake since 1700, so pressure has been building for over 300 years, making a big one more likely there.
Cites specific data (87 of 100). Names the geologic reason (plate boundaries, pressure release). Uses pattern reasoning (long quiet stretch = pressure building). Hits exactly what the standard is targeting.
Based on the data, the next major earthquake in the U.S. is most likely along the Cascadia Subduction Zone off the coast of Washington and Oregon. The data shows two patterns. First, location: 87 out of the last 100 magnitude 5+ quakes in the U.S. clustered along Pacific Coast plate boundaries. Second, frequency over time: the Cascadia zone has a recorded major rupture about every 300 to 500 years, and the last one was in January 1700. That puts it inside the window for another major event. I can't predict the exact day. The data doesn't give that. But the location and the long quiet stretch both point at Cascadia. A forecast based on this would prioritize mitigation in Seattle and Portland: earthquake-resistant retrofits, tsunami evacuation routes along the coast, and ShakeAlert coverage.
Two distinct data patterns identified (location AND frequency). Probability language used correctly. Names the limit of the forecast (no exact date). Connects the forecast to a mitigation plan, which is what the standard's "inform the development of technologies" clause is asking for. This is the macro-to-micro reasoning the standard targets.