2025 Aviator Battery Dies Above 90°F? Track the Rear Camera Wake-Up

Battery Dies Only In Heat?

Record the overnight low, the parked duration and whether ambient temperature exceeded 90°F (32°C) before charging or disconnecting the battery. Ford says some 2025 Aviators can suffer an intermittent drain only above that threshold when the rear camera module keeps FD-CAN3 awake. A battery health check still matters, but the scoped correction is a current FDRS camera-module software update rather than another battery by default.

The first useful tool task is to separate a damaged battery from the event that discharged it, then monitor low-voltage leakage without changing the parked state. A technician could use the AUTOOL BT960 for that bounded battery and current evidence. BT960 can test compatible 12-volt lead-acid or supported lithium starting batteries and log leakage current in an appropriately arranged low-voltage circuit; it cannot identify the waking module, preserve every network sleep condition, run FDRS, install the camera update or prove that heat caused this discharge.

The strange part of this complaint is its selectivity. The SUV may behave normally through mild weeks, then need a jump after one hot night. That makes yesterday’s weather and the untouched morning state more useful than a generic list of things that drain batteries. Treat the vehicle like a night-shift witness: record what it did, when the temperature crossed the threshold and which network refused to go home. Only then does the rear-camera software path become more than a guess.

Write down the overnight temperature first

Use a weather app’s hourly history, not the afternoon forecast. Record the overnight high and low at the vehicle’s location, whether the Aviator sat in direct evening sun, when it was parked and when the no-start was discovered. Ford’s line is greater than 90°F (32°C), not simply ‘summer.’ Note whether the vehicle has failed below that temperature too; a broad all-weather pattern weakens this narrow explanation. If possible, keep a three-column log for date, hottest ambient and next-morning result. Two reproducible hot failures are far more useful to a shop than ‘it dies randomly.’

Preserve the first dead-battery evidence

Before connecting a booster, photograph the cluster response and measure battery terminal voltage if it is safe. Note whether interior lamps are dim, relays chatter, remote entry works or the starter clicks. Save a full module scan before clearing anything once stable power is available. A severely discharged battery can create a crowd of undervoltage and communication codes, so distinguish the first complaint from the aftermath. Stop if the battery is hot, swollen, leaking or damaged; do not repeatedly crank it. Charging restores a test foundation; it also changes the evidence, which is why the first observations matter.

Test the battery without ending the investigation

A battery can be both the victim and, after repeated deep discharge, part of the continuing problem. Charge it by the Lincoln procedure, confirm the correct battery type and test conductance or load capacity. Inspect terminals and charging-system performance. If it fails, replacement may be justified—but ask what pulled the replacement down. If it passes, do not translate that into ‘nothing is wrong.’ Ford’s software condition is intermittent and temperature-dependent. Record the test result, installed date and state of charge so the next hot soak begins with a known battery rather than another unknown.

Recreate the parked state on a hot day

Reproduction needs the same parked state: normal shutdown, doors and liftgate closed, keys moved away, no phone app polling, accessories unplugged and enough time for modules to sleep. Set up measurement before the final closure where the current procedure allows. Opening a door midway can wake multiple networks and hide the original offender. Do not defeat latches or safety systems casually. Compare a cooler overnight soak with a soak above the threshold, keeping duration and user actions similar. The goal is not to bake the vehicle artificially; it is to see whether ordinary hot-weather parking changes sleep behavior.

Observation	Stronger meaning	Next move
Fails only after nights above 90°F	Ford heat gate is plausible	Preserve hot-soak network data
Battery fails after full charge	Battery damage is now real	Replace if specified, then find the draw
FD-CAN3 remains active with CMR implicated	SSM branch is earned	Check current FDRS application
Current software, draw still present	This bulletin is not the whole answer	Resume standard sleep-current isolation

Watch FD-CAN3 rather than pulling random fuses

Random fuse pulling is a poor first move on a multiplexed SUV. Each pull can wake modules, create codes and change the current path. Ford identifies the rear camera module as capable of keeping FD-CAN3 awake, so the shop should use FDRS and an appropriate current/network capture to see whether that bus continues activity after other systems settle. Record current versus time and the moment FD-CAN3 goes quiet—or does not. A high total draw alone does not name the camera; network activity and module response are what connect the symptom to this branch.

Confirm the rear camera module branch

Confirm the model year, the exact SSM number and whether the current FDRS application offers the CMR Driver Status Monitor Camera Module software update. The camera in this bulletin is not the ordinary reversing image viewed by the driver, and a clear rear-camera picture does not prove the module slept. Conversely, a separate camera image fault needs its own diagnosis. If unplugging, commanding or observing the CMR changes the measured state under Ford’s procedure, preserve that result. Do not replace the camera merely because it is named in a bulletin whose temperature and network gates were never reproduced.

Use FDRS for the scoped software correction

The repair is a software application run with the latest Ford Diagnosis and Repair System, not a universal battery reset. Prepare stable 12-volt support exactly as Ford requires, keep the laptop and interface powered and let FDRS identify the correct file. Record the prior and new module levels. If programming is interrupted, follow Ford recovery instructions instead of cycling connectors. The update should not be attempted through a generic scan function, and a battery tester cannot supply the proprietary application. If FDRS shows the current calibration already installed, return to ordinary parasitic-draw diagnosis.

Verify across another hot soak

Verification should challenge the original trigger. Fully charge the proven battery, shut the vehicle down normally and repeat an overnight soak when ambient temperature again exceeds 90°F. Log sleep current and FD-CAN3 state without repeatedly waking the SUV, then record morning voltage and starting behavior. One cool-night pass does not test the complaint. If the draw survives the current software, give the shop the time-current trace and broaden the search; do not reinstall the same update or condemn the battery again. A real fix survives heat, sleep and the next start together.

The useful answer is not ‘buy another battery’ or ‘the camera is bad.’ It is a controlled comparison between a cool sleep and a hot sleep, starting with an independently proven 12-volt battery. When FD-CAN3 remains awake and the vehicle matches Ford’s scope, the CMR software update is a focused correction. When those gates are absent, the diary keeps an intermittent draw from becoming an expensive story about the wrong part.

Official references

• Ford SSM 55087—2025 Aviator Hot-Weather 12-Volt Battery Drain
• NHTSA Recall Lookup