Ultrasonic Rail Testing Cost: What Drives It and How to Cut It

Ultrasonic rail testing cost is set mainly by track miles, the test interval that 49 CFR 213.237(c) requires (370 days or 30 MGT on Class 4–5 track), test days and mobilization. One public contract award gives a reference point: San Diego MTS's 2019 bid priced testing at $212.43 per track mile, or $3,100.73 per extra test day.

That figure is one transit system's bid, not a market rate. This guide shows every public price we could cite, with its date and scope. It then sets out a cost-estimating method you can run on your own network, and five ways to cut the bill without cutting compliance.

What do public contracts show about ultrasonic rail testing cost?

Public board records give a few hard numbers, but they cover very different scopes, so none of them is a price list. Transit agencies publish their rail flaw testing awards in board packets. We searched board reports, contract awards and FRA rulemaking documents in October 2026 and found the figures below.

Sources: San Diego MTS board agenda, Dec 13, 2018, item 18; BART Executive Decision Document, RFP 6M3750; MTA LIRR staff summary, contract 397260RFP; MTA NYCT procurements, Sept 2022; 79 FR 4234, Jan 24, 2014 (govinfo).

Several points stand out. The San Diego bid form says its pricing was "based on given work windows and historical production test speeds", so track access is built into the per-mile rate.

BART's staff report says the winning price came in under the engineer's estimate partly because the firm was local, "saving travel and lodging costs". In San Diego, the single bidder's first price was $205,531.38, and it fell to $145,629.12 after negotiation.

We found no public bid tabulation that gives a per-mile price for a short line or an industrial track owner. FRA's $2,000-a-day figure is twelve years old and was written to show the rule's small-business impact, so treat it as a floor, not a budget. If you need a current number, the method below and two or three written quotes are more reliable than any published average.

Key takeaway: the only cited unit rates are from 2019 and 2014; use them to check a quote's structure, not as today's price.

What drives the cost of rail flaw testing?

Rail flaw testing cost is mostly time: test days on the rail, travel days to reach it, and hours spent proving suspect indications. Everything else, from track class to reporting format, changes how many of those days and hours you buy.

Track miles and the 213.237 interval set the base workload. The production rate decides how many days that workload takes. Mobilization is a fixed charge per visit, so it hurts most on small networks.

The owner pays some costs that never appear on the contractor's invoice. On FRA track, the crew is a group of roadway workers under 49 CFR Part 214, and a moving test vehicle normally needs working limits set up by a qualified roadway worker in charge. On rail transit, 49 CFR Part 671 and the agency's own RWP program apply. Either way, that protection is owner staff time on every test day.

Key takeaway: count test days, travel days, verification hours and your own RWP hours; the quote alone shows only part of the cost.

How do 213.237 intervals change the annual bill?

The test interval decides how many times a year you pay for a visit, and 49 CFR 213.237(c) sets it by track class and traffic. For FRA-regulated track, the rule reads:

"Internal rail inspections on Class 4 and 5 track, or Class 3 track with regularly-scheduled passenger trains or that is a hazardous materials route, shall not exceed a time interval of 370 days between inspections or a tonnage interval of 30 million gross tons (mgt) between inspections, whichever is shorter." — 49 CFR 213.237(c) on eCFR

Other Class 3 track must be tested at least once each calendar year, with no more than 18 months between tests, or every 30 MGT, whichever interval is longer, and never more than 5 years apart. The rule sets no internal test interval for Class 1 and 2 track. Class 6 and higher track falls under 213.339, at least twice a year with 120 days or more between tests.

The 274-day figure is 30 ÷ 40 × 365. The 7.5 years is 30 MGT ÷ 4 MGT a year. These traffic levels are examples, not data for any real line.

Rail transit not connected to the general railroad system is outside Part 213 under 213.3(b)(3). Its interval comes from the agency's own standards and its state safety oversight agency. BART's 2025 staff report, for example, says California Public Utilities Commission requirements and District standards require testing "twice per year". San Diego's light rail, which shares track with a freight railroad, tests its Blue Line four times a year by the agency's choice.

The interval is the minimum. An owner may test more often on older rail or where service failures have occurred, and how often rail must be tested explains the tonnage-versus-calendar calculation in more detail.

Key takeaway: a line that crosses 30 MGT in nine months costs about a third more a year than the same line at 20 MGT.

How do you estimate the cost for your own track?

