Indian soldiers losing lives on China border a first in 45 years

coastaldigest.com web desk
June 16, 2020

New Delhi, Jun 16: Despite Prime Minister Narendra Modi led government’s attempt to downplay the border dispute with China, matters have heated up unprecedentedly along the Line of Actual Control (LAC)- the effective Sino-India border in Eastern Ladakh. 

The country has lost three precious lives – an army officer and two soldiers. The last time blood was spilled on the LAC, before the latest episode, was 45 years ago when the Chinese ambushed an Assam Rifles patrol in Tulung La.

India had lost four soldiers on October 20, 1975 in Tulung La, the last time bullets were fired on the India-China border though both the countries witnessed bitter stand-offs later at Sumdorong Chu valley in 1987, Depsang in 2013, Chumar in 2014 and Doklam in 2017.

Between 1962 and 1975, the biggest clash between India and China took place in Nathu La pass in 1967 when reports suggest that around 80 Indian soldiers were killed and many more Chinese personnel.

While three soldiers, including a Commanding Officer, were killed in the latest episode in Galwan Valley, the government describes it as a "violent clash" and does not mention opening fire.

New Delhi described the locality where the 1975 incident took place as "well within" its territory only to be rebuffed by Beijing as "sheer reversal of black and white and confusion of right and wrong".

The Ministry of External Affairs had then said that the Chinese had crossed the LAC and ambushed the soldiers while Beijing claimed the Indians entered their territory and did not return despite warnings.

The Indian government maintained that the ambush on the Assam Rifles' patrol in 1975 took place "500 metres south of Tulung" on the border between India and Tibet and "therefore in Indian territory". It said Chinese soldiers "penetrating" Indian territory implied a "change in China's position" on the border question but the Chinese denied this and blamed India for the incident.

The US diplomatic cables quoted an Indian military intelligence officer saying that the Chinese had erected stone walls on the Indian side of Tulung La and from these positions fired several hundred rounds at the Indian patrol.

"Four of the Indians had gone into a leading position while two (the ones who escaped) remained behind. The senior military intelligence officer emphasised that the soldiers on the Indian patrol were from the area and had patrolled that same region many times before," the cable said.

One of the US cables showed that former US Secretary of State and National Security Adviser Henry Kissinger sought details of the October 1975 clash "without approaching the host governments on actual location of October 20 incident". He also wanted to know what ground rules were followed regarding the proximity of LAC by border patrols.

A cable sent from the US mission in India on November 4, 1975 appeared to have doubts about the Chinese account saying it was "highly defensive".

"Given the unsettled situation on the sub-continent, particularly in Bangladesh, both Chinese and Indian authorities have authorised stepped up patrols along the disputed border. The clash may well have ensued when two such patrols unexpectedly encountered each other," it said.

Another cable from China on the same day quoted another October 1974 cable, which spoke about Chinese officials being concerned for long that "some hotheaded person on the PRC (People's Republic of China) might provoke an incident that could lead to renewed Sino-Indian hostilities. It went on to say that this clash suggested that "such concerns and apprehensions are not unwarranted".

According to the United States diplomatic cables, Chinese Foreign Ministry on November 3, 1975 disputed the statement of the MEA spokesperson, who said the incident took place inside Indian territory.

The Chinese had said "sheer reversal of black and white and confusion of right and wrong". In its version of the 1975 incident, they said Indian troops crossed the LAC at 1:30 PM at Tulung Pass on the Eastern Sector and "intruded" into their territory when personnel at the Civilian Checkpost at Chuna in Tibet warned them to withdraw.

Ignoring this, they claimed, Indian soldiers made "continual provocation and even opened fire at the Chinese civilian checkpost personnel, posing a grave threat to the life of the latter. The Chinese civilian checkpost personnel were obliged to fire back in self defence."

The Chinese Foreign Ministry spokesperson had also said they told the Indian side that they could collect the bodies "anytime" and on October 28, collected the bodies, weapons and ammunition and "signed a receipt".

