TLP:CLEAR · Disclosure is not limited.

South China Sea: Coast Guard Pressure Persists After Sabina Shoal Collision

Time window: Last 7 days · Audience: General analyst · Type: Situation report · DTG: 2026-09-21 10:10Z · Overall confidence: HIGH

BLUF

China is very likely to continue China Coast Guard pressure against Philippine vessels and aircraft around Sabina Shoal, Subi Reef, Mischief Reef and Scarborough Shoal over the next 1-3 months. A collision involving Sanzhou'ao and Philippine vessel 3015 was likely reported on 18 September, but the available evidence does not resolve which vessel caused it or whether the incident will trigger broader military escalation.

Executive summary

Chinese reporting states that China Coast Guard vessel Sanzhou'ao conducted a law-enforcement operation near Sabina Shoal on 18 September and that Philippine vessel 3015 twice attempted to cross its bow within 10 minutes before the vessels collided. The Philippines had earlier reported Chinese radio warnings and observed flares during an unarmed Philippine Coast Guard flight near Subi Reef and Mischief Reef on 7 September. Chinese maritime authorities also issued entry bans for rocket launch operations on 17-18 September and military training on 17 September, but the supplied reporting does not establish that these notices responded to the Philippine flight. China has continued forceful diplomatic messaging, while wider reporting describes increased coast guard activity and access restrictions around disputed features. The evidence supports continued coercive maritime competition, but fault, intent and escalation risk remain contested.

Change from previous assessment

Since the prior brief on 20 September, the assessment has not changed in direction but has become more specific. New material adds China's account that Philippine vessel 3015 twice crossed Sanzhou'ao's bow within 10 minutes, details the 7 September Philippine flight near Subi Reef and Mischief Reef, and confirms separate 17-18 September maritime exclusion notices. The current material uses Sanzhou'ao and 3015, whereas the prior brief used CCG-21585 and BRP Datu Magat Salamat, so vessel identity and fault remain unresolved. This brief adds a separate judgement that the exclusion notices were unlikely to be a demonstrated response to the Philippine flight and retains the assessment that a sustained armed clash is very unlikely.

Key judgments

1. A collision on 18 September between China Coast Guard vessel Sanzhou'ao and Philippine vessel 3015 near Sabina Shoal is likely, but the available account does not establish which vessel caused it. Chinese Coast Guard reporting and associated video accounts state that 3015 ignored warnings, twice attempted to cross Sanzhou'ao's bow within 10 minutes, and collided on the second attempt. These claims come from Chinese official or major-media reporting, so the reported contact is better supported than the attribution of fault. (Confidence: low · ASSESSED)

• I&W: CONFIRM: Within 0-14 days, the Philippine Coast Guard or an independent review publishes geolocated footage or track data showing contact between 3015 and Sanzhou'ao near Sabina Shoal. (0-14 days)
• I&W: BREAK: Within 0-14 days, authenticated footage or official track data shows that the vessels did not contact or identifies different vessels at the scene. (0-14 days)

2. China is very likely to sustain China Coast Guard-led pressure against Philippine government vessels and aircraft around Sabina Shoal, Subi Reef, Mischief Reef and Scarborough Shoal during the next 1-3 months. The reported methods include law-enforcement patrols, radio warnings, flares, obstruction, water-cannon use and expanded coast guard or maritime-militia presence. The Scarborough Shoal reporting on floating platforms and a quadrupling of ships rests on thin, single-source think-tank reporting, which lowers confidence in that element without changing the broader assessment. (Confidence: medium · ASSESSED)

• I&W: CONFIRM: Within 0-14 days, the China Coast Guard announces another operation involving a named vessel at Sabina Shoal or Scarborough Shoal, while a Philippine government vessel receives warnings, obstruction or other physical interference. (0-14 days)
• I&W: BREAK: Over 1-3 months, Chinese and Philippine authorities report no close manoeuvres, water-cannon use or physical contact at Sabina Shoal, Subi Reef, Mischief Reef or Scarborough Shoal. (1-3 months)

3. Chinese maritime authorities almost certainly issued separate entry bans for rocket launch operations on 17-18 September and military training on 17 September in parts of the South China Sea. The warnings are supported by multiple reports, including major-media and social-media accounts, but the evidence does not establish that either notice was directed at the Philippine Coast Guard flight near Subi Reef and Mischief Reef. (Confidence: high · REPORTED)

