Smartphone Lightning Localization Project

Smartphone Lightning Localization Project

ISEF Category: Earth and Environmental Sciences

Ready to Turn This Idea Into a Real Project?

This guide was put together with the help of AI research tools to give you a solid starting point. But a competitive science fair project lives in the details: refining your research question, fine-tuning your variables, analyzing your data, and presenting your findings like a seasoned scientist.

For next steps tailored to your interests, skill level, and timeline, work one-on-one with a MehtA+ mentor. Learn more about MehtA+ Science & Engineering Research Mentorship →

Subcategory: Atmospheric Science  ·  Difficulty: Advanced  ·  Setup: Home Setup  ·  Time: Full Year

The Hook

A lightning flash reaches you before the thunder does, and that gap is a clue. If several phones record that same thunder, you can triangulate where the strike happened. Your job is to turn noisy phone audio into a map. Then you can test how close your map gets to real lightning networks.

What Is It?

This project asks you to estimate where a lightning strike happened by using the time it takes thunder to reach different smartphones. Light travels too fast to help much here, but sound moves slowly enough that tiny timing differences matter. If one phone hears thunder before another, the strike was probably closer to the first phone. That idea is called time-of-arrival localization.

Think of it like finding a friend in a dark room by hearing where their footsteps came from. One sound by itself only gives you a rough idea. Several sounds from different places let you narrow the location much more. A particle filter is a computer method that tests many possible strike locations, then keeps the ones that fit the phone timing data best.

Why This Is a Good Topic

This topic works well because you can test a real sensing problem with data you can collect or simulate yourself. It connects to weather safety, storm monitoring, and low-cost citizen science. You can study timing error, phone placement, wind and terrain effects, and how a geolocation algorithm performs when the inputs are messy. That gives you room to ask a real research question, not just build a demo.

Research Questions

  • How does the number of participating smartphones affect lightning location accuracy?
  • What is the effect of microphone timing error on particle-filter geolocation results?
  • Does using only thunder time-of-arrival data produce usable strike locations compared with open lightning records?
  • To what extent does phone spacing improve or hurt localization accuracy?
  • Which particle-filter settings give the lowest average distance error against NLDN or Blitzortung data?
  • How does terrain or urban noise change the quality of thunder timing data?

Basic Materials

  • Smartphone with microphone access and audio recording app.
  • Second smartphone or laptop for a second recording station.
  • Tripod or stable surface for each phone.
  • GPS app or phone location services for station coordinates.
  • Spreadsheet software for timestamp tracking and error calculation.
  • Map software or a simple plotting tool for visualizing station positions and estimated strike locations.
  • Notebook for recording storm conditions, phone placement, and noise sources.

Advanced Materials

  • Laptop or desktop computer for running the particle filter.
  • Python with scientific libraries for data cleaning and localization.
  • Audio editing software for checking thunder onset times.
  • GPS receiver or high-accuracy phone GNSS logs for station coordinates.
  • Reference lightning data from NLDN or Blitzortung open archives.
  • GIS software for mapping strike estimates, station geometry, and error fields.
  • External microphone or audio interface for higher-quality timing capture.

Software & Tools

  • Python: Cleans timestamps, runs the particle filter, and computes location error.
  • Jupyter Notebook: Keeps your code, plots, and notes together in one place.
  • ImageJ: Can help you inspect plotted waveforms or exported screenshots when you compare timing markers.
  • QGIS: Maps station locations, predicted strike points, and reference lightning data.
  • Google Sheets: Organizes station coordinates, thunder times, and trial-by-trial error calculations.

Experiment Steps

  1. Define the exact timing signal you will measure, then decide whether you will use live field recordings, archived audio, or simulated thunder timing data.
  2. Choose the location model you will test, then decide how many phone stations, and what geometry, your setup needs.
  3. Build a reference dataset by pairing your phone-based estimates with open lightning records from NLDN or Blitzortung.
  4. Design a particle-filter workflow that converts timing differences into a strike location estimate, then set the error metric you will judge.
  5. Plan controls for noise, phone model differences, GPS uncertainty, and missed thunder detections so you can separate signal from error.
  6. Compare alternative setups, then decide which configuration gives the best tradeoff between accuracy, data quality, and feasibility.

Common Pitfalls

  • Using thunder peak time instead of thunder onset time, which shifts every distance estimate.
  • Mixing phone clocks that are not synchronized, which breaks the time-of-arrival calculation.
  • Recording too close to reflections from buildings or hills, which adds false echoes to the timing data.
  • Treating GPS phone locations as exact, which can create large errors in your strike map.
  • Comparing your estimates to lightning network data without matching the same flash or time window, which makes validation meaningless.

What Makes This Competitive

A stronger project will do more than draw a few strike points on a map. You can push it by testing multiple timing methods, comparing several phone layouts, and quantifying uncertainty instead of only reporting average error. A careful validation against open lightning records makes the project much stronger. If you also study when the model fails, you will sound like a real researcher, not just a coder.

Project Variations

  • Use audio from a fixed backyard sensor network instead of phones, then compare whether better placement beats better hardware.
  • Focus on urban storms, then test how building reflections change thunder timing and localization error.
  • Swap the particle filter for a simpler triangulation method, then compare which model handles noisy phone data better.

Learn More

  • NOAA National Severe Storms Laboratory: Search for lightning safety, thunder, and storm science background pages.
  • NASA Earth Observatory: Search for articles on lightning, thunderstorms, and remote sensing of storms.
  • NLDN documentation and lightning climatology papers: Search PubMed and journal databases for studies that use lightning network validation.
  • Blitzortung network resources: Read about community lightning detection and open strike maps on the project site and related forum posts.
  • MIT OpenCourseWare, Signals and Systems: Use the course materials to review time-delay estimation and filtering ideas.
  • Bulletin of the American Meteorological Society: Search for review articles on lightning detection networks and localization methods.

For next steps tailored to your interests, skill level, and timeline, work one-on-one with a MehtA+ mentor. Learn more about MehtA+ Science & Engineering Research Mentorship →

To discover more projects, visit the MehtA+ Science Fair Project Discovery Hub​ →

Shopping Cart