What If a Recall Repair Doesn’t Fix the Problem? NHTSA’s GM 6.2L Engine Investigation Explained

If a GM 6.2-liter L87 engine allegedly fails after Recall 25V-274 service, the completed recall repair is part of the evidence—not the end of the inquiry. The repair records may show what the dealer inspected, which remedy branch it selected, and which engine was in the vehicle. Records created after the failure may then help evaluate what happened next.

The National Highway Traffic Safety Administration’s Office of Defects Investigation opened Engineering Analysis EA26005 on August 20, 2026, to investigate alleged losses of motive power involving L87 engines after recall remedies and in later-production engines. As of August 31, 2026, EA26005 was an open investigation. It was not a new recall, a finding that the existing remedy was inadequate, or a determination of what caused any particular failure.

For an owner whose recall service was completed before an alleged failure, the immediate questions are vehicle-specific: Which remedy was performed? What test results supported that decision? Which engine was installed? What diagnostic and programming records exist? And can the engine or removed components be preserved without unsafe operation or unauthorized interference with a repair?

The Short Answer: EA26005 Is an Investigation, Not Another Recall

EA26005 grew out of Recall Query RQ26001. ODI opened that query on January 16, 2026, after receiving 36 owner questionnaires alleging engine failure following completion of Recall 25V-274 remedies. The allegations involved both branches of the recall remedy. ODI then opened the Engineering Analysis to evaluate alleged post-remedy failures and reports involving engines produced after the period identified in the original recall.

As of August 31, 2026, NHTSA’s EA26005 record listed no associated new recall. Recall 25V-274 remained the existing recall. An Engineering Analysis allows ODI to examine allegations and supporting evidence more closely; the opening of one does not itself establish a defect, causation, or remedy failure. EA26005 could lead to further agency action, or the investigation could close without another recall.

The investigated scope includes L87-equipped model-year 2021–2026:

Chevrolet Silverado 1500, Tahoe, and Suburban;
GMC Sierra 1500, Yukon, and Yukon XL; and
Cadillac Escalade and Escalade ESV vehicles.

A model name and year do not, by themselves, establish that a particular vehicle has an L87 engine, was included in Recall 25V-274, completed the recall remedy, or has an unrepaired recall. Those questions require VIN- and vehicle-specific records.

Recall 25V-274 and EA26005 Cover Different Questions and Populations

The existing recall and the open investigation overlap, but they are not interchangeable.

	Recall 25V-274	Engineering Analysis EA26005
Status	Existing safety recall	Open NHTSA investigation as of August 31, 2026
Population	597,571 U.S. vehicles	Estimated 997,743 vehicles in the investigation population
Model years	2021–2024	2021–2026
Engine	L87-equipped vehicles within the recall scope	L87-equipped vehicles within the investigation scope
Central question	Remedy for GM’s identified original suspect population	Alleged failures after recall remedies and reports involving later-production engines
What it does not establish	Why a specific later incident occurred	That every investigated vehicle is defective, recalled, or experienced a confirmed failure

What Recall 25V-274 Covers

Recall 25V-274 currently covers 597,571 U.S. model-year 2021–2024 L87-equipped vehicles. GM identified the original suspect-engine production period as March 1, 2021, through May 31, 2024.

In its revised Part 573 filing, GM described two primary alleged root causes for the original recall population: sediment-related rod-bearing damage and crankshaft dimensions or surface finish outside specification. Those were GM’s findings concerning the original recall population. ODI has not determined through the EA26005 opening record that either mechanism explains the alleged post-remedy or later-production failures now under investigation.

What EA26005 Is Examining

EA26005 covers an estimated 997,743 model-year 2021–2026 L87-equipped vehicles. It examines two broad groups:

allegations of engine failure after a Recall 25V-274 remedy; and
reports involving L87 engines produced after the production period cited in that recall.

