You should: Sign up > Write articles > tell people about your articles > Monetize them > Earn money  > learn/do/earn more

2019 India–Pakistan border skirmishes

From Wikiafripedia, the free afripedia (encyclopedia)
Jump to navigation Jump to search

2019 India–Pakistan skirmishes
Part of the Indo-Pakistani conflicts and the Kashmir conflict
Kashmir map.svg
Map of the Kashmir region
Date14 February 2019 – 22 March 2019
Location
Result Inconclusive
Belligerents

 India

Jaish-e-Mohammed

 Pakistan

Casualties and losses
(Before the onset of hostilities:40–46 CRPF killed[1][2] and 70 wounded[3])
5–10 soldiers wounded[4][5]
1 pilot captured (released)[6]
1 MiG-21 shot down (per India)[7][8]
2 fighter jets shot down (per Pakistan)[9][10][11]

Many Jaish-e-Mohammed militants killed (per India)[12]


None killed (per Pakistan)[13][14]

10–12 Pakistani and 4 Indian civilians killed[15][16][17]

2 soldiers killed [18]
1 F-16 and 3 UAVs shot down (per India)[19][20][21]

India and Pakistan have engaged in a military confrontation across the de facto border in Kashmir, a disputed region which is claimed by both countries and large parts of which are controlled by each country.[22]

The heightened tensions stemmed from a suicide car bombing carried out on 14 February 2019 in which 40 Indian security personnel were killed. A Pakistan-based militant group, Jaish-e-Mohammad, claimed responsibility for the attack.[23] India blamed Pakistan for the bombing and promised a robust response.[24] India has regularly stated Pakistan was utilising militants to destabilise Indian-administered Kashmir.[25] Pakistan, however, denied any involvement in the bombing.[26]

Some twelve days later, India and Pakistan conducted airstrikes against targets in each other's territory.[27]

The first airstrike was conducted by India in the early morning hours of February 26 in the vicinity of the town of Balakot in Khyber Pakhtunkhwa province in Pakistan,[28] several kilometres inside the province's boundary with Pakistan-administered Kashmir.[29] Pakistan's military, the first to announce the airstrike on February 26 morning,[30] described the Indian planes as dropping their payload in an uninhabited wooded hilltop area near Balakot.[31] India, confirming the airstrike later the same day, characterised it to be a preemptive strike directed against a terrorist training camp, and causing the deaths of a "large number" of terrorists.[12][32]

The second airstrike, a retaliatory one,[33] was conducted during daytime on February 27 by Pakistan in a region of Indian-administered Kashmir. A dogfight during this airstrike caused an Indian MiG-21 Bison warplane to be shot down and its pilot, Wing Commander Abhinandan Varthaman, to be taken prisoner by the Pakistan military before being returned on March 1.[34][35]

Analysis of open-source satellite imagery by the Atlantic Council's Digital Forensics Laboratory,[36] San Francisco-based Planet Labs,[37] European Space Imaging,[38] and the Australian Strategic Policy Institute,[39] has concluded that India did not hit any targets of significance on the Jaba hilltop site in the vicinity of Balakot.[40][41]

On April 10, 2019, some international journalists, who were taken to the Jaba hilltop in a tightly controlled trip arranged by Pakistani government, although unable to make a knowledgeable evaluation,[42][43] found the largest building of the site to show no evidence of damage or recent rebuilding.[44][45][46][43]

On 22 March Pakistan and India accepted a peace offer.[47][48]

Background[edit source | edit]

India and Pakistan have long been at odds with each other, having engaged in several wars, conflicts, and military standoffs. The roots of the continued tension are complex, but have centered mainly around the erstwhile princely state of Jammu and Kashmir. After the 1947 Partition of India, the newly-formed independent states of Pakistan and India squabbled over it, which led to the Indo-Pakistani War of 1947–1948 and a subsequent sharing of the state. The settlement was non-agreeable to both the parties and since then, this had become an ongoing intractable issue leading to a war in 1965. The nations also partook in another war in 1971 which led to the formation of Bangladesh. Both countries developed nuclear weapons in the 1990s and this had a sobering effect on the next major conflict – the 1999 Kargil War.[49]

