A vehicle model year before 2000 shown by registration or VIN can establish the federal ELD exception; FMCSA also accepts a pre-2000 engine in a newer registered vehicle. Keep reliable vehicle and engine records.
What this means for your fleet
Create an exception file for each affected power unit with vehicle and engine evidence, replacement history, the rule basis, and the alternate record workflow the driver will use. Recheck the file after an engine change.
Two ways model year can establish the exception
A vehicle model year before 2000 shown by registration or VIN can establish the federal ELD exception. FMCSA also accepts a pre-2000 engine installed in a newer registered vehicle. Keep vehicle and engine-change documentation at the carrier’s principal place of business. The exception is from the ELD requirement, not automatically from HOS or RODS duties.
What to check
Use these checks before changing a log, policy, device, integration, or buying decision.
| Check | How to verify |
|---|---|
| 1. Identify vehicle and engine model years | Keep both vehicle and engine model-year records; which evidence establishes the exception depends on the exact vehicle and engine facts. |
| 2. Retain registration VIN and engine documentation | Retain the registration, VIN record, engine plate or manufacturer record, and a dated match to the assigned vehicle. |
| 3. Review replacement-engine history | Document replacement-engine work, engine model year, invoices or manufacturer evidence, and the reviewer conclusion. |
| 4. Define the alternate record method | Name the alternate RODS method, required forms, retention location, responsible person, and a completed sample day. |
| 5. Train dispatch not to assume from appearance | Use a dispatch rule that requires documented engine-year evidence before assigning the alternate record method. |
Common failure modes
- Ignoring a qualifying pre-2000 vehicle model year.
- Losing replacement-engine records.
- Assuming exempt from ELD means exempt from HOS.
Limits and exceptions
This guide does not decide a fact-specific legal exception, certify a record, or guarantee a compliance, safety, cost, or audit outcome. Keep the original ELD record and any edit history. Use the current official rule for applicability and the exact installed-device manual for screen-by-screen actions.
Sources, review date, and limits
Reviewed August 10, 2026. Each source supports only the point described beside it. Rules and product details can change; recheck dynamic facts before changing a fleet workflow or signing a contract.
- Official supporting-documents FAQ covering categories, quantity rules, six-month retention, and pre-2000 engine evidence — Federal Motor Carrier Safety Administration.
- Official ELD exceptions and exemptions FAQ — Federal Motor Carrier Safety Administration.
- Current 49 CFR Part 395 text covering HOS limits, exceptions, RODS, supporting documents, ELD duties, and technical requirements — Office of the Federal Register and U.S. Government Publishing Office.
- Current first-party product, plan, feature, and support representations; dynamic facts require release-date recheck — Factor ELD.
Review the exact operation
Bring the driver, vehicle, trip, jurisdiction, current official rule, and original ELD record for a qualified determination. Factor ELD can demonstrate its current product; rule applicability remains a fleet compliance decision.