US Airways: Held Hostage In Sacramento!
A US Airways customer review by GetHuman user GetHuman-texedna from November 29th, 2017
Background on GetHuman-texedna's case
GetHuman: GetHuman-texedna - can you tell our other US Airways customers when your case took place?
GetHuman-texedna: Yes I can. It was middle of the night, on November 28th.
GetHuman: Did you reach out to US Airways, and if so, how?
GetHuman: And which of these common US Airways customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-texedna a list of common US Airways problems)
GetHuman-texedna: "Change flight" was why I was trying to call.
GetHuman-texedna's review of US Airways customer service
GetHuman: So how would you sum up your experience for GetHuman's US Airways customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
GetHuman-texedna: Held Hostage In Sacramento!
GetHuman: Can you tell the rest of us a bit more from what happened on 11/28/17?
GetHuman-texedna: My wife and I encountered a recent travel experience on US Airways which was deplorable! We were basically held hostage in Sacramento Airport for ** hours. The delays and changes were not due to weather conditions, but rather gross mismanagement.*The itinerary of the tickets purchased was a nonstop flight from California leaving on a night flight to arrive early the next morning in Charlotte. This return itinerary changed from that * to * different itineraries:**.*Mon., Aug. **, **** SMF to CLT on Flight ***** departing **:**pm. The plane arrived an hour late and reported a problem. While the plane was being examined the pilot timed out. The flight was cancelled. It took an hour to be rebooked for US Airways Flight **** at *:**am Tue., Aug. **. We inquired about lodging and were told it looked bleak. Finally we did receive a hotel voucher and managed to get * hours sleep.**.*Tue., Aug., **th we arrived for this flight departing SMF for CLT at *:**am with a stop in Phoenix. The agent suggested a direct flight departing **:**am supposedly created for the aforementioned cancelled flight.**.*We boarded the **:**am direct flight from SMF to CLT. It taxied out to the runway only to be called back to the terminal because of a detected brake failure. Needless to say, after waiting on this plane about an hour, this flight was also cancelled. We were instructed to deboard the plane and return to the terminal to be rebooked once again on a *th flight.**.*Tue., Aug. **th *:**pm departure on Delta Flight ***** from SMF, connecting on US Airways Flight **** in Seattle to depart **:**pm with final arrival to CLT Wed., Aug.. **th *:**am. *The final flight on Delta was successful! But the entire flying experience with US Airways was extremely frustrating and tedious. We were deprived of sleep, incurred extra expenses of purchasing meals at the airport, and lost a full day of employment. *The first flight would have worked out fine with minimal improvement in communication on the management level.*Our expectation is that we will be compensated fairly to demonstrate your appreciation of our business.
GetHuman: Let's quantify your experience contacting US Airways. On a scale of 1 to 5, how easy is it go get help on a US Airways problem?
GetHuman-texedna: I'd give them a one out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
GetHuman-texedna: I'd give them a four out of five on communication.
GetHuman: And what about US Airways's ability to quickly and effectively address your problem?
GetHuman-texedna: For that I would say three out of five.
GetHuman: And finally- any advice for other US Airways customers?
GetHuman-texedna: Call them early in the day or late. Don't forget any personal or account information you might need for US Airways to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-texedna taken from his US Airways customer service problem that occurred on November 28th, 2017.