The 997,743 figure is an investigation population. It is not the number of recalled vehicles, confirmed failures, owner complaints, or vehicles NHTSA has found defective. It also does not mean every model-year 2021–2026 vehicle listed above is recalled.

What the Complaint Numbers Say—and What They Do Not Say

The figures in the EA26005 opening record describe different complaint groups and datasets. Some overlap. They should not be combined into one total or used to calculate a failure rate.

Figure	What the opening record says it represents	What it does not establish
499	ODI complaints alleging post-remedy engine failure in vehicles subject to Recall 25V-274	499 technically confirmed failures from one cause
473	The portion of those 499 allegations reported after the oil-viscosity remedy	That 0W-40 oil caused the alleged failures
26	The portion of those 499 allegations reported after complete engine replacement	That replacement engines had or failed from the original recall condition
191	Separate reports involving L87 engines produced after the recall’s cited production period	That the original production window was incorrect or every later engine is defective
690	ODI incidents combining the 499 post-remedy allegations and 191 later-production reports	A count to add to the manufacturer dataset
6,953	Post-remedy complaints reported by GM	6,953 independently confirmed failed engines
6,050	Total incidents NHTSA listed after eliminating “duplicates received by the manufacturer”	A defect count or defect rate

Alleged Failures After Recall Remedies

RQ26001 began after 36 owner questionnaires alleged engine failure after completion of Recall 25V-274 service. By the opening of EA26005, ODI reported 499 complaints alleging post-remedy engine failure in recalled vehicles: 473 following the oil-viscosity remedy and 26 following complete engine replacement.

That timing is relevant to the investigation, but it does not establish a mechanism. The 473 allegations do not show that 0W-40 caused an engine failure. The 26 allegations do not show that replacement engines contained the original defect or failed for the same reason as engines in the original recall population. The opening record also does not supply remedy-branch denominators that would support a comparison of relative failure rates.

Reports Involving Later-Production Engines

ODI separately received 191 reports of L87 engine failure involving engines produced after the period cited in Recall 25V-274. Those reports explain why the Engineering Analysis reaches beyond the original production window. They do not prove that GM’s original window was wrong, that the original recall condition extends to later engines, or that every 2025–2026 L87 engine is defective.

Why 690, 6,953, and 6,050 Are Not Additive

The 690 ODI incidents consist of the 499 alleged post-remedy incidents plus the 191 later-production reports. GM separately reported 6,953 post-remedy complaints. NHTSA listed 6,050 total incidents after eliminating, in the opening resume’s words, “duplicates received by the manufacturer.”

These categories overlap and cannot be added together. The opening materials do not explain the complete method used to reach the 6,050 total. None of the figures is a count of technically confirmed, identical engine failures. Without validated incidents and a clearly defined denominator, the figures do not establish a defect rate.

Crash, Fire, Injury, and Causation Limits

The EA26005 opening table records one incident in a combined crash/fire category, one injury incident involving one injury, and no fatality incidents. The table does not distinguish whether the crash/fire entry was a crash, a fire, or both. The opening information also does not establish that an L87 condition caused an event or injury, and it leaves open whether the crash/fire and injury entries concern the same event.

What Recall Service Records May Show

When an alleged failure follows completed recall service, saying “the recall was done” leaves out the most useful details. Recall 25V-274 directed dealers to inspect the engine and choose between two remedy branches. If the engine failed inspection, the current remedy description calls for repair or replacement as necessary. Vehicles that passed received the oil-related remedy. The VIN-linked repair order and service history may show which branch was followed, when the work occurred, and what information supported the decision.

The Two Remedy Branches

Under GM’s recall bulletin, the dealer was directed to inspect the engine and then:

repair or replace the engine as necessary if it failed inspection; or
for an engine that passed, install higher-viscosity 0W-40 oil, a new oil filter and oil-fill cap, and an owner’s-manual insert.

Neither a model-year assumption nor a general statement that the recall was completed establishes which branch a specific vehicle received. The repair order, labor and parts entries, technician narrative, and VIN-linked service history may answer that question.