As of now, the Line of Control demarcates the areas of administration: Pakistan administers the territory to the northwest of the line; India administers the territory to the southeast.[50] Since 1989, a militant-fueled insurgency has raged in Indian-administered Kashmir, driven by a desire for either independence or union with Pakistan.[51][52][53] The United Nations has stated Pakistan was providing material support to the militants and stated India was committing human-rights violations.[54]

The standoff occurred ahead of the 2019 Indian general election.[55][56] After the Pulwama attack, Pakistan's PM attributed Indian government's desire to retaliate against Pakistan to the upcoming election.[57][58] The Indian government rejected the allegation.[57] Many analysts have stated that a military response to Pakistan would improve the electoral prospects of India's ruling party.[59][60][56][61]

Military events[edit source | edit]

Pulwama attack[edit source | edit]

The 2019 Indo-Pakistan military standoff is a result of[62] a militant attack in February 2019, when a Central Reserve Police Force (CRPF) convoy carrying security personnel on the Jammu-Srinagar National Highway was attacked by a vehicle-borne suicide bomber at Lethpora in the Pulwama district, Jammu and Kashmir, India. Over 40 CRPF personnel and the perpetrator were killed in the attack, which Jaish-e-Mohammed took responsibility for. The attacker was identified as Adil Ahmad Dar, a militant from Jammu and Kashmir, and a member of Jaish-e-Mohammed.[63] This was the deadliest attack on Indian forces in Kashmir since 1989.[64]

Balakot airstrike[edit source | edit]

On 26 February 2019, the Indian Air Force conducted airstrikes at Balakot in Pakistan. The strikes were subsequently stated to be "non-military" and "preemptive" in nature; targeting a Jaish-e-Mohammed facility within Pakistan. The Indian government stated that the airstrike was in retaliation to the Pulwama attack and that "a very large number of JeM terrorists, trainers, senior commanders and groups of jihadis" were eliminated who were preparing for launching another suicide attack targeting Indian assets.[65]

Indian media reported to have confirmed from official sources that twelve Mirage 2000 jets were involved in the operation and that they struck multiple militant camps in Balakot, Chakothi and Muzaffarabad operated by Jaish-e-Mohammed, Lashkar-e-Taiba and Hizbul Mujahideen,[66] killing about 350 militants. The exact figures varied across media-houses.[67]

Pakistani officials acknowledged the intrusion of Indian aircraft into the country's airspace but rejected the statements about the results. They stated that the Indian jets were intercepted and that the payloads were dropped in unpopulated areas and resulted in no casualties or infrastructural damage.[68] Pervez Khattak, the Pakistani Defence Minister, stated that the Pakistani Air Force did not retaliate at that time because "they could not gauge the extent of the damage".[69]

Business Today India stated that the area around Balakot had been cordoned off by the Pakistan Army and evidences such as the dead bodies were being cleared from the area.[70] Praveen Swami writing for Firstpost said that Indian intelligence estimated a figure of about 20 casualties and that there were five confirmed kills per burial records.[71] He also said there was a JeM rally in Khyber-Pakhtunkhwa on 28 February, wherein Masood Azhar's brother, Abdul Rauf Rasheed Alvi mentioned India's attack of their headquarters and vowed revenge.[71] In another piece he stated that RAW analysts estimated 90 casualties including three Pakistani Army trainers, based on intercepted communications.[72] Swami also said there was a lack of witness testimony to independently assess the validity of above statements.[72]

This airstrike was the first time since the Indo-Pakistani War of 1971 that aerial attacks had been carried out across the Line of Control.[72]

