3H Smart Trip Situation playbooks · Grand Canyon & desert

🏜️ Grand Canyon & the desert, when the day goes sideways

In a city, a bad day is solved by the nearest counter. Out here the nearest counter may be an hour away, the phone may have no signal, and the weather is a participant, not a backdrop. So this playbook inverts the city order: safety and shelter first, communication second, paperwork last — and several cards below are about deciding not to move. The safety content is built on the National Park Service's own canyon guidance and the Arizona Department of Transportation's desert-driving campaigns, not on folklore. If a ranger, a road sign or a closure notice in front of you says otherwise, it wins — the park's current status changes with the season and, after the August 2026 flood, month to month: check our Grand Canyon page's status box and the NPS pages before any below-rim plan.

⏱️ If it's happening right now

Read this first: this page is general information — it is not medical advice and not legal advice. Desert and canyon safety guidance changes with conditions on the ground; the National Park Service's current messages, trailhead signs and ranger instructions override anything written here. This page deliberately prints no compensation amounts and no promises: it gives you the order of actions and where the official procedures live.
Three habits, desert edition. (1) The vehicle is shelter — in heat, a stopped car with shade and water beats walking for help, almost every time; the cards below say when that flips. (2) Leave a trace before you need one — someone outside the canyon should already hold your plan; there is no official check-in service to do it for you. (3) Evidence still matters, later — photograph and note times when it's safe to do so; the claim, if there is one, is built afterwards out of exactly that.

🚗 On the desert road

The rental car dies on a desert highway Scene A5 · Breakdown, remote

The engine quits somewhere with one bar of signal, no shade but the car's own, and a horizon in every direction. This is the same breakdown as the city version with every variable turned against improvisation — so the order is tighter, and it comes from the desert-safety guidance the NPS and Arizona's DOT publish for exactly these roads.

  1. Coast to a stop fully off the pavement if you can, set the parking brake, and turn on the hazard lights while traffic is a factor. Note your location now — the last mile marker you passed, the road name, your direction of travel. Out here, "where" is half the rescue.
  2. Call for help immediately, while you still have signal and battery — the rental company's roadside assistance (the number is on your agreement and usually on a card in the car) and, if anyone is in danger, 911. The state's own advice for a breakdown in extreme heat starts with exactly this: call at once, to keep the wait as short as possible. Give the location from step 1 before you describe the car.
  3. Stay with the vehicle. A car is visible from the air and the road, carries shade and whatever water you have, and is what rescuers are looking for. The park service's desert guidance is blunt that walking away is how survivable breakdowns become searches. Raise the hood to signal trouble, and stay in the shade the car makes.
  4. Manage the heat while you wait. If the air conditioning still runs, use it. If it doesn't, open all the windows. If the interior becomes too hot to sit in, everyone — people and pets — gets out carefully and waits in the car's shade instead, per ADOT's extreme-heat breakdown guidance.
  5. Ration the phone, not the water. One charged phone is your lifeline: brief calls, screen down, no navigation experiments. Drink the water you have in small, regular amounts — saving it "for later" in desert heat is the false economy the safety pages warn about.
  6. If you truly must walk — no signal all day, no traffic, help not coming: stay on the road itself, go after the heat breaks rather than at midday, take all the water you can carry, and leave a note on the car with the date, the time, your direction and your plan. This is the exception, and the note is what makes it a plan instead of a disappearance.
Out here: two structural facts shape this card. First, distances — the tow and the replacement car are coming from a town, not the next exit, so "roadside assistance is on its way" can mean hours; that's why the call goes first and the waiting strategy matters. Second, coverage — signal on the rim roads and desert highways is patchy by geography, and the rental agreement, not an app, is the document that always works: read its roadside number into your phone's notes before the drive. And a pre-drive line that belongs on this card: in canyon country, the fuel gauge is a safety device — the desert runs in this region are long enough that "I'll fill up at the next one" is a decision, not a default.
📝 Log it now (battery permitting): the mile marker, the time you called, who you spoke to, and photos of the car and the dash. The Guide & Trip Record app works offline on your device — which is the point, out here.

The city version of this scene, with the crash paperwork order: San Diego playbook — rental breakdown & crash. Source guidance: NPS — desert backcountry road safety.

A crash, an hour from the nearest town Scene A6 · Crash, remote

