USDOT 4353234 · Regional & Local Freight Specialists
Sultan Freight Logistics box truck in the yard illustrating the English proficiency out-of-service rule 2026 and driver qualification in NJ and NY
Compliance

The English Proficiency Out-of-Service Rule 2026: What FMCSA Proposed and How to Comment

Regla de inglés out of service 2026: qué propuso FMCSA y cómo comentar

Por Sultan Freight Editorial9 min de lectura

On August 10, 2026, FMCSA published a proposed rule that would write the English language proficiency requirement into the federal regulations as an out-of-service condition. The English proficiency out-of-service rule 2026 does not create a new requirement — the requirement has existed since 1936. What it changes is permanence: it moves roadside enforcement from agency policy into the regulation itself. The public comment window closes October 9, 2026, and FMCSA asked specific questions it wants carriers to answer. For fleets running NJ, NY and the Northeast, this is one of the few moments where a small carrier's operating data is worth as much to the agency as a trade association's brief.

What FMCSA actually proposed

The Notice of Proposed Rulemaking sits under Docket No. FMCSA-2026-0826. It responds to a petition from the Commercial Vehicle Safety Alliance (CVSA) and aligns the Federal Motor Carrier Safety Regulations with the enforcement tolerances already in the North American Standard Out-of-Service Criteria. Three sections would change:

SectionProposed changePractical effect
49 CFR 390.5 and 390.5TRevise the definition of "out-of-service order" to include 391.11(b)(2)An ELP violation becomes an OOS condition in the regulation, not just in CVSA criteria
49 CFR 391.11, new paragraph (c)A driver violating (b)(2) must be placed out of service immediatelyRemoves inspector discretion; makes the outcome uniform across states
Border zone exceptionLimited carve-out for trips confined to U.S.–Mexico commercial zonesViolation still cited, but no OOS order for qualifying trips

Source: Federal Register document 2026-16288, published August 10, 2026. Docket No. FMCSA-2026-0826.

The quiet consequence is in the plumbing. Because states participating in the Motor Carrier Safety Assistance Program must adopt requirements compatible with the FMCSR, codifying the rule means enforcement survives any future change to CVSA's criteria. Policy can be rescinded with a memo. A regulation takes another rulemaking.

The requirement itself is 90 years old

The Interstate Commerce Commission first required in December 1936 that drivers in interstate commerce read and speak English well enough to understand traffic and warning signs. It was recodified through the Motor Carrier Safety Act of 1984 and now lives at 49 CFR 391.11(b)(2). A qualified driver must be able to converse with the general public, understand highway traffic signs and signals in English, respond to official inquiries, and make entries on reports and records.

What changed over the years was never the standard — it was the consequence at roadside:

DateWhat happenedRoadside outcome
Dec 1936ICC establishes the English requirementDriver qualification standard
Apr 2005CVSA adds ELP to the OOS criteriaOut of service
Apr 2015CVSA removes ELP from the OOS criteriaViolation only
Jun 2016FMCSA policy memo: cite, do not place OOSViolation only
Jun 25, 2025CVSA restores ELP to the OOS criteriaOut of service
Aug 10, 2026FMCSA proposes to codify it in the FMCSRComment period open until Oct 9
Enforcement has been live since June 25, 2025. The comment period is about whether it becomes permanent — not about whether it starts.

That distinction matters for planning. Since June 2025, more than 20,000 drivers have received ELP-related out-of-service orders according to enforcement data tracked by Trucksafe; some press reporting puts the figure higher. Whatever the final number, a carrier waiting for the rule to be finalized before acting has already been exposed for fifteen months.

The border commercial zone exception, and its limit

Read this one carefully. Under the proposal, a driver in violation of the ELP requirement is not placed out of service if their current trip is confined to the U.S.–Mexico border commercial zones designated in 49 CFR Part 372, Subpart B. The exception attaches to the trip, not to the driver. If bills of lading, dispatch records, equipment interchange receipts or the driver's own statements show the trip continues beyond those zones, the OOS order applies. The violation is still cited either way.

For a Northeast carrier this exception is essentially academic — but it explains why FMCSA is asking for cost data, and it is the part of the proposal where the agency has admitted it is least sure of its own numbers.

How to file a comment before October 9, 2026

A docket comment is not a petition or a vote. It is evidence entered into a record the agency must consider and respond to. Comments carrying operational data from a working carrier are weighted differently than comments carrying opinion, and FMCSA said plainly which data it lacks.

  1. Answer what the agency asked. FMCSA specifically requested comment on the validity of its methodology for estimating how many drivers are affected in border commercial zones, on the average time and cost to dispatch a replacement driver when one is placed out of service, and on any cost impacts it has not accounted for.
  2. Bring your own numbers. If you have ever had to recover a load after a driver was sidelined, you know the real cost: the replacement driver's time, the deadhead, the layover, the detention at the receiver, the missed appointment. That figure, from your own operation, is exactly the input FMCSA said it is missing.
  3. File online. Go to regulations.gov, Docket FMCSA-2026-0826 and use the comment button. Comments are public.
  4. Or file by mail. Dockets Operations, U.S. Department of Transportation, 1200 New Jersey Avenue S.E., W58-213, Washington, D.C. 20590-0001. Reference the docket number.
  5. Or file by fax. (202) 493-2251, same docket reference.
What weakens a comment. Three things: submitting after the deadline, arguing a position without a number attached, and commenting on a question the docket did not ask. The record closes October 9. A one-page comment with a real cost figure from a one-truck operation is worth more to the record than five pages of general argument.

What a carrier should do regardless of the outcome

The rule may be finalized, modified or withdrawn. The enforcement posture does not depend on that. Practical steps:

  1. Treat ELP as a driver qualification item. It belongs in the DQ file process next to the CDL, the medical certificate and the MVR. FMCSA published guidance in May 2025 on assessing it during qualification.
  2. Document the assessment. FMCSA does not prescribe a test. What protects a carrier in a compliance review is a consistent, written, repeatable process — not a particular score.
  3. Brief dispatch. Dispatching a driver who cannot meet the requirement is a compliance exposure and a liability exposure at once.
  4. Check it at hire, not at roadside. The cost of finding out during a Level 1 inspection is the load, the appointment and the relationship with the shipper. We covered the inspection side of this in our note on Operation Safe Driver Week.

Our July piece on English language proficiency and the CDL covers what the roadside assessment looks like in practice. For the broader 2026 regulatory picture, see the FMCSA rule changes that took effect in July.

The honest read

This proposal does not change what is required of a driver today. It changes how hard that requirement is to undo, and it hands carriers a twenty-day window to put real operating costs into a federal record that currently contains an estimate the agency itself flagged as uncertain. Most small carriers will let the window close without filing. The ones who file with a number will be the only small carriers in the record.

Running freight in NJ, NY or the Northeast?

Sultan Freight Logistics moves regional and local freight out of Newark. If you want your driver qualification and compliance files organized before an audit finds the gap, start with CarrierShield.

See CarrierShield →