Estimate it from the bottom up: tests per year, test days per visit, mobilization, verification and your own protection hours. Each line uses an input you can check or replace with a quote.

1. List segments, miles and class. Use track miles (each track counted separately), not route miles.
2. Set tests per year for each segment under 213.237(c), or under your transit standard.
3. Estimate test days. Divide the miles per visit by an assumed production rate in miles per test day. The rate depends on access windows, rail condition and test type, so ask bidders for their historical rate on similar track.
4. Add mobilization. Count the travel days to and from the site for each visit.
5. Add suspect-verification time. Stop-and-verify includes hand verification within the test day, but heavy defect counts can push crews into overtime. Continuous testing moves verification to a separate visit.
6. Add owner-borne RWP and flagging. Count the hours your roadway worker in charge, pilot or flag staff spend on each test day, including briefing and travel.
7. Add reporting. Check whether reports, data files and electronic records under 213.241 are included or billed.
8. Add stand-by and contingency. Weather days and lost windows are often billed at the test-day rate.

Worked example: a 70-mile short line

Every input below is an assumption for illustration. The contractor rates are San Diego MTS's 2019 contract rates, the only public unit rates we found, used here to show the arithmetic. Replace them with your own quotes.

Case 1: test both segments together once a year (70 miles).

Case 2: test Segment A alone each year and leave Segment B at the 5-year legal minimum (45 miles).

The difference between the two cases is exactly one test day, $3,100.73, for 25 more miles. That is about $124 per added mile, against $359 per mile when Segment A is tested alone. Mobilization is the reason: in Case 2 it is more than a third of the bill ($5,694.16 of $16,159.12).

Two checks keep the example honest. The Case 1 result, $275 per track mile, sits above San Diego's $212.43 because this example pays mobilization separately on a small job, while the MTS bid carried a $0 mobilization line on 192 miles. And if Segment A carried 40 MGT instead of 20, tonnage would govern, the test would fall due about every 274 days, and some years would need a second visit with a second mobilization.

Key takeaway: on small networks, the fixed cost of each visit drives the per-mile price more than the miles do.

How can you cut cost without cutting compliance?

Buy fewer, longer, cleaner visits: combine segments, grind before you test, match the test type to the network, protect the access window and keep records that let you schedule to the real limit. None of these reduces how often the rule requires a valid search.

Combine segments into one mobilization

Combining segments spreads one mobilization over more miles, as the worked example shows. Line up the due dates so that segments with different intervals fall due in the same visit. The test must still be within each segment's 370-day or 30 MGT limit, so pull the earlier date forward rather than letting a later one slip.

Owners with track in more than one place can share a visit with a neighboring owner or with an industrial customer's spur. Travel days are billed per trip, not per owner.

Coordinate testing with rail grinding

Grind first, then test. Rolling contact fatigue and shelling block the sound beam, and a search the operator can't complete is not a valid search under 213.237(g). That length of rail must be retested, run at no more than 25 mph, or replaced before the deadline, as 213.237(h) sets out.

Research supports the order. In TTCI field work reported in TD20-002, corrective grinding restored a valid ultrasonic test at 68 of 88 exception locations (77%), and at all of them where at least 0.060 in. of metal was removed. Grinding itself earns no 213.237 credit; it only makes the test succeed. See rail grinding and its effect on ultrasonic inspection for the details.

Choose continuous or stop-and-verify on purpose

Under 49 CFR 213.240, an owner may use continuous testing to satisfy 213.237. The vehicle runs without stopping, and every suspect must then be field-verified by a qualified person within 84 hours, or 36 hours for suspects that would need remedial action A, A2 or B. In stop-and-verify testing, the crew verifies each indication on the spot, and 213.113(b) applies.

The cost trade is between vehicle time and verification visits. Continuous testing covers more miles per day but needs a second crew or the owner's own staff to verify suspects inside the windows. Stop-and-verify is slower but finishes each mile in one pass, which often suits short lines and transit systems. FRA's 2020 rule preamble describes stop-and-verify testing as "normally not exceeding 20 miles per hour", while a continuous system "runs non-stop along a designated route" (85 FR 63362). Our comparison of continuous vs stop-and-verify rail testing sets out the rule differences.

Use the access window fully

Production rate depends on uninterrupted time on the rail. A crew that gets a 6-hour window but loses 2 hours to late track authority has paid for a full day and tested two-thirds of one. Book the window, the roadway worker in charge and the authority in advance, and agree what happens if the window is cancelled.

