Seismic Wave Travel Time Calculator
Introduction: why seismic wave travel-time estimates matter
In earthquake work and subsurface surveying, the hard part is often not the algebra itself; it is translating a source distance and a pair of wave speeds into an arrival-time estimate you can trust. That is what Seismic Wave Travel Time Calculator is built for. It condenses the travel-time workflow into a repeatable check: enter the distance from source to receiver, choose the wave velocities, and read a result that can be compared across scenarios.
A travel-time calculator is most helpful when it turns a seismology question into values you can inspect. The notes on this page explain the fields, units, and assumptions so the P-wave and S-wave arrivals are easier to interpret. Without that context, two people can enter the same seismic setup in different ways and end up with numbers that look inconsistent even though the formula behaved correctly.
The sections below show how to choose the inputs, what the arrival-time output means, and where the model's simplifying assumptions start to matter.
What problem does a seismic wave travel time calculator solve?
The question behind Seismic Wave Travel Time Calculator is usually how long it takes a seismic pulse to cross a known distance through Earth or through a modeled layer. In practice, that means comparing a source-to-station distance against a P-wave speed, an S-wave speed, or both, so you can estimate when each arrival should show up.
Before you start, state the seismology question in one sentence. Examples include: “When should the P wave reach the station?”, “How far apart will the P and S arrivals be?”, “What velocity gives this arrival time?”, or “Is this source distance plausible for the observed lag?” Once the question is clear, it becomes much easier to choose the right inputs.
How to use this seismic wave travel time calculator
- Start by entering Distance to Source (km) with the unit shown beside the field.
- Enter Primary Wave Velocity (km/s) with the unit shown beside the field.
- Enter Secondary Wave Velocity (km/s, optional) with the unit shown beside the field.
- Run the calculation to refresh the results panel.
- Review the output's unit, scale, and direction before comparing scenarios.
If you are comparing earthquake cases or survey lines, write down the inputs so you can reproduce the same arrival-time result later.
Inputs: how to choose distance and wave speeds for seismic arrivals
The calculator’s form collects the values that control how quickly the wavefront reaches the receiver. Many mistakes come from unit mismatches—kilometers versus meters, seconds versus minutes—or from using a speed that does not match the geologic setting. Use the following checklist as you enter your values:
- Units: confirm the unit shown next to the input and keep your measurements consistent with it.
- Ranges: if an input has a minimum or maximum, treat it as the model’s safe operating range for source distance or wave speed.
- Defaults: any prefilled values are placeholders; replace them with values from your own seismic scenario before relying on the output.
- Consistency: if two inputs describe related quantities, make sure they fit the same wave path and station geometry.
Common inputs for Seismic Wave Travel Time Calculator include:
- Distance to Source (km): the measured, quoted, or modeled source-to-station distance for the event or profile you are testing.
- Primary Wave Velocity (km/s): the P-wave speed you want to use for the crust, layer, or survey line you are evaluating.
- Secondary Wave Velocity (km/s, optional): the S-wave speed or another comparison speed for the same path.
If you are unsure about a value, it is better to begin with a conservative estimate and then run a second scenario with a faster or slower wave speed. That gives you a bracket around the P-wave and S-wave arrivals rather than a single number you might over-trust.
Seismic travel-time formulas: how the calculator turns distance and velocity into arrivals
For a seismic travel-time estimate, the workflow is straightforward: gather the distance, apply the wave speed, and report the arrival in seconds. Even when the geology is more complicated than a single homogeneous layer, the calculator still reduces the problem to a consistent sequence of unit handling and division.
The travel-time result R can be written as a function of the inputs x1 … xn:
A very common special case is a path total that combines the key parts of a seismic scenario after each one is scaled by its own factor:
Here, wi can represent a path correction, a scaling factor, or a unit conversion that adjusts one part of the seismic travel-time model. That is how calculators express “this segment matters more” or “this input needs a correction before it is compared.” When you read the result, ask whether doubling one major input changes the travel time in the direction and proportion you expect; if it does not, revisit the units and assumptions.
Worked example (step-by-step): a P-wave and S-wave over the same path
Worked examples are a quick way to confirm that a seismic travel-time setup makes sense before you trust the arrival times. For illustration, suppose you enter the following three values:
- Distance to Source (km): 1
- Primary Wave Velocity (km/s): 2
- Secondary Wave Velocity (km/s, optional): 3
A simple check sum for the example values is:
Sanity-check total: 1 + 2 + 3 = 6
After you click calculate, compare the P-wave arrival and, if you entered one, the S-wave arrival with your expectation. If the numbers look far off, check whether you entered a distance in kilometers but a speed in meters per second, or whether the optional secondary velocity is actually a value from a different layer. If the result is in the right ballpark, change one input at a time to see how the arrival gap moves.
Comparison table: sensitivity to source distance in a seismic run
The table below changes only Distance to Source (km) while keeping the other example values constant. The comparison value in each row is a simple proxy for how the distance change affects the seismic timing result at a glance.
| Scenario | Distance to Source (km) | Other inputs | Scenario total (comparison metric) | Interpretation |
|---|---|---|---|---|
| Conservative (-20%) | 0.8 | Unchanged | 5.8 | A shorter path typically reduces the arrival time in a simple velocity model. |
| Baseline | 1 | Unchanged | 6 | This is the reference P-wave and S-wave case to compare against the other scenarios. |
| Aggressive (+20%) | 1.2 | Unchanged | 6.2 | A longer path usually increases the arrival time and widens the lag between arrivals. |
Use the calculator's actual result panel with shorter, baseline, and longer source distances to see how much the P-wave and S-wave arrivals separate when the geometry changes.
How to interpret seismic arrival times
The result panel is meant to translate the source distance and wave speed into arrival times you can compare directly, not into a pile of intermediate seismology terms. When you get a number, ask three questions: (1) does the unit match the moment you care about? (2) does the scale look plausible for the distance and velocities you entered? (3) if you tweak a major input, does the output move in the direction seismic intuition predicts? If you can answer “yes” to all three, you can treat the estimate as a useful first pass.
When relevant, copying the summary gives you a record of the source distance, P-wave speed, S-wave speed, and the resulting arrival gap. Saving that snapshot helps you compare nearby earthquakes, test alternate layer speeds, and explain the scenario to a teammate without retyping the inputs.
Limitations and assumptions for seismic travel-time estimates
No seismic travel-time calculator can capture every layer, reflection, or local anomaly, so the result should be treated as a practical estimate rather than a full earthquake model. Keep these common limitations in mind:
- Input interpretation: read each field literally; a station distance is not the same as a path length through layered rock.
- Unit conversions: convert source data carefully before entering values.
- Linearity: quick estimators often assume constant wave speed; real earth materials can slow, speed up, or bend waves.
- Rounding: displayed arrival times are rounded to a practical precision, so tiny differences from hand calculations are normal.
- Missing factors: fault geometry, depth, anisotropy, and scattered arrivals may not be represented.
If you rely on the output for hazard analysis, field planning, safety decisions, or teaching, treat it as a first estimate and verify it against authoritative seismic data or a more detailed model. The value of the calculator is that it makes your assumptions visible: you can see which source distance and wave speeds drive the arrival time, adjust them transparently, and explain the logic clearly.
Echo Runner Mini-Game
Ride the seismic front and stamp arrivals at just the right moment. Tap, click, or press Space as the P and S waves hit the station line—the tighter your timing, the more insight you gain.