Date: 202104
Local time of day: 0601-1200
Location: L30.TRACON, NV
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B LAS
ATC / advisory: TRACON L30
Reporter organization: Air Carrier
Reporter function: Captain; Check Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Workload; Human-Machine Interface; Confusion; Communication Breakdown; Situational Awareness
Second reporter function: First Officer; Pilot Flying
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Chart Or Publication; Software and Automation; Human Factors; Procedure; Airspace Structure
Primary problem: Procedure

Narrative: We were Filed and Cleared for 'RNDRZ1 Arrival ILS 26L' in LAS. We set and Descended to 8;000 ft. with Managed Descend Mode. Controller then gave us Descend to 6;000 ft. and pointed out traffic. When we leveled off at 6;000 feet; I queried the controller by transmitting Level 6;000 ft. just passing BERBN Fix. He said 'Roger' as we continued to look for our traffic. We were coupled with ILS 26L and the aircraft started to turn after HOGOG Fix to Heading 020. It is only then; the Controller gave us vector to 080 even as he pointed out the traffic. He then told us that we should have picked up 080 heading after BERBN. RNDRZ1 states at BERBN FIX that 'Landing RWY19L/R; 26L/R EXPECT RADAR vectors to final approach course'. Controller never gave us a vector after BERBN and since Aircraft X Connects from BERBN-BISHP-HOGOG-KODSE-HUXAR; AC started the turn to 020.The initial clearance from ATC was too close to Descend Via Cleared for the ILS 26L. Traffic watch was involved. On the Arrival (which is New) the INSET does NOT display a Track of 079 only a small print that says 079 track after BERBN. This is Aircraft X specific when we select the STAR and APPROACH. I suggest that ATC proactively assign a heading prior to or after BERBN just as they to in LAX after SLI Heading 340 on GOATZ1 Arrival. Train Crews to clear the Waypoint after BERBN so there is a Discontinuity which would Default to 079 Heading.


Second narrative: We were filed and cleared for the RNDRZ1 arrival ILS 26L. I set 8;000 ft. in managed descent. Controller then cleared us to 6;000 feet and pointed out traffic. Leveled off at 6;000 feet and the Captain informed ATC that we were at 6;000 feet and passing BERBN and response was Roger. Continued to actively look for traffic. I was coupled to ILS 26L and just as the aircraft at HOGOG started it's turn the Controller gave us a 080 heading and was pointing out traffic at the same time. Then the controller stated that we should have flown a 080 heading out of BERBN. The RNDRZ1 states at BERBN fix that landing runway 26L expect radar vectors.From ATC initial clearance is too close to descend VIA for ILS 26L. Traffic watch was involved. Arrival the INSET does not display a track of 079 after BERBN only in the small print does it show 079. ATC should issue a heading at BERBN. The aircraft did not to link to the approach or to the arrival or remove the linked portion.


Synopsis: A Flight Crew reported while flying a new RNAV arrival the Controller told them they should have turned to a heading at a fix but the procedure specifies 'expect' vectors at the fix.