Date: 201706
Location: LAS.Airport, NV
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
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Human-Machine Interface; Troubleshooting
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Airspace Structure; Chart Or Publication; Procedure; Equipment / Tooling; Human Factors
Primary problem: Chart Or Publication

Narrative: I would like to bring attention to; what I believe is a database error for one of the arrivals that blends into an approach into LAS. A couple of weeks ago; we were flying the SITEE1 arrival with 25L loaded up. I had RNAV-V 19R in the secondary; however I selected No Transition with an Approach via from LOOSN (if remember correctly). I selected No Transition because it has been my experience in the past that ATC will provide vectors; then clear you direct to (i.e.; TRROP or LOOSN) and then clear you for the approach. This time; however; we were cleared for the 'SITEE arrival; RNAV-V 19R.' The FO selected the appropriate arrival and runway from the database. However; it did not blend cleanly. The SITEE arrival ends at GRMPS and then has a manual heading afterwards. The RNAV-V 19R begins at LOOSN; which is prior to GRMPS. A complete course reversal.We were descending below 10;000; trying to slow down and come down; it was very turbulent; we were on our last leg of our last day of a 4-day trip. I have been flying in and out of LAS for 4+ years. The FO had been flying in and out of LAS for 2+ years; and we struggling to sequence the flight plan. The plane flew to a point where it couldn't handle the flight plan sequence because of the course reversal; while we're trying to clean it up. It defaulted to a Heading mode (chirp chirp chirp). I quickly turned the heading to the next point as the FO was finishing cleaning up the FMS. We overflew one of the points by a tenth or two; but otherwise flew the rest of the arrival and approach as charted.If prior to TOD; you load the Arrival and RNAV approach in the secondary fight plan and clean it up; this should not be a problem. Mainly because you have time to clean it up. However; if you activate secondary; and then later given a runway change (i.e.; you have RNAV-V 19R all cleaned up; activate it; fly it then given RNAV-V to 19L) I think some sequencing issue will happen.I believe the intent of this arrival and approach is to have it blend all nice and clean like others do. For example; LAX RIIVR arrival into ILS. The SAN LYNDI arrival into RNAV 27. Select the arrival and runway from the FMS; quickly review the points and restrictions; and you are all set. No clean up involved. No sequencing. No course reversal.I believe the SITEE arrival should end at LOOSN and the RNAV approaches should begin at LOOSN. If there needs to be a manual heading after this point for carriers who do not fly RNAV visual approaches; then our FMS should automatically take out that manual heading and sequence automatically; nice and clean.




Synopsis: Air carrier pilot reported their FMS could not navigate the LAS RNAV-V 19R Approach properly due to the fixes on the SITEE Arrival not blending into the approach.