High Altitude Performance Optimization and Robust Design of Anti-Drone System.

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   Operating a jammer is unlawful for a private team on any band in India, so the neutralisation half of an anti-drone system cannot be developed, tested or demonstrated at all

2. It gets worse

   Micro-radian pointing accuracy is explicitly named and requires precision gimbals, encoders and structures costing lakhs — a hobby pan-tilt bracket is three orders of magnitude away and the gap is not one you can close with software

3. Still reading?

   The statement never specifies detection range, target class or accuracy target, so there is no bar to hit and no way to claim you met one

4. And the finisher

   The entire premise is high-altitude qualification and you cannot qualify anything without environmental chambers, which means the differentiating claim is untested by construction

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  1/5

  You have picked a fight with physics, procurement, or both. One of them always wins.

  Neutralisation of a drone in India means RF jamming or equivalent interference, which a student team cannot lawfully operate on any spectrum, and the rest is no better — micro-radian pointing needs precision gimbals and encoders costing lakhs, detection radar is defence-grade, and the high-altitude qualification the whole statement is about needs environmental chambers you do not have.

• Innovation scope

  3/5

  Mildly interesting. The novelty will not carry the room; the build has to.

  The statement names the subsystem domains and the effects to compensate but prescribes no architecture, sensing modality or control approach, so the design space is open — the constraint here is access, not imagination.

• Clarity

  2/5

  Nobody is sure what is being asked, quite possibly including the people who asked it.

  It asks for a robust high-altitude anti-drone system without specifying detection range, target drone class, neutralisation method, pointing accuracy target or the altitude envelope to qualify against, so the requirement is a list of desirable properties rather than a specification anyone could build to.

• Acceptance potential

  1/5

  The numbers do not like you. Bring something the numbers cannot see.

  This is a genuine trap and worth saying plainly — the neutralisation stage is legally off limits, the precision hardware is unaffordable, and the environmental qualification that is the entire point cannot be performed, so every submission will be a pan-tilt camera tracking a toy quadcopter in a corridor with the hardening presented as slides.

• Effort

  Massive

  A semester of work wearing a hackathon costume. Something is getting cut; decide what now, not in week five.

  Detection, identification, tracking and neutralisation across mechanical, electrical, RF and electro-optical subsystems, plus environmental qualification, compensation algorithms, thermal design and health monitoring, is a multi-year defence development programme compressed into a problem statement.

• Demo-ability

  Hard

  Near impossible to show working in five minutes, which is roughly five minutes more than you get.

  Neither defining condition can be shown — the high-altitude environment cannot be reproduced and the neutralisation function cannot be legally operated — so whatever appears on stage demonstrates a tracking mount indoors and asserts everything the statement is actually about.

• Data

  None supplied

  No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

  Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen 🪞

Somewhere around 90–210 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• Passive RF detection of drone control and video links is genuinely achievable with an inexpensive software-defined radio and is the one subsystem a student team can build and demonstrate honestly
• The compensation problem for temperature-induced cable rigidity and sensor drift is a real, interesting control question that can be studied on a small gimbal without any of the defence hardware
• DRDO as a T1 sponsor means a genuinely expert panel, so a narrow, rigorous contribution on one subsystem will be understood and valued more than a broad claim