Tracking IFTA Miles in States You Barely Drive Through (The Short-State Problem)

You are hauling freight from New York to Virginia on I-95. The route clips through Delaware for about 12 miles. Your driver barely notices — there is no toll booth, no weigh station, and the state-line signs blur past at highway speed. But those 12 miles matter. IFTA requires you to report every mile driven in every jurisdiction, regardless of how few miles you logged there. Omitting a state — even one you passed through in 10 minutes — is an under-reporting error that auditors are specifically trained to catch.

This is the “short-state problem,” and it affects thousands of carriers every quarter. Routes across the eastern United States routinely pass through states for as few as 5–15 miles. Drivers using manual trip sheets forget to log them. Carriers using low-frequency GPS trackers miss them entirely. The result is a mileage gap that shows up during audits as unreported jurisdiction miles — one of the most common IFTA assessment triggers.

Yes, Every Mile Counts

The IFTA Articles of Agreement are clear: a member jurisdiction is owed tax on every mile driven within its borders by a qualified motor vehicle. There is no minimum mileage threshold. If your truck drives 3 miles through a state, those 3 miles must appear on your IFTA return for that jurisdiction. If you drive through a state and report zero miles, you have under-reported — and the state has not received the fuel tax it is owed.

The tax amount on short-state miles is typically small. At an average tax rate of $0.50 per gallon and 6 MPG, 10 miles through a state generates about $0.83 in net tax. But the audit consequence of omitting those miles is disproportionate. Auditors use short-state omissions as an indicator of sloppy record-keeping, which often triggers a deeper review of your entire filing.

What Happens When You Omit a Short State

During an IFTA audit, the auditor reconstructs your travel patterns using fuel receipts, shipper/receiver addresses, toll records, and routing software (typically PC*Miler). If the auditor's reconstruction shows your truck passed through Delaware but your filing shows zero Delaware miles, the auditor will:

Flag the omission as a reporting discrepancy
Recalculate your mileage for the affected trips using their routing software
Assign estimated miles to the missing state
Reallocate miles from adjacent states to balance the total
Assess additional tax, penalty, and interest on the unreported jurisdiction miles

The penalty typically far exceeds the tax that was owed. Late-payment interest accrues from the original due date, and many jurisdictions add a flat penalty of $50–$500 per quarter for inaccurate reporting. A $0.83 tax liability can become a $200+ assessment after penalties and interest.

Common Short-State Corridors

Certain interstate routes are notorious for short state crossings. If your fleet runs any of these corridors, your drivers are passing through states that are easy to miss on manual logs:

I-95 Through Delaware

The I-95 corridor through Delaware spans approximately 12 miles between the Maryland and Pennsylvania borders. Trucks traveling between the mid-Atlantic and the Northeast cross Delaware in about 11–12 minutes at highway speed. This is the single most commonly omitted state on IFTA returns filed by East Coast carriers. Delaware's IFTA auditors are well aware of this pattern and routinely cross-reference I-95 toll data with IFTA filings.

I-90 Through Indiana (Near Chicago)

The Indiana Toll Road (I-90) runs approximately 15 miles through the northwest corner of Indiana between the Illinois border and the Michigan state line near the Gary/Hammond area. Trucks heading from Chicago to Detroit or points east pass through Indiana briefly. Because the route also traverses the Chicago metro area with heavy traffic and complex interchanges, drivers focused on navigation often forget to log the Indiana state-line crossing.

I-81 Through West Virginia (Eastern Panhandle)

I-81 passes through the eastern panhandle of West Virginia for approximately 12 miles between Virginia and Maryland. The stretch runs through Martinsburg and is heavily traveled by trucks moving between the Shenandoah Valley and the I-70 corridor. Drivers frequently log Virginia and Maryland miles but omit the brief West Virginia segment.

I-70 Through West Virginia (Northern Panhandle)

The I-70 corridor clips through the northern panhandle of West Virginia for approximately 14 miles between Pennsylvania and Ohio. This is one of the busiest freight corridors in the eastern US, and the West Virginia segment is short enough that drivers often do not register the crossing on manual logs.

I-95 Through Rhode Island

I-95 runs through Rhode Island for approximately 43 miles — not as short as Delaware, but short enough that it is frequently under-reported. Carriers filing from southern New England sometimes roll Rhode Island miles into Connecticut or Massachusetts, especially when the truck makes no stops in Rhode Island.

