11 days ago

AeroHack Submission Scope & Eligibility

Submissions must directly address aerospace-related challenges (aircraft, spacecraft, mission systems, or engineering analysis). Off-scope submissions may not be judged. Early resubmissions are welcome while the window remains open.

Questions?

If you have any questions about the hackathon, please post on the discussion forum.


14 days ago

Update: AeroHack build window extended — clearer timeline & expectations

Based on early interest, the AeroHack build window has been extended to give teams adequate time to deliver correct, reproducible, and well-validated solutions.

What changed (exact):

  • Hacking period: Feb 2 → Feb 23, 2026 (London time)

  • Judging period: Feb 23 → Mar 3, 2026

  • Winner announcement: Mar 3, 2026

Why this matters:
The extended timeline allows teams to properly implement a unified aircraft + spacecraft planning framework, run robustness/validation experiments, and produce clean results bundles and reports that judges can reproduce end-to-end.

Reminders:

  • No video required

  • Submissions must include runnable code, reproducible run steps, results (plots/metrics), and validation evidence

  • Solo…

Read more


14 days ago

Judge Update

AeroHack now includes an additional judge with 20+ years of global IT leadership and judging experience (IEEE Senior Member), strengthening evaluation of technical depth and robustness.

Questions?

If you have any questions about the hackathon, please post on the discussion forum.


15 days ago

flightalertpro884@gmail.com

Update Title:
AeroHack registration is open (solo allowed) — Starter Pack + clear requirements

Update Body:
Registration for AeroHack is open now (online). Solo participants are welcome (teams recommended but not required).

What you’ll build (advanced):

  • Aircraft: mission planning + simulation (UAV/fixed-wing) under constraints (wind, energy/endurance, maneuver limits, geofencing/no-fly zones)

  • Spacecraft: 7-day LEO CubeSat-style mission plan (observations + downlinks) under orbit/visibility + simplified pointing/power proxies

  • Unified approach: one planning framework across both domains (constraints + objective + planner)

No video required. Instead, submissions must include: runnable repo + reproducible run steps + results bundle (plots/metrics/outputs) + 4–8 page report +…

Read more