Logistics
FMCSA's camera-monitor request puts approval status on the fleet checklist
A fleet equipment review can move quickly from a demonstration to a purchase discussion. A regulatory application asks a different question: what has actually been authorized? FMCSA's new camera-monitor notice makes that distinction useful before a proposal becomes an operating assumption.

What the November 18 notice actually opens
FMCSA published a request for comments on Safety Vision, LLC's application to use its View Smart camera-monitor system as an alternative to two rear-vision mirrors. The application seeks a five-year exemption from 49 CFR 393.80(a). The notice identifies docket FMCSA-2026-3707 and a December 18, 2026 comment deadline.
The document is an application notice, not a grant. FMCSA says publication does not indicate its eventual decision; the agency will consider the application, safety analyses and comments before granting or denying the request. A supplier's submission and an agency's authorization therefore belong in separate fields in an equipment review.
Why the scope of a decision matters
The current eCFR text of section 393.80 contains the rear-vision mirror requirements and specified exceptions. The new notice concerns a particular requested alternative. It should not be read as a general announcement that cameras have replaced mirror requirements for every carrier or vehicle.
FMCSA's notice explains that a grant would identify the provisions covered, its effective period and its terms and conditions. For a fleet team, a useful working record would distinguish the exact document, the equipment configuration being evaluated and any unresolved applicability question. That is an operational review framework, not an interpretation of an individual carrier's legal position.
Separate a product evaluation from an operating assumption
Consider a hypothetical maintenance manager who receives a camera-monitor demonstration while reviewing replacement equipment. The demonstration might help the team define practical questions, such as where a display would sit, how a driver would report a fault or what maintenance information would need to be available. It does not, by itself, answer the authorization question.
An evaluation note can keep three tracks visible without declaring the product suitable or unsuitable. These are planning suggestions, not additional requirements imposed by the notice.
- Document status: identify whether the evidence is an application, a published agency decision or supplier material, and record when it was checked.
- Configuration: describe the vehicle and proposed installation precisely enough that a later reviewer can compare it with any applicable decision.
- Operating review: list questions about driver familiarization, fault reporting, maintenance responsibility and fallback arrangements for the responsible team to resolve.
What to watch after the comment period
A sensible follow-up is a dated review point rather than an assumed implementation date. The December 18 deadline is a deadline for comments, not an announced start date for an exemption. The published decision, if one follows, is the document that would establish the outcome of this application.
For dispatch and fleet coordination, the practical contribution is a shared record of what is known and what is still pending. A dispatcher need not turn an application headline into a vehicle-release instruction. Equipment changes can remain with the people responsible for reviewing the actual configuration and the relevant authoritative documents.
Sources
What to watch
Keep the equipment decision tied to its evidence
A clear equipment record separates the product being considered, the applicable agency decision and the checks still outstanding. This report provides general information, not legal advice or a determination that a particular vehicle or installation is authorized.
