USS Abraham Lincoln Ends a Record 266-Day Deployment. Its Next Homeport May Be Bremerton.

The USS Abraham Lincoln is ending a deployment the Navy would rather explain than defend. After 266 days at sea, more than 200 of them without a single port call, the aircraft carrier is heading home following weeks of reporting on moldy showers, rationed food, holes in the flight deck and sailors who tried to jump overboard. Acting Navy Secretary Hung Cao announced the return without naming a date. Addressing families directly, he was unable to say exactly when the ship would arrive, telling them only that it would happen "soon." What Cao did not say, and did not have to, is where the Lincoln is ultimately headed to live once its Navy career settles back into a routine. The Navy's own chief of naval operations has already said he expects the ship's next permanent homeport to be Naval Base Kitsap, in Bremerton — a decision that predates this week's crisis and will outlast it.

A 266-Day Deployment That Kept Extending

The Lincoln left San Diego in November on what the Navy initially described as a routine deployment to the Pacific and South China Sea. That changed in January, when the carrier strike group was redirected toward the Middle East ahead of the U.S.-Israeli strikes on Iran that began in late February. An expected May return date came and went with no replacement date announced. By the time Cao spoke this week, the ship had logged 266 total days deployed, more than 200 of them in a combat zone without pulling into a foreign or domestic port, according to TIME. Across that stretch, the strike group has enforced a U.S. blockade of Iranian ports and, by the Navy's own account, shot down "hundreds and hundreds" of missile and drone attacks aimed at American and allied forces in the region.

A carrier deployment built for roughly six to seven months stretching past nine is not, on its own, unheard of. What made the Lincoln's cruise different is that the extension had no announced end point for months at a time, and the ship's roughly 5,000 sailors and Marines had no fixed date to plan a homecoming around. Families told reporters that not knowing, more than the deployment's raw length, was what wore crews down fastest. A carrier at sea for nine months is still a carrier with a calendar; one at sea for an undefined "until further notice" is something else entirely, and that distinction runs through nearly every account of what went wrong aboard.

What Sailors and Families Say Went Wrong Aboard

Multiple outlets, drawing on interviews with sailors and their families, documented conditions that went beyond routine deployment hardship: moldy showers, missing basic toiletries like toothpaste and soap, food shortages that led to rationed meals, contaminated water, holes in the flight deck and persistent plumbing failures, according to TIME's reporting. Work shifts ran long with few days off across a deployment that offered almost no chance to decompress on land, let alone see family, for the better part of nine months. None of those complaints are exotic on their own. Sailors on long deployments have griped about food and berthing conditions for as long as there have been carriers, but the density of them, stacked across a cruise that kept extending with no fixed end, is what turned routine hardship into a story the Navy could no longer wave off.

The sharpest evidence of strain came from the mental-health toll. Families told reporters that multiple crew members had attempted to jump overboard during the deployment. TIME reported that one sailor went overboard on August 3 and was recovered within the hour; the Navy classified the incident as a mental-health case rather than an accident. Cao, addressing the concerns directly, said "the safety and security of our Sailors and Marines always comes first," but also acknowledged the strain in blunter terms than the Pentagon had used previously: "War is hell and normal routines are disrupted. There is no question our young men and women have been pushed to their limits." He said no service member had died aboard the ship during the deployment, a distinction the Navy has repeated carefully even as it concedes more of what families described.

The Navy's Denials Don't Match the Documentation

The response from the Pentagon and the White House, for months, was to dispute the severity of what families and sailors described rather than address it. Defense Secretary Pete Hegseth called the reporting "completely misrepresented." President Trump waved off the concerns entirely, saying the Lincoln had deployed "not nearly long enough." Adm. Daryl Caudle, the chief of naval operations, specifically denied food-shortage claims back in April, months before Cao's own acknowledgment this week that conditions aboard had pushed the crew "to their limits." Those two statements came from the same chain of command, roughly four months apart, about the same ship.

