The NTSA speed-limiter regime in Kenya is one of those compliance regimes where the rules are written down but the operating reality has to be learned. Augusta has worked through the certification process multiple times, including for some of Kenya's largest fleets. Here's the practical guide we wish we'd had.
This is not legal advice. The law is what NTSA publishes; this is what the published law looks like in operation, and what the typical operator needs to do.
What the regime actually requires
Every commercial vehicle classified as a Public Service Vehicle, school bus, or commercial cargo vehicle above the relevant tonnage must have an NTSA-certified speed-limiter device installed. The device caps the vehicle's speed at the regulator-defined maximum (currently 80 km/h for most categories), tamper-proofs the cap, and records speed events for audit.
Operators must also submit monthly compliance reports drawn from the device data, and accommodate periodic on-site audits.
Choosing the right device
The market is full of devices that claim NTSA certification. The bar to confirm is low: ask for the certification reference number, then verify it against the published NTSA-certified-devices list. Anything not on the list will fail audit, regardless of what the vendor's brochure says.
Beyond certification, the things that distinguish a good device from a barely-passing one:
- CAN-bus integration. Reads speed direct from the ECU rather than guessing from GPS. More accurate, harder to tamper.
- Internal battery. Survives short power cuts during installation or repair without losing state.
- OTA firmware updates. Saves money on field-service visits when the regulator changes the spec.
- Multi-MNO SIM. Better coverage in rural Kenya than a single-carrier device.
Installation gotchas
The most common reason vehicles fail their first compliance check isn't the device — it's the installation. Don't skip the post-install validation step. Drive the vehicle, generate one or two real speed events, and confirm they appear correctly in the platform before signing off.
Other common gotchas:
- Tampering seals applied incorrectly fail visual audit even if the device is functional.
- Installer isn't on the NTSA-approved list — automatic non-compliance.
- The vehicle's OEM speed-limiter wasn't disabled before installation; the two fight each other intermittently.
- The SIM is provisioned but not registered to the vehicle in the platform — telemetry shows up under "unknown vehicle."
Monthly reporting
NTSA wants a monthly report showing fleet-wide speed-limiter status, speed events above threshold, and any device offline / tamper events. Most platforms generate this automatically. The compliance failure that causes audit findings is rarely the data — it's the reports not being submitted on time, or being submitted in the wrong format because the regulator changed the template and nobody noticed.
Treat NTSA reporting like payroll, not like an annual exercise. Same person, same day each month, same checklist. The operators who get fined are the ones where the responsibility wasn't named clearly enough.— Abdulhamid Haid
When the audit comes
NTSA audits are usually unannounced. The auditor wants to see: a vehicle list, the device serial-number-to-vehicle mapping, the certification documents for each device family, the last twelve months of compliance reports, and a sample of speed events with the supporting raw data.
If your platform can produce all of that on demand, the audit takes a couple of hours. If it can't, the audit takes a week and the fine schedule starts.
Operate it cleanly
The operators who treat speed-limiter compliance as a foundational operational discipline — not a once-a-year fire drill — never have audit problems. The cost of getting it right is low; the cost of getting it wrong scales with fleet size.
If you're starting up a fleet or replacing your current speed-limiter platform, we're happy to share the full operating playbook with operators who are committing to do it well.