Prevention FAQ — FMCSR 396.5(a): Oil/Grease Leak

Inspectors are looking for visible oil or grease leaking from the engine, transmission, differentials, axle seals, power steering components, or any other drivetrain component. A drip, wet stain, or pooling under a parked unit is enough to trigger the citation. Our inspection records show that Texas is the only state with 396.5(a) activity in the last 180 days, accounting for 2 citations with a 50.0% out-of-service rate in that window — double the national all-time average for this code of 27.0%. That elevated OOS conversion rate in Texas signals aggressive enforcement posture; drivers operating through Texas should be especially thorough on fluid-system checks before crossing state lines.

Build a dedicated fluid-leak section into your DVIR pre-trip template covering these inspection points:

• Engine oil pan and drain plug — look for wet residue or fresh staining on the skid plate or frame rails below.
• Valve cover gaskets — check for oil weeping onto exhaust components (a fire risk, not just a citation risk).
• Transmission and transfer case seals — inspect the ground directly beneath when the unit has been parked overnight; a clean patch of pavement is meaningful.
• Rear axle and differential seals — axle seal leaks show as grease smear on the inside of the wheel rim and tire sidewall.
• Power steering reservoir and hose connections — feel along hose lengths for tacky residue.
• Fifth-wheel grease application points — excess grease thrown onto frame or tires often flags fifth-wheel over-lubrication.

Drivers should document 'no visible leaks' explicitly, not just leave the field blank.

Drivers are not required to carry repair receipts, but the carrier must retain the following under 49 CFR 396:

• Driver Vehicle Inspection Reports (DVIRs) that noted the defect, signed by the driver and countersigned by a qualified mechanic confirming repair.
• Repair work orders identifying the component repaired, parts replaced, technician name, and date — retained for at least 12 months from the repair date (or 6 months after the vehicle leaves the fleet, whichever is longer).
• Periodic inspection records showing the vehicle passed inspection after the fix.

For a CSA context: 396.5(a) carries a severity weight of 3, so a clean paper trail demonstrating prompt corrective action supports any future DataQs challenge and demonstrates due diligence to auditors reviewing your Vehicle Maintenance BASIC.

Our inspection records show that in the last 90 days, 396.5(a) co-occurred with nine other codes across the same inspections. Three stand out for root-cause implications:

• 393.47E (Slack adjuster defective) — pairing with a brake adjustment defect suggests deferred maintenance culture: if adjusters are out of spec, fluid seals are likely overdue too. Treat this as a 'how long has it been since a full PM?' signal.
• 393.48A (Inoperative/defective brakes) — a brake defect alongside an oil leak points to a vehicle that may have been run past its PM interval. Brake components near leaking axle seals can experience accelerated wear from oil contamination.
• 396.3A1BOS (Brakes out of service — ≥20% defective) — this OOS-level brake finding in the same inspection as an oil leak is a strong indicator of systemic neglect. When one component is visibly failing, inspectors inspect everything more closely.

The pattern: 396.5(a) citations rarely travel alone. They surface on vehicles where PM scheduling has slipped.

A two-step return-to-service protocol is the minimum acceptable standard:

1. Static verification — with the engine off, the technician confirms the leak source is sealed: new gasket, replaced seal, or tightened fitting. The repair area is cleaned with degreaser so any future leakage is immediately visible.
2. Dynamic verification — the vehicle is run at operating temperature for at least 15 minutes. The technician then re-inspects the repaired area and checks beneath the vehicle for any new drip pattern. For axle seal repairs, a short loaded move (even yard movement) helps confirm the fix under load.

The technician countersigns the DVIR and completes a work order with part numbers. The vehicle should not depart until a second-set-of-eyes walkaround confirms the undercarriage is dry. Given that our data shows 27.0% of all 396.5(a) citations resulted in OOS placement even though the code is not OOS-eligible by rule, re-inspection is worth the extra 20 minutes.

Run a structured five-part review within 72 hours of the citation:

