IRC SP 19 ATCC Survey Procedure — Step-by-Step Guide for NHAI Consultants

What IRC SP 19 Covers

IRC SP 19 (Manual for Survey, Investigation and Preparation of Road Projects) is the over-arching IRC document for the survey work that feeds a road-project DPR. Its traffic-survey sections (Cl. 4.2–4.4 and Annexure 4-1) define how ATCC surveys are conducted, classified, validated and reported. It works together with IRC 9 (Traffic Census on Non-Urban Roads) for AADT seasonal-correction methodology, IRC 106 (Capacity of Urban Roads in Plain Areas) for peak-hour analysis, IRC 37 (Flexible Pavement Design) for converting traffic data into MSA, and IRC SP 84 (Six-Laning Manual) for BoT/HAM concession-specific traffic-data requirements.

The IRC SP 19 17-Class Vehicle Classification

IRC SP 19 prescribes a 17-class vehicle classification scheme. Every ATCC survey output must classify vehicles into these categories — collapsing into broader bins (e.g., 5-class axle-only) is not IRC SP 19 compliant for NHAI DPR work.

Indicative VDF ranges shown above. Actual project VDF must be computed from paired axle load survey data using the fourth-power law per IRC 81 — the table values are starting defaults, not substitutes for project-specific axle load measurement.

Step 1 — Station Selection and Spacing

IRC SP 19 Cl. 4.2 prescribes ATCC station selection criteria. Stations must be on a straight, level mid-block section away from intersections (minimum 200 m clear), bus stops, fuel stations, toll plazas, and any other traffic-influencing feature. The station should be representative of the corridor's traffic-generation profile — separate stations are required for sections with materially different traffic character (e.g., upstream and downstream of a major industrial cluster, or before and after a town bypass diversion).

Station spacing on long corridors typically follows 25-50 km intervals, with denser placement at traffic-influence boundaries. A typical NHAI DPR for a 100 km corridor uses 4-6 stations; for a 250 km corridor, 8-12 stations. For BoT/HAM concession monitoring where year-on-year trends are tracked, the same stations are re-used annually to ensure comparability.

Step 2 — Equipment Deployment and Calibration

For video-AI ATCC, cameras are mounted on roadside poles or temporary masts at the height and angle that gives unobstructed view of all lanes in both directions. The AI system runs a 30-minute calibration sweep — sample frames are reviewed for plate visibility, occlusion patterns, sun-glare windows, and headlight bloom. If sight-lines are compromised on any direction, a backup pneumatic-tube ATCC is laid as a redundant counter.

For pneumatic-tube ATCC, tubes are stretched across the full carriageway and secured to the pavement surface with adhesive and road nails. The data logger is calibrated by manually verifying vehicle classifications against visual observation for the first 1-2 hours of operation. Tube tension must be within the manufacturer's specification — over-tensioned tubes miss low-pressure axle passes, under-tensioned tubes register false positives from pavement vibration.

For manual classified counts, surveyors are deployed in pairs at each direction with handheld tally counters per IRC class. Inter-surveyor classification consistency is established via a 2-hour calibration session at the start where both surveyors classify the same traffic stream and reconcile any disagreements before the survey begins.

Step 3 — 7-Day × 24-Hour Continuous Coverage

IRC SP 19 mandates a minimum of 7 consecutive days × 24 hours per day. Shorter samples (e.g., 3-day or daytime-only counts) are not acceptable for AADT estimation and are rejected at NHAI technical review. The 7-day requirement is designed to capture the full weekly traffic cycle including weekday-vs-weekend variation, market-day spikes, and any local periodic patterns. Continuous 24-hour coverage captures the full day-night cycle including the high-VDF night-time freight movement that disproportionately affects MSA computation.

During the 7-day window, the field team conducts daily QA visits to verify equipment integrity, IR illumination (for video-AI), tube tension (for pneumatic), surveyor wellness (for manual), and battery / power supply status. Any equipment failure during the survey window requires the affected hours to be either re-surveyed or marked as data gaps with explicit interpolation methodology in the final report.

Step 4 — Manual Ground-Truth Validation Sample

For automated methods (video-AI and pneumatic-tube), IRC SP 19 requires a manual ground-truth validation sample. NKMPV's standard protocol is a 10% stratified sample distributed across day/night/peak/weekend windows — typically four 4-hour blocks giving a 16-hour validation total per station. Trained surveyors classify the same traffic stream that the AI or pneumatic system is recording, and the two records are compared event-by-event.

