Orobanche Threat to Mustard: How a Parasitic Weed Is Undermining India’s Edible Oil Crop

Orobanche Threat to Mustard

Orobanche Threat to Mustard Latest News

  • Mustard is India’s largest indigenous source of edible oil, cultivated across nearly nine million hectares, mainly in Rajasthan, Uttar Pradesh, Madhya Pradesh, Haryana and West Bengal.
  • However, the crop is increasingly threatened by Orobanche aegyptiaca, a parasitic weed that attaches to mustard roots and siphons off water and nutrients, leading to poor plant growth and reduced seed yields.

How Orobanche Damages the Crop

  • Orobanche attaches itself to mustard roots underground and siphons off water, nutrients and carbon. 
  • This leads to wilting, yellowing, stunted plant growth and ultimately sharp declines in seed yields. 
  • Because the parasite remains hidden below the soil initially, damage is already extensive by the time it becomes visible.

Farmers See Sharp Yield Losses

  • Farmers report steep yield declines despite following recommended control measures. 
  • In Haryana’s Sirsa district, yields have fallen from 9–12 quintals per acre earlier to nearly 6 quintals per acre in recent seasons. 
  • Even herbicide sprays have shown little effect, pushing farmers to reduce mustard acreage in favour of wheat, chickpea and barley.

Why Infestation Is Spreading Fast

  • Each Orobanche plant produces thousands of tiny seeds that can remain viable in soil for up to 20 years and spread through wind and water. 
  • Fields repeatedly planted with mustard are especially vulnerable, as irrigation creates ideal conditions for seed germination and rapid underground attachment to crop roots.
  • The rising infestation has shaken farmer confidence in mustard, traditionally valued for its low irrigation needs. 
  • As Orobanche spreads, many farmers are cutting back on mustard cultivation, raising concerns over future domestic edible oil production.

Why Mustard Matters for India

  • Mustard is India’s most important edible oilseed crop, contributing over 4 million tonnes out of the country’s 10.5–10.6 million tonnes of annual indigenous edible oil production. 
  • It is central to efforts to cut India’s heavy dependence on edible oil imports.
  • Reducing Import Dependence - India imports nearly 16 million tonnes of edible oils every year — mainly palm, soybean and sunflower oil — costing $15.9 billion in 2023–24 and $18.3 billion in 2024–25. 
    • Improving mustard yields is therefore a key national priority to reduce this import bill.
  • Rising Disease and Pest Pressure - Mustard’s increasing vulnerability to Orobanche (margoja), along with pests like aphids and fungal diseases such as white rust, leaf blight, stem rot and powdery mildew, has emerged as a serious concern for productivity and farmer confidence.

Farmers Flag Changing Threat Patterns

  • Farmers report that Orobanche infestation is now appearing earlier in the crop cycle and in fertile soils, unlike earlier when it emerged later and mostly in sandy fields. 
  • This shift signals a growing and more aggressive threat.
  • The buildup of long-lasting Orobanche seed banks in soil has increased the weed’s damage potential, enabling early emergence and greater yield losses. 
  • This has left farmers increasingly uncertain, sowing mustard largely on hope rather than confidence.

Herbicides as a Possible Control Tool

  • Chemical control using herbicides such as glyphosate is one possible way to tackle Orobanche. 
  • However, this approach has major limitations with conventional mustard varieties.

Why Conventional Herbicides Don’t Work

  • Glyphosate and similar broad-spectrum, non-selective herbicides kill all plants by blocking the EPSPS (5-enolpyruvylshikimate-3-phosphate synthase) enzyme essential for protein formation. 
  • Applied to normal mustard, they destroy the crop along with the weed. 
  • At currently recommended low doses, they are also ineffective against Orobanche.

Role of Herbicide-Resistant Mustard

  • A new approach lies in breeding mustard varieties that can tolerate specific herbicides. 
  • Farmers are testing a hybrid mustard that is resistant to imidazolinone herbicides, allowing selective control of Orobanche without harming the crop.
  • The hybrid ‘Pioneer-45S42CL’ can tolerate imazapyr and imazapic herbicides.
  • Sold with a compatible herbicide formulation, it requires a single spray after 25 days of sowing and has shown encouraging early results in farmers’ fields.