The US cables from the then USSR suggested that the official media carried reports from Delhi on the October 1975 incident and they cited only Indian accounts of the incident "ridiculing alleged Chinese claims that the Indians crossed the line and opened fire first".

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
December 15,2025

Udupi, Dec 15: What was meant to be a post-pilgrimage gathering turned tragic in Padukere village of Brahmavar taluk, Udupi district, late Sunday night, when a clash among youths escalated into a fatal assault, leaving one man dead.

The victim has been identified as 30-year-old Santosh Mogaveera, a resident of Padukere.

According to preliminary information, the incident took place during a late-night drinking party involving a group of local youths who had recently returned after completing their pilgrimage to the Sabarimala shrine. An argument reportedly broke out among the group and soon escalated into a violent confrontation.

During the ensuing brawl, Santosh Mogaveera was allegedly assaulted and collapsed at the spot after sustaining serious injuries. He was rushed by local residents to a private hospital in Brahmavar, where doctors declared him dead.

On receiving information, senior police officials, including Brahmavar Circle Inspector Gopikrishna, Kota Police Sub-Inspector Praveen Kumar T, Station ASI Manthesh Jabagoudar, and head constables Pradeep and Ashok, visited the spot and conducted an inspection.

Police have taken four youths into custody in connection with the incident. A case has been registered at the Kota police station, and further investigation is underway to ascertain the exact sequence of events leading to the death.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
December 4,2025

indigocrisis.jpg

Angry outbursts, long queues, and desperate appeals filled airports across India today as IndiGo grappled with a severe operational breakdown. Hundreds of flights have been cancelled or delayed, leaving thousands of passengers stranded through the night and forcing many to spend long hours at helpdesks.

Social media was flooded with videos of fliers pleading for assistance, accusing the airline of misleading updates, and demanding accommodation after being stuck for 10 to 12 hours at airports such as Hyderabad and Bengaluru.

What Triggered the Meltdown?

IndiGo has attributed the widespread disruption to “a multitude of unforeseen operational challenges.” These include:

•    Minor technology glitches
•    Winter-season schedule adjustments
•    Bad weather
•    Congestion in the aviation network
•    New crew rostering rules (Flight Duty Time Limitations or FDTL)

Among these, the most disruptive has been the implementation of the updated FDTL norms introduced by the Directorate General of Civil Aviation (DGCA) in January 2024.

These rules were designed to reduce pilot fatigue and improve passenger safety. Key changes include:

•    Longer weekly rest periods for flight crew
•    A revised definition of “night,” extending it by an extra hour
•    Tighter caps on flight duty timing and night landings
•    Cutting night shifts for pilots and crew from six per roster cycle to just two

Once these norms became fully enforceable, airlines were required to overhaul rosters well in advance. For IndiGo, this triggered a sudden shortage of crew available for duty, leading to cascading delays and cancellations.

Why IndiGo Was Hit the Hardest

IndiGo is India’s largest airline by a wide margin, operating over 2,200 flights daily. That’s roughly double the number operated by Air India.

When an airline of this size experiences even a 10–20% disruption, it translates to 200–400 flights being delayed or grounded — producing massive spillover effects across the country.

IndiGo also relies heavily on high-frequency overnight operations, a model typical of low-cost carriers that aim to maximise aircraft utilisation and reduce downtime. The stricter FDTL norms clash with these overnight-heavy schedules, forcing the airline to pull back services.

Aviation bodies have also criticised IndiGo’s preparedness. The Airline Pilots' Association of India (ALPA) said airlines were given a two-year window to plan for the new rules but “started preparing rather late.” IndiGo, it said, failed to rebuild crew rosters 15 days in advance as required.

The Federation of Indian Pilots (FIP) went further, calling the crisis the result of IndiGo’s “prolonged and unorthodox lean manpower strategy,” and alleging that the airline adopted a hiring freeze even as it knew the new rules would require more careful staffing.

How Many Flights Are Affected?

