Responsibility of the Russian Federation for Shooting Down a Malaysian Passenger Aircraft on 17th July 2014
Bibliographic record
Abstract
On 17 July 2014, Malaysia Airlines Flight MH17 from Amsterdam to Kuala Lumpur was shot down over Eastern Ukraine. On board Boeing 777 there were 283 passengers and 15 crew members who all lost their lives. The victims’ families and the states whose citizens were lost now seek remedies from those that are responsible for this tragedy. This paper discusses the incident of MH17 which took place in Western Ukraine. This paper uses the analytical approach method applied in legal research with the aims of answering the question presented in the paper. The MH17 incident also brings us many international legal issues, therefore it was necessary to examine the challenges of holding persons responsible for the MH17 tragedy and especially the supplier of the anti-aircraft missile that was used. It then considers international law’s capacity for preventing recurrences of this tragedy by constraining non-state actors’ access to anti-aircraft missiles. Under the doctrine of state responsibility, the Netherlands and/or Malaysia may be able to bring a case before the ICJ for violations of international law and internationally wrongful acts attributable to Russia and/or Ukraine. It seems that that Russia and Ukraine may have violated their obligations under the civil aviation conventions to communicate information, to investigate the situation and allegations against potential perpetrators, and to prosecute or extradite those that may be responsible. One of the two conclusions that could be drawn upon this paper is that not only Russia could be held responsible but also Ukraine is partly accountable for the tragedy. Based on both national and international legislation, it can be argued that Ukraine has a duty to protect foreigners legally passing through its airspace, which could form the legal ground for a case in Ukraine against the state. Second, a civil suit against the airlines could be brought before a court in several states based on Chicago and Montreal Conventions.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.006 | 0.002 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".