The Attack on HMS Sheffield in the Falklands War: Through the Eyes of Lieutenant Colonel Nick Batho

This article contains assessments of the AM-39 Exocet anti-ship missile attack launched against the HMS Sheffield (D80) destroyer by Argentine Navy Dassault-Breguet Super Étendard attack aircraft on 4 May 1982 during the Falklands War. The article was written using statements made by Lieutenant Colonel Nick Batho in 2006 on the Save Our Shipmates website during the process of releasing the Board of Inquiry documents to the public. Batho's testimony, as the Air Defence Officer on board HMS Sheffield during the attack on 4 May 1982, sheds light on the technical and operational aspects of the incident. It should be noted that these statements regarding the 1982 incident were made in 2006. The passage of time and age may have contributed to possible memory lapses. This should be borne in mind when evaluating the testimony.

The cover photo was taken after HMS Sheffield (D80), a guided missile destroyer, was hit by an AM-39 Exocet anti-ship missile fired from an Argentine Navy Dassault-Breguet Super Étendard attack aircraft on 4 May 1982. As there were two ships of the same class in the Argentine Navy, a unique identification procedure was implemented to prevent possible confusion (friend or foe? identity confusion). In this context, the ship was painted with a large black mark vertically on both the starboard and port sides, including the exhaust stack outlet, as a distinguishing feature. This marking has been used as an important identification element in terms of operational speed and visual recognisability. Photo (Royal Navy)

1- In Pursuit of Truth and Accountability

I am writing this statement in response to the endless public debate over the years about what I did, what I did not do, where I was at certain times, and the reasons for my actions regarding the loss of HMS Sheffield. My aim is to present the absolute truth behind the events from my perspective, without holding anything back. I acknowledge that the passage of time may have blurred some details of my memories, but the fundamental truths of what I am about to recount remain unchanged. This text is an honest attempt to lay bare my actions, my decisions, and the reasoning behind those decisions, shaped by the conditions of the moment, which led to the loss of our ship. I invite the reader to first understand the operational status of the ship and crew during that critical period and our perception of the threat we faced in order to fully evaluate the events of that day.

2- Mission Context: Pre-war Operational Grounds

In wartime conditions, decisions made in seconds can only be fairly evaluated when the operational reality of that moment is fully understood. Factors such as the state of the ship's equipment, the level of training of the crew, the structure of the chain of command, and the intelligence at our disposal formed the basis for my actions that day. Without understanding this context, the logic behind the decisions made cannot be understood.

2.1- The Ship's State of Readiness and Training Deficiencies

HMS Sheffield was returning from a tour of duty in the Gulf just before being sent to the Falkland Islands. I must state clearly that at the end of this tour, the ship's operational effectiveness was ‘not particularly high’. During the mission, it was impossible to conduct adequate Air Defence Warfare (AAW) training due to the lack of appropriate assets (e.g., simulated enemy aircraft), and the crew's skills in this area were not fully honed. More than six months had passed since the ship's last visit to Portland, our main training base. Although some training was conducted during the transit south, upon arrival in the operational area, the constant operational deployment of ships and aircraft meant that virtually no training against live targets was possible. In particular, as the Argentines also possessed Type 42 destroyers, locking onto our own Sea Harriers was strictly prohibited.

2.2- The Experience Gap in the Chain of Command

There was a critical experience gap in our command structure, particularly regarding Air Defence Warfare. Our Ship's Captain, Captain Colonel Sam Salt, had joined the ship mid-mission and had not participated in the pre-mission preparation training. As a submariner, he already had very limited knowledge of AAW. The ship's Second-in-Command was a helicopter pilot and therefore also had very little knowledge of how to manage a Type 42 destroyer from the Operations Centre. The reason I mention this is that, under normal circumstances, during Defence Watches, the Ship's Commander and Second-in-Command would take command by keeping opposite watches in the Operations Centre. This was not the case on the Sheffield. As the areas of expertise of these two officers were not suited to this role, we were operating with one fewer naval officer than required in the chain of command. As a Lieutenant Colonel with only one year's experience, serving as Operations Officer at the time, I keenly felt this ‘lack of senior protection’ in the Operations Centre during our planning and operational discussions.

