Route deviation evidence answers a simple question with serious consequences: was the truck where it was supposed to be? In modern trucking operations, that question can be answered with more than driver testimony or dispatch notes. GPS pings, electronic logging device records, fleet-management communications, route plans, geofence alerts, dispatch instructions, and telematics reports can show where a truck traveled, when it left an assigned route, how long it remained off route, and whether the carrier had notice of the deviation.
A route deviation can involve several different scenarios. A driver may take an unauthorized shortcut through a residential area. A truck may leave a permitted oversize-load route. A hazardous-materials carrier may miss a restricted route or enter an area where its cargo should not travel. A driver may follow a consumer GPS instead of a commercial-vehicle route and end up on roads with low clearances, high-profile railroad crossings, weight limits, sharp grades, or turning geometry unsuitable for a tractor-trailer.
The evidence is powerful because it is time-stamped and location-based. It may show the truck's path before the crash, the moment it crossed into a restricted area, the dispatcher's knowledge of the event, and whether the company responded. But it must be used carefully. Electronic logging device data, fleet telematics data, and dedicated geofencing data are not the same thing. ELD records are required for hours-of-service compliance and contain location information, but their location precision is intentionally limited. Appendix A to 49 C.F.R. Part 395 states that commercial motor vehicle position measurement must be accurate to within ±0.5 mile when a valid coordinate is measured, and that reporting precision during commercial operation is "on the order of ±1 mile."[1]
That distinction matters in litigation. A carrier may produce an ELD printout and claim it shows the route. But the more important evidence may exist in another system: Samsara, Motive, Geotab, Verizon Connect, Omnitracs, PeopleNet, Fleetmatics, a dispatch platform, a route-planning program, or a driver's personal GPS device. In route-deviation cases, the first question is often not what the data shows. It is what systems existed and whether the data was preserved.
How Geofencing Works in Fleet Operations
A geofence is a digital boundary drawn around a real-world location. Geotab describes geofencing as a system that creates custom perimeters around physical locations; when a vehicle crosses the boundary, the system can send alerts, record activity, or trigger other configured actions. Geofences can be built around customer sites, yards, job zones, restricted areas, schools, construction zones, regions, or other locations that matter to a fleet.[2]
In trucking, geofencing turns vehicle location into an operational control. A carrier can define an approved route, a delivery zone, a terminal, a plant entrance, a rail yard, a restricted neighborhood, a fuel stop, or an off-limits roadway. Motive describes fleet geofencing as a virtual perimeter that uses GPS to trigger automated alerts when vehicles or assets enter or exit a specific area; its help materials also note that alert recipients can be customized, including fleet users and outside contacts by email.[3]
The practical use is supervision. Motive explains that fleet managers can be alerted when a vehicle deviates from its approved route or moves outside virtual boundaries, and that geofencing can be used to manage traffic restrictions by alerting when a truck is about to enter an off-limits area.[4] That is the core negligent-supervision issue. If the carrier had real-time notice that a truck left an approved route or entered a dangerous area, what did it do next?
Modern telematics systems can generate more than dots on a map. Samsara's alert-configuration documentation lists alert types including "Inside Geofence," "Outside Geofence," "Out of Route," "GPS Signal Loss," "Geofence Entry," "Geofence Exit," "Route Stop ETA Alert," harsh events, speeding, HOS violations, and other safety-related triggers.[5] Samsara's address documentation also describes configurable circular or polygonal geofences and address-related webhook events, meaning the evidence may include not only a map view but also API records, alert configurations, webhooks, and system-generated event histories.[6] (These vendor product descriptions reflect the platforms' documented capabilities as of the date accessed; specific features and terminology can change with product updates, so counsel should confirm current functionality and, where possible, corroborate with case-specific discovery.)
For crash investigation, that means the relevant records include the geofence definitions themselves. The size, shape, coordinates, alert threshold, active dates, notification recipients, alert status, and deactivation history can matter. If a carrier claims no alert was generated, the next question is whether the geofence existed, whether it was active, whether the truck or driver was assigned to it, and whether the alert was disabled.
What ELD Records Can and Cannot Prove
ELD data is important, but it should not be overstated. Appendix A to 49 C.F.R. Part 395 requires an ELD to automatically determine the commercial motor vehicle's position in latitude and longitude, without outside input or interference from the carrier, driver, or another person. It also states that CMV position measurement must be accurate to within ±0.5 mile when a valid coordinate is measured, and that reporting precision during commercial operation means position reporting accuracy will be on the order of ±1 mile.[7]
That level of precision may be enough to reconstruct a general route, identify a highway segment, or compare a truck's path against a planned trip. It is not always enough to establish lane-level position, a driveway entrance, or the exact side of a small boundary. FMCSA guidance also clarifies that ELD position information does not have to come from the engine control module; the position capability may be provided by another component of the ELD system.[8]
Federal retention rules create another practical issue. Section 395.8 requires motor carriers to retain records of duty status and supporting documents for at least six months.[9] FMCSA guidance similarly states that carriers must retain drivers' records of duty status and supporting documents for six months and maintain a backup copy of ELD records on a separate device for six months.[10] Supporting documents can be broader than the driver's log. Section 395.11 includes bills of lading, itineraries, schedules, dispatch records, trip records, expense receipts, and electronic mobile communication records transmitted through a fleet-management system. It also requires supporting documents to be retained so they can be matched to the corresponding driver's record of duty status and prohibits destroying or altering existing information in a supporting document.[11]
This matters because route-deviation proof often sits at the intersection of required records and business records. The ELD may show approximate location. The dispatch record may show the assigned route. The fleet-management message may show that a dispatcher told the driver to avoid a road. The geofence report may show the truck crossed a boundary. The route exception report may show the carrier received notice but did nothing.
When Route Choice Becomes a Safety Issue
Not every route deviation is negligent. Commercial drivers encounter closures, weather, congestion, detours, police direction, fuel needs, shipper delays, and emergency conditions. The legal and safety significance depends on why the route mattered. Hazardous-materials routing is one example. Part 397 governs hazardous-materials driving and routing rules. For highway route controlled quantities of Class 7 radioactive materials, the regulations address preferred routes, pickup and delivery routes, route plans, and deviations. The rule requires a written route plan for certain shipments and requires any variation between the route plan and the route actually used, and the reason for the variation, to be reported in an amendment to the route plan.[12]
FMCSA's hazardous-materials highway routing report explains why routing is treated as a safety and security issue rather than a mere efficiency decision. The report directed federal work on documenting existing and proposed hazardous-materials routes, developing a GIS-based framework for characterizing routes in the national hazardous-materials route registry, and identifying measurable criteria for route selection based on safety and security concerns.[13] The report also explains that route analysis often considers risk, trip efficiency, population exposure, emergency-response proximity, type of hazardous material, roadway conditions, and traffic conditions.[14]
Oversize and over-height loads present a different route problem. In Rayner v. Claxton, a Texas appellate court described a crash involving a truck carrying an oversized load. The driver mistakenly deviated from the TxDOT-approved route, continued several miles in the wrong direction, and the load struck an overpass; debris then struck another vehicle. The court noted that TxDOT permits for oversized loads contain a specific route and that the permit route is intended to ensure the load fits under bridges along the path of travel.[15]
That case illustrates the basic route-deviation theory: the road itself may be unsafe for that vehicle because the vehicle was never supposed to be there. A truck that is legal on one route may be too tall, too heavy, too long, or too difficult to turn on another.
How NTSB Investigations Use GPS and Telematics
NTSB reports show how location data can clarify crash sequences. In the Biloxi, Mississippi motorcoach grade-crossing crash, the driver used a Garmin DEZL 570MT GPS device for navigation. Although the device was damaged, investigators recovered the data. The GPS showed the motorcoach reached the stop line of the Main Street grade crossing about 35 seconds before the crash and recorded coordinate points showing the motorcoach at the stop line, on the tracks, and north of the tracks.[16]
The same report shows the limits of navigation systems. NTSB noted that the Garmin device could account for commercial-vehicle dimensions and avoid some route limitations, but it did not avoid routing vehicles over high-profile grade crossings unless prohibitory signs were present. In NTSB testing, the GPS suggested a route that included the Main Street crossing and displayed a "Risk of Grounding" warning when approaching it.[17] For a route-deviation article, the lesson is that GPS evidence may prove both the route taken and the limitations of the routing system used.
In the Cranbury, New Jersey crash, NTSB documented that the truck was equipped with a Qualcomm electronic log system for recording and monitoring driving and on-duty time. The driver had been on duty 13 hours 32 minutes of a 14-hour duty day, and NTSB found he likely would have received audible Qualcomm alerts as he approached the hours-of-service limit. The report also noted prior performance-tracking log events reflecting safety-manager involvement.[18] That is not a route-deviation case, but it is a carrier-notice case. Electronic systems can generate warnings, and the response to those warnings matters.
In the Palm Springs crash, NTSB used Fleetmatics GPS data to reconstruct truck movement and compare it with paper logs. Investigators obtained 30 days of Fleetmatics data, which recorded vehicle position and transmitted that information to the carrier. The data showed specific precrash movement and revealed multiple inconsistencies between the driver's paper logbook and GPS data in the days before the crash.[19] NTSB further found that although the fleet was equipped with Fleetmatics, the carrier and its consultant did not use the GPS data to verify hours-of-service compliance.[20]
Even personal devices can matter. In the Osseo, Wisconsin rollover investigation, NTSB examined data from the truck driver's personal Garmin GPS. The data showed the tractor's speed and heading over the final miles before the crash, including speed between 66 and 70 mph, heading changes, and deceleration.[21]
Litigation Lessons: Discovery, Preservation, and Causation
Route and geofence evidence is electronically stored information. Federal Rule of Civil Procedure 34 expressly covers ESI and allows requests to specify the form of production; if no form is specified, ESI must be produced in the form in which it is ordinarily maintained or in a reasonably usable form.[22] Texas Rule of Civil Procedure 196.4 is even more direct for Texas practice. A party seeking electronic or magnetic data must specifically request it and specify the form in which it should be produced, and the responding party must produce responsive data reasonably available in the ordinary course of business.[23]
That means a request for "GPS records" may not be enough. The request should identify native exports, CSV files, KML/KMZ files, route reports, breadcrumb data, geofence entry and exit logs, alert history, dispatch messages, driver app messages, ELD output files, audit logs, API exports, and platform-retention settings. The goal is to avoid receiving a screenshot when the useful evidence is a database export.
Preservation is time-sensitive. In De Leon v. Trahan, the Western District of Texas addressed unavailable Omnitracs data from a crash and denied sanctions because the plaintiff failed to establish a duty to preserve the data beyond six months. The court discussed the six-month retention timeline for certain driver and ELD records and noted that the plaintiff could have avoided the issue by sending a litigation-hold letter or otherwise putting defendants on notice within the six-month window.[24]
Litigation also requires causation, not just data. Transportation Concepts, Inc. v. Ramirez is a useful caution. The plaintiff alleged the carrier chose an unsafe route, but the Texas appellate court found insufficient evidence to support negligent supervision. The court noted evidence that drivers were allowed to deviate from chosen routes, and it rejected the route-based negligent-supervision theory because the plaintiff failed to prove the driver was unfit or that the carrier negligently supervised him at the time.[25]
The contrast between Rayner and Ramirez is important. Route evidence becomes strongest when the route was mandatory, safety-critical, known to the carrier, or tied directly to the crash mechanism. It becomes weaker when the plaintiff can only argue that another route might have been safer without proving carrier notice, breach, and causation.
What to Request After a Route-Deviation Crash
A complete route-deviation investigation should request more than the driver's log. The core records include dispatch instructions, trip sheets, route plans, customer instructions, bills of lading, itineraries, schedules, permits, hazmat route plans, driver messages, electronic mobile communications, GPS pings, breadcrumbs, route-exception reports, geofence definitions, geofence entry and exit logs, alert configurations, alert recipients, alert acknowledgments, and deactivation histories.
The system records matter too. Request the name of every platform installed or used on the truck: ELD provider, telematics provider, dashcam provider, trailer tracker, dispatch software, routing software, driver app, fuel-card system, toll transponder system, and any personal GPS device recovered from the vehicle. Ask whether the platform retained data locally, in the cloud, through an API, through a third-party vendor, or in reports periodically emailed to supervisors.
The core point is narrow but important: route deviation is not just a map issue. It can show that a truck entered a road it was never supposed to use, that a driver ignored route restrictions, that a carrier failed to act on repeated alerts, or that a crash occurred because the driver was navigating unfamiliar road geometry. Geofencing and telematics do not prove negligence by themselves. They prove movement, notice, timing, and sometimes nonresponse. In trucking litigation, those facts often determine whether a route choice was a harmless detour or a preventable safety failure.
Sources
- [1] Appendix A to Subpart B of 49 C.F.R. Part 395, § 4.3.1.6.↩
- [2] Geotab, What Is Geofencing? (vendor technical documentation, current as of last access).↩
- [3] Motive, Geofences (vendor technical documentation).↩
- [4] Motive, What Is a Geofence in Fleet Management? (vendor technical documentation).↩
- [5] Samsara, Get Configurations (vendor developer documentation).↩
- [6] Id.↩
- [7] Appendix A to Subpart B of 49 C.F.R. Part 395, § 4.3.1.6.↩
- [8] FMCSA, Is the ELD Required to Retrieve the CMV Position from the Device Connected to the Port?.↩
- [9] 49 C.F.R. § 395.8(k)(1).↩
- [10] FMCSA, How Long Must a Motor Carrier Retain a Driver's ELD Record of Duty Status?.↩
- [11] 49 C.F.R. § 395.11(c)(1), (e), (f).↩
- [12] 49 C.F.R. Part 397, Subpart D (§§ 397.101, 397.103).↩
- [13] FMCSA, Hazardous Materials Highway Routing Report.↩
- [14] Id.↩
- [15] Rayner v. Claxton, 659 S.W.3d 223 (Tex. App.—El Paso 2022, no pet.).↩
- [16] NTSB, Highway Accident Report HAR-18/01, Biloxi, Mississippi Motorcoach Grade-Crossing Crash.↩
- [17] Id.↩
- [18] NTSB, Highway Accident Report HAR-15/02, Cranbury, New Jersey Crash.↩
- [19] NTSB, Highway Accident Report HAR-17/04, Palm Springs, California Crash.↩
- [20] Id.↩
- [21] NTSB, Highway Accident Report HAR-08/02, Osseo, Wisconsin Rollover.↩
- [22] Fed. R. Civ. P. 34(a)(1)(A), (b)(1)(C), (b)(2)(E)(ii).↩
- [23] Tex. R. Civ. P. 196.4.↩
- [24] De Leon v. Trahan, No. PE-21-CV-00086-DC, 2024 WL 5454655 (W.D. Tex. Aug. 28, 2024).↩
- [25] Transportation Concepts, Inc. v. Ramirez, No. 08-24-00036-CV, 2025 WL 1749675 (Tex. App.—El Paso, June 24, 2025, no pet.).↩