The doors are closed. The cabin is full. Somewhere in Delhi's dispatch system, a flag trips — and a Boeing 777 bound for Vancouver turns around before it ever leaves Indian airspace. The story circulated as a blunder. It's more interesting than that. **A 777 is not a 777.** The family spans the 200, 200ER, 200LR, and 300ER — each with a different maximum takeoff weight, fuel capacity, and range envelope. Delhi to Vancouver is roughly 11,700 kilometres. That distance demands a long-range capable variant. Put the wrong one on the route and you're not just short on comfort — you're short on fuel. But range is only the first filter. What makes this genuinely complex is that the approvals authorizing an aircraft to fly a specific route are tied to its serial number, not its type certificate. **ETOPS authorization — the regulatory permission to fly extended routes over water and remote terrain — is granted per aircraft, per operator, based on that jet's individual maintenance history and the airline's regulatory standing with its authority.** A 777-200ER and a 777-300ER from the same airline can carry different ETOPS ratings. RVSM approval, country-specific overflight permits, and payload-range sign-offs follow the same logic. The aircraft's paperwork is as route-specific as the aircraft itself. This is the invisible taxonomy that fleet managers navigate daily — and it becomes exponentially harder when the fleet is in motion. Air India's 777 fleet is partly inherited from its pre-Tata era, a mixed inheritance of variants at different points in their service lives. Under the Tata restructuring, the airline is simultaneously retiring older frames, reactivating stored jets, and integrating new deliveries. Each change reshuffles which serial numbers carry which approvals on which routes. **The operational cost of getting it wrong is immediate.** A return-to-origin for a long-haul widebody burns six-figure fuel costs, resets crew duty time, triggers slot penalties at Vancouver, and forces passenger reaccommodation across time zones. The error wasn't just a scheduling mix-up. It was the surface area of a fleet in transformation, briefly visible.