These internal weaknesses, combined with what we believed to be the external threat perception we faced at the time, created a context that determined the course of events.

The map above is from Paul Brown, Abandon Ship: The Real Story of the Sinkings in the Falklands War (Oxford: Osprey Publishing, 2021), on page 59.

3- Perception of Threat: Reality Shaped by Intelligence

Every decision taken on the battlefield is a reflection of the intelligence available. Whether accurate or flawed, this intelligence fundamentally shapes the commanders' risk perception, tactical priorities, and defensive posture at that moment. In our case, the intelligence we had brought with it a series of assumptions that led to tragic consequences.

3.1- Flawed Intelligence: The Overlooked Exocet Threat

During the attack, we were receiving numerous intelligence reports classified as ‘top secret’ about Argentina's capabilities. One of the most critical parts of these reports clearly stated that Argentina possessed AM-39 Exocet air-launched missiles but had not ‘integrated’ them onto Super Etendard launch platforms. Today, we all know how wrong this information was, but at the time, it was information I took seriously and built all my tactical assessments upon.

3.2- Expected Primary Threat: Conventional Bombs

In light of the erroneous intelligence mentioned above, it was accepted that the primary air threat to ships would be ‘conventional bombs’, requiring visual targeting by the pilots of the attack jets that would attack our ship.

The practical implication of this assumption was that for an attack to succeed, Argentine pilots needed to see their targets with their own eyes. This made the ‘cloud base height’ the most critical tactical factor in terms of the ship's vulnerability. If the cloud base was low, we were safe because the pilots could not see us; if it was high, we were open to attack.

This strategic threat assessment directly influenced every tactical decision I made up until the moment of attack on 4 May.

4- Day of the Attack: My Decisions and Rationale

On the day of the attack, the Task Force was on “Air Threat Alert Yellow” status and had been waiting in this state for several days with no sign of Argentine aircraft. During this period, there had been numerous false alarms indicating the detection of the AGAVE radar (codenamed “Condor”), which is the Thomson-CSF/EMD Agave Radar on Super Étendard attack aircraft. It could detect a destroyer-sized target at a distance of approximately 100 kilometres (54 nautical miles). Each time, these signals turned out to belong to friendly Sea Harrier aircraft. This naturally made us all more cautious and sceptical about Condor reports.

To better understand the statements made by Lieutenant Colonel Nick Batho, Air Defence Officer of HMS Sheffield (D80), it would be useful to provide some information about air threat warnings.

The ‘Air Threat Warning’ codes used by the Royal Navy and Task Force during the Falklands War were critical situation levels based on NATO standards that determined the personnel's emergency readiness. This system was vital for managing the crew's response time and the readiness level of weapon systems based on the severity of the threat and its proximity to the ships. Here are the meanings of these three basic alert levels in the context of the Falklands War:

Air Threat Warning States

1. Air Threat Warning White (White)

Meaning: No Threat. No enemy aircraft or missile activity is expected or detected around the Task Force. The general situation is safe.

Action: Personnel are at rest or performing routine duties. Weapon systems and sensors operate at minimum levels or in standard surveillance mode. Energy is conserved.

2. Air Threat Warning Yellow

Meaning: Potential or Expected Threat. Enemy aircraft or missiles have been detected outside the critical engagement distance but are likely to enter the operational area. Threat perception has increased.

Action: Preparedness Status. This is the level at which the ship's personnel remain on standby for extended periods. A large portion of the crew is called to their battle stations or kept close to them.

Primary weapons and air defence systems (missiles, guns) are put on standby and directed towards the threat.

Non-essential radio transmissions are stopped (Radio Silence).

Air patrols (CAP) may be increased.

3. Air Threat Warning Red

Meaning: Imminent Threat or Inevitable Attack. An enemy aircraft or missile has entered the engagement range and immediate defensive action is required. There is usually very little time (e.g. a few minutes) before the threat reaches the ship.

