Ford Mustang Lincoln Instrument Cluster Recall: NHTSA 26V372 Covers 4,151 Vehicles

Status, June 30 source check: source-cleared for a BadPD vehicle-safety recall ledger. The official campaign is NHTSA 26V372 / Ford 26C27. It covers certain 2019 Ford Mustang, Lincoln Nautilus, and Lincoln Navigator vehicles previously repaired incorrectly under NHTSA 19V076 / Ford 19C03.

This is recall-record accountability reporting, not vehicle repair, driving, resale, insurance, legal, warranty, reimbursement, or purchase advice. The official NHTSA and Ford VIN records control whether a specific vehicle is included, open, repaired, validated, or closed.

What NHTSA And Ford Records Confirm

NHTSA’s June 11, 2026 acknowledgment letter lists 4,151 potentially affected units. Ford’s Part 573 vehicle rows also support that public total by listing 1,802 Lincoln Nautilus vehicles, 943 Ford Mustang vehicles, and 1,406 Lincoln Navigator vehicles. Those row counts add to 4,151.

The Part 573 population header, however, lists 2,349 as the total number potentially involved. BadPD is preserving that discrepancy as a pending record issue. The live public headline uses 4,151 because that is the NHTSA acknowledgment figure and the sum of Ford’s model-level rows. A later NHTSA or Ford correction would be a material update.

The affected vehicles may not have received the Instrument Panel Cluster, or IPC, software remedy for Ford recall 19C03 / NHTSA 19V076. Ford says certain vehicles had the prior repair recorded as successfully completed, but the correct software update remedy may not actually be installed on the vehicle.

The underlying condition is an instrument-cluster noncompliance and crash-risk issue. At vehicle start-up, the IPC may not function and can show a blank display. Ford says the display issue can include PRNDL illumination, gauge indicators, and telltale warning lights. The source set says that condition fails to comply with FMVSS 101, Controls and Displays.

NHTSA’s acknowledgment letter summarizes the consequence: a blank instrument cluster that fails to display critical safety information, such as vehicle speed or safety system warnings, increases crash risk. Ford says it is not aware of any reports of accident or injury related to this condition.

Why This Recall Is A Records Story

This is not only a dashboard-screen story. It is a software-remedy record story. The 2026 campaign exists because Ford’s records say some vehicles had the 19C03 / 19V076 remedy marked as successfully completed even though the intended software state may not have been installed. That creates a direct public accountability question: when a recall is closed in a system, what proof shows the correct software is actually on the vehicle?

The Part 573 chronology describes the same broader audit trail seen in other Ford software-remedy recalls. Ford says a concern about incomplete software recall remedies reached the Critical Concern Group on November 26, 2024. A cross-functional team audited software field service actions that used Ford service tools. Ford told NHTSA on December 19, 2024, that some vehicles did not have a match between the service-tool software state and the field service action software release.

Ford says later audit work identified discrepancies during the transition between the legacy IDS field service tool and the newer FDRS service tool, plus gaps in historical data. On April 16, 2026, Ford’s Critical Concern Review Group determined that several field service actions with recall remedies implemented through the IDS tool may have been closed without that remedy being installed. The included VINs are both vehicles confirmed to contain incorrect software and vehicles with a closed field service action where the software version cannot be confirmed due to record gaps.

For BadPD, that is the accountability core. A closeout flag is not the same thing as a verified software-state record. Owners, dealers, buyers, fleets, auction platforms, insurers, and regulators need the current campaign number, the VIN status, the software update record, and the validation receipt.

Remedy And Timing

The remedy is software. Owners are to be notified by mail and instructed to take their vehicle to a Ford or Lincoln dealer to have the IPC software updated. Ford says the software part numbers will then be validated using the Software Validation Form in the Professional Technician System before the field service action is closed. There will be no charge for the service.

The recall schedule says dealer notification is expected from July 6 through July 8, 2026. Remedy owner notification letters are expected to begin July 6 and be completed by July 10, 2026. The date VINs are planned to be searchable is July 6, 2026.

