Operation Chengiz Khan
Lua error in package.lua at line 80: module 'strict' not found.
Operation Chengiz Khan was the code name assigned to the preemptive strikes carried out by the Pakistani Air Force (PAF) on the forward airbases and radar installations of the Indian Air Force (IAF) on the evening of 3 December 1971, and marked the formal initiation of hostilities of the Indo-Pakistani War of 1971. The operation targeted 11 of India's airfields and there were artillery strikes on Indian positions in Kashmir. The air attacks failed as India had moved all aircraft to reinforced bunkers in anticipation of preemptive action by Pakistan due to India's support of the Mukti Bahini.
In an address to the nation on radio that same evening, then Indian Prime Minister Indira Gandhi held the air strikes to be a declaration of war against India and the Indian Air Force responded with initial air strikes the same night, which were expanded to massive retaliatory air strikes the next morning. Statements released by both nations the next day confirmed the "existence of a state of war between the two countries", although neither government formally issued a declaration of war.
Contents
Background
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
In March 1971, East Pakistan (now Bangladesh) declared independence from Pakistan, starting the Bangladesh Liberation War following rising political discontent and cultural nationalism in East Pakistan and the brutal suppressive force from West Pakistan in response (see Operation Searchlight and 1971 Bangladesh atrocities).[1][2]
Pakistan came under increasing criticism[3] from India, the Soviet Union, Japan, and Europe as the plight of the refugees and their impact on the Indian economy were highlighted by Indira Gandhi in the UN and on a number of global tours.[4] However, the United States and China showed little interest in the situation and actively opposed aid, intervention or support to the Mukti Bahini[5][6] (possibly fearing advancement of Soviet influence deep into South Asia[3]). India's aid to the Mukti Bahini continued unabated, and fighting between the Mukti Bahini and the Pakistani forces grew increasingly vicious. On 9 August 1971, India signed a twenty-year co-operation treaty with the Soviet Union[7] which promised military support to either nation should she be attacked. This provided India cover against any possible Chinese or American intervention in aid of Pakistan if it went to war with India. To the Pakistani leadership, it became clear that armed Indian intervention and secession of East Pakistan was becoming inevitable.[8]
The strategy of pre-emption
By October 1971, the Mukti Bahini had started launching massive raids deep into East Pakistan with active support of the Indian Army troops.[9] The situation had detoriorated to a state of active undeclared war in the East by the end of November, when Indian and Mukti Bahini forces launched offensives on both the eastern and western borders of East Pakistan. Regular Indian army troops engaged and mauled Pakistani armour at Garibpur,[10] during which the 2 intruding PAF jets were shot down and 1 more badly damaged in the Battle of Boyra while offensive manoeuvres were launched in Atgram against Pakistani border posts and communications centres along the eastern border. The Mukti Bahini also launched an offensive on Jessore at this time.[11] It was clear to Islamabad by this time that open conflict was inevitable, and that East Pakistan was indefensible in the long run.[12] Yahya Khan chose at this point to try to protect Pakistan's integrity and to hold India by Ayub Khan's strategy – "The defence of East Pakistan lies in the West".[13]
This policy made the assumptions that an open conflict with India would not last long due to international pressure, and since East Pakistan was undefendable, the war-effort should be concentrated on occupying as large an area of Indian territory as possible as a bargaining tool at the negotiating table. To this end, Gen. Tikka Khan had proposed an offensive into India, and the PAF's overriding priority was to give maximum support to this offensive.[citation needed] The initial plans for the offensive called for at least a temporary cover of air dominance by the PAF under which Khan's troops could conduct a lightning campaign deep into Western India before digging in and consolidating their positions. In order to achieve air dominance, Pakistan decided to launch an offensive counter air strike codenamed Operation Chengiz Khan on Indian airbases.
A second objective for the PAF was to conduct air interdiction against the supply routes for the Indian troops opposing Khan's proposed offensive, but these were accorded as secondary targets to be engaged after the operation started.[citation needed]
The PAF's strikes were based on the same strategy of pre-emptive neutralization of enemy air capability used by the Israeli Air Force against Egyptian and Arab air forces in Operation Focus during the Six-Day War of 1967.[14][15]
The decision to hit India with a pre-emptive air strike was taken on 30 November 1971 during a meeting among the Pakistani President, Gen. Yahya Khan, Chief of Staff Gen. Abdul Hamid Khan, and the Chief of General Staff, Lt. Gen. Gul Hassan Khan.
The objectives of the strike were:
- To surprise the IAF by attacking its forward airfields when it was least expected.
- To neutralize these in order to obtain at least temporary battlefield air superiority in the West.
- To counter-balance the Indian numerical advantage by hitting the forward operating bases of the Indian Air Force as a measure reducing the weight of expected counterattacks on PAF's own bases.
To achieve surprise, the decision was made to strike on a Friday, the day of the jumu'ah (Muslim Sabbath), at 17:45 hrs when shifts in IAF control centers were changing. Emulating its operations' experience in battle against the Indian Air Force during the Indo-Pakistani Conflict of 1965, the decision was made to hit the Indian bases in a two-wave dusk strike followed by a number of night-interdiction missions through the night.[14] The plans for the strike also anticipated the Indians securing their aircraft in blast pens.[citation needed] Also, anticipating difficulty in target acquisition for camouflaged targets such as fuel tanks, ammunition dumps and command centers, the primary objectives set for the operation were the runways and air defense radars.[citation needed]
The first strikes
The final orders for the strike were issued at 17:30 hrs. The first formations were in air and heading for their targets by 17:40 hrs. Officially, it was announced via government channels that the airstrikes were launched in response to attacks along the western border on Pakistan Rangers' outposts by regular troops of the Indian army, which the Indian Air Force was providing support to.[4] The Indians would later deny any engagement on the Western Front.[4] However, the Indian air defence radars failed to detect the approaching formations. The first indications for the Indians of the impending assault was the roar of the strike aircraft over their airfields,[14] while in Delhi, the air-raid sirens were the first indications for newsmen, gathered for the daily brief of the East-Pakistan situation, that something was going on.[4]
- Pathankot — The first of the strikes were mounted against Pathankot AB. Led by a flight of two Mirage IIIs (a reconnaissance craft and a strike escort)[14] a six ship mission of F-86Fs flying from Murid and led by Wing Commander S N Jilani hit Pathankot with unguided rockets and dropped several 125 kg bombs. The main target of this strike was the runway, which was damaged and took the Indian ground crew several hours to repair. These missions went unopposed since the IAF had not scrambled any interception, and faced only AA. Pathankot was covered by interceptors from Adampur following this first strike during the time it took the ground crew to repair its runway.[16]
- Amritsar — At 17:45 hrs, four Mirages flying from Sargodha and led by Wing Commander Hakimullah attacked Amritsar AB.[citation needed] Hakimullah's flight was armed with two 500 kg bombs each, which the strike used efficiently hitting the first 300m of the runway and cratering it enough to leave it nonoperational for several hours.[17][18] However, the Amritsar runway was repaired within the same night to receive detachments of Mig 21s and Su-7 that flew against Rafiqui AB the next morning. A second strike of two F-104 Starfighters, led by Wing Commander Amjad H Khan hit the P-35 radar station at Amritsar, rendering it inoperational for nearly an hour. Two Sukhois then took off from the one remaining serviceable lane of the runway, moments before it was bombed by a passing B-57.[16]
Within forty-five minutes of these strikes, Pakistani troops had shelled India's western frontier and were reported to have crossed the border at Punch in the state of Jammu.[4]
Followup counter-air strikes
The third wave of the PAF counter air strikes were directed to strike Ambala, Agra and Halwara around 18:00 hrs and continued in single or two ship formations through the evening until at least 22:30 hrs. These strikes involved fifteen B-57 Canberras, four T-33s, and one C-130. The B-57s flew seven single ship sorties. These caused significant damage, especially in Uttarlai, and Halwara and impeded IAF's preparation for retaliation.
- Ambala — Ambala was a hit by a two ship B-57 formation led by Wg. Cdr. Rais Rafi. The flight hit the runway with eight bombs, causing minor damage.
- Agra — Like Ambala, Agra, which lay deepest among the PAF's targets that evening, was struck by a two ship mission of B-57 led by Wg. Cdr. Yunus and followed by Flight Lieutenant Mazhar Bukhari. The bombs dropped by Yunus didn't explode. Rais Rafi explained the old age of the bombs as the reason for their ineffectiveness as these were supposed to be used in Second World War.[19] The first Indian Counter strikes launched that very night included the Canberras of No.5 Sqn[20] were based at Agra.
- Sirsa — Sirsa was hit by Sqn. Ldr. Alvi with bombs equipped with time-delayed fuses, damaging the runway heavily and forcing the runway to be closed for the rest of the night.[17]
- Uttarlai — Four T-33s from A-Flight No.2 Squadron, led by Sqn. Ldr. Qureshi, hit Uttarlai, causing damage to the runway. These were launched at the same time as the second strike over Srinagar. Uttarlai was attacked a second time later that night by Wg. Cdr. Akhtar. The net damage to the runway was significant enough to keep the runway closed for six days and for the taxiway to be used instead.[16]
- Jaisalmer, Jodhpur and Jamnagar — In the south, Sqn. Ldr. Ishtak Qureshi's bombs hit the underground power cable at Jaisalmer, cutting off the power supply and telephone connection for six hours. At the same time, Jodhpur was hit by two B-57s led by Sqn. Ldr. Sohail Mansur while Jamnagar was hit by Flt. Lt. Ejaz Azam.[16]
The later flights were not expected to achieve any significant objectives which they miraculously did, and also aided to hamper any counter-strike by the IAF.[14]
The Indian retaliation
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
As Indian Prime Minister Indira Gandhi addressed the nation on radio shortly after midnight[21] informing about the Pakistani attack, the Indian Air Force struck back. By 21:00hrs, the Canberras of the No.35 Squadron and No.106 Squadron, as well as No.5 and No.16 squadron were armed and ready for their foray deep into Pakistan. These flew against eight Western Pakistani airfields of Murid, Mianwali, Sargodha, Chander, Risalewala, Rafiqui, and Masroor. In total, 23 combat sorties were launched that night, inflicting heavy damage to Sargodha and Masroor.[14] The PAF units stationed on these airfields had to operate from taxiways for the following two days.
Through the night the IAF also struck the main East Pakistani airfields of Tejgaon, and later Kurmitolla. At the same time, the IAF was deploying additional aircraft to its forward airfields for the strikes that were to follow the next morning. Within two days, the Indian Air Force was to achieve complete air supremacy in East Pakistan.[8]
Analysis
In total, the Pakistani Air Force dropped 183 bombs over 12 target runways and 120 hits were reported by the pilots.[14] However, of its stated objectives, the PAF was unable to neutralize the Indian Air Force in the west although it certainly achieved surprise[4] besides damaging a few aircraft.[22]
Just as importantly, only a limited section of the PAF's strike capability was employed during Operation Chengiz Khan. Also, compared to the Israeli Air Force's preparation for airstrikes against Egyptians (the Israeli pilots had flown against replicas of the most important Arab airfields) and the use of specific armaments, the PAF had been limited by servicability before the USA supplied spare parts in March of the year and training was limited if any.[14] Constraints of the fledgling Pakistani economy also meant the development of its military could not be supported. The Pakistani Air Force thus lacked ammunition for effective runway denial.[14] East Pakistani personnel of the PAF who defected may have revealed some of the plans, and it appears that IAF was expecting a pre-emptive strike against its forward airfields.[14] A large-scale offensive was therefore doomed to fail, likely to cause heavy losses and bring the PAF in a position where it could never seriously challenge IAF operations.[4]
References and notes
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 3.0 3.1 Donaldson 1972
- ↑ 4.0 4.1 4.2 4.3 4.4 4.5 4.6 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Remarks of President Richard M Nixon on 10 April 1971 at State Department signing of Biological Weapons Convention.
Every Great Power must follow the principle that it should not directly or indirectly allow any other nation to use force or armed aggression against one of its neighbors.
- ↑ Kapur 1972
- ↑ 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Faruqui 2001
- ↑ 14.0 14.1 14.2 14.3 14.4 14.5 14.6 14.7 14.8 14.9 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 16.0 16.1 16.2 16.3 “My years with the IAF” by Air Chief Marshal P C Lal
- ↑ 17.0 17.1 Lal 1986
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
Further reading
- Lua error in package.lua at line 80: module 'strict' not found..
- Lua error in package.lua at line 80: module 'strict' not found..
- Lua error in package.lua at line 80: module 'strict' not found..
- Lua error in package.lua at line 80: module 'strict' not found..