Villagers from the area said that four bombs struck a nearby forest and a field resulting in damage to a building and injuring a local man around 3:00 AM.[73][74] A team from Al Jazeera visited the site two days after the strikes and said "splintered pine trees and rocks" which were strewn across the four blast craters. Local hospital officials and residents said that they did not come across any casualty or wounded people. The reporters located the facility,[67] a school run by Jaish-e-Mohammed, at around a kilometre to the east of one of the bomb craters, atop a steep ridge, but were unable to access it.[75] Reporters from Reuters were denied access to the madrassa by the military but they reported the structure and its vicinity to be intact from the rear.[74]

Some diplomats and analysts have raised doubts about the efficacy of the strike, stating that the terrorist groups along the border would have vacated the area, after the Indian Prime Minister vowed to retaliate against the Pulwama attack.[76] The local people varied as to the purpose of the facility.[75] Whilst some stated it being an active Jaish training camp, others stated it to have been a mere school for the local kids and that such militant camps had used to exist far earlier.[74][75] Satellite-data analysis by Nathan Ruser, from the Australian Strategic Policy Institute said there was an absence of any apparent evidence to verify Indian statements.[67][77][78] Michael Sheldon, a digital forensics analyst at the Atlantic Council, did an independent investigation on the issue, in which he said that no damage was caused to any infrastructure around the target site. He concluded that "something appears to have gone wrong in the targeting process", which was mysterious in light of the autonomous nature of the missiles reportedly used.[79][80][81][82]

In contrast, Indian officials said that synthetic aperture radar showed that four buildings had been destroyed; however, they did not release those images.[78] Vice-Marshal RGK Kapoor of the Indian Air Force said on 28 February 2019 that though it was "premature" to provide details about the casualties, they had "fairly credible evidence" of the damage inflicted on the camp by the air strikes.[74]

Border skirmishes[edit source | edit]

Heavy skirmishes between Pakistani and Indian forces occurred along the Line of Control on 26 February, with small arms and mortar fire being exchanged.[83] Pakistani officials reported that at least four civilians were killed, and eleven were wounded.[84][85] A 55-year-old woman and her two children were killed in the Nakyal sector. In the Khuiratta sector, a 40-year-old woman was killed.[84]

Throughout 27 February, heavy exchanges of fire between Indian and Pakistani forces continued along the Line of Control.[86] Ten Indian soldiers were injured along with two residential houses being destroyed in the skirmishes.[5] The Pakistani Army stated that on March 1, two of its soldiers were killed by firing from the Indian Army at the Line of Control.[87] Shelling across the Line of Control killed a Kashmiri woman and her two sons after a shell landed on their home, with another civilian being critically wounded.[88] On 6 and 7 March, Pakistani and Indian forces exchanged heavy artillery fire along the line of control, with Pakistani forces using 130 mm and 105 mm artillery and 120 mm mortars.[89] In response to the Pakistani artillery fire, the Indian army began utilizing 155mm FH77B Bofors cannons against Pakistani positions.[89]

Retaliatory airstrikes, capture and release of pilot[edit source | edit]

On 27 February, Pakistani military officials announced that Pakistan had carried out an airstrike against multiple targets in Jammu and Kashmir. A military spokesman said that the Pakistan Air Force (PAF) was able to lock onto Indian military installations, but opted to drop weapons into open areas instead, "to avoid human loss and collateral damage."[90][91] Pakistan's Prime Minister Imran Khan said that the airstrikes only aimed to "send a message" and appealed for negotiations to avoid a full-blown war.[92] The spokesman further said that the Pakistan Air Force had shot down two Indian aircraft after they encroached on Pakistan's airspace, one of which fell in Pakistan administered Kashmir while the other fell in Indian administered Kashmir.[93][94] It was also stated that Pakistan Army had captured two Indian pilots, one of whom was said to be injured and taken to the Combined Military Hospital.[90][95] But a subsequent statement revised the count down to one–Abhinandan Varthaman, a Wing Commander.[8]