The paperwork order from the city playbook still applies — but out here it runs behind a different first question: is anyone hurt, and how long until help can physically arrive?

  1. People first, harder than in the city. Check everyone in both cars. Anyone injured: 911 if you have signal — and know that response times out here are measured differently; shade and calm for the injured person are real first aid while you wait. Don't move a seriously injured person unless the scene itself is dangerous.
  2. Make the scene visible and safe: hazards on, cars fully off the travelled lane if they can move, everyone standing well off the road — desert highways carry fast traffic that isn't expecting pedestrians.
  3. Exchange and record everything, because there may be no second chance to get it: the other driver's name, licence and insurance details, plates, and photographs of both cars, the damage, the positions and the road. Distances out here mean the other party may be gone before any officer arrives — your photos and notes become the record, and the police report can be followed up afterwards.
  4. Notify the rental company within 24 hours — the deadline in the major companies' own accident guidance — and open the incident report. If the car is undriveable, roadside assistance arranges the tow; where it's towed to is a decision to confirm on that call, not to discover later.
  5. Assemble the claim file as you go: original and final rental agreements, the incident report, the police report when you have it, repair estimate and itemised bill, damage photos, and any demand letter. If you'll claim on the card you paid with, its benefits guide sets the exact list and deadlines — read it before assuming any version of this list, including ours, is complete.
Out here: the honest regional difference is time and reachability. A crash report, a tow and a replacement car all move at desert distances; a claim file assembled at the scene (step 3) is worth more here than anywhere, because you cannot go back for the other driver's insurance details tomorrow. One more structural point: if the crash involves a rental and injuries, your travel insurer's 24-hour assistance line belongs in the first hour of calls, alongside the rental company — many plans coordinate the medical side from that first call. The medical doors themselves (ER vs urgent care, and your right to be screened) are mapped in our emergency guide.
📝 Log it now: photos before anything moves, the other party's details, times of every call, and the report numbers as they arrive — the trip record app's claim-day checklist is the checklist for this file.

Tickets and rental admin fees after the fact: emergency guide — tickets · The city version of this scene: San Diego playbook.

The wall of dust is coming at the highway Scene D3a · Dust storm

A haboob doesn't arrive like weather; it arrives like a wall. Arizona's transportation department runs a named campaign for this exact moment — "Pull Aside, Stay Alive" — and its steps are specific enough, and counter-intuitive enough, that they are worth learning before you ever see one.

  1. Don't drive into it. If you can see the wall coming, slow down, check the traffic around you, and leave the highway or stop before visibility goes — the campaign's first rule is not to enter the storm hoping to outrun it.
  2. Get completely off the paved surface. Not the shoulder, not the emergency lane: off the pavement entirely, as far as you safely can. Cars stopped on the road itself are the ones that get hit.
  3. Turn off every light — headlights, hazards, all of them — set the parking brake, and take your foot off the brake pedal. This is the step everyone gets wrong. In near-zero visibility, drivers behind you steer toward lights they can see, mistaking them for a moving car to follow. Dark and parked is how you stop being a target.
  4. Stay inside, seatbelt on, and wait. Dust storms typically pass in minutes to under an hour. The car is the shelter; outside it you are invisible to traffic and breathing the storm.
  5. When it clears, re-enter slowly and expect debris, standing water and confused traffic for the next few miles — the storm's exit is its own hazard.
In Arizona: dust storms are a monsoon-season phenomenon — the season runs roughly mid-June to the end of September — and they arrive fast behind thunderstorm outflows, often late in the day. The state's real-time road information runs through AZ511; on a monsoon-season afternoon, checking it before a desert leg is the cheap version of this card. The companion rule from the same agencies: never stop in a dust storm in a travel lane, and never rely on the car in front of you — their lights may be the trap described in step 3.
📝 Log it now: little to log in this one — note the time and where you stopped, and any damage once it's light. If the storm leg broke a connection or a booking, the receipts go in the trip record with everything else.

The official campaign, in the state's own words: ADOT — "Pull Aside, Stay Alive" · Arizona Emergency Information Network — dust storms.

Water is running across the road Scene D3b · Flooded road · monsoon