Ask bidders to price stand-by days and weather days explicitly, as San Diego's Exhibit A did. Then you can compare the cost of a lost window with the cost of adding staff to protect it.

Keep records that let you schedule to the real limit

Good records save money in three ways. Tonnage records show whether days or MGT governs each segment, so you test when the rule requires and not earlier by guesswork. The 213.241 records of untested track, under (c)(6), show where no-tests recur, so you can grind or clean those spots before the next visit.

Records also make the RFP accurate. Bidders price risk, and a scope with exact track miles, special trackwork counts, window lengths and last year's defect and no-test counts gets tighter prices. Our RFP manual for ultrasonic testing lists what to include.

Key takeaway: every lever here buys back time on the rail; none of them stretches the interval.

What does the technician's qualification add to the price?

Qualified people are a fixed part of the price, because federal rules and the employer's written practice both set minimums. Under 49 CFR 213.238, the operator of rail flaw detection equipment must have a documented training program, written authorization from the employer and at least 160 hours of supervised experience on the equipment. FRA doesn't certify the operator; the employer qualifies them.

Rail testing providers may also certify their technicians under ASNT's SNT-TC-1A, which is a recommended practice: the employer, not ASNT, certifies. The original article's figures (80–120 classroom hours and 100–200 practical hours for Level II) don't match it.

Recent editions of SNT-TC-1A are commonly reported to recommend about 40 hours of UT training for Level I and 40 more for Level II, so about 80 hours in total, for a high-school graduate. Experience is reported as about 630 hours in UT for Level II, with about 1,200 hours of total NDT experience. Some written practices count the Level I hours (about 210 in UT) on top, giving 840 hours. These values come from secondary sources and vary with education and edition, so check the edition your provider's written practice cites.

Higher qualification shows up in the price as a higher day rate, but it lowers other costs. An experienced operator calls fewer false suspects, which cuts verification time, and documents untested rail correctly, which avoids invalid-search surprises at audit.

Key takeaway: ask for the 213.238 qualification records and the written practice, not just a certificate.

How does rail flaw testing actually work, and why does it matter for price?

Rail flaw testing uses pulse-echo ultrasound from the rail head, and the equipment needed to do it drives the day rate. Probes at several angles, typically 0°, 37–45° and 70°, send pulses into the rail through a wheel, sled or contact probe. The same probes receive the echoes from cracks, holes and the rail base.

Through-transmission, with a transmitter on one side of the part and a receiver on the other, isn't used for rail in track. The rail can be reached only from the head, so the 0° probe reads the loss of the base echo as a pulse-echo signal. The original article presented through-transmission as one of two rail methods, which is wrong.

FRA's 2014 preamble describes the coverage: the waves "normally scan the entire rail head and web, as well as the portion of the base directly beneath the web" (79 FR 4234, p. 4237). The same preamble describes four processes: portable testing at walking pace, start/stop testing, a chase-car process and continuous testing.

Phased array UT is mainly used in rail for verification and research, not as routine test-vehicle output. If a quote prices it, ask what it adds beyond the 213.237 search.

Key takeaway: the test process, not the physics, sets the miles per day and therefore the day-rate value.

What can't a cost estimate or a rail test tell you?

A cost estimate can't fix the price of defects found, and a rail test can't find every defect. Both limits belong in the budget.

• Remedial work isn't in the testing price. Each verified defect triggers a 213.113 remedial action, from joint bars to rail replacement. Those costs depend on what the test finds.
• No test finds everything. TTCI reported in 2016 that conventional ultrasonic inspection finds "about 90 percent" of flaws during periodic inspection (TD16-030). San Diego MTS's staff report states it plainly: "no testing program will be able to identify every defect."
• Coverage stops short of most of the base. Vehicle testing covers the head, the web and the base under the web, so field welds may need hand UT of the base flange.
• Surface conditions mask defects. Shells and head checks mainly mask detail fractures, because that is where those defects start. Grinding helps, but some no-tests remain.
• Old public rates age fast. The 2019 and 2014 figures here predate several years of wage and fuel inflation. Use them for structure only.
• Scopes differ. The MTA award bundles joint bar and eddy current inspection, and the NYCT contract puts the contractor's system on the agency's own cars. Per-mile comparisons across those scopes mislead.
• Liability allocation affects price. San Diego's report notes that pricing reflected the agency indemnifying the testing company, so contract terms change bids.

