2025 Explorer or Aviator P1299? Prove the Temperature Before Calling It an Overheat

P1299: Prove The Temperature

When the warning appears, reduce load and stop safely; never open a hot system. Save the codes and compare coolant level, leak evidence, fan operation and an independent temperature reading before deciding whether the engine is truly hot. Only then check the VIN and current Ford history for the calibration route formerly described by 25B02. That order protects the engine without turning Ford’s software finding into permission to ignore steam, coolant loss or abnormal heat.

The useful tool category here is a controlled cooling-system pressure test after the engine is fully cold, but only after the safe test point and decision are clear. The AUTOOL SC301 is one practical route for that bounded step. SC301 can pressure-test and vacuum-fill a cooled compatible cooling system at Ford’s stated limits; it cannot make a hot engine safe, measure actual running temperature, read P1299, update the PCM or prove the warning is false.

Think of this case as two truths that must coexist. A red temperature warning deserves an immediate conservative response. A scoped calibration fault can also create that warning when the fan and cooling system are normal. The job is to preserve both possibilities until physical evidence separates them.

Stop first; decide later

Reduce load, turn off the A/C and pull over where the vehicle is protected from traffic. If there is steam, coolant odor, visible leakage, knocking, or a gauge that remains at the hot limit, shut the engine down and arrange a tow. Do not remove a pressure cap or add coolant while the system is hot. A software bulletin is never a roadside test for whether scalding coolant is present. If the warning disappears after a restart, photograph the original message if possible and still record the time, speed, outside temperature, grade, towing load and how long the engine had been running.

Save the three-code snapshot

Before codes are cleared, save P1299, P2C38 and P2C39 with status and freeze-frame. Record any fan-control, coolant-temperature, low-voltage or communication codes too. Ford’s program describes the three over-temperature codes in affected vehicles, but a different companion code can change the diagnosis. Note whether reduced power, limited acceleration or a capped top speed occurred. Those behaviors may be the controller’s protection response; they do not reveal whether the triggering temperature was physical or calculated. A complete before-scan gives the next technician the state that repeated key cycles can erase.

Compare warning state with physical temperature evidence

Once the engine is cold, compare the dashboard story with independent evidence: coolant level at the specified cold mark, fresh wet traces, dried residue, hose condition and an external temperature reading at appropriate points. Live coolant-temperature data should rise smoothly from ambient on a cold start. An implausible jump, disagreement with a contact or infrared check, or a normal physical temperature during the warning supports a signal or software branch. A genuinely hot engine, pressure loss or boiling keeps the mechanical cooling branch open regardless of VIN eligibility.

Evidence pair	Safer interpretation
Warning plus steam, loss or abnormal measured heat	Treat as genuine overheating until repaired
Warning plus normal physical temperature and normal cooled pressure test	Check scoped software and signal path
Normal temperature now but no saved event data	Do not guess; preserve the next event and inspect basics
Warning returns after current software	Reopen sensor, wiring and mechanical cooling diagnosis

Check coolant, pressure, flow and airflow as separate questions

Treat level, pressure, flow and airflow as four questions. Low level or a pressure-decay result sends the search toward leaks and cap integrity. A full system that heats quickly may need flow, thermostat or pump evaluation. Heat that builds mainly at low road speed makes airflow and fan command important. Air pockets can make a sensor alternate between coolant and vapor. Do not use one normal fan observation to declare the entire system normal, and do not pressure-test above Ford’s current limit to make a small leak reveal itself faster.

Match the Chicago build window and VIN record

The historical program covered certain 2025 Explorer and Aviator vehicles with 2.3L or 3.0L GTDI engines assembled in Chicago. Explorer build dates ran from November 29, 2023 through October 14, 2024; Aviator through October 15, 2024. The VIN had to appear in Ford’s system. A matching year, engine and symptom are not enough. Ask the servicing dealer to check current OASIS history, whether the PCM calibration was already installed, and whether another cooling-system communication applies to this VIN.

Treat the ended program date honestly

Program 25B02 stated an end date of March 31, 2026. That date has passed. Its technical explanation remains useful, but the old document is not a promise of present no-charge coverage, mobile repair or pickup service. Current warranty, campaign and goodwill decisions belong to Ford and the individual VIN record. Phrase the appointment request precisely: the vehicle displayed the warning with these codes, this physical temperature evidence was observed, and you want current calibration and service history checked—not simply ‘perform a free recall.’

Update software only through the current Ford path

When the physical cooling checks are normal and the VIN/calibration path fits, Ford’s directed action is PCM programming with approved access and stable support voltage. This is not equivalent to clearing codes or disconnecting the battery. Ask for the before-and-after calibration identifiers and a successful programming record. If programming fails, or if communication codes appear, recovery belongs inside Ford’s current service process. Mechanical parts should not be installed merely to make the red warning feel explained when the data and pressure evidence remain normal.

Verify one cold start and one controlled warm drive

Verification needs two states: a true cold start and a controlled warm drive that resembles the original event without creating danger. Confirm a smooth temperature rise, commanded and actual fan behavior, stable coolant level and absence of fresh leaks. Rescan all modules rather than checking only the MIL. If the warning returns with abnormal heat or pressure loss, stop and reopen mechanical diagnosis. If physical values remain normal and the three codes do not return after the correct calibration, the repair solved the driver’s problem without teaching anyone to ignore the next red warning.

A useful handoff contains the VIN, engine, build date, warning photo, complete code report, freeze-frame, cold coolant level, leak/pressure result, independent temperature comparison and installed calibration. That record lets the shop answer the real question—was the engine hot, or did the controller only believe it was—without asking the owner to gamble the engine on a bulletin title.

Official references

• Customer Satisfaction Program 25B02—PCM Software Update
• NHTSA Recall Lookup