Desert rain doesn't soak in; it runs. A dip in the road that was dry an hour ago can carry a current strong enough to move a car — the emergency agencies' shared slogan exists because people keep testing it: "Turn Around, Don't Drown."

  1. Stop before the water, every time. If you can't see the road surface through it, you cannot judge its depth or whether the road is even still there underneath.
  2. Know the physics the slogan is built on: around a foot of moving water can float a car, and less can take your footing if you're walking. The car does not win this negotiation.
  3. Respect the barricade as a legal line, not a suggestion. Driving around a road-closed barrier in Arizona is a violation in itself — and under the state's so-called "stupid motorist" law, a driver who enters a flooded road past a warning and has to be rescued can be charged for the cost of that rescue. The detour is cheaper in every currency.
  4. Wait, or reroute — on high ground. Flash floods in desert washes rise and fall fast. Waiting on high ground for the water to drop, and checking AZ511 for the closure's status, is a plan; creeping through is not.
  5. Never camp or park in a dry wash in monsoon season — the flood that fills it can arrive from a storm miles away, under a blue sky where you're standing.
In Arizona: the washes and dips are part of the road design here, not an exception — desert highways cross drainage paths that run a few days a year and decide those days completely. Monsoon season (roughly mid-June to end-September) is when this card applies; outside it, the same crossings are dusty dips you barely notice. The state's closure and conditions source is AZ511 — check it before desert legs in season, the way you'd check a flight status.
📝 Log it now: a photo of the closure or the water (from dry ground), the time, and the detour you took — if the delay broke a prepaid booking, this is the evidence half of that conversation, kept in the trip record.

The state's flood-driving guidance: ADOT — "Turn Around, Don't Drown".

Thunder over the rim — and smoke on the horizon Scene D4 · Lightning · wildfire evacuation

Two different skies, one shared rule: in open country, the weather and the land can both revoke your plans with very little notice, and both are situations where official words — a ranger's, an alert's — outrank your itinerary.

  1. Lightning: when thunder roars, go indoors. The National Weather Service's rule is a complete plan in one line: at the first thunder, get into a substantial building or a hard-topped vehicle, and stay there until 30 minutes after the last thunder. There is no safe place outside in a thunderstorm — not under a tree, not in a wash or an open shelter, and not "just for the photo" at a rim viewpoint, where you are the tallest object on a very flat horizon.
  2. On a trail, the 30-minute rule runs your afternoon. Monsoon-season storms build fast over the canyon, usually in the afternoon — which is one more reason the park's own hiking pattern puts the exposed hours early. If you're caught mid-trail, get off exposed points and away from water and metal railings, and wait the storm out rather than racing it to the rim.
  3. Wildfire: learn the two words before you need them. In California and Arizona's shared evacuation vocabulary, an Evacuation Warning means a potential threat — if you need extra time, or have pets or anyone who moves slowly, you leave now. An Evacuation Order means an immediate threat to life: it is a lawful order to leave at once, and the area is closed. There is no third step where you finish packing.
  4. Leave early, by the route officials name. Fire agencies' standing advice is to go at the Warning stage rather than gamble on the Order — roads out of canyon and forest country are few, and they fill. Follow the evacuation route given in the alert, not the scenic one in your plan.
  5. Where the words come from: Wireless Emergency Alerts reach any phone in the zone with no registration; county systems (the canyon sits in Coconino County, whose alert system you can register for before a trip) carry the detailed zone maps and updates. The alert on your phone, not social media, is the official channel.
Out here: this is not a theoretical card. The North Rim's historic Grand Canyon Lodge was destroyed by the 2025 Dragon Bravo Fire, and the rim has run restricted seasons since — fire is part of how this landscape now works, and closures after the August 2026 flood have tightened things further. Treat the park's current-status pages (linked from our Grand Canyon page) as part of packing: check them the week of the trip and the morning of the hike, because the answer changes.
📝 Log it now: screenshots of the alerts you received, with times — if an evacuation or closure breaks prepaid plans, the alert is the documentation the refund conversation will ask for. Keep them in the trip record.

Official wording: National Weather Service — lightning safety · CAL FIRE — evacuation terms, defined · CAL FIRE — ready, set, go.

🥾 Below the rim

Below the rim, and the heat is winning Scene C2 · Heat · dehydration · altitude

