AIS 140 Compliance,
made simple
Everything you need to become AIS 140 compliant — what it is, whether it applies to your fleet, what a certified VLTD must do, and how to get through empanelment. From an operator fitting compliant devices across India since 2009.
AIS 140 is an Indian government standard that requires certain commercial and public-service vehicles to fit a certified Vehicle Location Tracking Device (VLTD) with GPS/NavIC, one or more emergency panic buttons, and a live data link to state monitoring servers. Compliance is usually tied to getting or renewing a vehicle permit. This guide explains who must comply, exactly what the device must do, and how to get compliant without failing empanelment.
What is AIS 140?
AIS 140 (Automotive Industry Standard 140) is a standard issued under India's Ministry of Road Transport & Highways (MoRTH) for intelligent transportation systems — most importantly vehicle location tracking and emergency-request functionality in public and commercial transport.
In plain terms, it mandates two things on covered vehicles: a VLTD that continuously reports the vehicle's position to a state-approved backend, and one or more panic buttons a passenger or driver can press to raise an alert.
Does AIS 140 apply to my fleet?
Applicability is set nationally but enforced by each State Transport Authority, so the exact list and dates vary by state — always confirm with your RTO. Broadly, AIS 140 commonly applies to:
- Public service vehicles — buses, taxis and cabs carrying passengers (yellow-plate commercial vehicles).
- Commercial vehicles on national / all-India permits, and many goods carriers.
- School and college transport — mandated in many states (see the state snapshot below).
It typically does not apply to private cars. The practical trigger is the permit: in most states you cannot obtain or renew the vehicle's permit or fitness certificate without a compliant VLTD fitted and registered.
Does it apply to you? Check in 10 seconds
Tell us your vehicle type and state and we'll send a tailored compliance summary — what applies, the device you need, and the fitment steps for your RTO.
Interactive rules engine to follow post-launch; today this routes to our compliance team with your context.
Compliance snapshot by state
Rules and enforcement differ by state — this is where most guides stop and where operators get stuck. We expand this to every state as we verify each RTO's process.
| State | School transport | Practical trigger |
|---|---|---|
| Kerala | Mandated | Permit / fitness |
| Maharashtra | Mandated | Permit / fitness |
| Madhya Pradesh | Mandated | Permit / fitness |
| Punjab | Mandated | Permit / fitness |
| Himachal Pradesh | Mandated | Permit / fitness |
| Chhattisgarh | Mandated | Permit / fitness |
| Jammu & Kashmir | Mandated | Permit / fitness |
| Other states | Confirm with your RTO | Permit / fitness |
AIS 140 for public and commercial vehicles applies across India; school-transport mandates and enforcement vary by state, so always confirm the current position with your state RTO. We expand this table as we verify each state.
What must an AIS 140 device do?
A compliant VLTD must meet the standard's functional requirements — and each is where a cheap device cuts a corner. Verify against the current AIS 140 text.
| Requirement | What it means | Compliant | Common shortcut |
|---|---|---|---|
| GNSS positioning | Satellite positioning with defined accuracy | GPS + NavIC | GPS only |
| Emergency button | Alert to the monitoring centre | Hard-wired panic button(s) | None |
| Backend link | Live data to state-approved servers | Registered on state portal | Only the vendor app |
| Connectivity | Reliable cellular coverage | Embedded M2M SIM | Consumer SIM |
| Power | Keeps reporting if power is cut | Internal backup battery | No backup |
| Integrity | Detects interference | Tamper & health alerts | Silent when unplugged |
AIS 140 device vs a normal GPS tracker
A cheap "GPS tracker" is not AIS 140 compliant — even if it shows location perfectly. This is the difference that fails permits.
| Capability | AIS 140 VLTD | Normal GPS tracker |
|---|---|---|
| Type-approval / certification | Required (ARAI/ICAT) | None |
| State backend empanelment | Yes | No |
| NavIC / IRNSS | Yes | Usually not |
| Panic / SOS button | Mandatory | Rare |
| Backup battery & tamper alerts | Required | Varies |
| Valid for permit / fitness | Yes | No |
Why AIS 140 installations get rejected
In our experience fitting compliant devices since 2009, most rejections aren't about the hardware — they're about small process gaps that are easy to avoid once you know them. The most common we see:
- Device not empanelled in that state (approved elsewhere, assumed valid everywhere).
- Fitted, but backend registration on the state portal never completed — so it's invisible to the authority.
- Data stopped weeks earlier (SIM/health) and nobody noticed until renewal.
What our engineers check before handover: live data reaching the state backend, a successful panic-button test, tamper seals in place, and the vehicle correctly linked on Vahan/permit.
What "certified" really means
Not every GPS tracker is an AIS 140 device. A compliant device is type-approved / tested by an authorised agency — industry sources consistently name ARAI and ICAT — and appears on the approved / empanelled lists your state and its backend provider accept.
- Check the test certificate and certifying agency (and its number).
- Confirm the exact model is on your state's empanelled list.
- Confirm the vendor handles backend registration, not just the hardware.
How do I choose the right AIS 140 device?
The cheapest device is rarely the right one — a failed empanelment or a dead unit at renewal costs far more. From what we see across thousands of fitments, weigh these before you buy:
- Genuinely certified & approved model — with a verifiable certificate, not just an "AIS 140" label.
- Backend compatibility — empanelled with your state's VLTD portal, so registration actually goes through.
- Warranty & AMC — clear terms; who replaces a failed unit, and how fast.
- Installation quality — an authorised installer, proper seals, and a real installation certificate.
- Service availability — local support where your vehicles run, not a phone number in another state.
- Ongoing health monitoring — so a dropped device is caught in days, not at renewal.
Get these right and compliance stays effortless year after year. That's the difference between buying a box and staying compliant.
How to get compliant
Confirm applicability & deadline
Check your vehicle category and the current deadline with your state RTO.
Choose a certified device empanelled in your state
Certification alone isn't enough — it must be accepted by your state's backend.
Fit it through an authorised installer
With tamper-evident seals and a proper installation certificate.
Register the device with the state backend
Link it to the vehicle (Vahan / permit) on the state VLTD portal.
Verify the data is flowing
Confirm the backend is receiving data before you rely on it for permit work.
Keep it healthy
Monitor for disconnection / tamper so you stay compliant at renewal.
The checklist our engineers use before handover
A one-page, print-ready checklist for getting a vehicle compliant and through empanelment — the same steps we run on every fitment.
Get compliant with MaxTrax
We've been deploying vehicle-tracking hardware and software across India since 2009, for 2,000+ fleets. For AIS 140 we provide certified, state-empanelled VLTDs; end-to-end fitment + backend registration (not just a device in a box); a platform so you can see compliance — panic-button tests, device health, live location; and on-ground support from offices in Delhi, Dehradun, Mysore and Guwahati.
AIS 140 — frequently asked questions
Last updated: July 2026