GM Mustard as a Future Option

  • Researchers have also developed GM mustard lines resistant to glyphosate and other herbicides, offering multiple chemical options and reducing the risk of resistance buildup.
  • Given mustard’s strategic importance and the rising weed threat, policymakers face a critical decision on permitting GM crops. 
  • Any decision, experts argue, should be guided by science and farm economics rather than ideology.

Source: IE

Orobanche Threat to Mustard FAQs

Q1: What is the Orobanche threat to mustard crops?

Ans: The Orobanche threat to mustard comes from a parasitic weed that attaches to roots, stealing water and nutrients, causing stunted growth and heavy yield losses.

Q2: Why is the Orobanche threat to mustard hard to detect early?

Ans: The Orobanche threat to mustard remains underground initially, and by the time shoots appear above soil, irreversible crop damage has already occurred.

Q3: Why is the Orobanche threat to mustard spreading rapidly?

Ans: The Orobanche threat to mustard spreads due to long-lived soil seed banks, repeated mustard cultivation, irrigation-triggered germination, and wind- and water-based seed dispersal.

Q4: Why does the Orobanche threat to mustard matter for India’s economy?

Ans: The Orobanche threat to mustard endangers India’s biggest edible oil crop, risking higher import dependence and undermining efforts to reduce the edible oil import bill.

Q5: How are farmers tackling the Orobanche threat to mustard?

Ans: Farmers are testing herbicide-resistant mustard hybrids and selective herbicides, while scientists explore GM mustard lines to manage the Orobanche threat to mustard sustainably.

Indian Telecom Security Assurance Requirements (ITSAR) – India’s Proposed Smartphone Security Regime

ITSAR

ITSAR Latest News

  • The Union Government is considering legally enforcing Indian Telecom Security Assurance Requirements (ITSAR) for smartphones, involving 83 security standards, including source code disclosure, software controls, and user-permission restrictions.
  • This has triggered strong resistance from global smartphone makers like Apple (5% market share in India), Samsung (15%), Google, and Xiaomi (19%), who argue that many provisions lack global precedent and threaten proprietary technologies.

Background

  • India is the world’s second-largest smartphone market with nearly 750 million users.
  • Rising online fraud, cybercrime, and data breaches have prompted the government to strengthen device-level security.
  • The proposals align with the Indian PM’s broader push for digital security and data sovereignty.
  • Similar tensions have emerged earlier over mandatory cyber safety apps (later revoked), and stringent testing norms for security cameras due to national security concerns.

Key Features of the Proposed Security Standards

  • Source code disclosure:
    • Manufacturers must submit proprietary source code for review and vulnerability analysis by government-designated labs.
    • Objective: Detect backdoors and systemic vulnerabilities.
    • Industry response:
      • The Manufacturers’ Association for Information Technology (MAIT) calls it “not possible” due to corporate secrecy and privacy norms.
      • No such requirement exists in the EU, North America, Australia, or Africa.
  • Background permission restrictions:
    • Apps cannot access camera, microphone, or location in the background. Mandatory continuous status-bar alerts when permissions are active.
    • Concern: No global precedent or standardized testing method.
  • Permission review alerts: Devices must periodically prompt users to review app permissions. Industry wants alerts limited to “highly critical” permissions to avoid user fatigue.
  • One-year log retention:
    • Phones must store security audit logs (logins, app installs) for 12 months.
    • Industry concern: Consumer devices lack sufficient storage capacity.
  • Periodic malware scanning: Mandatory automatic malware scans. Concerns: Battery drain, slower device performance, etc.
  • Removal of pre-installed apps: All non-essential pre-installed apps must be removable. Companies argue many apps are integral system components.
  • Mandatory notification of software updates:
    • Manufacturers must inform the National Centre for Communication Security before releasing major updates or patches.
    • Industry view: This will be impractical during zero-day vulnerabilities. Delays may increase user exposure to active cyber threats.
  • Tamper detection (Rooting/Jailbreaking): Devices must detect tampering and show persistent warnings. Industry response: No reliable universal detection mechanism exists.
  • Anti-rollback protection: Blocking installation of older software versions, even if manufacturer-signed.
  • Concern: No global standard; may restrict legitimate use cases.

