ATCC vs Manual Traffic Count: Why Video-AI Wins on Accuracy, Speed and Evidence

The Three ATCC Methods Used in India Today

An ATCC (Automatic Traffic Counter Classifier) survey records and classifies every vehicle passing a section continuously for 7 days × 24 hours per IRC SP 19. Three methods are commonly used on Indian highway projects, and they are not interchangeable: each has distinct strengths and known failure modes. Choosing the wrong one for a given project produces traffic data that may pass internal QA but fail downstream — in IRC 37 MSA computation, in arbitration, or in toll-revenue audit.

1. Manual classified count

Trained surveyors at the roadside classify each passing vehicle into IRC categories using handheld tally counters, log volumes hourly, and rotate shifts every 8 hours over the 7-day window. This is the IRC reference method — every other approach is benchmarked against it. Strengths: highest classification depth (a trained eye can distinguish a 4-axle MAV from a 5-axle MAV at 80 km/h on a clear day, while no automated method does this perfectly). Weaknesses: classifier fatigue, cost (≈ 6 surveyors per station for 7-day continuous coverage), and the practical near-impossibility of running multiple stations simultaneously across a long corridor.

2. Pneumatic-tube ATCC

Heavy-duty rubber tubes are stretched across the carriageway and connected to a roadside data logger. Each axle pass triggers a pressure pulse; the logger records timestamp, axle spacing, and speed. Vehicles are then classified by axle count and wheelbase pattern into a simplified scheme — typically 5 to 7 classes (cars, LCV, 2-axle, 3-axle, MAV, bus). Strengths: cheap per station, weather-resistant, works at night without lighting. Weaknesses: cannot visually distinguish vehicle types with the same axle signature (a mini-bus and an LCV-passenger both have 2 axles and similar wheelbases — pneumatic tubes record them identically), tubes degrade after ~10,000 vehicle passes, and tubes can be damaged by tracked agricultural vehicles or pulled out of position by aggressive starts at signalised intersections.

3. Video-AI ATCC

High-resolution roadside cameras record continuously for the 7-day window. A deep-learning classifier processes each frame in real-time on the edge device or in batch on the cloud, classifying every vehicle into the full IRC SP 19 17-class scheme using visual signature — length, height, body shape, axle count, headlight pattern. Strengths: matches manual classification depth (full 17 classes), no fatigue, no shift-change drift, processes parallel multi-station deployments without proportionally increasing field staff, and produces a permanent video evidence trail. Weaknesses: requires unobstructed sight-line to the carriageway, can degrade in heavy rain or fog (mitigated by IR night-vision and weather-sealed housings), and the AI model needs to be trained on Indian-fleet imagery — a generic Western fleet classifier will misclassify auto-rickshaws, ADVs, tractor-trailers and Indian-spec MAVs systematically.

Head-to-Head: Where Each Method Wins or Fails

Why the Accuracy Difference Matters for IRC 37 MSA

The classification accuracy difference is not academic — it directly propagates into the IRC 37 design-traffic computation. Vehicle Damage Factor (VDF) values vary substantially across the 17 classes (per IRC 37 Table 2, a 2-axle truck has VDF ≈ 1.5–2.5, a 5-axle MAV has VDF ≈ 4.5–5.5, and a 7+-axle MAV can exceed 6.0). If a pneumatic-tube ATCC pools 4-, 5-, 6- and 7+-axle MAVs into a single 'MAV' bucket and applies an average VDF, the MSA computation underestimates damage when overloaded heavy MAVs dominate the fleet — and overestimates damage when the fleet is predominantly 4-axle. Either error pushes the IRC 37 pavement design away from the actual loading reality. NHAI scrutiny and arbitration history have repeatedly flagged this exact issue when DPR design-traffic projections diverge from observed performance.

Video-AI ATCC, by classifying into the full 17-class scheme prescribed by IRC SP 19, allows VDF to be computed correctly per class — which is the methodology IRC 37 actually assumes. The combination of accurate classification and paired axle load survey data is what produces a defensible MSA value for tender, arbitration, or audit.

The Fatigue Drift Problem in Manual Counts

Published transportation-research studies on manual classified counts in tropical climates show a consistent pattern: accuracy holds at 90%+ for the first 4 hours of a shift, drifts to 85% by hour 8, and drops to 75–80% in hours 16–24 of a continuous shift. The drop is highest for fast-moving traffic, mixed fleet streams (where the surveyor has to make rapid 17-way classification decisions on every vehicle), and night-time conditions where tail-light signature is the only available classification input. Even with shift rotations every 8 hours, the inter-shift handover introduces classification drift between surveyors with different visual judgment thresholds for borderline cases — a 'mini-bus' to one surveyor is an 'LCV-passenger' to another.

