MCS-150 Mileage Reporting Explained — What Goes in the Box

The mileage line on MCS-150 confuses more carriers than any other field on the form. It is one number on a single line, but the FMCSA cross-references it against IFTA reports, roadside inspection data, and ELD exports under §390.21, and a wrong number here can flag the carrier for an audit two cycles later and surface a stale year on SAFER. This guide explains exactly what to report, where to pull it from, and how the FMCSA reads the result.

What the Mileage Line Asks For

MCS-150 asks for total vehicle miles traveled (VMT) by your fleet during the most recent full calendar year. The number reported is one aggregate figure for the entire USDOT — not per-truck, not per-state, not split by category. Every USDOT-registered power unit you operated during that year contributes its miles to the same total.

The form does not ask you to break out:

• Loaded vs empty miles — both count.
• Interstate vs intrastate miles — both count.
• IFTA vs non-IFTA jurisdictions — both count.
• On-duty vs personal-conveyance miles — both count if the truck is registered under the USDOT.
• Miles by individual driver — the form does not segment by driver.

Where to Pull the Number From

Three sources deliver clean fleet-level VMT, in rough order of cleanliness:

Best: ELD export

Modern ELD platforms (Motive, Samsara, Geotab, Omnitracs, etc.) aggregate every truck's odometer movement at the fleet level. Run a calendar-year report for the prior year, sum the odometer deltas across every active power unit, and you have the number. ELD reports also tie back cleanly to IFTA filings, which means the MCS-150 number reconciles to your other regulatory data on its own.

Solid: IFTA quarterly returns

IFTA quarterly returns include total miles in IFTA jurisdictions for every IFTA-registered power unit. Sum the four quarters of the prior calendar year and you have most of the picture. The gap is non-IFTA miles — if your fleet has trucks below 26,001 lbs GVWR, or operates outside IFTA jurisdictions (Alaska, Hawaii, foreign territories), those miles are missing from IFTA totals and need to be added separately from odometer or ELD data.

Workable: Odometer readings

For carriers without ELD or IFTA filings (small intrastate fleets, lighter vehicles), the fall-back is direct odometer reads on each truck. Capture the odometer at January 1 and December 31 of the calendar year, subtract, and add across the fleet. This is the most error-prone method because trucks sold/bought/leased mid-year complicate the math — if a truck was acquired in March, you need its odometer reading on the day it joined the fleet, not January 1.

Special Cases

New entrants in their first year

If your USDOT was issued in the calendar year just ended, report actual miles from the activation date through December 31. Do not annualize, do not extrapolate, and do not put zero unless the USDOT was activated within 30 days of the calendar year-end and no operations occurred. The FMCSA understands a partial-year number for a new entrant — it does not understand a 100,000 flat-rate placeholder for a fleet that only ran for two months.

Brokers and freight forwarders

Pure brokers and freight forwarders (no operated power units) put zero. The mileage line is irrelevant to a broker's record — the FMCSA expects zero or a blank. Hybrid carriers who broker some loads and run some loads themselves report only the miles run on their own equipment.

Leased equipment

Miles run by power units leased to your USDOT count toward your MCS-150 total for the period the lease was active. Miles run by trucks you leased out to another carrier (operating under their USDOT during that window) do not. The rule follows operational control, not legal title.

Owner-operators leased to a carrier

If you operate under your own USDOT for some loads and lease to a larger carrier for others, only count the miles run under your own USDOT. Miles run while under the lessor's authority show up on their MCS-150, not yours.

How the FMCSA Reads the Number

Three things happen with your reported VMT:

1. Cross-checked against IFTA. The FMCSA shares data with state IFTA offices. A number wildly different from your sum-of-IFTA-quarterlies flags as inconsistent and increases compliance-review risk.
2. Cross-checked against roadside inspection density. A fleet reporting 50,000 fleet-miles but showing up at 40 roadside inspections in high-traffic states reads as under-reported.
3. Used in CSA / Safety Measurement System normalization.CSA scores divide certain violation counts by miles to produce a per-mile rate. Under-reporting miles inflates the rate — which raises your CSA score, which raises insurance premiums.

Common Mileage Mistakes

• Round numbers. 100,000 flat. 250,000 flat. The FMCSA reads suspiciously round numbers as placeholders.
• Per-truck instead of fleet total. Reporting 100,000 when the fleet is six trucks each running 100,000 miles is a 600,000-mile under-report.
• Forgetting trucks sold mid-year. A truck that ran 60,000 miles before being sold in August still contributes those 60,000 miles to the total.
• Forgetting empty/deadhead miles. Some carriers report “loaded miles only.” The form does not ask for that — total VMT includes empty miles.

Documenting Mileage for an Audit

Under §390.21, the FMCSA can request supporting documentation for any number on the MCS-150 during a compliance review or new-entrant safety audit. Mileage is the line auditors most often ask to substantiate. The supporting evidence the FMCSA will accept:

• ELD platform export showing per-unit annual VMT for the calendar year reported.
• Sum of IFTA quarterly returns plus an explanation of any non-IFTA miles added separately.
• Per-unit odometer logs (start-of-year and end-of-year readings) for every power unit.
• Maintenance work orders that show odometer readings at service intervals, used to triangulate when other sources are missing.

Keep this evidence in your compliance file for at least three years past each biennial filing — the FMCSA can audit a filing at any point during its useful life, and an audit dating back two cycles is uncommon but not unprecedented.

Mileage and CSA Scoring

The MCS-150 mileage line directly affects CSA scoring through the Power-Unit-Miles (PUM) normalization in the Safety Measurement System. CSA divides certain BASIC violation counts by power-unit-miles to produce a comparable rate across carriers of different sizes:

• Under-reporting miles inflates the rate. A carrier reporting 400,000 miles when the real number is 800,000 effectively doubles its calculated violation density. Each violation event counts twice as much against the CSA score.
• Over-reporting miles deflates the rate. Sometimes intentionally, sometimes from estimation errors. The FMCSA detects this through IFTA cross-reference and treats it as a misrepresentation.
• Honest reporting is the lowest-risk play. CSA scores are bounded; you do not get below zero by inflating mileage, and you create audit risk by under-reporting it. The mileage that matches your IFTA / ELD record is the right answer.

Mid-Cycle Mileage Updates

Mileage on its own does not require an out-of-cycle MCS-150. The §390.19 triggers (address change, name change, fleet change, operation type change) cover identity and structure but not the prior calendar year's VMT. If you realize after submission that the mileage figure was wrong, file a corrective MCS-150 at any time — the URS portal accepts re-submissions and the most recent filing supersedes prior ones. The corrective update does not reset the biennial schedule.

State-Level Mileage Filings vs MCS-150

Several states require carriers to report mileage separately for state-level weight-distance taxes — Kentucky KYU, New Mexico, New York HUT, Oregon weight-mile. Those filings serve a different purpose (state tax revenue) and capture state-specific miles only. The MCS-150 number should equal or exceed the sum of those state-level reports for any given period; if the MCS-150 total is lower than what a single state reports for that same year, something is misreported on one of the two filings.

Bottom line: Pull total fleet-level VMT from ELD or IFTA records for the prior calendar year. Include empty miles, every jurisdiction, and every USDOT-registered power unit. Avoid round numbers and report what your operational data actually shows.