HOA Diverted My Irrigation Water to Their Lake — Then the Ditch Company’s Gate Logs Exposed It — Transcript
Full transcript
- 0:00The first time I knew something was
- 0:01wrong, Clare Voss was standing beside
- 0:04the diversion gate in a crimson red
- 0:06blazer while an HOA contractor adjusted
- 0:08the hardware that controlled water
- 0:10flowing toward my ranch. My irrigation
- 0:12ditch was already running lower than it
- 0:14should have, but the decorative lake
- 0:16inside the subdivision was rising fast.
- 0:19I started photographing the gate, the
- 0:21water line, and the time. What I did not
- 0:23know yet was that every adjustment had
- 0:26already been recorded. My name is Grant
- 0:28Ellison. I am 56 years old and I run
- 0:31cattle on a dry country property that
- 0:33depends on scheduled irrigation water to
- 0:35keep pasture productive through the
- 0:37hottest part of the season. When my turn
- 0:39comes, I need that water moving through
- 0:41the lateral ditch and into the fields
- 0:43where it was assigned. A main irrigation
- 0:45ditch runs along the eastern edge of the
- 0:47valley. Smaller laterals branch off from
- 0:50it at controlled turnouts. One feeds my
- 0:53ranch. Another serves land farther north
- 0:56near Fair Haven Crossing, an upscale
- 0:58subdivision built around landscaped
- 1:00common areas and a decorative lake. For
- 1:03years, the arrangement caused no
- 1:05trouble. The ditch company published
- 1:07delivery schedules. Gates were adjusted
- 1:10as water moved from one account to the
- 1:12next. I tracked my start times, watched
- 1:14the flow at my turnout, and moved water
- 1:16across the pasture according to the same
- 1:18routine every summer. Clare Voss became
- 1:21president of the Fair Haven Crossing HOA
- 1:23the previous year. She was 43, polished,
- 1:27sharp, and easy to spot near the ditch
- 1:30because she almost always wore red. That
- 1:33afternoon, it was a fitted crimson
- 1:34blazer, black trousers, and dark shoes
- 1:37that looked out of place beside
- 1:39steelgate hardware and dusty ditch
- 1:41banks. I had seen HOA crews maintaining
- 1:44the lake shoreline and common area
- 1:46landscaping before. None of that
- 1:48interested me as long as their work
- 1:50stayed inside their own system. What
- 1:52caught my attention that day was the
- 1:54sound of metal. I had driven toward my
- 1:57turnout because the flow at the ranch
- 1:59had dropped more quickly than expected.
- 2:01My delivery window was still active, yet
- 2:04the water entering my lateral looked
- 2:06weak. Wet marks showed higher on the
- 2:08ditch wall than the current level. That
- 2:10was not normal for the middle of a
- 2:12scheduled run. I followed the ditch
- 2:14upstream near the split toward Fair
- 2:16Haven Crossing. A contractor was leaning
- 2:18over the gate mechanism with a wrench
- 2:20and a long metal handle. Clare stood
- 2:23several yards away with a black folder
- 2:25under one arm, watching the work. The
- 2:27contractor changed the gate position.
- 2:30The sound of rushing water changed
- 2:31almost immediately. More water pushed
- 2:34toward the branch leading north. Less
- 2:37continued toward my side. I did not know
- 2:39exactly what authority the contractor
- 2:41had, and I did not want to turn a water
- 2:44problem into a shouting match before I
- 2:46understood what had happened. So, I took
- 2:48out my phone. First, I photographed the
- 2:51gate from far enough back to show both
- 2:53channels. Then, I photographed the gate
- 2:55stem, exposed threads, locking hardware,
- 2:58and direction of flow. I took another
- 3:00image that included Clare, the
- 3:02contractor, and the turnout in the same
- 3:04frame. Then I recorded a short video of
- 3:07the water moving past the split. The
- 3:10difference between the two branches was
- 3:11visible. The branch toward Fair Haven
- 3:14Crossing carried a stronger current. The
- 3:16branch toward my ranch looked reduced.
- 3:18Clare noticed what I was doing. Her
- 3:21posture stiffened. She shifted the black
- 3:23folder against her side and watched me
- 3:25with irritated focus, as if the
- 3:27paperwork in her hand should settle the
- 3:29issue. I kept documenting. The ditch
- 3:32bank was dry enough that recent changes
- 3:34in water level left clear marks. I
- 3:37photographed those, too. Then I drove
- 3:40back toward the ranch. At my turnout,
- 3:42the flow had dropped even farther. I
- 3:45placed a measuring rod at the point I
- 3:47normally use to monitor depth and
- 3:49photographed the reading. I wrote down
- 3:51the time in a notebook I kept in the
- 3:53truck. The pasture nearest the turnout
- 3:56was still green, but the soil farther
- 3:58out had already started drying under
- 3:59several days of heat. One missed hour
- 4:02would not ruin it. A badly reduced
- 4:04delivery over the rest of the cycle
- 4:06could. That was the part outsiders
- 4:09sometimes missed about irrigation. The
- 4:11value was not just in water existing
- 4:13somewhere in the system. The timing,
- 4:15volume, and destination mattered. A
- 4:18ranch could sit near a full ditch and
- 4:20still lose a crop if the assigned flow
- 4:22never reached the right turnout during
- 4:24the scheduled window. I checked my
- 4:26delivery schedule again. My account was
- 4:29still active. The printed time block had
- 4:31not ended. I had no notice of a
- 4:33shutdown, maintenance warning, or
- 4:35reduced service. Nothing in my paperwork
- 4:38explained why the flow had changed. Late
- 4:41that afternoon, I drove past the road
- 4:44bordering Fair Haven Crossing. The
- 4:46decorative lake was visible through an
- 4:48opening between landscaped trees. Its
- 4:50water line looked high. Fresh water was
- 4:53moving through an inlet near the south
- 4:54end, sending a light ripple across the
- 4:57surface. around it. The HOA common area
- 5:00looked almost unnaturally green against
- 5:02the dry hills beyond the subdivision. I
- 5:05stopped where I could see the lake
- 5:07without entering HOA property and took
- 5:09another photograph. The image had been
- 5:11taken less than an hour after the
- 5:13contractor adjusted the diversion gate.
- 5:16That did not prove the water in the lake
- 5:18was mine. It proved only that two things
- 5:21were happening at the same time. My
- 5:23ranch flow had dropped. The HOA side
- 5:26flow had increased. I needed more than
- 5:29coincidence.
- 5:31I needed to know what the ditch company
- 5:32believed the gate position should have
- 5:34been during my delivery window. Before
- 5:37sunset, I went back one more time to the
- 5:39turnout. The contractor was gone. Claire
- 5:42was gone. The gate remained in the new
- 5:45position. I photographed it again from
- 5:48the same angle I had used earlier. That
- 5:50gave me a clear sequence for the
- 5:52afternoon. The final image showed one
- 5:54detail I had missed while everyone was
- 5:56standing there. A small metal
- 5:58identification plate was bolted to the
- 6:00gate assembly. It carried a turnout
- 6:03number and a ditch company asset code. I
- 6:06zoomed in until both were readable. That
- 6:09number was more useful than Claire's
- 6:10folder, more useful than the HOA lake,
- 6:13and more useful than any argument I
- 6:15could have had beside the ditch. It gave
- 6:18me a specific control point and if the
- 6:20ditch company tracked adjustments at
- 6:22that control point, there should be a
- 6:24record showing exactly when someone
- 6:26changed it. The next morning, I stopped
- 6:29treating the problem like a strange
- 6:30water reading and started treating it
- 6:32like a failed delivery. My first job was
- 6:35to eliminate anything on my own property
- 6:37that could explain the shortage. I
- 6:40walked the lateral from the ranch
- 6:41turnout to the first pasture check
- 6:43structure. The headgate was fully open.
- 6:45The channel was clear enough to carry
- 6:47normal flow, and none of the banks had
- 6:49slumped into the ditch overnight. Water
- 6:52was reaching the ranch. It simply was
- 6:54not arriving in the volume my scheduled
- 6:56run required. That sent the problem
- 6:58upstream. The timing made it urgent. My
- 7:02cattle were supposed to rotate onto the
- 7:03upper pasture after this irrigation
- 7:05cycle. The winter feed acorage beside it
- 7:09was also due for water. If I lost enough
- 7:11of the delivery, I would not just be
- 7:13looking at dry grass. I would have to
- 7:15change grazing plans and possibly
- 7:18replace feed I had expected to produce
- 7:20myself. I drove into the upper pasture
- 7:23instead of spending another hour beside
- 7:25the ditch. The difference was already
- 7:27visible from the truck. Grass closest to
- 7:30the lower irrigated ground still held
- 7:32good color, but the higher section had
- 7:35begun taking on a duller cast under the
- 7:37heat. I walked far enough into the field
- 7:39to press a soil probe into several
- 7:41places. Moisture remained deeper down,
- 7:44yet the top layer was drying faster than
- 7:46it should have during an active run.
- 7:49That gave me a practical deadline. The
- 7:51field was not ruined. It was still
- 7:53recoverable, but the missing water had
- 7:56started costing me time.
- 7:58I changed the cattle rotation that
- 8:00morning and kept the herd off the upper
- 8:02section. That bought the pasture a
- 8:04little protection, but it also turned
- 8:06the shortage into an operational problem
- 8:08I could no longer ignore. Back at the
- 8:10truck, I pulled out my irrigation
- 8:12schedule. My account was still inside
- 8:15its assigned delivery window. There was
- 8:17no maintenance notice, no shortened run,
- 8:20and no indication that my turn had been
- 8:22moved. I checked the time against the
- 8:24notes from the previous afternoon. The
- 8:26contractor had adjusted the diversion
- 8:28gate while my account was active. My
- 8:31turnout had weakened afterward. That was
- 8:33enough to justify looking beyond the
- 8:35ranch. I drove upstream again, but this
- 8:38time I did not stop first at the main
- 8:40diversion gate. I continued along the
- 8:43public ditch road toward a small
- 8:44measurement structure the company used
- 8:46farther down the branch serving my
- 8:48property. Water passed through it, but
- 8:50the current looked noticeably weaker
- 8:52than I was accustomed to seeing during a
- 8:54full run. That observation gave me
- 8:57something more useful than another
- 8:58photograph of dry grass. The shortage
- 9:01existed before the water reached my
- 9:03ranch turnout. Whatever had happened was
- 9:05upstream of my private irrigation
- 9:07system. I recorded the time and
- 9:09location, then continued toward the
- 9:11diversion. Nobody was there. The gate
- 9:14still sat in the position the contractor
- 9:16had left it. The northern branch carried
- 9:19visibly more water than mine, but I did
- 9:21not stand there documenting the same
- 9:23scene again. I already had that.
- 9:26Instead, I looked at where the northern
- 9:28channel went. The ditch followed the
- 9:30edge of the Fair Haven Crossing
- 9:32development before disappearing behind
- 9:34landscaped BMS and a row of trees. I had
- 9:37always known that branch served the
- 9:39subdivision area. I had never needed to
- 9:42care exactly how. Now I did. I drove to
- 9:45a public road crossing farther north
- 9:47where the channel passed through a
- 9:49culvert. Water moved strongly beneath
- 9:51the road. On the other side, the branch
- 9:54continued toward Fair Haven Crossing.
- 9:57For the first time, I could physically
- 9:59follow the route instead of simply
- 10:00looking at two water levels and assuming
- 10:03they were related. The discovery did not
- 10:05prove anyone had taken my allocation. It
- 10:08did establish that the same control
- 10:10point I had watched being adjusted could
- 10:12reduce the branch toward my ranch while
- 10:14feeding the channel that continued
- 10:16north. That was a much better question
- 10:18to carry into the next stage. When I
- 10:21returned home, I stopped trying to
- 10:23estimate what the pasture might lose. It
- 10:26was too early for that. I concentrated
- 10:28on preserving the timeline instead. My
- 10:31scheduled delivery was active when the
- 10:33gate changed. The reduced flow was
- 10:35measurable upstream of my ranch. The
- 10:37northern branch remained strong after
- 10:39the adjustment. The control point had a
- 10:42ditch company asset number attached to
- 10:44it. Those facts were enough. I spent the
- 10:47rest of the afternoon moving cattle and
- 10:49changing my pasture plan around the
- 10:50water I actually had rather than the
- 10:53water I had expected. That practical
- 10:56adjustment bothered me more than Clare's
- 10:58reaction at the gate. I could handle
- 11:00somebody being irritated that I
- 11:01photographed a contractor. What I could
- 11:04not absorb casually was losing part of a
- 11:07scheduled irrigation run and
- 11:08reorganizing my ranch around a decision
- 11:11I had never authorized.
- 11:13By evening, the upper pasture was still
- 11:15holding. The winter feed acreage was
- 11:17still salvageable. But I had ruled out
- 11:20the explanation that worried me first.
- 11:22The failure was not inside my ranch. The
- 11:26weak flow already existed before the
- 11:28water reached my turnout, and the ditch
- 11:30carrying the stronger share continued
- 11:32north toward Fair Haven Crossing. The
- 11:34next useful discovery came from
- 11:36following the water instead of watching
- 11:38the grass. The branch toward Fair Haven
- 11:41Crossing disappeared behind landscaping
- 11:43near the subdivision, but it did not
- 11:45vanish underground for long. A public
- 11:48road curved along the southern
- 11:49perimeter, and from there I could see
- 11:51where the ditch crossed beneath the
- 11:53pavement and reappeared near the HOA
- 11:55common area. I drove the route slowly.
- 11:59The channel passed behind a line of
- 12:00ornamental trees, crossed another
- 12:03service road, and eventually fed a
- 12:05concrete inlet structure near the
- 12:07southern end of the decorative lake.
- 12:10That was the physical connection I had
- 12:12been missing. The branch controlled by
- 12:15the diversion gate did not merely run
- 12:16somewhere in the direction of Fair Haven
- 12:18Crossing. It reached the lake. Fresh
- 12:21water was entering when I arrived. The
- 12:24lake itself looked unusually high for
- 12:26that point in the dry season. A row of
- 12:29pale shoreline rocks gave me a rough
- 12:31visual reference, but I did not spend
- 12:33the afternoon photographing them from
- 12:35every angle. I already knew what the
- 12:37bigger discovery was. I could trace the
- 12:40water from the diversion structure to
- 12:41the HOA inlet. Now the investigation had
- 12:44a route. A property management vehicle
- 12:47was parked near the common area service
- 12:49lane. Two workers were checking the
- 12:51shoreline equipment while Clare Voss
- 12:53stood near the inlet with a black
- 12:55folder. Her red blazer made her easy to
- 12:58identify from the public side of the
- 12:59road. I took one wide photograph that
- 13:02captured the inlet, the lake, and the
- 13:04maintenance activity. Then I put the
- 13:06phone away. Watching the lake rise was
- 13:09not going to tell me who had authority
- 13:11to change the gate. I needed to
- 13:13understand why the HOA had been working
- 13:15on the water system at the exact time my
- 13:17delivery weakened. A little later,
- 13:20another maintenance truck arrived
- 13:21carrying equipment used around the lake
- 13:23edge. The crew inspected the inlet
- 13:26structure and a line running toward the
- 13:28landscaped common area. Nothing about
- 13:30the scene looked like an emergency.
- 13:33There was no broken pipe flooding the
- 13:34road, no damaged bank, and no visible
- 13:37condition that would explain an urgent
- 13:39need to override another irrigation
- 13:41customer. That did not mean no
- 13:43legitimate maintenance issue existed. It
- 13:46meant the physical scene was not going
- 13:48to answer the authorization question for
- 13:50me. I left Fair Haven Crossing and drove
- 13:53directly back to the upstream control
- 13:55point. The hardware had not moved again.
- 13:58More importantly, the identification
- 14:00plate was still clear enough to read
- 14:02from the ditch bank. I copied the asset
- 14:04number into my notebook. That number
- 14:06gave me a way to stop thinking in terms
- 14:08of my ranch versus their lake. The ditch
- 14:11company would not organize its records
- 14:13around either of those descriptions. It
- 14:15would organize them around accounts,
- 14:17turnouts, control points, and delivery
- 14:19windows. That was the language I needed.
- 14:23Before contacting the company, I checked
- 14:25one more thing. I drove to another
- 14:28public crossing farther downstream on
- 14:30the ranch branch. The flow there was
- 14:32weak, too. That confirmed the same
- 14:35shortage at a second point outside my
- 14:37property. It also meant I could stop
- 14:39revisiting the pasture every few hours,
- 14:42looking for dramatic deterioration. The
- 14:44pasture would show consequences later.
- 14:47The water system was showing the cause.
- 14:49Now, back home, I laid out only the
- 14:52information that advanced the problem.
- 14:54My delivery schedule established when my
- 14:56account should have been receiving
- 14:58water. The upstream observations showed
- 15:00the shortage existed before the ranch
- 15:02turnout. The diversion structure showed
- 15:05where the flow could be split. Following
- 15:07the northern branch showed that it
- 15:09reached the Fair Haven Crossing Lake,
- 15:11and the asset number identified the
- 15:13exact control point where the change had
- 15:15occurred. The sequence was finally
- 15:18specific enough to investigate. I did
- 15:20not need another image of Clare. I did
- 15:23not need another photograph of grass
- 15:25losing color. I needed to know whether
- 15:27the ditch company had ordered the gate
- 15:29adjustment, whether someone outside the
- 15:31company had requested it, and what
- 15:33account was active when the hardware
- 15:35moved. The next morning, the water at my
- 15:38ranch had improved slightly. Not enough
- 15:40to recover the lost portion of the
- 15:42delivery, but enough that I could keep
- 15:44the immediate pasture problem under
- 15:46control. That gave me room to focus on
- 15:48the records. I gathered my account
- 15:51number, delivery schedule, turnout
- 15:53identifier, and the gate asset code.
- 15:56Then I added the time of the contractor
- 15:58adjustment from my phone metadata. Those
- 16:01were the details that could be checked
- 16:02against an operating system. As I drove
- 16:05toward the ditch company office, Fair
- 16:07Haven Crossing disappeared behind me.
- 16:10For 3 days, the dispute had looked like
- 16:12a rancher watching his pasture dry while
- 16:14a subdivision kept a lake full. That was
- 16:17no longer the useful version of the
- 16:19story. The useful version had a control
- 16:21point. It had an asset number. It had an
- 16:25active delivery window. And somebody had
- 16:28changed that gate while my water was
- 16:30supposed to be moving toward the ranch.
- 16:32The ditch company office did not look
- 16:34like the place where a property dispute
- 16:36would turn. It looked like every small
- 16:38irrigation office I had dealt with for
- 16:40years. a gravel lot, a low metal
- 16:43building, maps on the wall, schedules
- 16:46taped near a dispatch desk, a dry erase
- 16:49board covered with turnout numbers,
- 16:51delivery windows, and field notes. That
- 16:54ordinary setting was exactly what I
- 16:56needed. I brought the folder with my
- 16:58account number, the turnout ID, the
- 17:00photographs, and the delivery schedule.
- 17:03The first thing I wanted to establish
- 17:04was simple. Had my water delivery been
- 17:07changed by the company? My account
- 17:09showed the same window I had been
- 17:11working from. No cancellation, no
- 17:14emergency interruption, no scheduled
- 17:17maintenance block, no notation showing
- 17:19that my delivery had been voluntarily
- 17:21transferred or postponed. That
- 17:23eliminated one explanation.
- 17:26The next step was tracing the turnout.
- 17:28The asset code on the metal plate
- 17:30matched a control point in the company's
- 17:32network. That control point split flow
- 17:35between the lateral serving my ranch and
- 17:37a branch running toward the Fair Haven
- 17:39crossing area. The map itself did not
- 17:42accuse anyone of anything. It simply
- 17:44showed where the water could go. I
- 17:47compared that map with the photographs
- 17:48from the first afternoon. The location
- 17:51matched. The gate I had photographed was
- 17:54the correct control point. Then I
- 17:56started looking at the operational
- 17:58entries tied to that asset. The company
- 18:01tracked adjustments because different
- 18:03accounts received water at different
- 18:04times. Field personnel needed to know
- 18:07when gates were opened, reduced, reset,
- 18:10or checked. I did not receive the full
- 18:13history all at once. At first, I saw
- 18:16only enough to confirm that the gate had
- 18:18not remained in its normal scheduled
- 18:19position. An adjustment had been entered
- 18:22during my delivery window, then another.
- 18:25The timing stopped me. The first entry
- 18:28landed close to the period when I had
- 18:30noticed the ranch flow weakening. A
- 18:32later entry fell near the time I
- 18:34photographed the stronger current moving
- 18:36toward Fair Haven Crossing. That did not
- 18:39yet tell me who requested the change. It
- 18:41did not tell me how much water had been
- 18:43redirected, but it proved something I
- 18:46had not been able to establish from the
- 18:47field alone. The gate had been
- 18:50intentionally moved. I wrote the times
- 18:52down. Then I compared them with the
- 18:54metadata from my phone.
- 18:56The first photograph of Clare and the
- 18:58contractor beside the diversion
- 19:00structure had been taken shortly after
- 19:02one of the recorded adjustments. My
- 19:04turnout measurement came later. The lake
- 19:06photograph came after that. The sequence
- 19:09tightened. What had looked like separate
- 19:12observations now began fitting around
- 19:14specific operational events. I asked
- 19:17myself whether that could still be
- 19:18routine system balancing. It could, at
- 19:22least in theory. That was why I kept
- 19:25going. The ditch company also tracked
- 19:27which account was supposed to be
- 19:29receiving water during each delivery
- 19:31period. My account remained active
- 19:33through the same hours. There was no
- 19:35notation showing that my allocation had
- 19:38ended before the gate was changed. That
- 19:41mattered more than the appearance of the
- 19:42lake. The schedule and the adjustment
- 19:45record were now overlapping. Water
- 19:47assigned to my account was still in its
- 19:49delivery window when the control point
- 19:51changed. I went back through the
- 19:54previous week's entries to understand
- 19:56what normal looked like. The pattern was
- 19:58different. During ordinary deliveries,
- 20:01the gate changed when one account ended
- 20:03and another began. The timing followed
- 20:06the schedule. The entries I was looking
- 20:08at did not fit that pattern as neatly.
- 20:10They sat inside my active window. That
- 20:13was the first part of the company record
- 20:15that made me uncomfortable in a way the
- 20:17photographs had not. A photograph can
- 20:19capture a moment. An operating schedule
- 20:22shows what should have been happening at
- 20:24that moment. I returned to the ranch
- 20:26that afternoon and checked the turnout
- 20:28again. The flow had improved slightly,
- 20:30but not enough to make up for the
- 20:32earlier shortage. The upper pasture had
- 20:35lost more color. The winter feed acreage
- 20:38was showing visible stress across a
- 20:39wider section. I photographed those
- 20:42areas from the same marked positions.
- 20:44That gave me a third day of comparison.
- 20:47I was starting to see the economic side
- 20:49of the problem taking shape. If the
- 20:52water returned immediately, I might lose
- 20:54growth. If the delivery remained short,
- 20:57I could lose part of a cutting. The
- 20:59damage was still developing. The record
- 21:02trail was developing faster. Later that
- 21:04day, I drove past Fair Haven Crossing
- 21:07again. Clare was near the lake with two
- 21:09people I had not seen before. One wore a
- 21:12property management badge. The other
- 21:14carried rolled site drawings.
- 21:16Clare still wore red. This time the
- 21:19blazer was easy to spot from the road.
- 21:21Even though she stayed well inside the
- 21:23HOA common area, nobody was working at
- 21:26the diversion gate. Nobody was moving
- 21:29equipment. The tension had shifted.
- 21:32The problem was no longer happening only
- 21:34beside the ditch. It had entered
- 21:36offices, account records, and
- 21:38maintenance files. I did not approach
- 21:41them. I took one wide photograph showing
- 21:44the lake and the active inlet. Then I
- 21:47left. That evening, I rebuilt the
- 21:50timeline on paper. My irrigation
- 21:52delivery started. The gate was adjusted.
- 21:55My turnout flow dropped. The HOA side
- 21:58branch strengthened. The lake rose. The
- 22:01company recorded another adjustment.
- 22:04My delivery window remained active. The
- 22:07pieces were no longer floating
- 22:09separately. They were beginning to form
- 22:11one continuous sequence, but there was
- 22:14still a missing line. The operational
- 22:16entries showed when the gate moved. They
- 22:19did not yet tell me what direction each
- 22:21adjustment represented in measurable
- 22:23terms, who authorized it, or whether the
- 22:25Fair Haven crossing branch received more
- 22:27flow as a result. For that, I needed the
- 22:30more detailed gate history, not the
- 22:33schedule, not the summary entry, the
- 22:36actual control log, the one tied to the
- 22:38asset number. I had photographed on the
- 22:40first afternoon. That was the record
- 22:43that could turn a suspicious sequence
- 22:44into something much harder to explain
- 22:46away. The detailed gate log changed the
- 22:49dispute from suspicion into sequence. It
- 22:52was tied to the same asset number I had
- 22:54photographed on the diversion structure,
- 22:56and unlike the short operational
- 22:58summary, it showed each recorded
- 23:00adjustment in order. The first entry
- 23:03fell inside my irrigation window. The
- 23:05gate had been moved away from the
- 23:07position that normally supported my
- 23:09delivery. The second entry showed
- 23:11another change less than an hour later.
- 23:14That adjustment increased flow toward
- 23:15the Fair Haven crossing branch. I read
- 23:18the times again. Then I pulled up the
- 23:21photographs from my phone. Clare and the
- 23:23contractor had been standing beside the
- 23:25gate during that same period. The photo
- 23:28metadata did not match the log to the
- 23:30exact second, but it did not need to.
- 23:33The sequence was close enough to connect
- 23:35what I had seen to what the operating
- 23:37record showed. A contractor was
- 23:39physically adjusting the gate. The
- 23:41company log recorded an adjustment at
- 23:43that control point. My ranch flow
- 23:46dropped afterward. The HOA side branch
- 23:49strengthened. The lake rose for the
- 23:52first time. All of those pieces belong
- 23:54to the same timeline. The log contained
- 23:57more than timestamps. Each adjustment
- 24:00entry included a field note indicating
- 24:02the direction of the change. One entry
- 24:05reduced the opening serving my lateral.
- 24:07Another increased the setting on the
- 24:09branch feeding toward Fair Haven
- 24:10crossing. That was the part I had been
- 24:13waiting for. The issue was no longer
- 24:15whether someone had touched the gate.
- 24:17The record showed what the adjustment
- 24:19did. I compared those settings with
- 24:21prior delivery cycles. During normal
- 24:24operation, my account received a
- 24:26stronger opening through most of its
- 24:28scheduled window. The branch toward Fair
- 24:31Haven Crossing was not supposed to
- 24:32receive that kind of increased flow. At
- 24:35the same time, the current cycle was
- 24:37different. My opening had been reduced
- 24:40before my delivery period ended. The
- 24:42northern branch had been increased.
- 24:45The timing lined up with the photographs
- 24:47of Clare, the contractor, and the rising
- 24:49lake. I still did not assume that meant
- 24:52Clare personally controlled the ditch
- 24:54company. She did not. The gate log
- 24:57described operation, not motive.
- 25:00So I looked for the request trail. The
- 25:02company kept notes when outside parties
- 25:04asked for adjustments related to
- 25:06maintenance, access, or shared
- 25:08infrastructure. One entry referenced a
- 25:10service request connected to Fair Haven
- 25:12Crossing. The request was logged shortly
- 25:15before the first adjustment. It
- 25:17described a lake level maintenance
- 25:19concern near the subdivision's common
- 25:21area. That wording mattered. It
- 25:24connected the HOA's concern about its
- 25:26lake to the exact control point that
- 25:29governed part of my scheduled delivery.
- 25:31The contractor had not simply wandered
- 25:33to the wrong gate. Someone had asked for
- 25:36an adjustment associated with Fair Haven
- 25:38Crossing. The gate had then been moved.
- 25:42The branch toward the lake received more
- 25:44flow. My ranch received less. The
- 25:47company record did not show any
- 25:49corresponding notation authorizing a
- 25:51reduction to my irrigation account. That
- 25:54gap was important. The system showed a
- 25:56reason for increasing water toward the
- 25:58HOA. It did not show a reason for taking
- 26:01water away from me during my active
- 26:03window. I placed the service request
- 26:05beside the delivery schedule. The timing
- 26:08over overlapped. Then I placed both
- 26:10beside my first turnout reading. The
- 26:12reduction at the ranch followed the gate
- 26:14change. By then, the evidence had
- 26:17stopped depending on how full the HOA
- 26:19lake looked. The lake was still useful
- 26:21visually, but the gate log was stronger.
- 26:24It showed control. It showed timing and
- 26:28it showed direction. I returned to the
- 26:31field that afternoon with a copy of the
- 26:33relevant entries. The pasture stress had
- 26:35become easier to see from a distance.
- 26:38The higher section of grass had dulled
- 26:40further. The winter feed acorage still
- 26:42had recoverable growth, but the mist
- 26:45water had already affected how evenly
- 26:47the field was holding color. I
- 26:49photographed the same marked positions
- 26:51again. Those images would matter later
- 26:53when I had to calculate loss. For now,
- 26:56the more important change was
- 26:58institutional. The ditch company had
- 27:00begun reviewing who had requested the
- 27:02Fair Haven crossing adjustment and what
- 27:04authorization had been checked before
- 27:06the gate was moved. That was the first
- 27:09sign that the issue was no longer being
- 27:11treated as a minor field complaint.
- 27:14Clare appeared again near the HOA lake
- 27:17that evening. She stood beside the
- 27:19property management employee I had seen
- 27:21earlier, still in the crimson red
- 27:23blazer, but the scene was quieter than
- 27:25before. No contractor was touching the
- 27:28diversion hardware. No one was directing
- 27:31water. The inlet into the lake had
- 27:33slowed. I photographed the shoreline
- 27:35from the same roadside point. The water
- 27:38was no longer climbing at the rate I had
- 27:40seen during my delivery window. That
- 27:43image did not prove the cause by itself.
- 27:45The log already did more than the
- 27:47photograph ever could. The strongest
- 27:49part of the record was that it existed
- 27:51independently of my interpretation. The
- 27:54company needed those entries to operate
- 27:56the ditch. The timestamps, asset code,
- 27:59adjustment direction, and service
- 28:01request all existed because the system
- 28:03had to track where water was being sent.
- 28:05When I lined everything up, the path was
- 28:08clear enough to follow. My account was
- 28:10active. A Fair Haven crossing service
- 28:13request was entered. The gate was
- 28:15adjusted. My lateral was reduced. The
- 28:18HOA side branch was increased. My ranch
- 28:21flow dropped. The lake rose.
- 28:25That was the evidence payoff I had been
- 28:27looking for from the beginning. But it
- 28:29still left one question unresolved. Fair
- 28:32Haven Crossing had a lake. It had
- 28:34landscaping. It had a maintenance
- 28:37concern. None of that answered whether
- 28:39the HOA had any right to use water that
- 28:42was already scheduled to my ranch
- 28:44account. The gate log showed what
- 28:46happened. The allocation records would
- 28:48have to show whether they had any
- 28:49authority to do it. The allocation
- 28:52records answered the question the gate
- 28:53log could not. The HOA owned the lake.
- 28:57It did not own my irrigation delivery.
- 29:00That difference sat at the center of
- 29:02everything. The ditch company's account
- 29:04records showed my ranch as the active
- 29:06delivery account for the window when the
- 29:08gate had been changed. The turnout
- 29:10serving my property was tied to that
- 29:12account and the scheduled volume had
- 29:14been assigned before Claire's service
- 29:16request ever appeared in the system.
- 29:18Fair Haven Crossing had its own water
- 29:20related maintenance needs. It had
- 29:22landscaping. It had a decorative lake.
- 29:26It had infrastructure connected to the
- 29:28same broader ditch network. What it did
- 29:30not have was a record transferring my
- 29:32scheduled allocation into its control. I
- 29:36went through the account history
- 29:37carefully. There was no approved
- 29:39exchange, no temporary assignment, no
- 29:42written transfer, no emergency override
- 29:45giving the HOA priority over my ranch
- 29:48delivery. The records did not show any
- 29:50arrangement allowing Fair Haven Crossing
- 29:52to take water from my active window
- 29:55simply because the lake level was low.
- 29:57That was the legal reality I had been
- 29:59looking for. Owning the receiving pond
- 30:01did not create a right to whatever water
- 30:03could be made to flow into it. The water
- 30:06moving through the ditch system was
- 30:07tracked by delivery account and
- 30:09allocation. During those hours, that
- 30:12account was mine. The distinction became
- 30:14even clearer when I compared the
- 30:16delivery map with the HOA property map.
- 30:19Fair Haven Crossings common area sat
- 30:21north of the diversion point. My ranch
- 30:24turnout sat on a separate branch. The
- 30:26system served both areas, but the
- 30:28branches were not interchangeable just
- 30:30because they shared infrastructure
- 30:32upstream. That mattered because Clare's
- 30:34position had always rested on the
- 30:36practical fact that the HOA maintained
- 30:38the lake. The allocation records dealt
- 30:41with a different question. Who had the
- 30:43right to receive the scheduled water at
- 30:45that time? The answer was much narrower,
- 30:48my ranch. I also checked whether the HOA
- 30:52had any standing agreement with the
- 30:53ditch company that could complicate the
- 30:55issue. There were records for normal
- 30:57lake maintenance deliveries and common
- 30:59area irrigation periods. Those
- 31:02deliveries had their own windows,
- 31:04their own entries, their own operating
- 31:07instructions. None of them overlapped
- 31:09with a general right to alter my
- 31:11allocation. That removed another
- 31:13possible explanation. The lake did have
- 31:16legitimate water access, just not
- 31:18through my active delivery. The service
- 31:21request tied to Fair Haven Crossing
- 31:23began to look different once placed
- 31:25beside those records. It had described a
- 31:28lake level concern. The contractor
- 31:30responded at the control point. The gate
- 31:33was moved. The HOA side branch
- 31:36increased. My lateral was reduced, but
- 31:39the request itself did not create the
- 31:41authority to reassign water already
- 31:43scheduled to another account. That was
- 31:46the central mistake.
- 31:48Someone treated a maintenance request as
- 31:50if it could override an allocation. The
- 31:52records did not support that. By then,
- 31:55the ditch company had also started
- 31:57reviewing its own internal process. The
- 31:59question was no longer limited to why
- 32:01the gate moved. It became how an outside
- 32:04maintenance request reached the point
- 32:06where a contractor could change a
- 32:08control setting without verifying the
- 32:10active account. That procedural failure
- 32:13mattered because it explained how the
- 32:15diversion became possible. It did not
- 32:18change who was supposed to receive the
- 32:19water. I went back to the ranch after
- 32:22reviewing the allocation file. The upper
- 32:25pasture had stabilized somewhat after
- 32:27flow was restored. The winter feed
- 32:29acreage was still uneven. Some sections
- 32:32had recovered color. Others had lost
- 32:35enough growth that I could see the
- 32:36difference from the fence line. I
- 32:38photographed the same marked positions
- 32:40again. The damage was no longer
- 32:42developing as quickly, but it was
- 32:44measurable. That was important for what
- 32:47came next. The property side of the
- 32:49dispute was mostly settled. The water
- 32:52had been assigned. The gate had been
- 32:54adjusted. The diversion had been logged.
- 32:57The HOA request had been identified. The
- 33:00delivery account showed who should have
- 33:02received the flow. What remained was
- 33:04value. How much production had I
- 33:06actually lost? How much could be
- 33:08supported by records instead of
- 33:10frustration. I went back through
- 33:12previous irrigation cycles and compared
- 33:14similar heat periods. The same pasture
- 33:17had held more growth when the full
- 33:19delivery arrived on time. The winter
- 33:21feed acreage had produced more
- 33:23consistently under normal watering. I
- 33:26was not interested in claiming every dry
- 33:28blade of grass as damage. that would
- 33:30weaken the case. I needed a reasonable
- 33:32estimate tied to the acreage and the
- 33:34missed delivery period. The ditch
- 33:37company records helped there, too.
- 33:39Because the active window and gate
- 33:41adjustments were documented, the
- 33:42shortage had a defined beginning and
- 33:44end. That gave me a time period to
- 33:47compare against crop and pasture
- 33:48performance. Clare appeared one more
- 33:51time near the lake before the allocation
- 33:53review was complete.
- 33:55She stood beside the property management
- 33:57employee, red blazer bright against the
- 33:59pale shoreline. This time there was no
- 34:02contractor at the gate. No wrench, no
- 34:05adjustment. The lake level was lower
- 34:08than it had been during my scheduled
- 34:09run. The HOA landscaping remained green,
- 34:13but the inlet was no longer pushing the
- 34:15same volume. I photographed the scene
- 34:18from the roadside. The image was less
- 34:20dramatic than the first one. That was
- 34:22fine. The important part was already in
- 34:25the records. The legal twist was not
- 34:27that Fair Haven Crossing had no right to
- 34:29any water. It did. The twist was that
- 34:32its legitimate water rights did not
- 34:34include mine. The HOA could maintain its
- 34:38lake with water allocated to its own
- 34:40account. It could not convert a
- 34:42maintenance concern into control over a
- 34:44delivery already assigned to my ranch.
- 34:46The gate log showed the diversion. The
- 34:49allocation records showed why it was
- 34:51unauthorized. Those two pieces finally
- 34:54answered both halves of the dispute.
- 34:56What happened and who had the right to
- 34:59the water? The only unresolved question
- 35:01was what the documented shortage had
- 35:03cost me. The final stage of the dispute
- 35:06was less dramatic than the first
- 35:07afternoon at the gate. It was also more
- 35:10important. By then the central questions
- 35:13had been answered. My irrigation account
- 35:15had been active. The diversion gate had
- 35:18been adjusted during that window. The
- 35:20branch toward Fair Haven Crossing had
- 35:22received more flow. My ranch delivery
- 35:25had been reduced. The gate log recorded
- 35:28the change. The allocation records
- 35:30showed that the water scheduled during
- 35:32those hours belonged to my delivery
- 35:34account. What remained was damage. I
- 35:38started with the pasture. The sections
- 35:40closest to the turnout had recovered
- 35:42reasonably well once normal flow
- 35:44returned. Farther west, the stress had
- 35:46lasted longer. The winter feed acreage
- 35:49showed the clearest difference. Growth
- 35:51was thinner and less even than
- 35:53comparable sections from previous
- 35:54irrigation cycles. I measured the
- 35:57affected acreage and compared it with my
- 35:59own production records. I did not use
- 36:01the highest yield from a good year. I
- 36:04used conservative numbers from recent
- 36:06comparable conditions. The goal was not
- 36:08to inflate the claim. It was to make the
- 36:11loss difficult to dismiss. The shortage
- 36:13had a documented start. The restoration
- 36:16had a documented time that gave me a
- 36:19defined period of reduced delivery. The
- 36:22field photographs showed how the pasture
- 36:24changed during that period. The
- 36:26historical records showed how the same
- 36:28acreage normally performed when it
- 36:30received the scheduled water. The ditch
- 36:33company's records filled in the
- 36:34operational gap between those two
- 36:36points. That made the damage calculation
- 36:38much cleaner. Fair Haven Crossings
- 36:41insurer became involved. The
- 36:43contractor's insurance representative
- 36:45did too. The ditch company reviewed its
- 36:48own role separately because the
- 36:50adjustment had occurred through
- 36:51infrastructure under its control. Nobody
- 36:54needed a dramatic confrontation by then.
- 36:56The records had narrowed the dispute too
- 36:58far. The HOA had made a service request.
- 37:02The gate had been changed. The scheduled
- 37:05allocation had not been transferred. My
- 37:08ranch had received less water. The
- 37:10pasture had suffered measurable loss.
- 37:12The final financial resolution covered
- 37:15the reasonable value of the documented
- 37:17agricultural damage and the additional
- 37:19costs tied directly to the interrupted
- 37:22irrigation cycle. There was no enormous
- 37:25settlement, no fantasy penalty, no
- 37:28sudden courtroom victory. I recovered
- 37:31what the records supported. That was
- 37:33enough. The procedural changes mattered
- 37:36more. The ditch company changed how
- 37:39outside maintenance requests were
- 37:40handled at shared control points. A
- 37:43contractor could no longer adjust a
- 37:45turnout simply because a nearby customer
- 37:47reported a maintenance need. The active
- 37:50delivery account had to be checked
- 37:52first. Any requested change that could
- 37:54affect another customer's scheduled
- 37:56water required direct verification
- 37:58before the hardware was moved. The
- 38:01control gate itself received a clearer
- 38:03operating tag tied to the account
- 38:05schedule. Access to the adjustment
- 38:07mechanism was restricted. The contractor
- 38:10also received a revised procedure for
- 38:12fair haven crossing. HOA staff could
- 38:15report lake level concerns. They could
- 38:17request legitimate water service. They
- 38:20could schedule maintenance through their
- 38:21own account. They could not direct a
- 38:24field contractor to alter a shared
- 38:26diversion point without the ditch
- 38:28company confirming the active delivery.
- 38:30That distinction was now written down.
- 38:33Clare remained president of Fair Haven
- 38:35Crossing. I saw her several times after
- 38:38the claim was resolved. The red blazer
- 38:41was still easy to recognize, but I never
- 38:43again saw her standing beside that gate
- 38:45while someone adjusted it. That was the
- 38:48change I cared about. The next
- 38:50irrigation cycle arrived several weeks
- 38:53later. I drove to the turnout before the
- 38:55scheduled start. The gate position
- 38:58matched the company's operating plan.
- 39:00The control hardware was secured.
- 39:03The identification plate was clean and
- 39:05readable. When my delivery began, the
- 39:07flow at the ranch turnout rose steadily.
- 39:10I measured it at the same point I had
- 39:12used during the dispute. This time, the
- 39:14reading was where it should have been.
- 39:17Water moved through the lateral and
- 39:18spread across the pasture. The higher
- 39:21ground darkened as moisture reached it.
- 39:23The winter feed acreage took water
- 39:25evenly. I drove past Fair Haven Crossing
- 39:28later that afternoon. The decorative
- 39:30lake sat lower than it had during my
- 39:32stolen delivery window, but it was still
- 39:35healthy. The landscaping around it
- 39:37remained green. Nothing had collapsed.
- 39:40Nothing had been ruined. The HOA simply
- 39:43had to use the water available to its
- 39:45own account. That was the quietest part
- 39:47of the whole story. The conflict had
- 39:50never required one side to lose
- 39:52everything. It required the system to
- 39:54stop treating my allocation as available
- 39:56whenever somebody else wanted more. The
- 39:59photographs from the first afternoon
- 40:01remained in my phone. Clare beside the
- 40:03gate, the contractor on the hardware,
- 40:06the stronger flow moving north, my
- 40:08reduced turnout, the rising lake. But
- 40:12those images were not what finally
- 40:13settled the matter. The gate logs showed
- 40:16the adjustments. The allocation records
- 40:19showed who was entitled to the delivery.
- 40:21The field records showed what the
- 40:23shortage cost. Together they turned a
- 40:26suspicious drop in water into a
- 40:27documented sequence. I had started with
- 40:30one question. Why was my ranch running
- 40:32dry while the HOA lake kept filling? The
- 40:36answer turned out to be buried in
- 40:37ordinary operating records. A gate had
- 40:40been moved during my scheduled delivery.
- 40:43The water had been redirected. And once
- 40:45the ditch company's own log showed when
- 40:47and how it happened, Fair Haven Crossing
- 40:50could no longer treat the shortage as
- 40:51just another summer irrigation
About this transcript
This page contains the full transcript of HOA Diverted My Irrigation Water to Their Lake — Then the Ditch Company’s Gate Logs Exposed It by HOA LAND WARS, generated from the public captions YouTube serves with the video. The transcript has 6,680 words across 1,057 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.
What you can do with it
Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.
Free YouTube transcript tool
YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.