Fratricide (military): Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Howard C. Berkowitz
imported>Howard C. Berkowitz
No edit summary
Line 1: Line 1:
{{subpages}}
{{subpages}}
{{TOC-right}}
'''Fratricide''', in a military context, happens when members of one's own forces are hit by fires from the same side, ''or'' weapons interfere with one another such that their effect is neutralized.  This is often called "friendly fire", although the apocryphal "[[Murphy's Law]]s of Combat" mention:
:*Friendly fire isn't.
:*When the pin is pulled, Mr. [[Grenade]] is no longer our friend. 


'''Fratricide''', in a military context, happens when members of one's own forces are hit by fires from the same side. This is often called "friendly fire", although the apocryphal "[[Murphy's Law]]s of Combat" mention:
Fratricide against one's own troops has a variety of causes. In a fast-moving battlefield, perhaps the most common cause is improper identification. It is worth noting that use of [[identification-friend-or-foe]] technology preceded common use of the terms "friendly fire" or "fratricide."  Positive identification is a major preventive step.
:*Friendly fire isn't.  
:*When the pin is pulled, Mr. [[Grenade]] is no longer our friend.


Formally, the United States [[Department of Defense]] defines "friendly fire" as {{quotation|In casualty reporting, a casualty circumstance applicable to persons killed in
Formally, the United States [[Department of Defense]] defines "friendly fire" as {{quotation|In casualty reporting, a casualty circumstance applicable to persons killed in
Line 14: Line 16:
   | date=12 July 2007
   | date=12 July 2007
   | url = http://www.dtic.mil/doctrine/jel/new_pubs/jp1_02.pdf
   | url = http://www.dtic.mil/doctrine/jel/new_pubs/jp1_02.pdf
   | accessdate = 2007-10-01}} </ref>}}
   | accessdate = 2007-10-01}} </ref>}} The term was popularized during Vietnam, in the book, by ''New York Times'' reporter C.D.B. Bryan, about an incident where families could not find out why their son died. <ref name=Bryan>{{citation
 
| title = Friendly Fire
| author =  C. D. B. Bryan
| publisher = Putnam | year =  1978
|ISBN =0525704388}}</ref>
Fratricide was one of the major causes of Coalition casualties during [[Operation Desert Storm]].''' [[Deconfliction]]''' is the part of mission planning that tries to ensure that all preplanned attacks know the position of friendly forces. One of the drivers of [[network-centric warfare]] is giving all units and personnel improved [[situational awareness]], such that a unit that moves to take advantage of a sudden enemy weakness is not incorrectly identified as an enemy force to be engaged.
Fratricide was one of the major causes of Coalition casualties during [[Operation Desert Storm]].''' [[Deconfliction]]''' is the part of mission planning that tries to ensure that all preplanned attacks know the position of friendly forces. One of the drivers of [[network-centric warfare]] is giving all units and personnel improved [[situational awareness]], such that a unit that moves to take advantage of a sudden enemy weakness is not incorrectly identified as an enemy force to be engaged.


In [[swarming (military)]] and other forms of operations in which multiple friendly directions strike in constantly changing time and space, real-time communications are key in avoiding fratricide. Even so, without computer assistance to recognize impending fratricide, people may be overloaded with information and make errors in recognizing their own side.
In [[swarming (military)]] and other forms of operations in which multiple friendly directions strike in constantly changing time and space, real-time communications are key in avoiding fratricide. Even so, without computer assistance to recognize impending fratricide, people may be overloaded with information and make errors in recognizing their own side.


