The MC# Tenure Rule: Why Carriers Under 18 Months Are a 2× Crash Multiplier

I've turned down a lot of loads over a low MC# tenure. I've also taken a few. The pattern that keeps showing up in the data — and the pattern plaintiff's lawyers love to put in front of juries — is that brand-new carriers crash at a meaningfully higher rate than established ones, and the gap doesn't close as fast as anyone expected.

This isn't theory. FMCSA ran the analysis internally and the headline number is stark: motor carriers operating within 24 months of *graduating* the new-entrant program had **roughly two times more total crashes and nearly two times more fatal crashes per 100 power units** compared to a control group of established carriers. That's after they passed the safety audit. The risk doesn't reset when the new-entrant flag comes off — it just stops being shown.

If you're building a carrier file post-*Montgomery*, that single statistic should change how you look at any MC# under about 18 months. Not "automatic decline." Just "additional vetting required, and document it."

What the FMCSA new-entrant program actually is

When a new motor carrier registers, FMCSA puts them in a probationary program under 49 CFR Part 385, Subpart D. For 18 months they're subject to enhanced monitoring, may get a safety audit visit, and have to demonstrate basic compliance: hours-of-service records, driver qualification files, vehicle maintenance, drug & alcohol program, accident register. If they make it through without disqualifying findings, they "graduate" out of the program and lose the new-entrant flag.

The graduation does not mean the carrier is safe. It means they passed a baseline compliance check. FMCSA's own analysis found that even carriers that *passed* the audit went on to crash at roughly twice the rate of peers in the following two years.

There are a few reasons why. New carriers have less management depth, less driver retention, less capital cushion when something breaks. Their safety culture isn't tested by years of incident debriefs. They're often financially squeezed, which pushes some of them toward longer hours, deferred maintenance, or hiring drivers other carriers wouldn't take. None of that is true of every new carrier — but it's true on average.

The 18-month rule of thumb, more carefully

A lot of brokers (me included) use 18 months of authority as a soft threshold. It's not a federal rule. It maps roughly to the new-entrant graduation window plus a small buffer. It's a heuristic.

The heuristic works better when you separate it into two questions:

One: How long has the carrier held its current FMCSA operating authority? You can pull this from SAFER or from the FMCSA L&I record (the docket history shows authority grant dates and any revocations). Under 18 months is the bucket where the FMCSA new-entrant data is most directly relevant.

Two: What is the experience of the *people* running the carrier? This matters more than the authority date and it's where the heuristic breaks down. A carrier with a 14-month-old MC# whose officers and key drivers all came from a 20-year-old company that was just restructured is not the same risk profile as a 14-month-old carrier with first-time owners and rookie drivers.

The first carrier is on the new-entrant clock. The second is in the FMCSA crash data.

The chameleon problem

This is where the new-entrant question intersects with fraud. A "chameleon" carrier is one that lets its old authority go dormant after a bad safety record (or revocation, or insurance non-renewal) and re-registers under a fresh MC# with the same officers, the same equipment, sometimes the same drivers. They look like a new entrant. They aren't.

FMCSA tries to catch these. There's a list of vetting checks the agency uses — same officers, same address, same VINs across applications, similar names. It catches some. It misses some, and the ones that get through arrive at your desk looking like clean 8-month-old MC#s.

Three quick things to check on any MC# under 18 months:

• Officer history. SAFER doesn't show officer names directly, but the BMC-91 / 91X filings on L&I list the named insured. If the named insured matches a recently-cancelled or revoked carrier, that's worth a phone call. Some commercial vetting tools have officer-history lookups; if you don't have one, ask the carrier directly for their owners' prior authority history and put it in the file.
• Equipment age vs. authority age. A 9-month-old MC# operating five 2008-model-year sleepers is doing one of two things. Either they're an owner-operator who just stepped off another carrier (legitimate, easy to verify), or they're a chameleon with the prior carrier's iron. Ask. Document.
• Driver hiring lag. A carrier that's been in business 11 months and is hiring drivers off Indeed every week is a different operational profile from one that brought a stable driver group with them.

A concrete scenario

You're a broker. A 13-month-old carrier — MC-1402189 / DOT-3712840 — wants to haul a 38,000-lb dry van load from Atlanta to Newark for you. Rate is $2.55/mile, market is paying $2.35. Cheap rate plus new authority is the textbook pattern that gets brokers sued.

What do I do? I pick up the phone. Not the carrier's dispatcher number — the number listed on the BMC-91 filing for the named insured. I confirm the insurance is real, in good standing, and the named insured matches the MC#. I ask the carrier directly about their officers' prior authority history — names, prior MC#s, why they left. I look at the BASICs (probably "Insufficient Data" across most categories, which is its own signal). I look at MCS-150 — is it current, do the truck/driver counts make sense.

Then I make a call. If everything checks and the rate gap is explainable by current capacity, I take the load. I write a short one-paragraph rationale into the carrier file: tenure, what I checked, what convinced me, what mitigation steps I required (a signed safety attestation, a verified ACORD 25, etc.).

If something doesn't check — owner won't give a straight answer on prior authority, equipment doesn't match the authority age, ACORD producer can't confirm the policy — I pass. And I document why.

The regulation, in plain English

49 CFR Part 385, Subpart D is the new-entrant safety assurance program. The audit covers Parts 382 (drug/alcohol), 391 (driver qualification), 395 (HOS), 396 (inspection/repair/maintenance), and 387 (insurance). Passing the audit means the carrier had baseline compliance on the day FMCSA looked. It does not mean the carrier is safe on the day you tender.

At load-tender time, the implication is that a new-entrant graduation date is a *data point*, not an answer. The data point you actually need is the carrier's BASIC trend and crash history during and after the new-entrant period — and for very new carriers, that data won't exist yet. Which puts the diligence weight on the things that *can* be checked: officers, equipment, insurance verification, and a contractual safety attestation.

How I document this

For any carrier with authority under 18 months I add four lines to the file beyond the normal vetting:

1. **Authority grant date** with source (FMCSA L&I docket entry, screenshot timestamped).

2. **Stated officer prior authority history** as told to me on a recorded call or written response — with a verification check against L&I where possible.

3. **Reasoned tender decision**: tenure noted, mitigation steps required (e.g., enhanced attestation, certificate-holder verified ACORD 25, no high-value cargo on the first load).

4. **Whatever I'm relying on to deem them safe**: a satisfactory pre-trip attestation, a phone confirmation with the insurance agent, a clean L&I record, etc. — the actual basis of the decision.

When that file lands in front of a plaintiff's lawyer two years from now, the difference between "I just ran the MC#" and "I ran the MC#, found 13 months of authority, asked the following six questions, got the following answers, required the following attestation, and tendered" is the difference between an indefensible record and a defensible one.

— Mason Lavallet

Founder, DOTScreener.com

---

Sources

• [FreightWaves — FMCSA data shows rise in crash rates among new-entrant carriers](https://www.freightwaves.com/news/fmcsa-data-shows-rise-in-crash-rates-aomng-new-entrant-carriers) — analysis of the FMCSA internal data
• [49 CFR Part 385 Subpart D — New Entrant Safety Assurance Program](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-385/subpart-D)
• [FMCSA — Safety Audits and New Entrant Program Overview](https://www.fmcsa.dot.gov/registration/get-mc-number-authority-operate)
• [American Transportation Research Institute (ATRI) — research on new-entrant carrier safety](https://truckingresearch.org/)
• [Hanson Bridgett — Montgomery v. Caribe Transport II analysis](https://www.hansonbridgett.com/publication/260514_8509_supreme-court-faaaa)