One of the quiet superpowers of an ultrasonic gas meter is that it can grade its own homework. Because the meter measures how fast sound travels through the gas, it can compare that measured speed of sound against a theoretical value calculated from the gas composition, and any disagreement is an early warning that something is wrong. This guide explains how an AGA 9 ultrasonic meter derives its measured speed of sound, how that is compared against the AGA 10 calculated value as a live health check, and what a growing deviation is telling an operator.
Ultrasonic Meter Speed-of-Sound Check in one line: A speed-of-sound (SOS) check is a diagnostic that compares the speed of sound an ultrasonic meter measures in the flowing gas against the theoretical speed of sound calculated from the gas composition using AGA Report No. 10. When the meter is healthy, the gas analysis is correct, and no liquids are present, the two values track closely. A growing deviation between measured and calculated SOS signals a problem - composition error, transducer fouling, or liquid in the line - which is why it is one of the most valued diagnostics for custody ultrasonic measurement.
An ultrasonic flow meter works by firing acoustic pulses between pairs of transducers set at an angle across the pipe and timing how long each pulse takes to travel with the flow and against it. The difference in those transit times gives the gas velocity, which the meter integrates across its measurement paths to compute flow. But the same transit-time measurements also yield the speed of sound in the gas directly, because the average of the upstream and downstream travel times over the known path length is a measurement of how fast sound itself moves through that gas, independent of the flow.
This is a genuine, independently measured physical quantity that falls out of the meter's normal operation at no extra cost. A multipath AGA 9 meter measures speed of sound on each acoustic path, so it produces several SOS readings that should all agree with one another when the meter is healthy and the gas is uniform. That per-path agreement is itself a first diagnostic: if one path reports a speed of sound noticeably different from its neighbors, that path may be fouled, obstructed, or have a failing transducer while the others remain trustworthy.
The measured speed of sound only becomes a health check when there is something to compare it against, and that reference comes from AGA Report No. 10, which calculates the speed of sound in natural gas from its composition, pressure, and temperature. Feeding the gas chromatograph analysis, the line pressure, and the flowing temperature into the AGA 10 method gives a theoretical speed of sound - the value the gas physically should exhibit. The meter then compares its own measured speed of sound against this calculated value, and the difference between them is the SOS deviation that operators watch.
When everything is right, the measured and calculated values agree to within a small tolerance, and that agreement is a strong, live confirmation that the meter, the pressure and temperature inputs, and the gas analysis are all mutually consistent. A persistent or growing gap points to one of a few culprits. A composition error - a stale or wrong GC analysis - shifts the calculated value away from the true one, so the deviation is really telling you the analysis is off. Transducer fouling or buildup on the meter internals distorts the measured value. And liquids carried into a meter meant for dry gas change the acoustic behavior and can move the measured speed of sound noticeably, flagging a wet-gas condition the volume alone might not reveal.
This self-checking ability is a major reason ultrasonic meters are favored for custody transfer: unlike a device that simply reports a number and trusts you to believe it, a USM continuously offers evidence that its number is right. Alongside speed-of-sound agreement, operators also watch related diagnostics such as per-path velocity profile, signal gain, and performance, but the SOS comparison is often the headline indicator because it ties together the meter, the process conditions, and the gas analysis in a single, interpretable figure. A stable, near-zero deviation is a clean bill of health.
In a cloud SCADA platform such as Merobix, the measured and calculated speed of sound, and the deviation between them, can be trended continuously and alarmed on tolerance, so a slow drift becomes visible long before it corrupts a month of custody data. For a remote metering skid where nobody is standing next to the meter, that matters: an operator watching the SOS deviation curve can tell the difference between a genuine meter problem, a GC analysis that has gone stale, and liquids arriving in the line, and can dispatch the right response. Catching a rising deviation early is what turns a potential measurement dispute into a routine maintenance ticket.
It tells you whether the meter's measurement is consistent with the gas it is measuring. The meter compares the speed of sound it measures against a theoretical value calculated from gas composition, pressure, and temperature using AGA 10. Close agreement confirms the meter and its inputs are healthy, while a growing deviation warns of composition error, transducer fouling, or liquids.
Three common causes are a wrong or stale gas composition, which throws off the calculated reference value; fouling or buildup on the transducers, which distorts the measured value; and liquids entering a dry-gas meter, which changes the acoustic behavior. Watching how the deviation behaves, and alongside other diagnostics, helps distinguish which of these is happening.
Because it lets the meter continuously verify its own health rather than just reporting a number to be trusted. For custody transfer, where measurement equals money, having a live, independent check that the meter, the process conditions, and the gas analysis all agree provides confidence in the billed volume and catches problems early, often before they affect any settlement.
This page references the standards, specifications, and official documentation published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.