==Prevention==
Situational awareness or a [[common operational picture]] is the ideal.  Such awareness goes beyond direct identification, to include common map coordinates and "safe zones". 
===Positive identification===
One program involves France, Germany, Great Britain and the United States. <ref name=Signal1998-05>{{citation
| title = Atlantic alliance efforts provide common combat identification
| journal = Signal
| date = May 1998
| author = Reed, Fred V
| url = http://findarticles.com/p/articles/mi_qa5438/is_199805/ai_n21426277/}}</ref>
==Inadvertent attacks on friendly personnel and units==
==Inadvertent attacks on friendly personnel and units==


Fluid situations and rapidly moving forces tend to increase the risk of friendly fire, as do communication problems with one's allies. For example, Canadian forces driving through Belgium and Holland during the Second World War were bombed by both American and British aircraft.
Fluid situations and rapidly moving forces tend to increase the risk of friendly fire, as do communication problems with one's allies. For example, Canadian forces driving through Belgium and Holland during the Second World War were bombed by both American and British aircraft.


Friendly fire can also result from bugs in weapons systems or deficiencies in training and documentation that lead to errors by field personnel. The worst friendly fire incident of the Afghan war took place at the [[Afghanistan War (2001-), major combat phase#Kandahar|Battle of Kandahar]], [http://www.gpsnavigatormagazine.com/gps-blamed-in-deadly-fire-event.html] when a US soldier used a GPS device to sight in on a Taliban position and had the battery die before he could transmit the target co-ordinates to the bombers. He replaced the battery and transmitted. Unfortunately, the device defaults back to its own position on power-up. The bombers duly came and hammered the co-ordinates they were given. They hit the headquarters of an Afghan force under future president [[Hamid Karzai]], accompanied by [[United States Army Special Forces#Operational Detachment A|U.S. Special Forces Operational Detachment ODA 574]], killing 30 and wounding many more.
Friendly fire can also result from bugs in weapons systems or deficiencies in training and documentation that lead to errors by field personnel. The worst friendly fire incident of the [[Afghanistan War (2001-)]] took place at the [[Afghanistan War (2001-), major combat phase#Kandahar|Battle of Kandahar]], [http://www.gpsnavigatormagazine.com/gps-blamed-in-deadly-fire-event.html] when a US soldier used a GPS device to sight in on a Taliban position and had the battery die before he could transmit the target co-ordinates to the bombers. He replaced the battery and transmitted. Unfortunately, the device defaults back to its own position on power-up. The bombers duly came and hammered the co-ordinates they were given. They hit the headquarters of an Afghan force under future president [[Hamid Karzai]], accompanied by [[United States Army Special Forces#Operational Detachment A|U.S. Special Forces Operational Detachment ODA 574]], killing 30 and wounding many more.


==Inadvertent interference with one's own weapons effects==
==Inadvertent interference with one's own weapons effects==

Revision as of 10:10, 27 May 2009

This article is developing and not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
This editable Main Article is under development and subject to a disclaimer.

Template:TOC-right Fratricide, in a military context, happens when members of one's own forces are hit by fires from the same side, or weapons interfere with one another such that their effect is neutralized. This is often called "friendly fire", although the apocryphal "Murphy's Laws of Combat" mention:

  • Friendly fire isn't.
  • When the pin is pulled, Mr. Grenade is no longer our friend.

Fratricide against one's own troops has a variety of causes. In a fast-moving battlefield, perhaps the most common cause is improper identification. It is worth noting that use of identification-friend-or-foe technology preceded common use of the terms "friendly fire" or "fratricide." Positive identification is a major preventive step.

Formally, the United States Department of Defense defines "friendly fire" as

In casualty reporting, a casualty circumstance applicable to persons killed in

action or wounded in action mistakenly or accidentally by friendly forces actively engaged with the enemy, who are directing fire at a hostile force or what is thought to be a hostile force.

— United States Joint Chiefs of Staff[1]

The term was popularized during Vietnam, in the book, by New York Times reporter C.D.B. Bryan, about an incident where families could not find out why their son died. [2]

Fratricide was one of the major causes of Coalition casualties during Operation Desert Storm. Deconfliction is the part of mission planning that tries to ensure that all preplanned attacks know the position of friendly forces. One of the drivers of network-centric warfare is giving all units and personnel improved situational awareness, such that a unit that moves to take advantage of a sudden enemy weakness is not incorrectly identified as an enemy force to be engaged.

In swarming (military) and other forms of operations in which multiple friendly directions strike in constantly changing time and space, real-time communications are key in avoiding fratricide. Even so, without computer assistance to recognize impending fratricide, people may be overloaded with information and make errors in recognizing their own side.

Prevention

Situational awareness or a common operational picture is the ideal. Such awareness goes beyond direct identification, to include common map coordinates and "safe zones".

Positive identification

One program involves France, Germany, Great Britain and the United States. [3]

Inadvertent attacks on friendly personnel and units

Fluid situations and rapidly moving forces tend to increase the risk of friendly fire, as do communication problems with one's allies. For example, Canadian forces driving through Belgium and Holland during the Second World War were bombed by both American and British aircraft.

Friendly fire can also result from bugs in weapons systems or deficiencies in training and documentation that lead to errors by field personnel. The worst friendly fire incident of the Afghanistan War (2001-) took place at the Battle of Kandahar, [1] when a US soldier used a GPS device to sight in on a Taliban position and had the battery die before he could transmit the target co-ordinates to the bombers. He replaced the battery and transmitted. Unfortunately, the device defaults back to its own position on power-up. The bombers duly came and hammered the co-ordinates they were given. They hit the headquarters of an Afghan force under future president Hamid Karzai, accompanied by U.S. Special Forces Operational Detachment ODA 574, killing 30 and wounding many more.

Inadvertent interference with one's own weapons effects

It can affect both people and materials; there are a number of nuclear warfare scenarios where the explosions from earlier bombs and warheads interfere with missiles and aircraft that must travel through turbulent air or intense radiation.

Deconfliction

Deconfliction is the process, during planning and operations, of detecting potential threats of fratricide and taking action to prevent it.

References