In the past 48 hours, over 300 flights have been cancelled. At least 100 more are expected to be cancelled today.

City-wise impact:

•    Hyderabad: 33 expected cancellations; several fliers stranded overnight
•    Bengaluru: over 70 expected cancellations
•    Delhi, Mumbai, Chennai, Kolkata: widespread delays and missed connections

Passengers shared distressing accounts online.

One customer at Hyderabad airport said they waited from 6 PM to 9 AM with “no action taken” regarding their delayed Pune flight. Another said IndiGo repeatedly told them the crew was “arriving soon,” only for the delay to stretch over 12 hours.

IndiGo has apologised for the disruption and promised that operations will stabilise within 48 hours, adding that “calibrated adjustments” are being made to contain the chaos.

What Should Passengers Do Now?

For those flying in the next few days, especially with IndiGo, here are key precautions:

1. Keep Checking Flight Status
Monitor your flight closely before leaving for the airport, as delays may be announced last-minute.

2. Arrive Early
Expect long queues at counters and security due to crowding and rescheduling.

3. Carry Essentials
Pack snacks, water, basic medicines, chargers, and items for children or senior citizens. Extended waiting times should be anticipated.

4. Use Flexible Booking Options
If you booked tickets with a free-date-change or cancellation option, consider using them.
If you haven’t booked yet, prefer refundable or flexible fares, or even consider alternate airlines.

5. Follow IndiGo’s Updates
Keep an eye on IndiGo’s official social media channels and contact customer support for rebooking and refund queries.

What Needs to Change?

Pilot groups have raised concerns not just about staffing but also the planning practices behind it.
The Federation of Indian Pilots accused IndiGo of:

•    Imposing an unexplained hiring freeze despite knowing the FDTL changes were coming
•    Entering non-poaching agreements that limited talent movement
•    Keeping pilot pay frozen
•    Underestimating the need to restructure operations in advance

They have urged DGCA to approve seasonal schedules only after airlines prove they have adequate pilot strength under the new norms.

ALPA also warned that some airlines might be using the delays as an “immature pressure tactic” to push DGCA for relaxations in the new rules — which, if granted, could compromise the very safety standards the norms were meant to protect.

Both pilot bodies stressed that no exemption should dilute safety, and any deviations should be based solely on scientific risk assessment.

Is a Solution in Sight?

While IndiGo says normalcy will return within two days, aviation experts believe that fully stabilising operations could take longer, depending on how quickly the airline can:
•    Re-align rosters
•    Mobilise rested crew
•    Boost staffing
•    Adjust its winter schedule to match regulatory requirements
Passengers are advised to remain prepared for continued delays over the next few days as the airline works through its backlog. 

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
December 4,2025

indigocrisis.jpg

Angry outbursts, long queues, and desperate appeals filled airports across India today as IndiGo grappled with a severe operational breakdown. Hundreds of flights have been cancelled or delayed, leaving thousands of passengers stranded through the night and forcing many to spend long hours at helpdesks.

Social media was flooded with videos of fliers pleading for assistance, accusing the airline of misleading updates, and demanding accommodation after being stuck for 10 to 12 hours at airports such as Hyderabad and Bengaluru.

What Triggered the Meltdown?

IndiGo has attributed the widespread disruption to “a multitude of unforeseen operational challenges.” These include:

•    Minor technology glitches
•    Winter-season schedule adjustments
•    Bad weather
•    Congestion in the aviation network
•    New crew rostering rules (Flight Duty Time Limitations or FDTL)

Among these, the most disruptive has been the implementation of the updated FDTL norms introduced by the Directorate General of Civil Aviation (DGCA) in January 2024.

These rules were designed to reduce pilot fatigue and improve passenger safety. Key changes include:

•    Longer weekly rest periods for flight crew
•    A revised definition of “night,” extending it by an extra hour
•    Tighter caps on flight duty timing and night landings
•    Cutting night shifts for pilots and crew from six per roster cycle to just two

