IRC 64:2017 is the Indian Standard (IRC) for guidelines for capacity of roads in rural areas. IRC 103:2012 focuses on the fundamental principles of rural road capacity analysis. It defines capacity in terms of the maximum volume of traffic that a road can handle under prevailing conditions while maintaining a specified level of service. The code emphasizes the unique factors influencing rural road capacity, such as lower operating speeds, presence of mixed traffic (including slow-moving vehicles and animal-drawn vehicles), limited access control, and varying road geometries. It provides methodologies for calculating capacity and service volume for different types of rural roads, including single-lane, intermediate-lane, and two-lane roads, taking into account the impact of shoulder width, horizontal and vertical curves, and intersections.
This IRC code provides guidelines for determining the capacity of rural roads, considering their specific geometric characteristics, traffic composition, and operational conditions. It aims to assist engineers in planning, designing, and assessing the performance of rural road networks.
Key reference values — verify against the current code edition / project specification.
| Reference | Value | Clause |
|---|---|---|
| Subject | Capacity of roads in rural areas | Scope |
| Capacity unit | PCU/day (or PCU/hour) by road type | Metric |
| PCU factors | Vehicle-class equivalency (slow + mixed traffic) | Method |
| Capacity governed by | Carriageway width, terrain, traffic mix | Design |
| Use | Upgrade/widening warrant (single→intermediate→2-lane) | Application |
| Read with | IRC 73 (rural roads) / IRC 106 (urban capacity) | Cross-ref |
IRC 64 specifies guidelines for capacity of roads in rural areas — methods to estimate the traffic-carrying capacity of rural and semi-urban roads (single lane, intermediate lane, two-lane, two-lane with paved shoulders, multilane), including the effect of road geometry, terrain, traffic composition, and operating conditions on capacity.
Use IRC 64 in: - New road planning — sizing the road for projected 15-20 year traffic - Capacity analysis of existing roads — bottleneck identification, upgrade decisions - Traffic impact assessments for development projects (housing, industry, ports) - Investment justification — road widening / four-laning / six-laning decisions - PMGSY upgrade decisions (single-lane to intermediate lane, intermediate to two-lane) - Service-level analysis on operating roads
IRC 64 distinguishes between: - Capacity — maximum hourly flow (vehicles/hour, or PCU/hour after passenger-car-unit conversion) under specified operating conditions - Service volume — flow at a specified Level of Service (LoS A, B, C, D, E) - Design service volume — capacity used for road sizing decisions (typically LoS C for rural, LoS B for new)
This code is the rural-roads capacity manual; for urban roads, see IRC:106. For expressways and high-speed corridors, IRC:73 + IRC:106 + project-specific HCM analyses are used.
Capacity per direction (vehicles per hour, mixed traffic, ideal conditions):
| Road type | Plain terrain | Rolling terrain | Hilly terrain | |---|---|---|---| | Single lane (3.75 m) | 800 PCU/h | 600 PCU/h | 400 PCU/h | | Intermediate lane (5.5 m) | 1,400 PCU/h | 1,000 PCU/h | 700 PCU/h | | Two lane (7 m, undivided) | 2,000 PCU/h per direction | 1,500 PCU/h | 1,000 PCU/h | | Four lane (14 m, divided) | 3,500 PCU/h per direction | 2,800 PCU/h | 1,800 PCU/h | | Six lane (21 m, divided) | 5,500 PCU/h per direction | 4,500 PCU/h | 3,000 PCU/h |
Passenger Car Unit (PCU) factors:
| Vehicle type | Plain | Hilly | |---|---|---| | Two-wheeler | 0.5 | 0.5 | | Car / jeep | 1.0 | 1.0 | | Auto-rickshaw | 0.8 | 0.8 | | Bus | 3.0 | 3.5 | | Truck (single unit) | 3.0 | 3.5 | | Truck-trailer | 4.5 | 5.0 | | Tractor + trailer | 4.5 | 5.0 | | Bicycle / cycle rickshaw | 0.5 | 0.5 | | Pedestrian (cross-flow) | adjust separately |
Adjustments (multiply ideal capacity by): - Lane width < standard: 0.85-0.95 - Shoulder width < 1.5 m: 0.90 - Heavy commercial vehicle % > 50: 0.85 - Steep grades (> 4 % > 100 m length): 0.70-0.85 - Narrow bridges, sharp curves: 0.85 - Pedestrian / bicycle activity: 0.85-0.95
Level of Service (LoS) flow ratios (V/C):
| LoS | V/C ratio | Description | Use | |---|---|---|---| | A | < 0.30 | Free flow | Aspirational; rural new construction | | B | 0.30-0.50 | Stable flow, reasonable freedom | New construction target | | C | 0.50-0.70 | Stable flow, restricted freedom | Operating design level | | D | 0.70-0.85 | Approaching unstable | Acceptable on existing roads | | E | 0.85-1.00 | Unstable, capacity | Congested | | F | > 1.00 | Forced flow, breakdown | Failed |
Worked example — sizing a new rural road:
A new district road is to be designed for 15-year horizon traffic. Survey shows current AADT 4,000 vehicles/day; projected 8,500 by year 15. Composition: 50 % cars, 20 % two-wheelers, 15 % trucks, 10 % buses, 5 % miscellaneous.
1. Convert to PCU/day: - Cars: 4250 × 1.0 = 4,250 PCU/d - Two-wheelers: 1700 × 0.5 = 850 PCU/d - Trucks: 1275 × 3.0 = 3,825 PCU/d - Buses: 850 × 3.0 = 2,550 PCU/d - Misc: 425 × 1.0 = 425 PCU/d - Total: ~12,000 PCU/d
2. Convert to peak-hour flow: - Peak-hour factor (rural): 8-10 % of daily flow → ~1,000 PCU/h
3. Match to road type from capacity table (plain terrain): - Single lane (800 PCU/h): V/C = 1000/800 = 1.25 → LoS F (failed) - Intermediate lane (1400 PCU/h): V/C = 1000/1400 = 0.71 → LoS D (acceptable) - Two lane (2000 PCU/h per direction, ~3000 PCU/h two-way undivided): V/C = 0.33 → LoS B (target)
4. Design recommendation: two-lane road. Provides LoS B at horizon year — comfortable margin for further growth.
5. Geometric design (IRC:73:1980): two-lane 7 m carriageway, 1.5 m earthen shoulders, design speed 80 km/h, vertical curves per IRC SP 23.
6. Pavement design (IRC:37:2018): based on commercial vehicle daily count and CBR.
7. Capacity reserve — design for LoS B (V/C 0.33-0.50) ensures future-proof against demand growth or composition shift (more trucks).
1. Using AADT (annual average daily traffic) directly as capacity input. Capacity is hourly, AADT is daily. Convert via peak-hour factor (rural: 8-10 % of daily; urban: 6-8 %). 2. Forgetting PCU conversion. A road with 50 % heavy trucks has very different effective flow than a 50 % car road, even with same vehicle count. Always convert via PCU factors. 3. Designing for current year traffic. Roads serve 15-30 years; design for projected 15- to 20-year traffic at minimum. Growth rate typically 5-10 % per annum for Indian roads. 4. Ignoring intersection capacity. Most road corridors are limited by intersection capacity, not link capacity. A 4-lane road with a bottleneck signal at every km drops to 1,200-1,800 PCU/h effective. Apply IRC SP 41 or capacity software (SIDRA, VISSIM) for intersection-controlled segments. 5. Standard capacity values without local adjustment. Adjustments for narrow lanes, shoulders, side friction, terrain are real and significant. Ignore them and you over-estimate capacity by 20-40 %. 6. Not accounting for non-motorised traffic. Bicycles, animal carts, pedestrians on rural roads consume 'capacity' of the lanes they share with motor traffic. Apply the appropriate adjustment. 7. Heavy local turning movements not modelled. Side roads, village exits, market entries cause friction, slowing through-traffic. Capacity drops substantially in such zones. 8. Aspirational LoS A on rural road designs. LoS A means very low V/C (< 0.30), implies wasteful overdesign. Aim for LoS B or C; LoS A is for special corridors only (e.g., new expressways). 9. No consideration of seasonal variation. Festival traffic, harvest season, market days — these can spike traffic 2-3× routine. Design hour traffic ≠ AADT/365 × peak-hour factor; check for special peaks. 10. Mixing 'lane capacity' and 'directional capacity'. Two-lane undivided road: 2,000 PCU/h per direction in IRC 64; some confusion with HCM 'two-lane two-way' which is total capacity both directions ~1,800-2,800 PCU/h. Use IRC convention consistently. 11. Not checking for safety implications of high V/C. High capacity utilisation correlates with higher accident rates (less time gap, less recovery margin). Combined safety + capacity analysis is best practice.
Standard road planning cascade:
1. Need identification — connectivity, congestion, deteriorated road, new development. 2. Origin-destination + traffic survey — current AADT, peak-hour, composition, growth rate. 3. Forecast traffic — to design horizon (15-20 years for highways, 10 for rural roads). 4. Capacity analysis (this code, IRC 64) — match projected demand to road type / lane configuration / LoS target. 5. Geometric design (IRC:73, IRC:38, IRC SP 23) — width, alignment, sight distance, junctions. 6. Intersection design (IRC SP 41, IRC SP 87) — at-grade signalised, grade-separated. 7. Pavement design (IRC:37 or IRC:58) — flexible or rigid based on life-cycle cost. 8. Cross-drainage + side drainage. 9. Cost estimation + financial analysis — life-cycle cost, IRR, BCR. 10. Tendering + construction. 11. Operation + monitoring — traffic counts validate forecast; trigger expansion if forecast exceeded.
Use IRC 64 strategically: - For new road: forecast traffic → capacity table → road type → LoS validation - For existing road upgrade: count + composition → check current LoS → if LoS D or worse, plan widening/upgrade - For investment justification: BCR / IRR analysis using time-savings and operating-cost reductions enabled by capacity expansion - For corridor planning: identify weakest-capacity link in the corridor; that's where investment is most leveraged
| Parameter | IS Value | International | Source |
|---|---|---|---|
| Vehicle Classes | Defined vehicle types (cars, trucks, buses, RVs, light trucks, etc.) | ||
| Peak Hour Factor (PHF) | Used across various standards for traffic flow variability within the peak hour. | ||
| Level of Service (LOS) | Ranges (e.g., A-F) with performance measures like density, speed, delay. | ||
| Adjustment Factors | Factors for lanes, shoulders, traffic composition, grade, curves, etc. |