NJSwamplands

Your snipes from that awful experience always gives me a chuckle.

sonyeoshin

UA166 FUK-GUM 738 returned to FUK due to a flaps issue with the aircraft.

https://simpleflying.com/united-airl...cy-wing-issue/
https://www.flightaware.com/live/fli...215Z/RJFF/RJFF

sonyeoshin

UA102 IAH-MUC 763 diverted to EWR. Flight will not continue to MUC. Return UA109 MUC-IAH on 5/11 cancelled as a result.
UA154 Island Hopper 738 cancelled after HNL-MAJ due to a crew related scheduling disruption. Plane later did UA3041 from MAJ-GUM, skipping the other islands on the route.
UA912 ORD-KEF 752 cancelled due to a crew related scheduling disruption after a nearly 4 hour delay. Return UA913 KEF-ORD on 5/11 cancelled as a result.

sonyeoshin

UA930 SFO-LHR 772 cancelled due to maintenance. Return UA939 LHR-SFO on 5/12 cancelled as a result.
UA857 SFO-PVG 77W diverted to KIX.

ironmanjt

Yikes - please tell me they notified pax in HNL and didn't strand pax continuing beyond MAJ in MAJ...

sonyeoshin

UA132 Island Hopper 738 cancelled due to an unexpected operational issue.
UA857 SFO-PVG 77W returned to SFO. Flight took off again 7 hours late. Return UA858 PVG-SFO scheduled 5/13 has been delayed by 8 hours.
UA869 SFO-HKG 77W returned to SFO to address a customer issue. However status page now shows as cancelled due to unexpected operational issue. Return UA878 HKG-SFO on 5/13 cancelled as a result.
UA942 IAD-LIS 764 cancelled due to maintenance. Return UA943 LIS-IAD on 5/13 cancelled as a result.

ContinentalFan

UA29 SFO/SIN returned to the gate on Sunday morning to offload a passenger with an emergency medical issue. The flight was delayed and arrived in Singapore just over an hour late. The return flight, UA28, was scheduled to depart at 2200 local time, but it�s apparently still sitting at the gate.

sonyeoshin

UA882 HND-ORD 78X cancelled due to maintenance.

clearedforlanding

Bit of a new convert gently moving my flying from BA/One World to United/Star. Wondering what happened today and if this is some standard operating procedure I should be aware of going forward...

I was booked on UA2 Singapore - San Francisco today (15 May) which departs Singapore at 9am. Selected a seat, everything confirmed.

Around midnight I decide to randomly check my phone. I haven't received any messages or notifications but the UA app seems to say UA2 is cancelled due to a technical issue with the plane. Checking, UA1 is in the sky flying to SIN and the same plane generally operates the UA2. I click to check rebooking options and there's a new flight scheduled called UA3014 scheduled. Also at 9am on the 15th and available for me to 'rebook' onto. I do it. The flight is fairly empty and I actually snag a better bulkhead Polaris seat than I had before!

Turns out the UA28 (second SIN-SFO rotation) the night before turned back after take off and was subsequently cancelled. UA1 indeed landed into Singapore. The UA1 plane is operating UA3014. But UA2 is cancelled.

I'm lucky to be on the plane and on my way, albeit on a different flight number. This seems incredibly bizarre to me. Why would they do this? It seems there are passengers at the airport who were booked on UA2 but cannot get a seat on UA3014 despite it departing at the same time on the same route on the same metal on the same day. We literally all got dumped off the flight and first come first serve allowed to rebook onto it! Why would United do this?

drewguy

It’s not SOP. Don’t know all the details but if a plane didn’t make it UA has to figure out how to accommodate two return flights on one plane. You may have been lucky that you “rebooked” into the same flight before UA started doing it for everyone and prioritizing people based on status, etc.

EWR764

Seems like 3014 was initially planned to replaced the canceled UA28, a "try again" leg for N27957, but flown by N29971 (inbound UA1) as it was created around the time UA28 was returning to SIN. Not long thereafter, it was apparently determined that the airplane wasn't going to fly this morning. So, perhaps N27957 was assinged to UA2, but when it was determined that N27957 wasn't going to be available, UA2 was canceled.

I can't speak to why UA2 was canceled and not 3014, and swapped over to the available frame. N27957 is still in SIN, but flights are back on track.

ContinentalFan

I left SIN on UA2 on Tuesday. I noticed a United B789 sitting in a hangar. I didn�t get a chance last night to track it down, but maybe it was there for maintenance. Assigning a �rescue� flight number makes sense if they�re unsure when another aircraft might be available. It�s a bit of a pain, as in my experience, you don�t get a timely alert from United about the new flight. The good news is that if you didn�t get the seat you wanted, you can try and grab it on the rescue flight: for whatever reason, United doesn�t assign everyone to the new flights, so seats are open.

BlueZebra

Local media reported an engine problem after take off, causing the flight to return to SIN. Not sure why that doesn't jive with the OP's info.

mduell

Re UA3014 taking the plane and cancelling UA2, rather than reaccomodating the UA28 pax on UA2, sometimes UA does seemingly strange things to work around limitations of the reservation system.

gwade

https://avherald.com/h?article=518a977a

"Uncontained" always catches my attention.