Date: 201503
Location: LAS.Airport, NV
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class B LAS
ATC / advisory: TRACON L30
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Human factors: Confusion; Training / Qualification
Second reporter function: Pilot Flying; Captain
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: ATIS reported visual approaches (not CHARTED VISUALS) to 25L and 19 L/R. Flights ahead of ours were getting 25L and we were on the GRNPA arrival. We briefed a visual to 25L. Upon our change over to Vegas approach we received a change to 19R. We were short on time to make the change. In the rush to change to 19R neither of us found an RNAV visual approach due to the placement in the iPad Jeppsen [FD PRO]. We found an RNAV to 19R but it was GPS. Since we were cleared for the visual we loaded that into the FMC. We were both aware of terrain and selected a safe altitude and made a slight turn to be sure to avoid the terrain and started a decent. ATC noticed our course change and questioned which approach we were flying. Advised we were on the incorrect approach. It was not until we parked that we were able to find the RNAV VISUAL to 19R.


Second narrative: We were on the GRNPA RNAV arrival to LAS and assigned direct TRROP and 250 KTS. Previous aircraft had been sent to RWY 25L and we were briefed and programed for the same. The ATIS reported visual approaches to 25L and 19L/R. Prior to TRROP about 15 nm from LAS we were cleared for RNAV Visual 19R. We opened the APP button in Jeppesen FD PRO and scrolled down to RWY 19R and only found one approach; and that was the RNAV (GPS) 19R. Thinking that was what ATC meant FO replied RNAV GPS 19R and ATC countered with RNAV Visual 19R.Not seeing any other options we felt that ATC was combining a visual approach and the RNAV. So with terrain and airport reported in sight we inserted that approach and direct to JOGMU and turned right and started descent to 5300 feet. Around 6000 feet ATC complained that we were North of course and to climb to 6500 feet; which we did immediately. We reported the field in sight again and was cleared for a Visual Approach 19R and to slow to final speed. We were high and fast; but a slight purposeful overshoot and level S turn to final got us quickly configured and back on profile for a normal visual approach and landing.Once at the gate we found the RNAV VISUAL 19 R/L approach under the General category not under RWY 19R. I assume it is placed there because of the 19 R and L designation; but that is not intuitive. It should be listed under each runway it serves and given a distinct name such as Newark's Turnpike Visual 4L/R; or the River Visual to DCA. Then the ATIS could list the desired Visual approach; which we carefully read at cruise altitude and carefully program with no other distractions. Also; I'm sure ATC could have told us sooner their plan for our runway assignment than to wait until inside of 20 nm out. In hindsight; it's dangerous to make assumptions and I could have refused the last minute assignment and declared we were only set up for the 25L approach or take radar vectors to 19R visual.


Synopsis: A320 flight crew reports being cleared for the RNAV Visual to Runway 19R at LAS but can't locate the procedure on their iPads. The RNAV (GPS) 19R is loaded believing this is what the controller meant. It is not; and vectors are issued for a standard visual approach.