How to read an FMCSA carrier record, field by field

An FMCSA record looks like one document. It is really four separate files stitched together, maintained on different schedules, answering different questions. Reading it well means knowing which file you are looking at.

Operating authority

The question it answers: may this entity legally haul regulated freight for hire in interstate commerce?

Across live records the status split is roughly:

Pending is the field most often misread. Roughly one entity in four with an authority record is Pending, not Active. It looks like progress and is not permission.

Each status carries a reason code, which is where the useful detail lives:

• GRANTED — first issued
• REINSTATED — was inactive, now restored. Worth a look at why it lapsed
• Revoked — pulled by FMCSA
• Voluntary Suspension — the carrier asked
• `Involuntary Suspension - insurance cancellation effective; no active insurance meeting

minimum coverage on file` — the single most common enforcement reason

That last string is FMCSA describing the failure mode in its own words. It appears about 2,090 times in three months of records.

What it does not tell you: whether the carrier is insured *today*. Different file.

Insurance on file

The question it answers: what financial-responsibility filings has an insurer submitted on this carrier's behalf?

Read three things, in this order:

1. Form code. BMC-91X, BMC-91, BMC-82, BMC-35 satisfy the liability requirement. BMC-34 is cargo. BMC-84/BMC-85 are broker bonds 2. Class. Primary or excess. An excess layer alone satisfies nothing 3. Status. A policy listed in the active table may still have been cancelled — the cancellation is a separate record keyed by policy number

The amounts cluster hard: $750,000 on about 50,674 filings, $1,000,000 on about 24,982. That first figure is the federal minimum for general freight, unchanged since 1980.

What it does not tell you: whether the premium was paid, whether coverage applies to your specific load, or whether the certificate you were emailed is genuine. Full form-code breakdown.

Registration (the MCS-150)

The question it answers: what did the carrier tell FMCSA about itself, and when?

Fleet size, driver count, address, phone, cargo types, operation class. Carriers must update it every two years.

Read the date before the numbers. A power-unit count from a filing four years old describes a company that may no longer exist in that shape. The registration section is self-reported and stale by design — it is the least authoritative part of the record, and it looks the most like hard data.

Two fields that do earn attention:

• Operation class — Interstate vs intrastate. An intrastate carrier cannot legally take

your interstate load regardless of everything else

• Classification — "Authorized For Hire" versus "Private Property". A private fleet

hauls its own goods

Activity history

The question it answers: has this pattern happened before?

This is the section that rewards reading. A single cancellation is common — 460,122 carriers have exactly one in their history. What stands out is the shape:

A carrier with six or more lapses is not unlucky. That is a pattern, and it is visible only if you look at history rather than current status.

The four questions worth asking of any record

1. Is authority Active — not Pending, not recently reinstated? 2. Is there primary liability on file today, at the limit you require, not cancelled? 3. Is this a carrier or a broker — does a BMC-84/BMC-85 appear? 4. What does the history look like — first lapse, or the seventh?

Answering those four takes a minute per carrier and catches most of what the record can catch.

What no record can settle

Whether the person emailing you is the company on the page. Whether they intend to run the load themselves. Whether the truck that arrives is theirs.

Those are phone calls, and no amount of public data replaces them.

FMCSA filings can also be delayed, duplicated or wrong — we measure roughly 7% duplicate rows in the raw feeds. Treat a clean record as evidence, not proof.