That gap is worth sitting with, because it isn't one outlet's word against the Navy's denial. It is the same set of facts: mold, rationed food, overboard incidents, a deployment that outran its own timeline, independently documented by TIME, Just The News and other outlets over successive weeks, while the Navy's public position moved from a flat denial in April, through Hegseth's "completely misrepresented" and Trump's "not nearly long enough," to a qualified, partial acknowledgment once the ship was already steaming home in August. The Lincoln's return doesn't resolve that gap; it just moves the argument about who was right onto dry land, where the sailors and their families, not the Pentagon's press office, are the ones left making the case.

Why the Navy's Own Leadership Points This Carrier at Bremerton

The Lincoln is currently homeported at Naval Air Station North Island in San Diego, and Cao's announcement this week was about that homecoming, not a permanent relocation. But the ship's longer-term future has already been signaled separately, months before this crisis broke. In June, Adm. Caudle told the Kitsap Sun that he expects the Lincoln's homeport to eventually shift north: "Reagan is going to stay here, and I believe that Abraham Lincoln will probably...change homeport to here as well," he said, referring to Naval Base Kitsap, according to Forbes. Caudle framed the move as part of a broader Navy shift toward the Indo-Pacific amid what he described as great-power competition with China, arguing a Bremerton-based carrier would allow faster deployment across the Pacific and to other global theaters than one based in San Diego.

Naval Base Kitsap, which spans more than 12,000 acres across its Bremerton and Bangor sites, is already the Navy's third-largest fleet concentration area and holds dry docks large enough to service a nuclear-powered carrier. It is not a new role for Bremerton, which has homeported carriers before this. What is notable is the timing: the base's next scheduled carrier, the future USS John F. Kennedy, isn't expected to arrive in the Pacific Northwest before fiscal year 2029, leaving a gap the Lincoln could plausibly fill years before then if Caudle's plan holds.

Read the Language Carefully — Nothing Here Is Finalized

It matters that Caudle's own words were hedged, not confirmed: "I believe" and "will probably" are the language of an admiral describing a plan still in motion, not an order that has been signed. No Navy official, including Cao in this week's announcement, has put a date on a Bremerton homeport shift, and nothing about the Lincoln's current return to San Diego commits the ship to Kitsap on any fixed timeline. Readers who saw this week's homecoming headlines and assumed the carrier was steaming directly toward Puget Sound are getting ahead of what the Navy has actually said on the record, and, for that matter, ahead of the dry-dock and rotation scheduling that would have to line up before any ship physically changes coasts.

That distinction cuts against the instinct to treat every Lincoln headline as a Kitsap headline. The crisis aboard the ship this week is about a deployment that just ended, and a homecoming that is happening in San Diego, not Bremerton. The homeport question is a separate, slower-moving Navy planning decision that predates this crisis by months, was already public well before the overboard incidents made national news, and will keep moving on its own schedule regardless of how this week's return is remembered. Conflating the two would overstate how settled Bremerton's role actually is, and would do a disservice to a story whose two halves genuinely don't move at the same speed.

What a Homeport Shift Would Actually Mean for Kitsap

If the shift happens as Caudle described, the practical impact on Kitsap County would be substantial and slow-building rather than immediate. A carrier crew of roughly 5,000 sailors and Marines, even accounting for turnover and the share of family members who don't relocate at once, represents a meaningful population and housing draw in a county whose largest employer is already the Navy through the Puget Sound Naval Shipyard. Homeport shifts of this scale typically phase in over a year or more between an announcement and a ship's actual arrival, tied to dry-dock scheduling, maintenance availability and crew rotation cycles rather than a single move-in date, which is one more reason nothing here should be read as imminent.

For a county that already anchors a large share of its economy to shipyard work, a Lincoln homeport would be additive to a role Bremerton already plays rather than a new one. Naval Base Kitsap's dry docks exist precisely because carriers have called this stretch of Puget Sound home before. But it would also mean absorbing a crew shaped by exactly the kind of scrutiny this week's headlines describe: sailors and families who, whenever they eventually arrive, will carry fresh memories of a 266-day deployment the Navy spent months publicly denying and is only now, partially, admitting went wrong. A community that welcomes a carrier crew is also, in a real sense, welcoming whatever came home with it.