Window switch recorded. Logged to Flight Director.

[STATION ENTRY GATE]

Workstation Authentication

Enter your assigned Station License Key provided by Flight Director, and optionally name your flight crew.

or quick station test

[PHASE 01 / LAUNCH READINESS POLL]

Phase 1: Go / No-Go Rapid Verification

Rapid-fire verification: 20 randomized computing, math, and logic statements. You have strictly 3.0 seconds per statement to evaluate GO or NO-GO!

⚡

Rapid Verification Briefing

You will receive 20 randomized statements from the 150-question master pool. Each statement displays for strictly 3 seconds before expiring. Decide quickly: [G] / Left Arrow for GO • [N] / Right Arrow for NO-GO.

[PHASE 02 / BLACKBOX CRASH ANALYSIS]

Phase 2: Telemetry Analysis & Python IDE

The rocket ascended nominal through apogee but experienced an in-flight anomaly and impacted ground. Decode raw blackbox telemetry (flight_telemetry_crash.csv) using the built-in Python WebAssembly IDE.

[TELEMETRY BLACKBOX DATASET]

flight_telemetry_crash.csv

126 frames • 10 channels (altitude, velocity, voltage, current, IMU, status)

Download CSV ↓ Upload .py

telemetry_analysis.py

Pyodide Ready

TERMINAL OUTPUT (STDOUT) WebAssembly execution stream

[READY] Press 'Run Code' to inspect telemetry blackbox stream...

[PHASE 03 / ACCIDENT INVESTIGATION BOARD]

Phase 3: Root-Cause Investigation

Answer the official forensic board questions based on the telemetry you analyzed in Phase 2 to conclude why the CanSat rocket crashed (15 Questions, 120 PTS max).

📋

Investigation Board Examination

This final forensic exam requires Forced Fullscreen Mode. Any window defocussing or tab switching will be logged in real-time to the Flight Director.

● Fullscreen Anti-Cheat Active. Answer all 15 questions based on blackbox telemetry (Max 120 PTS: 8 PTS each).

[APOGEE TIMING / 01]

At what flight timestamp did the rocket reach its apogee (peak altitude where vertical velocity transitioned to 0.0 m/s)?

t = 5,000 ms (5.0s) t = 15,000 ms (15.0s) t = 25,000 ms (25.0s) t = 35,000 ms (35.0s)

[PEAK ALTITUDE RECORD / 02]

What was the absolute maximum altitude achieved by the vehicle above launch level recorded by the barometric sensor?

983.0 meters AGL 1,215.0 meters AGL 1,580.4 meters AGL 2,430.0 meters AGL

[LIFTOFF DYNAMICS / 03]

What was the initial vertical acceleration (Gz) registered by the accelerometer during motor burn at liftoff (t = 0 ms)?

+1.00 G +3.29 G +9.81 G +18.40 G

[FREEFALL CHARACTERISTICS / 04]

Following apogee during initial unpowered descent (t = 25,000 ms to 34,000 ms), what was the steady freefall vertical velocity before anomaly onset?

-9.8 m/s -38.0 m/s -62.5 m/s -95.0 m/s

[ANOMALY ONSET / 05]

At what timestamp in the blackbox telemetry record does the flight status flag first transition to ANOMALY_EPS_VOLTAGE_SAG_BROWNOUT?

t = 15,000 ms t = 25,000 ms t = 35,000 ms (35.0s) t = 49,500 ms

[BUS VOLTAGE COLLAPSE / 06]

At the onset of the anomaly (t = 35,000 ms), how low did the battery bus voltage plunge from its previous nominal 3.77V level?

Dropped to 3.50 V Dropped to 2.39 V Dropped to 1.20 V Dropped to 0.00 V

[CURRENT CONSUMPTION SURGE / 07]

What current draw surge directly coincided with the severe voltage collapse between t = 35,000 ms and 36,500 ms?

Current remained normal at 140 mA Current surged from ~140 mA up to ~700 mA (0.70 A) Current dropped to 0 mA due to open circuit Current surged past 10,000 mA

[DEPLOYMENT ALTITUDE CRITERIA / 08]

According to flight operational parameters, at what target altitude was the recovery parachute deployment squib programmed to trigger?

1,000 meters AGL 400 meters AGL 200 meters AGL 50 meters AGL

[RECOVERY ACTUATION ROOT CAUSE / 09]

Why did the parachute deployment squib fail to fire when the CanSat descended through the 400m threshold (t ≈ 39,000 ms)?

The parachute canopy was torn by high wind shear Severe bus voltage sag below 2.4V caused an MCU brownout reset / power lockout, suppressing the squib firing routine The barometric sensor disconnected from the I2C bus The flight computer assumed the payload had already landed

[POST-ANOMALY TERMINAL VELOCITY / 10]

Following recovery failure at t = 42,500 ms (RECOVERY_DEPLOY_FAILED_TERMINAL_DESCENT), what was the uncontrolled terminal descent velocity?

-12.0 m/s -24.5 m/s -43.5 to -44.8 m/s (~160 km/h) -98.0 m/s

[ATTITUDE & STABILITY / 11]

What do the gyroscope angular rate readings (gyro_x_dps, gyro_y_dps) reveal about payload attitude between 42,500 ms and 60,000 ms?

Stable upright orientation with near-zero angular motion Severe chaotic tumbling with rotational rates oscillating wildly up to ±47°/s Steady single-axis roll stabilization at 2°/s Dead sensor output reporting constant zero

[GROUND IMPACT TIMESTAMPS / 12]

At what exact timestamp did the flight computer register ground collision, changing status to GROUND_IMPACT_TERMINATED?

t = 35,000 ms t = 49,500 ms t = 61,500 ms (61.5s) t = 75,000 ms

[IMPACT DECELERATION FORCE / 13]

What maximum impact deceleration shock was recorded on the vertical Z-axis accelerometer (accel_z_g) upon collision?

-3.29 G -9.81 G -22.40 G -55.00 G

[ROOT CAUSE CLASSIFICATION / 14]

Based on the comprehensive telemetry investigation, what was the primary root cause that resulted in the total loss of the CanSat?

Parachute canopy structural rip caused by aerodynamic buffeting Primary EPS battery voltage collapse under high current load causing MCU brownout and recovery deployment lockout Barometer calibration error giving false positive ground detection RF radio transmitter frequency drift disabling ground control uplink

[CORRECTIVE ACTION MANDATE / 15]

To prevent this specific catastrophic failure mode on future missions, what hardware modification is strictly required?

Remove the parachute recovery subsystem to save payload weight Electrically isolate pyrotechnic squibs / high-current RF stages from MCU logic using separate regulators and supercapacitor buffering Reduce telemetry logging frequency from 2 Hz down to 0.1 Hz Replace the microcontroller with an analog timer circuit

MISSION STATUS

STANDBY FOR NEXT PHASE

INVESTIGATION LEDGER

ARCHIVED & SEALED