Skip to main content
Trip Reports

Most Rafting Trip Reports Are Useless. Here’s How to Write One That Saves Lives.

Trip reports that omit water levels, class ratings, and specific hazards are worthless. I argue for a standard template that prioritizes actionable safety data.

In 2024, the US Coast Guard verified 3,887 recreational boating incidents involving 556 deaths and 2,170 injuries (USCG 2024 Recreational Boating Statistics). That’s a lot of carnage on the water. And a good chunk of it could be prevented if boaters shared better information. I’m talking about trip reports—the lifeblood of the rafting community. But here’s the problem: most trip reports are garbage. They’re either humblebrags about epic lines or vague recollections that help no one. I’m going to argue that every rafting trip report should include a minimal set of hard data—water level, class rating, and specific hazards—and that omitting them is not just lazy, it’s irresponsible.

The Danger of Vagueness

Let’s start with the most common failure: “We ran the Gauley at a fun level.” What does that mean? Was it 2,000 cfs or 8,000? Without a number, that report is useless. The International Scale of River Difficulty rates rapids from Class I to Class VI, but the scale is not exact, and rivers do not always fit easily into one category (American Whitewater International Scale). A rapid can be Class III at low water and Class IV at high water. So if you don’t report the level, you’re hiding the most important variable.

On the New River, gauge height converts to flow: 8.1 feet on the Thurmond gauge equals about 11,400 cfs, and 10.6 feet equals about 20,200 cfs (NPS New River Gorge Private Boater). Those are wildly different experiences. A trip report that says “the New was running” tells me nothing. Give me the feet or the cfs.

What Every Trip Report Must Include

I’m not asking for a novel. I’m asking for five fields. If you can’t provide these, don’t bother posting.

  • River and section: Be specific. “Lower Gorge” is not enough. Name the put-in and take-out.
  • Water level: Give the gauge reading and the unit (cfs or feet). If you don’t know, say so—but then your report is incomplete.
  • Class rating: Use the International Scale. If it was Class IV, say Class IV. Don’t say “technical.”
  • Hazards: New strainers, undercut rocks, portages. For example, on the New River, some rapids have hazardous undercut rocks (NPS New River Gorge Whitewater). That’s critical intel.
  • Weather and temperature: Cold water kills. If the water was 45°F, say so.

That’s it. Five fields. Takes two minutes.

Why This Matters: The Human Cost

In 2024, where cause of death was known, 76% of fatal boating incident victims drowned; where PFD usage was known, 87% were not wearing a personal flotation device (USCG 2024 Recreational Boating Statistics). That’s a staggering number. But here’s the thing: trip reports can’t force anyone to wear a PFD. However, they can warn about the specific conditions that make a swim more likely. A report that says “Class V, high water, and a swimmer got stuck in a hydraulic for 30 seconds” tells me to bring my A-game and maybe portage.

Consider the Grand Canyon. Commercial trips run 226 river miles from Lees Ferry to Diamond Creek over 3–18 days (NPS Grand Canyon River Concessioners). A trip report for that run without water level is malpractice. The Colorado can fluctuate wildly, and the difference between 8,000 cfs and 20,000 cfs is the difference between a family float and a serious expedition.

The Counterargument: “Trip Reports Are for Storytelling”

I hear you. Some people write trip reports to entertain, to share the vibe, to remember the camaraderie. Fine. But you can do both. You can tell the story of the epic surf and also include the gauge height. The two are not mutually exclusive. In fact, the best trip reports I’ve read are the ones that weave the data into the narrative. “We put on at 10.6 feet—20,200 cfs—and the wave train at Surprise was a washing machine.” That’s informative and exciting.

The counterargument fails because it assumes that adding data ruins the story. It doesn’t. It enriches it. And it might save someone’s life.

My Recommendation: Adopt a Standard Header

I’m calling for a community-wide standard: every trip report, whether on a forum, a blog, or social media, should start with a header containing the five fields above. No exceptions. If you’re posting a video, put the data in the description. If you’re telling a story at the bar, at least mention the level. This isn’t about bureaucracy; it’s about safety.

The American Whitewater Safety Code advises boaters to allow an extra margin of safety between their skills and the river rating in extreme conditions, such as when the water is cold, at higher flows, or if the river is remote and inaccessible (American Whitewater Safety Code 2024). Trip reports are how we learn about those conditions. They are a safety tool. Treat them like one.

So next time you run a river, take two minutes to jot down the data. Your fellow boaters will thank you. And you might just prevent a fatality.

Sources

  • USCG 2024 Recreational Boating Statistics - https://www.uscgboating.org/library/accident-statistics/Recreational-Boating-Statistics-2024.pdf
  • American Whitewater International Scale - https://www.americanwhitewater.org/explore/safety/international-scale-of-river-difficulty
  • NPS New River Gorge Private Boater - https://www.nps.gov/neri/planyourvisit/whitewater_private.htm
  • NPS New River Gorge Whitewater - https://www.nps.gov/neri/planyourvisit/whitewater.htm
  • NPS Grand Canyon River Concessioners - https://www.nps.gov/grca/planyourvisit/river-concessioners.htm
  • American Whitewater Safety Code 2024 - https://site-media.americanwhitewater.org/Scale-of-River-Difficulty-Safety-Code-2024.pdf

Share this article:

Comments (0)

No comments yet. Be the first to comment!