The cleanest way to understand Ford's latest Explorer recall is as a story about the seam between software and mechanism — the place where a transient error in code leaves a permanent mark on hardware. NHTSA campaign 26V371000, filed June 9, 2026, covers certain 2024 Explorer vehicles equipped with the 2.3-liter engine and the 10R60 ten-speed automatic transmission. The defect begins as a fault you cannot see and ends as a vehicle that will not stay put.
According to the recall record, an unintentional reset of the powertrain control module — the PCM, the computer that manages the engine and transmission — can occur while the vehicle is in motion. That reset, mid-drive, can result in park system damage. The park system is the mechanism that physically locks the transmission output when the driver selects PARK; on a modern shift-by-wire vehicle, that selection is a software request that commands an actuator, not a direct cable pull. If the request arrives while the mechanism is in a compromised state, the hardware can be left damaged. The agency's consequence statement spells out the failure mode.
"A park system that is damaged may not shift into 'PARK,' resulting in a vehicle rollaway and increasing the risk of injury or crash."— NHTSA recall 26V371000, source
Why shift-by-wire turns a software glitch into a mechanical failure
For most of automotive history, PARK was a purely mechanical guarantee. You moved a lever, a cable or linkage rotated a manual valve and dropped a parking pawl into a gear on the transmission output shaft, and the car was locked regardless of what any computer thought. The shift-by-wire architecture that now dominates new vehicles — the Explorer included — replaces that linkage with an electronic shifter and an actuator. The benefit is packaging freedom and clean integration with stop-start, hill-hold, and automated features. The cost is that the integrity of PARK now depends on the controller behaving correctly during the transition.
That is the precise hinge this recall turns on. A PCM that resets unexpectedly while the vehicle is moving is operating outside its normal state machine, and the recall language indicates that this abnormal sequence is what can damage the park mechanism. It is worth being careful about what the record does and does not say: it does not claim every reset damages the park system, and it does not state how often the reset occurs. What it establishes is a credible path from a software event to a mechanical defect to a rollaway — and a rollaway is among the small set of failure modes serious enough to warrant a recall on its own merits, because an unoccupied vehicle that moves can strike a person who has no way to react.
An inspect-and-repair remedy, not a flash
Notably, the remedy here is not a simple reflash of the PCM. Per the recall record, dealers will inspect for park system damage and repair the vehicles as necessary, free of charge. That phrasing — inspect, then repair as necessary — tells you the defect leaves physical evidence that a technician has to assess. If the fix were purely preventing future resets, a software update alone would suffice; the inclusion of physical repair means some vehicles may already carry damage from a reset that has occurred. This is the operational difference between a software bug and a software bug with a mechanical consequence: you can patch the cause, but you still have to go find and fix the effects.
The scoping detail rewards a closer look. By naming only the 2.3L engine paired with the 10R60 transmission, the recall implies the defect lives in the interaction between a specific PCM calibration and a specific transmission's park mechanism, not in the Explorer's hardware generally. Different engine-and-transmission pairings run different control software and, often, different park-system hardware, so a fault that reproduces in one combination need not exist in another. That precision is a feature of how modern defect investigations work: rather than recall an entire model line out of caution, the manufacturer narrows the population to the exact configuration where the failure path is credible. It is both more honest and more useful — it tells an owner of a differently equipped Explorer that they are not affected, and it concentrates the remedy where the risk actually lives.
Ford's internal number for the recall is 26S39. Owner notification letters are expected to be mailed June 15, 2026, and owners may contact Ford customer service at 1-866-436-7332. The recall record notes that the Vehicle Identification Numbers involved will become searchable on NHTSA.gov on June 12, 2026, so owners can confirm whether a specific Explorer is included by entering its VIN in the agency's recall lookup. The campaign's scoping to the 2.3L / 10R60 combination is a meaningful constraint — Explorers with other powertrains are not named — and reinforces that the issue lives in a specific PCM-and-transmission calibration rather than across the whole model line.
The broader signal for software-defined vehicles
This recall is a small, concrete example of a tension the industry keeps running into as it moves controls into software. Every function relocated from a cable to a controller inherits the controller's failure modes, including the rare and ugly ones like an unexpected reset. The engineering answer is not to retreat from shift-by-wire — the packaging and feature benefits are real — but to design the safe state so that a controller fault cannot leave a safety-critical mechanism in a damaged or undefined condition. A robust system fails into PARK, or at least fails without breaking the mechanism that delivers PARK. Campaign 26V371000 is, in effect, a field correction to a place where that safe-state design did not fully hold.
For owners, the practical advice mirrors what the situation demands: if you own a 2024 Explorer with the 2.3L engine, watch for the notification, and until the repair is complete, treat the parking brake as the real backstop — engaging it whenever the vehicle is parked is exactly the mechanical redundancy that protects against a park system that may not hold. The recall removes the defect; the parking brake is the seatbelt for the interim.