﻿<?xml version="1.0" encoding="utf-8"?>
<!--<!DOCTYPE nitf SYSTEM "nitf-3-4.dtd">-->
<nitf>
  <head>
    <title id="Title">#Title</title>
    <docdata management-doc-idref="">
      <date.issue id="CreationDate" norm="" />
      <du-key id="rev-ver" generation="1" version="Default" />
      <du-key id="Parent-Version" version="" />
      <identified-content>
        <classifier id="newspro-nitf" value="r2" />
        <classifier id="Newspro-App" value="Epaper" />
        <classifier id="Content-Type" value="Story" />
        <classifier id="storyID" value="" />
        <classifier id="CmsConID" value="" />
        <classifier id="Desk" value="" />
        <classifier id="Source" value="" />
        <classifier id="Edition" value="" />
        <classifier id="Category" value="-1" />
        <classifier id="UserName" value="" />
        <classifier id="PublicationDate" value="11/09/2026" />
        <classifier id="PublicationName" value="HI" />
        <classifier id="IsPublished" value="Y" />
        <classifier id="IsPlaced" value="Y" />
        <classifier id="IsCompleated" value="N" />
        <classifier id="IsProofed" value="N" />
        <classifier id="User" value="" />
        <classifier id="Headline-Count" value="" />
        <classifier id="Slug-Count" value="0" />
        <classifier id="Photo-Count" value="0" />
        <classifier id="Caption-Count" value="0" />
        <classifier id="Word-Count" value="0" />
        <classifier id="Character-Count" value="0" />
        <classifier id="Location" value="" />
        <classifier id="TemplateType" value="1" />
        <classifier id="StoryType" value="Story" />
        <classifier id="Author" value="" />
        <classifier id="UOM" value="mm" />
        <classifier id="NumCol" value="0" />
        <classifier id="kicker" value="" />
        <classifier id="ByLine" value="" />
        <classifier id="DateLine" value="" />
        <classifier id="box-geometry" value="619,791,955,1241" />
        <classifier id="Layer" value="Default" />
        <classifier id="numcol" value="3" />
        <classifier id="ArticleStyle" value="" />
        <classifier id="Epaper-Build" value="7.96.0.0" />
        <classifier id="ProcessingDateTime" value="Thu Sep 10 2026 23:44:25 GMT+0530" />
      </identified-content>
      <urgency id="home-page" ed-urg="0" />
      <urgency id="priority" ed-urg="0" />
      <doc-scope id="scope" value="0" />
    </docdata>
    <pubdata type="print" name="HI" date.publication="20260911T000000+5.30" edition.name="VSP" edition.area="VSP" position.section="11MAIN05FVSP" position.sequence="5" ex-ref="11MAIN05FVSP.indd" />
  </head>
  <body boxBorderWeightColor="" boxBorderWeight="">
    <body.head>
      <hedline>
        <hl1 id="Headline1" class="1" style="Headline1">
          <lang class="3" style="Headline1" font="Chronicle Display" fontStyle="Roman" size="40">Jumbo dies after being hit by light engine</lang>
        </hl1>
      </hedline>
    </body.head>
    <body.content id="Bodytext" CaptionAsBody="0">
      <block>
        <media id="1" media-type="image">
          <media-reference id="tn" source-credit="" data-location="1" source="Elephantdies_5_VSP_tn.jpg" Units="pixels" width="50" height="50"></media-reference>
        </media>
      </block>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">C B Singh
Rayagada</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">A male elephant was killed by a train near Brundabadi village in Rayagada district’s Bissam Cuttack block on September 9 night. The incident has raised serious questions about how effectively the Forest department tracks elephant movements and communicates alerts to the railway system.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">Forest officials are investigating the elephant’s death and performing a standard post-mortem examination. Meanwhile, serious questions have been raised about whether the elephant’s presence on the railway tracks was detected and reported to train authorities in time.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">The local station master said a light engine passed through the area at around 10.45 pm with no prior elephant movement warnings from the Forest department. This lack of communication raises a critical question: Was there any advance indication that an elephant was approaching the tracks? Railway tracks near elephant habitats are high-risk zones where preventing collisions requires constant field surveillance, identifying vulnerable areas, and quick coordination between forest and railway officials.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">The Forest department’s press release omits whether the Brundabadi stretch was a known elephant corridor, if recent movements were recorded, or if railway authorities received warnings before the train passed. It is unclear if the department monitored night-time elephant movements along the track or if forest staff routinely alerted railway authorities. Advance warning is critical, as train crews have almost no time to react to animals on the tracks at night.</lang>
      </p>
    </body.content>
  </body>
</nitf>