Key Challenges and Way Ahead

  • Data Security vs proprietary rights: Risk of exposing trade secrets. Risk-based regulation focusing on critical vulnerabilities rather than blanket controls.
  • Lack of global precedent: Potential regulatory overreach. Adopt global best practices aligned with OECD and EU cybersecurity norms.
  • Ease of doing business: Compliance costs may deter investment. Ensure time-bound clearance mechanisms for security updates. Strengthen user-level security awareness alongside device-level controls.
  • Operational practicality: Update delays, battery drain, storage constraints. Explore independent third-party audits instead of direct source code disclosure.
  • Innovation chill: Excessive regulation may impact R&D. Maintain a balance between national security, privacy, and innovation.

Conclusion

  • India’s proposed smartphone security framework (ITSAR) reflects legitimate concerns over cybersecurity, data protection, and national security in a rapidly digitising economy. 
  • However, enforcing intrusive measures like source code disclosure without global precedent risks undermining innovation, trust, and market competitiveness. 
  • A consultative, proportionate, and globally harmonised approach is essential to safeguard users while preserving India’s attractiveness as a major digital and manufacturing hub.

Source: TH | ET

ITSAR FAQs

Q1: What is the rationale behind India’s proposal to mandate source code disclosure by smartphone manufacturers?

Ans: To enhance national cybersecurity and data sovereignty by identifying vulnerabilities and preventing exploitation.

Q2: Why have global smartphone manufacturers opposed India’s proposed ITSAR?

Ans: They argue that measures like source code review, malware scanning are operationally impractical.

Q3: How do India’s proposed smartphone security norms raise concerns related to Ease of Doing Business?

Ans: Mandatory disclosures, compliance costs, may discourage investment and innovation in India’s digital ecosystem.

Q4: What is the significance of background permission restrictions in the proposed smartphone security framework?

Ans: They aim to protect user privacy by preventing unauthorised background access to location services, thereby reducing cyber misuse.

Q5: How can India address cybersecurity concerns without hampering technological innovation?

Ans: India should adopt a risk-based, consultative, and globally aligned cybersecurity framework.

Age of Consent in India – Law, Adolescent Autonomy, and Child Protection

Age of Consent

Age of Consent Latest News

  • The Supreme Court has flagged the misuse of the POCSO Act in consensual adolescent relationships, reopening the debate on India’s age of consent. 

Legal Framework Governing the Age of Consent in India

  • The age of consent refers to the legally defined age at which an individual is considered capable of giving valid consent for sexual activity. 
  • In India, this age is 18 years, as stipulated under the Protection of Children from Sexual Offences (POCSO) Act, 2012, which classifies anyone below 18 as a “child.” 
  • Consequently, any sexual activity involving a minor is treated as statutory rape, irrespective of consent.
  • This position was reinforced by the Criminal Law (Amendment) Act, 2013, which aligned Section 375 of the Indian Penal Code with the POCSO threshold. 
  • The Bharatiya Nyaya Sanhita (BNS), 2023, has retained this framework, reaffirming that consent is legally irrelevant if the individual is below 18.
  • Historically, India’s age of consent has evolved from 10 years (IPC, 1860) to 12 years (1891), then 14 and 16 years, before being raised to 18 years in 2012
  • It is distinct from the minimum age of marriage, which is 18 years for women and 21 years for men under the Prohibition of Child Marriage Act, 2006.

Arguments Supporting a Review of the Age of Consent

  • A key driver of the current debate is the sharp rise in POCSO cases involving adolescents aged 16-18 years, often arising from consensual romantic relationships. 
  • In many such cases, the minor involved testifies that the relationship was voluntary, yet the law mandates criminal prosecution.
  • Empirical data strengthen this concern. The NFHS-4 (2015-16) indicates that 39% of girls reported sexual debut before the age of 18. 
  • Further, studies by civil society organisations analysing thousands of POCSO judgments show that nearly one-fourth of cases involve consensual adolescent relationships, with a large majority of victims refusing to testify against the accused.
  • Supporters of reform argue that the current law fails to acknowledge adolescent sexuality and autonomy, leading to the criminalisation of normal teenage relationships. 
  • They point out that the original intent of POCSO was to combat sexual abuse and exploitation, not to penalise peer relationships. 
  • Many also cite international practices, where several countries fix the age of consent at 16 years, often coupled with “close-in-age” or “Romeo-Juliet” exemptions to prevent misuse.

