• Please take a moment and update your account profile. If you have an updated account profile with basic information on why you are on Air Warriors it will help other people respond to your posts. How do you update your profile you ask?

    Go here:

    Edit Account Details and Profile

Marines/A-10 Friendly Fire Incident

Status
Not open for further replies.

ElPensador

Registered User
I just saw this on the news and looked it up on the net. Anyone else hear of this?


http://edition.cnn.com/2004/US/03/29/iraq.friendly.fire/


(CNN) -- A report released Monday by U.S. Central Command recommends disciplinary action against a U.S. Marine Corps captain who called in airstrikes on his fellow Marines in the deadliest "friendly fire" incident of the Iraq war.

Eighteen Marines were killed during a battle March 23, 2003, in Nasiriya. But because some of the bodies had been hit by both U.S. and Iraqi weapons, investigators could confirm only eight deaths by hostile fire.
 

flynglthrnk

USMC PLC
Make sure you read the article and not just the quote posted. After reading the second half titled "The ground just explodes" it seems as though they are trying to blame the Air Force and the article portrays it as being kind of suspicious. The mistake was probably caused by a combination of the Marine Captain and the Air Force pilot's error.
 

ElPensador

Registered User
Yeah it seems as if the Marine captain messed up in giving the order for the air strike, and the Air Force pilots weren't trained to recognize Marine vehicles, so they fired on them.

This makes me wonder: why would the Marines rely on Air Force for close air support, since they wouldn't be trained to recognize the vehicles? Isn't that one reason why there are Marine aviators to support the Marines on the ground? Or were there none in the area? Anyone? Anyone?

Of course, none of the articles on the net have all of the details, and there's no report posted yet at the Central Command website(http://www.centcom.mil/CENTCOMNews/newsfeatures.asp), where it was reported to have been...
 
Pensador, I think it all has someting to do with the whole unified command thing. Correct me if I'm wrong, but this also happened back in Desert Storm One.

One of the things the AF(or at least Horner) took with him from Vietnam is the belief that dividing up an operating area into Navy air and AF zones is dumb.
So in DS One, Horner legally had control of Navy and Marine air...which means the Marines don't always have their "own" air arm any more whenever they're under joint control.
Same goes for the Navy.

I have to wonder though, from a pilot's perspective, is it really easy to tell a AAV from a pickup truck? I don't know what altitude the A-10 guys were at but I'd figure they'd be worried enough about eating a MANPAD in the ass.
 

Flash

SEVAL/ECMO
None
Super Moderator
Contributor
Air Force pilots weren't trained to recognize Marine vehicles, so they fired on them.

Not exactly.

I have to wonder though, from a pilot's perspective, is it really easy to tell a AAV from a pickup truck?

No.

From everything I have read, this unfortunate incident can be attributed to the fog of war. The Marine FAC was attached to another unit and did not know that Marines were across a key bridge. He apparently did not check through a more senior commander, though he had authorization from the CO on the scene.

Trying to tell the difference between a AAV and any other Armored vehicle from the air is very difficult. That task is made even worse when you are trying to avoid getting your ass shot off and the battle is occuring in the middle of a city, not open desert. Even though there were steps taken to prevent this kind of incident from occuring, it is almost inevitable this kind of thing will happen. As for the Marines having to rely on the USAF for support I have one word for you, joint. Anyways, the A-10 is probably the best CAS plane around and the pilots feel and act closer to the grunts on the ground than any other AF types. They take perverse pride in being the bastard stepchildren of AF Tacair.
 
Status
Not open for further replies.
Top