You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 3.85.0.0/16 has been blocked (disabled) by ‪ST47‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider. To prevent abuse, web hosts may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a web host's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and they should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 21:48, 22 February 2026.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
This IP address range has been globally blocked.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

This block affects editing on all Wikimedia wikis.
The IP address or range 3.85.0.0/16 has been globally blocked (disabled) by ‪Jon Kolbert‬ for the following reason(s):

Open proxy/Webhost: See the help page if you are affected

This block will expire on 05:35, 21 February 2029.

Even while globally blocked, you will usually still be able to edit pages on Meta-Wiki.

This block may be appealed at Global steward requests on Meta-Wiki.

Other useful links: Global blocks · Help:I have been blocked

You can view and copy the source of this page:

((Short description|American integrated naval weapons system developed by RCA and produced by Lockheed Martin))
((more citations needed|date=February 2019))

[[File:USS Lake Champlain (CG-57).JPG|thumb|((USS|Lake Champlain|CG-57)), a ((sclass|Ticonderoga|cruiser|0)) Aegis-equipped [[guided missile]] cruiser, launched in 1987. Beginning with ((USS|Bunker Hill|CG-52)), this version is equipped with the [[Mark 41 Vertical Launching System|Mark 41 VLS]], whereas earlier versions were equipped with the [[Mark 26 missile launcher|Mark-26 twin-arm missile launcher system]].]]

The '''Aegis Combat System''' is an American integrated naval weapons system, which uses computers and radars to track and guide weapons to destroy enemy targets. It was developed by the Missile and Surface Radar Division of [[RCA]], and it is now produced by [[Lockheed Martin Missiles and Fire Control|Lockheed Martin]].

