AVGEEK
The ePlane design trade-offs behind urban air mobility
Satya Chakravarthy discusses compact eVTOL design, balancing range, payload and cost, alongside regulatory approvals and the path he envisages towards commercial air-taxi operations in India.
The conversation
What does it take to reimagine flight for India’s cities — and make it affordable, scalable, and safe? In this episode of The Indian AvGeek, I sit down with Prof. Satya Chakravarthy, Founder, CEO-CTO of The ePlane Company and long-time professor at IIT Madras, to explore how deep-tech innovation is reshaping the skies above us.
From his early fascination with aerospace engineering to his bold leap from academia into ventures like ePlane and Agnikul Cosmos, Prof. Chakravarthy shares the sparks that drive him to tackle frontier problems. We dive into his concept of “defrastructure” — the invisible backbone of future mobility — and how it guides his work across aviation, space, and urban transport.
Together, we unpack:
• 🚁 The design philosophy behind ePlane’s compact eVTOLs and the balancing act of range, payload, and cost • 🛫 The regulatory gauntlet of securing DGCA’s Design Organisation Approval and lessons learned • 🔬 The breakthrough of “aerodynamic synergy” in the e200X and why 196+ design iterations were worth it • 🌆 The roadmap to commercial operations, early customer reactions, and how India’s cities might embrace air taxis • 🌍 India’s place in the global aerospace race — from UAM to rocketry, and even the possibility of a homegrown civilian airliner • 💡 Insights from global peers like Joby, Archer, and EHang, and what India can adapt for its own skies • 👩💻 His advice for young engineers and entrepreneurs daring to build at the edge of science and business
Vishal Mehra - @vishal1mehra
Key Takeaways
- Chakravarthy starts with a credible customer problem and a market large enough to justify aerospace development costs, rather than technology chosen for its own sake.
- For the proposed taxi operation, compactness and repeated short trips before charging shape the aircraft design; they are commercial requirements as well as engineering goals.
- Passenger payload is a constraint Chakravarthy wants to protect, with range and other performance characteristics improved through successive engineering steps.
- The intended initial air-ambulance use case brings practical cabin requirements: stretcher access, medical equipment, monitoring and hospital data transmission.
- Autonomous-flight capability and permission to carry passengers are separate questions. Chakravarthy says the company is not pushing pilotless passenger operations in India.
- Near-term plans centre on developing and selling aircraft through manufacturing and operating partners; Chakravarthy is explicit that cargo economics still need exploration.
- Viable air-taxi operations also depend on safe landing sites, charging and reliable ground connections; the vehicle alone cannot make a practical end-to-end passenger journey.
Additional subjects
Editorial analysis
The business case begins with a usable journey
Professor Satya Chakravarthy starts with a problem in urban mobility rather than an ambition to build an impressive machine. Aerospace development is expensive, he argues, so the customer need and potential market must justify the effort. For The ePlane Company, that means asking how an aircraft could reach people close to where they live and take them close to where they need to be. His broader vision is to reduce dependence on large, fixed infrastructure, not simply reproduce the airport journey on a smaller scale.
Engineering trade-offs follow the operating model
The proposed operating model then shapes the engineering. An air taxi needs a compact footprint and, in his account, enough flying capability to complete multiple short trips before a charging stop. That creates a difficult combination: short wings, slow flight and the efficiency of wing-supported cruise. Chakravarthy explains the company’s effort to make rotors and wings work together, while describing design as a succession of trade-offs rather than one decisive breakthrough. Passenger payload is a constraint to protect; range, stability, transition behaviour and power demand must be improved around it.
Certification and the air-ambulance opportunity
Commercialisation is a separate challenge. Chakravarthy describes learning to treat regulatory compliance as part of building the product and working with the DGCA to understand what is required. The first intended market is air ambulances, where cabin equipment, stretcher access, the paramedic’s working position and hospital data connections all affect the aircraft. His proposed passenger fares and timetable are expectations, conditional on development, testing and permissions. They are not an account of an operating service already carrying fare-paying customers.
Infrastructure, autonomy and commercial responsibility
The discussion also locates the aircraft inside a larger system. Landing sites need standards, charging and timely development; ground connections must make the whole journey usable. Chakravarthy separates the ability to develop pilotless technology from permission and public willingness to carry passengers without pilots. Near term, he describes an aircraft-development and sales business working with manufacturing partners and operators. He is more tentative about cargo economics than medical transport. That uneven confidence is useful: different applications need different business cases, even when they share much of the technology.
Questions & answers
Why begin with the urban journey rather than the aircraft?
Chakravarthy argues that an expensive aerospace development programme needs a credible, large enough market and a practical benefit for passengers. The design should follow the problem rather than the reverse.
Which requirements shape the proposed ePlane vehicle?
Compact landing space, useful passenger payload and the ability to complete repeated short journeys influence rotor, wing, range and charging trade-offs. He presents these as engineering objectives under development.
Why does the air-ambulance use case receive priority?
He identifies a medical mission with practical requirements—stretcher access, space for a paramedic, equipment and hospital connectivity—rather than merely fitting the same cabin to every use case.
Does technological autonomy mean pilotless passenger service is approved?
No. Chakravarthy distinguishes development capability from regulatory permission and passenger acceptance, and says pilotless passenger operations are not the company’s near-term focus in India.
What must exist beyond a certified aircraft?
Appropriate landing sites, charging, connections to ground transport, trained operators and commercial partners. His timelines and fare expectations remain contingent plans, not evidence of an operating airline service.
Sources & attribution
Original conversation: The Indian AvGeek — Episode 53. Originally published 2 November 2025.
Historical context: This analysis reports the ePlane Company founder’s 2025 statements. Aircraft specifications, certification status, schedules, commercial pricing and regulatory expectations are not independently established as current October 2026 conditions.
Editorial Q&A: These are source-grounded explanatory paraphrases, not verbatim interview dialogue.
Development qualification: Proposed passenger fares, medical operations, autonomy and commercial timelines are forecasts or goals conditional on technical development and regulatory permission, not an account of a certified passenger service in operation.