STARS, TRANSITIONS AND APPROACH VIAS: CONTROLLED ARRIVAL STRINGING
An arrival can contain several connected elements: enroute transition, STAR, approach VIA and the approach itself. Database/provider organization affects which choices are offered. Read the complete procedure identifiers and actual chart sequence rather than assuming that selecting the correct runway establishes every preceding segment. For EGLL, use the current assigned arrival and approach; the historical route ending at LOGAN does not supply those choices automatically. [66, PDF pp. 119-120,199-204,336-340]
1. Open the destination arrival revision. Identify the intended runway/approach and select the compatible STAR, transition and VIA choices as presented. Read each selected element and return to the full flight plan. A familiar STAR name can still connect to a different approach transition, and a database list may distinguish multiple variants that look similar when abbreviated. [66, PDF pp. 119-120,199-204,336-340]
2. Check the join from enroute. Find the last route fix and first arrival fix, then inspect every connecting leg. Resolve repetitions and discontinuities by the intended route, not by a rule that all matching names must collapse. A chart can legitimately revisit a fix, and a procedural hold can deliberately duplicate the holding-fix relationship in the list. [66, PDF pp. 119-120,199-204,336-340]
3. Check the join into approach. Inspect the VIA or transition to the final approach path, its turns and altitude/speed restrictions. NO STAR or NO VIA are deliberate choices when the intended clearance requires them. They are not a universal repair for a troublesome transition. If selected, establish what provides the missing operational continuation, such as actual vectors or a separately cleared connection. [66, PDF pp. 119-120,199-204,336-340]
4. Audit a late change in full. A new runway or VIA can re-string the arrival and replace previously edited segments. Compare the revised temporary sequence with the current chart from the affected join through the missed approach. Inspect constraints and any manually entered changes again. Do not assume a manual edit remains both present and appropriate simply because it preceded the runway-change request. [66, PDF pp. 119-120,199-204,336-340]
5. Reconcile the rest of arrival preparation. After insertion, update radio-aid verification, PERF APPR data, minimum/configuration selection and landing-performance review as affected. Check the actual active leg after vectors or SEC use. The completion point is one current arrival across route, radio selection, performance assumptions and guidance plan, rather than a changed runway name on the bottom line alone. [66, PDF pp. 119-120,199-204,336-340]