India rejected this version of events and stated to have "successfully foiled" Pakistan's attempt to "target military installations".[96] An Indian Air Force (IAF) official statement hours after the airstrike stated that bombs had been dropped on Indian army formation compounds, but there was no damage to military installations.[97] The Indian military later stated that three Pakistan Air Force jets had crossed the Line of Control (LoC) from Nowshera, Jammu and Kashmir and had dropped bombs over Nadian, Laam Jhangar, Kerri in Rajouri District and Hamirpur area of Bhimber Galli in Poonch, before being pushed back by six Indian airforce jets.[98][99][100] There were no damage or casualties.[101] Raveesh Kumar from the Indian Ministry of External Affairs also stated that a Pakistani aircraft of the sortie was shot down by the Indian Air Force in the process.[19][72] India initially contradicted Pakistan's statement of capturing a pilot[102] but subsequently the Indian Ministry of External Affairs confirmed[19] that an Indian pilot was missing in action after a MiG-21 Bison fighter plane was lost while engaging with Pakistani jets.[103]

The retaliatory air strikes coupled with the capture of the Indian pilot led to a heightened state of military alert. Tanks were deployed to the border in the Pakistani side whilst several Kashmiri residents reportedly fled their homes and painted their homes with red-cross signs to avert air-strikes.[104]

Pakistan released the captured pilot on 1 March, describing the move as a gesture of peace.[6][105][106] The Indian Air Force though stated that the pilot's release was an obligation under the Geneva Conventions.[107] The Indian media also criticized Pakistan's release of his photographs and interrogation videos to be against the protocols of the convention.[108][109] A video published by the state just prior to his release that showed him praising Pakistani Army and condemning Indian media was criticized for being heavily edited.[110][111]

Naval intrusion[edit source | edit]

On 5 March, the Pakistani Navy stated to have successfully warded off an intrusion attempt by an Indian submarine into its territorial waters and released a video of a surfaced submarine.[112][113][114] The Indian Navy subsequently rejected these statements as "false propaganda."[115]


Other incidents[edit source | edit]

Closure of Pakistani airspace[edit source | edit]

On 27 February, Pakistan cancelled all commercial flights and closed its airspace until the midnight of 28 February.[116][117] A NOTAM was issued by the Pakistan Civil Aviation Authority to close the airspace.[118] Airlines were required to reroute or cancel their flights with routes planned over Pakistan.[119] On 1 March, the NOTAM closing the airspace was extended until 8:00 AM (UTC) on 4 March with 23 exceptions listed.[120] Pakistan's airspace was closed for flights crossing the country's airspace except for arriving and departing flights at major airports in Pakistan.[121] The airspace closure was again repeatedly extended,.[122][123][124][125] The Pakistan finally opened its airspace for all civilian aircraft on 15 July 2019, after 140 days.[126][127]

India did not close down its civilian air traffic and only the Srinagar airspace was closed for 2–3 hours on the day of the skirmish.[128] However the Pakistani flights were allowed usage of Indian airspace only after 15 July when Pakistan opened up its airspace.[129]

The airspace closure led to a loss of US$100 Million for Pakistan due to the skipping of its airspace by an average of 400 aircraft daily.[130] Air India suffered loss of ₹491 Crore till 2 July, as it had to reroute its flights that were affected by the closure of Pakistani airspace. Similarly private Indian airlines SpiceJet lost ₹ 30.73 crore, IndiGo lost ₹ 25.1 crore and GoAir lost ₹ 2.1 crore.[131]

Suspension of Samjhauta Express[edit source | edit]

On 28 February, Samjhauta Express, a train that runs twice weekly between India and Pakistan, was suspended by the government of Pakistan.[132] It was scheduled to depart from Lahore with 16 passengers, who were stranded there.[133] On 4 March, Pakistan, and consequently India, resumed the operations of Samjhauta Express.[134]

Pakistan arrests suspected militants[edit source | edit]

