CT Assignment 2
Team 6 – CSE B
Group Members:
1. Name: K. Prashanth
Roll No.: 1602-24-733-097
2. Name: B. Priyadarshini
Roll No.: 1602-24-733-098
3. Name: K. Rahul
Roll No.: 1602-24-733-099
4. Name: K. Raja
Roll No.: 1602-24-733-100
5. Name: T. Sahasra
Roll No.: 1602-24-733-102
6. Name: A. SaiAshish
Roll No.: 1602-24-733-103
Project Title:
A Critical Thinking Audit of ISRO's Chandrayaan-3: An Analysis of Success After
Failure.
1. Problem Statement
On September 6, 2019, the Indian Space Research Organisation (ISRO)
attempted to make history with its Chandrayaan-2 (C2) mission by soft-landing
the Vikram lander on the lunar surface. The mission, watched by the entire
nation, ended in a high-profile failure when ISRO lost communication with the
lander just 2.1 km above the Moon. The lander deviated from its intended path
and crash-landed. This failure was not just a technical setback but a significant
national disappointment.
Just four years later, on August 23, 2023, ISRO executed the Chandrayaan-3
(C3) mission with flawless precision. The world watched as the lander
successfully navigated the same perilous descent, achieving a perfect soft
landing and making India the fourth nation in history to do so and the first to
ever reach the unexplored lunar south pole. This region is of immense scientific
interest due to the potential for water ice in permanently shadowed craters.
This dramatic turnaround from a critical failure to a historic success is a prime
case study in engineering and critical thinking. It was not a matter of luck, but a
direct result of a rigorous, systematic, and humble analysis of failure. The
"problem" for this audit is to deconstruct the logical, procedural, and design-
based assumptions that led to the C2 failure and to identify the specific critical
thinking processes that ISRO implemented to ensure the C3 success.
The objective of this project is to conduct a "Critical Thinking Audit" 2 of this
engineering turnaround. We will analyze the failure of Chandrayaan-2 to
identify its root causes and then dissect the success of Chandrayaan-3 to
highlight the "Lessons Learned"3. This case study serves as a model for all
engineering disciplines on how to systematically convert failure into a robust
and successful outcome.
2. Background & Evidence
To analyze the shift in thinking, we must first establish the evidence of what went
wrong and what was changed. This data is based on ISRO's own public statements,
post-failure analysis reports, and subsequent technical presentations on the
Chandrayaan-3 design.
The C2 failure was a cascading event that began during the "fine braking" phase of
the 15-minute descent.
The Event: The lander successfully completed its "rough braking" phase.
However, during the subsequent "fine braking" phase, the telemetry data
showed that the lander's engines produced slightly more thrust than the
nominal (expected) value.
The Anomaly: This minor hardware anomaly (higher thrust) caused the
lander to accumulate a small velocity error.
The Software Flaw: The critical failure was in the software. The guidance
algorithm's pre-programmed parameters had a "success-based" design; its
acceptable tolerance for such an error was too narrow. When the
accumulated error exceeded this narrow boundary, the software attempted to
correct the trajectory too aggressively. This rapid correction demand
saturated the engines' slew rate (their ability to turn), causing the lander to
become unstable and begin to tumble.
The Result: The lander lost control, lost its orientation, and could no longer
aim its engines correctly. Communication was lost at 2.1 km, and the lander
crash-landed at high speed. The core issue was not a hardware failure, but
a software logic failure; the system was "brittle" and could not handle a
real-world, off-nominal event.
3. Framework Application (SWOT Analysis)
Strengths (Internal Positives)
1. Learning from Failure (Chandrayaan-2):
ISRO effectively analyzed the failure of Chandrayaan-2’s lander and
implemented corrective measures — showcasing institutional learning and
adaptive problem-solving.
2. Engineering Precision and Cost Efficiency:
Achieved lunar landing at a fraction of the cost compared to other space
agencies, reflecting ISRO’s engineering ingenuity and resource
optimization.
3. Successful Soft Landing at Lunar South Pole:
First-ever successful landing near the lunar south pole, a region of immense
scientific interest — enhancing India’s global scientific prestige.
4. Strong Leadership and Team Coordination:
Cohesive project management, interdisciplinary collaboration, and resilient
leadership were key in overcoming previous technical setbacks.
5. Boost in National Morale and Global Image:
The mission unified public sentiment, reinforcing India’s reputation as a
capable and innovative spacefaring nation.
Weaknesses (Internal Challenges)
1. Technological Dependency and Constraints:
Limited access to advanced components and space-grade technologies due to
international restrictions still poses long-term developmental hurdles.
2. Communication and Navigation Limitations:
Despite success, some aspects like autonomous navigation and terrain
recognition systems still require further advancement for deep-space
missions.
3. Budgetary Restrictions:
Operating within tight financial boundaries may limit experimentation and
risk-taking capacity compared to agencies like NASA or ESA.
4. Limited Commercial Leverage:
Scientific missions like Chandrayaan-3, though prestigious, generate limited
direct economic returns or industry spin-offs.
Opportunities (External Positives)
1. Global Collaborations:
Success opens doors for international partnerships with NASA, ESA, and
JAXA on lunar exploration and future Mars missions.
2. Commercial and Strategic Expansion:
Strengthens India’s position in the global space economy, offering prospects
in lunar mining, communication satellites, and space-based research
services.
3. STEM Inspiration and Human Capital Growth:
Inspires a new generation of scientists, engineers, and innovators in India,
potentially strengthening the national R&D ecosystem.
4. Laying the Foundation for Chandrayaan-4 and Gaganyaan:
Chandrayaan-3’s technological validation paves the way for more complex
human and robotic missions.
5. Leadership in South-South Cooperation:
Enhances India’s role as a mentor for developing nations in affordable space
technology and exploration.
Threats (External Risks)
1. Intensifying Global Competition:
Other nations (China, USA, Japan) are rapidly advancing lunar exploration,
potentially overshadowing ISRO’s achievements in future missions.
2. Geopolitical and Technological Restrictions:
Export control regimes and limited access to global space markets could
hinder technological growth.
3. Funding and Policy Fluctuations:
Political or economic shifts could affect ISRO’s budget allocations and long-
term planning.
4. Space Debris and Lunar Environmental Risks:
Increased space traffic and lunar missions raise the risk of debris and surface
contamination, threatening sustainability.
5. Rising Public and Global Expectations:
Following the success, pressure for consistent high-performance could strain
organizational flexibility and innovation.
4. Solution
The C3 mission is the solution. Its design and execution provide a set of "Lessons
Learned" that are directly applicable to any engineering project.
Lesson 1: Adopt a "Failure-Based Design" Philosophy (Resilience > Perfection)
The most profound shift was from a "success-based" to a "failure-based" design.
The C2 team designed a perfect lander. The C3 team designed a resilient lander.
They assumed failure at every step: engines will fail, sensors will be wrong,
software will be buggy, and the landing will be hard. This pessimistic critical
thinking built an optimistic and robust outcome.
Lesson 2: Prioritize Software Robustness Over Brittle Logic
The C2 failure was a software failure triggered by a minor hardware anomaly. This
is a key lesson for the modern world, where systems are increasingly complex. The
C3 software was designed to be "anti-brittle." Its primary goal was to maintain
stability even with bad data, rather than crash while trying to achieve perfection.
Lesson 3: Build Redundancy in All Critical Systems
The C3 lander's design philosophy was "Redundancy, Redundancy, Redundancy."
This was most evident in the addition of the LDV sensor. The principle is simple:
never trust a single source of truth. In a complex system, critical data points (like
velocity) must be verified by at least two independent sources.
Lesson 4: Test for Failure, Not Just for Success
The C3 testing campaign is a model for overcoming confirmation bias. The team's
"failure injection" simulations—where they forced the C3 computer to re-live the
C2 crash—were a deliberate attempt to seek out disconfirming evidence. The goal
of testing should not be to get a "pass" mark, but to find the exact point at which
the system breaks, and then fix it.
Lesson 5: Treat Failure as Invaluable Data
The C2 crash was not a total loss. The telemetry data from that 15-minute descent
was the single most important asset ISRO had. It provided the exact blueprint of
the problem. A culture that buries its failures or refuses to analyze them (due to ego
or shame) cannot learn. ISRO’s humble, transparent, and data-driven analysis of its
own failure is the ultimate lesson.
5. Bias & Reflection
The transition from Chandrayaan-2 to Chandrayaan-3 is a textbook case study in
identifying and systematically overcoming cognitive biases in a high-stakes
engineering environment.
Biases Evident in Chandrayaan-2:
o Confirmation Bias: The pre-mission simulations were likely subject
to this bias. Engineers may have unconsciously favoured simulation
data that confirmed a successful landing, while unintentionally
overlooking the "edge cases" or off-nominal scenarios that ultimately
caused the failure.
o Overconfidence Bias: Following a long string of national successes
(like Chandrayaan-1 and the Mars Orbiter Mission/Mangalyaan), it is
possible that an "organizational overconfidence" emerged. This could
have led to a critical underestimation of the risks and an implicit trust
that its models and hardware were nearly infallible.
o Normalcy Bias: The team may have assumed that the "fine braking"
phase would be nominal because it had been in all successful
simulations, failing to give sufficient weight to the possibility of an
unexpected anomaly.
Reflections on the Critical Thinking Process (Chandrayaan-3):
o The entire C3 design process was a structured exercise
in overcoming these biases. The "failure-based design" philosophy is,
by definition, a tool to counteract overconfidence and confirmation
bias.
o The team actively sought out disconfirming evidence (by running
"failure injection" tests).
o They embraced the failure data from C2 as a gift, rather than a source
of shame.
o Conclusion: The success of Chandrayaan-3 was not just a
technological victory; it was a victory of process and culture. It serves
as a masterclass in applied critical thinking, demonstrating how a
large engineering organization can systematically identify its own
logical flaws and cognitive biases to achieve a resilient and historic
outcome.