A recall of 91,198 Ford F-150 pickups for Daytime Running Lamp that do not dim appropriately, reducing the visibility of other drivers and increasing the risks of a crash.
Ford Motor Company (Ford) is recalling certain 2018-2020 F-150 vehicles previously repaired incorrectly under recall number 20V097. When the headlight switch is turned from “Autolamps” to “Headlamps On,” the Daytime Running Lamps (DRLs) may remain fully bright instead of dimming to parking lamps as intended. As such, these vehicles fail to comply with the requirements of Federal Motor Vehicle Safety Standard (FMVSS) number 108, “Lamps, Reflective Devices and Associated Equipment.”
The date VINs are planned to be searchable is July 6, 2026 on the NHTSA website.
Here is the relevant information from the NHTSA Recall notice:
NHTSA ID Number: 26V373000
Manufacturer: Ford Motor Company
Components: EXTERIOR LIGHTING
Potential Number of Units Affected: 91,198
Descriptive Information:
The Ford process is capable of determining which software part numbers have been installed in production and service. Affected vehicles may not have received the Body Control Module (BCM) software remedy for Ford Recall 20C03 / 20V097.
These vehicles are not produced in VIN order. Information as to the applicability of this action to specific vehicles can best be obtained by either calling Ford’s toll-free line (1-866-436-7332) or by contacting a local Ford or Lincoln dealer who can obtain specific information regarding the vehicles from the Ford On-line Automotive Service Information System (OASIS) database. 91198 F-150 vehicles are affected.
Description of the defect or noncompliance:
According to Ford’s records, certain 2018-2020 MY Ford F-150 vehicles did not have the remedy for Safety Recall 20C03 / 20V-097 installed correctly but were recorded as having the repair successfully completed. Because the correct software update remedy may not be installed on the vehicle, the underlying condition specified in Safety Recall 20C03 / 20V-097 may still exist, and Daytime Running Lamps (DRL) are illuminated, and the Master Lighting Switch (MLS) is manually rotated from the “Autolamp” position to the “headlamp on” (Low Beam) position, the DRLs remain activated instead of dimming to parking lamps as required by FMVSS 108, exceeding the photometric output allowed by FMVSS 108.
Description of the safety risk, including crash, fire, death, injury:
The underlying safety risk specified in Safety Recall 20C03 / 20V-097 still exists on this specified vehicle. Ford described that safety risk as, “The increased photometric intensity from the DRL when combined with the low beam headlamp function does not comply with the requirements of FMVSS 108 and may reduce the visibility of other drivers, increasing the risk of a crash.”
Description of the cause:
The headlamp function is controlled by the Body Control Module (BCM). For this condition, the DRL function control within the headlamps is not compatible with the timing from the Body Control Module (BCM) when the Master Lighting Switch in the vehicle is manually rotated from “Autolamp” to either the low beam or park switch position. As a result, the lamp will remain “latched” in the DRL active state.
Identification of any warning that can occur:
None.
Chronology
On November 26, 2024, an issue pertaining to incomplete software recall remedies was brought to Ford’s Critical Concern Group (CCRG) for review. This issue was initially identified in a Quality Office forum, where an audit was requested for software part numbers applied to vehicles remedied under a sample of field service actions (FSAs). Initial review of three FSAs revealed insufficient data to confirm correct software application across all FSAs using the current field service tool, known as FDRS. CCRG decided to conduct further investigation.
In December 2024, a cross-functional team was formed to audit all software FSAs that used the FDRS service tool, with its first focus being on safety and compliance FSAs. Templates were created to track software lineage part numbers.
On December 19, 2024, Ford informed NHTSA of this concern — the service tool data confirmed that the software state on the service tool at the time of installation matches the FSA software release for most vehicles. However, there are vehicles that do not have a match between the software state on the service tool and the FSA software release. Ford discussed with NHTSA its plan to address the mismatched vehicles.
In January 2025, the cross-functional team created database records to store all software lineage part numbers for previously launched FSAs. The team then began auditing the current software level for every VIN repaired under several previously launched FSAs.
In March 2025, during a comprehensive audit of software-related FSAs dating back to 2017, discrepancies were identified during the transition between the legacy field service tool, known as IDS, and the new FDRS service tool. The audit revealed that implementation inconsistencies found in FDRS could also be present within the IDS software as well as a significant lack of historical data. Further investigation was deemed necessary.
In November 2025, a harvest program was approved to assess the success of remedies applied using the IDS tool for programs administered during this transition period. Results of this harvest program showed that in some FSAs, the intended remedy software may not have been successfully applied to all vehicles.
On April 16, 2026, the matter was presented to the Critical Concern Review Group (CCRG). The CCRG determined that several FSAs that had a recall remedy implemented using the IDS tool may have been closed without that remedy being installed. As a result, an activity was initiated to verify the software levels of vehicles that previously received these FSA repairs. The VINs included in this program are both (1) VINs confirmed to contain the incorrect software, and (2) VINs with a closed FSA, but the software version cannot be confirmed due to gaps in the records.
On May 27, 2026, Ford’s audit team confirmed that the software state matched the FSA software release in a subset of vehicles out of the total population of completed FSA 20C03 remedy repairs.
On June 2, 2026, Ford’s Field Review Committee reviewed the concern and approved a field action.
Ford is not aware of any reports of accident or injury related to this F-150 condition.
Remedy:
Owners will be notified by mail and instructed to take their vehicle to a Ford or Lincoln dealer to have the BCM software updated. Then, the software part numbers will be validated using the Software Validation Form in the Professional Technician System before the FSA is closed. There will be no charge for this service.
Ford provided the general reimbursement plan for the cost of remedies paid for by vehicle owners prior to notification of a safety recall in May 2023. Owners who have paid to have these repairs completed at their own expense may be eligible for reimbursement, in accordance with the recall reimbursement plan on file with NHTSA.
How remedy component differs from recalled component:
The software service package will have the intended remedy for 20C03 / 20V-097.
Identify how/when recall condition was corrected in production:
Not required per 49 Part 573.
Description of recall schedule:
Notification to dealers is expected to occur on July 6, 2026. Mailing of remedy owner notification letters is expected to begin July 6, 2026 and is expected to be completed by July 10, 2026.