The estimate also leaves out the cost of an invalid search caught late. Under 213.237(h), rail that couldn't be validly searched must be retested, held to 25 mph or replaced before the deadline, and each option has its own cost.

Key takeaway: budget for defects found and no-tests, not just for the test itself.

How EMA Industries applies this

EMA Industries provides ultrasonic rail flaw testing for transit agencies, short lines and industrial track owners. It is based in Southern California and mobilizes nationwide, and also offers rail weld inspection and NDT Level III services. Send your track miles, track classes, annual tonnage, access windows and last test date through the contact page, and EMA Industries will prepare a quote with test days, mobilization and verification itemized as in the method above.

For more on choosing a provider, see ultrasonic rail testing services in the USA and the rail inspection RFP guide. The rule itself is explained in 49 CFR 213.237 rail flaw detection requirements.

Frequently asked questions

How much does ultrasonic rail testing cost per mile?

Public figures are scarce. San Diego MTS's 2019 contract priced light rail testing at $212.43 per track mile on about 192 track miles, with extra test days at $3,100.73. FRA estimated in 2014 that a small railroad could rent a test car for about $2,000 a day. Current prices depend on mobilization, access windows and scope, so get written quotes.

Is a per-mile price or a day rate better for the owner?

A per-mile price moves production risk to the contractor, which suits a well-defined network with reliable windows. A day rate suits short or irregular scopes, but the owner then carries the risk of slow production and lost windows. Contracts can combine both, as San Diego's did: a per-mile base with day, overtime, mobilization and stand-by rates for extra work.

Does rail grinding count toward the 213.237 test?

Grinding doesn't count; Part 213 gives it no credit. It can make the next test succeed, though, by removing the surface fatigue that blocks the beam and causes invalid searches. Schedule grinding before the test, not after.

How many hours does a UT Level II technician need?

Under SNT-TC-1A, recent editions are commonly reported to recommend about 80 hours of UT training in total and about 630 hours of UT experience for Level II, with the exact values set by the employer's written practice. Separately, a rail flaw equipment operator needs at least 160 hours of supervised experience under 49 CFR 213.238.

Can we save money by testing other Class 3 track less often?

Other Class 3 track can legally go up to 5 years between tests at low tonnage. An owner may still choose to test it yearly because, once the crew is on site, the added miles cost only extra test days, about $124 a mile in our worked example. Older rail or a history of service failures is another reason to test more often than the minimum.

Sources

• 49 CFR 213.237, Inspection of rail (eCFR); text read on Cornell LII, October 2026
• 49 CFR 213.238, Qualified operator (eCFR)
• 49 CFR 213.240, Continuous rail testing (eCFR)
• 49 CFR 213.241, Inspection records (eCFR)
• 49 CFR 213.339, Inspection of rail in service, Class 6+ (eCFR)
• 49 CFR 213.3, Application (eCFR)
• 49 CFR Part 214, Railroad Workplace Safety (eCFR) and Part 671, Rail Transit Roadway Worker Protection (eCFR)
• FRA, Track Safety Standards; Improving Rail Integrity, final rule, 79 FR 4234, Jan 24, 2014 (govinfo PDF)
• FRA, Rail Integrity and Track Safety Standards, final rule, 85 FR 63362, Oct 7, 2020 (govinfo)
• San Diego Metropolitan Transit System, Board of Directors agenda, Dec 13, 2018, item 18, Ultrasonic Rail Testing Services – Contract Award, with bid forms and Exhibit A (PDF)
• San Francisco Bay Area Rapid Transit District, Executive Decision Document, Ultrasonic Rail Flaw Detection Testing Services, Agreement 6M3750, board agenda June 26, 2025 (Legistar)
• MTA Long Island Rail Road, staff summary, Rail Flaw Testing and Joint Bar Inspection Services for LIRR/MNR, contract 397260RFP, 2023 (PDF)
• MTA New York City Transit, procurement staff summary, Sept 2022, ultrasonic internal rail flaw inspections (PDF)
• TTCI, TD20-002, rail grinding and ultrasonic test exceptions (PDF)
• TTCI, TD16-030, Witte and Poudel, High-Speed Rail Flaw Detection Using Phased Array Ultrasonics, July 2016 (PDF)
• ASNT, Standards and recommended practices: SNT-TC-1A and CP-189