Significance
2 measured / 2 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 2 events
Connected Situation / Through 2026-10-27
M/V June Aster Fire and Aftermath
- stories
- 24
- events
- 2
- entities
- 45
- connections
- 24
Frozen through 2026-10-27 UTC · published 2026-10-27 17:25 UTC · analysis as of 2026-10-26 20:27 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On 9 September, “Ferry fire kills five off Palawan” reported five deaths in a fire off Palawan. On 10 September, one headline reported five dead and 87 missing off Palawan, while another reported five dead and 86 missing. The linked coded Event assigns Norway, which conflicts with the headline’s location. A 12 September headline reported 35 deaths, while another dated the same day reported 76 deaths and 13 missing; a 14 September report again gave 76 deaths and 13 missing, followed by a 16 September report of 77 deaths. These were differing reported tallies, not a single consistent count. On 16 September, the Philippine Coast Guard collected oily water from the M/V June Aster in Coron, according to the Event dated that day. Later headlines attributed the fire to flammable cargo and lithium batteries, while another said a chemical spill may have triggered it. The Philippine Coast Guard complaint against the captain and a reported halt of work on six vessels added investigative and regulatory follow-up.
Footnotes[15][14][16][12][11][9][17][6][4][2][5][1]Assessment
The central thread is a deadly ferry fire followed by recovery, casualty-identification, environmental, investigative and regulatory accounts; the headlines establish reported actions and figures, not a final casualty tally. The 10 September headline places the fire off Palawan, but its linked Event assigns Norway, so that Event does not establish the incident’s location. MARINA’s cargo and lithium-battery explanations remain attributed claims, while the chemical-spill account is explicitly qualified as a possibility; none establishes a definitive cause. The Coast Guard complaint headline establishes a reported filing, not a legal finding, and the six-vessel halt headline does not establish its precise legal basis. Before-and-after snapshots show matching fields for the Event entries and story records presented as revisions since the prior analysis.
Footnotes[15][12][11][9][3][1][14][16][6][4][2][5]Explanation originally captured 2026-10-26 · Evidence through 2026-10-27 UTC · Source edition sed_664724f611c16f3b38bbf78ef8bd794d
What informs this explanation
- Complete retained Story and Event membership
- Daily reporting and coded-occurrence time steps
- Event taxonomies, metrics, units, and denominators
- Canonical Entities and recorded actor/target bindings
- Typed reporting, membership, and incident edges
- Changes against the preceding retained edition
- Permitted macro, public-record, and asset facts only when they were retained with an explicit source and observation date
Quantitative
Evidence in numbers
- Scope
A 41-day Situation represented by 2 coded Events carried across 24 member Stories.
- Coded activity
The coded activity is led by EN04 · Environmental Pollution Event (1) and IN02 · Transport Disruption (1).
- Prominent subjects
Philippine Coast Guard is prominent in the retained actor and relationship evidence.
- Entity coverage
45 canonical Entities are linked to this edition.
Metric coverage. 2 coded Events · 2 CAMEO+ · 0 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude3.5
min 3max 4
Systemic importance0.13
min 0.1max 0.15
Propagation potential0.31
min 0.24max 0.38
Market sensitivity0.05
min 0.05max 0.05
Dot = mean · shaded span = observed range · position uses each metric’s defined scale.
All 6 scores, distributions & definitions
How the coder scored the full retained Event set
2 coded events — 2 CAMEO+
- Significance · 20.28min 0.23max 0.33
- Magnitude · 23.5min 3max 4
- Systemic · 20.13min 0.1max 0.15
- Propagation · 20.31min 0.24max 0.38
- Market · 20.05min 0.05max 0.05
- Confidence · 20.55min 0.32max 0.78
No conflict-family event here, so nothing carries a fatality count — a missing column, not a toll of zero. 2 sit outside POLITICAL, where Goldstein and quad class are undefined.
Magnitude
2 measured / 2 eligible · 0 missing · 0 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across all 2 events — every one of them CAMEO+
Systemic
2 measured / 2 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 2 events — every one of them CAMEO+
Propagation
2 measured / 2 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 2 events — every one of them CAMEO+
Market
2 measured / 2 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 2 events — every one of them CAMEO+
Confidence
2 measured / 2 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 2 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day17 reporting days · click a day to open or close it
2026-10-19from the recordslatest
Philippines halts work on six vessels after deadly ferry fire
1 Story and 0 coded Events (0 / 0 against the day before). Widest coverage: Philippines halts work on six vessels after deadly ferry fire (2 articles).
- 10
- Stories · vs day before
- 00
- Events · vs day before
- 2
- articles
The lay of the land
Situation timeline
Threads
All 17 daysarticlesstoriesevents
09-0909-1209-1509-2410-0310-19
Loading Situation timeline…
What kind of event · 2 coded types
over 2 coded events on this edition
- Environment1
- EN04 · Environmental Pollution Event1
- Infrastructure1
- IN02 · Transport Disruption1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystCasualty reports and missing-person figures
Headlines give early death and missing-person figures, followed by higher death tolls and a later report of eight missing.
- development
AnalystSearch, victim identification and environmental response
Headlines report a search for eight more victims and identification of 50 victims; the Event describes the Coast Guard collecting oily water.
- development
AnalystReported explanations of the fire
MARINA headlines attribute the fire to flammable cargo and lithium batteries; another headline says a chemical spill may have triggered it.
- development
Key actors
- PC
Key Events
contextAnalystPhilippine Coast Guard collects oily water from June Aster
Dated 16 September, this Event names the Philippine Coast Guard collecting oily water from the M/V June Aster in Coron.
Dated 16 September, this Event names the Philippine Coast Guard collecting oily water from the M/V June Aster in Coron.
Footnotes[17]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
The Event names the Philippine Coast Guard as the actor collecting oily water. · recorded participationAnalystPhilippine Coast Guard collects oily water from June Aster → Philippine Coast Guard
The Event identifies the Coast Guard as actor, and the Entity identifies the organization.
The headline reports the missing figure revised down to eight; the linked Event describes oily-water collection. · reporting linkAnalystMissing passengers in Coron vessel tragedy revised down to eight → Philippine Coast Guard collects oily water from June Aster
The Story links to the Event; the headline reports eight missing and the Event describes oily-water collection.
The linked headline places the fire off Palawan, while the Event assigns Norway. · reporting linkAnalystخفر السواحل الفلبيني: 5 قتلى و87 مفقودا في حريق العبارة جون أوستر قبالة بالاوان → Ferry fire leaves over 80 people missing
The linked Story headline reports Palawan; the Event assigns Norway.
Coast Guard District Palawan is a mention in the story, not a recorded participant in an Event. · reporting linkAnalystPassenger ferry fire off the Philippines leaves 5 dead, 86 missing → Coast Guard District Palawan
The Entity is identified as mention-only and has no supporting Event.
How a Situation is put together24 Stories · 2 Events · 24 membership connections · 113 graph edges
A retained time step
This edition freezes the complete served membership and analysis available through its UTC cutoff. Later repairs or identity changes do not rewrite what this edition showed.
Stories, Events, and cast
Stories are reporting clusters. Events are coded occurrences within that reporting. The cast contains 45 canonical people and organizations linked to the retained evidence.
Typed connections
Story-to-Event edges identify supporting reporting. Entity-to-Event edges identify recorded actor or target participation. Mentions and analytical roles stay visibly distinct from recorded participation.
Core, precursor, and continuation labels organize the reading. They do not by themselves establish causation. Collapsed graph groups and paginated evidence change presentation only; counts use the complete retained edition.