The Diagnostic Path Behind the Remedy Decision

GM’s diagnostic procedure changed during the recall, so the service date and bulletin revision matter. Earlier bulletin revisions instructed technicians to export a selected waveform region as a CSV for an automated pass/fail result. By February 2026, Revision 12 had removed manual data collection and entry: GM Waveform Capture automatically recorded, saved, and uploaded data, displayed a pass/fail result, and generated a warranty claim code.

Depending on when the service occurred and which revision governed the work, existing records that may help reconstruct the recall visit include:

the recall repair order and GM Investigate Vehicle History;
pre- and post-service DTC scans;
a legacy CSV from an earlier procedure, or later automatically captured or uploaded waveform data;
the pass/fail output and, under the later procedure, the warranty claim code;
technician worksheets and notes;
Techline or SPS records and relevant software versions;
mileage recorded during the work; and
parts and labor codes.

It should not be assumed that every dealer retained every item or that an owner will automatically receive each record. Public materials do not establish retention periods or owner access for automatically captured waveform data. The existence, retention, and availability of revision-specific records are questions to address promptly. A legacy CSV, captured waveform data, or a pass/fail result does not by itself prove whether an engine was defective; it documents information used in the procedure that governed the recall visit.

Evidence to Identify and Preserve After an Alleged Post-Recall Failure

Safety comes first. An owner should not drive, restart, test, modify, or disassemble a vehicle believed to be unsafe merely to reproduce a symptom or create evidence. Safe handling and necessary work should be coordinated through appropriate channels. Evidence preservation should focus on documenting the current condition and identifying existing records and components without unauthorized interference.

1. Tie the VIN to the Complete Service Timeline

Create a chronology that connects the vehicle and its engine to the relevant events. Useful items may include:

the VIN and records confirming L87 equipment;
Recall 25V-274 status and completion date;
mileage at recall service and at the alleged failure;
recall and other repair orders;
dealer and warranty history;
prior engine-replacement history;
later visits, warning complaints, and diagnostic work;
towing and incident records; and
communications with the dealer, manufacturer, insurer, tow operator, or storage facility.

A public NHTSA VIN lookup may identify an unrepaired recall. It is not a complete history of completed recall work, dealer diagnostics, programming, warranty service, or engine replacement.

2. Confirm Which Remedy Branch Was Actually Performed

Use the records rather than assumptions to determine whether the engine passed the recall test and received the oil-related remedy or failed inspection and was repaired or replaced as necessary. Record the dealer, date, and mileage. Look for repair-operation and labor codes, oil/filter/cap entries, an owner’s-manual insert notation, engine-repair or replacement entries, and the technician narrative where available.

This is a documentation step, not a conclusion that either remedy succeeded or failed on that vehicle.

3. Preserve the Revision-Specific Diagnostic and Electronic Records

The recall visit’s date and governing bulletin revision determine which diagnostic records may exist. Earlier service may have produced a legacy CSV and pass/fail output. Under the procedure in place by Revision 12, GM Waveform Capture automatically recorded, saved, and uploaded waveform data before displaying a pass/fail result and generating a warranty claim code. A prompt written request can ask whether the applicable legacy or later records still exist, along with DTC scans, Techline or SPS records, software-version information, and technician worksheets.

The request should seek preservation of existing material without assuming that every record was retained or that the requester has an automatic right to receive every item. Keep copies of the request and any response.

4. Record Engine Identity Before Anything Is Changed

Engine identity may matter, especially if the vehicle received a replacement engine before or during the recall process. Without dismantling the vehicle, safely document or request documentation of:

engine build-date labels;
part numbers and serial identifiers, if available;
component or design versions reflected in existing records;
any replacement date; and
records linking the original and replacement engines to the VIN.

