WASHINGTON — A deadly Osprey aircraft crash last November off the coast of Japan was caused by cracks in a metal gear and a Minnesota pilot’s decision to keep flying, instead of heeding multiple warnings that he should land, according to an Air Force investigation released Thursday.

The CV-22B Osprey crash killed eight Air Force Special Operations Command service members and led to a months-long military-wide grounding of the fleet. It’s among four fatal Osprey crashes in the last two years driving investigations into the Osprey’s safety record. It’s created a split among the services about the future role of the unique aircraft, which can fly like an airplane but land like a helicopter.

For months, the Air Force would only say an unprecedented component failure caused the crash. On Thursday, it identified that a toothed piece called a pinion gear — a critical part of the proprotor gearbox — was to blame. The proprotor gearbox serves as the aircraft’s transmission: Inside each gearbox, five pinion gears spin hard to transmit the engine’s power to turn the Osprey’s masts and rotor blades.

While the Air Force is confident it was the pinion gear that failed, it still doesn’t know why.

But Pentagon leadership in charge of the V-22 Ospreys knew that “total loss of aircraft and crew were possible” should those proprotor gearbox components fail, lead investigator Lt. Gen. Michael Conley told reporters Wednesday in a call ahead of the report’s release. In a rare move, the investigation also faulted that office, saying it did not share safety data that could have educated crews on the severity of the risk.

In an interview with The Associated Press, Conley said he believed it was the pilot’s instinct to complete the military exercise that drove his decisions.

“To a degree, it’s a way of life here. I mean, we want people in this command that that are biased towards ‘yes,’ biased towards getting the mission done,” Conley said. “As we went through the investigation, I saw someone that was confident in the aircraft but not cocky.”

On the day of the crash, the Osprey was flying along the coast of mainland Japan headed to Okinawa when the first indications of trouble began.

In aircraft, vibrations are monitored as signs of potential trouble. A data recorder noted vibrations on the left side of the driveshaft that links the two engines and acts as a fail safe in case one engine loses power.

A second vibration followed. This time one of the five pinion gears inside the left proprotor gearbox was vibrating.

But pilot and Andover, Minnesota native Maj. Jeff Hoernemann and his crew never knew about the vibrations, because that data can only be downloaded at the end of a flight.

Five minutes after the first vibration, a left proprotor gearbox chip burn warning posted in the cockpit. The warning lets the crew know there’s metal flaking coming off the Osprey’s gearing, another indication of stress.

Chipping is a common enough occurrence in rotary flight that there’s a safety net designed into the Osprey. The chip detector can burn the chips off so they don’t travel in the oil and destroy the transmission.

If the burn is successful, the warning clears.

The crew got six chip warnings that day. Each presented an opportunity for Hoernemann to heed the warning and land as a precaution but he did not, and investigators found that decision was a causal factor in the crash.

When the third chip burn warning posted, the crew was still close to mainland Japan and just 10 miles (16 kilometers) from its nearest airfield. The official guidance after three chip burns was to “land as soon as practical,” guidance that still leaves that decision to the pilot’s discretion.

According to the voice data recorder, Hoernemann and the crew were looking for secondary indications of a problem, such as the proprotor gearbox overheating, but saw none. So Hoernemann instead directed his co-pilot to keep monitoring the situation and elected to continue the 300-nautical-mile flight over water to Okinawa.

Hoernemann was likely balancing split priorities in his decision-making, the investigation found. He was leading the airborne portion of the military exercise and had spent months planning for it.

Until almost the final minutes of flight, he kept his primary focus on completing the exercise, not the evolving aircraft situation, the investigation found. He rejected his co-pilot’s suggestions on using an onboard mapping tool to identify the closest airfield to land. But the co-pilot was also not direct about “his uneasiness with the evolving issues,” the investigation found, based on the recovered voice data.

The fourth and fifth chip burn warnings came fast. Then with the sixth, escalation: just chips. It meant the Osprey could not burn them off. “Land as soon as practical” turned into “land as soon as possible.” Still, the crew members did not act with urgency.

In the final minutes of flight, they’d begun to position the aircraft to land. The Osprey was half a mile (0.8 kilometers) from an airfield at Yakushima, flying about 785 feet (240 meters) above the water.

But they waited again and deferred as Japanese traffic controllers told them to hold for local traffic to take off, even as Hoernemann confirmed over the radio they had an in-flight emergency.

The Osprey gave its final chip-related warning three minutes before the crash: chip detector fail. Hoernemann told the crew he was no longer worried, he now assumed the earlier warnings were errors due to a faulty chip detector.

Instead, investigators later found the fail message occurred because the detector “had so many chips on it, it couldn’t keep up,” Conley said.

Hoernemann then directed his co-pilot to “do one more big, right-hand loop and come in and just set up for landing.”

But inside the proprotor gearbox, the pinion gear was breaking apart. At least one piece wedged into the teeth of the larger transmission gearing system, jamming and breaking off gearing teeth until the left proprotor gearbox could no longer turn the Osprey’s left proprotor mast.

Within six seconds of the proprotor gearbox failing, catastrophic destruction splintered through the Osprey gearing and interconnected drive system. At that point, there was nothing the crew members could have done to save themselves or the aircraft, the investigation found.

The Osprey rolled violently, inverted twice with its left engine housing on fire and crashed into the water, killing all on board.

Following the crash, crews are now directed to land as soon as practical on a first chip burn and as soon as possible on the second. The joint program office is also working on a new system that would communicate vibration data in real time to pilots, to give them better awareness during flight.

The accident killed Maj. Eric V. Spendlove, 36, of St. George, Utah; Maj. Luke A. Unrath, 34, of Riverside, California; Capt. Terrell K. Brayman, 32, of Pittsford, New York; Tech. Sgt. Zachary E. Lavoy, 33, of Oviedo, Florida; Staff Sgt. Jake M. Turnage, 25, of Kennesaw, Georgia; Senior Airman Brian K. Johnson, 32, of Reynoldsburg, Ohio; Staff Sgt. Jacob M. Galliher, 24, of Pittsfield, Massachusetts; and Hoernemann, 32, of Andover, Minnesota.