1. Identify the last PM date for that unit. Was the citation issued before or after the scheduled interval? If before, investigate why the leak wasn't caught on pre-trip.
2. Pull the last 30 days of DVIRs for the unit. Did any driver note 'no defects' in the fluid-leak section? If so, is that plausible given the inspector's finding?
3. Check the top-makes pattern — our database shows Freightliner (FRHT) units account for 1,505 of all 4,930 all-time citations for this code, more than any other make. If your fleet runs FRHT-branded equipment, verify whether a specific model year or engine family is overrepresented in your own internal data.
4. Review co-occurring violations from the inspection report. If brakes or lighting also appeared, widen the PM audit to similar units in the same run pool.
5. Document findings and corrective action in the maintenance file. This paper trail is critical if you later file a DataQs challenge.

396.5(a) carries a CSA severity weight of 3, placing it in the lower-to-mid tier of the severity scale. For context, our database ranks this code #342 out of 3,036 FMCSR codes by all-time citation volume at 4,930 citations, meaning it is a meaningful but not dominant source of Vehicle Maintenance BASIC points across the industry.

A severity-3 violation multiplied by the time-weight factor (most recent violations score higher) and the inspection factor accumulates in the BASIC over a 24-month rolling window. Because 396.5(a) is not OOS-eligible, the direct operational disruption is lower than, say, 396.3(a)(1) — which carries a 45.3% OOS rate across 236,919 citations in our records. However, a pattern of 396.5(a) hits signals a PM program that struggles to catch fluid leaks before inspectors do, which draws scrutiny in interventions and audits even when individual violations carry modest weight.

Our inspection records show the top five cited makes — FRHT (1,505 citations), UTIL (572), KW (465), HYTR (456), and WANC (432) — span tractors and trailers, so training must cover both.

For tractor drivers (FRHT, KW, PTRB, INTL, VOLV): train specifically on engine compartment inspection posture — not just checking the dipstick, but visually scanning the block, valve covers, and oil cooler lines. Many drivers check oil level without ever looking at the pan or front crank seal.

For trailer inspection (UTIL, HYTR, WANC, GDAN): train drivers to inspect axle seals and hub-oil sight glasses on trailer tandems. Trailer axle seals account for a significant share of grease leak findings and are routinely skipped in pre-trips.

Practical scenario training — showing drivers what a 'cite-worthy' leak looks like versus normal surface grime — is more effective than classroom-only instruction. Use photos from actual DVIR defect submissions in your fleet as training materials.

File a DataQs challenge when at least one of the following applies:

• The cited component was repaired and documented before the inspection — if a work order shows the seal was replaced within the prior 30 days and the citation was based on residual surface grime rather than an active leak, that is a factual dispute worth raising.
• The violation was recorded against the wrong vehicle — unit number or VIN mismatches are a documented source of citation errors.
• The inspection report contains a factual error — wrong regulation cited, wrong component description, or date/time discrepancy.

Do not file a challenge simply because the severity weight is low. Focus on situations where the underlying facts are genuinely wrong. A successful DataQs challenge removes the citation from the BASIC calculation entirely. Given the severity weight of 3, the BASIC point gain per citation is modest, but a cluster of 396.5(a) hits on a single unit in a short window can trigger algorithm attention, so correcting errors promptly has compounding value.

Our inspection records show only 3 citations in the last 12 months and 2 in the last 90 days for this code nationally — a very low current enforcement volume. That low recent activity does not mean the defect itself is rare; it means fewer inspectors are flagging it as the primary violation code in this period.

Recommended cadence:

• At every PM service: a clean-and-inspect protocol (degrease the engine bay and undercarriage, run to temperature, re-check) should be standard. This catches developing leaks before they become citation-level.
• Monthly shop walkarounds: designate one technician per month to do a bottom-of-the-unit visual on each active unit — 10 minutes per truck, logged.
• Post-idle audits: any vehicle that has sat more than 7 days should receive a leak check before dispatch, since seals can weep when cold-soaked.

The fact that 2 of the last 90 days' citations resulted in co-occurring brake and steering defects signals these are not isolated fluid issues — they are whole-vehicle condition problems. Monthly audits give you the earliest catch.