Once these norms became fully enforceable, airlines were required to overhaul rosters well in advance. For IndiGo, this triggered a sudden shortage of crew available for duty, leading to cascading delays and cancellations.

Why IndiGo Was Hit the Hardest

IndiGo is India’s largest airline by a wide margin, operating over 2,200 flights daily. That’s roughly double the number operated by Air India.

When an airline of this size experiences even a 10–20% disruption, it translates to 200–400 flights being delayed or grounded — producing massive spillover effects across the country.

IndiGo also relies heavily on high-frequency overnight operations, a model typical of low-cost carriers that aim to maximise aircraft utilisation and reduce downtime. The stricter FDTL norms clash with these overnight-heavy schedules, forcing the airline to pull back services.

Aviation bodies have also criticised IndiGo’s preparedness. The Airline Pilots' Association of India (ALPA) said airlines were given a two-year window to plan for the new rules but “started preparing rather late.” IndiGo, it said, failed to rebuild crew rosters 15 days in advance as required.

The Federation of Indian Pilots (FIP) went further, calling the crisis the result of IndiGo’s “prolonged and unorthodox lean manpower strategy,” and alleging that the airline adopted a hiring freeze even as it knew the new rules would require more careful staffing.

How Many Flights Are Affected?

In the past 48 hours, over 300 flights have been cancelled. At least 100 more are expected to be cancelled today.

City-wise impact:

•    Hyderabad: 33 expected cancellations; several fliers stranded overnight
•    Bengaluru: over 70 expected cancellations
•    Delhi, Mumbai, Chennai, Kolkata: widespread delays and missed connections

Passengers shared distressing accounts online.

One customer at Hyderabad airport said they waited from 6 PM to 9 AM with “no action taken” regarding their delayed Pune flight. Another said IndiGo repeatedly told them the crew was “arriving soon,” only for the delay to stretch over 12 hours.

IndiGo has apologised for the disruption and promised that operations will stabilise within 48 hours, adding that “calibrated adjustments” are being made to contain the chaos.

What Should Passengers Do Now?

For those flying in the next few days, especially with IndiGo, here are key precautions:

1. Keep Checking Flight Status
Monitor your flight closely before leaving for the airport, as delays may be announced last-minute.

2. Arrive Early
Expect long queues at counters and security due to crowding and rescheduling.

3. Carry Essentials
Pack snacks, water, basic medicines, chargers, and items for children or senior citizens. Extended waiting times should be anticipated.

4. Use Flexible Booking Options
If you booked tickets with a free-date-change or cancellation option, consider using them.
If you haven’t booked yet, prefer refundable or flexible fares, or even consider alternate airlines.

5. Follow IndiGo’s Updates
Keep an eye on IndiGo’s official social media channels and contact customer support for rebooking and refund queries.

What Needs to Change?

Pilot groups have raised concerns not just about staffing but also the planning practices behind it.
The Federation of Indian Pilots accused IndiGo of:

•    Imposing an unexplained hiring freeze despite knowing the FDTL changes were coming
•    Entering non-poaching agreements that limited talent movement
•    Keeping pilot pay frozen
•    Underestimating the need to restructure operations in advance

They have urged DGCA to approve seasonal schedules only after airlines prove they have adequate pilot strength under the new norms.

ALPA also warned that some airlines might be using the delays as an “immature pressure tactic” to push DGCA for relaxations in the new rules — which, if granted, could compromise the very safety standards the norms were meant to protect.

Both pilot bodies stressed that no exemption should dilute safety, and any deviations should be based solely on scientific risk assessment.

Is a Solution in Sight?

While IndiGo says normalcy will return within two days, aviation experts believe that fully stabilising operations could take longer, depending on how quickly the airline can:
•    Re-align rosters
•    Mobilise rested crew
•    Boost staffing
•    Adjust its winter schedule to match regulatory requirements
Passengers are advised to remain prepared for continued delays over the next few days as the airline works through its backlog. 

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.