PACCAR filed NHTSA safety recall 26V744, manufacturer campaign 26PACL, covering 6,185 model-year 2027 trucks: Kenworth T680, T880 and W990 models and Peterbilt 567, 579 and 589 models produced on model-specific dates between February 11 and October 8, 2026. The November 11 Part 573 report says the forward-looking radar may treat stationary or slow-moving objects in the left adjacent lane as relevant objects and produce unintended braking or false-positive automatic emergency braking events. PACCAR told NHTSA that the parameter calculator used for the radar produces a software data set that may not be written correctly into radar memory, causing an incorrect lateral-position default. The report lists no advance warning and says an unintended braking event may increase crash or injury risk. It also states that forward collision mitigation for objects in the truck's own lane is not affected because the camera detects those objects. PACCAR estimated that 0.1% of the recalled population has the defect and reported eight warranty claims, eight potentially related field reports, and no deaths or injuries as of November 4. The remedy is a field software update that corrects the radar-memory issue. The official schedule lists January 10, 2027 for dealer, interim owner, and remedy notifications and for affected VINs to become searchable. The report does not mark a do-not-drive or park-outside advisory, but carriers should follow current PACCAR, Kenworth, Peterbilt, dealer, and NHTSA instructions for each VIN rather than treating that absence as permission to ignore the recall.
NHTSA says 6,185 model-year 2027 Kenworth and Peterbilt trucks may brake unexpectedly because of a specific forward-radar software defect.
- Open a campaign record for NHTSA 26V744 and PACCAR 26PACL. Preserve the official Part 573 report, affected models and production dates, component and risk description, remedy, notification schedule, manufacturer contacts, last verification time, and any later amendment or dealer bulletin.
- Check every potentially affected tractor by full VIN through the authoritative manufacturer, dealer, and NHTSA process. Include owned, leased, rented, newly delivered, spare, team, dedicated, and temporarily assigned units; do not rely on the model badge, a fleet list without build data, or the absence of an owner letter.
- Place unresolved VINs in a visible safety-review status. Safety and maintenance should document the current manufacturer or dealer instruction and determine the dispatch restriction, monitoring requirement, or hold. Dispatchers must not clear a truck merely because it has not produced a warning or because a load has a tight appointment.
- Give affected drivers a verified response card. Describe the potential unintended-braking behavior, safe reporting and emergency steps, fleet and dealer contacts, the authorized movement plan, and the prohibition on disabling, disconnecting, recalibrating, or road-testing the radar without approved technical direction.
Why this development matters
Fleet Safety & Maintenance can influence pricing, lane selection, capacity, customer expectations, and the level of operating risk carried by a motor carrier. The headline matters only after a team understands which loads, drivers, customers, or markets may actually be affected.
The development covered in “PACCAR Recalls 6,185 Trucks” should be evaluated against the carrier’s real network. National trends can create useful direction, but individual results still depend on equipment type, geography, contract terms, driver availability, fuel exposure, and service requirements.
Dispatchers should separate verified facts from forecasts and commentary. Regulatory proposals are not final rules, market averages are not guaranteed lane rates, and a single company announcement does not automatically represent the entire trucking industry.
What happened
PACCAR filed NHTSA safety recall 26V744, manufacturer campaign 26PACL, covering 6,185 model-year 2027 trucks: Kenworth T680, T880 and W990 models and Peterbilt 567, 579 and 589 models produced on model-specific dates between February 11 and October 8, 2026. The November 11 Part 573 report says the forward-looking radar may treat stationary or slow-moving objects in the left adjacent lane as relevant objects and produce unintended braking or false-positive automatic emergency braking events. PACCAR told NHTSA that the parameter calculator used for the radar produces a software data set that may not be written correctly into radar memory, causing an incorrect lateral-position default. The report lists no advance warning and says an unintended braking event may increase crash or injury risk. It also states that forward collision mitigation for objects in the truck's own lane is not affected because the camera detects those objects. PACCAR estimated that 0.1% of the recalled population has the defect and reported eight warranty claims, eight potentially related field reports, and no deaths or injuries as of November 4. The remedy is a field software update that corrects the radar-memory issue. The official schedule lists January 10, 2027 for dealer, interim owner, and remedy notifications and for affected VINs to become searchable. The report does not mark a do-not-drive or park-outside advisory, but carriers should follow current PACCAR, Kenworth, Peterbilt, dealer, and NHTSA instructions for each VIN rather than treating that absence as permission to ignore the recall.
The development matters when it changes load planning, pricing, communication, safety, or the daily decisions made by carriers and dispatch teams.
What dispatch teams should do
The development is most useful when it becomes a specific operating check instead of another headline.
- Open a campaign record for NHTSA 26V744 and PACCAR 26PACL. Preserve the official Part 573 report, affected models and production dates, component and risk description, remedy, notification schedule, manufacturer contacts, last verification time, and any later amendment or dealer bulletin.
- Check every potentially affected tractor by full VIN through the authoritative manufacturer, dealer, and NHTSA process. Include owned, leased, rented, newly delivered, spare, team, dedicated, and temporarily assigned units; do not rely on the model badge, a fleet list without build data, or the absence of an owner letter.
- Place unresolved VINs in a visible safety-review status. Safety and maintenance should document the current manufacturer or dealer instruction and determine the dispatch restriction, monitoring requirement, or hold. Dispatchers must not clear a truck merely because it has not produced a warning or because a load has a tight appointment.
- Give affected drivers a verified response card. Describe the potential unintended-braking behavior, safe reporting and emergency steps, fleet and dealer contacts, the authorized movement plan, and the prohibition on disabling, disconnecting, recalibrating, or road-testing the radar without approved technical direction.
- Schedule the software remedy with the dealer and connect it to the load plan. Confirm appointment, availability, estimated downtime, safe route or tow decision, cargo and trailer disposition, substitute tractor, driver hours, customer update, and the exact evidence required before dispatch release.
- Close the campaign per VIN only after the repair order identifies 26V744 or 26PACL, the truck, completed radar software update, date, mileage, dealer or technician, and maintenance approval. Reconcile repaired, pending, unknown, sold, and out-of-service units until the fleet register contains no unexplained gap.
The Dispatch Control view
Carriers should verify the underlying source, identify the lanes or workflows actually affected, and avoid changing policy based on a headline alone. Market reports and regulatory announcements can signal risk before they create a direct requirement.
Keep rate, route, driver, equipment, documents, and customer communication connected so the team can respond quickly when conditions change.
How to put the information into daily practice
Start by identifying where fleet safety & maintenance appears in the current dispatch workflow. Review what information is collected, who confirms it, where it is stored, and what event triggers the next action. If the answer depends on a private text message or someone’s memory, the process is difficult to audit and difficult to scale.
Use one load timeline to connect the booking decision, driver assignment, route and appointment plan, status updates, exceptions, supporting documents, accessorial approvals, and invoice readiness. Each update should answer three questions: what changed, who owns the response, and when the next update is due.
Introduce the improvement on a small group of active loads before applying it to the whole fleet. Review the exceptions at the end of each shift, correct unclear fields or instructions, and then make the successful version the standard operating procedure.
- Open a campaign record for NHTSA 26V744 and PACCAR 26PACL. Preserve the official Part 573 report, affected models and production dates, component and risk description, remedy, notification schedule, manufacturer contacts, last verification time, and any later amendment or dealer bulletin.
- Check every potentially affected tractor by full VIN through the authoritative manufacturer, dealer, and NHTSA process. Include owned, leased, rented, newly delivered, spare, team, dedicated, and temporarily assigned units; do not rely on the model badge, a fleet list without build data, or the absence of an owner letter.
- Place unresolved VINs in a visible safety-review status. Safety and maintenance should document the current manufacturer or dealer instruction and determine the dispatch restriction, monitoring requirement, or hold. Dispatchers must not clear a truck merely because it has not produced a warning or because a load has a tight appointment.
- Give affected drivers a verified response card. Describe the potential unintended-braking behavior, safe reporting and emergency steps, fleet and dealer contacts, the authorized movement plan, and the prohibition on disabling, disconnecting, recalibrating, or road-testing the radar without approved technical direction.
- Schedule the software remedy with the dealer and connect it to the load plan. Confirm appointment, availability, estimated downtime, safe route or tow decision, cargo and trailer disposition, substitute tractor, driver hours, customer update, and the exact evidence required before dispatch release.
- Close the campaign per VIN only after the repair order identifies 26V744 or 26PACL, the truck, completed radar software update, date, mileage, dealer or technician, and maintenance approval. Reconcile repaired, pending, unknown, sold, and out-of-service units until the fleet register contains no unexplained gap.
- Assign a named owner and a due time for every unresolved exception.
- Keep customer and driver communication attached to the load record.
- Review the result after delivery and carry the lesson into the next similar load.
Common mistakes and practical risk controls
The most common mistake is acting with incomplete information because the load feels urgent. Speed is useful only when the basic facts are verified. Before committing the truck, confirm the parties, rate or cost exposure, equipment, timing, route constraints, required documents, and the person authorized to approve changes.
Another mistake is allowing an exception to remain inside a phone call. If detention, a missed appointment, an equipment problem, a route change, a rejected shipment, or a compliance concern is not recorded, the next person cannot make a fully informed decision. Written timestamps and supporting documents protect both service and payment.
Finally, avoid measuring activity instead of outcomes. More calls, messages, or status entries do not necessarily mean better control. The useful question is whether the process produced a safer trip, an on-time delivery, a complete document set, a satisfied customer, and an acceptable contribution margin.
- Do not promise an appointment before checking realistic transit and driver hours.
- Do not rely on an unverified email, changed phone number, or altered payment instruction.
- Do not close the load while documents, accessorials, or customer exceptions remain unresolved.
- Do not change a compliance process based only on a headline; confirm the official requirement first.
What managers should measure
A useful scorecard for fleet safety & maintenance should be short enough to review every week. Combine service, cost, workflow, and safety measures so that one improvement does not hide damage somewhere else.
Compare performance by customer, lane, dispatcher, equipment type, and exception reason. Trends become actionable when the team can see where a delay or cost begins, not only the final monthly total.
- On-time pickup and delivery percentage, including the documented cause of every miss.
- Loaded and empty miles, revenue per total mile, and contribution per truck-day.
- Average check-in, loading, unloading, and detention time by facility.
- Time from delivery to verified POD and time from verified POD to invoice.
- Number of avoidable exceptions, repeated data corrections, and unresolved driver issues.
- Safety or compliance events that required a dispatch change or management review.
A simple implementation checklist
Use this checklist during a dispatch meeting or process review. Each item should be visible in the company’s transportation management workflow and understandable to the person covering the desk after hours.
- The load has a verified customer or broker, rate, commodity, equipment type, weight, and reference number.
- Every stop has an address, appointment, contact, instructions, service-time allowance, and required document.
- The assigned driver and equipment can complete the plan safely and legally.
- Fuel, toll, deadhead, parking, and likely delay exposure are reflected in the operating decision.
- The driver knows the next action, expected updates, and the exceptions requiring immediate escalation.
- Delivery paperwork and accessorial evidence will flow directly into review and invoicing.
- A manager can reconstruct the load history without searching personal messages or separate spreadsheets.
Frequently asked questions
Does this news item change a carrier’s legal requirements immediately?
Not necessarily. A news report may describe a proposal, pilot, market development, enforcement trend, or company announcement. Confirm final regulatory requirements through the responsible government agency before changing compliance policy.
How should a dispatcher use national freight-market data?
Use it as context for direction and risk. The operating decision should still use current lane data, equipment availability, driver hours, deadhead, fuel, appointments, and the carrier’s own accepted-load history.
When should customers receive an update?
Send an update when the development materially changes price, capacity, transit, appointment reliability, documentation, or regulatory handling for their shipment. Explain the specific impact and the next action.
What should the carrier monitor next?
Monitor the original source, current fleet safety & maintenance indicators, lane-level results, customer requests, and any official implementation or enforcement date.