NHTSA API records accessed by BadPD on June 30, 2026 show the new 26V372 recall in the recall histories for the 2019 Ford Mustang, 2019 Lincoln Nautilus, and 2019 Lincoln Navigator. The same API records also preserve the older 19V076 recall. Those two campaign records should be kept separate. A prior 19V076 closure is historical context, while 26V372 is the current campaign dealing with vehicles that Ford says were previously repaired incorrectly or cannot be verified through the software-state record.

Dealer And VIN Records That Should Exist

The practical file starts with a current VIN lookup. The model-year and population details are useful, but they do not prove that a specific vehicle is included. After VIN confirmation, the important service record should name 26C27 or 26V372, show the IPC software update, and show the Software Validation Form result before the action is closed.

A generic note saying “cluster recall checked” is weaker than a repair order that identifies the current campaign and validation result. The reason is built into the recall itself: the older 19V076 remedy may have been marked complete without the intended software being installed. If the new record does not prove software state, the public has learned little from the second recall.

Dealers also need to distinguish this instrument-cluster campaign from other Ford software-remedy campaigns. This one is not the F-150 DRL/FMVSS 108 campaign and it is not the Focus CPV/PCM campaign. It concerns the IPC software on a defined 2019 Mustang, Nautilus, and Navigator population, tied to the older 19V076 / 19C03 instrument-cluster recall.

Resale, Fleet, And Auction Exposure

These vehicles can move through individual ownership, dealer trade-ins, commercial fleets, auctions, financing portfolios, insurance files, and private sales. A current software-remedy recall needs to follow the VIN, not just the first owner letter. The relevant records for a buyer or fleet manager are the current NHTSA/Ford VIN result, the 26C27 service record, and the validation proof.

Because VINs were planned to be searchable on July 6, 2026, there is a timing gap between the public filing and practical VIN confirmation for some users. During that gap, the campaign facts support awareness and watch-listing, not a claim that a particular vehicle is affected. Once the VIN tool is live, the public-interest question becomes completion: open, repaired, validated, or still pending.

For resellers and auction platforms, the stronger record sequence is before-and-after proof. The before record shows the vehicle’s open recall status when checked. The after record shows the 26C27 appointment, IPC software update, validation form completion, and final closeout. That sequence prevents an old 19V076 closure from being mistaken for current 26V372 completion.

Completion Reports And Public Follow-Up

NHTSA’s acknowledgment letter reminds Ford that quarterly completion reports and later annual status reports are required. Those reports matter because they show whether a source-cleared recall became completed repairs. For a campaign this size, the public should eventually see how many vehicles were notified, repaired, unreachable, or still open.

The next useful documents include the final owner notification letter, dealer bulletins, technical instructions, software-validation workflow, and any Ford or NHTSA follow-up about the 2,349 versus 4,151 count discrepancy. If Ford identifies more software-remedy closure gaps, this campaign should be read with those records because the chronology describes a broader audit of software field service actions.

Why The Count Discrepancy Should Stay Visible

The 2,349 versus 4,151 mismatch is not a reason to discard the recall. It is a reason to keep the source labels attached. NHTSA’s acknowledgment letter is a separate public record from Ford’s Part 573 form, and the model-level rows in the Part 573 form support the same 4,151 total that NHTSA published. The population-header number in the Part 573 form does not match those rows. That should be corrected or explained in a later file so owners, dealers, journalists, and completion-report readers are not forced to guess which number controls.

Count accuracy matters because completion percentages are only meaningful when the denominator is stable. If the public later sees a quarterly completion report, the repair rate should be measured against the right population. A campaign with 2,349 vehicles and a campaign with 4,151 vehicles are materially different for notification, dealer capacity, fleet tracking, and public oversight. BadPD is using the NHTSA acknowledgment and row-sum figure while explicitly preserving the discrepancy so the source record is not flattened.