I-10 Through the Florida Panhandle (Near Alabama)

I-10 passes through a narrow section of the Florida panhandle near Pensacola. Trucks heading from Mobile, Alabama to destinations in the Florida panhandle may cross in and out of Florida within 15–20 miles. The multiple border crossings in this area — Alabama to Florida and back — create confusion in manual logs.

I-64/I-77 Through West Virginia

West Virginia appears repeatedly on this list for good reason: its irregular shape creates multiple short-crossing opportunities. I-64 passes through the southern part of the state, and I-77 traverses the central region. Both routes intersect state borders in ways that create 10–30 mile segments that manual loggers frequently omit.

I-84 Through a Corner of Pennsylvania

I-84 clips through the northeast corner of Pennsylvania for approximately 50 miles between New York and Connecticut via the Scranton area. While not as short as some other crossings, the route feels like a continuous Northeast corridor trip, and drivers sometimes fail to separate the Pennsylvania segment from the New York and Connecticut portions.

How GPS Catches Short-State Miles Automatically

GPS-based IFTA tracking eliminates the short-state problem entirely — if the sampling rate is frequent enough. Here is why:

A GPS app recording coordinates every 10–30 seconds captures your position approximately every 950–2,850 feet at highway speed. A 12-mile transit through Delaware produces 24–72 GPS readings within the state. Each reading is automatically compared against state boundary polygons using point-in-polygon detection. The system detects the crossing into Delaware, logs miles while in Delaware, and detects the crossing out — all without any driver input.

The driver does not need to notice the state-line sign. The driver does not need to record an odometer reading. The driver does not even need to know which state they are in. The GPS and the algorithm handle it automatically.

When GPS Can Miss Short States

GPS tracking can miss short-state crossings if the sampling rate is too low. An app or device that only records a position every 5 minutes captures a GPS point roughly every 5.4 miles at highway speed. In a 12-mile state transit, it might capture only 1–2 points in the state — or, if the timing is unlucky, zero. With no GPS points in the state, the system may not detect the crossing at all.

This is why sampling rate is one of the most important factors when evaluating IFTA tracking apps. An app that samples every 30 seconds will never miss a 12-mile state crossing. An app that samples every 5 minutes might miss it 10–20% of the time.

Manual Logs and the Short-State Gap

Drivers using paper trip sheets or manual mileage logs are the most likely to miss short-state miles. The failure mode is simple and understandable:

Distraction at the border: State-line signs on interstates are small and easy to miss, especially in heavy traffic, bad weather, or unfamiliar territory
Forgetting to record: Even if the driver notices the crossing, the act of pulling out a trip sheet, recording the odometer, and noting the state requires conscious effort — effort that competes with driving safely
Intentional omission: Some drivers deliberately skip short states because the paperwork seems disproportionate to the miles driven — “I was only in Delaware for 10 minutes, why bother?”
Multi-state metro areas: In regions where state borders run through metropolitan areas (Kansas City, New York/New Jersey, Memphis, St. Louis), drivers may cross state lines multiple times during local deliveries without recording each crossing

Studies of IFTA audit adjustments consistently show that under-reported short-state miles are among the top three reasons for audit assessments. It is not that carriers intentionally cheat — it is that manual tracking makes it genuinely difficult to capture every short crossing accurately.

The Audit Risk of Omitting Short States

IFTA auditors have access to tools that make short-state omissions easy to detect:

Routing software: Auditors enter your origin/destination pairs into PC*Miler or similar software to calculate the expected route, including all states traversed. If the software shows your route passed through a state you did not report, it triggers further investigation.
Fuel receipt locations: If you purchased fuel in Maryland and later in Pennsylvania, but reported no Delaware miles, the auditor knows you most likely drove I-95 through Delaware between those fuel stops.
Toll records: States like Delaware and West Virginia can access toll records from the I-95 and I-70/I-77 corridors. A toll transaction in Delaware proves you drove through the state.
Pattern analysis: Auditors compare your mileage distribution against industry averages for similar carriers. If every other carrier running your lanes reports Delaware miles and you do not, the pattern is obvious.

The likelihood of getting caught omitting a short state is high, and the trend is increasing as auditors gain access to more electronic data sources. The best defense is not hoping the auditor misses it — it is accurately reporting every mile in every state.

How to Fix Short-State Gaps in Your Records

If you discover that your historical filings omitted short-state miles, you have options:

File amended returns. IFTA allows carriers to file amended quarterly returns to correct errors. If you realize that your last four quarters omitted Delaware miles, you can amend those returns to add the missing jurisdiction. You will owe the additional tax plus interest from the original due date, but you avoid the penalty for inaccurate reporting.
Switch to GPS tracking going forward. The fastest way to eliminate short-state gaps is to adopt a GPS-based tracking system that captures every crossing automatically. This corrects the problem for all future filings without requiring driver behavior change.
Add state-line checkpoints to driver procedures. If you continue using manual logs, provide drivers with a list of short-state crossings on their regular routes. A simple laminated card listing “I-95: Remember to log Delaware” serves as a reminder at the critical moment.
Cross-reference with routing software. Before filing each quarter, run your trip origins and destinations through routing software to identify states your trucks should have traversed. Compare the routing output to your reported jurisdictions. Missing states indicate trips where the driver may have forgotten a short-state entry.

Real-World Example: The Delaware Problem

Consider a carrier based in New Jersey that runs regular loads to Washington, D.C. The standard route is I-95 south through Philadelphia, across Delaware (12 miles), through Maryland, and into D.C. The carrier makes this run 3 times per week, 13 weeks per quarter — 39 trips through Delaware each quarter.

If the driver logs the trip manually and consistently forgets to record the Delaware crossing, the quarterly filing omits approximately 468 Delaware miles (39 trips x 12 miles). At Delaware's diesel tax rate of approximately $0.22 per gallon and 6 MPG, the unreported tax is about $17.16 per quarter — a small amount.

But during an audit covering 4 quarters, the auditor finds 1,872 unreported Delaware miles. The additional tax is approximately $68.64, but the assessment includes:

Tax owed: $68.64
Interest (typically 1% per month from original due date): ~$24.71
Penalty for inaccurate reporting: $200 per quarter x 4 = $800
Total assessment: ~$893.35

The penalty alone is over 11 times the tax that was owed. And this is for a single omitted state on a single route. Carriers running multiple routes with multiple short-state crossings can face assessments in the thousands of dollars.

Frequently Asked Questions

Is there a minimum number of miles before I have to report a state on IFTA?

No. IFTA has no minimum mileage threshold. If your truck drives 1 mile in a state, that mile must be reported on your quarterly return for that jurisdiction. Every mile counts, regardless of how briefly the truck was in the state.

What if I am not sure whether my route actually entered a state?

Use routing software (PC*Miler, Google Maps, or similar) to trace your exact route between origin and destination. The software will show every state the route passes through, including short crossings. If the route enters a state for any distance, report those miles. When in doubt, report the state — it is better to report a few extra jurisdiction miles than to omit a state entirely.

Do Canadian provinces have the same short-crossing issue?

Yes, though it is less common because Canadian provinces are generally larger. Cross-border carriers traveling between Ontario and Quebec or between Manitoba and Saskatchewan can encounter short-province crossings on certain routes. The IFTA reporting requirement is the same: every kilometer in every jurisdiction must be reported.

Can an IFTA auditor really tell if I missed a 10-mile state crossing?

Yes. Auditors use routing software to calculate expected routes based on your trip origins and destinations. If the expected route passes through a state you did not report, the discrepancy is flagged automatically. Auditors also cross-reference toll records and fuel receipts that place your truck in or near the missing state. The detection tools are sophisticated and improving every year.

Will GPS tracking completely solve the short-state problem?

GPS tracking with a sampling rate of 30 seconds or less will catch every short-state crossing on your regular routes. The only scenario where GPS might miss a crossing is if the device is not running (app closed, phone dead, tracker unplugged). As long as the tracking system is active for every trip, short-state omissions are eliminated entirely.

Bottom Line

Short-state miles are the most commonly under-reported component of IFTA filings — and one of the easiest problems for auditors to detect. Routes that clip through Delaware, West Virginia's panhandles, the Indiana Toll Road, and similar corridors generate legitimate tax obligations that must be reported regardless of how few miles are involved. Manual trip sheets make short-state omissions almost inevitable because they rely on the driver noticing and recording every brief crossing. GPS-based tracking with frequent sampling eliminates the problem entirely by detecting state crossings automatically, without any driver action at the border. If your fleet runs routes with known short-state crossings, switching to a GPS-based IFTA app like FleetCollect is the most reliable way to ensure every mile in every state appears on your quarterly return — keeping you compliant and protected if an audit comes.