Prevention FAQ — FMCSR 393.78: Windshield Condition Defective

Inspectors are evaluating whether windshield condition impairs the driver's forward view. Specific triggers include cracks running through the driver's primary sightline, large chips or starred breaks in the swept area, discoloration or hazing that reduces visibility, and illegal aftermarket tinting. Stickers, mirrors, or objects mounted in the swept area can also factor in.

Enforcement intensity is heavily concentrated in Texas, which generated 16,748 citations in just the last 180 days — far exceeding every other state in our database. Illinois is notable for a different reason: its 2.4% OOS rate on 291 citations is the highest among top states, meaning Illinois inspectors are more likely to convert a 393.78 stop into an out-of-service event than peers. New Mexico (1.6% OOS rate) and California (0.8%) also show elevated OOS conversion. If your fleet runs significant Texas miles, this code should be a primary focus — no other jurisdiction is generating remotely comparable citation volume.

Build these as discrete, checkable line items — not a single "check windshield" bullet:

• Crack scan: Walk the full width of the windshield at eye level. Note any crack longer than a dollar bill in the driver's primary sightline (roughly the area swept by wipers).
• Chip and star map: Any chip larger than a quarter, or a star break with arms extending into the swept area, requires reporting before dispatch.
• Haze and delamination check: Look through the glass at a distant object. If the image blooms or doubles, the laminate is failing.
• Obstruction scan: Confirm no stickers, GPS mounts, or hanging objects are placed in the primary sightline.
• Wiper contact zone: Run wipers on low and confirm they clear the swept zone without smearing across a crack — smearing often reveals delamination not visible in static inspection.
• Interior fogging tendency: Note if the defroster keeps the interior surface clear within 5 minutes; persistent fogging can itself contribute to an impaired-view citation.

Drivers should initial the windshield line separately on the DVIR, not bundle it into a general "cab condition" checkbox.

Drivers should carry the shop work order in the cab — not just a receipt — showing the vehicle's unit number, the specific nature of the repair (e.g., "chip fill, driver-side lower quadrant" or "full replacement, OEM glass"), and the technician's name and date. If the repair was a resin fill rather than replacement, the documentation should confirm the crack or chip no longer penetrates to the inner layer.

Carriers should retain:

• The original DVIR entry that triggered the repair, with the driver's description and the mechanic's signature certifying the defect was corrected.
• The vendor invoice, including glass specifications (DOT-marked glass is required for CMVs).
• Photos of the defect before repair and the completed repair after — time-stamped and linked to the unit record in your maintenance management system.

Retention period should align with your standard maintenance record policy, but given that 393.78 is ranked #10 of 3,036 FMCSR codes by citation volume, windshield records are worth keeping for the full three years required for inspection and maintenance documentation.

Our inspection records show clear systemic patterns in the co-occurring codes from the last 90 days:

393.9 (Inoperable Required Lamp) — 3,550 shared inspections. This is the most frequent pairing. When a fleet is generating both lamp-out and windshield violations on the same inspection, the underlying issue is almost always a failed or superficial pre-trip process. Drivers are not completing the exterior walk-around with enough attention to any item that requires visual inspection.

392.2RG (Operating while ill or fatigued) — 1,663 shared inspections. This pairing suggests the windshield defect was not new — the driver knowingly operated with an impaired view, which inspectors read as a fatigue/judgment issue as well as a maintenance failure. Root cause here is often dispatch pressure overriding the driver's decision to refuse a unit.

396.5B (Fuel system leak) — 1,423 shared inspections. Appearing alongside a fuel leak indicates the unit had deferred multiple maintenance items simultaneously. This points to a PM interval problem or a work-order backlog, not isolated bad luck on the windshield.

All three patterns suggest the same corrective priority: strengthen DVIR follow-through and close deferred-defect loops before dispatch.

Do not return a unit to service based on a driver's verbal report that the glass shop "fixed it." Require the following verification steps:

1. Physical re-inspection by a second person (shop foreman or safety coordinator, not the same technician who did the work) before the unit is marked available in your dispatch system.
2. View-plane test: Stand at the driver's seat position and look through the repaired area at a defined distant point. The view should be optically clear — no distortion, hazing, or visible crack remnant in the swept zone.
3. DOT marking confirmation: If glass was replaced, verify the new glass carries a DOT-compliant marking. Non-DOT glass on a CMV creates a standalone violation exposure beyond 393.78.
4. DVIR closure: The mechanic must sign the corrective-action line on the DVIR, not just close the work order in the maintenance system. Both records should exist.
5. Photo documentation: Capture a post-repair image from the driver's eye point, stored with the unit's maintenance record.

For fleets operating heavily in Texas — 16,748 citations in the last 180 days came from that state alone — this verification step is non-negotiable before any southbound or cross-Texas dispatch.

Run the review within 48 hours while details are fresh. Structure it in three layers:

Unit-level: Pull the DVIR history for the cited unit going back 90 days. Was the windshield defect noted and not acted on, or is this a first appearance? If it appeared previously without a repair order being generated, you have a DVIR follow-through failure, not just a maintenance failure.

Driver-level: Review the driver's pre-trip entries for the cited day. If they signed off "satisfactory" on the windshield, that is a training and accountability issue. If they noted a defect that wasn't acted on by dispatch or maintenance, the failure is upstream.

Fleet-level: Check how many other units in the active fleet have windshield defects that are open, deferred, or sitting in a work-order queue. Given that 393.78 ranks #10 of 3,036 FMCSR codes by citation volume across our entire database, a single citation is more likely to be a symptom of a systemic gap than a one-off event.

Document the root-cause finding and the corrective action taken. That record protects you in a DataQs challenge and demonstrates good-faith corrective action to an auditor.

Every 393.78 citation carries a CSA severity weight of 4. That weight is then multiplied by a time-weight factor (violations in the most recent 6 months carry a 3x multiplier; months 7–12 carry 2x) before being added to your Vehicle Maintenance BASIC numerator.

Because 393.78 is OOS-eligible but has an all-time OOS rate of only 0.3% — compared to the all-FMCSR average of 31.4% — most citations do not trigger the additional OOS severity multiplier. However, volume matters: across 13 million inspections in our database, this code has accumulated 157,894 all-time citations and ranks #10 of 3,036 FMCSR codes. A fleet accumulating multiple 393.78 hits within a 24-month window will see meaningful BASIC score movement even without a single OOS event, because the violation count itself drives the percentile ranking against peer carriers.

Fleets in Illinois should note the 2.4% OOS rate for that state — an OOS event on this code adds a severity multiplier on top of the base weight of 4, accelerating BASIC impact significantly.

Our database shows Freightliner (FRHT) units account for 25,936 all-time citations under this code — more than any other make, and nearly 10,000 more than second-ranked Kenworth (KW) at 16,961. Peterbilt (PTRB) follows at 16,316. These three makes alone represent the majority of citation exposure, so if your training is prioritized, start with drivers operating those platforms.

Core training modules to build or refresh:

• What constitutes "impaired view" from an inspector's perspective — drivers systematically underestimate what qualifies. Show side-by-side photos of citable vs. non-citable conditions.
• DVIR specificity — train drivers to describe defects with location language ("crack, driver side, lower third, 4 inches, entering swept zone") not just "windshield crack noted."
• Refuse-the-unit authority — drivers must understand they have explicit authority to refuse a unit with a citable windshield defect and that doing so protects them personally from a 392.2RG fatigue/judgment pairing, which appeared in 1,663 shared inspections with this code in just the last 90 days.
• Repair vs. replace decision tree — train drivers on when a chip fill is acceptable versus when a crack requires full replacement before the unit moves.

A DataQs challenge is worth filing when you have objective evidence that the inspection finding was factually incorrect — not simply that you disagree with the inspector's judgment call. For 393.78, viable challenge grounds include:

• Repair completed before the inspection: If the windshield was replaced or repaired prior to the inspection date and the officer cited the unit anyway, a timestamped work order and photo showing the completed repair, dated before the inspection, is strong grounds.
• Unit misidentification: If the cited unit number does not match your fleet — confirm against the inspection report's VIN.
• Defect location outside the swept area: If your photo documentation shows the crack or chip was in the far corner outside the driver's sightline and the inspector's narrative is inconsistent with that, document it precisely.

Do not challenge on the basis that the defect was minor or that the driver didn't notice it. Illinois's 2.4% OOS rate and New Mexico's 1.6% rate indicate inspectors in those states are making deliberate severity assessments — an argument of "it wasn't that bad" will not succeed.

File within 90 days of the inspection date. Include: the inspection report, repair documentation, pre- and post-repair photos, and a brief factual narrative.

Run windshield-specific self-audits on a monthly cadence at minimum, and shift to bi-weekly from May through October. Here's why the data supports that timing:

Across our inspection records for the last 12 months, citation volume for 393.78 surges sharply in summer. May 2025 jumped to 3,901 citations (from 1,394 in April), and the peak was August 2025 at 4,237 citations. Volume stayed elevated through October 2025 (4,373 citations) before moderating into winter. The last 90 days recorded 9,334 citations total, and the last 12 months generated 44,990 — meaning roughly 21% of all-time citations in this code occurred in just the past year, signaling accelerating enforcement attention.

For self-audit structure:

• Monthly: Shop-level physical inspection of all units, documented with a checklist and sign-off separate from routine PM.
• Pre-summer (April): Full fleet sweep with photo documentation before volume peaks.
• Post-winter (February–March): Targeted review, as thermal cycling, ice scraping, and sand/salt road spray are primary crack-initiating events for the Freightliner, Kenworth, and Peterbilt units that dominate citation counts.

Log audit results in your maintenance system so you can demonstrate proactive identification and repair to any auditor.