On 5 March, Pakistan arrested 44 members of various groups, including the Jaish-e-Muhammad. Some of those arrested had been named by India in a dossier it gave to Pakistan in the aftermath of the Pulwama attack.[135] Pakistan said those arrested will be held for at least 14 days, and if India provided further evidence they would be prosecuted.[136] Among those arrested were relatives of JeM leader Masood Azhar, including his son Hamad Azhar and his brother Abdul Rauf.[135]

Peace Offer[edit source | edit]

Both Prime Minister Imran Khan of Pakistan and Prime Minister of India Narendra Modi agreed on a peace offer on 22 March ending hostilities and vowed to fight against terrorism together.[137][138]

Aftermath[edit source | edit]

Revocation of special status and August border clashes[edit source | edit]

On 5 August 2019, the Government of India revoked the special status granted to Jammu and Kashmir[139]

On 15 August Pakistan and Indian forces exchanged fire over the disputed frontier in Kashmir, leaving 3 Pakistani soldiers dead and two civilians.[140]

On 21 August the Indian-administered Kasmir police informed about a gun battle that left a rebel and a police officer killed.[141] The deceased militant was a member of Lashkar-e-Taiba a terror organization.[141]

Artillery strike[edit source | edit]

The Statesman reported that 18 terrorists and 16 Pakistani soldiers were killed when Indian Army launched artillery strikes on terrorist camps in Neelum valley on October 19 and 20.[142] Mohammad Faisal, however, said that five Pakistani civilians had died.

International reaction[edit source | edit]

A number of nations, including Australia,[143] Canada,[144] China,[145] Indonesia,[146] Malaysia,[147] Sri Lanka,[148] the United Arab Emirates,[149] and the United States,[150] expressed their concern, with some calling for restraint. Iran and Turkey have each offered to mediate the crisis.[151][152]

See also[edit source | edit]

Notes[edit source | edit]