Concerns Against Lowering the Age of Consent

  • Opponents of lowering the age of consent emphasise that the existing bright-line rule provides an unambiguous and uniform standard for child protection. 
  • Any dilution, they argue, risks creating loopholes that could be exploited by traffickers, abusers, and those in positions of trust.
  • Evidence suggests that child sexual abuse is frequently perpetrated by known persons, family members, neighbours, teachers, or caregivers. 
  • A Ministry of Women and Child Development study (2007) found that over 50% of abusers were known to the child, raising concerns that claims of consent in such contexts may mask coercion or manipulation.
  • Parliament has consistently upheld this protective approach. 
  • Multiple parliamentary committees and the Law Commission of India (283rd Report, 2023) have warned that reducing the age of consent could weaken POCSO and undermine efforts against child marriage, trafficking, and exploitation.

Judicial Responses and Emerging Nuances

  • Courts have increasingly struggled to balance the letter of the law with the real-life consequences of its application. 
  • While several High Courts have acknowledged the need to view consensual adolescent relationships differently, they have also reiterated that, under POCSO, consent of a minor has no legal validity.
  • The Supreme Court has reaffirmed this position, even while exercising extraordinary powers in select cases to mitigate harsh outcomes. 
  • Recent judicial observations suggest growing recognition of the trauma caused when consensual relationships are prosecuted, but without altering the statutory framework.

Way Forward

  • The debate underscores the need for a calibrated legal response, rather than a binary choice between protection and autonomy. 
  • Many experts advocate limited close-in-age exemptions for adolescents aged 16-18, combined with judicial oversight to detect coercion or abuse.
  • Beyond legal reform, long-term solutions lie in comprehensive sex education, accessible adolescent health services, and gender-sensitive policing. 
  • Strengthening social support systems can reduce misuse of the law while ensuring that genuine cases of abuse are addressed effectively.

Source: TH

Age of Consent FAQs

Q1: What is the current age of consent in India?

Ans: It is 18 years under the POCSO Act and the Bharatiya Nyaya Sanhita.

Q2: Why has the age of consent debate resurfaced?

Ans: Due to rising POCSO cases involving consensual adolescent relationships.

Q3: Does Indian law recognise consent of minors?

Ans: No, consent of anyone below 18 is legally invalid.

Q4: What are ‘close-in-age’ exemptions?

Ans: Legal provisions that protect consensual relationships between adolescents close in age.

Q5: Who has the authority to change the age of consent?

Ans: Parliament has exclusive legislative authority to amend the law.

Fog-Induced Disruptions in India: How Railways and Airlines Manage Winter Delays

Fog-Induced Disruptions

Fog-Induced Disruptions Latest News

  • Every winter, dense fog—especially in northern India—disrupts travel plans, causing delays and cancellations across rail and air networks. 
  • Low visibility affects safety and scheduling, forcing operators to slow down or halt services.
  • Indian Railways faces severe congestion during foggy periods, with cascading delays and cancellations. 
  • To mitigate risks, it equips loco pilots with fog safety devices and is investing in improved fog-related technologies, while prioritising safety over speed.
  • Airlines have managed fog better through advanced navigation technology and specialised operating procedures. 
  • However, surging passenger volumes mean that even brief disruptions can trigger widespread knock-on delays across airports and flight schedules nationwide.

Why Fog Lingers Over North India

  • Northern India is mainly affected by radiation fog, which forms on clear winter nights when the ground cools rapidly, moisture condenses, and calm winds trap the fog near the surface. 
  • This leads to frequent episodes of extremely low visibility that disrupt train and flight operations.
  • Air pollution worsens the problem. Smog mixes with fog, making it denser, lowering it closer to ground level, and prolonging poor visibility even after sunrise. 
  • High pollution levels, especially around Delhi, have increasingly intensified and extended fog-related disruptions over the years.

