CSA

When a Lamp Failure Becomes a Bigger Problem: Understanding 393.9 Violations

Violation 393.9 is cited over 1.1 million times but rarely triggers out-of-service status by itself. Here's what the gap between citations and enforcement actually means for your fleet's maintenance discipline.

A burned-out clearance lamp is one of the easiest violations to miss. Until you don't.

Violation 393.9—"Inoperable Required Lamp"—shows up in the record with stunning frequency. Over 1.1 million citations, across nearly 800,000 inspections. That's not rare. That's routine. And that's exactly why it matters.

It carries a severity weight of 2, putting it in the low tier of the FMCSA's Safety Management System scoring scheme. It's not an out-of-service violation by itself—no inspector pulls your truck off the road just because a marker light burned out.

So why do I get asked about it constantly?

The answer is in the gap between the numbers.

What the Numbers Actually Tell You

There's a 6.4% out-of-service rate attached to 393.9 citations. In nearly 795,000 inspections where this violation was recorded, about 72,774 ended with the truck being removed from service—for some reason.

The lamp itself didn't cause the OOS. But the inspector who found the lamp kept looking, and that's where the real problems showed up.

This is the difference between understanding a violation in isolation versus how inspections actually work. When an inspector spots a burned-out clearance lamp, it often signals that the truck hasn't been maintained carefully. A lamp can burn out on any truck any day—but frequently enough it correlates with finding other defects. Brake wear. Tire damage. Suspension problems. Things that DO create out-of-service conditions.

The 393.9 violation is a canary in the coal mine.

393.9 at a glance
2 / 10
Severity weight
6.4%
OOS rate
1,136,869
Times cited

What the Regulation Actually Requires

49 CFR 393.9 covers clearance lamps, identification lamps, and other marker lights required on commercial motor vehicles. Every required lamp must function—no ambiguity.

For most tractors, this means:

  • Clearance lamps (front and rear)
  • Side marker lamps (amber front, red rear)
  • Identification lamps (top rear)
  • Tail lamps, brake lamps, and turn signals

The regulation exists because darkness makes visibility zero. When you're moving an 80,000-pound vehicle at 65 mph, other drivers need to know you're there. That's the mechanical principle underneath every lamp requirement.

Severity vs. the maximum
393.9
2
Max severity
10

Why This Shows Up So Often

Here's the practical reason 393.9 gets cited so much: it's easy to check and even easier to cite.

A roadside inspection takes minutes. The inspector does a walk-around, hits every light switch position, marks down anything that doesn't illuminate. No ambiguity. Either the light works or it doesn't. This is binary—nothing like violations that require interpretation or measurement.

When you're running a fleet of any real size, you're going to catch burned-out bulbs. Most times they're just burned-out bulbs. Sometimes they indicate deeper maintenance or training failures. The issue is knowing which is which, and building a pre-trip inspection process that catches these before an inspector does.

What This Costs You in SMS

The severity weight of 2 means this violation is light in the SMS algorithm. It won't blow up your scores the way unsafe driving or crash-indicator violations would. But it counts, and on a fleet, the weight accumulates.

More important: 393.9 is in the vehicle maintenance category, which contributes to your Safety Management System profile under that metric. Brokers, shippers, and insurance carriers review that metric when evaluating your operation.

Use the SMS calculator to see exactly how a 393.9 violation shifts your profile. The real impact becomes visible when you model it against your actual inspection history.

The Maintenance Window

Bulbs age. A lamp working today might not work in six months. Unlike brake pads or tires, you can't measure lamp life with a gauge—you have to check them.

Under SMS scoring, violations are weighted based on recency. A violation from the last six months carries full weight. Violations older than two years carry zero weight. That time-based structure means stale violations disappear—but only if you're not adding new ones.

For 393.9, the practical implication is straightforward: make lamp checks part of your regular maintenance schedule, with documentation showing when lamps were inspected and replaced.

Building the Right Response

If you're seeing 393.9 citations in your inspection data:

  1. Check your pre-trip forms. Every lamp should be required, with space for condition notes. If drivers skip it or mark everything "good" automatically, you know why lamps fail at roadside.
  1. Document replacements. This isn't about perfection—it's about showing maintenance is intentional, not reactive.
  1. Cross-reference with other violations. When 393.9 shows up, what else was on that inspection? Always alone? You've got a burn-out pattern. Always paired with other issues? You've got a training or maintenance process breaking down.

The Bottom Line

393.9 is a low-severity violation that almost never takes a truck out of service by itself. But it shows up in 6.4% of inspections that do result in OOS citations—often a leading indicator of deeper problems.

Don't ignore it just because it won't wreck your SMS scores. Treat it as a maintenance discipline check.

You can track this directly in your inspection data. Pull every report that flagged 393.9 and see what else appeared on the same inspection. The pattern tells you whether you're dealing with random lamp burn-outs or a systemic maintenance failure. Use VioCodes to look up the specifics of what the regulation requires and track these violations alongside your other maintenance defects.

Sources

vehicle maintenancecode deep divelamp violations393.9SMSsafety managementroadside inspections
Drafted with a data-grounded automated process and guardrail-checked before publishing. Here’s exactly how →

Keep reading