Preface
Thanks to my own personal constitution, I have a real knack for attracting "unclean things" that make my flights—or those of people around me—prone to IRROPS. For example, the IRROPS mentioned in @IPFS's post about 5 IRROPS across 4 trips in my past 6 months were, I suspect, triggered by me:
So (with nothing better to do) I was forced to develop a full set of IRROPS-handling skills, and today they happened to come in handy for no apparent reason. Since the IRROPS process was too dramatic, I decided to post to celebrate (commemorate) it.
Executive Summary
TL;DR: The ticket was HA's LAX-HNL-SEA. I was originally #1 on the upgrade list for LAX-HNL, but the LAX-HNL delay meant the second segment no longer met MCT. When I contacted reservations to rebook, the agent mistakenly changed the date of the LAX-HNL flight, and at the same time a weird bad interleaving occurred with the upgrade processing, causing the passenger ranked #2 on the upgrade list to take the only remaining First Class seat. In the end, the agent coordinated with the gate agent to cancel that passenger's upgrade and reassign the seat to me.
Background
I was planning to take advantage of the 11/11 holiday to do a mileage run on a SEA-HNL round trip. After some far-in-advance IRROPS, I strong-armed a reservations agent into giving me an extremely bizarre routing: SEA-LAX-HNL-SEA-PDX-PAE. While flying the first segment, SEA-LAX, I suddenly got a notification that LAX-HNL's AS 809 was delayed by an hour due to a late-arriving inbound aircraft, leaving only 23 mins for the connection to the later HNL-SEA AS 822—below HNL's MCT (25 mins). So I started thinking on the plane about how to rebook, and found that AS 900 on the same routing but departing a bit later would provide just enough buffer. I decided to call reservations after landing at LAX to get it changed.
Who would have thought rebooking could go sideways?
After landing at LAX, I called Alaska reservations directly. I have to say, your AS reservations agents are truly chill:
Agent: This is xxx from Seattle, what are you trying to do today? Me: My flight has IRROPS and no longer meets MCT—can you help fix it? Agent: (opens PNR) Are you doing a mileage run? Me: Yes. Agent: I see the IRROPS. Agent: I'm glad that you started the mileage run early! Agent: Every December I receive a lot of IRROPS calls where people start at the last minute and panic after IRROPS because there are no alternative flights
From prior research I knew that LAX-HNL's AS 809 was the only A332-operated flight after the afternoon period, so I didn't want to touch that flight and decided to change the return flights instead. On alaskaair.com I found that the AS 900 - AS 3169 - AS 2143 sequence would preserve the HNL-SEA-PDX-PAE routing, so I strong-armed the agent, recited the menu of flights, and asked them to see if they could protect that sequence, while the agent pulled in a supervisor to help with the ticket.
I had assumed this would be a very smooth, even trivial, IRROPS—but reservations always manages to pull off something big. While I was listening to music, I curiously checked the flights in my reservation on alaskaair.com, and my heart sank—
Why has my AS 809 moved to tomorrow?
Why did the one remaining first class seat on today's AS 809 suddenly get snatched by the person below me on the list?
At the same time, the agent suddenly came back and told me to go to the gate to find the gate agent. Unfortunately it was still too early and AS 809's gate agent wasn't on duty yet. Luckily LAX is an AS base, so I randomly found a gate whose agent had just closed the door and sincerely asked them to help deal with this mess.
Reservation: When I was changing the ticket just now, it seems the auto-upgrade script ran. This passenger got upgraded, but when the ticket was changed the date for AS 809 was entered wrong, so the upgrade didn't apply. Instead, a passenger below me got upgraded. Gate agent 1: ???? (wtf???????) Reservation: Can you see who was upgraded last? We need to kick them back down and get me upgraded. Gate agent 2: I don't know, let me look at who's in first class on AS 809. Gate agent 1: (works for a while) Can you tell?? First class has a bunch of titanium, a bunch of platinum, a bunch of gold, and a bunch of silver—can we just kick off a silver randomly?? Gate agent 2: Who was upgraded last? Let me ask station support how to view upgrade history. ... (Four-way call: me/gate agents/station support/reservation—20 minutes omitted) ... Gate agent 1: ok, I'm now kicking the last person upgraded back down, and then I'll put you back into first class right away.
And so I got a lie-flat seat on an A332, while some unfortunate passenger below me lost their lie-flat seat and was kicked back to premium class.
After this drama was resolved, I thanked the gate agents, and reservations said they'd immediately add my next two segments, SEA-PDX and PDX-PAE, and fix them too.
After another ten minutes, the agent came back and told me that because my ticket was still economy when they put me back into first class, their supervisor didn't dare touch the ticket either, fearing weird problems would come up again during reissue, so they decided to reissue the ticket after I departed LAX—
As a result, the gate agent printed a boarding pass marked flight coupon required.
Agent: ??? Let me go revalidate this segment.
(Five minutes later)
Agent: I revalidated it for you, you are good to go. When you get to HNL, check in for the remaining segments because we need to reissue the new ticket.
So after nearly an hour of IRROPS handling, it ended perfectly—the only casualty was one random passenger below me who got kicked from first class back to premium class.
Lessons Learned
Lesson 0: You need at least one tool to check fare/seat inventory.
Although this was a very small IRROPS, when a massive IRROPS happens (e.g., a flight cancellation where the whole flight needs to be reaccommodated), the reaction time left to people is very, very short (FCFS). So if you have an inventory tool on hand, you can check alternative flights the moment you receive the IRROPS notification, and if there's suitable availability you can try calling reservations and strong-arm them into issuing the ticket (bushi).
Lesson 1: Start mileage run planning ASAP.
As the agent said, December is peak mileage run season, so I strongly recommend that forum members with mileage run plans plan as early as possible and leave themselves enough buffer.
Lesson 2: The moment you get a flight IRROPS, you should immediately enter battle mode and prepare to fight others for flights.
The moment you receive an IRROPS notification: if you're at the airport, immediately find a gate agent and/or customer support to help handle the flight; if you're not at the airport, call reservations IMMEDIATELY—after all, if an entire flight is cancelled, existing capacity is very likely unable to cover everyone affected.
Summary
This experience once again proves that the most important things in handling IRROPS are reacting promptly, doing your homework in advance, and knowing what you want. If you can prepare an alternative routing before contacting reservations, it not only greatly reduces communication costs but also increases the probability of successfully protecting your ideal flights. Of course, when unexpected system issues like mine occur, stay patient, check the PNR promptly, and find ways to reach out to all available resources (e.g., reservations, gate agents) to do your best to keep your travel unaffected.
Finally, I still want to thank Alaska reservations. Although the whole drama was to some extent created by them, they were willing to spend nearly an hour coordinating multiple departments to fix a bizarre itinerary, and that service attitude is worth acknowledging. And many thanks to the LAX gate agents for being willing to stay at the gate after finishing their own flights to help me deal with this mess—I'll definitely praise that employee on Alaska Listens.
As for that unlucky passenger who was inexplicably upgraded to First Class and then kicked back to Premium Class, I can only say I'm very sorry—your lie-flat seat was taken by a stinky CS student who was debugging race conditions on the spot.
And I hope the next few segments don't pull any more stunts—after all, I just want to quietly rack up miles (


After the ticket change, the system's automatic upgrade script triggered an erroneous action—did this incur any additional fees or delay the subsequent itinerary? For example, after the date was mistakenly changed, was there any need to reconfirm hotel or ground transportation?