How Flights Operate in Low-Visibility Conditions

  • Low Visibility Procedures (LVP) - When dense fog sharply reduces visibility, airports activate Low Visibility Procedures. These include Low Visibility Take-Offs and precision landings using advanced navigation aids.
  • Instrument Landing System (ILS) CAT IIIB – ILS, a ground based radio navigation system, provides pilots with accurate horizontal and vertical guidance during landing. CAT IIIB, one of the highest precision categories, allows landings with visibility as low as 50 metres.
  • Limited Airport and Aircraft Capability - Only select Indian airports, most notably Delhi, are equipped for CAT IIIB operations. 
    • Airports without such systems must resort to delays or cancellations during heavy fog. 
    • Aircraft and flight crew also require specific certification to operate under CAT IIIB conditions.
  • Airline Preparedness - Airlines plan rosters to ensure enough CAT IIIB-trained pilots and crew are available at fog-prone airports. They also position CAT IIIB-certified aircraft at these hubs to reduce disruption.
  • Forecasting and Regulation - The aviation regulator has designated December 10 to February 10 as the official fog season. Airlines and airports rely on real-time weather data, predictive analytics, and AI-based tools to anticipate fog and manage operations more efficiently.

Why Fog-Related Flight Disruptions Cannot Be Fully Avoided

  • Safety Limits Under Low Visibility Procedures - Even with Low Visibility Procedures in place, operations slow down significantly. Aircraft need greater spacing during take-offs and landings, which reduces overall airport capacity.
  • Reduced Airport Throughput - In dense fog, major hubs like Delhi see hourly aircraft movements drop sharply. Recovery from even one hour of fog can take two to three hours, creating cascading delays.
  • Ground Movement Constraints - Taxiing between runways and terminals becomes much slower in poor visibility, adding to congestion and delaying both arriving and departing flights.
  • Mismatch Between Landing and Take-Off Visibility - CAT IIIB landings can occur at lower visibility than take-offs. This can cause arriving aircraft to pile up while departures remain grounded, leading to parking congestion and diversions.
  • Visibility Below Operational Thresholds - If visibility falls below 50 metres, even CAT IIIB operations may be suspended, forcing a halt to landings until conditions improve.
  • Flight Diversions and Alternate Airports - Airlines plan fair-weather alternate airports for diversions during fog. Final diversion decisions depend on real-time weather and the availability of engineering support at alternate locations.

How Indian Railways Manages Train Operations During Fog

  • Dense winter fog in northern India causes severe train delays, sometimes exceeding 12 hours. 
  • Safety concerns make fog management a critical operational priority for Indian Railways.

Fog Safety Devices for Loco Pilots

  • Indian Railways uses Fog Safety Devices (FSDs)—GPS-based handheld tools that give audio-visual alerts to drivers about signals, stations, crossings, and obstacles in geo-fenced areas.
  • In December 2025, 25,939 FSDs were deployed, with around 23% allocated to Northern Railway, the most fog-prone zone.

Modified Signalling to Reduce Risk

  • To prevent congestion and accidents during fog, Northern and North Central Railways use modified automatic signalling, limiting train movement to two trains between stations. Luminous strips on signals improve visibility.

Kavach: Automatic Train Protection System

  • Indian Railways is rolling out Kavach, its Automatic Train Protection (ATP) system, which displays signal information inside the locomotive cabin and automatically applies brakes if needed. 
  • This allows safer operations even in dense fog.
  • The advanced Kavach 4.0 has been commissioned on 738 route km, covering key sections of the Delhi–Mumbai and Delhi–Howrah high-density corridors. 

Source: IE | ToI

Fog-Induced Disruptions FAQs

Q1: What causes fog-induced disruptions in India every winter?

Ans: Fog-induced disruptions in India are caused by radiation fog, stagnant winds, and high pollution, especially in northern regions, leading to extremely low visibility conditions.

Q2: How do airlines handle fog-induced disruptions in India?

Ans: Airlines manage fog-induced disruptions in India through Low Visibility Procedures, CAT IIIB landings, trained pilots, certified aircraft, and predictive weather technologies.

Q3: Why are fog-induced disruptions in India unavoidable for flights?

Ans: Fog-induced disruptions in India slow aircraft movements, reduce runway capacity, and limit ground visibility, causing cascading delays even at technologically advanced airports.

Q4: How does Indian Railways manage fog-induced disruptions in India?

Ans: Indian Railways tackles fog-induced disruptions in India using fog safety devices, modified signalling systems, luminous markers, and the Kavach automatic train protection system.

Q5: Why do fog-induced disruptions in India cause network-wide delays?

Ans: Fog-induced disruptions in India create cascading effects because trains and aircraft operate in interconnected networks, where one delay quickly impacts multiple routes and schedules.

Enquire Now