Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the gotmls domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170
Kes Kematian Askar Akan Disiasat CID – Ayob Khan – Independent

Independent

Kes Kematian Askar Akan Disiasat CID – Ayob Khan

—

by

Admin
in
   
Reading Time: < 1 minute

JOHOR BAHRU | Polis akan menjalankan siasatan menyeluruh berkait kematian seorang askar yang dikatakan melompat dari tingkat tiga bangunan kediaman di sebuah kem tentera di Batu Pahat pada 29 Ogos.

Ketua Polis Johor, Datuk Ayob Khan Mydin Pitchay berkata, kes itu juga kini disiasat oleh Jabatan Siasatan Jenayah Johor (CID).

“Sebelum ini, kes tersebut diklasifikasikan sebagai laporan kematian mengejut tetapi sekarang ia telah diambil alih dan berada di bawah pengurusan CID Johor,” katanya ketika dihubungi di sini, pada Selasa.

Ayob Khan berkata demikian ketika diminta mengulas dakwaan bahawa askar itu dianiaya dan dibuli sebelum ini.

Semalam, Timbalan Ketua Polis Daerah Batu Pahat, Suprintendan Muhammad Izzudin Runggai, melalui satu kenyataan, mengatakan askar itu mengalami kecederaan parah di kepala dan dirawat di unit rawatan rapi (ICU) Hospital Sultanah Nora Ismail (HSNI) di Batu Pahat.

Dia disahkan meninggal dunia pada 6 Sept ketika masih menjalani rawatan di ICU.

Pada masa yang sama, Muhammad Izzudin mengatakan polis akan menentukan kesahihan tuntutan oleh ahli keluarga mangsa bahawa ada kemungkinan mangsa dianiaya dan dibuli ketika berada di kem sebelum kejadian.

Sebelum ini, berita mengenai askar itu tersebar di media sosial.