Date: 201603
Local time of day: 1801-2400
Location: LAS.Airport, NV
Flight conditions: VMC
Light: Night
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B LAS
ATC / advisory: TRACON L30
Aircraft component: Electronic Flt Bag (EFB)
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Confusion; Situational Awareness
Second reporter function: Pilot Flying; First Officer
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure; Chart Or Publication; Procedure
Primary problem: Chart Or Publication

Narrative: Nearing LAS we anticipated and briefed an ILS/Visual approach. Upon contacting LAS TRACON we were told to expect a Visual Approach to Runway 25L. As we neared the airport; we saw Runway 19L. When we told TRACON that the runway was in sight; they cleared us for the RNAV Visual 19R. We selected the RNAV for the runway in the FMC but could not find an RNAV Visual Approach on the IPAD. We were rapidly approaching the airport when TRACON asked us why we were not going to the TRROP fix. We told TRACON that the fix was not on our approach chart. They indicated that this was a common problem; cleared us for a Visual Approach which ended with an uneventful landing.

Callback: Reporter stated that after landing the RNAV Visual 19R approach was found in the iPad filed under General rather than under Runway 19R as expected.

Second narrative: On arrival into LAS ATIS says using Runway 25L. Briefed approach 25L and on descent around 7000 feet Approach says the wind just picked up out of the south gusting 24 knots making 25L a big crosswind leg so they offered RNAV 19R. We said fine. Went into the box and into the iPad all at 6000 feet to change runway to RNAV 19R. Then ATC says the runway is ahead so we accepted a visual approach with the RNAV 19R as backup. All the while we are descending and getting closer to the runway and now in a hurry to get down. While trying to keep up ATC says it is RNAV visual 19R which we are doing the visual to RNAV 19R. Looked in the box and saw 2 RNAV approaches and on the iPad too and saw no charted visual RNAV 19R. Turned 15 degrees right to give room to get down on the visual and ATC immediately says why aren't you flying the charted visual? We responded that we didn't have it and they gave us vectors. There were no terrain or traffic conflicts. ATC says over the radio this is a very common problem and that all crews are not following the charted RNAV 19R visual approach. We would have flown it if we could have found it in a timely manner. As we had the RNAV and then the RNAV visual approaches given to us all within a minute or two after planning on 25L.


Synopsis: B737 NG flight crew was cleared for a LAS 'RNAV Visual 19R Approach'. The approach was selected in the FMC but not found in the iPad database.