Marine V-22 Osprey Damaged After Being Hit by Civilian Plane on Runway

A civilian aircraft collided with a sitting MV-22 Osprey last month in San Diego, resulting in millions’ worth of damage to the tiltrotor aircraft.

The Class A mishap, defined as one that involves fatalities, damage totaling $2 million or more, or a complete loss of the aircraft, happened May 30 at Brown Field, a Marine Corps official told Military.com. The incident was highlighted in a recently released Naval Safety Center accident report.

Read Next: Challenged by Netflix Show, US Space Force Rushes to Trademark Name

According to the official, the pilot of the civilian plane lost control of the aircraft, traveling across the runway and eventually impacting the Osprey. A spokesperson for Brown Field did not have additional details on what type of civilian aircraft was involved by press time.

“Aircraft routinely operate from Brown Airfield for training, 1st Lt Zachary Bodner, a spokesman for the 3rd Marine Aircraft Wing, said Tuesday.

An investigation into the incident is pending, he added.

In December, the Marine Corps received its first modified MV-22, with a modernized and streamlined configuration.

The “C” upgrade, under the Common Configuration-Readiness and Modernization (CC-RAM) program, moves more than 70 configurations into fewer than 17 variants for the aircraft, manufacturer Bell-Boeing said in a release at the time.

Naval Air Systems Command — which oversees the Osprey program — gave the joint venture company $57 million in 2017 to begin the CC-RAM program.

In 2019, NAVAIR awarded Bell-Boeing another $146 million contract to upgrade additional MV-22 aircraft.

— Oriana Pawlyk can be reached at oriana.pawlyk@military.com. Follow her on Twitter at @Oriana0214.

Related: The Military Still Wants a Belly Gun for the V-22 Osprey

Show Full Article

© Copyright 2020 Military.com. All rights reserved. This material may not be published, broadcast, rewritten or redistributed.

Source link

Leave a Reply

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