Action: Engagement.

All personnel immediately take up positions at their battle stations.

The ship begins high-speed manoeuvres to prepare for collision.

Weapon systems are ready to fire, and engagement begins upon the commander's order or automatically.

Shipboard damage control teams take up their positions.

According to information provided by Lieutenant Colonel Nick Batho, prolonged Yellow Alarm status (alarm fatigue) and false alarms reduced the crew's alertness to a real threat.

When the Exocet missile struck HMS Sheffield, the ship was probably still in the Yellow state or the transition to the Red state had occurred too late. This psychological and procedural delay prevented a timely response to the attack.

After these brief notes and reminders, we continue with Lieutenant Colonel Nick Batho's account of that day.

This section is a moment-by-moment account of my actions that day. My aim is not only to describe what I did, but also to convey why I made those decisions under the information and conditions available at the time, that is, the thought process that went through my mind. For while mistakes are clearly visible in hindsight, it is essential to explain what it meant to act under the pressure of the moment and with the information available.

4.1- Decision to Depart from the Operations Centre

Before starting my watch (it could have been around 12:00 or 12:30), I went up to the bridge to get a general situation update and, in particular, to check the cloud base myself. Due to the expected ‘conventional bomb’ threat, the cloud base was the most important tactical data for me. At one point during my watch, I requested the Officer of the Watch (OOW) to check the cloud base again via open line. The report received was ‘significantly different’ from my own pre-watch observation (a high base meant we were vulnerable, while a low base meant we could not be attacked because the pilots could not see the target). This concerned me. The OOW in question was one of our less experienced officers, and the accurate determination of cloud base height was of vital importance. My thinking at the time was this: the conventional bomb attack we were expecting would give us ample warning time to activate our countermeasures before the aircraft reached us. This thought, coupled with the days of inactivity, influenced my decision to visit the bridge to personally verify this critical information.

4.2- Bridge Visit and Cabin Route

After meeting with the OOW on the bridge to discuss the cloud base, I set off to return to the Operations Centre. The ship's defence status was at 2Y (two-Yankee) level, which meant the watertight doors were closed. Using the portside staircase to reach the Operations Centre would require me to open a closed watertight door. Therefore, I decided to use the starboard side staircase, which would take me directly to the corridor where the Operations Centre was located and would not require me to open and close a door. This route took me past my cabin, which was on the same level as the Officers' Mess (Wardroom). I used this opportunity to check the details of the conventional bomb targeting systems used by the Argentines. This information was contained in a ‘Top Secret’ package that was not readily accessible in the Operations Centre. After opening my safe and checking the relevant data, I again avoided opening a watertight door by passing through the Officers' Mess and the pantry and heading for the starboard staircase.

4.3- The Human Moment in the Officers' Mess

Passing in front of the Officers' Mess (Wardroom), I encountered a group of petty officers. They asked me how things were going. Aware of how isolated they felt due to their lack of access to operational information, I spoke with them for a few minutes, trying to boost their morale and make them feel secure. I may have been offered a cup of coffee during this conversation, but that was certainly not the reason I was in the Officers' Mess. It was simply on my route to the Operations Centre.

Amidst these personal movements and decisions, the tactical situation was about to change dramatically in a matter of seconds.

5. The Moment of Attack and Aftermath: Collision and Chaos

Our transition from days of low-level alert to the sudden, violent, and shocking reality of an attack happened in seconds. A state of calm anticipation instantly turned into a struggle for survival.

5.1- Return to the Alarm and Operations Centre

While talking to the stewards in the Officers' Lounge, I heard the announcement ‘AAWO to Operations Centre’ over the ship's public address system. I immediately descended the stairs behind the galley and entered the Operations Centre. The PWO (Principal Warfare Officer) greeted me and said that another unit had reported ‘Condor’ (the code name for the AGAVE radar). I sat down in my chair, put on my headphones, and immediately asked the Fighter Controller if we had a Combat Air Patrol (CAP) on the bearing reported; he replied in the negative. Then, when I turned back to my screen, what I saw was a state of complete ‘frantic activity’: numerous automatic tracking ‘eggs’ and perhaps one or two confirmed close or approaching contacts. While trying to understand the situation, the Seadart missile director was attempting to lock onto the target but was unable to lock onto any target with the 909 radar.