Initially used by the [[United States Navy]], Aegis is now used also by the [[Japan Maritime Self-Defense Force]], [[Spanish Navy]], [[Royal Norwegian Navy]], [[Republic of Korea Navy]], and [[Royal Australian Navy]], and is planned for use by the [[Royal Canadian Navy]]. As of 2022, a total of 110 Aegis-equipped ships have been deployed, and 71 more are planned (see [[#Operators|operators]]).

[[#Ballistic Missile Defense|Aegis BMD]] (Ballistic Missile Defense) capabilities are being developed as part of the [[NATO missile defense system]].<ref name="The White House">((cite web|title=Fact Sheet on U.S. Missile Defense Policy - A "Phased, Adaptive Approach" for Missile Defense in Europe|url=https://obamawhitehouse.archives.gov/the_press_office/FACT-SHEET-US-Missile-Defense-Policy-A-Phased-Adaptive-Approach-for-Missile-Defense-in-Europe|work=Office of the Press Secretary|publisher=The White House|access-date=23 August 2012|date=17 September 2009))</ref>

==Etymology==
The word "[[Aegis]]" is a reference that dates back to Greek mythology, with connotations of a protective shield, as the Aegis was the [[buckler]] (shield) of Zeus, worn by Athena.

==Overview==
[[File:Aegis Combat System.png|thumb|400px|[[Diagram]] of the Aegis Combat System (Baseline 2-6)]]
The Aegis Combat System (ACS) implements advanced command and control (command and decision, or C&D, in Aegis parlance). It is composed of the Aegis Weapon System (AWS), the fast-reaction component of the Aegis Anti-Aircraft Warfare (AAW) capability, along with the [[Phalanx CIWS|Phalanx Close In Weapon System (CIWS)]], and the [[Mark 41 Vertical Launch System]].<ref>Originally, the first five ships of the United States' Aegis equipped [[Ticonderoga-class cruiser]]s were outfitted with Mark-26 twin-arm missile launchers; however, the ships with this system have been decommissioned and are no longer in service.</ref> Mk 41 VLS is available in different versions that vary in size and weight. There are three lengths: ((convert|209|in|m|abbr=on)) for the self-defense version, ((convert|266|in|m|abbr=on)) for the tactical version, and ((convert|303|in|m|abbr=on)) for the strike version. The empty weight for an 8-cell module is ((convert|26800|lb|kg|abbr=on)) for the self-defense version, ((convert|29800|lb|kg|abbr=on)) for the tactical version, and ((convert|32000|lb|kg|abbr=on)) for the strike version, thus incorporating [[anti-submarine warfare]] (ASW) systems and [[BGM-109 Tomahawk|Tomahawk]] Land Attack Cruise Missiles (TLAM). Shipboard torpedo and naval gunnery systems are also integrated.

AWS, the heart of Aegis, comprises the [[AN/SPY-1]] Radar, MK 99 Fire Control System, Weapon Control System (WCS), the Command and Decision Suite, and Standard Missile family of weapons; these include the basic [[RIM-66 Standard]], the [[RIM-156 Standard ER]] extended range missile, and the newer [[RIM-161 Standard Missile 3]] designed to counter [[ballistic missile]] threats. A further SM-2 based weapon, the [[RIM-174 Standard ERAM]] (Standard Missile 6) was deployed in 2013. Individual ships may not carry all variants. Weapons loads are adjusted to suit assigned mission profile. The Aegis Combat System is controlled by an advanced, automatic detect-and-track, multi-function three-dimensional [[passive electronically scanned array]] [[radar]], the AN/SPY-1. Known as "the Shield of the Fleet", the SPY high-powered (6 [[megawatt]]) radar is able to perform search, tracking, and missile guidance functions simultaneously with a track capacity of well over 100 targets at more than ((convert|100|nmi|km|-1)).<ref>((cite encyclopedia | title = Aegis Combat System | encyclopedia = The Warfighter Encyclopedia | publisher = Warfighter Response Center | date = October 8, 2003 | url = https://wrc.navair-rdte.navy.mil/warfighter_enc/weapons/shiplnch/aegis.htm | access-date = August 10, 2006 | archive-url = https://web.archive.org/web/20041105105518/https://wrc.navair-rdte.navy.mil/warfighter_enc/weapons/shiplnch/aegis.htm | archive-date = November 5, 2004 )).</ref> However, the AN/SPY-1 Radar is mounted lower than the [[AN/SPS-49]] radar system and so has a reduced [[radar horizon]].<ref>((cite web|url=http://www.fas.org/man/dod-101/sys/ship/weaps/an-spy-1.htm|title=AN/SPY-1 Radar|access-date=29 January 2016))</ref>

The Aegis system communicates with the Standard missiles through a radio frequency (RF) uplink using the AN/SPY-1 radar for [[mid-course update]] [[missile guidance]] during engagements, but still requires the [[AN/SPG-62]] [[fire-control radar]] for terminal guidance. This means that with proper scheduling of intercepts, a large number of targets can be engaged simultaneously.

The [[computer]]-based command-and-decision (C&D) element is the core of the Aegis Combat System and came from the [[Naval Tactical Data System]] (NTDS) threat evaluation and weapons assignment (TEWA) function.<ref>[https://ethw.org/First-Hand:Legacy_of_NTDS_-_Chapter_9_of_the_Story_of_the_Naval_Tactical_Data_System#Building_Aegis First-Hand:Legacy of NTDS - Chapter 9 of the Story of the Naval Tactical Data System] Section 4.3 Building Aegis. [[Engineering and Technology History Wiki]]</ref> This interface makes the ACS capable of simultaneous operation against almost all kinds of threats.

In December 2019, Lockheed Martin released a promotional video heralding the 50th anniversary of the Aegis combat system.<ref>((cite web |title=20191205_Lockheed_AEGIS_50th_Anniversary_3D_ME_FINAL |url=https://vimeo.com/377587148/64f428add4 |website=Vimeo.com |publisher=Green Buzz Agency |access-date=10 December 2019 |archive-url=https://web.archive.org/web/20191210152251/https://vimeo.com/377587148/64f428add4 |archive-date=10 December 2019 |date=5 December 2019 |url-status=live))</ref>

== Development ==
[[File:USS Norton Sound (AVM-1) underway at sea, circa in 1980.jpg|thumb|((USS|Norton Sound|AVM-1|6)) in 1980. The installation containing the fixed radar arrays of the AN/SPY-1A system can be seen mounted at the top of the forward superstructure]]
Aegis was initially developed by the Missile and Surface Radar Division of [[RCA]], which was later acquired by [[General Electric]]. The division responsible for the Aegis systems became Government Electronic Systems. This, and other [[GE Aerospace (1960s)|GE Aerospace]] businesses, were sold to [[Martin Marietta]] in 1992.<ref>Lenorovitz, Jeffrey. "GE Aerospace to merge into Martin Marietta" ''[[Aviation Week & Space Technology]]''. November 30, 1992. Accessed on July 19, 2007</ref> This became part of [[Lockheed Martin]] in 1995.

By the late 1950s, the U.S. Navy replaced guns with guided missiles on its ships. These were sufficient weapons but by the late 1960s, the U.S. Navy recognized that reaction time, firepower, and operational availability in all environments did not match the [[anti-ship missile]] threat.<ref>((Cite book |title=Hearings on H.R. 6566, ERDA Authorization Legislation (National Security Programs) for Fiscal Year 1978 |year=1977 |page=145))</ref> The new threat of Soviet anti-ship missiles exposed a weakness in contemporary naval radar. The requirements of both tracking and targeting these missiles was limited by the number of radars on each ship, which was typically 2–4. In 1958 the navy started the [[Typhon Combat System]], a prophetic program culminating in the futuristic but unreliable [[AN/SPG-59]] phased array radar, which was never made viable and was cancelled in 1963 to be replaced by the Advanced Surface Missile System (ASMS).<ref>((Cite web |url=http://www.harpoonhq.com/waypoint/articles/Article_044.pdf |title=Archived copy |access-date=2012-07-11 |archive-date=2017-11-18 |archive-url=https://web.archive.org/web/20171118103754/http://www.harpoonhq.com/waypoint/articles/Article_044.pdf ))</ref>

As a result, the U.S. Navy decided to develop a program to defend ships from anti-ship missile threats. An Advanced Surface Missile System (ASMS) was promulgated and an engineering development program was initiated in 1964 to meet the requirements.<ref>((cite web|url=http://usmilitary.about.com/od/navyweapons/a/aegis.htm|title=Aegis Cruisers|work=About.com Careers|access-date=29 January 2016|archive-date=4 March 2016|archive-url=https://web.archive.org/web/20160304193341/http://usmilitary.about.com/od/navyweapons/a/aegis.htm))</ref> ASMS was renamed "Aegis" in December 1969 after the [[aegis]], the [[shield]] of the [[Greek mythology|Greek god]] [[Zeus]]. The name was suggested by Captain L. J. Stecher, a former [[Tartar Guided Missile Fire Control System|Tartar Weapon System]] manager, after an internal U.S. Navy contest to name the ASMS program was initiated. Captain Stecher also submitted a possible acronym of Advanced Electronic Guided Interceptor System although this definition was never used.<ref>Lockheed Martin. "Aegis Heritage". Presentation. November 20, 2002.</ref> The main manufacturer of the Aegis Combat System, Lockheed Martin, makes no mention of the name Aegis being an acronym, nor does the [[United States Navy|U.S. Navy]].

In 1970, then-Captain [[Wayne E. Meyer|Wayne Meyer]] was named Manager Aegis Weapons System. Under his leadership the first systems were successfully deployed on various U.S. Navy vessels.

The first Engineering Development Model (EDM-1) was installed in a test ship, ((USS|Norton Sound|AVM-1|6)), in 1973.<ref>((cite web|url=http://www.navy.mil/navydata/fact_display.asp?cid=2100&tid=200&ct=2|title=The US Navy -- Fact File: Aegis Weapon System|author=Dan Petty|access-date=29 January 2016|archive-date=4 February 2016|archive-url=https://web.archive.org/web/20160204184720/http://www.navy.mil/navydata/fact_display.asp?cid=2100&tid=200&ct=2))</ref> During this time frame, the Navy envisioned installing the Aegis Combat System on both a nuclear-powered "[[strike cruiser]]" (or CSGN) and a conventionally-powered destroyer (originally designated DDG 47). The CSGN was to be a new, 17,200 ton cruiser design based on the earlier ((sclass|California|cruiser|5)) and ((sclass|Virginia|cruiser|0)) cruisers. The Aegis destroyer design would be based on the gas turbine powered ((sclass|Spruance|destroyer|4)). When the CSGN was cancelled, the Navy proposed a modified ''Virginia''-class design (CGN 42) with a new superstructure designed for the Aegis Combat System and with a displacement of 12,100 tons. As compared to the CSGN, this design was not as survivable and had reduced command and control facilities for an embarked flag officer. Ultimately this design was also cancelled during the Carter Administration due to its increased cost compared to the non-nuclear DDG 47. With the cancellation of the CGN 42, the DDG 47 Aegis destroyer was redesignated as CG 47, a guided missile cruiser.

The first cruiser of this class was ((USS|Ticonderoga|CG-47|6)), which used two twin-armed Mark-26 missile launchers, fore and aft. The commissioning of the sixth ship of the class, ((USS|Bunker Hill|CG-52|6)) opened a new era in surface warfare as the first Aegis ship outfitted with the [[Martin Marietta]] Mark-41 [[Vertical Launching System]] (VLS), allowing a wider missile selection, more firepower, and survivability. The improved AN/SPY-1B radar went to sea in ((USS|Princeton|CG-59|6)), ushering in another advance in Aegis capabilities. ((USS|Chosin|CG-65|6)) introduced the [[AN/UYK-43]]/[[AN/UYK-44|44]] computers, which provide increased processing capabilities.

During 1980, the ((sclass|Arleigh Burke|destroyer|2)) was designed using an improved sea-keeping hull form, reduced [[infrared]] and radar cross-sections, and upgrades to the Aegis Combat System. The first ship of the class, ((USS|Arleigh Burke|DDG-51)), was commissioned during 1991.

Flight II of the ''Arleigh Burke'' class, introduced in 1992, incorporated improvements to the SPY-1 radar, and to the Standard missile, active electronic countermeasures, and communications. Flight IIA, introduced in 2000, added a [[helicopter]] hangar with one anti-submarine helicopter and one armed [[attack helicopter]]. The Aegis program has also projected reducing the cost of each Flight IIA ship by at least $30 million.

Recent Aegis Combat System ships come with [[active electronically scanned array]] radars which use solid-state [[gallium nitride]] emitters. These include [[Canadian Surface Combatant|Canadian Surface Combatant (CSC)]] and Spanish [[F110-class frigate]]s, which use the [[AN/SPY-7]] radar from Lockheed-Martin, and [[Constellation-class frigate]]s which use [[AN/SPY-6]] radar from [[Raytheon]]. AN/SPY-6 radar will also be installed in Flight III and Flight IIA ''Arleigh Burke'' class destroyers, giving them Ballistic Missile Defense capability currently deployed on Flight I and Flight II ships.

== Ballistic Missile Defense ==
((anchor|Aegis Open Architecture))
The [[Aegis Ballistic Missile Defense System]] (BMD) program by the U.S. [[Missile Defense Agency]] enables the Aegis system to act in a sea-based [[ballistic missile defense]] function, to counter short- and medium-range [[ballistic missile]]s of the variety typically employed by a number of potential opponent states. The program is part of the [[United States national missile defense]] strategy and [[NATO missile defence system|NATO European missile defense system]].<ref name="The White House"/>

BMD capabilities allow vessels equipped with [[Mk 41 Vertical Launching System]] (VLS) to intercept ballistic missiles in post-boost phase and prior to reentry, using the [[RIM-161 Standard Missile 3]] (SM-3) mid-course interceptors<ref>((Cite web |title=Standard Missile-3 (SM-3) |url=https://missilethreat.csis.org/defsys/sm-3/ |access-date=2022-08-30 |website=Missile Threat |language=en-US))</ref> and the [[RIM-156 SM-2ER Block IV|RIM-156 Standard Missile 2 Extended Range Block IV]] (SM-2ER Block IV)<ref>((Cite web |title=Standard Missile-2 Block IV |url=https://missilethreat.csis.org/defsys/standard-missile-2-block-iv/ |access-date=2022-08-31 |website=Missile Threat |language=en-US))</ref> terminal-phase interceptors.<ref>((Cite web |title=Aegis Ballistic Missile Defense |url=https://missilethreat.csis.org/system/aegis/ |access-date=2022-11-30 |website=Missile Threat |language=en-US))</ref> The SM-2ER Block IV can engage the ballistic missiles within the atmosphere (i.e. endoatmospheric intercept) in the terminal phase of a missile's trajectory with a blast fragmentation warhead. The Standard Missile 3 is a development of the SM2-ER Block IV, capable of exo-atmospheric intercept (i.e. above the atmosphere) during the midcourse phase; its kinetic warhead (KW) is designed to destroy a ballistic missile's warhead by colliding with it. [[RIM-174 Standard ERAM]] (Standard Missile 6) extended range active missile is a further development of the SM-2ER Block IV, which adds a booster and an [[active radar homing]] seeker.<ref name="naval-technology.com">[http://www.naval-technology.com/projects/aegis-ballistic-missile-defence-bmd-us/ Aegis Ballistic Missile Defence (BMD) System, United States of America]</ref> SM-6 can be used for either air defense or ballistic missile defense, providing extended range and increased firepower; it is not intended to replace the SM-2 series of missiles.<ref>Sydney J. Freedberg, Jr., [http://breakingdefense.com/2014/08/non-standard-navy-sm-6-kills-cruise-missiles-deep-inland/ "Non-Standard: Navy SM-6 Kills Cruise Missiles Deep Inland"] – Breakingdefense.com, 19 August 2014</ref> The SM-6 Block IB includes a larger 21-inch rocket motor that sits on top of the 21-inch booster.<ref name="news.usni.org">((Cite web|url=https://news.usni.org/2018/12/18/39724|title = Report to Congress on Aegis Ballistic Missile Defense|date = December 18, 2018))</ref>

To enable Ballistic Missile Defense capabilities, [[signal processing]] for the SPY-1 radar was upgraded using [[commercial off-the-shelf]] components and [[open architecture]] standards.<ref>((cite web|url=http://www.lockheedmartin.com/us/news/press-releases/2010/september/091610_aegis_bmd.html|title=Lockheed Martin Successfully Completes Formal Testing of Second-Generation Aegis Ballistic Missile Defense Capability|website=www.lockheedmartin.com|date=2010-09-16|url-status=usurped|archive-url=https://web.archive.org/web/20130127000428/http://www.lockheedmartin.com/us/news/press-releases/2010/september/091610_aegis_bmd.html|archive-date=2013-01-27))</ref> The Multi-Mission Signal Processor (MMSP) provides Anti-Air Warfare (AAW) and Ballistic Missile Defense (BMD) capability for the first 28 ships (DDGs 51–78) of the U.S. Navy's ''Arleigh Burke''-class destroyers. This capability is also incorporated in ((USS|John Finn|DDG-113)) and following new construction, as well as Aegis Ashore. MMSP modifies transmitters of the [[SPY-1|SPY-1D]] radar to enable dual-beam operation for reduced frame times and better reaction time, and provides stability for all [[waveform]]s, allowing the radar system to detect, track, and support engagements of a broader range of threats. MMSP improves performance in [[littoral]], ducted [[Clutter (radar)|clutter]], [[electronic attack]] (EA), and [[chaff (countermeasure)|chaff]] environments and provides greater commonality in computer programs and equipment.<ref>FY 2013 Presidential Budget (PB): Navy, February 2012. Exhibit R-2, Research, Development, Test, and Evaluation (RDT&E) Budget Item Justification: Program Element (PE) 0604501N: Advanced Above Water Sensors, Page 2 of 37. [https://web.archive.org/web/20140201211211/http://www.dtic.mil/descriptivesum/Y2013/Navy/stamped/0604501N_5_PB_2013.pdf]. Accessed on 04 April 2013</ref><ref>((cite web|url=http://www.lockheedmartin.com/us/news/press-releases/2010/april/aegis-live-tracking-041210.html|title=pr_mission_aegis-live-tracking-041210 · Lockheed Martin|website=www.lockheedmartin.com))</ref>

As of April 2022, the U.S. and Japan are the only countries to purchase or deploy the Aegis BMD on their military ships.<ref name=RL33745/><ref>((cite web|url=http://www.mda.mil/system/aegis_bmd.html |title=Aegis Ballistic Missile Defense |author=<!--Staff writer(s); no by-line.--> |date=8 January 2014 |website=Missile Defense Agency |publisher=US Dept. of Defense |access-date=30 January 2014 |archive-url=https://web.archive.org/web/20140125154343/http://www.mda.mil/system/aegis_bmd.html |archive-date=25 January 2014 ))</ref><ref>((cite web|url=http://www.mda.mil/system/aegis_foreign_mil_sales.html |title=Aegis Ballistic Missile Defense - Foreign Military Sales |author=<!--Staff writer(s); no by-line.--> |date=2 January 2014 |website=Missile Defense Agency |publisher=US Dept. of Defense |access-date=30 January 2014 |archive-url=https://web.archive.org/web/20131013190230/http://www.mda.mil/system/aegis_foreign_mil_sales.html |archive-date=13 October 2013 ))</ref>

Flight III of ''Arleigh Burke'' class destroyers starting with ((USS|Jack H. Lucas|DDG-125)) are equipped with [[AN/SPY-6]] AESA radar from [[Raytheon]], which is 30 times more sensitive and thus can handle 30 times more targets comparing to the SPY-1D radar, providing increased air and missile defense capabilities.<ref name= 30xCapable /><ref name="spy6family">((cite web |url=https://www.raytheonmissilesanddefense.com/capabilities/products/spy6-radars |title=U.S. Navy's SPY-6 Family of Radars |date=12 July 2020 |website=www.raytheonmissilesanddefense.com |publisher=Raytheon |access-date=12 July 2020))</ref> Flight IIA ships will also be upgraded to SPY-6 in the future, giving them Aegis BMD capabilities.<ref name="spy6family" /><ref name= 30xCapable >Justin Katz [https://breakingdefense.com/2022/01/raytheon-to-start-back-fitting-destroyers-with-spy-6-radar/ Raytheon to start backfitting destroyers with SPY-6 radar]. Breaking Defense (11 Jan 2022)</ref>

[[Aegis Ashore]] is a land-based version of Aegis BMD which includes the AN/SPY-1 radar and command systems, and Mk 41 VLS equipped SM-3 and SM-6 missiles. Test installation exists at the [[Pacific Missile Range Facility]] in [[Hawaii]]. A [[Deveselu Military Base|site]] in [[Deveselu]], [[Romania]] is operational since 2016, and a site near [[Redzikowo]], [[Poland]] will become operational in 2022. Japan intended to deploy two systems with an [[AN/SPY-7]] AESA radar by 2021, but cancelled these plans in 2020. Possible deployments of Aegis Ashore include U.S. naval base at [[Guam]].<ref name=RL33745>((Cite web|url=https://crsreports.congress.gov/product/details?prodcode=RL33745|title=Navy Aegis Ballistic Missile Defense (BMD) Program: Background and Issues for Congress (RL33745)|publisher=Congressional Research Service|date=2022-04-01|access-date=2022-05-08|archive-url=https://web.archive.org/web/20220401000000/https://crsreports.congress.gov/product/details?prodcode=RL33745|archive-date=2022-04-01|url-status=live)) [https://sgp.fas.org/crs/weapons/RL33745.pdf Alt URL]</ref>

U.S. Army [[United States Army Futures Command#Integrated Air and Missile Defense Battle Command System|Integrated Air and Missile Defense Battle Command System]] (IBCS) program aims to integrate Aegis BMD and its [[AN/SPY-1]] and [[AN/SPY-6]] radars with [[MIM-104 Patriot]] ([[AN/MPQ-65]]A and GhostEye), [[NASAMS]] (GhostEye MR), [[AN/TPY-2]] ([[THAAD]] and [[Ground-Based Midcourse Defense|GMD]]), and [[F-35 Lightning II]] ([[AN/APG-81]]) radars to form a [[plug and fight]] network of land, sea, and air-based sensors to help detect and track ballistic missile threats and select Patriot and THAAD surface-to-air launchers that are best positioned for a successful intercept.

===NATO European Phased Adaptive Approach===
((main|Destroyer Squadron 60|European Phased Adaptive Approach))
On 5 October 2011, [[U.S. Secretary of Defense]] [[Leon Panetta]] announced that the United States Navy will station four [[Aegis Ballistic Missile Defense System]] warships at [[Naval Station Rota]], Spain, to strengthen its presence in the Mediterranean Sea and bolster the ballistic missile defense (BMD) of NATO as part of the [[European Phased Adaptive Approach]] (EPAA) missile defense program. On 16 February 2012, it was reported that the ((Sclass|Arleigh Burke|destroyer))s ''Donald Cook'' and ''Ross'' would be relocated to Rota during Fiscal Year 2014, followed by ''Porter'' and ''Carney'' in fiscal year 2015.<ref name="NNS120216-15">((Cite web |title= Navy Names Forward Deployed Ships to Rota, Spain |url= http://www.navy.mil/submit/display.asp?story_id=65393 |work= NNS120216-15 |publisher= [[U.S. Department of Defense]] |date= 16 February 2012 |access-date= 11 August 2013 |archive-date= 12 October 2014 |archive-url= https://web.archive.org/web/20141012100428/http://www.navy.mil/submit/display.asp?story_id=65393 ))</ref> On 9 May 2013, Commander [[Destroyer Squadron 60]] was formally designated to perform [[U.S. Navy type commands|type-command]] administrative oversight for the four BMD-capable destroyers based at Rota, Spain.<ref name=13U102244>((Cite web |title= ESTABLISHMENT OF COMMANDER, DESTROYER SQUADRON SIX ZERO |url= http://doni.daps.dla.mil/Directives/05000%20General%20Management%20Security%20and%20Safety%20Services/05-400%20Organization%20and%20Functional%20Support%20Services/5400.2244.pdf |work= OPNAVNOTE 5400 Ser DNS-33/13U102244 |publisher= [[United States Department of the Navy]] |date= 9 May 2013 |access-date= 11 August 2013 |archive-date= 14 October 2013 |archive-url= https://web.archive.org/web/20131014080705/http://doni.daps.dla.mil/Directives/05000%20General%20Management%20Security%20and%20Safety%20Services/05-400%20Organization%20and%20Functional%20Support%20Services/5400.2244.pdf ))</ref>

===JMSDF Aegis Afloat===
((Main|Aegis system equipped vessels (ASEV)))
[[File:Conceptual image of JMSDF ballistic missile defense ship, 23 December 2022.png|thumb|right|Artist's impression of future BMD ship (JSDF Photo)]]
[[File:JS Chokai（DDG-176）, USS CHANCELLORSVILLE（CG-62）and ROKS SEJONG DAEWANG（DDG-991）during Japan-U.S.-ROK Trilateral Exercise in the Sea of Japan.jpg|thumb|right|BMD maneuvers (October 6, 2022)]]
[[File:JS Haguro（DDG-180）launching SM-3 Block IB. Hawaii, Nov 19, 2022.jpg|thumb|right|JS ''Haguro''（DDG-180）launching SM-3 Block IB missile (November 19, 2022)]]
The [[Japanese Maritime Self Defense Force]] (JMSDF) currently operates 4 ((sclass|Kongō|destroyer|4)), 2 ((sclass|Atago|destroyer|4)), and 2 ((sclass|Maya|destroyer|4)) guided-missile destroyers as part of its "Aegis Afloat" program (''See table below'').

Additionally, on 31 August 2022, The [[Japan Ministry of Defense]] announced that JMSDF will operate two "[[Aegis system equipped vessels (ASV)|Aegis system equipped ships]]" (イージス・システム搭載艦 in Japanese) (''pictured'' to replace the earlier plan of Aegis Ashore installations, commissioning one by the end of fiscal year 2027, and the other by the end of FY2028. The budget for design and other related expenses are to be submitted in the form of "item requests", without specific amounts, and the initial procurement of the lead items are expected to clear legislation by FY2023. Construction is to begin in the following year of FY2024. At 20,000 tons each, both vessels will be the largest [[surface combatant]] warships operated by the JMSDF, and according to ''[[Popular Mechanics]]'', they will "arguably [be] the largest deployable surface warships in the world.".<ref name="Lia">((Cite web |date=1 September 2022 |author=Lia Wong |title=Japanese Defense Budget Expansion Includes Two 20,000 Ton Cruisers |url=https://www.overtdefense.com/2022/09/01/japanese-defense-budget-expansion-includes-two-20000-ton-cruisers/ |website=Overt Defense |access-date=7 September 2022))</ref><ref name="Mahadzir">((Cite web |date=6 September 2022 |author=Dzirhan Mahadzir |title=Japan to Build Two 20,000-ton Missile Defense Warships, Indian Carrier Commissions |url=https://news.usni.org/2022/09/06/japan-to-build-two-massive-20000-ton-missile-defense-warships-indian-carrier-commissions#more-97081/ |website=[[United States Naval Institute|USNI News Blog]] |access-date=7 September 2022))</ref><ref name=Yoshihiro>((Cite web |date=1 September 2022 |author=Yoshihiro Inaba |title=Japan's New "Aegis Equipped Ships": What We Know So Fars |url=https://www.overtdefense.com/2022/09/01/japanese-defense-budget-expansion-includes-two-20000-ton-cruisers/ |website=NavalNews |access-date=7 September 2022))</ref><ref name=Mizokami>((cite web |url=https://www.popularmechanics.com/military/navy-ships/a41123804/japan-to-build-20-000-ton-warships/ |author=Kyle Mizokami |title=Japan Defense Ministry plans new Aegis destroyers in place of Aegis Ashore |date=12 September 2022 |access-date=13 September 2022 |archive-url=https://web.archive.org/web/20220912200955/https://www.popularmechanics.com/military/navy-ships/a41123804/japan-to-build-20-000-ton-warships/ |website=[[Popular Mechanics]] |archive-date=12 September 2022 |url-status=bot: unknown ))</ref>

On 6 October 2022, five warships from the United States, Japan, and South Korea held a multilateral ballistic missile defense exercise in the [[Sea of Japan]] (''pictured'') as part of the military response to [[2021–2022 North Korean missile tests|ongoing North Korean intermediate-range ballistic missile tests over the Japanese home islands]].<ref>((cite web |url=https://news.usni.org/2022/10/06/warships-from-u-s-japan-south-korea-ballistic-missile-defense-drills-after-north-korean-missile-shots#more-97916 |title=UPDATED: Warships from U.S., Japan, South Korea Ballistic Missile Defense Drills After North Korean Missile Shots |last=LaGrone |first=Sam |date=October 6, 2022 |website=News Blog |publisher=[[United States Naval Institute]] |access-date=October 11, 2022 |quote=))</ref><ref>((cite web |url=https://www.navalnews.com/naval-news/2022/10/us-navy-jmsdf-and-rok-navy-conduct-bmd-exercise/ |title= US Navy, JMSDF And ROK Navy Conduct BMD Exercise |last=|first=|date=October 6, 2022 |website=NavalNews.com |publisher= |access-date=October 25, 2022 |quote=))</ref>

On 16 November 2022, the guided-missile destroyer ((JS|Maya|DDG-179|2)) fired an SM-3 Block IIA missile, successfully intercepting the target outside the atmosphere in the first launch of the missile from a Japanese warship. On 18 November 2022, the ((JS|Haguro|DDG-180|2)) likewise fired an SM-3 Block IB missile with a successful hit outside the atmosphere (''pictured''). Both test firings were conducted at the U.S. [[Pacific Missile Range Facility]] on [[Kauai Island]], Hawaii, in cooperation with the U.S. Navy and [[U.S. Missile Defense Agency]]. This was the first time the two ships conducted SM-3 firings in the same time period, and the tests validated the ballistic missile defense capabilities of Japan's newest ((sclass|Maya|destroyer|1))s.<ref>((cite web |url=https://news.usni.org/2022/11/21/two-japanese-destroyers-score-in-ballistic-missile-defense-test-off-hawaii#more-99073 |title=Two Japanese Destroyers Score in Ballistic Missile Defense Test off Hawaii |last=Mahadzir |first=Dzirhan |date=November 21, 2022 |website=News Blog |publisher=[[United States Naval Institute]] |access-date=November 22, 2022 |quote=))</ref>

On 23 December 2022, the Japanese Ministry of Defense's 2023 budget and program guidance illustrated examples of operation (運用の一例) for the Aegis-equipped naval forces of the Japanese Maritime Self Defense Force (MSDF).  The two ASEV warship would be exclusively tasked for dedicated ballistic missile defense (BDM) missions (BMD等) and operate off the Korean peninsula in the [[Sea of Japan]], allowing the other Aegis guided-missile destroyers to meet other contingencies (侵攻阻止) while operating independently to maintain the [[sea lines of communication]] (SLOC) open in the [[East China Sea]] southwest of the Japanese home islands.<ref name="LaGrone2">((cite web |url=https://news.usni.org/2022/12/27/japanese-mod-releases-details-on-ballistic-missile-defense-ships#more-99887 |title=Japanese MoD Releases New Details on Ballistic Missile Defense Ships |last=LaGrone |first=Sam |date=December 27, 2022 |website=News Blog |publisher=[[United States Naval Institute]] |access-date=January 3, 2023 |quote=))</ref><ref name="NavalNewsStaff1">((cite web |url=https://www.navalnews.com/naval-news/2022/12/japanese-mod-releases-further-details-of-asev-bmd-destroyers/ |title=Japanese MoD Releases Further Details About Its Future BMD Destroyers |last= |first= |date=December 25, 2022 |website=Naval News |publisher= |access-date=January 3, 2023 |quote=))</ref><ref name="Helfrich">((cite web |url=https://www.thedrive.com/the-war-zone/first-rendering-of-japans-ballistic-missile-defense-ship-concept-released |title=First Rendering Of Japan's Ballistic Missile Defense Ship Concept Released |last=Emma |first=Helfrich |date=December 29, 2022 |website=The Drive |publisher= |access-date=January 3, 2023 |quote=))</ref><ref name="MOD12232022">((cite web |url=https://www.mod.go.jp/j/yosan/yosan_gaiyo/2023/yosan_20221223.pdf |title=Defense Programs and Budget of Japan FY Reiwa 5 (2023) Budget Overview |author=<!--Not stated--> |date= December 23, 2022 |website=Budget overview |publisher=[[Japanese Ministry of Defense]] |page=15 |access-date=2023-01-09 |quote=Japanese))</ref>

On 22 February 2023, five warships from the United States, Japan, and South Korea held a multilateral ballistic missile defense exercise in the [[Sea of Japan]] in response to the launch of a North Korean [[Hwasong-15]] ballistic missile on 18 February 2023, landing in [[Exclusive economic zone of Japan|Japan's exclusive economic zone (EEZ)]] in the Sea of Japan, in an area 125 miles west of the island of [[Oshima (Hokkaido)|Ōshima]], which lies ((convert|30|mi|km)) west of the main island of [[Hokkaido]]. Two additional IBCBMs were subsequently launched on 20 February 2023, with both landing in the Sea of Japan off the east coast of the [[Korean Peninsula]].<ref>((cite web |url=https://news.usni.org/2023/02/22/u-s-japan-south-korea-hold-ballistic-missile-defense-drills-after-north-korean-launches#more-101115 |title=U.S., Japan, South Korea Hold Ballistic Missile Defense Drills after North Korean Launches |last=Mahadzir |first=Dzirhan |date=February 22, 2023 |website=News Blog |publisher=[[United States Naval Institute]] |access-date=February 22, 2023 |quote=))</ref>  On 19 December 2023, United States, Japan, and South Korea announced the activation of a real-time North Korea missile warning system as well as jointly established a multi-year trilateral exercise plan in response to North Korea's continued ballistic missile launches.<ref>((cite web |url=https://news.usni.org/2023/12/19/u-s-japan-south-korea-establish-north-korean-missile-warning-system-trilateral-exercises |title=U.S., Japan, South Korea Establish North Korean Missile |last=Mahadzir |first=Dzirhan |date=December 19, 2023 |website=News Blog |publisher=[[United States Naval Institute]] |access-date=December 22, 2023 ))</ref><ref>((cite web |url=https://www.mod.go.jp/en/article/2023/12/c74496d9056f871004eb2983fb03d626fcc2ff94.html |title=Japan-United States-Republic of Korea Trilateral Ministerial Joint Press Statement |last= |first= |date=December 19, 2023 |website=Press Release |publisher=[[Ministry of Defense (Japan)|Japanese Ministry of Defense]] |access-date=December 24, 2023 ))</ref>

;List of JMSSDF Aegis Afloat ships
{| class="wikitable"
! Name !!style="line-height:1.2em;"| Hull Pennant No. !! Builder/Shipyard !! Aegis Radar !! [[Anti-Ballistic Missile]] !! Vertical Launchers !! Commissioned !! Home port !! Flotilla !! Squadron !! Status
|-
|colspan=11 style="background: #80D8FF;text-align:center;"|((sclass|Maya|destroyer|4)) 
|-
| ((JS|Maya|DDG-179|6))
| DDG-179
| [[Japan Marine United|JMU, Yokohama]]
| [[AN/SPY-1|AN/SPY-1D(V)]]
| [[RIM-161 Standard|SM-3 Standard missile]]
| [[Mark 41 Vertical Launching System|Mark 41]]: 96 cells (total)
| 19 March 2020 
| [[Yokosuka]]
| Escort Flotilla 1 
| Escort Squadron 1
| Active
|-
| ((JS|Haguro|DDG-180|6))
| DDG-180
| [[Japan Marine United|JMU, Yokohama]]
| [[AN/SPY-1|AN/SPY-1D(V)]]
| [[RIM-161 Standard|SM-3 Standard missile]]
| [[Mark 41 Vertical Launching System|Mark 41]]: 96 cells (total)
| 19 March 2021
| [[Sasebo, Nagasaki|Sasebo]]
| Escort Flotilla 4 
| Escort Squadron 8
| Active
|-
|colspan=11 style="background: #80D8FF;text-align:center;"|((sclass|Atago|destroyer|4))
|-
| ((JDS|Atago|DDG-177|6)) 
| DDG-177
| [[Japan Marine United|JMU, Yokohama]]
| [[AN/SPY-1|AN/SPY-1D(V)]]
| [[RIM-161 Standard|SM-3 Standard missile]]
| [[Mark 41 Vertical Launching System|Mark 41]]: 96 cells (total)
| 15 March 2007
| [[Maizuru, Kyoto|Maizuru]]
| Escort Flotilla 3
| Escort Squadron 3
| Active
|-
| ((JDS|Ashigara|DDG-178|6)) 
| DDG-178
| [[Japan Marine United|JMU, Yokohama]]
| [[AN/SPY-1|AN/SPY-1D(V)]]
| [[RIM-161 Standard|SM-3 Standard missile]]
| [[Mark 41 Vertical Launching System|Mark 41]]: 96 cells (total)
| 13 March 2008
| [[Sasebo, Nagasaki|Sasebo]]
| Escort Flotilla 2
| Escort Squadron 2
| Active
|-
|colspan=11 style="background: #80D8FF;text-align:center;"|((sclass|Kongō|destroyer|4))
|-
| ((JDS|Kongō|DDG-173|2))
| DDG-173
| [[Mitsubishi Heavy Industries]]
| [[AN/SPY-1|AN/SPY-1D]] [[Passive electronically scanned array|PESA]]
| [[RIM-161 Standard|SM-3 Standard missile]]
| [[Mark 41 Vertical Launching System|Mark 41]]: 90 cells (total)
| 25 March 1993
| [[Sasebo, Nagasaki|Sasebo]]
| Escort Flotilla 1
| Escort Squadron 5:
| Active
|-
| ((JDS|Kirishima|DDG-174|2)) 
| DDG-174
| [[Mitsubishi Heavy Industries]]
| [[AN/SPY-1|AN/SPY-1D]] [[Passive electronically scanned array|PESA]]
| [[RIM-161 Standard|SM-3 Standard missile]]
| [[Mark 41 Vertical Launching System|Mark 41]]: 90 cells (total) 
| 16 March 1995 
| [[Yokosuka, Kanagawa|Yokosuka]]
| Escort Flotilla 2
| Escort Squadron 6
| Active
|-
| ((JDS|Myōkō|DDG-175|2)) 
| DDG-175
| [[Mitsubishi Heavy Industries]]
| [[AN/SPY-1|AN/SPY-1D]] [[Passive electronically scanned array|PESA]]
| [[RIM-161 Standard|SM-3 Standard missile]]
| [[Mark 41 Vertical Launching System|Mark 41]]: 90 cells (total)
| 14 March 1996
| [[Maizuru, Kyoto|Maizuru]]
| Escort Flotilla 3
| Escort Squadron 3
| Active
|-
| ((JDS|Chōkai|DDG-176|2))
| DDG-176
| [[IHI Corporation]]
| [[AN/SPY-1|AN/SPY-1D]] [[Passive electronically scanned array|PESA]]
| [[RIM-161 Standard|SM-3 Standard missile]]
| [[Mark 41 Vertical Launching System|Mark 41]]: 90 cells (total)
| 20 March 1998
| [[Sasebo, Nagasaki|Sasebo]]
| Escort Flotilla 4
| Escort Squadron 8
| Active
|-
|}

==System problems==
In 2010, it was reported that Aegis radar systems on board some individual warships were not being maintained properly. A Navy panel headed by retired Vice Adm. Phillip Balisle issued the "Balisle report," which asserted that over-emphasis on saving money, including cuts in crews and streamlined training and maintenance, led to a drastic decline in readiness, and left Aegis Combat Systems in low state of readiness.<ref>[http://www.navytimes.com/news/2010/07/navy_aegis_070510w/ Study says Aegis radar systems on the decline], by Philip Ewing, Navy Times, Wednesday July 7, 2010.</ref>

===Iran Air Flight 655===
((Main|Iran Air Flight 655))

[[File:CG-47 CIC.png|thumb|upright|Layout of the [[Combat Information Center]] of early Aegis cruisers]]

The Aegis system was involved in a disaster in which ((USS|Vincennes|CG-49|6)) mistakenly shot down [[Iran Air Flight 655]] in 1988 resulting in 290 civilian deaths.

A formal military investigation by the United States Navy concluded that the Aegis system was completely operational and well maintained. The investigation found that if the [[commanding officer]] had relied on the complete tactical data displayed by the Aegis system, the engagement might never have occurred. Additionally, psychological effects of the crew subconsciously manipulating the data to accord with a predefined scenario greatly contributed to the false identification. The investigation found that the Aegis Combat System did not contribute to the incident and that the system's recorded target data contributed to the investigation of the incident. The discrepancies between the Aegis data report and what the ship's personnel reported to the commanding officer are as follows:<ref>((Cite web |last=Fogarty |first=William M. |date=July 28, 1988 |title=Formal Investigation into the Circumstances Surrounding the Downing of Iran Air Flight 655 on 3 July 1988 |url=http://www.dod.mil/pubs/foi/International_security_affairs/other/172.pdf |archive-url=https://web.archive.org/web/20060506205901/http://homepage.ntlworld.com/jksonc/docs/ir655-dod-report.html |archive-date=6 May 2006 |access-date=March 31, 2006 |id=93-FOI-0184))</ref>

{| class="wikitable"
|-
! Aegis Data Report
! Personnel Report to CO
|-
| Iran Air Flight 655 continuously ascended in duration of flight
| Iran Air Flight 655, after attaining ((convert|9000|to|12000|ft|m|abbr=on)), reportedly descended on an attack vector on USS ''Vincennes''
|-
| Iran Air Flight 655 continuously squawked [[Transponder (aviation)#Transponder modes|Mode III]] [[identification, friend or foe]] (IFF) in duration of flight
| Iran Air Flight 655 reportedly squawked Iranian [[F-14 Tomcat]] on Mode II IFF for a moment; personnel proceeded to re-label the target from "Unknown Assumed Enemy" to "F-14"
|-
| Iran Air Flight 655 held consistent climb speed in duration of flight
| Iran Air Flight 655 was reported to increase in speed to an attack vector similar to an F-14 Tomcat
|-
|}

Other analyses found that ineffective user interface design caused poor integration with the crisis management human processes it was intended to facilitate. The Aegis System software shuffles target tracking numbers as it gathers additional data. When the captain asked for a status of the original target identifier TN4474, the Aegis system had recycled that identifier to a different target which was descending, indicating possible attack posture.<ref>((cite journal |last1=Fisher |first1=Craig |last2=Kingma |first2=Bruce |date=2001 |title=Criticality of data quality as exemplified in two disasters |journal=Information and Management |volume=39 |issue=2 |pages=109–116 |doi=10.1016/S0378-7206(01)00083-0 |citeseerx=10.1.1.15.1047 |s2cid=13015473 ))</ref> An article by [[David Pogue]] in ''[[Scientific American]]'' rated it as one of the five "worst digital user-interface debacles of all time."<ref>((cite magazine |last=Pogue |first=David |date=1 April 2016 |title=5 of the Worst User-Interface Disasters |url=https://www.scientificamerican.com/article/pogue-5-of-the-worst-user-interface-disasters/ |magazine=Scientific American |access-date=3 July 2019 |archive-url=https://web.archive.org/web/20160922042401/http://www.scientificamerican.com/article/pogue-5-of-the-worst-user-interface-disasters/ |archive-date=22 September 2016 |url-status=live ))</ref>

==Operators==
{| class="wikitable" style="margin-left: 10px"
|-
! Country
! Ship class
!Active
! Planned 
! Retired
|-
| rowspan="2" |((navy|Australia))
| ((sclass|Hunter|frigate|3)) ([[Type 26 frigate|Type 26]])
| 
| 6
|
|-
| ((sclass|Hobart|destroyer|3))
| 3
|
|
|-
|((flagicon image|Naval Ensign of Canada.svg)) [[Royal Canadian Navy]]
| [[Canadian Surface Combatant]] ([[Type 26 frigate|Type 26]])
| 
| 15
|
|-
| rowspan="3"|((navy|Japan))
| ((sclass|Maya|destroyer|3))
| 2
| 
|
|-
| ((sclass|Atago|destroyer|3))
| 2
|
|
|-
| ((sclass|Kongō|destroyer|3))
| 4
|
|
|-
| ((navy|Republic of Korea))
| ((sclass|Sejong the Great|destroyer|3))
| 3
| 3
|
|-
| ((navy|Norway))
| ((sclass|Fridtjof Nansen|frigate|3))
| 4
|
| 1
|-
| rowspan="2"|((navy|Spain))
| [[F110-class frigate|''Bonifaz''-class]] [[frigate]]
| 
| 5
|
|-
| ((sclass|Álvaro de Bazán|frigate|3))
| 5
|
| 
|-
| rowspan="3"|((navy|United States))
| [[Constellation-class frigate|''Constellation''-class frigate]]
| 
| 20
|
|-
| ((sclass|Arleigh Burke|destroyer|3))
| 73
| 19
|
|-
| ((sclass|Ticonderoga|cruiser|3))
| 17
|
| 10
|-
| colspan="2" |((left|'''Totals:'''))
|'''113'''
|'''71'''
|'''11'''
|}

* The [[Royal Australian Navy]] commissioned three ((sclass|Hobart|destroyer|1))s which have Aegis as the core of their combat systems, with the last entering service in 2020. The Australian Government announced that the class of nine ((sclass|Hunter|frigate|1))s to be built in the next decade will also be Aegis equipped, but with a tactical interface developed by Saab Australia.<ref>((cite web|url=http://www.theaustralian.com.au/national-affairs/missile-defence-for-australias-future-frigates-against-rogue-states/news-story/9a7cdda6bd7c9ffa943a6d67342f0a97|title=Subscribe to The Australian - Newspaper home delivery, website, iPad, iPhone & Android apps|website=www.theaustralian.com.au))</ref> The number of ''Hunter''-class frigates were reduced to 6 following the Australian government's Enhanced Lethality Surface Combatant Fleet program.
*The [[Royal Canadian Navy]] has awarded [[Lockheed Martin Canada]] building 15 [[Canadian Surface Combatant]]s. The ships will be equipped with the AN/SPY-7(V)1 solid state radar and the International Aegis Fire Control Loop (IAFCL) is integrated with Canada's combat management system, CMS 330, developed by Lockheed Martin Canada for the Royal Canadian Navy's [[Halifax-class frigate|''Halifax'' class]] ships. The program will make Canada the owner of the world's second largest Aegis fleet.<ref name=":0" />
* The [[Japanese Maritime Self-Defense Force]] operates seven Aegis ships comprising the four ((sclass|Kongō|destroyer|1))s that entered service from 1993 and two improved units known as the ((sclass|Atago|destroyer|4)) from 2007. Two further improved units known as the ((sclass|Maya|destroyer|4)) were ordered with the first being commissioned in 2020 and the second in 2021.
* The [[Royal Norwegian Navy]] has acquired five Spanish-built ((sclass|Fridtjof Nansen|frigate))s equipped with the Aegis system, with the first, ((HNoMS|Fridtjof Nansen|F310|6)) entering service in 2006 and the last, ((HNoMS|Thor Heyerdahl|F314|6)), in 2011. One, ((HNoMS|Helge Ingstad|F313|6)) was sunk after colliding with an oil tanker. After being raised, it was thought that repairing the ship was too costly and so it was decided to scrap the ship.
* [[Republic of Korea Navy]] currently operates three ((sclass|Sejong the Great|destroyer|1))s, with the lead ship commissioned in 2008. Three further vessels have been ordered.
* The [[Spanish Navy]] is currently operating five F100 ((sclass|Álvaro de Bazán|frigate|0)) Aegis [[frigate]]s, and starting it 2024, it will operate the ((sclass2|F110|frigate|1))<ref>((cite web|url=http://abcblogs.abc.es/tierra-mar-aire/public/post/fragatas-espanolas-diseno-23108.asp/|title=Fragatas F-110: presupuestados por ahora 174 millones en I+D+i y su diseño|date=20 January 2018|publisher=ABC|access-date=24 January 2018))</ref> as well. The F-110 class will incorporate the International Aegis Fire Control Loop (IAFCL) integrated with SCOMBA, the national combat system developed by Navantia.<ref name=":0">((Cite web|url=https://www.navalnews.com/event-news/sna-2020/2020/01/sna-2020-four-nations-to-be-protected-with-lockheed-martins-next-generation-spy-7-radar/|title=SNA 2020: Four Nations to Be Protected with Lockheed Martin's Next Generation SPY-7 Radar|date=2020-01-15|website=Naval News|language=en-US|access-date=2020-01-15))</ref>
* The [[US Navy|U.S. Navy]] currently operates the Aegis equipped ((sclass|Ticonderoga|cruiser|1))s and ((sclass|Arleigh Burke|destroyer|1))s and has ordered more of the latter. It will reportedly integrate the new Aegis Baseline 10 on its upcoming [[FFG(X)]] ships <ref>((Cite web|url=https://www.navalnews.com/naval-news/2020/04/fincantieris-fremm-wins-us-navy-ffgx-frigate-competition/|title=Fincantieri's FREMM Wins US Navy FFG(X) Frigate Competition|date=30 April 2020))</ref>
* Informally, some media refer to the Chinese phased-array radar air-defense destroyers, [[Type 052C destroyer|Type 052C]] and [[Type 052D destroyer]]s, as "Chinese Aegis".<ref>((cite web|title=PLA Navy shows off 'Chinese Aegis' at RIMPAC 2014|date=2014-06-19|url=http://missilethreat.com/pla-navy-shows-off-chinese-aegis-at-rimpac-2014/|archive-url=https://web.archive.org/web/20140814150412/http://missilethreat.com/pla-navy-shows-off-chinese-aegis-at-rimpac-2014/|archive-date=2014-08-14))</ref> Outside foreign observers retain the usage of "Aegis" mainly for the brand-name Aegis Combat System-equipped classes.<ref>((cite web|url=https://thediplomat.com/the-naval-diplomat/2012/09/06/taipei-must-admit-defeat-in-the-arms-race-and-then-work-around-it/|title='Taipei must admit defeat in the arms race…' - The Diplomat|author=James R. Holmes, The Diplomat|work=The Diplomat|access-date=29 January 2016))</ref>

==Gallery==
<gallery>
File:Aegis operators.png|Map with Aegis operators in blue
File:DDG173 JDS Kongo.jpg|((JS|Kongō)), the first non-U.S. ship equipped with AWS
File:USS Vincennes (CG-49) Aegis large screen displays.jpg|Large screen displays on ((USS|Vincennes|CG-49|6)), typical of early Aegis platforms, 1988
File:USS Normandy (CG-60) CIC consoles.jpg|[[Combat Information Center]] (CIC) consoles aboard [[USS Normandy (CG-60)|USS ''Normandy'']], 1997
File:USS John S. McCain (DDG-56) Aegis large screen displays.jpg|Large screen displays on ((USS|John S. McCain|DDG-56|6)), circa 1997. Destroyers have two displays while cruisers have four.
</gallery>

==See also==
* [[Wayne E. Meyer]]
* ((lwc|Aegis Ballistic Missile Defense System))
* ((lwc|PAAMS))
* ((lwc|Typhon Combat System))
* Some destroyers owned by the Chinese Navy equipped with active electronically scanned array and vertical launch systems are also informally called '''Chinese Aegis''' (((lang|zh|中华神盾))), such as [[Type 052D destroyer]], etc.

==References==
((Reflist))

==External links==
((Commons))
* [https://web.archive.org/web/20120524041024/https://www.netc.navy.mil/centers/cscs/ Center For Surface Combat Systems (CSCS)] U.S. Navy Combat Systems Training, Dahlgren, VA.
* [https://web.archive.org/web/20120524041947/https://www.netc.navy.mil/centers/cscs/atrc/  AEGIS Training and Readiness Center (ATRC)] U.S. Navy AEGIS Training, Dahlgren, VA.
* [http://www.fas.org/man/dod-101/sys/ship/weaps/aegis.htm AEGIS Weapon System MK-7] in the FAS Military Analysis Network.
* [http://www.fas.org/man/dod-101/sys/ship/ddg-51.htm DDG-51 ARLEIGH BURKE-class] in the FAS Military Analysis Network.
* ((cite encyclopedia|title=AN/SPY-1 |encyclopedia=The Warfighter Encyclopedia |publisher=Warfighter Response Center |date=October 8, 2003 |url=https://wrc.navair-rdte.navy.mil/warfighter_enc/weapons/SensElec/RADAR/anspy1.htm |access-date=August 10, 2006 |archive-url=https://web.archive.org/web/20041105105825/https://wrc.navair-rdte.navy.mil/warfighter_enc/weapons/SensElec/RADAR/anspy1.htm |archive-date=November 5, 2004 )).
* ((cite web|title=AEGIS Weapon System MK-7 |publisher=[[Jane's Information Group]] |date=April 25, 2001 |url=http://www.janes.com/defence/naval_forces/news/misc/aegis010425.shtml |access-date=August 10, 2006 |archive-url=https://web.archive.org/web/20060701055247/http://www.janes.com/defence/naval_forces/news/misc/aegis010425.shtml |archive-date=July 1, 2006 |url-status=live ))
* ((cite book  | chapter = MK 7 AEGIS FIRE CONTROL SYSTEM RADAR | title = FIRE CONTROLMAN, VOLUME 02--FIRE CONTROL RADAR FUNDAMENTALS | publisher = US NAVY | chapter-url = http://www.tpub.com/content/fc/14099/css/14099_38.htm | url = http://www.maritime.org/doc/pdf/fc2.pdf | access-date = August 10, 2006))

((US Navy navbox))
((Lockheed Martin))
((Naval combat systems))
((Authority control))

((DEFAULTSORT:Aegis Combat System))
[[Category:Anti-aircraft warfare]]
[[Category:Computer systems of the United States Navy]]
[[Category:Anti-ballistic missiles of the United States]]
[[Category:Missile defense]]
[[Category:Naval radars]]
[[Category:Phased array radar]]

Pages transcluded onto the current version of this page (help):

Aegis Ballistic Missile Defense System (edit)
Aegis Combat System (edit)
HNoMS Fridtjof Nansen (F310) (edit)
HNoMS Helge Ingstad (F313) (edit)
HNoMS Thor Heyerdahl (F314) (edit)
JDS Ashigara (DDG-178) (edit)
JDS Atago (DDG-177) (edit)
JDS Chōkai (DDG-176) (edit)
JDS Kirishima (DDG-174) (edit)
JDS Kongō (DDG-173) (edit)
JDS Myōkō (DDG-175) (edit)
JS Haguro (DDG-180) (edit)
JS Kongō (edit)
JS Maya (DDG-179) (edit)
PAAMS (edit)
Typhon Combat System (edit)
USS Arleigh Burke (DDG-51) (edit)
USS Bunker Hill (CG-52) (edit)
USS Chosin (CG-65) (edit)
USS Jack H. Lucas (DDG-125) (edit)
USS John Finn (DDG-113) (edit)
USS John S. McCain (DDG-56) (edit)
USS Lake Champlain (CG-57) (edit)
USS Norton Sound (AVM-1) (edit)
USS Princeton (CG-59) (edit)
USS Ticonderoga (CG-47) (edit)
USS Vincennes (CG-49) (edit)
Template:Ambox (view source) (template editor protected)
Template:Anchor (view source) (template editor protected)
Template:Authority control (view source) (template editor protected)
Template:Cite book (view source) (protected)
Template:Cite encyclopedia (view source) (protected)
Template:Cite journal (view source) (protected)
Template:Cite magazine (view source) (protected)
Template:Cite web (view source) (protected)
Template:Commons (view source) (template editor protected)
Template:Convert (view source) (template editor protected)
Template:Country data Australia (view source) (template editor protected)
Template:Country data Japan (view source) (template editor protected)
Template:Country data Norway (view source) (template editor protected)
Template:Country data Republic of Korea (view source) (template editor protected)
Template:Country data South Korea (view source) (template editor protected)
Template:Country data Spain (view source) (template editor protected)
Template:Country data United States (view source) (template editor protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Flagicon image (view source) (template editor protected)
Template:HNoMS (view source) (semi-protected)
Template:Hlist/styles.css (view source) (protected)
Template:Icon (view source) (template editor protected)
Template:JDS (view source) (semi-protected)
Template:JS (view source) (semi-protected)
Template:Lang (view source) (template editor protected)
Template:Left (view source) (extended confirmed protected)
Template:Link with country (view source) (semi-protected)
Template:Lockheed Martin (edit)
Template:Lwc (view source) (semi-protected)
Template:Main (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:Military navigation (view source) (template editor protected)
Template:More citations needed (view source) (template editor protected)
Template:Naval combat systems (edit)
Template:Naval weapons systems (edit)
Template:Navbox (view source) (template editor protected)
Template:Navy (view source) (template editor protected)
Template:Navy/core (view source) (template editor protected)
Template:Pagetype (view source) (protected)
Template:Plainlist/styles.css (view source) (protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:SDcat (view source) (protected)
Template:Sclass (view source) (template editor protected)
Template:Sclass2 (view source) (template editor protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Template:Side box (view source) (template editor protected)
Template:Sister project (view source) (template editor protected)
Template:Template link (view source) (protected)
Template:Tl (view source) (protected)
Template:USS (view source) (template editor protected)
Template:US Navy navbox (view source) (semi-protected)
Template:Wikidata (view source) (template editor protected)
Module:Anchor (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Authority control (view source) (template editor protected)
Module:Authority control/config (view source) (template editor protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Commons link (view source) (template editor protected)
Module:Convert (view source) (template editor protected)
Module:Convert/data (view source) (template editor protected)
Module:Convert/text (view source) (template editor protected)
Module:Disambiguation/templates (view source) (protected)
Module:EditAtWikidata (view source) (protected)
Module:Exponential search (view source) (template editor protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Format link (view source) (template editor protected)
Module:Hatnote (view source) (template editor protected)
Module:Hatnote/styles.css (view source) (template editor protected)
Module:Hatnote list (view source) (template editor protected)
Module:Icon (view source) (template editor protected)
Module:Icon/data (view source) (template editor protected)
Module:Labelled list hatnote (view source) (template editor protected)
Module:Lang (view source) (template editor protected)
Module:Lang/ISO 639 synonyms (view source) (template editor protected)
Module:Lang/data (view source) (template editor protected)
Module:Language/data/iana languages (view source) (template editor protected)
Module:Language/data/iana regions (view source) (template editor protected)
Module:Language/data/iana scripts (view source) (template editor protected)
Module:Language/data/iana suppressed scripts (view source) (template editor protected)
Module:Language/data/iana variants (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Military navigation (view source) (template editor protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Navbar (view source) (protected)
Module:Navbar/configuration (view source) (protected)
Module:Navbar/styles.css (view source) (protected)
Module:Navbox (view source) (template editor protected)
Module:Navbox/configuration (view source) (template editor protected)
Module:Navbox/styles.css (view source) (template editor protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Pagetype/disambiguation (view source) (protected)
Module:Pagetype/setindex (view source) (protected)
Module:Pagetype/softredirect (view source) (protected)
Module:Redirect (view source) (protected)
Module:SDcat (view source) (protected)
Module:Side box (view source) (template editor protected)
Module:Side box/styles.css (view source) (template editor protected)
Module:String (view source) (protected)
Module:TableTools (view source) (protected)
Module:Unicode data (view source) (template editor protected)
Module:Unicode data/scripts (view source) (template editor protected)
Module:Unsubst (view source) (protected)
Module:WPMILHIST Infobox style (view source) (template editor protected)
Module:WPSHIPS utilities (view source) (template editor protected)
Module:WPSHIPS utilities/data (view source) (template editor protected)
Module:Wd (view source) (template editor protected)
Module:Wd/i18n (view source) (template editor protected)
Module:Wikitext Parsing (view source) (protected)
Module:Yesno (view source) (protected)

Return to Aegis Combat System.

Retrieved from "https://en.wikipedia.org/wiki/Aegis_Combat_System"