Heavy Transport
Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Communication Breakdown; Confusion
ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Airspace Structure; Procedure
Aircraft X was filed for the SMUKE2 RNAV STAR to IND; which was landing Runways 23L and 23R. Indianapolis Center clearance was 'Descend via SMUKE2 arrival landing southwest.' In the case of the GIIBS2 arrival; 'landing southwest' would be sufficient. However; on the SMUKE2; the routing for Runway 23L and 23R diverge at FIIRE; to an East and West downwind; respectively. A proper descend via clearance for the SMUKE2 would be 'descend via the SMUKE2 arrival; Runway 23L (or 23R).' 'Southwest' is insufficient guidance for the SMUKE2 arrival; and in the event of lost communication; the flight crew and ATC would be unsure what routing to follow based on the Assigned; Vectored; Expected; Filed hierarchy. Note 4 on the SMUKE2 arrival page states to expect a descend via clearance with landing direction from Center and a landing runway from approach. I questioned the clearance with Indy Center who replied that 'everyone else' does it. I requested clarification as to the routing after FIIRE; and Center took us off the arrival and assigned direct VHP VOR and 11;000 feet. This is potentially a normalization of deviance; and is certainly poor STAR implementation where crews are cleared to descend to an altitude (6;000 feet); but beyond their known routing. Descend via procedures need to be linked to a specific routing in the event of lost communications.
Heavy Transport aircraft Captain reported being assigned the SMUKE2 STAR to IND without a runway transition; resulting in confusion.