Flight delays and cancellations in China follow civil aviation rules that differ from EU261. Foreign travelers can secure care, rebooking, and sometimes modest cash compensation — if they document the event and know what is excluded.

Fault Versus Non-Fault Causes

Carrier-side technical, crew, and certain operational failures are more likely to support cash compensation. Serious weather, many air traffic control measures, and security-related closures are commonly non-compensable for cash, though care duties may still apply.

At-the-Airport Checklist

1. Get a written cause explanation
2. Photograph boards; save app alerts
3. Keep expense receipts if care is not provided
4. Confirm rebooking or refund options in writing
5. Note times and counters for your timeline

Snapshot

Pattern: Passengers who file with cause letters and boarding passes outperform passengers who only argue at the gate.

Lesson: Treat disruptions like small claims files. Process beats outrage.

Expectations

Scheduled cash amounts are generally modest versus EU fixed sums. Prioritize care obligations and timely claims. Escalate to aviation complaint channels when airlines stonewall; litigate only for high-impact losses.

Connections and Group Travel

Document both segments when a delay causes a missed connection. Group travelers should appoint one document lead so claim packets stay consistent.

Shared Habits With Injury Files

Fault labels, proof, and schedules also drive traffic cases. Freeze evidence early and negotiate from documents.

Working Notes for Busy Readers

Keep a one-page action list: deadlines, document gaps, and decision forks. Share it with anyone who approves budget or strategy. Long chat exports are harder to use than a dated checklist with owners next to each task.

Ask counsel for three plain deliverables after kickoff: a chronology table, an exhibit index, and a short risk matrix. Request status notes that change only what moved since last time so foreign stakeholders can join midstream without rereading a novel.

Separate legal conclusions from business preferences in writing. "Trial risk is high, so settle in this band" is a legal-informed judgment. "We dislike conflict" is a preference. Both can be valid; mixing them produces muddled instructions.

Quality Control Before You File or Sign

Run a final pass: Do names and dates match across exhibits? Does every money figure have a source document? Is the company representative's authorization current? Are you asking for remedies the forum can actually grant?

If any answer is no, fix the packet before the hearing or the signature table. Speed without control turns a readable plan into an unreadable emergency.

Operational Detail

Readers handling fault versus non-fault causes should calendar statutory and contractual deadlines in one shared tool. Missed windows are rarely cured by longer explanations after the fact.

When multiple advisors touch fault versus non-fault causes, appoint a single drafting owner for external letters. Parallel voices create inconsistencies that counterparties exploit.

Translate only the pages that drive rights and remedies. High-quality translation of decisive clauses beats bulk machine output across the entire folder.

After each milestone, write three bullets: what we know, what we still need, and what decision is required. This keeps fault versus non-fault causes files scannable for executives.

Preserve original electronic files with metadata. Screenshots help illustration; native exports win authenticity fights related to fault versus non-fault causes.

Budget realistically for appraisal, notarization, and travel. Underfunded fault versus non-fault causes strategies produce incomplete records and weak settlement leverage.

If settlement becomes likely, draft term sheets with payment timing, default outcomes, and release scope before the meeting ends. Handshake deals on fault versus non-fault causes often unravel.

Document holds should include phones, email, chat apps, and shared drives used by the team closest to the facts. Partial holds create avoidable risk.

For foreign headquarters, provide a glossary of Chinese institutions and document types appearing in the file. Confusion about names slows approvals more than legal complexity does.

Revisit strategy when a new official letter arrives. Do not assume yesterday's plan still fits; update the issue map the same day.

Readers handling fault versus non-fault causes should calendar statutory and contractual deadlines in one shared tool. Missed windows are rarely cured by longer explanations after the fact.

When multiple advisors touch fault versus non-fault causes, appoint a single drafting owner for external letters. Parallel voices create inconsistencies that counterparties exploit.

Translate only the pages that drive rights and remedies. High-quality translation of decisive clauses beats bulk machine output across the entire folder.

After each milestone, write three bullets: what we know, what we still need, and what decision is required. This keeps fault versus non-fault causes files scannable for executives.

Preserve original electronic files with metadata. Screenshots help illustration; native exports win authenticity fights related to fault versus non-fault causes.

Budget realistically for appraisal, notarization, and travel. Underfunded fault versus non-fault causes strategies produce incomplete records and weak settlement leverage.

If settlement becomes likely, draft term sheets with payment timing, default outcomes, and release scope before the meeting ends. Handshake deals on fault versus non-fault causes often unravel.

Document holds should include phones, email, chat apps, and shared drives used by the team closest to the facts. Partial holds create avoidable risk.

For foreign headquarters, provide a glossary of Chinese institutions and document types appearing in the file. Confusion about names slows approvals more than legal complexity does.

Revisit strategy when a new official letter arrives. Do not assume yesterday's plan still fits; update the issue map the same day.

Readers handling fault versus non-fault causes should calendar statutory and contractual deadlines in one shared tool. Missed windows are rarely cured by longer explanations after the fact.

When multiple advisors touch fault versus non-fault causes, appoint a single drafting owner for external letters. Parallel voices create inconsistencies that counterparties exploit.

Translate only the pages that drive rights and remedies. High-quality translation of decisive clauses beats bulk machine output across the entire folder.

After each milestone, write three bullets: what we know, what we still need, and what decision is required. This keeps fault versus non-fault causes files scannable for executives.

Preserve original electronic files with metadata. Screenshots help illustration; native exports win authenticity fights related to fault versus non-fault causes.

Budget realistically for appraisal, notarization, and travel. Underfunded fault versus non-fault causes strategies produce incomplete records and weak settlement leverage.

If settlement becomes likely, draft term sheets with payment timing, default outcomes, and release scope before the meeting ends. Handshake deals on fault versus non-fault causes often unravel.

Document holds should include phones, email, chat apps, and shared drives used by the team closest to the facts. Partial holds create avoidable risk.

For foreign headquarters, provide a glossary of Chinese institutions and document types appearing in the file. Confusion about names slows approvals more than legal complexity does.

Revisit strategy when a new official letter arrives. Do not assume yesterday's plan still fits; update the issue map the same day.

Readers handling fault versus non-fault causes should calendar statutory and contractual deadlines in one shared tool. Missed windows are rarely cured by longer explanations after the fact.

When multiple advisors touch fault versus non-fault causes, appoint a single drafting owner for external letters. Parallel voices create inconsistencies that counterparties exploit.

Translate only the pages that drive rights and remedies. High-quality translation of decisive clauses beats bulk machine output across the entire folder.

After each milestone, write three bullets: what we know, what we still need, and what decision is required. This keeps fault versus non-fault causes files scannable for executives.