This is the canyon's defining emergency, and the National Park Service writes about it with unusual directness: there are no easy trails into the canyon, rangers respond to hundreds of heat-related rescues a year, and the classic victim is someone who treated the way down as the hard part. It isn't. Down is optional; up is mandatory — and the canyon gets hotter as you descend, roughly 5.5°F for every 1,000 feet, with the inner canyon running some 30°F hotter than the rim on a summer day.

  1. At the first real symptoms — nausea, dizziness, exhaustion, a headache that builds — stop. The NPS sequence is: rest in shade, sip water slowly and eat, especially salty food, and give recovery real time — an hour or more. Pushing on "to the next resthouse" while symptomatic is how this scene escalates.
  2. Cool the body, not just the throat. If there's a creek or a water station, wet clothing and skin. Shade, rest, cooling — in that combination — is the park's own field treatment for someone overheating.
  3. Drink to thirst — and no further. The canyon's counter-intuitive danger is over-drinking plain water: the NPS warns that too much water without salt causes hyponatremia, a life-threatening salt imbalance. Water and salty snacks travel as a pair; your body can only absorb so much per hour, so small and often beats heroic gulps.
  4. Respect the clock the park prints everywhere: in summer, don't hike between 10 a.m. and 4 p.m. And don't attempt rim-to-river-and-back in a day at all — the NPS states it flatly, in every season's messaging, with summer's inner-canyon shade temperatures able to exceed 100°F. If your plan already broke that rule, the fix is to stop descending now, not at the bottom.
  5. If someone can't continue, or symptoms worsen — confusion, stumbling, stopping sweating — that's the emergency line: send for help (next card) or use the nearest emergency phone. This is the moment the scene stops being self-help.
  6. The altitude footnote: the rims sit around 7,000 (South) to 8,000 (North) feet. Breathlessness, poor sleep and a headache on arrival day are the altitude introducing itself — another reason the big hike belongs on day two, not the afternoon you drive in.
Below the rim: water is infrastructure, not scenery. The canyon's pipeline can break at any time, and the NPS publishes which trail water stations are on or off that day in its Key Messages — check before you descend, and always carry a way to treat water. The trails are not interchangeable: Bright Angel has seasonal water, shade and ranger stations; South Kaibab has no water and almost no shade. Choosing the trail is choosing your margin in this scene.
📝 Log it now: where, when symptoms started, and what you did — if this ends at a clinic or in a claim, that timeline is the first thing asked. The trip record app works fully offline; write it at the resthouse, not from memory at the rim.

The park's own curriculum: NPS — Key Hiking Messages · NPS — canyon safety · Which door for treatment afterwards: emergency guide — hospitals & medical help.

Lost, off the route — and the phone says "No Service" Scene F1 · Lost · no signal

