Defense

August 20, 2012

Marines apply lessons from MV-22 crash throughout force

Tags:
by Jim Garamone
American Forces Press Service

An MV-22 Osprey prepares to fly Japan Defense Minister Satoshi Morimoto to Marine Corps Base Quantico following a joint press conference with Defense Secretary Leon E. Panetta at the Pentagon Aug. 3, 2012.

Pilots from throughout the Marine Corps are already applying lessons learned from the investigation of an MV-22 Osprey crash in Morocco in April, the chief of Marine aviation said in Washington, D.C., Aug. 17.

Marine Corps Lt. Gen. Robert E. Schmidle Jr. said the recently concluded investigation found no mechanical or material failures. “There were no issues with the safety of the aircraft,” he told reporters at a Pentagon news conference. He attributed the crash to “an extraordinarily complex set of circumstances.”

Two Marines – Cpl. Robby A. Reyes and Cpl. Derek A. Kerns – were killed in the incident and the pilot and co-pilot were injured.

The Marines were part of Marine Medium Tilt-rotor Squadron 231. The aircraft and Marines were part of the 24th Marine Expeditionary Unit aboard the USS Iwo Jima. They were participating in Exercise African Lion, a military exercise with Morocco, and had just delivered 12 Marines to the Moroccan training area.

Schmidle told reporters the aircraft took off with its nose pointed into the wind. Typically, the aircraft would move nose into the wind and fly off, he said. But rather than fly over troops and equipment, the pilots hovered the aircraft and rotated right. With the wind behind them, the pilots then shifted the aircraft propellers toward fixed wing flight. This caused the plane’s center of gravity to shift forward, pushing the nose down. That, plus a strong tailwind, caused it to crash, Schmidle said.

The aircraft could have flown as a helicopter and avoided the accident, he said. The crew also could have flown over the troops and equipment with no ill effects aside from downdrafts.

The Marine Corps will apply information from the accident investigation where it makes sense to do so, the general said. “There are some things we are going to do right away,” he said. “We are briefing all the MV-22 pilots and aircrew on this mishap … so they all understand what occurred and what caused this to happen with the tail wind component.”

The Marines will also make changes in simulation training to recreate the effect in Morocco so pilots can recognize the situation and take appropriate steps when they encounter it, he said. “In training, we are going to look and see what we can do in the academic syllabus,” Schmidle added.

More than half of the reporters attending today’s Pentagon news conference represented media from Japan, where there has been concern about the plane’s safety. Twelve Ospreys arrived in Japan in late July, and will eventually operate out of Marine Corps Air Station Futenma on the island of Okinawa. Many Japanese oppose the move and anti-Osprey groups say the aircraft is inherently unsafe. But Schmidle called the plane “solid and safe,” noting it has a 1.94 mishap rate per 100,000 flight hours – well below the rate for rotary wing aircraft.

Marine Corps officials have said their service chose the MV-22 to replace the 1950s vintage CH-46 helicopter because of its revolutionary capabilities. It takes off and lands like a helicopter but flies like a fixed-wing plane. It is twice as fast as the CH-46, can carry three times the payload and has approximately four times the combat radius.

 




All of this week's top headlines to your email every Friday.


 
 

 
Army photograph by C. Todd Lopez

Smart-mortar will help Soldiers more effectively hit targets

Army photograph by C. Todd Lopez Nick Baldwin and Evan Young, researchers with the Armament Research Development and Engineering Center at Picatinny Arsenal, Pennsylvania, discuss the 120mm Guided Enhanced Fragmentation Mortar ...
 
 

Air Force assigns new chief scientist

The Air Force announced the service’s new chief scientist to serve as a science and technology adviser to the secretary of the Air Force and the chief of staff of the Air Force, May 21. Dr. Greg Zacharias will be the 35th chief scientist and is ready to “dive in” to his new role. “I...
 
 

TSgt promotion release delayed to allow system validation

Technical sergeant promotion selection results, originally scheduled for release May 28, will be delayed to enable the Air Force to continue to validate extensive system changes to the Weighted Airman Promotion System, officials announced. The 15E6 technical sergeant promotion cycle is the first to incorporate recent changes in the enlisted evaluation and promotion system. Recent...
 

 

Freedom completes rough water trials

The littoral combat ship USS Freedom completed Seakeeping and Structural Loads Trials, commonly referred to as Rough Water Trials in late March the Navy reported May 21. The U.S. Navy must demonstrate the seaworthiness and structural integrity of each new ship class. One of the primary ways the Navy verifies these qualities is through a...
 
 

Air Force releases Strategic Master Plan

The Air Force officially released the Strategic Master Plan May 21, which is the latest in a series of strategic documents designed to guide the organizing, training and equipping of the force over the coming decades. The SMP builds on the strategic imperatives and vectors described in the capstone document, America’s Air Force: A Call...
 
 

HYT extension possible for SrA-MSgt in 35 career fields

Eligible senior airmen, staff sergeants, technical sergeants and master sergeants in 35 Air Force specialties will be able to apply for a high year of tenure extension and, if approved, will be able to extend between 12 and 24 months past their current HYT. The Air Force is introducing several personnel and manpower initiatives to...
 




0 Comments


Be the first to comment!


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>