FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

2000 Marana V-22 crash

8 Apr 2000 · Marana Northwest Regional Airport

United States Marine Corps Bell Boeing V-22 Osprey · Vortex ring state

Report a problem

Event

Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
Event fatalities
19 · all aircraft and ground
Ground fatalities
Unknown
Occupants
Unknown
Survivors
0
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Military

Bell Boeing V-22 Osprey

Aircraft type
Bell Boeing V-22
Category
Powered-Lift · from aircraft type
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
Unknown
Onboard fatalities
19
Route
From not recordedTo not recorded

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

On 8 April 2000, a V-22 Osprey aircraft operated by the United States Marine Corps crashed during a night training exercise at Marana Regional Airport near Tucson, Arizona. The crash killed all 19 U.S. Marines on board and intensified debate about the reliability of the Osprey.

It was later determined that the aircraft had entered an aerodynamic condition known as vortex ring state, which resulted from a high rate of descent compounded by pilot error. As a result of the investigation findings, the V-22 was subject to further redesign, and eventually entered operational service in 2007.

Accident

On 8 April 2000, a V-22 Osprey, callsign Nighthawk 72, being flown by Major Brooks Gruber and Lieutenant Colonel John Brow was conducting a nighttime training exercise simulating a combatant evacuation at Marana Northwest Regional Airport in Marana, Arizona about twenty miles northwest of Tucson. The V-22 was carrying 15 passengers, all U.S. Marines from 3rd Battalion, 5th Marines, and was flying in a formation of four V-22s when the accident occurred. Two of the V-22s in the formation were actually carrying out the exercise while the other two were observing their performance.

As they approached the landing site, the pilots of the mishap V-22 realized they were 2000 ft above the required descent altitude and reduced power. As Lt. Colonel Brow maneuvered the aircraft to land, the Osprey entered an erratic roll, turning on its back and slamming into the ground nose first. All 19 Marines aboard the aircraft were killed. The second V-22 also made a hard landing but suffered no fatalities.

Investigation and cause

Investigation

Shortly after the crash an investigation was commissioned to determine its cause. The investigation ruled out most possible causes and narrowed in on the aircraft's rate of descent as the primary cause. Investigators compared the mishap aircraft's actual rate of descent with the V-22 flight manual's required rate of descent and found discrepancies. As the V-22 descended to land it was dropping at 2000 ft per minute, well above the prescribed 800 ft per minute. The speed caused the aircraft to enter an aerodynamic condition known as vortex ring state. In this condition, a vortex envelops the rotor, causing an aircraft to lose lift, in essence descending in its own downwash.

After two months of investigation by the Marine Corps Judge Advocate General a final report was released which absolved the aircraft itself of any mechanical faults and instead pinned the blame on the exceptionally high rate of descent coupled with human error.

The final arbiter in the debate is the determination in 2016 by then Deputy Defense Secretary Robert Work that vindicates the pilots in the crash, a battle that took 16 years.

Text from the Wikipedia article “2000 Marana V-22 crash” (revision 1359544976, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

Sources

Wikipedia article: 2000 Marana V-22 crash
Article
2000 Marana V-22 crash
Revision
1359544976 · 2026-06-15 · retrieved 2026-09-18
Wikidata
Q48850657
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
Where each value comes from
Record
Wikipedia article "2000 Marana V-22 crash" (page 56260634, revision 1359544976)
Date
Wikipedia infobox: date
Place and country
Wikipedia infobox: site; country from Wikidata (P17)
Map position
Wikipedia article coordinates
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
operator named as an armed force or military unit in the infobox
Fatalities
Wikipedia infobox: aircraft fatalities
Ground fatalities
not stated in the Wikipedia infobox
Summary
Wikipedia infobox: summary
Source notes (1)
  • Wikipedia · Facts from the Wikipedia article's infobox and coordinates, not checked against an investigation report. Independent review pending.