IRC 37:2018 Flexible Pavement Design — Method, Inp...

7 min read · IRC 37 · Pavement Design · Highway Engineering · Structural Engineering · IS Codes
Home / Knowledge / IRC 37
IRC 37Pavement DesignHighway EngineeringStructural EngineeringIS Codes📖 7 min · 1,605 words
🧮 Construction Cost Calculator
Free calculator with IS code clause references
Try Free →

IRC 37:2018 Flexible Pavement Design — Method, Inputs, Worked Example

IRC 37:2018Guidelines for the Design of Flexible Pavements (Fourth Revision) — is the code every highway designer in India works to for bituminous pavements. It replaces IRC 37:2012, tightens the traffic inputs, updates the fatigue and rutting models, and formally endorses IITPAVE as the recommended analysis software. If you are preparing a DPR, a design submission for NHAI/PWD, or a DSR-rate estimate, the pavement composition and layer thicknesses you arrive at will trace back to this document.

This article explains what IRC 37:2018 actually does — the inputs it demands, the failure models it uses, the design charts versus the mechanistic-empirical path, and a worked example at 10 MSA traffic on a subgrade CBR of 5%. Where a specific clause matters, it is cited inline.

1. What the 2018 revision changes

IRC 37 has gone through four revisions (1970, 1984, 2001, 2012, 2018). The 2018 revision introduced six substantive changes over 2012:

  • Higher design traffic bands. The upper limit in the design catalogue extended to 300 MSA (from 150 MSA), acknowledging that six-lane expressways and heavy-freight corridors exceed the earlier ceiling.
  • Reliability upgraded. For high-volume roads (≥ 30 MSA), design reliability is set at 90%; for lower volumes, 80%. This directly feeds the allowable rut depth and fatigue-crack area.
  • Updated mix types. Explicit recognition of Stone Matrix Asphalt (SMA) for the wearing course on heavily-trafficked roads, and modified-binder mixes for zones with high temperature differential.
  • Two-layer cemented bases. Cemented base (cementitious material binding granular aggregate) + crack-relief layer (SAMI or aggregate interlayer) is now a design option — reduces total pavement thickness by 40–100 mm typical.
  • Revised fatigue model. The allowable tensile strain at the bottom of the bituminous layer is now computed from a new MEPDG-derived model that is more sensitive to binder grade and mix volumetrics.
  • Drainage explicitly factored in. A layer-drainage coefficient modifies the resilient-modulus inputs, reflecting the field observation that poorly drained subgrades fail early regardless of the analytical design margin.

2. The design inputs IRC 37 demands

Before you can open IITPAVE or pull a catalogue chart, IRC 37 requires five verified numbers:

  1. Design CBR of subgrade — from a 4-day soaked CBR test (IS 2720 Part 16). IRC 37 prescribes using the 10th percentile of multiple section tests, not the average, for high-volume roads.
  2. Annual Average Daily Traffic (AADT) in commercial vehicles per day, at opening year, with 10-year growth projection.
  3. Vehicle Damage Factor (VDF) — converts mixed commercial traffic to standard axles. Values range from 1.5 for plain-terrain low-volume roads to 5.5 for high-volume plain-terrain NH expressways. Table 1 of IRC 37.
  4. Lane Distribution Factor (LDF). For two-lane, two-way: 0.5. For four-lane divided: 0.75 (outer lane carries most). For six-lane divided: 0.60.
  5. Design period — usually 15 years for flexible pavements, 20 years for state highways, up to 20 years for expressways.

Design MSA formula: N = 365 × A × [(1+r)n − 1] / r × VDF × LDF × 10−6 — where A is AADT of commercial vehicles at opening, r is annual growth rate, n is design life in years.

3. The two paths — catalogue or IITPAVE

IRC 37:2018 offers two design paths:

  • Plate 1–6 catalogue charts. For standard situations — subgrade CBR ≥ 5%, design traffic up to 300 MSA, conventional bituminous composition — read the total thickness + layer breakdown directly off the plate. Fast, conservative, audit-trail-friendly.
  • Mechanistic-Empirical (IITPAVE) analysis. Layer stiffnesses (resilient moduli) entered as inputs; IITPAVE computes tensile strain at bottom of bituminous layer and vertical compressive strain at top of subgrade; designer iterates the layer thicknesses until both strains are within allowable per fatigue and rutting models. Needed when you want to optimise, use non-standard materials, or adjust for temperature-differential zones.

For 90% of routine Indian highway designs, the catalogue is the correct choice. IITPAVE is essential when any of the following apply: cemented base with SAMI, foamed-bitumen mix, design traffic > 300 MSA, or explicit fatigue-life verification for NH / Bharatmala corridors.

4. Pavement composition — what layers sit where

A standard IRC 37 flexible pavement has four layers from top down:

LayerMaterialTypical thicknessFunction
Wearing courseBC (Bituminous Concrete) — or SMA on heavy-traffic roads40–50 mmSkid resistance, ride quality, waterproofing
Binder courseDBM (Dense Bituminous Macadam)50–100 mmStructural — resists fatigue cracking
Base courseWMM (Wet-Mix Macadam) — or cemented base + SAMI150–250 mmLoad distribution to subbase
SubbaseGSB (Granular Sub Base)150–300 mmDrainage, frost heave buffer, further load spread
SubgradePrepared in-situ soil(existing)Foundation — must be compacted to 97% MDD min

For every catalogue plate in IRC 37, the total thickness and the breakdown across these layers is tabulated against design traffic (MSA) and subgrade CBR.