AI classifiers do not fatigue and do not have inter-shift drift. The same model processes every frame uniformly across the 7-day window. The only drift source is environmental — rain spatter on the lens, sun glare at low-angle hours, occasional pedestrian or animal in frame — and these are detectable by the model itself (low-confidence frames are flagged for human review). Independent academic benchmarks of Indian-fleet-trained vehicle classifiers consistently report 94-97% per-class accuracy on the IRC SP 19 17-class scheme.

The Evidence Trail Problem

ATCC data is contested more often than most consultants expect. Three contexts where the evidence trail decides the dispute: (1) toll-revenue arbitration, where a concessionaire's actual revenue diverges from the DPR projection and the underlying ATCC count comes under independent re-verification; (2) IRC 37 design adequacy disputes, where premature pavement failure triggers a contractor-vs-authority arbitration and the DPR's design-traffic input is challenged; and (3) BoT/HAM concession monitoring, where annual ATCC counts feed minimum-traffic-guarantee calculations and the concessionaire or authority can dispute the count. In all three, the question becomes: can you re-verify the count independently?

Manual counts produce tally sheets — defensible, but only if the surveyors are available to testify and the sheets have not been tampered with. Pneumatic-tube counts produce a logger file with axle records — re-verifiable as data, but no visual basis for the classification decision. Video-AI ATCC produces a per-vehicle frame archive: the actual vehicle that was counted is visible, and any independent reviewer (auditor, arbitrator, opposing party's expert) can re-classify the same frame and reproduce the result. NKMPV delivers the full 7-day unedited video footage on hand-over media as part of every video-AI ATCC engagement — meaning the count itself can be independently audited at any future date.

When to Use Each Method

Manual classified count: short-duration (1-day) counts, low-budget studies on rural ODR/MDR roads where the IRC SP 19 17-class precision is not required, or as the validation ground-truth sample for an AI-based count (typically a 10% stratified sample). Also the only practical method for turning movement counts at very small intersections where camera-mounting is impractical.

Pneumatic-tube ATCC: highway sections where (a) classification depth beyond axle-count is genuinely not needed (e.g., capacity analysis where total volume matters more than fleet composition), (b) camera sight-lines are obstructed by trees or terrain, or (c) the survey budget genuinely cannot accommodate video-AI deployment. As a backup redundancy alongside primary video-AI, pneumatic tubes provide independent axle confirmation.

Video-AI ATCC: the default choice for any NHAI DPR, BoT/HAM concession, or arbitration-defensible count. The combination of full 17-class compliance, sustained accuracy, parallel scalability, and evidence trail makes it the method that holds up at every downstream stage — design, audit, dispute. The only contexts where it is unsuitable are (a) physical sight-line obstruction (rare on highways, common in dense urban contexts), and (b) projects with a hard pneumatic-tube specification in the contract (some legacy NHAI tender documents still specify pneumatic-tube — a clarification request usually resolves this).

IRC SP 19 Compliance Requirements All Methods Must Meet

Whichever method is chosen, IRC SP 19 imposes minimum requirements that NHAI DPR-acceptance depends on: 7-day continuous coverage (no shorter sample is acceptable for AADT estimation), 24-hour-per-day recording (no daytime-only counts), classification into the 17-class scheme (or supplementary classification if axle-only data is collected), station spacing per IRC SP 19 Cl. 4.2, and AADT computation using IRC 37 / IRC 9 seasonal correction factors. A method that delivers 95% accuracy but fails the 7-day coverage requirement is not IRC SP 19 compliant. A 10-day count using a 5-class pneumatic scheme is not IRC SP 19 compliant either, even though the duration exceeds the minimum.

For step-by-step IRC SP 19 procedure compliance — station selection, calibration, validation, data analysis and reporting — see our dedicated guide: IRC SP 19 ATCC Survey Procedure — Step-by-Step Guide for NHAI Consultants.

Method-Selection Summary

On Indian highway projects in 2026, video-AI ATCC is the default-correct choice for any DPR, BoT/HAM, or audit-grade survey requirement. Pneumatic-tube ATCC remains useful as a low-cost option for capacity-only studies and as backup redundancy. Manual counts are best deployed as the validation ground-truth sample inside an AI-based survey, or for short-duration intersection turning movement work.

For pricing comparison across methods, see ATCC Survey Cost in India — Pricing Guide for NHAI, BoT/HAM & DPR Projects. For the full service scope and engagement options, see the ATCC Survey service page.