• I&W: CONFIRM: Within 0-14 days, Chinese maritime authorities publish operational records or repeat the notices with the same dates, times and entry restrictions. (0-14 days)
• I&W: BREAK: Within 0-14 days, an official correction states that the rocket launch or military training notices were not issued or did not apply to the reported South China Sea areas. (0-14 days)

4. It is unlikely that the 17-18 September rocket-launch and military-training warnings were a demonstrated response to the Philippine Coast Guard flight near Subi Reef and Mischief Reef on 7 September. The notices do not name the Philippines, and the causal assessment rests on a single-source account; an explicit Chinese statement linking the notices to the flight would overturn this judgement. (Confidence: medium · ASSESSED)

• I&W: CONFIRM: Within 0-14 days, Chinese official messaging explicitly links the exclusion windows to the 7 September Philippine flight. (0-14 days)
• I&W: BREAK: Within 0-14 days, the original notices identify a separate launch or training purpose and contain no reference to the Philippine flight. (0-14 days)

5. Another close or physical encounter between Chinese and Philippine maritime forces is likely within the next 1-3 months. The 18 September contact follows reported dangerous encounters involving Philippine vessels 3012, 3018 and 3001, 3005 and 3017 around Scarborough Shoal, as well as a reported ramming incident involving a Chinese patrol boat near Second Thomas Shoal. Several of these historical accounts are Chinese official or major-media reporting without an opposing account, so the recurrence assessment is less secure than the fact of repeated official claims. (Confidence: medium · ASSESSED)

• I&W: CONFIRM: Within 0-14 days, a China Coast Guard vessel and a Philippine government vessel again make contact, conduct a dangerous bow-crossing manoeuvre or use a water cannon at Sabina Shoal, Scarborough Shoal or Second Thomas Shoal. (0-14 days)
• I&W: BREAK: Over 1-3 months, vessels at those sites maintain separation with no reported contact, water-cannon use or dangerous crossing manoeuvres. (1-3 months)

6. A sustained armed clash between China and the Philippines is very unlikely over the next 1-3 months. The supplied reporting centres on China Coast Guard law-enforcement operations, radio warnings, flares, maritime exclusion notices and an unarmed Philippine patrol aircraft. Confidence is low because this judgement depends partly on the absence of approved reporting on firearms or other weapons use, while a March report described Southern Theater Command activity involving a Philippine C-208 aircraft. (Confidence: low · ASSESSED)

• I&W: CONFIRM: Within 0-14 days, Chinese or Philippine authorities report firearms, missile employment or direct Southern Theater Command participation in an encounter involving the two countries. (0-14 days)
• I&W: BREAK: Over 1-3 months, incidents remain limited to China Coast Guard law enforcement, radio warnings, flares and exclusion notices, with no reported weapon use. (1-3 months)

Outlook & scenarios

Managed coercion and repeated close encounters (55%)

China Coast Guard patrols and Philippine government activity continue around Sabina Shoal, Scarborough Shoal, Subi Reef and Mischief Reef. Both sides use warnings, public accusations and close manoeuvres, producing another contact or obstruction incident without sustained weapons use.

Temporary operational restraint (25%)

After diplomatic exchanges, China Coast Guard and Philippine government vessels reduce close approaches for several weeks. China retains its maritime claims and patrol presence, while the Philippines continues selected surveillance activity without a new collision.

Serious incident with limited escalation (15%)

A new collision, water-cannon event or dangerous bow-crossing manoeuvre causes injuries or major vessel damage. China and the Philippines intensify diplomatic accusations and maritime deployments, but the confrontation remains below sustained armed conflict.

PLA involvement widens the crisis (5%)

The Southern Theater Command becomes directly involved in a new encounter with a Philippine aircraft or vessel rather than leaving the incident to the China Coast Guard. The resulting shift from law-enforcement activity to overt military involvement produces a broader regional crisis.

Recommendations