GM’s replacement-engine instructions called for checking earlier engine-replacement history and reading the installed engine’s build-date sticker. Identifiers that are not safely accessible may need to be documented by a qualified person rather than the owner.

5. Address the Engine and Removed Components Before Return or Disposal

GM stated that returned engines would be inspected to confirm failure. If an engine or internal component is removed after an alleged post-remedy event, it may become important physical evidence. Preservation should be discussed before teardown, alteration, destruction, disposal, shipment, or a core return when reasonably possible and safe.

That does not mean an owner necessarily owns or controls the engine or can personally retrieve it. Possession, warranty terms, ownership, dealer or manufacturer procedures, storage space and cost, and case-specific requirements may all matter. An owner should not remove parts, interfere with necessary safety work, or take a component without authorization.

In litigation, Oregon ORCP 43 A(1) and Washington CR 34(a) authorize a party to request relevant documents, electronically stored information, and tangible things within another party’s possession, custody, or control. Production from a nonparty generally follows a different subpoena process. These discovery rules do not create an automatic pre-suit right to possess an engine. Broader guidance on protecting vehicle and repair evidence after an incident explains why prompt, careful preservation matters.

Why a Post-Service Failure Does Not Answer What Caused It

The sequence—recall service followed by an alleged failure—matters, but timing alone does not identify the cause or responsible party. Depending on the vehicle-specific evidence, questions may involve the original vehicle condition, selection or implementation of the recall remedy, later service, a different failure mechanism, or another cause. That list frames issues to investigate; it is not a conclusion that any one explanation applies or a complete list of all possibilities.

EA26005 is examining mechanisms across post-remedy and later-production reports. It has not resolved those alternatives. Owners who need the broader framework can review how defect evidence differs from repair-negligence evidence, while keeping the GM investigation and the records for the particular vehicle at the center of this inquiry.

What Owners Should Do Next Without Risking Safety or Evidence

After an alleged failure following recall service:

Do not operate or test an unsafe vehicle. Arrange appropriate towing, storage, inspection, or other safe handling instead of trying to reproduce symptoms.
Document the current condition non-invasively. Preserve photographs and a contemporaneous account of warning lights, sounds, the sequence of any loss of power, mileage, location, and communications. GM’s original recall filing listed possible warnings such as knocking or banging, a check-engine light, hesitation, high RPMs, abnormal shifting, reduced propulsion, or a no-start condition. Those signs were described as possible, not universal, and their presence or absence does not determine cause.
Gather the VIN-linked record. Collect recall, repair, warranty, diagnostic, programming, replacement-engine, towing, and incident records.
Ask about preservation promptly. Determine who has the engine, components, and electronic records and whether teardown, shipment, core return, or disposal is planned. Address ownership and storage rather than assuming control.
Monitor two separate sources. Check the vehicle’s VIN-specific recall information and the live EA26005 record separately. An investigation update and a VIN’s recall status answer different questions.
Consider case-specific guidance after a crash or injury. If the alleged failure was connected to a collision or physical injury, timely advice may help address safety, possession, storage, and preservation before evidence changes. Information about Oregon product-liability claims may provide additional context, but an investigation or completed recall does not establish a claim or guarantee an outcome.

What Remains Unknown as EA26005 Continues

As of August 31, 2026, ODI had not publicly resolved several questions important to owners:

What mechanisms explain the oil-remedy, replacement-engine, and later-production reports?
Is there a relationship between any of those reports and the condition described in the original recall?
Which engine build dates, component or design versions, suppliers, and serial identifiers appear among the reports?
Which bulletin revision governed each recall visit, and which legacy CSVs or later automatically captured waveform data, pass/fail outputs, warranty claim codes, DTC scans, Techline or SPS records, software versions, and technician worksheets have GM or dealers retained?
Who possesses removed engines or internal components, and can they be preserved for independent inspection?
Will ODI seek a revised remedy, an expanded or new recall, other owner instructions, or no further action?

