Date: 201507
Local time of day: 0601-1200
Location: LAS.Airport, NV
Flight conditions: VMC
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B LAS
ATC / advisory: TRACON L30
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Training / Qualification; Time Pressure; Confusion; Communication Breakdown
Second reporter function: Pilot Not Flying; First Officer
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Returned To Clearance; Flight Crew Took Evasive Action
Contributing factors: Procedure; Airport; Chart Or Publication
Primary problem: Procedure

Narrative: Built and briefed the GRNPA1 arrival for ILS 25L. In quick order we were cleared direct to TRROP and for the RNAV visual 19R. We put in RNAV (GPS) 19R and quickly briefed the RNAV procedure as we were getting saturated. Captain recognized that we were really getting close to Nellis AFB. In very quick order we were told to confirm that we were doing the RNAV visual 19L. We quickly turned south as the controller gave us a heading of 190. The FO loaded the RNAV visual 19R as we were turning south to stay clear of Nellis AFB. By this time our aircraft was between TRROP and TOWEN. Simultaneously the Captain became concerned about the approach corridor to the LAS 25L/R; and Approach Control issued a heading of 260; the Approach Controller asked if we had the field in sight and cleared us for the visual to 19R; contact Tower. We performed a stabilized approach to 19R full stop. During debrief the crew noticed that the RNAV visual 19R on [our aircraft] FMC approach selection shows up as RNAV V 19R. In addition; JEPP PRO on the IPAD; with IPAD in the horizontal position; under approach selection; the RNAV visual 19L/R is not visible. The RNAV visual is listed under the general approaches; not under the RWY 19L or 19R approaches. When scrolled down to the RWY 19 approaches the RNAV visual is buried at the top of the page.My discussion with the LAS TRACON Controller he mentioned that their notes said to only allowed old 737 to do the RNAV visual approach to Runway 19L and 19R.


Second narrative: We then proceeded to JeppFD-Pro; scrolled to the approaches for 19 and selected the only RNAV approach to 19R I saw; which was the RNAV (GPS) Rwy 19R. We briefed this approach and discussed the proximity to Nellis AFB. Very shortly; the Captain mentioned we seemed be very close to Nellis. Almost simultaneously the controller came on and asked us to verify we were flying the RNAV Visual to 19R vice the RNAV 19R. I said 'verifying' and went heads down to check (although at that time I was pretty sure I had selected the incorrect approach). The controlled turned us to 190 heading. I realized there were two RNAV 19R approaches; one being a GPS while the other was a (V). I then loaded the RNAV (V) 19R and communicated what had happened to the Captain. While turning towards heading 190; the Captain said he was watching the 25 approach corridor. The controller then turned us right to 270 saying; 'I don't know where you are going with these vectors.' He then cleared us for the visual 19R and switched us to Tower.


Synopsis: An air carrier crew flying a GPS equipped aircraft flew the LAS RNAV RWY 19R after a late runway change and were told they should have flown the LAS RNAV VISUAL RWY 19R. The LAS RNAV RWY 19R is meant for non-GPS equipped aircraft.