Fog disrupts over 100 flights in New Delhi

December 25, 2012

fog

New Delhi, December 25: Dense fog continue to wreak havoc on the operations at the Indira Gandhi International Airport here for the third consecutive day and led to delay of over 100 flights, diversion of seven and cancellation of 10 others.

Schedules of over 100 flights were badly affected after dense fog enveloped the airport late last night and early this morning.

The flights were delayed from half an hour to five hours and some of them had to be cancelled, causing inconvenience to the passengers, airport officials said.

Fog started to descend at the airport around 10 PM yesterday but the runway visibility was fine and flight operations were normal.

But the situation started to deteriorate around 11.21 PM when visibility dropped to 50 metres on the third runway (29/11). However, the visibility was around 800 metres on the main runway (28/10) and, therefore, flight operations went on unhindered on it, they said.

Fog became more dense around 12.30 AM, when the visibility on the main runway also dropped to 50 metres while that on the third runway was below 50 metres, which brought the flight operations to a standstill.

A total of seven (six domestic and one international) flights were diverted to nearby airports like Jaipur, Ahmedabad and others, the officials said. The visibility started to increase after 1.30 AM on the main runway and flights began taking off as and when the conditions were right, they said, adding the flights arriving here were using instrument landing system (ILS).

The visibility at one end of the third runway remained zero till almost 5.30 AM.

A total of 138 domestic and international flights arrived assisted by various category of ILS. 69 flights with CAT-I (when visibility is upto 550 m), 19 flights with CAT-II (when visibility was between 550 and 300 me), 30 flights with CAT-IIIA (when visibility was between 300 and 200 m) and 20 flights with CAT-IIIB (visibility between 200 and 50 m), an airport official said.

Yesterday around 140 flights were affected due to dense fog.

MeT department has predicted that the runway visibility is likely reduce to 500 metres in shallow fog by 11.30 PM and it may further reduce to below 200 metres in dense fog from 3.30 AM tomorrow.

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.
Agencies
February 4,2020

New Delhi, Feb 4: Four-month-old Mohammed Jahaan accompanied his mother almost every day to the Shaheen Bagh demonstration where he was a favourite with the protesters who would take turns to hold him and often draw the tricolour on his cheeks.

Jahaan will not be seen at Shaheen Bagh anymore. He died last week after acquiring a severe cold and congestion following exposure to the winter chill at the outdoor demonstration. His mother is, however, undeterred and determined to participate in the protests, saying it is "for the future of my children".

The infant's shattered parents, Mohammed Arif and Nazia, live in a tiny shanty put together with plastic sheets and cloth in Batla House area and have two other children -- a five-year-old daughter and a one-year-old son.

Hailing from Bareilly in UP, the couple is barely able to make ends meet. Arif is an embroidery worker and also drives an e-rickshaw. His wife helps him in his embroidery work.

"I haven't been able to earn enough in the last month despite driving the battery rickshaw in addition to my embroidery work. Now with our baby's demise, we have lost everything," he said, showing a picture of little Jahaan wearing a woolen cap that read 'I Love My India'.

A visibly disturbed Nazia said Jahaan passed away in his sleep on night of January 30 after returning from the protests.

"I had returned from Shaheen Baag at around 1 AM. After putting him and other kids to sleep, even I went to sleep. In the morning, I suddenly found him motionless. He was gone in his sleep," she said.

The couple said they took their motionless baby to the nearby Alshifa Hospital on the morning of January 31 where he was declared dead on arrival.

Nazia, who had been visiting the Shaheen Bagh demonstration everyday with Jahaan since December 18, says that he died after catching a cold that turned lethal.

She said she didn't realise that his congestion was so severe. However, the baby's death certificate issued by the hospital does not mention any specific reason for the death.

Shazia, a neighbour who was present at the couple's home, said Nazia had fought with her mother and husband to visit Shaheen Bagh everyday. Nazia would gather all women in the bylane outside her house so that they could together walk to the demonstration, around 2 km away. Sometimes, Arif would drop some of them to Shaheen Bagh on his e-rickshaw.

Nazia said she strongly feels that the CAA and NRC are against the welfare of all communities and will join the Shaheen Bagh protests, but this time without her children.

"Why was I doing this? For my children and the children of all us who need a bright future in this country," she told PTI.

"The CAA divides us on religion and should never be accepted. I don't know if there is politics involved but I know that I must question what is against the future of my children."

Arif, however, blamed the NRC and CAA for his child's death.

"Had the government not brought CAA and NRC, people would not have protested and my wife would not have joined them, my son would have been alive," he said.

Comments

Angry Indian
 - 
Tuesday, 4 Feb 2020

inna lillahi inna ilaihi rajioon...so sad

 

Modi, delhi police and Amith Shah the biggest EVIL of india is responsible for this samll soul death...

 

you have to answer one day after you die...dont think this world is permenant..

 

you will never see heaven forever...you must root in hell

 

GADDAR PM & HM

 

Jai Hind

 

 

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
July 1,2020

Patna, July 1: A wedding ceremony in rural Patna a fortnight ago where the groom was running high fever, two days before he died and his body cremated without being tested for COVID 19, appears to have set off the biggest infection chain in Bihar so far, health department officials said on Tuesday.

More than 111 people have tested positive in Paliganj sub-division of Patna district, about 55 km from the state capital, in the last few days, out of over 350 who have been tested upon contact tracing, they said. Fifteen of his relatives who attended the wedding tested positive for the contagion and apparently infected others.

The officials, who requested anonymity, said the groom was a software engineer based in Gurugram and had returned home for his marriage in the last week of May. A few days after the ''tilak'' ceremony, he started showing symptoms of the disease.

On June 15, the date of wedding, he was running high fever and wanted the ceremony to be deferred, but relented upon the insistence of family members who made him swallow paracetamol tablets and go through the rituals.
On June 17, his condition deteriorated significantly and family members made a dash to AIIMS, Patna, but he died on the way.

The body was cremated in a huff, without the authorities being informed. But somebody telephoned the district magistrate and narrated the whole episode. All close relatives of the deceased, who attended the ceremony, were tested on June 19. Of them 15 tested positive, the officials said.

As a measure to contain the spread of the disease, a special camp was set up at the village where the marriage took place on June 24-26 during which samples of 364 people were collected. Of them, 86 tested positive, the officials added.

The sudden explosion of the dreaded coronavirus has triggered panic in the area. Although most who tested positive were asymptomatic, they have been admitted to isolation centres in Bihta and Phulwarisharif.

Block Development Officer Chiranjeev Pandey said Meetha Kuan, Khagari Mohalla and parts of Paliganj Bazaar have been sealed for thorough sanitisation.

Patna district happens to be the worst-affected in Bihar with 699 confirmed cases till date and five casualties, according to figures provided by the administration. The number of active cases is 372.

On Monday, when the state witnessed its biggest single day spike with 394 cases, Patna district accounted for more than 20 per cent of these. About eighty cases were reported from Paliganj alone.

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.
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.