A routine engine run-up of a U.S. Air Force KC-46 Pegasus tanker at an Alaska military airfield tore a crater roughly 25 feet wide into the runway surface, forcing a temporary halt to flight operations and adding to a growing list of problems with the troubled aerial refueling platform. The incident, which occurred during ground testing at Joint Base Elmendorf-Richardson, caused no injuries but left a gash in the tarmac large enough to sideline the runway while repair crews assessed the damage. For a tanker program already weighed down by years of delays and technical deficiencies, the episode raises pointed questions about whether the KC-46’s adapted commercial engines can withstand the demands of military operations in extreme environments.
What Happened on the Runway
During a standard ground engine test, one of the KC-46’s Pratt & Whitney PW4062 turbofan engines produced a force event severe enough to blow apart the runway surface beneath it. The resulting crater, estimated at 25 feet across, scattered asphalt and debris across the surrounding tarmac. Ground crews immediately shut down the test and cordoned off the area. No personnel were in the blast zone at the time, and the aircraft itself did not sustain structural damage visible to initial inspectors, according to base officials.
The scale of the damage is striking for what was supposed to be a controlled, low-risk procedure. Engine run-ups are performed regularly on military and commercial aircraft to verify powerplant performance before flight. They do not typically involve the kind of thrust output that would destroy hardened runway material. That this one did suggests either an abnormal engine event, such as an uncontained surge or compressor stall, or a flaw in the test setup that channeled exhaust energy directly into the pavement at close range.
Elmendorf-Richardson sits in Anchorage, where winter temperatures routinely drop well below zero and runway surfaces endure freeze-thaw cycles that can weaken asphalt over time. Whether the condition of the pavement contributed to the crater’s size or whether the engine output alone was responsible has not been publicly determined. The Air Force has opened an investigation but has not released preliminary findings. For now, officials have described the episode as an “anomaly” and emphasized that flight operations resumed on alternate surfaces while repairs continued.
A Familiar Pattern of KC-46 Setbacks
The crater is the latest in a long sequence of problems that have dogged the KC-46 since Boeing won the tanker contract over a decade ago. The aircraft, derived from the Boeing 767 commercial airframe, was designed to replace the aging KC-135 Stratotanker fleet. But its path from contract award to operational capability has been marked by cost overruns, missed deadlines, and a series of technical deficiencies that the Air Force has tracked in formal categories.
Among the most persistent issues has been the Remote Vision System, which allows boom operators to guide the refueling boom using cameras rather than a direct-view window. The system has suffered from image quality and depth-perception problems that made it difficult to safely connect with receiver aircraft, particularly in low-light conditions. Boeing has been working on a redesigned version, but the fix has taken years to develop and certify, delaying the tanker’s transition to full combat readiness.
Other documented problems include fuel leaks, cargo lock malfunctions, and stiff boom actuators that risked damaging receiver aircraft during contact. Each deficiency has required engineering changes, flight testing, and schedule adjustments that have pushed the KC-46’s full operational capability further into the future. The Alaska crater incident, while different in nature from these airborne issues, feeds the same concern: that the platform is not yet reliable enough to fill the role the Air Force needs it to play, particularly in demanding theaters where tankers must operate from remote or austere bases.
For Air Mobility Command, which is trying to balance the aging KC-135 fleet against the slow arrival of fully mission-capable KC-46s, every new problem carries operational consequences. Tankers are the backbone of U.S. global airpower, enabling fighters, bombers, and cargo aircraft to reach distant theaters. An aircraft that cannot be trusted to perform routine ground tests without damaging its own runway adds another layer of uncertainty to a program already under intense scrutiny from Congress and defense watchdogs.
Engine Failures and Runway Damage in Military Aviation
Craters caused by military aircraft are not unheard of, though they more commonly result from crashes than from ground tests. A useful comparison comes from a 2018 incident in which an F-16 fighter jet lost its engine and caught fire over Washington before crashing. The pilot ejected safely and survived, but the impact gouged a crater of similar scale into the ground. That event involved a full-speed crash of a single-engine fighter, not a stationary tanker running its engines on a test pad.
The fact that a ground-based engine run produced damage comparable to what a fighter jet crash left behind is what makes the Alaska incident so unusual. In the F-16 case, the kinetic energy of a falling aircraft combined with residual fuel created the crater. In the KC-46 case, the energy came from the engine alone, directed downward or rearward into the runway surface. That distinction matters because it implies the forces involved were far outside the expected parameters of a normal test, raising questions about thrust settings, aircraft positioning, and the integrity of the pavement.
Military runways and engine test areas are typically built to withstand jet blast. Concrete blast pads behind engine run-up positions are standard at most Air Force installations. Whether Elmendorf-Richardson’s test area met current specifications, or whether the KC-46 was positioned on a section of runway not reinforced for high-thrust operations, are questions the investigation will need to answer. If the tanker was inadvertently run at high power on standard asphalt rather than a dedicated pad, the root cause may lie as much in procedures as in engineering.
Cold Weather and Infrastructure Stress
Alaska presents unique challenges for military aviation infrastructure. The freeze-thaw cycle that characterizes Anchorage winters can degrade asphalt and even concrete over time, creating subsurface voids and weakened layers that may not be visible from above. If the runway section where the test occurred had accumulated hidden damage from years of thermal cycling, it may have been more vulnerable to the forces generated by the KC-46’s engines than a similar surface at a temperate-climate base.
This does not excuse the outcome. Military bases in Alaska are supposed to maintain their runways to standards that account for local conditions. But deferred maintenance is a well-documented problem across the Department of Defense’s infrastructure portfolio. The Government Accountability Office has repeatedly flagged a backlog of facility repairs at military installations nationwide, and Alaska bases, with their harsh conditions and remote logistics, are among the most expensive to maintain. When budgets tighten, airfield resurfacing and deep structural repairs can be tempting targets for delay.
If the investigation finds that pavement degradation played a role, the incident becomes less about the KC-46 specifically and more about whether the Air Force is investing enough in the ground infrastructure that supports its most expensive aircraft. In that scenario, the crater would be a warning that even proven platforms can be compromised by aging runways and underfunded maintenance. Conversely, if the engine itself or the way it was operated was at fault, the implications would cut directly to the tanker program’s technical maturity, suggesting that Boeing and the Air Force still have work to do to understand how the Pegasus behaves at high power in harsh environments.
What Comes Next for the Pegasus
For now, the Air Force is treating the Alaska crater as an isolated event pending the outcome of the investigation. Engineers are examining the damaged surface, reviewing engine data from the run-up, and interviewing ground crews about the test setup and procedures. Depending on what they find, the service could issue new guidance on where and how KC-46 engine runs are conducted, restrict power settings during ground tests, or order inspections of other run-up areas at cold-weather bases.
Boeing, already under pressure to resolve the tanker’s open deficiencies, will be watching closely. If investigators trace the event to an engine anomaly or an interaction between the PW4062’s exhaust flow and the KC-46 airframe that was not fully anticipated, the company could face another round of design reviews and possible modifications. Even if the root cause lies primarily in the runway, the optics of a high-tech tanker tearing up its own operating surface are unlikely to help a program that has struggled to convince skeptics it is ready for front-line duty.
Ultimately, the Alaska crater underscores how fragile the margin can be between routine operations and disruptive mishaps when new aircraft meet old infrastructure in extreme climates. Whether the KC-46 Pegasus emerges from this episode as a victim of a weakened runway or as the source of yet another technical headache, the incident adds one more data point to a narrative that Air Force leaders would prefer to change: a flagship tanker that, years after its debut, is still fighting to prove it can do the basics reliably, from the flightline up.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