1. Maintain a daily incident ledger for Sabina Shoal, Subi Reef, Mischief Reef, Scarborough Shoal and Second Thomas Shoal. Record vessel names, aircraft type, warnings, course changes, water-cannon use, contact, injuries and official attribution separately.
2. Prioritise collection of original video, geolocation and track data concerning Sanzhou'ao and Philippine vessel 3015. Keep the contact assessment separate from the unresolved question of fault, and preserve both the Chinese designation of 3015 and the vessel identities used in the prior brief.
3. Treat the 17-18 September rocket-launch notice and the 17 September military-training notice as separate events from the 7 September Philippine flight unless an original Chinese notice or official statement establishes a direct link.
4. Set an immediate escalation alert for any report of firearms, missile employment, injury, major hull damage or Southern Theater Command participation in an encounter involving a Philippine aircraft or vessel.
5. Review daily Chinese Foreign Ministry, China Coast Guard and Philippine Coast Guard releases for changes in language concerning maritime infringement, provocative actions, Sabina Shoal and the South China Sea arbitration ruling.
6. Use the next 1-3 months as the primary warning window for a repeat close encounter, and brief decision-makers when named Chinese or Philippine platforms reappear at the same shoals after a public warning or exclusion notice.

Confidence & uncertainty

Overall confidence is high for the occurrence of the Chinese diplomatic statements, maritime warnings and reported China Coast Guard activity. These points draw on multiple claims from official bodies and major-media reporting, with additional corroboration from social-media reporting. Confidence is lower on collision fault, Chinese intent and escalation because the Sabina Shoal account is one-sided, the linkage between the exclusion notices and the Philippine flight is unproven, and the legal characterisation of Chinese activity east of Taiwan is contested.

Intelligence gaps

• [EEI 1.4 · UNCOVERED] Abrupt changes to vessel identification behavior: AIS transponder deactivations, spoofing, or mismatches between flagged identity and observed equipment/markings among PRC maritime law-enforcement or militia vessels operating near Philippine claims. Recommended collection: maritime/AIS
• [EEI 2.1 · UNCOVERED] Issued directives, patrol orders, or internal guidance from PRC Central Military Commission, PLAN, CCG, or provincial maritime authorities that specify objectives, geographic limits, patrol tempos, or escalation thresholds for operations near Philippine-claimed features. Recommended collection: signals/communications
• [EEI 2.3 · UNCOVERED] Evidence of mobilization orders, tasking lists, or logistics planning for Maritime Militia units (vessel requisitions, local fisheries bureau instructions, fuel/resupply manifests) indicating intent to employ militia alongside CCG/PLAN assets. Recommended collection: HUMINT/defense
• [EEI 3.1 · PARTIAL] Deployment and movement of Philippine Coast Guard and Navy vessels (class, location, on-station times) and scheduled or unscheduled escort/resupply missions to occupied features. Recommended collection: military/AIS
• [EEI 3.2 · PARTIAL] Air component activity: number and frequency of Philippine air patrol sorties, maritime domain awareness flights, and air-to-surface or maritime strike assets placed on alert or redeployed toward contested areas. Recommended collection: imagery/satellite
• [EEI 3.3 · PARTIAL] Requests for diplomatic, intelligence, or military assistance from allies (e.g., US, Australia, Japan) including notifications of planned joint patrols, port calls, or freedom of navigation operations with dates and participating units. Recommended collection: open-source/official statements
• [EEI 3.4 · UNCOVERED] Changes to Philippine rules of engagement, emergency law measures, mobilization orders, or civil advisories (evacuations, fishing bans) that alter civilian or military behavior in contested maritime zones. Recommended collection: open-source/official statements

Cited sources

[1] 中国评论通讯社 (China Review News Agency, 中评社) · 菲船只蓄意“碰瓷”挑衅我海警艇　有何图谋 (B) · sha256:d46fd1a6c750 [2] 新京报 (Beijing News) · 菲律宾船只蓄意“碰瓷”挑衅中方海警艇 有何图谋？ — 新京报 (B) · sha256:c6c3260e42b9 [3] 搜狐 (Sohu) · 最后48小时！中国准时封海，执行火箭发射行动，菲律宾后悔也没用 - 搜狐时间线 (B) · Wed Sep 16 2026 13:46:00 GMT+0000 (Coordinated Universal Time) · sha256:bc4427135c3f [4] 网易号 (NetEase Hao self-media user via 163.com) · 菲律宾后悔也没用，倒计时3天，中方将准时封海！ (E) · Wed Sep 16 2026 05:00:48 GMT+0000 (Coordinated Universal Time) · sha256:c8a09104423e [5] Center for Strategic and International Studies (CSIS) · Expect A More Dangerous Asia If Maritime Issues Don’t Make the Trump-Xi Agenda (B) · sha256:ec6105608915

Source content hashes were computed at collection time; the cited text is preserved unmodified for the life of this product.

Red cell review: PARTIAL DISSENT, KJ-1 downgraded MEDIUM→LOW (kj_single_origin)

TLP:CLEAR