India's Tejas Fighter Jet: A Look at Its Safety Journey Through Two Decades and Two Incidents
Share- Nishadil
- November 22, 2025
- 0 Comments
- 3 minutes read
- 4 Views
News of an Indian Air Force (IAF) Tejas fighter jet crashing near Jaisalmer recently certainly grabbed attention, and for good reason. It was, after all, the very first operational loss for India's homegrown Light Combat Aircraft (LCA) Tejas. But here's the fascinating bit: in the grand scheme of things, across prototypes and production models spanning more than two decades, this marks only the second major incident for the Tejas program. Quite remarkable, isn't it? Let's take a moment to really dig into these two rare occurrences and understand what happened.
Let's start with the most recent event, the one fresh in everyone's minds. It was Friday, March 8, 2024, a day when an LCA Tejas, specifically a Tejas PV-1 model, met with an unfortunate accident right near Jaisalmer. The aircraft was actually participating in the 'Bharat Shakti' exercise, a significant demonstration of India's defence capabilities. Thankfully, and this is always the most crucial part, the pilot managed to eject safely, walking away from what could have been a catastrophic situation. Initial reports strongly suggest that an engine failure was the culprit, prompting the pilot to take the necessary, albeit difficult, decision to abandon the aircraft. It certainly served as a stark reminder of the inherent risks in aviation, even for our most advanced machines.
Now, rewind the clock back nearly twenty years, to July 2, 2004. This incident unfolded near Gwalior and involved a Tejas prototype, specifically the PV-1 — yes, the very first prototype of the Light Combat Aircraft. It was a test flight, a critical phase in any new aircraft's development, when suddenly, the engine experienced a flameout. Imagine that: the engine just cuts out mid-flight. Squadron Leader N. Maithani, a highly skilled test pilot, was at the controls. With incredible presence of mind and expert maneuvering, he managed to guide the aircraft down, making what's often referred to as a 'belly landing' after running off the runway. The aircraft sustained only minor damage, and most importantly, the pilot was completely unharmed. This was a true testament to both the pilot's skill and, perhaps, the aircraft's inherent design robustness, even in its early developmental stages.
So, when you look at these two events side-by-side, spanning over two decades of intense development, rigorous testing, and eventual operational deployment, a remarkable picture emerges. The Tejas has demonstrated an incredibly strong safety record. Think about it: only two major incidents over 24 years is quite an achievement, especially for an indigenous fighter jet that has faced its share of developmental challenges and skepticism along the way. When we compare this to, say, the older MiG-21 fleet, which, despite being a workhorse, has unfortunately seen a far higher rate of accidents over its service life, the Tejas's track record really shines. It underscores not just the diligent work put in by Hindustan Aeronautics Limited (HAL) and the Aeronautical Development Agency (ADA), but also the robust design and rigorous testing protocols that have gone into making this aircraft a reliable asset for the Indian Air Force.
In essence, while any aircraft incident is a serious matter and a subject of thorough investigation, the two Tejas crashes are exceptions, rather than the rule. They don't detract from the aircraft's overall success story. Instead, they highlight the inherent risks of military aviation while simultaneously showcasing the impressive safety and reliability journey of India's very own Tejas. It's a journey that continues, making us all proud of this homegrown technological marvel safeguarding our skies.
Disclaimer: This article was generated in part using artificial intelligence and may contain errors or omissions. The content is provided for informational purposes only and does not constitute professional advice. We makes no representations or warranties regarding its accuracy, completeness, or reliability. Readers are advised to verify the information independently before relying on