![\"\"](\"https:\/\/www.azuse.cloud\/wp-content\/uploads\/2025\/09\/cca1fed286759e5c53381ee608f1cf1b-300x169.webp\")
<\/p>\n<\/p>\n
<\/p>\n
You may remember a bit back when an F-15 had an unfortunate mid-air refueling experience with one of our new KC-46 tankers (the ones supposed to replace the aging 707-based KC-135 and KC-10 tankers.) At the time it was speculated that the boom had malfunctioned and caused the accident. The boom literally fell off the tanker into the desert<\/p>\n
In an unusual disclosure, the Air Force released accident reports for all three mishaps together, with a single press release.<\/p>\n
After an early morning take-off from Travis Air Force Base, California, on Aug. 21, 2024, the Kansas-based KC-46 met with two F-15Es for a routine mid-air refueling. One of the jets tried four times to hook up to the plane\u2019s refueling boom, but the fighter\u2019s pilot had trouble maintaining constant contact. His wingman connected for a full gas-up.<\/p>\n
On a final attempt, as the boom connected to the F-15E\u2019s fuel port, the fighter continued to fly towards the tanker, compressing the boom to 3.75 feet, more than two feet shorter than its normal operation. Then, as the two jets tried to separate, the boom momentarily caught in the F-15E\u2019s fuel port. As the F-15 eased back, it pulled on the stuck probe with 7,404 pounds of force, extending the boom 17 feet.<\/p>\n
In the few seconds the jet was stuck, the boom operator tried to fly the boom upwards. When the probe finally released from the F-15, the upward push from the boom operator caused the boom to spring violently upwards, smashing into the bottom of the KC-46\u2019s tail section.<\/p>\n
\u201cThe boom reached a peak fly-up rate of 114 degrees per second,\u201d the report found, before smashing into the underside of the tanker.<\/p>\n
The damage, officials said, totaled $14,381,303.<\/p><\/blockquote>\n
Yeah, that’s an owie. And only the most recent of three.<\/p>\n
\nOn Oct. 15, 2022, a KC-46 from Joint Base McGuire-Dix-Lakehurst flew a routine training mission to refuel a flight of F-15Es from Seymour Johnson Air Force Base, North Carolina.<\/p>\n
Similar to the 2024 accident, the boom\u2019s nozzle became stuck in the F-15 after a mistake by the boom operator and the failure of the F-15E pilot to recognize the condition. Also, like the 2024 accident, when the boom finally released, the operator\u2019s actions caused the boom to spring upwards forcefully and strike the underside of the KC-46, causing over $8 million in damage.<\/p>\n<\/blockquote>\n
You may also recall that the KC-46 does away with the rear boom operator’s position, and has a remote camera array for the boom operator\u00a0 to use.<\/p>\n
\nIn that 2022 flight, an accident board found, the boom operator \u201cinadvertently placed a radial force on the ARB that caused the nozzle to become bound in the receiver\u2019s receptacle. As a result, the bound forces exceeded the structural limitations\u201d of the boom and \u201ccaused a rapid upward movement\u201d that struck the plane.<\/p>\n
But unlike the 2024 mishap, the accident board found the operator\u2019s mistakes were neither intentional nor preventable, but were due to a poorly designed flight control system, or FCS.<\/p>\n
\u201cA pattern begins to emerge which leads me to conclude that this FCS input by [the boom operator] was inadvertent and due to a limitation of the KC-46 [boom] control system,\u201d investigation board President Col. Chad Cisewski wrote. \u201cIt is not a reasonable conclusion that [the boom operator] could have recognized his inadvertent input and corrected the situation with the current [boom] control deficiencies.\u201d\u00a0 \u00a0Task & Purpose<\/a><\/p>\n<\/blockquote>\n
The third incident was minor, when it was found the RSV cameras had inadequate resolution to see if the boom was engaged properly – that only cost a bit over $100,000<\/p>\n
It’s sounding like there is plenty of blame to go around between design, boom operators, and refuelee pilots.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"