So this happened to me a few nights ago and I thought I'd share what happened because if I knew then what I know now, I would have handled it differently. Pax and friend get in in Old Town with 2.0X surge, UberX, destination around Belmont and Pulaski. A few blocks from destination, a trip request comes in from the next pax a block away from the drop off, I accept. Then, when we get to pax1's destination, he tells me that was to drop off the friend, now he wants to change destination to his place which is another few miles. I tell him that's a problem because I accepted the next trip and I need to pick up that person. While still parked at destination 1, he put the new destination in through the app and navigation started directing me towards that location, but I'm thinking about pax2 and how I don't seem to have the option to cancel his ride, only navigate to pax1's second destination, so I tell him I have to end the trip and he'll have to request another Uber. He was cool about it and I tried to make him feel better that it'd probably be cheaper since he wouldn't be on the surge pricing, but I still felt bad (for kicking him out and missing out on surge miles). Anyway, once I cancelled his ride and he got out, I was expecting directions to pax2's location but there was nothing...so I think what happens in a situation like that is that when a second pax is in queue but pax1's destination is changed, Uber automatically cancels pax2's ride. Lesson learned - before accepting a "next trip" request, and you have multiple pax in the car...make sure they're all getting out at that destination.