The FMCSA Company Census File: What a Carrier Record Contains

Who appears in the file

FMCSA says the file contains active, pending and inactive registered entities. That population extends beyond interstate freight carriers: it includes entities subject to different federal requirements and some intrastate carriers. A count of census records is therefore not a count of freight carriers available for a broker’s load.

The agency documents exclusions, including shipper-only businesses and entities with an active Hazardous Materials Safety Permit in the specified systems. Read the current coverage statement before interpreting an absent record or estimating the size of a market.

Sources: FMCSA Open Data Program

Identity fields come first

Use the USDOT number as the carrier-record identifier. Compare the legal name, DBA and complete address with the entity on the carrier packet. Preserve physical and mailing addresses separately; substituting one for the other can create a false discrepancy or an unjustified match.

When linking census data to state filings, retain the original names and addresses alongside any normalized values. Removing punctuation may help comparison. Removing unit numbers or treating a parent and operating subsidiary as interchangeable discards evidence. An ambiguous match should remain unresolved until another source establishes the relationship.

A daily file is not a live business record

FMCSA publishes the census daily from a database that is already 24 hours old. The file does not represent real-time changes, and other agency systems can follow different schedules. A broker reviewing a newly filed change should compare source dates before assuming two services disagree about the same observation.

The MCS-150 date is another clock. It identifies the carrier’s filing or update, not the precise date every field changed. FMCSA requires applicable entities to update registration information biennially, even when nothing has changed. A recent export can still contain older carrier-supplied information.

Sources: FMCSA Open Data Program; FMCSA registration updates

Fleet and mileage fields need their context

Power-unit and driver counts describe reported business scale. They do not identify the truck assigned to today’s shipment. If the carrier offers capacity that appears inconsistent with the record, ask for an explanation and verify the operating arrangement rather than treating a reported count as a dispatch system.

Keep mileage with its reporting year. Dividing recent crashes by an older mileage value can produce a precise but misleading rate. Before calculating a comparison, establish that the numerator, denominator, entity and time period are compatible. Otherwise show the underlying observations without inventing a risk score.

Read status at the correct level

An active census entity and an active authority for a particular operation are different findings. The census contains docket-status information, but a shipment decision still requires checking the appropriate authority and any relevant exemptions. A valid USDOT lookup also does not authenticate the person sending the carrier packet.

FMCSA now distinguishes modern MOTUS operating-authority datasets from archived legacy files. An integration must identify which schema it reads. A parser that successfully opens an old archive has not established current authority status.

Sources: FMCSA Open Data Program

Comparing two snapshots

Suppose a fictional carrier’s phone number differs between Monday’s and Wednesday’s files, and Tuesday’s download failed. The defensible observation is that the change appeared between the two successful snapshots. Wednesday is the detection date, not necessarily the event date.

Retain the source files, publication dates, retrieval times and changed values. A complete later snapshot can restore the current view after a missed download, but it cannot reveal every intermediate change. State that gap when presenting historical evidence or deciding which contact to verify.