Start with the park's own answer to "will my phone work in the canyon?" — probably not. Across northern Arizona, and in the canyon above all, holding a signal is close to impossible below the rim. So this scene is not a phone problem with a hiking flavour; it's the canyon's default state, and the playbook was written by the NPS for it.

  1. Stop. The first rule of being lost is to stop making it worse. Sit down, drink, eat something salty, and reconstruct: where were you last certain of the route? Off-trail wandering in the canyon doesn't trend toward rescue; it trends toward terrain you can't climb out of.
  2. Retrace only if the way back is genuinely known and short. A corridor trail you left five minutes ago is one thing; "roughly uphill" in canyon country is how people end up cliffed out. If the retraced route isn't certain, staying findable beats moving bravely.
  3. Use the canyon's own emergency network: the emergency phones. On the corridor trails — Bright Angel, South Kaibab, North Kaibab — there are coin-free emergency phones connected to the park's 24-hour dispatch, located at ranger stations (Havasupai Gardens and Phantom Ranch are staffed year-round) and at the Bright Angel resthouses, with campground ranger stations on the same system. The nearest resthouse or ranger station is your 911.
  4. If the phone doesn't work, the NPS fallback is people: send for help along the trail — and send two people together, so the messengers can't become a second emergency. The person who stays puts out signals: bright clothing visible from above, a whistle if you carry one, and stays put.
  5. Know the line the rangers draw: "fatigue is not an emergency" is an actual NPS sentence — being tired and slow is a reason to rest, eat and reassess, not to trigger a rescue. Unable to move, injured, ill, or genuinely lost with night coming: those are emergencies, and the phones exist for them.
  6. The structural fix runs before the hike: there is no official check-in/check-out service in the park. Instead, leave your plan — leader's name, route, which rim you're exiting at, return date — with someone outside, and contact them when you're out. If you're overdue, that person is the alarm system. (And on rescue costs, the park's structure is: the search and rescue itself is the NPS's; ground ambulance and commercial air transport afterwards are the patient's — one more reason the assistance number in your insurance belongs in the pre-hike notes.)
Below the rim: the August 2026 flood rewrote parts of this map — the North Kaibab Trail is fully closed, both river bridges are closed, and Phantom Ranch is closed with no reopening date at the time of writing, per the NPS status pages summarised in our Grand Canyon page's status box. Routes, detours and which stations are operating change with the recovery — so this card gives you the structure (nearest resthouse or ranger station; send two; stay findable) and the park's current pages give you the map. Check them the morning you descend; a playbook printed from last season's canyon is a historical document.
📝 Before it matters: the most valuable log entry in this whole playbook is written at the trailhead — route, turnaround time, exit rim, and who holds the plan — photographed and left in the trip record and with your person outside. Offline is the app's home turf.

The park's hiking FAQ, including the phones and the "probably not" verdict: NPS — Grand Canyon hiking FAQ · Day-hiking guidance: NPS — day hiking.

Your bag went to the canyon — but not with you Scene A3 · Bag variant · the rim edition

Same lost-bag scene as the city playbook — the DOT rules, the baggage desk, the receipts — until the last mile, where this region changes it: your bag may be findable and still be a day away from you.

  1. Report it where it happened, before you leave that airport — Phoenix, Las Vegas or Flagstaff are the usual gateways — and leave with the written report and file reference. Everything in the city card applies: reasonable, verifiable incidental expenses are claimable; keep receipts; the liability limit is a ceiling, not an entitlement.
  2. Give the airline an address that understands the geography. "Deliver to my hotel" works in a city. Out here, name the rim lodge or the gateway-town hotel, with dates — a bag delivered to a trailhead town the day after you've driven into the park is a bag you'll collect on the way out.
  3. Decide what the hike actually needs, and replace only that. The essentials for below-rim safety — water capacity, sun protection, the medication in the lost bag — get replaced before you descend, claim or no claim. The rest waits. Never let a baggage delay talk you into hiking under-equipped to "keep the schedule".
  4. Medication in a lost bag is a medical scene, not a baggage scene: a pharmacist or urgent care in the gateway town, and your insurer's assistance line, are the route to a bridge supply — start it the same day, not at the rim.
Out here: we found no regional rule that changes the baggage claim itself — the DOT structure is the whole claim, exactly as in the San Diego card. What changes is only logistics: gateway airports sit hours from the rim, park lodges are not courier hubs, and the free rim shuttles move people, not luggage. Plan the delivery address like you plan the drive — as part of the route.
📝 Log it now: file reference, delivery address given, and every replacement receipt — the trip record holds them until the claim is assembled back home.

The full official structure: US DOT — lost, delayed or damaged baggage · The city version of this card: San Diego playbook — the carousel stops.

🌆 The same scenes, with a city around you: cancelled flights, lost bags, hotel walk-aways and rip currents — the San Diego situation playbook, where every problem has a counter nearby.
🚨 The institutions, when you reach one: hospitals and your right to be screened, consulates, tickets and courts — our emergency & officialdom guide picks up where the playbook hands off.
🏞️ Plan the canyon itself: trails, mules, lotteries and this season's closures — our Grand Canyon guide, and the which rim? and from Las Vegas companions.
📱 Keep the evidence in one place: the Guide & Trip Record app that comes with our books keeps your trip record on your own device — offline, which in this region is not a feature but the requirement — and its claim-day checklist is the file these cards keep pointing at.
📚 In the book: Las Vegas & Beyond, Planned Right — Book 2 of the 3H Smart Trip Guides — treats the canyon as the great day trip it is, rims, distances and all. See the book →

General information only — not medical or legal advice. Canyon safety content follows the National Park Service's Grand Canyon guidance (Hike Smart, Key Hiking Messages, hiking FAQ); dust-storm and flood content follows the Arizona Department of Transportation and the Arizona Emergency Information Network; lightning follows the National Weather Service; evacuation terms follow CAL FIRE's published definitions — all checked November 2026. Park conditions and closures change; the NPS current-status pages are the final word.