For each IRC class, per-class accuracy is computed as (correctly classified events / total events) × 100. Acceptance threshold is ≥ 95% per class. Any class with < 95% match triggers (a) re-training of the AI model on that class's frames before final classification is locked, or (b) for pneumatic-tube data, supplementary manual classification overlay for that class throughout the 7-day window. The validation methodology, sample size, and per-class results are reported transparently in the final NABL deliverable — NHAI technical review explicitly checks for this section.

Step 5 — ADT and AADT Computation

Average Daily Traffic (ADT) is computed from the 7-day total: ADT = (sum of 7-day classified volumes) / 7, computed separately for each direction and aggregated for total. ADT is the survey-week average, not the annual average — applying ADT directly into IRC 37 design-traffic calculations underestimates traffic during peak months and overestimates during low months.

Annual Average Daily Traffic (AADT) is derived by applying seasonal correction factors to ADT. IRC 9 provides region-specific monthly factors that account for typical seasonal variation in Indian highway traffic — for example, a survey conducted in March typically has a seasonal factor of 1.05–1.10 (above the annual average), while a survey conducted in August (monsoon) typically has 0.85–0.95 (below average). The applied factor must reflect both the survey month and the corridor's regional traffic-generation profile (agricultural belt, industrial cluster, tourism circuit, etc.).

Day-of-week correction is applied where the 7-day window did not include a representative spread (rare, since 7 consecutive days always cover the full week). Where it does apply, IRC 9 provides day-factors (typical weekday vs. typical Sunday) for AADT normalisation.

Step 6 — VDF and MSA Computation per IRC 37

Vehicle Damage Factor (VDF) is computed per class from paired axle load survey data using the fourth-power law per IRC 81: for each axle, equivalent standard axle load = (actual axle load / 80 kN)⁴, summed across all axles of the vehicle to give the VDF for that vehicle. Class-level VDF is the average across the axle-load sample for that class. NHAI DPR review explicitly checks that VDF is project-specific (computed from on-site axle-load data), not just defaulted from IRC 37 Table 2.

Cumulative Million Standard Axles (MSA) — the design-traffic input for IRC 37 — is computed using:

N = 365 × A × D × F × [(1+r)ⁿ − 1] / r

Where: N = cumulative MSA over the design life; A = AADT of commercial vehicles in the year of completion; D = lane distribution factor (per IRC 37 Cl. 5.1); F = average VDF for the commercial-vehicle fleet (computed from class-level VDF weighted by class share); r = annual traffic growth rate (typically 5-7.5% for Indian highways); n = design life in years (typically 15-20 for NH and 10-15 for SH per IRC 37 Cl. 5.3).

For overlay design under IRC 115 on existing pavements, the same MSA is computed for the residual life period. The IRC 37 MSA combined with FWD structural deflection data drives overlay thickness selection — see IRC 115 Overlay Design — FWD Back-Calculation Guide for the structural-side methodology.

Step 7 — Reporting and NABL Deliverables

An IRC SP 19 compliant ATCC report includes the following sections, all of which NHAI technical review explicitly checks:

Common Rejection Reasons at NHAI Technical Review

Across NHAI DPR reviews, the recurring reasons ATCC sections are sent back for rework are: (1) survey duration shorter than 7 × 24 hours; (2) classification scheme broader than IRC SP 19 17-class (e.g., reporting only 5 axle-based classes); (3) AADT computed without seasonal correction factor application; (4) VDF defaulted from IRC 37 Table 2 without project-specific axle-load measurement; (5) station selection on bridges, intersection-influence-zones, or non-representative sections; (6) missing manual ground-truth validation for automated counts; and (7) NABL accreditation reference missing or referring to a different scope (e.g., a NABL-accredited soil testing lab claiming acceptance for traffic surveys). Each of these can be avoided by structuring the engagement up front with explicit IRC SP 19 conformance items in the scope-of-work.

Method Choice — Video-AI vs Pneumatic vs Manual

All three methods can satisfy IRC SP 19 if executed correctly, but their accuracy and evidence-trail characteristics differ. For a head-to-head comparison and method-selection guidance, see ATCC vs Manual Traffic Count — Why Video-AI Wins on Accuracy. For pricing implications of each method, see ATCC Survey Cost in India — Pricing Guide.

Compliance Summary

An IRC SP 19 compliant ATCC survey delivers: full 17-class classification, 7-day × 24-hour continuous coverage, ≥ 95% per-class validated accuracy, project-specific AADT with seasonal correction, project-specific VDF from paired axle load survey, and IRC 37 MSA computation with all parameters transparently tabulated. NHAI DPR acceptance, BoT/HAM concession monitoring, and arbitration defensibility all depend on these items being satisfied — and explicitly demonstrated in the report — not just the headline traffic volume number.