5.2. Critical Moments: Chaff and SCOT Communication

At that critical moment, I did not fire the Chaff D (deception) rockets. I am certain that two key factors influenced this decision: Firstly, the severe shortage of rockets we had available. We only had 48 rockets on board the ship. Since each defence pattern required 16 rockets, this meant we only had the capacity for three full patterns of defence. Second, and more importantly, there was an entrenched belief that the expected threat consisted solely of iron bombs.

Furthermore, it is a fact that the SCOT satellite communication system, which was active immediately before the attack, jammed the frequency band used by the Agave radar. After days of inactivity, authorising the use of SCOT to receive our signal traffic was a calculated risk. My expectation was that PWO would issue the ‘silence SCOT’ command as soon as it received the Condor report, and our ability to detect the missile warhead after impact supports that this command was given.

5.3- Impact and Initial Shock

What I felt afterwards was not a huge explosion, but more like a ‘heavy blow’ or ‘punch’ felt when docking at a pier. Immediately after the impact, the Electronic Warfare Director (EWD) reported detecting parameters belonging to an Exocet missile warhead. Now we knew what had hit us.

The event itself had taken place in seconds, but its long-term personal consequences would last a lifetime.

6- Legacy and Moral Burden: A Personal Accounting

A professional account of what happened would be incomplete without acknowledging the deep, indelible and lasting personal impact the event left behind. This was an incident that scarred not only a ship, but also lives and souls.

6.1- The Weight of Responsibility

Having my name mentioned on television, in newspapers and on websites as the person responsible for the loss of the Sheffield was ‘very difficult to live with’ for me and, more importantly, for my family. Very few people have to carry the burden of the loss of 20 lives forever. Which of you reading these lines would want to attend a memorial service feeling what I feel? This burden does not lighten with time; on the contrary, it becomes heavier with every memorial service, with every news report.

6.2- Giving Credit Where Credit is Due

On this occasion, I wish to categorically reject any suggestion that any other crew member on board was ‘asleep,’ lax, or negligent in their duties. Everyone did their utmost under extremely difficult conditions. Every individual on board that day acted with the highest level of professionalism and courage.

6.3- Self-Criticism, Regret and Hope

In the wake of all that has happened, I must take stock of my own actions. I am the first to admit that I made a ‘serious error of judgement’ by not remaining in the Operations Centre during my watch. However, I must also point out that there is ‘no certainty’ that the outcome would have been different had I stayed there.

Nevertheless, I ‘apologise unreservedly’ for the mistakes I made. My hope is that this statement will provide a better understanding of why I did what I did that day and reflect the ‘humility and sadness’ I feel about events that took place so long ago in that distant land.

Nick Batho's statements can be summarised as such. I have observed that criticism directed at Lieutenant Colonel Batho, either by name or indirectly, regarding the incident in which HMS Sheffield (D80) was struck by an AM-39 Exocet anti-ship missile during the Falklands War, has been extensively covered in many sources. Therefore, upon finding a direct statement from Lieutenant Colonel Nick Batho regarding the incident, I wanted to compile the relevant text, format it into a more comprehensible article, and share it with you.

You can review the following link to access my previous article directly related to the sinking of HMS Sheffield. If you haven't read it yet, I recommend you take a look for the sake of context.

The First Major Loss: How HMS Sheffield (D80) Was Hit in the Falklands War?

https://strasam.org/savunma/deniz-silah-ve-sistemleri/ilk-buyuk-kayip-falkland-savasinda-hms-sheffield-d80-nasil-vuruldu-3870

References

The Falklands: The Air Threat to the British Task Force - War History

https://www.navylookout.com/in-perspective-the-loss-of-hms-sheffield/

https://www.navy-net.co.uk/community/threads/help-needed-loss-of-hms-sheffield.55833/page-2#post-956281