#5: [12-Nov-19]

#3: [06-Sep-04]

#2: [23-Mar-01]

#4: [12-May-19] (incomplete)

#6: [10-Jun-19] (incomplete)

06-Jan-2001 -- The sun was setting rather quickly as I left confluence 42°N 101°W. According to my GPS, sunset was at 5:30pm. If it was correct, I had one hour to drive 50 miles and find the next confluence.

Originally, this confluence wasn't listed on this website. I was curious to find out why. I made it to Ashby, NE around 5:20pm and still had a ways to go. I found a one-lane road that went south just before I reached the border between Grant and Sheridan Counties.

As I started down the road, the distance meter on my GPS started to fall quite quickly. It seemed as though I'd find the confluence somewhere just up ahead on the road itself. Unfortunately, the road veered west with a few tenths of a mile remaining. The sun was already below the horizon, so I stopped the car, grabbed my camera & coat, and took off running towards the direction the compass was indicating. I eventually came to a barbwire fence with a large pond just beyond it. I now understood why the confluence wasn't listed on the website.

My journey had started twelve hours ago, when I left Omaha, NE at 6:00am for my first confluence, 42°N 97°W, near Pilger, NE. When it was all said and done, I had visited three confluences, attempted two, had to abort (postpone) one, and covered 900 miles. I'd have to say that's not too bad for someone who didn't even know what a confluence was a week ago.

On my return to Omaha, I rewarded myself with a stop at Ole's Big Game Steakhouse in Paxton, NE. I thought it was quite fitting, considering all the hunting I had done today. If you're ever in the area, this place has to been seen to be believed.

A few days after the trip, I was searching on-line for this confluence. I'd like to attempt this one again this summer also. A few places showed the confluence located to the south of the pond. I think I'll bring an inflatable raft just to be safe.