Those questions are why the live investigation status and the evidence for a particular vehicle should be kept distinct. A future agency update may change the population or regulatory picture, but it will not replace the need to examine what happened to an individual vehicle.

Frequently Asked Questions

Is EA26005 a new recall for GM 6.2L engines?

No. As of August 31, 2026, EA26005 was an open Engineering Analysis, and NHTSA listed no associated new recall. Recall 25V-274 remained the existing recall. The investigation could lead to further action or close without another recall.

Are all model-year 2021–2026 GM vehicles with a 6.2L engine recalled?

No. Recall 25V-274 currently covers 597,571 U.S. model-year 2021–2024 L87-equipped vehicles. EA26005 has a broader estimated investigation population of 997,743 model-year 2021–2026 L87-equipped vehicles. An investigation population is not a recall population, and model and year alone do not establish the engine or recall status of a specific VIN.

Do reports after the 0W-40 remedy show that the oil caused engine failures?

No. ODI reported 473 allegations following the oil-viscosity remedy, but the EA26005 opening record does not establish that 0W-40 caused those events. It also does not provide the data needed to calculate a failure rate for that remedy branch.

What records show how Recall 25V-274 was performed on a specific vehicle?

The starting points are the VIN-linked repair order and service history, including the service date and bulletin revision. Depending on when the work occurred and what was retained, relevant material may include the selected remedy branch, DTC scans, an earlier-procedure legacy CSV or later automatically captured or uploaded waveform data, pass/fail output, warranty claim code, technician notes, Techline or SPS records, software versions, mileage, and parts and labor codes.

What should happen to a failed engine or removed parts?

Preservation should be addressed promptly before alteration, disposal, shipment, or core return when it is safe and practical to do so. Possession and testing may depend on ownership, location, warranty arrangements, storage, and case-specific requirements. Owners should not remove, retrieve, or interfere with components without authorization.

Does an engine failure after recall service prove who is responsible?

No. Timing alone does not establish whether an event involved the original condition, remedy selection or implementation, later service, a different failure mechanism, or another cause. Vehicle-specific records, physical evidence, and appropriate technical evaluation are needed.

A Focused Review Can Start With the Records

If a completed Recall 25V-274 remedy was followed by an alleged loss of power, the most useful next step is often to secure the vehicle-specific timeline before records or components are lost. Johnson Law can review the available recall, service, diagnostic, incident, and preservation information with people seeking guidance after a crash or injury in Oregon or Washington. An investigation or record review does not guarantee that a viable claim exists or predict an outcome.

Sources and Source Notes

NHTSA EA26005 Opening Resume — investigation opening date, scope, population, complaint categories, and incident table.
NHTSA live EA26005 record — investigated models and investigation/associated-recall status.
NHTSA RQ26001 Opening Resume — January 16, 2026 opening and the initial 36 owner questionnaires.
NHTSA live Recall 25V-274 record — current recall population, scope, and general remedy wording.
GM revised Part 573 report for Recall 25V-274 — GM’s suspect production period, original alleged root causes, and possible warnings.
GM Safety Recall Bulletin N252494000, Revision 12 — current repair-or-replace remedy wording and the later GM Waveform Capture procedure.
GM Safety Recall Bulletin N252494000, Revision 02 — legacy diagnostic-procedure context and GM’s statement concerning inspection of returned engines.
GM replacement-engine Bulletin N252494002 — prior engine-replacement history and installed-engine build-date instructions.
NHTSA Information Request PE25001-01 — requested VIN-level production, component-version, warranty, repair-order, and replacement-part data.
Oregon Rules of Civil Procedure, ORCP 43 — party requests for documents, electronically stored information, and tangible things in litigation.
Washington Civil Rule 34 — party requests involving documents, electronically stored information, and tangible things in litigation.

This article provides general educational information based on public materials available as of August 31, 2026. It is not legal advice, does not determine what caused a particular engine failure or incident, and does not create an attorney-client relationship.