Skip to content

Weike-2 Launch Success and Fuel Testing


Basic Information

  • Test Location: Unspecified (presumed to be the test site)
  • Participants: Principal Zhou, Principal Zhao, Principal Yang, VHSTIT team members
  • Recording Time Range: January 8, 2026 (Friday) 13:00 - 16:30 (Beijing Time)
  • Log Compilation Time: January 9, 2026

Launch Records

Serial No. Rocket Model Fuel Type Executor Result Notes
1 Weike-1 Fuel Type 2 Principal Zhou Ignition failure First attempt
2 Weike-1 Fuel Type 2 Principal Zhou Ignition failure Second attempt
3 Weike-1 Fuel Type 2 Principal Zhou Ignition failure Third attempt
4 Weike-2 Fuel Type 1 Principal Zhou Ignition successful, flight altitude 10.73m Presumed overweight nose cone causing insufficient altitude
5 Weike-1 Fuel Type 1 Principal Zhao Ignition successful, flight altitude 59.63m1 Altitude sensor detached, parachute did not deploy

Details on rocket models and fuel specifications


Analysis and Improvement Recommendations

Problem Summary

  1. Insufficient reliability of Fuel Type 2: Three ignition failures, possibly related to the uniformity or combustion characteristics of self-made fuel.
  2. Structural design defects:
  3. Overweight nose cone (Weike-2) leading to limited flight altitude.
  4. Nose cone wrapping too tight (Weike-1) affecting parachute release.
  5. Data recovery mechanism: Sensor fixing method needs improvement to avoid detachment.

Future Plans

  1. Suspend use of Fuel Type 2, prioritize testing prefabricated fuel (Fuel Type 1).
  2. Optimize nose cone weight balance and front structure to reduce front-end mass.
  3. Improve parachute compartment design to ensure deployment mechanism is not obstructed by wrapping.
  4. Strengthen sensor fixing method, employ redundant fixing or cushioned design.

Compilation Time: January 9, 2026 12:30 (Beijing Time)

Note: Except for explicitly stated times, some times are estimated; all analyses are based on current test data and require further verification.


  1. The altitude sensor is not ruled out from causing data errors due to impact