References[edit source | edit]

  1. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  2. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  3. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  4. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  5. 5.0 5.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  6. 6.0 6.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  7. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  8. 8.0 8.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  9. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  10. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  11. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  12. 12.0 12.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  13. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  14. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  15. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  16. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  17. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  18. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  19. 19.0 19.1 19.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  20. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  21. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  22. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "Both India and Pakistan claim the Himalayan region of Kashmir, but it has been divided between them for more than 70 years."
  23. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "The Pakistan-based militant group Jaish-e-Mohammed claimed responsibility for the bombing. It said it was carried out by Adil Ahmad Dar, a locally recruited fighter from south Kashmir’s Pulwama district. The group released a video showing Dar delivering his will and a photograph of him surrounded by guns and grenades."
  24. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "“We will give a befitting reply, our neighbour will not be allowed to de-stabilise us,” Modi said ..."
  25. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "India and the United States accuse Pakistan of supporting and sheltering militants who launch attacks into Indian-held territory, something Pakistan denies."
  26. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "Pakistan has denied involvement in the attack, in which at least 40 Indian soldiers were killed Thursday when a driver slammed an explosives-packed vehicle into a paramilitary convoy."
  27. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: The two days of tit-for-tat airstrikes ... the first since 1971, were triggered by a Feb. 14 terrorist bombing in Indian-controlled Kashmir that killed 40 Indian security personnel."
  28. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  29. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "Pakistan, ... said the war planes made it up to five miles [eight kilometres] inside its territory"
  30. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "Pakistan, which was the first to announce the incursion, ..."
  31. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "A spokesman for Pakistan’s armed forces, Maj. Gen. Asif Ghafoor, on Tuesday posted on Twitter four images of a forested area pockmarked with small craters and debris, which he said was the site of Indian airstrikes."
  32. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  33. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "A day after India’s strike, Pakistan retaliated, sending planes to attack military installations in India."
  34. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  35. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  36. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "Indian fighter jets carried out strikes against targets inside undisputed Pakistani territory, but open-source evidence suggested that the strike was unsuccessful."
  37. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "The images produced by Planet Labs Inc, a San Francisco-based private satellite operator, show at least six buildings on the madrasa site on March 4, six days after the airstrike. ... There are no discernible holes in the roofs of buildings, no signs of scorching, blown-out walls, displaced trees around the madrasa or other signs of an aerial attack."
  38. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: " ... said Managing Director Adrian Zevenbergen. '... The image captured with Worldiew-2 of the buildings in question shows no evidence of a bombing having occurred. There are no signs of scorching, no large distinguishable holes in the roofs of buildings and no signs of stress to the surrounding vegetation.' "
  39. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "But India’s recent air strike on a purported Jaish-e-Mohammad terrorist camp in Balakot in Pakistan on 26 February suggests that precision strike is still an art and science that requires both practice and enabling systems to achieve the intended effect. Simply buying precision munitions off the shelf is not enough."
  40. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: " Open-source satellite imagery suggests India did not hit any targets of consequence in the airstrikes it conducted after the terrorist attack on the paramilitaries.
  41. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "Analysis of open-source satellite imagery has also cast doubt on India’s claims. A report by the Atlantic Council’s Digital Forensic Research Lab was able to geolocate the site of the attack and provide a preliminary damage assessment. It compared satellite images from the days before and after India’s strike and concluded there were only impacts in the wooded areas with no damage visible to surrounding structures."
  42. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "The expectation among some of the visitors was that it might help to settle a number of mysteries about the attack. In particular, whether, as India had said, it was a huge success and took out a major militant training camp or whether - as Pakistan says - India’s warplanes missed the madrasa compound completely and hit surrounding hills instead. The difference - as many as 300 dead militants or no fatalities at all. There was also the question about whether the madrasa, one of more than 30,000 across Pakistan where children of all ages are taught to memorize and recite the Koran, was a cover for the Islamist group Jaish-e-Mohammed (JeM), which was allegedly using the site to train fighters to infiltrate Indian-controlled Kashmir. ...But the journalists and diplomats, most of whom spent well over an hour climbing steep slopes to get to the madrasa in the Jaba village area near the town of Balakot, didn't get enough time to make any kind of informed assessment. They were mostly restricted to looking around the madrasa’s main building. They were hurried away by the army, which organized the trip, after less than half an hour."
  43. 43.0 43.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "It was at the centre of a clash that almost brought two nuclear nations to war, but exactly what goes on inside a small madrasa on a hilltop near Kashmir remains a mystery. One thing is clear: India's claim that it destroyed a militant training camp and killed more than 300 extremists cannot be backed up by the evidence. More than a month after India launched airstrikes inside Pakistan in retaliation for a militant attack that killed 40 paramilitary troops in Kashmir, foreign media have been allowed to see the areas hit."
  44. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "Those visiting the site on Wednesday didn't see any signs that there had been significant building work to either clear structures or erect new ones. And the vegetation didn't appear to have suffered the stress that might be expected from a missile attack. ... The main madrasa building itself doesn't appear to be reinforced in any major way - it has a metal roof with some modest wooden beams."
  45. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "They were given access to an Islamic school in Balakot, where Indian media say militants were killed in retaliation for an attack in Kashmir. The large building appeared to be fully intact ..."
  46. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). Quote: "International outlets which visited the Indian air strike site in Pakistan found no evidence of a major terrorist training camp -- or of any infrastructure damage at all."
  47. https://www.voanews.com/south-central-asia/pakistani-pm-receives-national-day-greetings-indian-counterpart
  48. https://www.pakistantoday.com.pk/2019/03/22/time-to-work-together-indias-modi-messages-pm-imran/
  49. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  50. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  51. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  52. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  53. Conflict Encyclopedia – India: Kashmir Archived 1 October 2017 at the Wayback Machine, Uppsala Conflict Data Program, 29 May 1977, retrieved 2013-05-29,
  54. Why the Kashmir conflict is not just an India-Pakistan border dispute Archived 5 March 2019 at the Wayback Machine, PBS, March 9, 2019.
  55. Tensions Between India and Pakistan Are at Their Highest Point in Decades. Here's What to Know Archived 28 February 2019 at the Wayback Machine, TIME.
  56. 56.0 56.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  57. 57.0 57.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  58. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  59. Lara Seligman and Robbie Gramer. "Amid Re-Election Campaign, Modi Takes the Fight to Pakistan Archived 28 February 2019 at the Wayback Machine," Foreign Policy, February 27, 2019.
  60. Soutik Biswas. "'War' and India PM Modi's muscular strongman image Archived 6 March 2019 at the Wayback Machine," BBC News, March 6, 2019.
  61. Krishna N. Das, Devjyot Ghoshal. "Air strike on Pakistan sparks celebrations in India, seen boosting Modi support Archived 6 March 2019 at the Wayback Machine," Reuters, February 26, 2019.
  62. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  63. Pulwama Attack 2019, everything about J&K terror attack on CRPF by terrorist Adil Ahmed Dar, Jaish-eMohammad Archived 18 February 2019 at the Wayback Machine, India Today, 16 February 2019.
  64. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  65. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  66. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  67. 67.0 67.1 67.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  68. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  69. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  70. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  71. 71.0 71.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  72. 72.0 72.1 72.2 72.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  73. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  74. 74.0 74.1 74.2 74.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  75. 75.0 75.1 75.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  76. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  77. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  78. 78.0 78.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  79. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  80. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  81. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  82. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  83. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  84. 84.0 84.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  85. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  86. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  87. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  88. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  89. 89.0 89.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  90. 90.0 90.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  91. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  92. "Pakistan PM Imran Khan appeals for talks with India to avoid war Archived 27 February 2019 at the Wayback Machine", The Guardian
  93. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  94. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  95. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  96. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  97. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  98. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  99. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  100. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  101. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  102. M. Ilyas Khan, Abhinandan: Villagers recount dramatic capture of pilot Archived 1 March 2019 at the Wayback Machine, BBC News
  103. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  104. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  105. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  106. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  107. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  108. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  109. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  110. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  111. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  112. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  113. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  114. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  115. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  116. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  117. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  118. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  119. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  120. https://www.caapakistan.com.pk/upload/Notams/A210-19.txt[permanent dead link]
  121. https://www.caapakistan.com.pk/NOTAMS/NotamView.aspx
  122. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  123. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  124. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  125. https://www.livemint.com/news/india/pakistan-airspace-closure-costs-over-rs-548-crore-to-indian-airlines-1562254701059.html
  126. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  127. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  128. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  129. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  130. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  131. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  132. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  133. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  134. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  135. 135.0 135.1 Asghar, Naseem. "Son of Masood Azhar among 44 arrested Archived 6 March 2019 at the Wayback Machine," The Express Tribune.
  136. Asad Hashim. "Pakistan arrests scores in fresh crackdown on armed groups Archived 6 March 2019 at the Wayback Machine," Al Jazeera English
  137. https://www.voanews.com/south-central-asia/pakistani-pm-receives-national-day-greetings-indian-counterpart
  138. https://www.pakistantoday.com.pk/2019/03/22/time-to-work-together-indias-modi-messages-pm-imran/
  139. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). (subscription required) Quote: "Jammu and Kashmir, state of India, located in the northern part of the Indian subcontinent in the vicinity of the Karakoram and westernmost Himalayan mountain ranges. The state is part of the larger region of Kashmir, which has been the subject of dispute between India, Pakistan, and China since the partition of the subcontinent in 1947."
  140. Five killed as Pakistan and India trade fire amid Kashmir tension
  141. 141.0 141.1 Two killed in first Kashmir gun battle since lockdown began
  142. https://web.archive.org/web/20191028153039/https://www.thestatesman.com/india/18-terrorists-killed-jem-launch-pads-destroyed-artillery-strikes-army-pok-reports-1502813337.html
  143. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  144. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  145. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  146. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  147. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  148. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  149. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  150. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  151. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  152. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).

Template:Indo-Pakistani relations