How Claude Helped Me Navigate a Travel Nightmare (Without Losing My Mind)
Our Belize diving trip got derailed by an emergency diversion to Amarillo, Texas. Here's how I used Claude to turn chaos into a series of informed decisions, fast.
Andrew and I had been planning this trip for months.
Belize. Coral reefs. Several days of back-to-back dives as I work toward my PADI Divemaster certification. We had our gear packed, our dive shop confirmed, our underwater cameras charged. And then our flight got diverted to Amarillo, Texas.
Not delayed. Diverted. As in: we are no longer going to our destination, please remain seated while we figure out what comes next.
That moment (the announcement crackling through the cabin, the collective groan, the phones lighting up) is the kind of travel chaos that used to send me into a spiral of refreshing airline apps and holding on hold for 45 minutes. This time was different. This time I had Claude.
The Diversion
We were somewhere over the southwest when the captain announced a mechanical issue requiring an unscheduled landing. Amarillo was the nearest airport with the right facilities.
Within minutes of wheels down, the cabin transformed into a collective problem-solving session. Everyone was on their phone trying to figure out what to do next. The airline's app was already showing "delayed" with no updated connection info. The gate agents were overwhelmed.
I opened Claude.
What I Actually Used It For
1. Understanding My Rights Before Calling the Airline
The first thing I did was ask Claude to explain IROPS (Irregular Operations) and what American Airlines is actually obligated to provide passengers during an involuntary diversion.
I didn't know that term before that conversation. Twenty minutes later, I was at the gate agent counter asking about IROPS accommodations with enough confidence that they immediately escalated to a supervisor. That framing, using their own terminology, changed the entire dynamic of the conversation.
Claude didn't give me a script. It gave me vocabulary and context. That's underrated.
2. Real-Time Flight Tracking and Connection Math
While Andrew waited in line at the service desk, I was feeding Claude our current situation: which flights were still operating to Belize, what connections might work through Dallas or Houston, what the timing looked like given our current ETA to clear customs.
It helped me run the math out loud: if we land at X and our connection leaves at Y, and it takes Z minutes to deplane and walk to the next gate, what's actually realistic? This sounds simple, but when you're stressed and tired and also trying to not lose your dive trip, having something that can just reason with you is genuinely calming.
3. Charter and Ground Transportation Options
Our dive shop in Belize had a strict check-in window: if we missed it, we'd lose our first two dive days. So I asked Claude to help me think through whether there were any charter or ground options out of Amarillo that could get us to a connection city faster.
It helped me draft an outreach message to a local charter company I found listed. (The charter didn't pan out, but I had a real conversation with a real human within 20 minutes, which felt like progress.)
4. Hotel Comparison
The airline eventually offered two hotel options for the overnight. I asked Claude to quickly compare them based on the names and what it knew: distance to the airport, what kind of properties they were, whether there were any obvious red flags. It gave me a useful summary in about 30 seconds. We picked the one closer to the terminal.
5. A Second Opinion
This is the one I didn't expect to value as much as I did: Andrew was also using Claude independently on his phone. We'd occasionally compare conclusions. It was a kind of redundancy check: if we both arrived at the same answer from slightly different angles, we felt more confident. If we got different answers, we'd dig deeper.
There's something useful about having a thoughtful sounding board when you're under pressure. Not to make decisions for you, but to pressure-test your reasoning.
What It Didn't Do
Claude didn't magically fix anything.
We still spent the night in Amarillo. We still missed our first dive day. We still had to navigate a frustrating airline rebooking process that eventually worked out but took hours.
But what it did do was compress the time between problem and informed decision to almost nothing.
In past travel disruptions, the overwhelming feeling came largely from not knowing what I didn't know. What are my options? What should I be asking for? What's actually feasible here? That gap (between chaotic uncertainty and having enough information to act) is exactly where Claude is most useful.
The Bigger Pattern
I've been thinking about this a lot since we got back.
Travel disruptions are a microcosm of any high-stress decision environment: time pressure, incomplete information, emotional noise, multiple stakeholders, and cascading consequences. The tools that help you perform well in those environments tend to share one property: they reduce friction between where you are and where you need to be.
Claude doesn't replace judgment. It extends it. And in situations where I'm already capable but temporarily overwhelmed, having something that can reason alongside me without any of the emotional baggage is genuinely useful.
We made it to Belize, by the way. One day late, but we're on track to reach the ReefCI island this afternoon and the dive schedule is intact.
And honestly? The story of the detour ended up being more interesting than an uneventful arrival would have been.
Have you used AI to navigate a travel emergency or high-stakes real-time situation? I'd love to hear what worked, or what didn't. Find me on LinkedIn or say hi on Bluesky.
Tags 🏷️
