The MCS-150 stale-date math — how to use it for credit underwriting
What the MCS-150 is
The MCS-150 is FMCSA’s biennial census filing required of every active motor carrier with a USDOT number. It captures the carrier’s identifying information (name, address, contact), fleet size (power units, drivers), vehicle inventory (interstate/intrastate, commodity types), and operational data (annual mileage, commodities hauled, USDOT classification).
Under 49 CFR 390.19, carriers must update the MCS-150 every 24 months. The update schedule is based on the USDOT number: the last two digits determine the month, and the second-to-last digit (even or odd) determines which year of the two-year cycle. A USDOT ending in 13 updates in March of even years; one ending in 24 updates in April of odd years; etc.
Failure to update on schedule triggers an FMCSA notice. Continued failure can lead to deactivation of the USDOT — at which point the carrier is no longer registered to operate interstate.
Why the date matters for credit
For a credit underwriter, the date of the most recent MCS-150 update is one of the most useful single signals on the FMCSA record. Several reads:
1. Stale-date check vs. claimed time in business.
A common credit-fraud pattern: the credit application claims “10 years in business” but the USDOT issuance date is 18 months ago and the only MCS-150 ever filed was at registration. The numbers don’t reconcile. Either the carrier operated under a prior USDOT (chameleon pattern — see the chameleon-carrier post), or the time-in-business claim is fabricated, or the principals’ trucking experience predates the current entity.
Subtraction is the diligence step. Today minus USDOT issue date is the maximum possible time the current carrier has been operating. Anything more than that on the credit application requires explanation.
2. Currency check.
If the most recent MCS-150 is more than 24 months old, the carrier is past their update window. FMCSA may have already issued a notice. Continued non-update for another several months can result in deactivation — at which point the carrier loses interstate operating authority and the loan collateral becomes legally inoperable.
For a deal closing in the next 30 days, a stale MCS-150 is a real near-term risk. The carrier may not realize they’re past due; checking the deactivation date is part of the underwriting workflow.
3. Fleet-size consistency check.
The MCS-150 lists power units (tractors) and drivers. Compare to: - The credit application’s stated fleet size. - The number of vehicles being financed. - The insurance certificate’s listed vehicle count.
Discrepancies between these are common and almost always explainable, but the explanation needs to be on the record. A carrier financing 8 trucks who tells FMCSA they have 3 power units may be: - Under-reporting to keep insurance costs down (common, not a red flag for credit specifically). - Recently expanded and has not updated the MCS-150 (common, time-resolvable). - Misrepresenting fleet size to either FMCSA or you, take your pick.
4. Annual mileage as a revenue proxy.
The MCS-150 captures total annual mileage across the fleet. A rough revenue estimate for a general-freight carrier is $1.80-$2.50 per loaded mile (rates vary by lane and commodity). Mileage times rate gives a rough top-line revenue estimate that can be cross-referenced against the carrier’s stated revenue on the credit application.
This is rough — it doesn’t account for empty miles, brokered loads, lane mix, fuel surcharge structure — but it’s a sanity check. A carrier claiming $5M annual revenue with 200,000 reported miles is implausibly producing $25/mile, which is roughly 10x typical general-freight rates.
What “MCS-150 was last updated” actually means on SAFER
On the FMCSA SAFER record, the relevant field is “MCS-150 Form Date” (or “MCS-150 Date”). This is the date of the carrier’s most recent MCS-150 update — not the date of the carrier’s first MCS-150 filing. A carrier in business for 15 years should show an MCS-150 date within the last 24 months. One showing 2018 has not updated for 8 years; FMCSA has almost certainly sent multiple notices and the carrier is at risk of deactivation.
A small number of older inactive-but-registered carriers can show very stale MCS-150 dates because FMCSA’s deactivation process is slow. A carrier with an MCS-150 date of 2015 and current operating authority is in an administrative gray zone — technically still registered, but in violation of update requirements and at undefined risk of deactivation.
The PRISM enforcement layer
Many states use the Performance and Registration Information Systems Management (PRISM) program to coordinate carrier registration with FMCSA safety data. Under PRISM, a state can refuse to renew commercial vehicle registrations if the carrier’s USDOT is suspended or out of service. Some states refuse to renew if the MCS-150 is past due.
The practical effect: a carrier with a deeply stale MCS-150 may find itself unable to renew commercial vehicle registrations at the state DMV, which makes the equipment legally inoperable on public roads. This is the second-order risk from a stale MCS-150 — even before FMCSA deactivates the USDOT, the state may decline to renew the plates.
The new-entrant case
A carrier in the first 18 months after USDOT registration is in the “new entrant” period. During this period, the carrier must complete a safety audit. The MCS-150 is filed at registration and is current by definition for the first 24 months — the staleness check doesn’t yet apply.
What does apply: the new-entrant audit completion. The SAFER record will show whether the audit has been completed and what the result was. A new-entrant carrier with a pending or failed audit carries explicit FMCSA-enforcement risk on top of the normal credit risk.
What this means for you
The MCS-150 date is a 60-second check that surfaces multiple credit-relevant signals. Cross-reference against the USDOT issue date for time-in-business consistency, against the 24-month update window for stale-date risk, against the credit-app revenue for plausibility, and against the credit-app fleet size for consistency.
A VerifySOS lookup on a trucking deal pulls the MCS-150 date, computes the age against today, and flags stale-date and TIB-inconsistency cases automatically. Developers get the date, age-in-days, and consistency flags via /api/v1/lookup.