01 / THE DEEP READ
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.
An air taxi is only practical when the aircraft and the ground system are designed together.
The eVTOL promise depends on four interlocking systems
An editorial visualisation of the relationships and choices discussed in this episode.
02 / EXPLORE THE ARGUMENT
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.
03 / TRANSPARENCY
Sources & attribution
Supporting references and reporting notes. Select a reference to visit its source.
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.