What A Clean Closeout Would Show

A clean 26V372 closeout should have three pieces of proof. First, the VIN should show whether it belongs to the current campaign after the July 6 searchable date. Second, the dealer record should show that the IPC software was updated under 26C27 / 26V372 rather than only showing an older 19V076 closure. Third, the Software Validation Form should confirm the software part numbers before the field service action is closed.

Those records matter because the recall is about an old repair record not being enough. The public should not have to rely on another unsupported closeout flag. The useful receipt is a current campaign-specific repair order and validation record. For fleets and resale files, that receipt should stay with the vehicle file because future buyers or operators may otherwise see only the older 2019 campaign history and miss the 2026 follow-up.

Confirmed, Pending, Not Established

Confirmed by NHTSA/Ford records

• NHTSA 26V372 / Ford 26C27 is an official recall campaign.
• The campaign covers certain 2019 Ford Mustang, Lincoln Nautilus, and Lincoln Navigator vehicles.
• NHTSA’s acknowledgment letter lists 4,151 potentially affected units, and the Part 573 vehicle rows add to 4,151.
• The Part 573 population header lists 2,349, creating a source-record discrepancy that remains pending.
• Ford says affected vehicles may not have received the IPC software remedy for 19C03 / 19V076 even though the repair was recorded as completed.
• The underlying noncompliance concerns a blank IPC display at start-up and FMVSS 101 controls-and-displays requirements.
• Ford says it is not aware of any reports of accident or injury related to this condition.
• The planned dealer notification window is July 6 through July 8, 2026.
• The planned remedy owner notification window is July 6 through July 10, 2026.
• The planned VIN-search date is July 6, 2026.

Pending records

• Correction or clarification of the 2,349 versus 4,151 population discrepancy.
• Quarterly completion reports and later annual reports required by NHTSA’s acknowledgment letter.
• Dealer bulletin and final owner-letter copies after distribution.
• VIN-level open/closed status after the July 6 searchable date.
• Software Validation Form completion proof for repaired vehicles.
• Counts separating confirmed incorrect software from vehicles included because older software records could not be confirmed.
• Any later Ford or NHTSA incident, crash, injury, compliance, enforcement, or audit update.

Not established by this source set

• That every 2019 Mustang, Nautilus, or Navigator is included.
• That any specific vehicle currently has a blank instrument-cluster condition without VIN and service-record confirmation.
• That any accident or injury has occurred because of this condition.
• That any individual dealer knowingly closed an incorrect repair.
• That a prior 19V076 closure record is enough for a VIN that appears in 26V372.

BadPD Bottom Line

NHTSA 26V372 belongs in the BadPD recall-accountability lane because it shows how software-based recall remedies can become public-record problems. A recall is not fully accountable when the public can see only that an older action was closed. Owners, buyers, fleets, dealers, and regulators need a verifiable current record showing whether the vehicle is in 26V372, whether the IPC software update was installed, and whether the Software Validation Form confirmed the correct software state before the field service action was closed.

BadPD will update this ledger if Ford or NHTSA posts owner-letter files, dealer bulletins, quarterly completion data, audit details, population-count corrections, later incident records, or additional software-remedy recalls tied to the same field-service-tool records issue.

Source Ledger

• NHTSA Part 573 Safety Recall Report, campaign 26V372, June 16, 2026
• NHTSA acknowledgment letter, campaign 26V372, June 11, 2026
• NHTSA API recall record, 2019 Ford Mustang, accessed June 30, 2026
• NHTSA API recall record, 2019 Lincoln Nautilus, accessed June 30, 2026
• NHTSA API recall record, 2019 Lincoln Navigator, accessed June 30, 2026

Featured image is symbolic editorial artwork created for BadPD. It is not NHTSA, Ford, Lincoln, dealer, owner, vehicle, dashboard, instrument cluster, crash, injury, repair, software, VIN, or service-tool photography and is not a depiction of any specific recalled vehicle.