MU5735 crashed on 2022-03-21. The PRC has disclosed a very limited amount of information after years of investigation. It has long been suspected that the regime is trying to hide the facts behind this likely suicidal crash.

NTSB released a report in response to a FOIA request from a Chinese citizen on April 29, 2026. The report was quickly censored by the PRC on the same day, but it lives on the internet.

I have waited for the mainstream media to pick up this long technical report about a crash that killed 132 people for four days, but seen none, so I have to do my own work on this long report by enlisting the help of ChatGPT.

The strongest evidence of the man-made nature of this crash is the PRC's concealment and censorship. If the crash had been due to mechanical failures, the PRC would have released all the relevant reports as soon as possible, and likely would have had a propaganda campaign to blame Boeing and crush any rumors about pilot suicide.

The following is ChatGPT's summary of the NTSB report:

🧾 Overall summary of the MU5735 FOIA documents

These files are part of the U.S. NTSB-related FOIA release concerning the crash of China Eastern Flight MU5735 (Boeing 737-800) in March 2022.

🧠 Core takeaway (big picture)

Across the documents, the evidence strongly points to:

👉 Intentional control input leading to a rapid, near-vertical dive
—not a typical mechanical failure.

📊 Key findings from the documents

1. ✈️ Flight path & behavior

Aircraft was cruising normally (~29,000 ft)
Then:
- Sudden nose-down pitch
- Extremely steep descent (~30,000 ft/min at times)
Brief partial recovery
Followed by a second steep dive into terrain

👉 This pattern is not consistent with common system failures

2. 🎮 Flight control inputs

Data suggests:
- Manual control inputs pushed aircraft into dive
- Movements consistent with deliberate nose-down commands
Control surfaces behaved normally (no runaway system evidence)

3. ⚙️ Aircraft systems

No clear evidence of:
- Engine failure
- Structural breakup before impact
- Flight control system malfunction

👉 Systems appear functioning prior to impact

4. 🎧 Cockpit voice & data recorders

CVR/FDR were recovered and analyzed
Key points (from available summaries):
- No obvious distress calls
- No clear emergency troubleshooting sequence
Communication silence is notable

5. 🧍 Crew-related focus

The documents repeatedly examine:

Pilot actions
Possible incapacitation vs intent

👉 The investigation leans toward pilot input being central, though:

It avoids definitive public attribution in some sections

6. 🔍 Wreckage & impact

High-speed, near-vertical impact
Aircraft largely fragmented
No evidence of mid-air explosion

7. 🧪 Investigative tone

The documents are technical and cautious
They avoid strong public conclusions but:
- The data pattern is highly atypical
- Strongly aligns with intentional dive scenarios seen in past incidents

⚠️ Important nuance

These FOIA documents:

Are not a final public accident report
Contain raw investigative data, analysis notes, and communications

So:
👉 They imply conclusions rather than formally declaring them

🧠 Bottom line

Across all files:

Aircraft was functioning normally
Sudden, extreme dive initiated via control inputs
No evidence of mechanical failure explaining it
Scenario is most consistent with intentional or controlled input event

Detailed Timeline:

Here’s a clear, step-by-step timeline of China Eastern Flight MU5735 based on the FOIA documents you uploaded (e.g., and the related sets), combined with the flight data patterns visible in them.

⏱️ MU5735 Timeline (key events)

✈️ Cruise phase (normal flight)

~13:16 local time
Aircraft cruising normally at ~29,000 ft
Speed, altitude, and heading all stable
No anomalies recorded

👉 At this point, everything looks routine.

⚠️ Initial upset (start of incident)

~14:20:43
Sudden nose-down pitch begins
Vertical speed rapidly increases downward

👉 This is abrupt—not gradual—and marks the start of the event.

⬇️ Rapid descent (first dive)

Within seconds:
- Descent rate exceeds 20,000–30,000 ft/min
- Aircraft enters a very steep dive
No standard emergency recovery pattern observed

👉 This is far beyond typical accidental descent profiles.

📉 Mid-descent partial recovery

Around ~8,000–10,000 ft altitude
Aircraft briefly:
- Levels slightly
- Shows reduced descent rate

👉 Indicates:

Aircraft was still structurally intact
Control authority still existed

⚠️ Second dive (final phase)

Immediately after partial recovery:
- Aircraft pitches down again
- Enters another steep dive
No meaningful recovery afterward

👉 This second dive is critical—it suggests continued or renewed input, not a single transient failure.

💥 Impact

~14:22–14:23
Aircraft impacts terrain:
- Near-vertical trajectory
- Extremely high speed

👉 Wreckage pattern:

Highly fragmented
Consistent with high-energy, controlled descent into terrain

🧠 What the timeline implies

Key observations

Sudden onset → not gradual system degradation
Brief recovery → systems still functioning
Second dive → not a one-time failure
No distress calls → unusual for mechanical emergency

⚠️ Most important technical takeaway

This sequence:

Cruise → abrupt dive → partial recovery → second dive

is not consistent with typical failures like:

engine loss
turbulence
autopilot malfunction

It does match patterns seen in:

deliberate or sustained control input scenarios

📊 Simplified visual (conceptual)

Altitude
  |
30k ft ──────── cruise ───────────────
  |
  |            ↓ sudden dive
  |           /
  |          /
10k ft ──── / ── slight recovery ──
  |        /
  |       ↓ second dive
  |
  |      ↓↓↓↓↓↓↓↓↓↓↓↓↓
  |_________ impact _________
          Time →

🧾 Bottom line

Entire event lasted ~1.5–2 minutes
Aircraft remained controllable during part of the descent
The second dive is the most telling feature

👉 The timeline strongly indicates:

sustained or repeated control inputs, not a single failure event

Search This Blog

China Eastern flight 5735 (MU5735)