YT YouTube2Text

YouTube2Text → Transcripts → HOA Ordered My Avalanche Barrier Removed—Then the County Found It in Their Plan

HOA Ordered My Avalanche Barrier Removed—Then the County Found It in Their Plan — Transcript

by HOA Paper Trail · 6,144 words · 1,162 segments · language en · Watch on YouTube

Open in transcriber Summarize with AI Download SRT/VTT

Full transcript

0:00"That ugly wall comes out this week,"
0:02Dana Whitlock said, jabbing a finger
0:04toward the snow-covered barrier above my
0:06property.
0:07I looked at her, then at the steep slope
0:09behind it. "And who decided it was safe
0:12to remove?" Her expression hardened.
0:15"The board doesn't need your
0:16permission." I almost laughed. Not
0:19because it was funny, but because the
0:21barrier had been standing there longer
0:23than the HOA had, and nobody seemed
0:26interested in asking who put it there.
0:28Dana stood in the gravel turnout beside
0:31my truck, red blazer buttoned under a
0:33black winter coat she had left open
0:35despite the cold.
0:37Snow clung to the pine branches behind
0:39her, and the old barrier cut a dark line
0:42across the white slope above my house.
0:45She handed me a violation notice.
0:47The first page called it an unapproved
0:49architectural structure.
0:51The second gave me 30 days to submit a
0:54removal plan.
0:55After that, the association could begin
0:58daily fines.
0:59I read the notice once.
1:01"You've inspected it?" I asked. "Our
1:04architectural committee has reviewed the
1:06property." "That's not what I asked."
1:08Her mouth tightened.
1:10I pointed uphill. "Has anyone had an
1:13engineer look at that barrier before
1:15deciding it comes out?" Dana folded her
1:17arms. "It's visible from the road. It
1:20doesn't comply with current design
1:22standards, and the board voted to
1:24enforce the rule."
1:25The answer bothered me more than the
1:27fine. The barrier was not decorative. It
1:30was heavy steel-framed with thick
1:32weathered timbers anchored into the
1:34slope at an angle that made no sense for
1:36fencing or privacy. It had been there
1:38when I bought the house eight years
1:40earlier. The previous owner had never
1:42called it beautiful, but he had never
1:44called it optional, either.
1:46Dana tapped the notice with one gloved
1:48finger.
1:49"You have 30 days, Ethan. If you ignore
1:52this, the penalties escalate."
1:55"I'm not ignoring it."
1:56"Then remove it.
1:58I looked past her toward the slope.
2:01Fresh snow covered the upper ridge in a
2:03smooth white sheet. From the house, the
2:06barrier looked crude. Standing below it
2:09though, you could see how deliberately
2:11it had been placed across the fall line.
2:13Dana turned toward her SUV.
2:16Send your demolition plan to the
2:18committee by Friday. I watched her drive
2:20away, then carried the notice inside. I
2:23set it on the kitchen counter beside my
2:25keys and read the penalty schedule
2:27again. The amounts were not enormous at
2:29first, but they doubled quickly enough
2:31to make waiting expensive. Dana had
2:33given me a deadline designed to force
2:35action before I had time to ask whether
2:37removing the barrier was even
2:39responsible.
2:40On paper, Pine Hollow Ridge had reduced
2:43the whole problem to appearance. One
2:46structure, one violation, one deadline.
2:49But the barrier had been standing on
2:51that mountain before Dana joined the
2:53HOA, before the current board existed,
2:56and before I ever owned the property.
2:58If somebody had gone to the trouble of
3:00anchoring that much steel and timber
3:02into a steep Colorado slope, I wanted to
3:04know why.
3:06And more importantly, I wanted to know
3:08who had told them to do it.
3:11The next morning, I pulled the purchase
3:13file.
3:14I had bought the house eight years
3:15earlier from a retired ski patrol
3:17supervisor named Martin Vail. Back then,
3:21I cared about the roof, the workshop for
3:23my equipment repair business,
3:25and whether the access road stayed open
3:27through winter.
3:29The barrier above the house barely
3:30registered. Martin had called it part of
3:33the slope work. It was already old,
3:36weathered steel posts and heavy cross
3:38timbers anchored into the hillside. I
3:41assumed the developer had installed it
3:43and never asked who owned it or
3:44maintained it. Until Dana handed me that
3:47violation notice, I had never needed to.
3:49I I the closing packet across the
3:51kitchen table.
3:53Behind the inspection summary, I found a
3:56property condition attachment.
3:58Near the bottom was one line.
4:00Existing slope mitigation improvements
4:02observed above residential structure.
4:05I stopped with my thumb against the
4:06page.
4:07No diagram.
4:09No maintenance schedule. No explanation
4:11of what improvements meant. Still, it
4:14was the first document that described
4:16the work above the house as mitigation
4:18instead of appearance.
4:20I set it beside Dana's violation notice.
4:23One document treated the structure as
4:25part of the slope.
4:27The other treated it as an architectural
4:29problem. I called Martin.
4:31He sounded happy to hear from me right
4:33until I mentioned the barrier.
4:35You remember that structure above the
4:36place?
4:38A brief pause.
4:40Hard to forget. It's built like a tank.
4:43Did you build it?
4:44Ethan, I wouldn't spend that kind of
4:46money to block my own view. It was there
4:49before I bought the place.
4:51His voice had changed.
4:53Do you know who put it there?
4:55Not for certain. My inspector said the
4:57developer did the upper slope work
4:59before the road was finished. He told me
5:01not to mess with that thing unless
5:03somebody who understood the hillside
5:04looked at it first.
5:06Was that written anywhere? Not in
5:08anything I kept. And don't turn an old
5:11man's memory into a permit.
5:13I won't. I asked whether the HOA had
5:16ever bothered him about it. Martin gave
5:18a dry laugh. Back then, they cared about
5:21unpainted fences and trash cans. Nobody
5:23talked about taking that thing apart.
5:26Why not? Another pause.
5:29Because everybody treated it like it
5:30belonged to the mountain, not the house.
5:33What does that mean?
5:35It means if they're calling it
5:36decoration now,
5:38they may not know what they're looking
5:39at.
5:41Martin could not give me a drawing,
5:43approval number, or maintenance record.
5:45His memory was not evidence.
5:47But it pushed the timeline farther back.
5:50That afternoon, I went outside with the
5:52inspection packet under my coat. The
5:54posts were evenly spaced.
5:57The timbers sat at a deliberate angle.
5:59Each section followed the contour of the
6:01slope instead of the boundary of my
6:03yard.
6:04I stood under one steel upright and
6:06looked at the bolts disappearing into
6:08the hillside.
6:09Built like a tank no longer sounded
6:11exaggerated.
6:13I took photographs, touched nothing, and
6:16went back inside before the weather
6:17turned.
6:19Dana had reduced the problem to one
6:20sentence.
6:22It violated current architectural
6:23standards.
6:25The documents did not defeat that claim.
6:27They gave me a different question.
6:30If the barrier was one of the slope
6:31mitigation improvements noted when I
6:33bought the property, somebody had known
6:36what it was long before Dana called it
6:38an ugly wall. I opened the HOA portal
6:41and requested the oldest architectural
6:43files, subdivision plans, and every
6:45record tied to slope work above my lot.
6:48Then I wrote one phrase across the top
6:50of a yellow legal pad.
6:53Who installed it?
6:54By evening, snow had started again.
6:57I stood at the kitchen window and
6:58watched the barrier fade behind a thin
7:00white curtain.
7:02The question was no longer whether I
7:04liked how it looked. It was whether
7:06those four words, existing slope
7:09mitigation improvements, were describing
7:11the same structure Dana wanted gone.
7:14The first response from Pine Hollow
7:16Ridge arrived before breakfast on
7:18Monday.
7:19It was not a copy of anything old. It
7:22was a new enforcement letter.
7:24Dana had escalated the violation from a
7:26warning to a formal compliance action.
7:29The letter gave me 10 days to submit a
7:31demolition plan and said daily fines
7:34could begin immediately after the
7:35deadline if I failed to do it.
7:38I read the letter twice, then opened the
7:40HOA portal.
7:42The architectural guidelines were easy
7:44to find. They had been updated 3 years
7:47earlier and covered fences, sheds,
7:49retaining walls, satellite equipment,
7:51exterior lighting, and all visible
7:54structures not expressly exempted. The
7:57barrier above my house was not mentioned
7:59by name.
8:00Dana had classified it under that
8:02catch-all provision. I downloaded the
8:04guidelines and compared the effective
8:06date with the purchase file spread
8:08across my table.
8:10The barrier had been there long before
8:11those rules were adopted. That alone did
8:14not make the rule invalid.
8:17Associations updated standards and older
8:20structures could still become
8:21enforcement issues depending on the
8:23governing documents.
8:25But I wanted to know whether the board
8:27had ever treated this barrier as an
8:28architectural structure before.
8:30I sent a written request for the oldest
8:32file connected to my lot, including
8:35architectural approvals, violation
8:37history, maintenance records, and any
8:39documents referencing slope work above
8:41the property.
8:43Dana answered less than an hour later.
8:46There is no prior approval on file for
8:48the structure. That was all she wrote.
8:51I replied with a simpler question.
8:54Was there a prior violation?
8:56No answer.
8:58By noon, another notice appeared in the
9:00portal. This one included photographs
9:03Dana had taken from the internal road.
9:05The barrier looked exactly as it always
9:07had, weathered, dark, half buried in
9:10snow, running across the slope above the
9:13house.
9:14Under the photographs, somebody had
9:16typed, "Non-conforming visual
9:18obstruction inconsistent with current
9:21mountain view standards."
9:22That phrase told me plenty.
9:24Mountain view standards,
9:26not slope stability,
9:29not snow movement, not drainage,
9:32appearance. I called the association
9:35office and asked to speak with Dana.
9:37She came on the line. I'm trying to
9:39understand the basis for enforcement, I
9:41said.
9:43You told me the board reviewed this.
9:45What exactly did they review?
9:47The committee reviewed the structure
9:49under the architectural guidelines.
9:51Did they review any old development
9:53records?
9:54That isn't necessary for an
9:56architectural violation.
9:58Did they review anything from the
9:59county?
10:00A pause.
10:02Ethan, the issue is whether the
10:04structure complies with current
10:05community standards. That's not the only
10:08issue if it was installed for a reason.
10:11The board is not required to preserve
10:12every object a developer put on a
10:14hillside 20 years ago.
10:16That sentence stayed with me after the
10:18call ended. It was the first time Dana
10:20had acknowledged the possibility that
10:22the developer might have installed it.
10:25Not that she meant to.
10:27I wrote the sentence down anyway.
10:29That evening I received the board packet
10:31for the upcoming monthly meeting. Buried
10:34between landscaping contracts and snow
10:36removal bids was a short agenda item
10:38titled visual standardization upper
10:41ridge lots.
10:43I opened the supporting memo.
10:45The board wanted to improve what it
10:47called architectural consistency and
10:50view line quality before marketing began
10:53on a new phase of homes farther down the
10:55ridge.
10:56The memo listed several visible items
10:58the association wanted owners to remove
11:00or screen.
11:02Old propane cages,
11:04unpainted storage sheds,
11:06temporary fencing,
11:08and my barrier.
11:09Mine was the only item described as
11:12large slope structure.
11:14There was no engineering note attached,
11:16no hazard review,
11:18no reference to county planning.
11:20The board was treating everything on the
11:22list as a visual problem.
11:24That was the first real contradiction.
11:27If the barrier was nothing more than an
11:29ugly private structure,
11:30Dana's position made sense.
11:33If it had been installed as part of the
11:35development slope work, then lumping it
11:37together with storage sheds and fencing
11:40was a very different decision.
11:42I needed something older than the HOA's
11:44current rules.
11:46The next day, I drove to the county
11:48planning counter and asked whether they
11:50had archived subdivision materials for
11:52Pine Hollow Ridge.
11:54The planner at the desk, a man named
11:56Joel Ramirez, searched the system by
11:58subdivision name.
12:00Current files or original approvals?
12:03He asked.
12:05Original, if you still have them.
12:07He looked at me over the monitor.
12:09That could be a lot.
12:11I'm looking for anything tied to slope
12:13work above lot 27.
12:15Joel searched again, this time by parcel
12:18and development phase.
12:20A list of scanned documents appeared.
12:22Site plans,
12:24drainage exhibits, road profiles,
12:27a preliminary geotechnical memo.
12:30Several items had been digitized, others
12:32were marked archive only.
12:34Joel printed the index for me.
12:37Near the middle was a document titled
12:39Upper Slope Site Plan, Phase One.
12:42The plan had been reduced from a much
12:43larger sheet and several annotations had
12:46become gray smears.
12:48But one shape caught my attention.
12:51A dark line crossed the slope above the
12:53row of lots that included mine.
12:55It sat almost exactly where the barrier
12:57stood today.
12:58"What is that?" I asked. Joel leaned
13:01toward the page.
13:02"Can't tell from this copy."
13:04"There's no legend?"
13:06"Not on this sheet."
13:08He checked the index again.
13:10"There may be a larger original in the
13:12archive."
13:13I asked if I could request it. He gave
13:15me a form. I filled it out before
13:17leaving the counter.
13:20On the drive home, I kept thinking about
13:22that dark line. It might have been
13:24nothing.
13:25A contour notation, a temporary
13:27construction feature, a drainage
13:29element, a property management line,
13:32or the barrier.
13:34I refused to decide before I had the
13:36better copy. When I reached the house,
13:39Dana's SUV was parked near the turnout.
13:42She was standing beside the barrier
13:44access path with another board member,
13:46both looking uphill.
13:48I walked over. Dana held a clipboard.
13:51We're documenting the violation before
13:53the next compliance date. You're
13:56documenting it again? We need a current
13:58condition record. I pointed toward the
14:00barrier.
14:01Did you know there's an old site plan
14:03showing a structure in almost the same
14:05location? The other board member looked
14:07at Dana.
14:08Dana barely reacted. Old site plans do
14:12not override association rules.
14:14I didn't say they did.
14:16Then what are you suggesting? I'm
14:18suggesting you find out what you're
14:20ordering me to remove before you start
14:22finding me for not removing it. Her
14:24expression sharpened. We have a visible
14:27non-compliant structure. That is what
14:29the committee is addressing.
14:31Was it there when the subdivision was
14:33approved? I don't know. Was it installed
14:36by the developer? I don't know.
14:39Was it ever reviewed as part of slope
14:40mitigation?
14:42I don't know.
14:43That answer landed harder than I
14:45expected. Dana looked down at the
14:47clipboard.
14:49But none of that changes your deadline.
14:51I stared at her for a second. So the
14:53board doesn't know what it is, but
14:55you've already decided it has to come
14:57out.
14:58The structure violates the current
15:00standard. That was the whole argument.
15:03Not what the barrier did. Not why it had
15:06been built. Not whether anything else
15:08depended on it.
15:10Only that it was visible.
15:12After they left, I walked the length of
15:14the barrier from below. Snow had drifted
15:17against the lower timbers. Heavy bolts
15:19disappeared into steel brackets anchored
15:22deep into the slope. Nothing about it
15:24looked temporary.
15:26At the far end, partly hidden by brush,
15:29I found an old metal tag bolted to one
15:31of the posts.
15:33Most of the lettering had faded.
15:35I could make out a contractor name, or
15:38part of one, and a number beneath it.
15:41I photographed the tag and did not touch
15:42it.
15:43Back inside, I searched the contractor
15:46name.
15:47The company no longer existed, but an
15:49old business directory result described
15:51it as a mountain civil contractor
15:53specializing in slope stabilization,
15:56snow control installations, and drainage
15:58work.
15:59That was not proof that they had built
16:01my barrier for avalanche control.
16:04Contractors did many kinds of work.
16:06Still, the list of possibilities was
16:08narrowing.
16:10The next morning, Dana sent a second
16:12enforcement email.
16:14The board had confirmed the deadline.
16:16If I failed to submit a removal plan by
16:18Friday, the fine schedule would begin.
16:21Attached was the same architectural
16:23guideline I had already read.
16:25No old approval.
16:27No engineering review.
16:30No site plan.
16:31No explanation of the barrier's history.
16:34I printed the email and set it beside
16:36the blurry county plan.
16:38One document treated the barrier as an
16:40ugly structure that had to disappear.
16:43The other suggested someone had planned
16:45something in that exact part of the
16:46slope years before Dana ever saw it.
16:49I still did not know whether they were
16:51describing the same thing,
16:53but I finally knew what I needed to find
16:55out next.
16:56Was that dark line on the old site plan
16:59just another mark on a faded drawing?
17:01Or was it the first trace of the barrier
17:03the HOA wanted me to tear out?
17:06Joel called me just after 9:00 the next
17:07morning.
17:09"The archive pulled the original sheet,"
17:11he said.
17:12"If you want to see it at full scale,
17:14come in before 3:00."
17:16I was at the county building 40 minutes
17:18later.
17:19The planning archive was one floor below
17:21the public counter in a room that
17:23smelled of paper dust and old cardboard.
17:26Joel rolled a large plan tube onto a
17:28steel table and pulled out a sheet
17:30almost 4 ft wide.
17:32The reduced copy I had seen before had
17:35been a blur.
17:36This one was not.
17:38Pine Hollow Ridge phase one filled the
17:40page in fine black lines, road grades,
17:43lot boundaries, slope contours, drainage
17:46paths, and numbered call outs.
17:49The dark line above my lot was still
17:51there.
17:52Up close, it was not one line at all.
17:55It was a series of short connected
17:57segments set at an angle across the
17:59upper slope.
18:01Joel ran a finger near the call out
18:02without touching the paper.
18:04"Here," he said, "detail S4."
18:07I searched the legend.
18:10S4 did not say avalanche barrier.
18:13It said upper slope diversion structure,
18:15see geotechnical exhibit.
18:18That was enough to make my pulse jump,
18:20but not enough to settle anything.
18:22A diversion structure could serve
18:23several purposes.
18:26"Where's the exhibit?" I asked.
18:28Joel checked the archive index.
18:30"Separate submission, geotechnical
18:33package."
18:34He disappeared through a gray door and
18:36came back carrying a thick folder with a
18:37faded county stamp.
18:40Inside were slope profiles, drainage
18:42calculations, and a preliminary hazard
18:45memorandum prepared before the first
18:47homes were built.
18:48Most of it was technical. The map was
18:50not.
18:52A shaded hazard zone ran across the
18:54upper ridge.
18:55Several arrows pointed down slope. One
18:58of them ended near the area above my
19:00house.
19:01An attached exhibit showed three
19:03proposed mitigation features along the
19:05upper lots. One occupied almost the same
19:08position as the barrier above my house.
19:11I refused to call it a match.
19:13The drawing was old. The dimensions were
19:15hard to read.
19:17And a proposed feature on paper did not
19:19prove the exact structure had ever been
19:21built.
19:22Joel seemed to read my face.
19:24"You need the construction record." he
19:26said.
19:27We went back to the index.
19:29There were inspection notes for roads,
19:32drainage, foundations, and retaining
19:34work. Then Joel found a contractor
19:37submittal tied to the upper slope. The
19:39company name stopped me.
19:42Summit Ridge Civil Works.
19:44It matched the faded metal tag I had
19:46photographed on the barrier.
19:48I pulled out my phone and showed Joel
19:50the picture. He nodded once.
19:52"That gives you a connection, not
19:54necessarily the whole answer."
19:57The contractor file contained a purchase
19:59order, materials list, and inspection
20:01entries.
20:02It specified structural steel posts,
20:05treated timbers, anchor assemblies, and
20:08heavy hardware.
20:09But the file still did not say, in plain
20:12English, "This is Ethan Cole's avalanche
20:14barrier."
20:16The inspector's note used another
20:17phrase.
20:19"Upper slope diversion installation
20:20substantially complete."
20:23My yellow legal pad was filling quickly.
20:25Old site plan. Detail S4.
20:29Geotechnical exhibit.
20:31Summit Ridge Civil Works.
20:33Upper slope diversion installation.
20:35Every record pointed in roughly the same
20:37direction, but none answered the
20:39question alone.
20:40I requested copies of everything.
20:43Before I left, Joel searched the county
20:45system one more time.
20:47"There's a final subdivision approval
20:49letter." he said. "You may want that,
20:51too." The three-page letter referenced
20:53roads, drainage, emergency access, and
20:57completion of required mitigation items
20:59before final acceptance of phase one.
21:01One paragraph referred to upper slope
21:04protective measures shown in the
21:05approved geotechnical exhibits.
21:08No lot number, no maintenance
21:10assignment, useful but incomplete.
21:13On the drive home, I called the number
21:15on a business card Joel had given me for
21:17a licensed geotechnical engineer.
21:20Her name was Laura Bennett. I told her
21:23what I knew and what I did not.
21:25"I have an old development plan showing
21:27a diversion structure," I said. "I have
21:30a contractor record that might connect
21:32to the barrier above my house.
21:34The HOA wants me to remove it." There
21:36was a short silence.
21:38"Has anyone inspected the barrier in the
21:40field?" "Not an engineer."
21:43"Then don't draw conclusions from the
21:44paperwork yet." I liked her immediately.
21:48She asked me to email the site plan,
21:50geotechnical exhibit, contractor
21:52records, photographs, and the HOA
21:55notice.
21:56Two days later, she drove up in a white
21:58utility vehicle and spent nearly an hour
22:01studying the slope before saying much.
22:04Laura Bennett was 51, compact, direct,
22:08and dressed for cold weather rather than
22:10presentation.
22:11Dark insulated jacket, work pants,
22:13winter boots, safety glasses pushed up
22:16on her head.
22:17She started below the barrier, measuring
22:19post spacing, timber angles, anchor
22:22locations, and the direction each
22:24section faced. Then she walked farther
22:26down slope and studied the terrain from
22:28the side.
22:30"What are you looking for?" I asked.
22:32"Whether it was placed to stop
22:33something, redirect something, or just
22:36hold ground. Can you tell?"
22:39"Not yet."
22:40She climbed back toward the barrier,
22:43brushed snow from a steel bracket,
22:45measured the anchor hardware, then
22:47compared the structure with the
22:48engineering exhibit on her tablet. The
22:51drawing showed angled segments. So did
22:53the structure in front of us.
22:56Laura still refused to call them the
22:57same thing.
22:59"Geometry is one piece," she said.
23:01"Location is another. Materials are
23:04another. The real question is whether
23:06the installed feature follows the design
23:08intent closely enough to be considered
23:10part of the mitigation system.
23:12She asked where I had found the
23:14contractor tag.
23:15I led her to the far end.
23:17Snow had covered it again.
23:19She cleared the face carefully,
23:22photographed the faded name and number,
23:24then compared it with the contractor
23:26submittal.
23:27Same company, she said.
23:30My stomach tightened.
23:31So we have it.
23:33We have another connection.
23:35She said it so flatly that I laughed.
23:37You and Joel must have gone to the same
23:39school.
23:40No, we both know what happens when
23:42people fall in love with a conclusion
23:44before the evidence gets there.
23:46Laura walked the slope for another hour.
23:49She checked the barrier against the
23:50topography, photographed drainage paths,
23:53and examined old snow loading patterns
23:55around the posts.
23:57She never said the barrier was safe.
24:00She never said removing it would be
24:02dangerous.
24:03She said those were engineering
24:05conclusions, and she would not make them
24:07until she reviewed the full geotechnical
24:09package and compared the installation
24:11with the approved drawings.
24:14That was exactly the kind of answer I
24:16wanted, even if it meant waiting.
24:19While Laura worked, another email from
24:21Dana arrived. Subject: Final Reminder.
24:25The board expected my demolition plan by
24:28Friday.
24:29I showed Laura the message. She read it
24:32once. Did they provide an engineering
24:34basis for removal? No. Did they ask for
24:37one? No. She handed the phone back.
24:41I'm not commenting on their authority.
24:43I'm telling you I would not recommend
24:45altering this structure until it's
24:47function is verified.
24:49The sentence was careful, but it was the
24:51first professional warning I had heard
24:52about removal itself.
24:55The following morning, Laura asked me to
24:57meet her back at the county office.
24:59She had spent the night
25:01cross-referencing sheet numbers. On the
25:03archive table, she laid the geotechnical
25:06exhibit beside the final site plan and
25:08added a construction sketch I had not
25:10seen before.
25:12It came from the contractor file. The
25:14sketch showed post spacing, timber
25:17dimensions, anchor depth, and segmented
25:19alignment. Laura placed a transparent
25:22scale over it. "The field measurements
25:24are close," she said. "How close?"
25:27"Close enough that I need one more thing
25:29before I put anything in writing."
25:31"What?" "The final inspection or
25:34as-built record." Joel searched the
25:36index. There was one entry with no
25:38digital image attached. "Final upper
25:40slope inspection."
25:42"Archive only, 21 years old." Joel
25:46looked at the reference number and then
25:47at me.
25:48"This one may take a day or two." Dana's
25:51deadline was now 48 hours away. Every
25:54detail now carried more weight.
25:57I left the county building with copies
25:58of the old plans under my arm and
26:00Laura's warning in my head.
26:02By then, the investigation had moved
26:05beyond whether the barrier looked like
26:06something in an old drawing. The
26:08contractor matched. The location was
26:11close. The dimensions were close. The
26:14materials were close. And an inspection
26:17record existed for an upper slope
26:18installation.
26:20But the last link was still missing.
26:22Until we saw what the county inspector
26:24had actually signed off on 21 years
26:26earlier, I still could not say whether
26:29the structure above my house was the
26:30mitigation feature in those plans or
26:33merely something that looked almost
26:35exactly like it.
26:37Joel's email came in just before noon.
26:40The archive had found the final upper
26:42slope inspection.
26:43I drove back to the county building.
26:46Laura was already beside the steel
26:47archive table with Joel and a thin
26:50folder between them.
26:52The inspection record was shorter than I
26:54expected.
26:55One page. A stamped date. A contractor
26:58reference.
27:00A handwritten note from the county
27:01inspector.
27:02Laura read it silently, then slid it
27:05toward me.
27:06Upper slope diversion installation
27:08verified substantially in accordance
27:10with approved geotechnical detail S4.
27:14I looked at Laura. That's it?
27:16That's a very important piece, she said.
27:19But don't skip the rest. She placed the
27:22final inspection beside the contractor
27:24sketch, the approved geotechnical
27:26exhibit, and the site plan.
27:29Then she opened her field notebook.
27:31Post spacing.
27:33Segment angle.
27:35Anchor pattern.
27:36Timber dimensions.
27:38Position relative to the slope break.
27:41She had measured every one of them.
27:43The installed barrier at your property
27:45is not just in roughly the same place,
27:47she said.
27:49Its geometry pre-tracks the approved
27:51detail closely. Same segmented layout.
27:53Same orientation. Same structural
27:56concept. Same contractor. Same
27:59inspection trail. I stared at the
28:01papers.
28:02So it is the structure in the plan.
28:04In my opinion, yes.
28:06She tapped the final inspection.
28:09And that changes the question.
28:11Until then, Dana had treated the barrier
28:13as an old homeowner improvement that
28:15happened to offend current architectural
28:17standards.
28:19Laura was saying something very
28:20different.
28:22The structure had been installed as part
28:23of the original development work, not as
28:26a later private landscaping decision.
28:29I asked the question I had been
28:30avoiding.
28:31What does it actually do?
28:34Laura turned the geotechnical exhibit
28:36toward me.
28:37The easiest mistake is to think this is
28:39a wall designed to stop an avalanche
28:41head-on. It isn't.
28:43She traced the segmented alignment with
28:45her pen.
28:46The design intent is diversion.
28:49The slope geometry, angle of the
28:51segments, and placement are meant to
28:53influence the path of moving snow and
28:55loose surface material.
28:57Depending on conditions, the structure
28:59can reduce direct flow toward the
29:01developed lots and redirect part of that
29:04movement toward a less vulnerable path.
29:06Can it guarantee the house is safe?
29:09No.
29:10Can you guarantee removing it makes the
29:12house unsafe?
29:14No.
29:15She waited until I was looking directly
29:17at her.
29:18But removing a component from an
29:19approved mitigation system without
29:21analyzing the changed conditions would
29:24be irresponsible.
29:26Laura was not predicting disaster.
29:28She was saying the county approved
29:30system could not be treated like a fence
29:32someone disliked.
29:34The design had a function and changing
29:36it required engineering.
29:38Joel pulled the original subdivision
29:40approval letter across the table.
29:43One condition required completion of the
29:45protective measures shown in the
29:46approved geotechnical exhibits before
29:49final acceptance of phase one.
29:51Another referenced continued maintenance
29:53of designated slope control features
29:55under the development's operating
29:57documents.
29:59The maintenance responsibility was still
30:00unresolved, but there was no longer much
30:03mystery about why the barrier existed.
30:06The documents and field measurements
30:07pointed in the same direction, even if
30:10the maintenance question remained open.
30:13She had asked one question.
30:15Does this structure meet current
30:16appearance standards?
30:18The older records forced a different
30:20one.
30:21What authority did the association have
30:23to order removal of a county reviewed
30:25mitigation feature without first
30:27determining what function it served?
30:30Laura prepared a written engineering
30:32opinion that afternoon.
30:34She did not say the HOA had broken the
30:36law.
30:37She did not say the county owned the
30:38barrier.
30:40She did not say the barrier could never
30:41be modified.
30:43She stated what she could support.
30:46The existing structure corresponded
30:48closely with approved geotechnical
30:50detail S4.
30:52The contractor and inspection records
30:54tied the installation to the original
30:55subdivision work.
30:58Its configuration was consistent with a
31:00diversion function.
31:01Any removal, relocation, or material
31:04alteration should be preceded by
31:06engineering analysis of the slope
31:08conditions and the approved mitigation
31:10design.
31:12That was enough.
31:13I forwarded Laura's report, the county
31:16inspection record, the approved exhibit,
31:18and the original subdivision condition
31:20to Dana and the association's counsel.
31:23The reply did not come from Dana.
31:26It came from the HOA attorney. He asked
31:29that enforcement be temporarily paused
31:31while the board reviewed the historical
31:32approval package. The fine deadline was
31:35suspended. I read that sentence twice.
31:39For nearly 2 weeks, every message from
31:42Pine Hollow Ridge had pushed in one
31:43direction, remove the structure.
31:46Now the association wanted time. Not
31:49because I had shouted louder, because
31:51the question had changed from appearance
31:53to responsibility.
31:55Dana emailed me separately that evening.
31:58She wrote that the board had not been
31:59aware of the county inspection record
32:01when the violation was issued and that
32:03the architectural committee would review
32:05the new information.
32:07No apology.
32:09No admission.
32:10I did not need either one.
32:13The next morning, Laura met me at the
32:15property again.
32:16Snow had hardened along the upper slope
32:18overnight. She stood below the barrier
32:21and pointed toward the segmented line
32:22disappearing into the trees.
32:25"This is why engineers are careful with
32:27old infrastructure," she said.
32:29"Something can look obsolete long after
32:32people forget what problem it was built
32:33to solve."
32:35I looked at the heavy posts, weathered
32:37timbers, and steel brackets Dana had
32:40called ugly.
32:41Nothing about them had changed. Only the
32:44meaning had. But one question remained.
32:47The barrier had been installed under the
32:49subdivision's original mitigation plan.
32:52The county had inspected it.
32:54The engineering records showed why it
32:56existed.
32:57What nobody had yet answered was who, 21
33:00years later, was actually responsible
33:02for maintaining it. And whether Pine
33:04Hollow Ridge had inherited that duty
33:06along with everything else the developer
33:08left behind.
33:10The county's written response arrived
33:12the following Tuesday.
33:14Joel forwarded it before the planning
33:16department sent the formal copy to Pine
33:18Hollow Ridge.
33:20The letter did not declare who owned the
33:21barrier or order the HOA to maintain it.
33:25The structure above my lot appeared in
33:27the approved phase one hazard mitigation
33:29package, and the county would require
33:31technical review before any material
33:34alteration.
33:35The HOA scheduled a special board
33:37meeting.
33:38I went with Laura.
33:40Dana sat near the end of the table in
33:41her red blazer. Nobody mentioned how it
33:44looked. The association's attorney, a
33:47gray-haired man named Richard Hale,
33:49placed the county letter in the center
33:51of the table.
33:52He looked at Dana.
33:54When the committee issued the removal
33:56order, did anyone review the original
33:58phase one geotechnical package?
34:01Dana touched the edge of her blazer.
34:03That isn't part of our standard
34:05architectural checklist.
34:07Did anyone review it?
34:09No.
34:10Did you consult an engineer before
34:11ordering removal?
34:13We were evaluating compliance with
34:15visual standards.
34:16That wasn't my question.
34:18Her jaw tightened. No.
34:21Did anyone check the county planning
34:22file?
34:24No.
34:25Richard turned Laura's report toward the
34:27board. So, we ordered an owner to remove
34:29a structure before determining whether
34:31it was part of the subdivisions approved
34:33mitigation system.
34:35The room went silent.
34:36Dana tried again.
34:38It still does not comply with current
34:40appearance standards.
34:42That may be separate, Richard said.
34:45Appearance does not answer whether the
34:46association can order alteration of a
34:48county reviewed mitigation feature
34:50without technical review.
34:52Dana had no immediate reply.
34:55Laura stated only what her work
34:57supported. The barrier corresponded to
34:59the approved diversion detail closely
35:01enough that material alteration should
35:03be treated as an engineering matter, not
35:06routine cosmetic enforcement.
35:08Richard looked back at Dana.
35:10Was any of that known when the deadline
35:12was issued?
35:13No.
35:14Then the committee issued the deadline
35:16before it knew what it was ordering Mr.
35:18Cole to remove.
35:19Dana looked down.
35:21Then Richard moved to the harder
35:22question.
35:24Who was responsible for maintenance?
35:26Joel had found a turnover checklist from
35:28when the developer transferred common
35:30operations to Pine Hollow Ridge.
35:33It referenced designated slope control
35:35features for the association's
35:37maintenance program, but the attachment
35:39identifying them was missing.
35:42The board asked council to retrieve the
35:44complete package and withdrew my
35:45demolition deadline immediately.
35:48The fines were canceled.
35:50Dana objected once more that the barrier
35:52violated appearance standards.
35:54The board president looked at her.
35:56Then appearance gets reviewed after we
35:58know what we're responsible for.
36:01Two days later, the missing attachment
36:03came from the archive.
36:05The upper slope diversion feature
36:06serving the phase one ridge lots was
36:09listed as an association maintenance
36:10item. My lot was identified within the
36:13protected area.
36:15The document did not make Pine Hollow
36:17Ridge the owner of my land. It assigned
36:19the association an ongoing maintenance
36:21role for the mitigation feature the
36:23developer had installed.
36:25Council recommended suspending
36:27architectural enforcement, authorizing a
36:29current engineering inspection, and
36:31creating a maintenance schedule
36:33consistent with its original function.
36:35The board approved all three.
36:37Dana's violation notice was withdrawn.
36:40Her authority to issue removal orders
36:42involving safety-related infrastructure
36:44was narrowed.
36:46Future actions of that kind would
36:47require technical review and council
36:50approval before an owner received a
36:52deadline.
36:53The fine was gone.
36:55The barrier was staying.
36:57But one question still had to be
36:58resolved before I could call the matter
37:00finished.
37:02Who was going to pay for the engineering
37:03work, archive retrieval, and the
37:06maintenance the HOA had ignored for
37:08years?
37:09The final issue was money.
37:11Not the fines. Those were gone.
37:14The question was who would pay for the
37:16engineering review, archive work, and
37:19maintenance on a structure the HOA had
37:21nearly ordered me to remove?
37:23At the next regular board meeting,
37:25Richard Hale presented a recommendation.
37:28Pine Hollow Ridge would reimburse the
37:30county document fees and most of Laura's
37:32initial engineering bill because those
37:34costs had been triggered by the removal
37:36order. I would cover the small portion
37:39tied to work I had requested beyond the
37:41dispute.
37:42That felt fair.
37:44I had never wanted a windfall. I wanted
37:46the cost to follow the mistake.
37:48Then Laura's firm presented the
37:50condition assessment. The barrier did
37:52not need to be rebuilt. It needed care.
37:56Several timbers were weathered. Two
37:58anchor assemblies needed closer
38:00inspection.
38:01Debris had collected near the eastern
38:03end. Laura recommended replacing
38:06compromised wood, clearing that section,
38:09checking the anchors, and inspecting the
38:11structure after heavy snow seasons.
38:14The board approved the work and added
38:16the upper slope diversion feature to the
38:18association's long-term maintenance
38:20schedule.
38:21A month earlier, Dana had called it an
38:23ugly wall.
38:25Now it had an inspection interval, a
38:27maintenance budget, and a file number.
38:30Dana sat through the vote without
38:32speaking. She never apologized, and I
38:34did not ask her to.
38:36At the next architectural meeting, she
38:38was still in red and still unhappy
38:40whenever the barrier came up.
38:42But the board had changed the process
38:44around her.
38:46Future enforcement involving slope
38:48control or other safety-related
38:50infrastructure now required a records
38:52check before any removal notice.
38:54If the structure appeared in development
38:56or engineering files, technical review
38:59came first.
39:01No owner would be handed a demolition
39:03deadline simply because nobody knew what
39:05a structure was for.
39:07By late winter, the maintenance crew had
39:09replaced the worst timbers and cleared
39:11the buried end.
39:12Laura returned for the anchor checks and
39:14signed off on the work.
39:16Nothing dramatic happened afterward.
39:19No courtroom victory, no police, no
39:22public humiliation.
39:24The mountain did not care who had won
39:25the argument.
39:27One morning, after a storm moved through
39:29overnight, I stepped onto the porch with
39:32a cup of coffee.
39:33Fresh snow covered the rocks and roots
39:35above the house. The barrier cut across
39:38the white hillside in the same dark
39:40uneven line I had seen every winter
39:42since buying the place.
39:44For the first time, I understood why it
39:46had always looked slightly out of place.
39:49It was never designed to be beautiful.
39:52It was designed to do a job.
39:5421 years earlier, engineers had drawn it
39:57into a plan, a contractor had anchored
40:00it into the mountain, and a county
40:02inspector had signed off on the
40:03installation.
40:05Then people moved, boards changed, files
40:08disappeared into archives.
40:10Eventually, the reason was forgotten.
40:13The structure was not.
40:15That was Pine Hollow Ridge's real
40:17mistake. They confused forgotten history
40:20with useless history.
40:22Rules mattered, so did architectural
40:25standards.
40:26But before you order someone to tear out
40:28old infrastructure, you should know what
40:30problem it was built to solve.
40:32I finished my coffee and went back
40:34inside. The snow kept falling.
40:37The barrier stayed where it belonged. If
40:40your HOA has ever ordered you to remove
40:42or change something connected to safety,
40:44tell me what happened in the comments.
40:46And if you want more property conflict
40:48stories where the records change
40:50everything, subscribe.

About this transcript

This page contains the full transcript of HOA Ordered My Avalanche Barrier Removed—Then the County Found It in Their Plan by HOA Paper Trail, generated from the public captions YouTube serves with the video. The transcript has 6,144 words across 1,162 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 translate the transcript into 100+ languages.

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, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.