5. Worked example — 10 MSA traffic, CBR 5%

Take a two-lane, two-way state highway in plain terrain with opening-year AADT of 2,000 commercial vehicles per day, annual growth 5%, 15-year design life, VDF of 3.5, LDF of 0.5.

N = 365 × 2000 × [(1.05)15 − 1] / 0.05 × 3.5 × 0.5 × 10−627.6 MSA. Round up to 30 MSA design bucket.

Now read Plate 1 of IRC 37:2018 at CBR 5% and design traffic 30 MSA. The catalogue returns roughly:

  • BC wearing course: 40 mm
  • DBM binder course: 90 mm
  • WMM base: 250 mm
  • GSB subbase: 200 mm
  • Total pavement thickness: 580 mm

For comparison, the same alignment on CBR 8% would drop to roughly 500 mm total; on CBR 3% it climbs to about 700 mm, with an additional capping layer likely recommended. This sensitivity to subgrade CBR is why IRC 37 is strict about CBR sample density, 10th-percentile adoption, and soaked-condition testing.

6. Seasonal and temperature-zone corrections

IRC 37:2018 divides India into four temperature regions for bituminous-layer design. Hot-desert zones (Rajasthan, parts of Gujarat, Vidarbha) use modified-binder PMB 40 or similar, while temperate hill-state roads (Himachal, Uttarakhand) use softer PMB 70. This is set in Annex I of the code. Mix design (Marshall or Superpave) is governed separately by MoRTH Specifications Section 500.

For rutting-prone alignments (urban approaches, toll plazas, port-corridor stretches), IRC 37 allows designers to substitute SMA in the wearing course — ~40% more expensive in material but 2–3× longer rutting life on heavy-truck lanes.

7. Drainage — quiet killer of pavements

The 2018 revision is emphatic: poor drainage is responsible for the majority of premature pavement failures in India. IRC 37:2018 now requires a drainage-evaluation check at the subgrade and the subbase level, and restricts credit for design thickness if the drainage rating is poor. In plain terms — if the side drains are not functioning or the subgrade sits in standing water during monsoon, no design thickness will deliver the designed life. Don't design the pavement ignoring this; downgrade the effective CBR by one class when drainage is uncertain.

8. Connection to construction cost

Pavement thickness is the single largest driver of per-km highway cost. Moving from CBR 3% to CBR 5% subgrade can reduce total pavement thickness by ~20% — roughly ₹40–60 lakh per km of two-lane-equivalent saving. Designers have a real incentive to ensure subgrade preparation is done properly (lime or fly-ash stabilisation on expansive soil, moisture-density control) rather than paving over a marginal subgrade and compensating with thicker bituminous layers. Our cost calculator does not yet break out pavement costs separately, but DSR rate analysis under IRC 37 line items is a useful sanity check for your design submission.

9. Key differences from IRC 37:2012

TopicIRC 37:2012IRC 37:2018
Upper traffic limit150 MSA300 MSA
Reliability80%–90% (descriptive)80% (<30 MSA), 90% (≥ 30 MSA)
SMA wearing courseMentionedFormally included in catalogue
Cemented base + SAMINot standardStandard design option
Fatigue model1990s calibrationMEPDG-updated
DrainageReferencedExplicit downgrade rule

10. FAQ — IRC 37:2018

Is IRC 37:2018 compulsory for state PWD roads?

For NH works under MoRTH and for NHAI projects, yes. State PWDs typically adopt IRC 37 via their own circulars; most major states follow it directly. District-level rural roads may follow PMGSY specifications (SP 20, SP 72) which align with but are not identical to IRC 37.

When should I use IITPAVE over the catalogue?

Use IITPAVE when: (a) design traffic exceeds 300 MSA, (b) you are using non-standard materials (foamed bitumen, cold recycling), (c) you need a specific fatigue life demonstrated to the client, or (d) the alignment has unusually high temperature differential. For routine state-highway designs with standard BC/DBM/WMM/GSB, the catalogue is adequate and far less error-prone.

What's the minimum CBR for design under IRC 37:2018?

CBR 2% is the lowest band in the catalogue. Below 2%, the code recommends subgrade improvement — borrow fill, lime stabilisation, or geosynthetic reinforcement — rather than direct design.

Does IRC 37 cover rigid pavements?

No. Rigid pavements follow IRC 58 (cement concrete pavements) and IRC SP 62 (rural roads). IRC 37 is strictly flexible (bituminous) pavements.

What's the typical design life used?

15 years for NH flexible pavements is typical; 20 years for expressways; 10 years for low-volume rural roads. The design life feeds directly into the MSA calculation and therefore into the pavement composition.

Where does the Vehicle Damage Factor come from?

IRC 37 Table 1 gives default VDFs by terrain (plain / rolling / hilly) and traffic band. For high-volume corridors, a project-specific axle-load survey is the preferred approach — NH / NHAI projects usually conduct this as part of the DPR stage. Using default VDF on a corridor carrying heavy coal or iron-ore traffic will under-design the pavement.

🧮 Construction Cost Calculator
Free calculator with IS code clause references
Try Free →
Join InfraLens WhatsApp Channel
Get updates on new articles, tools, and IS code insights
More Articles
Clause references and parameter values are sourced from official BIS and international standards. Always refer to the original standard document for design decisions.
💬 Join the Discussion
Q: What has been your experience with this topic on site?
Q: Do you have any tips to share with fellow engineers?
Click a question to start your comment
Leave a Comment
0/500
No comments yet. Be the first to share your thoughts!