KUALA BERANG: Kejadian banjir kilat berlaku di Kilometer (km) 393 Lebuh raya Pantai Timur 2 (LPT 2) dari arah Ajil ke Kuantan, yang tular di media sosial pagi tadi surut sepenuhnya.
KUALA BERANG: Kejadian banjir kilat berlaku di Kilometer (km) 393 Lebuh raya Pantai Timur 2 (LPT 2) dari arah Ajil ke Kuantan, yang tular di media sosial pagi tadi surut sepenuhnya.
Ketua Polis Daerah Hulu Terengganu DSP Hasmeera Hassan berkata kejadian kira-kira 11 pagi itu dipercayai berpunca daripada limpahan air cerun berhampiran lokasi berkenaan.
Bagaimanapun, beliau berkata tiada kemalangan atau kejadian tidak diingini berlaku disebabkan insiden tersebut dan jalan di kedua-dua arah masih boleh dilalui kenderaan seperti biasa.
“Air limpahan telah pun surut sekitar 12.30 tengah hari tadi. Tiada penutupan jalan dan masih boleh dilalui oleh semua jenis kenderaan di kedua-dua arah,” katanya dalam kenyataan hari ini.
Menurut Hasmira, ketika ini pihak pengurusan LPT 2 sedang menjalankan kerja-kerja penilaian dan pemantauan di lokasi kejadian.
Dalam video berdurasi 16 saat yang tular di laman media sosial, menunjukkan limpahan air yang turun daripada cerun berdekatan LPT 2 memenuhi laluan lebuh raya tersebut namun kenderaan masih boleh melepasi kawasan Ajil.
Semalam, Jabatan Pengairan dan Saliran (JPS) dalam kenyataan telah memberi amaran mengenai beberapa kawasan di daerah Kuala Terengganu, Besut, Setiu, Hulu Terengganu, Dungun dan Kemaman yang dijangka dilanda banjir mulai hari ini berdasarkan simulasi model ramalan banjir JPS. — AlHijrah Online
Related
Discover more from ALHIJRAH ONLINE
Subscribe to get the latest posts sent to your email.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked