November 22, 2022- City of Santa Fe v. Albert Catanach, No. A-1-CA-38738

A-1-CA-38738Nmctapp

Texte intégral

Corrections to this opinion/decision not affecting the outcome, at the Court's discretion, can occur up to the time of publication
with NM Compilation Commission. The Court will ensure that the electronic version of this opinion/decision is updated accordingly
in Odyssey.
IN THE COURT OF APPEALS OF THE STATE OF NEW MEXICO	1
Opinion Number: ________________	2
Filing Date: November 22, 2022	3
No. A-1-CA-38738	4
CITY OF SANTA FE,	5
Petitioner-Appellee,	6
v.	7
ALBERT CATANACH; INFINITE	8
INTEREST ENT., LLC; and CNSP,	9
INC. d/b/a NMSURF,	10
Respondents-Appellants.	11
APPEAL FROM THE DISTRICT COURT OF SANTA FE COUNTY	12
David K. Thomson and Bryan Biedscheid, District Judges	13
Erin K. McSherry, City Attorney	14
Marcos D. Martinez, Senior Assistant City Attorney	15
Santa Fe, NM	16
for Appellee	17
Catron, Catron & Glassman, P.A.	18
Richard S. Glassman	19
Santa Fe, NM	20
for Appellants	21
Court of Appeals of New Mexico
Filed 11/22/2022 8:51 AM
OPINION	1
WRAY, Judge.	2
{1} 	In this appeal, we consider whether Petitioner-Appellee the City of Santa Fe	3
(the City) complied with federal laws that govern how local governments handle	4
applications relating to building, modifying, or relocating telecommunications	5
towers. Respondents-Appellants Albert Catanach, Infinite Interests, ENT., LLC, and	6
CNSP, Inc., d/b/a NMSURF (collectively, Applicant) submitted an application to	7
the City related to a telecommunications tower. Nearly a year later, Applicant	8
concluded the request had been “deemed granted” under federal law and so informed	9
the City. The district court granted the City’s subsequent petition for preliminary	10
injunction, denied Applicant’s motion to find the request “deemed granted,” and	11
denied Applicant’s motion to reconsider. We affirm in part, reverse in part, and	12
remand.	13
BACKGROUND	14
{2} 	The parties’ dispute centers on the City’s review of a telecommunications	15
facilities request in the context of multiple governing laws, including the City’s	16
permitting process; Section 332 of the federal Telecommunications Act, 47 U.S.C.	17
§ 332 (Section 332); the Middle Class Tax Relief and Job Creation Act of 2012	18
(Spectrum Act) § 6409, 47 U.S.C. § 1455 (Section 6409); and the corresponding	19
federal regulations. See In re Acceleration of Broadband Deployment by Improving	20
Wireless Facilities Siting Policies (FCC § 6409 Implementation Order), 29 FCC	21
2
Rcd. 12865, ¶¶ 191, 215-16 (Oct. 17, 2014), erratum 30 FCC Rcd. 31 (Jan. 5, 2015).1
1
Typically, the City applies Section 332 to review telecommunications applications	2
within 	the 	presumptively 	reasonable 	timeframes 	promulgated 	in 	the 	Federal	3
Communications Commission (FCC) regulations. See In re Petition for Declaratory	4
Ruling to Clarify Provisions of § 332(c)(7)(B) to Ensure Timely Siting Review & to	5
Preempt Under § 253 State & Local Ordinances that Classify All Wireless Siting	6
Proposals as Requiring a Variance (Reasonable Period of Time Ruling), 24 FCC	7
Rcd. 13994, ¶¶ 32, 42, 44-45 (Nov. 18, 2009).2 Applicant, however, invoked Section	8
6409, which (1) involves an expedited process under federal law and corresponding	9
FCC regulations; and (2) applies to “eligible facilities request[s],” defined as	10
requests to modify an existing telecommunications tower. See § 6409(a)(2). If the	11
application was an “eligible facilities request” under Section 6409, FCC regulations	12
require the City to respond to the application and act within 60 days, a far shorter	13
timeframe than the presumptively reasonable timeframes of 90 or 150 days 3
14
1In some publications, the FCC § 6409 Implementation Order is referred to
by its docket number, “FCC 14-153.” 	See, e.g., 	Portland Cellular P’ship v.
Inhabitants of Town of Cape Elizabeth, 139 F. Supp. 3d 479, 491 (D. Me. 2015).
2The Reasonable Period of Time Ruling is also sometimes referred to by its
docket number, “FCC 09-99.” See, e.g., ExteNet Sys., Inc. v. City of Cambridge,
Mass., 481 F. Supp. 3d 41 (D. Mass 2020).
3 The presumptively reasonable timeframes for local government action in
both Section 332 (90 or 150 days) and Section 6409 (60 days) are both referred to
as “shot clocks.” 	See In re Implementation of State & Local Governments’
Obligation to Approve Certain Wireless Facility Modification Requests Under
§ 6409(A) of the Spectrum Act of 2012 (In re Implementation of § 6409), 35 FCC
3
provided for under Section 332. See 47 C.F.R. § 1.6100(c)(2) (2021); Reasonable	1
Period of Time Ruling, 24 FCC Rcd. 13994, ¶ 4 (discussing Section 332 and defining	2
a reasonable timeframe of 90 days for review of collocation applications and 150	3
days for review of siting applications). Because the specific provisions of Section	4
332 (typical process) and Section 6409 (expedited process) are necessary to	5
understand the present case, we begin by briefly describing the applicable federal	6
law.	7
The Typical and the Expedited Processes	8
{3} 	Section 332 sets out what the City has described as the typical process	9
required of local governments when considering telecommunications requests.	10
Section 332 arose from Congress’s efforts “to promote competition and higher	11
quality in American telecommunications services and to encourage the rapid	12
deployment of new telecommunications technologies.” 	City of Rancho Palos	13
Verdes, Cal. v. Abrams, 544 U.S. 113, 115 (2005) (internal quotation marks and	14
citation 	omitted). 	In 	order 	to 	meet 	these 	goals, 	Congress 	imposed 	“specific	15
limitations on the traditional authority of state and local governments to regulate the	16
location, construction, and modification” of wireless communication facilities,	17
Rcd. 5977, ¶¶ 14-23 (June 10, 2020); FCC § 6409 Implementation, 29 FCC Rcd.
12865, ¶¶ 216, 254, 259 (discussing implementation of Section 6409, including
clarification of timeframes and “deemed grant” approach).
4
including timeframes for the local decision making process. Id. at 115-16. In relevant	1
part, Section 332 states,	2
(ii) A [s]tate or local government or instrumentality thereof shall act on	3
any request for authorization to place, construct, or modify personal	4
wireless service facilities within a reasonable period of time after the	5
request is duly filed with such government or instrumentality, taking	6
into account the nature and scope of such request.	7
(iii) Any decision by a [s]tate or local government or instrumentality	8
thereof to deny a request to place, construct, or modify personal	9
wireless 	service 	facilities 	shall 	be 	in 	writing 	and 	supported 	by	10
substantial evidence contained in a written record.	11
Section 332(c)(7)(B)(ii), (iii) (emphasis added). It is well established that Section	12
332 does not prevent a local government from requiring an applicant to comply with	13
local ordinances, regulations, and procedures, provided that local law comports with	14
the Section 332 shot clock and other requirements. See Nextel Partners of Upstate	15
N.Y., Inc. v. Town of Canaan, 62 F. Supp. 2d 691, 695 (N.D. N.Y. 1999) (“[Section	16
332] establishes the procedural requirements that local boards must comply with in	17
evaluating cell site applications, but the statute does not affect or encroach upon the	18
substantive standards to be applied under established principles of state and local	19
law.” (internal quotation marks and citation omitted)). The “reasonable period of	20
time” under Section 332(c)(7)(B)(ii) for local governments to respond to requests is	21
presumptively 90 or 150 days, depending on the type of request. See Reasonable	22
Period of Time Ruling, 24 FCC Rcd. 13994, ¶¶ 32, 42, 44-45. That shot clock can	23
be extended if the local government determines a Section 332 application is	24
5
incomplete and the government notifies the applicant within 30 days that it needs	1
additional information. Under those circumstances, “the time it takes for an applicant	2
to respond to a request for additional information will not count” toward the 90- or	3
150-day presumptively reasonable period of time for the local government to	4
respond. Reasonable Period of Time Ruling, 24 FCC Rcd. 13994, ¶ 53. In order for	5
the shot clock to toll, a local government’s “request for additional information must	6
specify the code provision, ordinance, application instruction, or otherwise publicly-	7
stated procedures that require the information to be submitted.” FCC § 6409	8
Implementation Order, 29 FCC Rcd. 12865, ¶ 260. Accounting for any tolling,	9
“[a]ny person adversely affected by any final action or failure to act by a [s]tate or	10
local government or any instrumentality thereof that is inconsistent with [Section	11
332(c)(7)(B)], within 30 days after such action or failure to act, commence an action	12
in any court of competent jurisdiction.” Section 332(c)(7)(B)(v).	13
{4} 	Some applications governed by Section 332 also fall within the purview of	14
Section 6409. As we have noted, Section 6409 requires local governments to engage	15
in an expedited review process of eligible facilities requests and act within 60 days	16
on applications “for [a] modification of an existing wireless tower or base station.”	17
Section 6409(a)(2). Modifications of towers, within the context of the Section 6409	18
6
expedited process, include removal, replacement, and collocation4 of equipment. See	1
id. If the modifications sought do not substantially change the physical dimensions	2
of the tower, notwithstanding other law, the local government “may not deny, and	3
shall approve” the eligible facilities request. Section 6409(a)(1); see 47 C.F.R.	4
§ 1.6100(c)(2) (“Within 60 days of the date on which an applicant submits a request	5
seeking approval under this section, the . . . local government shall approve the	6
application unless it determines that the application is not covered by this section.”).	7
{5} 	If the local government takes no action “to approve or deny a request seeking	8
approval under this section within the timeframe for review (accounting for any	9
tolling), the request shall be deemed granted.” 47 C.F.R. § 1.6100(c)(4). “The	10
deemed grant does not become effective until the applicant notifies the applicable	11
reviewing authority in writing after the review period has expired.” Id. Importantly,	12
the FCC adopted these regulations for Section 6409, but explicitly rejected the	13
“deemed 	granted” 	remedy 	for 	Section 	332 	violations. 	See 	FCC 	§ 6409	14
Implementation Order, 29 FCC Rcd. 12865, ¶¶ 281-84, 289; see also Reasonable	15
Period of Time Ruling, 24 FCC Rcd. 13994, ¶ 39. Instead, remedies for Section 332	16
violations are to be fashioned on a case-specific basis. Reasonable Period of Time	17
4Throughout this litigation, Applicant has relied on the term “collocation,”
which refers to placing additional transmission equipment on an existing tower or
base. See 47 C.F.R. § 1.6100(b)(2).
7
Ruling, 24 FCC Rcd. 13994, ¶ 39; see also FCC § 6409 Implementation Order, 29	1
FCC Rcd. 12865, ¶¶ 281-84.	2
{6} 	With this for context, we return to the facts of the present case.	3
The Approval Requests and Responses	4
{7} 	On April 9, 2015, Applicant sent an “application letter” to the City’s land use	5
department, specifically the land use director. Applicant requested to	6
collocate two towers on its building at [an address in Santa Fe, New	7
Mexico] approximately [thirty] feet south of the building on to one	8
tower located on the ground. This does not constitute a new tower;	9
however, a new tower would need to be built to collocate and	10
consolidate the existing two towers. These towers were approved by the	11
[C]ity respectively in 2005 and 2010.	12
Attaching the relevant federal regulations to the letter, Applicant sought approval	13
under Section 6409 and its expedited 60-day shot clock.	14
{8} 	The City’s senior land planner, Daniel Esquibel, responded by letter nineteen	15
days later on April 28, 2015 (Esquibel Letter). In relevant part, the Esquibel Letter	16
stated:	17
Your packet identified a request to construct an 80 foot high tower on	18
the property to the rear of the existing building. The proposed new	19
tower is to replace the existing two towers that extend through the roof	20
of the existing building. [Santa Fe, N.M., Code §] 14-6.2(E)(5)	21
“General Requirements” state that “all towers shall be set back a	22
distance equal to at least [100] percent of the height of the tower from	23
any adjoining lot line, measured from the base of the tower.” The tower	24
setbacks proposed identified setbacks are less than [100] percent of the	25
tower height (+/-16.8 feet from the rear property line, +/- 37.8 [feet]	26
from the north property line and +/- 47 feet from the south property	27
line).	28
8
In order to obtain[] the proposed setback requests a waiver must be	1
approved by the Planning Commission. This also shifts the authority of	2
review pursuant to [Section] 14-6.2(E)(3) to the Planning Commission.	3
Please contact [a named individual at a particular phone number] to set	4
up a pre-application conference to discuss application submittals and	5
fees, Early Neighborhood notification, and Planning Commission	6
review process.	7
If you have any questions regarding this matter, please do not hesitate	8
to contact me[.]	9
In response, on May 26, 2015, Applicant sent another letter, which attempted to	10
clarify that the request was “for permission to relocate certain equipment from one	11
or more towers on the roof of his building to a single similar tower on a nearby spot	12
on the ground.” Applicant requested that the City reevaluate its determination that	13
“the entire approval process” was necessary and noted the City’s previous setback	14
variance approval for the rooftop towers.	15
{9} 	In September 2015, the parties planned to meet to discuss the tower and,	16
specifically, 	Applicant’s 	ongoing 	argument 	that 	Section 	6409 	applied 	to 	the	17
application. Following the meeting, the City sent Applicant a letter that explicitly	18
rejected Applicant’s position that the tower project was “eligible” for review under	19
Section 6409. Seventy-one days later, on January 22, 2016, Applicant sent a new	20
“letter of application for relocation of telecommunications tower” and sought “to	21
remove these 2 towers and construct one (1) replacement tower” on the ground. After	22
three months passed, however, on April 28, 2016, Applicant reversed course. In	23
9
another letter, Applicant again asserted that Section 6409 applied to the request and	1
disagreed with the City’s interpretation of Section 6409. Applicant additionally	2
contended that the City had also failed to comply with Section 332. The April 28,	3
2016 letter informed the City that the Applicant now deemed the original application	4
granted under Section 6409 and would proceed with construction.	5
[Applicant] deems the application submitted to [the land use director],	6
via Certified Mail and by email on April 9 th
, 2015, GRANTED in	7
accordance with Section 6409a. Therefore, since there were no other	8
objections to the application, other than the set back issue, my client	9
will proceed forward with the modification of the towers in accordance	10
with the application and plans as submitted.	11
{10} 	The City responded a month later and “reject[ed the] letter’s conclusion that	12
the application has been deemed granted.” Applicant nevertheless built the tower,	13
which we will refer to as “the ground tower.”	14
The Petition for Injunction, Removal, and Remand	15
{11} 	The City red-tagged the ground tower and on July 14, 2016, filed a request for	16
a temporary restraining order, preliminary injunction, and permanent injunction in	17
the First Judicial District Court. Applicant removed the case to federal court and	18
filed an answer that included affirmative defenses and two counterclaims. One	19
counterclaim alleged that the City substantively did not comply with Section 332	20
(Counterclaim One). The other counterclaim (Counterclaim Two) first alleged that	21
the City failed to meet the Section 6409 60-day expedited timeline and, alternatively,	22
if the City had correctly decided that Section 6409 did not apply to the request, the	23
10
City was then obligated to resolve the request within the 90- or 150-day timeframe	1
under Section 332 and had failed to do so. The federal court remanded the case back	2
to state district court without addressing the merits. The City filed an answer to the	3
counterclaims in state district court and asserted that Applicant had been informed	4
about the necessary steps to obtain the permit under the City’s ordinances and that	5
Applicant caused any delay. In addition, the City pleaded as an affirmative defense	6
that Applicant’s counterclaims had “failed to state a cause of action on legal	7
grounds” because Applicant “started (and then deliberately abandoned) an attempt	8
to receive city approval.”	9
{12} 	The district court held a hearing, granted the City’s petition for a preliminary	10
injunction, and enjoined any additional work on the ground tower during the	11
pendency of these proceedings. Soon afterward, Applicant filed a motion for	12
summary judgment and argued that the City had violated both Section 6409 and	13
Section 332. Applicant also sought a stay of the preliminary injunction in order to	14
allow Applicant to move certain antennas from the roof to the ground tower. On	15
March 30, 2017, the district court denied Applicant’s summary judgment motion and	16
the request for stay.	17
The “Deemed Grant” Summary Judgment Motion	18
{13} 	In 2018, the parties brought two separate motions to district court for decision:	19
(1) the City’s motion challenging a second “deemed grant” letter sent by Applicant	20
11
relating to the roof antennas and asking the court to prohibit the installation; and (2)	1
Applicant’s renewed motion for summary judgment, which relied solely on Section	2
6409 and the ground tower. Despite the different factual bases for the motions, as	3
we will explain, the district court treated the motions as cross-motions and granted	4
the City’s motion and denied Applicant’s renewed motion. To understand the issues	5
before us on appeal, it is necessary to appreciate the way the parties framed the issues	6
for the district court.	7
{14} 	Though Applicant’s renewed summary judgment motion was limited to the	8
application of Section 6409 to the ground tower, the City’s response addressed	9
Section 332 and offered an explanation for how Section 332 works, characterizing	10
Section 6409 as an expedited Section 332 process. According to the City, because	11
the Esquibel Letter was sent within the Section 6409 timeframes, the letter qualified	12
as a proper and timely denial of Applicant’s request under both Section 332 and	13
Section 6409. In reply, Applicant disagreed with the City’s characterization of	14
Section 6409 and stated that “[a]s a matter of law, Section 6409 governed the	15
[a]pplication to the exclusion of Section 332.” Applicant argued that (1) Section	16
6409 “stands apart” from Section 332; (2) Section 6409 applied notwithstanding	17
Section 332; and (3) the City failed to comply with Section 6409. Applicant	18
additionally maintained that even if Section 332 applied, the Esquibel Letter was an	19
12
insufficient denial under Section 332, and the City had failed to act in “a reasonable	1
amount of time.”	2
{15} 	At the hearing on both parties’ summary judgment motions, the district court	3
asked the parties whether the “deemed granted analysis” under Section 6409 would	4
“dispose of whether [Applicant] is entitled to put any kind of tower on that building;”	5
and if the court’s ruling on the two pending summary judgment motions would	6
“dispose of the case.” Specifically, the district court inquired whether other reasons,	7
apart from the deemed grant issue under Section 6409, could justify lifting the	8
injunction to either allow the tower construction or the placement of antennas.	9
Applicant stated that while the motions were about different pieces of equipment	10
(the ground tower and antennas), the motions could be addressed at the same time	11
because they involved the same statute and legal question. The City acknowledged	12
that if the Esquibel Letter “is insufficient, then [Applicant] has strong grounds to say	13
that he can invoke deemed granted” under Section 6409. In response, Applicant	14
reiterated the argument that the Esquibel Letter was insufficient under Section 6409	15
because it did not “even come close” to stating whether the request was covered by	16
Section 6409 nor was it a “final letter” that would give Applicant grounds to invoke	17
any appellate process.	18
{16} 	The district court granted the City’s motion to prohibit placement of antennas	19
and denied Applicant’s motion. The district court found as follows:	20
13
Applying the applicable rules, the April 9, 2015 letter by [Applicant] to	1
the City regarding the plans to build a new tower in which the current	2
equipment would be transferred from the existing two towers to the	3
new, higher tower located in a different location on the ground, cannot	4
be read as anything other than a request to build a new tower. It is not	5
a modification to an existing tower, it is a new tower.	6
As a result of this finding, the district court determined that the Esquibel Letter,	7
“could have been more clearly written, but the intent of the letter was to notify	8
[Applicant] that the tower proposed is a new tower, it does not meet the setback	9
requirements and [Applicant’s] request must go through the application process.”	10
Continuing, the district court concluded, “[h]ad the City stamped the word ‘denied,’	11
it would have resolved sooner the questions litigated in this lawsuit, but a plain	12
reading of the letter makes clear that the application to build a new tower is not a	13
modification and needs to comply with the rules for new towers.” 5
14
{17} 	Applicant filed a motion to reconsider. The motion raised multiple issues, but	15
in relevant part challenged the district court’s failure to address Section 332. At the	16
hearing on the motion to reconsider, Applicant argued that the district court’s ruling	17
that the Esquibel Letter communicated noncoverage under Section 6409 was wrong	18
as a matter of law and that even if the Esquibel Letter was a sufficient notice of	19
noncoverage, the City was then obligated to review the request under Section 332.	20
5The district court did not separately analyze the City’s summary judgment
motion relating to the antennas, and we therefore do not reach the issues concerning
the placement of antennas on the ground tower.
14
When the district court asked whether a single letter could indicate that the request	1
was not covered by Section 6409 and also deny the request under Section 332,	2
Applicant declared that it would “bogle[] the mind” that the Esquibel Letter could	3
be both given that it did not reference either statute. Applicant maintained the	4
position that the City was required to provide clear notice of its decision that Section	5
6409 did not cover the request, and the City was then required to consider the request	6
under Section 332.	7
{18} 	The City, in response, characterized the district court’s original order as	8
establishing that “this [was] not an eligible facilities request [under Section 6409]	9
because it wasn’t an existing tower” and that the law did not require the City to issue	10
a notice that Section 6409 did not apply. Regarding Section 332, the City argued that	11
Applicant had elected to proceed under Section 6409, the Esquibel Letter was also a	12
denial under Section 332, and Applicant could have sought judicial review of any	13
Section 332 denial. The district court denied the motion to reconsider. Applicant	14
appealed.	15
DISCUSSION	16
{19} 	On appeal, Applicant contends that the ground tower application should have	17
been “deemed granted” under Section 6409 because the City failed to appropriately	18
respond within 60 days of the request, and a permit should otherwise issue because	19
the City failed to comply with the procedural requirements of Section 332. We	20
15
review de novo both issues of statutory construction and summary judgment rulings.	1
See State Pub. Educ. Dep’t v. Zuni Pub. Sch. Dist., 2018-NMSC-029, ¶ 17, 458 P.3d	2
362.	3
I. 	Our Appellate Jurisdiction	4
{20} 	We begin our discussion by raising and resolving the question of this Court’s	5
jurisdiction. See Smith v. City of Santa Fe, 2007-NMSC-055, ¶ 10, 142 N.M. 786,	6
171 P.3d 300 (“[I]t is incumbent upon the appellate court to raise jurisdiction	7
questions sua sponte when the Court notices them.”). As we have explained,	8
Applicant brought two counterclaims: Counterclaim One, relating to the substance	9
of Section 332 and Counterclaim Two, invoking Section 6409. Applicant voluntarily	10
dismissed Counterclaim One but maintained Counterclaim Two, which included—	11
in addition to his Section 6409 invocation—an allegation that, in the alternative, the	12
City failed to comply with Section 332’s procedural timeframes. The district court’s	13
summary 	judgment 	and 	reconsideration 	orders 	do 	not 	explicitly 	dismiss	14
Counterclaim Two or refer to the portion of that counterclaim that argued the City	15
had failed to comply with Section 332. We therefore must consider whether the	16
district court’s orders resolved Counterclaim Two so that the orders are final and	17
properly before us. See Rule 1-054(B) NMRA (“If an action presents more than one	18
claim for relief, whether as a claim, counterclaim, cross[-]claim, or third-party claim,	19
. . . the court may direct entry of a final judgment about one or more, but fewer than	20
16
all, claims or parties, only if the court expressly finds no just reason for delay.”); see	1
also Clinesmith v. Temmerman, 2013-NMCA-024, ¶ 35, 298 P.3d 458 (“The general	2
rule in New Mexico for determining the finality of a judgment is that an order or	3
judgment is not considered final unless all issues of law and fact have been	4
determined and the case disposed of by the trial court to the fullest extent possible.”	5
(internal quotation marks and citation omitted)).	6
{21} 	As we have explained, the City framed the Section 6409 issue as a subset of	7
Section 332 analysis and suggested that the Esquibel Letter satisfied its obligations	8
under both Section 332 and Section 6409. Applicant maintained that the two laws	9
were completely separate and the City had separate obligations under each. In the	10
order granting summary judgment, the district court concluded that Section 6409 did	11
not apply, and as a result, Applicant “must proceed to follow the application process	12
for a new tower.” The district court ordered that “the injunction will remain in place	13
until [Applicant] applies for and obtains the proper building permit” and that the	14
“case is dismissed.” Based on our review of the proceedings, as set forth in preceding	15
paragraphs, we conclude that the district court adopted the City’s view that	16
compliance with Section 6409 also included and satisfied the City’s Section 332	17
obligations. We will address the substance of the district court’s ruling shortly, but	18
for the purposes of finality, the district court resolved all issues of law and fact and	19
fully disposed the case. See Clinesmith, 2013-NMCA-024, ¶ 35 (explaining that the	20
17
general rule of finality “is not inflexible” and “is to be given a practical, rather than	1
a technical, construction” (internal quotation marks and citation omitted)). We	2
therefore turn to the merits of the appeal.	3
II. 	The Application of “Deemed Granted” Under Section 6409	4
{22} 	Applicant argues that the 60-day shot clock expired under Section 6409	5
because the Esquibel Letter (1) resulted in “a failure to act under Section 6409” and	6
47 C.F.R. § 1.6100(c)(4); and (2) was not a final appealable determination.6 The City	7
argues that the Esquibel Letter communicated to Applicant that Section 6409 did not	8
apply because in the City’s view, the application was for a new tower. We agree with	9
the City that the Esquibel Letter adequately communicated to Applicant the City’s	10
position that Section 6409 did not cover the request. See 47 C.F.R. § 1.6100(c)(2)	11
(requiring a locality to approve an application within 60 days unless “the application	12
is not covered by this section”). We further conclude that the Esquibel Letter was	13
sufficiently reviewable under Section 6409. Having communicated its decision that	14
Section 6409 did not apply with a sufficiently reviewable letter within 60 days, we	15
hold that the City complied with the Section 6409 shot clock. To explain these	16
conclusions, we return to the language of Section 6409 and its implementing	17
regulations.	18
6Applicant additionally argues that the Esquibel Letter did not toll the Section
6409 shot clock. Because the City does not rely on tolling, we do not engage in a
tolling analysis.
18
A. 	The Esquibel Letter Was a Notice That Section 6409 Would Not Apply	1
{23} 	The expedited process set forth in Section 6409 applies to “any eligible	2
facilities 	request 	for 	a 	modification 	of 	an 	existing 	wireless 	tower.” 	Section	3
6409(a)(1). An “existing” wireless tower is defined by the regulation: “A constructed	4
tower or base station is existing for purposes of this section if it has been reviewed	5
and approved under the applicable zoning or siting process, or under another [s]tate	6
or local regulatory review process.” 47 C.F.R. § 1.6100(b)(5). Thus, Section 6409	7
applies only to eligible facilities requests for existing wireless towers.	8
{24} 	In the request, Applicant stated, “This does not constitute a new tower;	9
however, a new tower would need to be built to collocate and consolidate the existing	10
two towers.” (Emphasis added.) The request included explicit references to Section	11
6409 and provided copies of the regulations. Despite having noted that a new tower	12
would need to be built, Applicant averred, “[A]s these are existing towers and we	13
are simply collocating them to a different location” the normal process pursuant to	14
the ordinance would not apply.	15
{25} 	In response, the Esquibel Letter stated the City’s position that the author had	16
“reviewed the information provided” and notified Applicant that (1) “[t]he proposed	17
new tower” would replace the existing two towers; and (2) Applicant would be	18
required to comply with setback requirements and obtain a variance. The Esquibel	19
Letter describes the setback requirements under the City’s ordinances, explains that	20
19
the proposed setback requires a waiver approved by the Planning Commission, and	1
indicates that “[t]his also shifts the authority of review pursuant to [Section] 14-	2
6.2(E)(3) to the Planning Commission.” In the context of these communications, the	3
Esquibel Letter communicated to Applicant that Section 6409, which Applicant	4
invoked and provided for the City’s consideration, did not apply to what the City	5
determined to be a “new tower.”	6
{26} 	Applicant contends that the Esquibel Letter was not a determination under	7
Section 6409 because (1) the letter “did not mention or show awareness of Section	8
6409” or request more information; (2) the letter looks like a “standard land use	9
letter;” and (3) Esquibel did not later characterize the letter as a Section 6409	10
determination. 	For 	these 	reasons, 	Applicant 	argues 	that 	the 	City 	made 	no	11
determination at all under Section 6409. This argument disregards the May 26, 2015	12
letter that Applicant sent in response to the Esquibel Letter. In the response letter,	13
Applicant disputed the City’s assertion that Applicant must “go through the entire	14
approval process to relocate his tower in the same manner as if approval for such a	15
structure had never been granted to him.” Despite the deficiencies in the Esquibel	16
Letter identified by Applicant on appeal, Applicant’s letter sent in response to the	17
Esquibel Letter demonstrates that Applicant understood that the City was refusing	18
to apply the Section 6409 expedited process. Having concluded that the Esquibel	19
20
Letter was notice to Applicant that Section 6409 would not apply, we next consider	1
the reviewability of the Esquibel Letter.	2
B. 	The Esquibel Letter Was Reviewable as a Claim Related to Section 6409	3
{27} 	Applicant maintains that the deemed grant determination was appropriate	4
because the Esquibel Letter was not a “final, appealable action” and instead sent the	5
request “into some kind of legal purgatory.” None of Applicant’s arguments,	6
however, acknowledge the limited finality requirements set forth in the Section 6409	7
corresponding regulations. Specifically, the “remedies” provision of 47 C.F.R.	8
§ 1.6100(c)(5) states that “[a]pplicants and reviewing authorities may bring claims	9
related to Section 6409(a) to any court of competent jurisdiction.” In FCC § 6409	10
Implementation Order, the FCC explained that appeals or claims related to Section	11
6409 “would appear likely to fall into one of three categories.” 29 FCC Rcd. 12865,	12
¶ 236.	13
First, if the [s]tate or local authority has denied the application, an	14
applicant might seek to challenge that denial. Second, if an applicant	15
invokes its deemed grant right after the requisite period of [s]tate or	16
local 	authority 	inaction, 	that 	reviewing 	authority 	might 	seek 	to	17
challenge the deemed grant. Third, an applicant whose application has	18
been deemed granted might seek some form of judicial imprimatur for	19
the grant by filing a request for declaratory judgment or other relief that	20
a court may find appropriate.	21
21
Id. Section 6409 does not appear to require a “final order” or “final determination”—	1
just a denial, a grant, or a “deemed grant.”7
2
{28} 	In the present case, as we have already determined, the Esquibel Letter was a	3
sufficient notice of noncoverage (or denial), which effectively communicated that	4
the City would not apply Section 6409. Applicant nevertheless contends that because	5
the City’s pleadings stated no final order had issued and the letter could not be	6
appealed under the City’s code, the Esquibel Letter was not a sufficient notice of	7
noncoverage. While the Esquibel Letter might not permit an administrative appeal	8
under the City’s code, the letter could support a claim in any “court of competent	9
jurisdiction” because the letter is “related to Section 6409(a).” See 47 C.F.R.	10
§ 1.6100(c)(5). We are therefore unpersuaded by Applicant’s argument that the	11
Esquibel Letter was insufficiently final or unreviewable and affirm the district	12
court’s ruling in this regard.	13
7We note that in the motion to reconsider, Applicant took umbrage with the
district court’s observation that had the City stamped “denied” on Applicant’s
request letter, the matter would have been resolved sooner. Applicant argued that the
district court’s order must have been referencing Section 332, “because you can’t
deny in [Section] 6409” and the order was “really confusing.” The FCC, however,
also has used the term “denial” when referring to a notice of noncoverage under
Section 6409. Therefore, while we understand Applicant’s position on the matter,
we purposefully use the term “denial” in accordance with the FCC’s guidance.
22
III. 	The Application of Section 332	1
{29} 	Applicant last argues that the City failed to comply with Section 332(c)(7)’s	2
procedural requirements. 8 Specifically, Applicant contends that the City did not	3
issue a final, appealable, written denial under Section 332, “supported by substantial	4
evidence contained in a written record.” Section 332(c)(7)(B)(iii). As a remedy for	5
these alleged deficiencies, Applicant seeks the issuance of the permit for the ground	6
tower. The City contends that Applicant failed to timely appeal Section 332 issues,	7
and regardless of the appeal’s timeliness, the Esquibel Letter was sufficient to satisfy	8
the procedural requirements of Section 332(c)(7). In reply, Applicant claims that the	9
City waived any argument that the Section 332 appeal is untimely by failing to plead	10
such a defense in the answer to Applicant’s counterclaims.	11
{30} 	We set out the parties’ appellate arguments to highlight the narrow decision	12
the district court made in this case and the resulting narrow window for our review.	13
Generally, our review is limited to whether the appellant meets the burden to	14
demonstrate 	error by the district court. 	See Farmers, Inc. 	v. 	Dal 	Mach. 	&	15
Fabricating, Inc., 1990-NMSC-100, ¶ 8, 111 N.M. 6, 800 P.2d 1063 (“[The	16
8Applicant solely challenges the Esquibel Letter’s adherence to the procedural
aspects of Section 332 and does not appear to challenge or argue that even if the
Esquibel Letter was procedurally sufficient under Section 332(c)(7), the letter was
substantively 	incorrect. 	Such 	a 	contention 	formed 	the 	basis 	for 	Applicant’s
Counterclaim One, which was dismissed by stipulation and therefore is not before
us.
23
a]ppellant must affirmatively demonstrate its assertion of error.”). In the present	1
case, the district court decided that the City complied with Section 6409 and	2
Applicant had to obtain a permit. As we have explained, we understand the district	3
court’s determination to rest on a legal conclusion that the City’s compliance with	4
Section 6409 and its timeframes also satisfied the requirements of Section 332. We	5
disagree with that legal conclusion because the two procedures are separate under	6
the applicable law. As we explain below, Applicant is entitled to a ruling on the	7
Section 332 claim.	8
{31} 	Section 6409(a)(1) begins by stating, in general, “[n]otwithstanding [S]ection	9
[332] or any other provision of law, a [s]tate or local government may not deny, and	10
shall approve, any eligible facilities request for a modification of an existing wireless	11
tower or base station that does not substantially change the physical dimensions of	12
such tower or base station.” The FCC has explained that when both Section 6409	13
and Section 332 apply, “if the reviewing [s]tate or municipality finds that Section	14
6409(a) does not apply (because, for example, it proposes a substantial change), we	15
provide that the presumptively reasonable timeframe under Section 332(c)(7) will	16
start to run from the issuance of the [s]tate’s or municipality’s decision that Section	17
6409(a) does not apply.” FCC § 6409 Implementation Order, 29 FCC Rcd. 12865,	18
¶ 220. The government may seek additional information to evaluate an application	19
under Section 332, “subject to the same limitations applicable to other Section	20
24
332(c)(7) reviews.” FCC § 6409 Implementation Order, 29 FCC Rcd. 12865, ¶ 220.	1
Thus, when the City sent the Esquibel Letter notifying Applicant of noncoverage,	2
the matter reverted to a Section 332 determination, and the associated timeframes	3
and requirements began to run.	4
{32} 	Viewing the proceedings as a whole, we conclude that the district court	5
conflated 	the 	Section 	6409 	determination 	with 	the 	necessary 	Section 	332	6
determination. We must therefore remand for further proceedings to allow the	7
district court to consider and resolve the Section 332 arguments that the parties have	8
raised on appeal.	9
CONCLUSION	10
{33} 	We hold that the district court properly denied Applicant’s “deemed granted”	11
motion as it pertains to Section 6409 and affirm the district court on that issue. We	12
remand to allow the district court to resolve in the first instance the issues raised by	13
the parties on appeal concerning the City’s compliance with Section 332 procedures.	14
{34} 	We 	therefore 	affirm 	in 	part, 	reverse 	in 	part, 	and 	remand 	for 	further	15
proceedings.	16
{35} 	IT IS SO ORDERED.	17
______________________________	18
KATHERINE A. WRAY, Judge	19
25
WE CONCUR:	1
__________________________	2
MEGAN P. DUFFY, Judge	3
__________________________	4
JANE B. YOHALEM, Judge	5

1 printed pages contain little extracted OCR body text; searchable legal-body completeness has not been established for those pages.

OCR transcription for search; preserved printed pages are authoritative

Corrections to this opinion/decision not affecting the outcome, at the Court's discretion, can occur up to the time of publication with NM Compilation Commission. The Court will ensure that the electronic version of this opinion/decision is updated accordingly in Odyssey.
IN THE COURT OF APPEALS OF THE STATE OF NEW MEXICO
Opinion Number:
Filing Date: November 22, 2022
No. A-1-CA-38738
CITY OF SANTA FE,
Petitioner-Appellee,
V. ALBERT CATANACH; INFINITE INTEREST ENT., LLC; and CNSP, INC. d/b/a NMSURF,
Respondents-Appellants.
APPEAL FROM THE DISTRICT COURT OF SANTA FE COUNTY David K. Thomson and Bryan Biedscheid, District Judges
Erin K. McSherry, City Attorney Marcos D. Martinez, Senior Assistant City Attorney Santa Fe, NM
for Appellee
Catron, Catron & Glassman, P.A. Richard S. Glassman
Santa Fe, NM
for Appellants
Court of Appeals of New Mexico Filed 11/22/2022 8:51 AM
Mark Reynolds
1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
16 17 18 19 20 21

OPINION	1
WRAY, Judge.	2
{1} 	In this appeal, we consider whether Petitioner-Appellee the City of Santa Fe	3
(the City) complied with federal laws that govern how local governments handle	4
applications relating to building, modifying, or relocating telecommunications	5
towers. Respondents-Appellants Albert Catanach, Infinite Interests, ENT., LLC, and	6
CNSP, Inc., d/b/a NMSURF (collectively, Applicant) submitted an application to	7
the City related to a telecommunications tower. Nearly a year later, Applicant	8
concluded the request had been “deemed granted” under federal law and so informed	9
the City. The district court granted the City’s subsequent petition for preliminary	10
injunction, denied Applicant’s motion to find the request “deemed granted,” and	11
denied Applicant’s motion to reconsider. We affirm in part, reverse in part, and	12
remand.	13
BACKGROUND	14
{2} 	The parties’ dispute centers on the City’s review of a telecommunications	15
facilities request in the context of multiple governing laws, including the City’s	16
permitting process; Section 332 of the federal Telecommunications Act, 47 U.S.C.	17
§ 332 (Section 332); the Middle Class Tax Relief and Job Creation Act of 2012	18
(Spectrum Act) § 6409, 47 U.S.C. § 1455 (Section 6409); and the corresponding	19
federal regulations. See In re Acceleration of Broadband Deployment by Improving	20
Wireless Facilities Siting Policies (FCC § 6409 Implementation Order), 29 FCC	21

2
Rcd. 12865, ¶¶ 191, 215-16 (Oct. 17, 2014), erratum 30 FCC Rcd. 31 (Jan. 5, 2015).1
1
Typically, the City applies Section 332 to review telecommunications applications	2
within 	the 	presumptively 	reasonable 	timeframes 	promulgated 	in 	the 	Federal	3
Communications Commission (FCC) regulations. See In re Petition for Declaratory	4
Ruling to Clarify Provisions of § 332(c)(7)(B) to Ensure Timely Siting Review & to	5
Preempt Under § 253 State & Local Ordinances that Classify All Wireless Siting	6
Proposals as Requiring a Variance (Reasonable Period of Time Ruling), 24 FCC	7
Rcd. 13994, ¶¶ 32, 42, 44-45 (Nov. 18, 2009).2 Applicant, however, invoked Section	8
6409, which (1) involves an expedited process under federal law and corresponding	9
FCC regulations; and (2) applies to “eligible facilities request[s],” defined as	10
requests to modify an existing telecommunications tower. See § 6409(a)(2). If the	11
application was an “eligible facilities request” under Section 6409, FCC regulations	12
require the City to respond to the application and act within 60 days, a far shorter	13
timeframe than the presumptively reasonable timeframes of 90 or 150 days 3
14
1In some publications, the FCC § 6409 Implementation Order is referred to
by its docket number, “FCC 14-153.” 	See, e.g., 	Portland Cellular P’ship v.
Inhabitants of Town of Cape Elizabeth, 139 F. Supp. 3d 479, 491 (D. Me. 2015).
2The Reasonable Period of Time Ruling is also sometimes referred to by its
docket number, “FCC 09-99.” See, e.g., ExteNet Sys., Inc. v. City of Cambridge,
Mass., 481 F. Supp. 3d 41 (D. Mass 2020).
3 The presumptively reasonable timeframes for local government action in
both Section 332 (90 or 150 days) and Section 6409 (60 days) are both referred to
as “shot clocks.” 	See In re Implementation of State & Local Governments’
Obligation to Approve Certain Wireless Facility Modification Requests Under
§ 6409(A) of the Spectrum Act of 2012 (In re Implementation of § 6409), 35 FCC

3
provided for under Section 332. See 47 C.F.R. § 1.6100(c)(2) (2021); Reasonable	1
Period of Time Ruling, 24 FCC Rcd. 13994, ¶ 4 (discussing Section 332 and defining	2
a reasonable timeframe of 90 days for review of collocation applications and 150	3
days for review of siting applications). Because the specific provisions of Section	4
332 (typical process) and Section 6409 (expedited process) are necessary to	5
understand the present case, we begin by briefly describing the applicable federal	6
law.	7
The Typical and the Expedited Processes	8
{3} 	Section 332 sets out what the City has described as the typical process	9
required of local governments when considering telecommunications requests.	10
Section 332 arose from Congress’s efforts “to promote competition and higher	11
quality in American telecommunications services and to encourage the rapid	12
deployment of new telecommunications technologies.” 	City of Rancho Palos	13
Verdes, Cal. v. Abrams, 544 U.S. 113, 115 (2005) (internal quotation marks and	14
citation 	omitted). 	In 	order 	to 	meet 	these 	goals, 	Congress 	imposed 	“specific	15
limitations on the traditional authority of state and local governments to regulate the	16
location, construction, and modification” of wireless communication facilities,	17
Rcd. 5977, ¶¶ 14-23 (June 10, 2020); FCC § 6409 Implementation, 29 FCC Rcd.
12865, ¶¶ 216, 254, 259 (discussing implementation of Section 6409, including
clarification of timeframes and “deemed grant” approach).

4
including timeframes for the local decision making process. Id. at 115-16. In relevant	1
part, Section 332 states,	2
(ii) A [s]tate or local government or instrumentality thereof shall act on	3
any request for authorization to place, construct, or modify personal	4
wireless service facilities within a reasonable period of time after the	5
request is duly filed with such government or instrumentality, taking	6
into account the nature and scope of such request.	7
(iii) Any decision by a [s]tate or local government or instrumentality	8
thereof to deny a request to place, construct, or modify personal	9
wireless 	service 	facilities 	shall 	be 	in 	writing 	and 	supported 	by	10
substantial evidence contained in a written record.	11
Section 332(c)(7)(B)(ii), (iii) (emphasis added). It is well established that Section	12
332 does not prevent a local government from requiring an applicant to comply with	13
local ordinances, regulations, and procedures, provided that local law comports with	14
the Section 332 shot clock and other requirements. See Nextel Partners of Upstate	15
N.Y., Inc. v. Town of Canaan, 62 F. Supp. 2d 691, 695 (N.D. N.Y. 1999) (“[Section	16
332] establishes the procedural requirements that local boards must comply with in	17
evaluating cell site applications, but the statute does not affect or encroach upon the	18
substantive standards to be applied under established principles of state and local	19
law.” (internal quotation marks and citation omitted)). The “reasonable period of	20
time” under Section 332(c)(7)(B)(ii) for local governments to respond to requests is	21
presumptively 90 or 150 days, depending on the type of request. See Reasonable	22
Period of Time Ruling, 24 FCC Rcd. 13994, ¶¶ 32, 42, 44-45. That shot clock can	23
be extended if the local government determines a Section 332 application is	24

5
incomplete and the government notifies the applicant within 30 days that it needs	1
additional information. Under those circumstances, “the time it takes for an applicant	2
to respond to a request for additional information will not count” toward the 90- or	3
150-day presumptively reasonable period of time for the local government to	4
respond. Reasonable Period of Time Ruling, 24 FCC Rcd. 13994, ¶ 53. In order for	5
the shot clock to toll, a local government’s “request for additional information must	6
specify the code provision, ordinance, application instruction, or otherwise publicly-	7
stated procedures that require the information to be submitted.” FCC § 6409	8
Implementation Order, 29 FCC Rcd. 12865, ¶ 260. Accounting for any tolling,	9
“[a]ny person adversely affected by any final action or failure to act by a [s]tate or	10
local government or any instrumentality thereof that is inconsistent with [Section	11
332(c)(7)(B)], within 30 days after such action or failure to act, commence an action	12
in any court of competent jurisdiction.” Section 332(c)(7)(B)(v).	13
{4} 	Some applications governed by Section 332 also fall within the purview of	14
Section 6409. As we have noted, Section 6409 requires local governments to engage	15
in an expedited review process of eligible facilities requests and act within 60 days	16
on applications “for [a] modification of an existing wireless tower or base station.”	17
Section 6409(a)(2). Modifications of towers, within the context of the Section 6409	18

6
expedited process, include removal, replacement, and collocation4 of equipment. See	1
id. If the modifications sought do not substantially change the physical dimensions	2
of the tower, notwithstanding other law, the local government “may not deny, and	3
shall approve” the eligible facilities request. Section 6409(a)(1); see 47 C.F.R.	4
§ 1.6100(c)(2) (“Within 60 days of the date on which an applicant submits a request	5
seeking approval under this section, the . . . local government shall approve the	6
application unless it determines that the application is not covered by this section.”).	7
{5} 	If the local government takes no action “to approve or deny a request seeking	8
approval under this section within the timeframe for review (accounting for any	9
tolling), the request shall be deemed granted.” 47 C.F.R. § 1.6100(c)(4). “The	10
deemed grant does not become effective until the applicant notifies the applicable	11
reviewing authority in writing after the review period has expired.” Id. Importantly,	12
the FCC adopted these regulations for Section 6409, but explicitly rejected the	13
“deemed 	granted” 	remedy 	for 	Section 	332 	violations. 	See 	FCC 	§ 6409	14
Implementation Order, 29 FCC Rcd. 12865, ¶¶ 281-84, 289; see also Reasonable	15
Period of Time Ruling, 24 FCC Rcd. 13994, ¶ 39. Instead, remedies for Section 332	16
violations are to be fashioned on a case-specific basis. Reasonable Period of Time	17
4Throughout this litigation, Applicant has relied on the term “collocation,”
which refers to placing additional transmission equipment on an existing tower or
base. See 47 C.F.R. § 1.6100(b)(2).

7
Ruling, 24 FCC Rcd. 13994, ¶ 39; see also FCC § 6409 Implementation Order, 29	1
FCC Rcd. 12865, ¶¶ 281-84.	2
{6} 	With this for context, we return to the facts of the present case.	3
The Approval Requests and Responses	4
{7} 	On April 9, 2015, Applicant sent an “application letter” to the City’s land use	5
department, specifically the land use director. Applicant requested to	6
collocate two towers on its building at [an address in Santa Fe, New	7
Mexico] approximately [thirty] feet south of the building on to one	8
tower located on the ground. This does not constitute a new tower;	9
however, a new tower would need to be built to collocate and	10
consolidate the existing two towers. These towers were approved by the	11
[C]ity respectively in 2005 and 2010.	12
Attaching the relevant federal regulations to the letter, Applicant sought approval	13
under Section 6409 and its expedited 60-day shot clock.	14
{8} 	The City’s senior land planner, Daniel Esquibel, responded by letter nineteen	15
days later on April 28, 2015 (Esquibel Letter). In relevant part, the Esquibel Letter	16
stated:	17
Your packet identified a request to construct an 80 foot high tower on	18
the property to the rear of the existing building. The proposed new	19
tower is to replace the existing two towers that extend through the roof	20
of the existing building. [Santa Fe, N.M., Code §] 14-6.2(E)(5)	21
“General Requirements” state that “all towers shall be set back a	22
distance equal to at least [100] percent of the height of the tower from	23
any adjoining lot line, measured from the base of the tower.” The tower	24
setbacks proposed identified setbacks are less than [100] percent of the	25
tower height (+/-16.8 feet from the rear property line, +/- 37.8 [feet]	26
from the north property line and +/- 47 feet from the south property	27
line).	28

8
In order to obtain[] the proposed setback requests a waiver must be	1
approved by the Planning Commission. This also shifts the authority of	2
review pursuant to [Section] 14-6.2(E)(3) to the Planning Commission.	3
Please contact [a named individual at a particular phone number] to set	4
up a pre-application conference to discuss application submittals and	5
fees, Early Neighborhood notification, and Planning Commission	6
review process.	7
If you have any questions regarding this matter, please do not hesitate	8
to contact me[.]	9
In response, on May 26, 2015, Applicant sent another letter, which attempted to	10
clarify that the request was “for permission to relocate certain equipment from one	11
or more towers on the roof of his building to a single similar tower on a nearby spot	12
on the ground.” Applicant requested that the City reevaluate its determination that	13
“the entire approval process” was necessary and noted the City’s previous setback	14
variance approval for the rooftop towers.	15
{9} 	In September 2015, the parties planned to meet to discuss the tower and,	16
specifically, 	Applicant’s 	ongoing 	argument 	that 	Section 	6409 	applied 	to 	the	17
application. Following the meeting, the City sent Applicant a letter that explicitly	18
rejected Applicant’s position that the tower project was “eligible” for review under	19
Section 6409. Seventy-one days later, on January 22, 2016, Applicant sent a new	20
“letter of application for relocation of telecommunications tower” and sought “to	21
remove these 2 towers and construct one (1) replacement tower” on the ground. After	22
three months passed, however, on April 28, 2016, Applicant reversed course. In	23

9
another letter, Applicant again asserted that Section 6409 applied to the request and	1
disagreed with the City’s interpretation of Section 6409. Applicant additionally	2
contended that the City had also failed to comply with Section 332. The April 28,	3
2016 letter informed the City that the Applicant now deemed the original application	4
granted under Section 6409 and would proceed with construction.	5
[Applicant] deems the application submitted to [the land use director],	6
via Certified Mail and by email on April 9 th
, 2015, GRANTED in	7
accordance with Section 6409a. Therefore, since there were no other	8
objections to the application, other than the set back issue, my client	9
will proceed forward with the modification of the towers in accordance	10
with the application and plans as submitted.	11
{10} 	The City responded a month later and “reject[ed the] letter’s conclusion that	12
the application has been deemed granted.” Applicant nevertheless built the tower,	13
which we will refer to as “the ground tower.”	14
The Petition for Injunction, Removal, and Remand	15
{11} 	The City red-tagged the ground tower and on July 14, 2016, filed a request for	16
a temporary restraining order, preliminary injunction, and permanent injunction in	17
the First Judicial District Court. Applicant removed the case to federal court and	18
filed an answer that included affirmative defenses and two counterclaims. One	19
counterclaim alleged that the City substantively did not comply with Section 332	20
(Counterclaim One). The other counterclaim (Counterclaim Two) first alleged that	21
the City failed to meet the Section 6409 60-day expedited timeline and, alternatively,	22
if the City had correctly decided that Section 6409 did not apply to the request, the	23

10
City was then obligated to resolve the request within the 90- or 150-day timeframe	1
under Section 332 and had failed to do so. The federal court remanded the case back	2
to state district court without addressing the merits. The City filed an answer to the	3
counterclaims in state district court and asserted that Applicant had been informed	4
about the necessary steps to obtain the permit under the City’s ordinances and that	5
Applicant caused any delay. In addition, the City pleaded as an affirmative defense	6
that Applicant’s counterclaims had “failed to state a cause of action on legal	7
grounds” because Applicant “started (and then deliberately abandoned) an attempt	8
to receive city approval.”	9
{12} 	The district court held a hearing, granted the City’s petition for a preliminary	10
injunction, and enjoined any additional work on the ground tower during the	11
pendency of these proceedings. Soon afterward, Applicant filed a motion for	12
summary judgment and argued that the City had violated both Section 6409 and	13
Section 332. Applicant also sought a stay of the preliminary injunction in order to	14
allow Applicant to move certain antennas from the roof to the ground tower. On	15
March 30, 2017, the district court denied Applicant’s summary judgment motion and	16
the request for stay.	17
The “Deemed Grant” Summary Judgment Motion	18
{13} 	In 2018, the parties brought two separate motions to district court for decision:	19
(1) the City’s motion challenging a second “deemed grant” letter sent by Applicant	20

11
relating to the roof antennas and asking the court to prohibit the installation; and (2)	1
Applicant’s renewed motion for summary judgment, which relied solely on Section	2
6409 and the ground tower. Despite the different factual bases for the motions, as	3
we will explain, the district court treated the motions as cross-motions and granted	4
the City’s motion and denied Applicant’s renewed motion. To understand the issues	5
before us on appeal, it is necessary to appreciate the way the parties framed the issues	6
for the district court.	7
{14} 	Though Applicant’s renewed summary judgment motion was limited to the	8
application of Section 6409 to the ground tower, the City’s response addressed	9
Section 332 and offered an explanation for how Section 332 works, characterizing	10
Section 6409 as an expedited Section 332 process. According to the City, because	11
the Esquibel Letter was sent within the Section 6409 timeframes, the letter qualified	12
as a proper and timely denial of Applicant’s request under both Section 332 and	13
Section 6409. In reply, Applicant disagreed with the City’s characterization of	14
Section 6409 and stated that “[a]s a matter of law, Section 6409 governed the	15
[a]pplication to the exclusion of Section 332.” Applicant argued that (1) Section	16
6409 “stands apart” from Section 332; (2) Section 6409 applied notwithstanding	17
Section 332; and (3) the City failed to comply with Section 6409. Applicant	18
additionally maintained that even if Section 332 applied, the Esquibel Letter was an	19

12
insufficient denial under Section 332, and the City had failed to act in “a reasonable	1
amount of time.”	2
{15} 	At the hearing on both parties’ summary judgment motions, the district court	3
asked the parties whether the “deemed granted analysis” under Section 6409 would	4
“dispose of whether [Applicant] is entitled to put any kind of tower on that building;”	5
and if the court’s ruling on the two pending summary judgment motions would	6
“dispose of the case.” Specifically, the district court inquired whether other reasons,	7
apart from the deemed grant issue under Section 6409, could justify lifting the	8
injunction to either allow the tower construction or the placement of antennas.	9
Applicant stated that while the motions were about different pieces of equipment	10
(the ground tower and antennas), the motions could be addressed at the same time	11
because they involved the same statute and legal question. The City acknowledged	12
that if the Esquibel Letter “is insufficient, then [Applicant] has strong grounds to say	13
that he can invoke deemed granted” under Section 6409. In response, Applicant	14
reiterated the argument that the Esquibel Letter was insufficient under Section 6409	15
because it did not “even come close” to stating whether the request was covered by	16
Section 6409 nor was it a “final letter” that would give Applicant grounds to invoke	17
any appellate process.	18
{16} 	The district court granted the City’s motion to prohibit placement of antennas	19
and denied Applicant’s motion. The district court found as follows:	20

13
Applying the applicable rules, the April 9, 2015 letter by [Applicant] to	1
the City regarding the plans to build a new tower in which the current	2
equipment would be transferred from the existing two towers to the	3
new, higher tower located in a different location on the ground, cannot	4
be read as anything other than a request to build a new tower. It is not	5
a modification to an existing tower, it is a new tower.	6
As a result of this finding, the district court determined that the Esquibel Letter,	7
“could have been more clearly written, but the intent of the letter was to notify	8
[Applicant] that the tower proposed is a new tower, it does not meet the setback	9
requirements and [Applicant’s] request must go through the application process.”	10
Continuing, the district court concluded, “[h]ad the City stamped the word ‘denied,’	11
it would have resolved sooner the questions litigated in this lawsuit, but a plain	12
reading of the letter makes clear that the application to build a new tower is not a	13
modification and needs to comply with the rules for new towers.” 5
14
{17} 	Applicant filed a motion to reconsider. The motion raised multiple issues, but	15
in relevant part challenged the district court’s failure to address Section 332. At the	16
hearing on the motion to reconsider, Applicant argued that the district court’s ruling	17
that the Esquibel Letter communicated noncoverage under Section 6409 was wrong	18
as a matter of law and that even if the Esquibel Letter was a sufficient notice of	19
noncoverage, the City was then obligated to review the request under Section 332.	20
5The district court did not separately analyze the City’s summary judgment
motion relating to the antennas, and we therefore do not reach the issues concerning
the placement of antennas on the ground tower.

14
When the district court asked whether a single letter could indicate that the request	1
was not covered by Section 6409 and also deny the request under Section 332,	2
Applicant declared that it would “bogle[] the mind” that the Esquibel Letter could	3
be both given that it did not reference either statute. Applicant maintained the	4
position that the City was required to provide clear notice of its decision that Section	5
6409 did not cover the request, and the City was then required to consider the request	6
under Section 332.	7
{18} 	The City, in response, characterized the district court’s original order as	8
establishing that “this [was] not an eligible facilities request [under Section 6409]	9
because it wasn’t an existing tower” and that the law did not require the City to issue	10
a notice that Section 6409 did not apply. Regarding Section 332, the City argued that	11
Applicant had elected to proceed under Section 6409, the Esquibel Letter was also a	12
denial under Section 332, and Applicant could have sought judicial review of any	13
Section 332 denial. The district court denied the motion to reconsider. Applicant	14
appealed.	15
DISCUSSION	16
{19} 	On appeal, Applicant contends that the ground tower application should have	17
been “deemed granted” under Section 6409 because the City failed to appropriately	18
respond within 60 days of the request, and a permit should otherwise issue because	19
the City failed to comply with the procedural requirements of Section 332. We	20

15
review de novo both issues of statutory construction and summary judgment rulings.	1
See State Pub. Educ. Dep’t v. Zuni Pub. Sch. Dist., 2018-NMSC-029, ¶ 17, 458 P.3d	2
362.	3
I. 	Our Appellate Jurisdiction	4
{20} 	We begin our discussion by raising and resolving the question of this Court’s	5
jurisdiction. See Smith v. City of Santa Fe, 2007-NMSC-055, ¶ 10, 142 N.M. 786,	6
171 P.3d 300 (“[I]t is incumbent upon the appellate court to raise jurisdiction	7
questions sua sponte when the Court notices them.”). As we have explained,	8
Applicant brought two counterclaims: Counterclaim One, relating to the substance	9
of Section 332 and Counterclaim Two, invoking Section 6409. Applicant voluntarily	10
dismissed Counterclaim One but maintained Counterclaim Two, which included—	11
in addition to his Section 6409 invocation—an allegation that, in the alternative, the	12
City failed to comply with Section 332’s procedural timeframes. The district court’s	13
summary 	judgment 	and 	reconsideration 	orders 	do 	not 	explicitly 	dismiss	14
Counterclaim Two or refer to the portion of that counterclaim that argued the City	15
had failed to comply with Section 332. We therefore must consider whether the	16
district court’s orders resolved Counterclaim Two so that the orders are final and	17
properly before us. See Rule 1-054(B) NMRA (“If an action presents more than one	18
claim for relief, whether as a claim, counterclaim, cross[-]claim, or third-party claim,	19
. . . the court may direct entry of a final judgment about one or more, but fewer than	20

16
all, claims or parties, only if the court expressly finds no just reason for delay.”); see	1
also Clinesmith v. Temmerman, 2013-NMCA-024, ¶ 35, 298 P.3d 458 (“The general	2
rule in New Mexico for determining the finality of a judgment is that an order or	3
judgment is not considered final unless all issues of law and fact have been	4
determined and the case disposed of by the trial court to the fullest extent possible.”	5
(internal quotation marks and citation omitted)).	6
{21} 	As we have explained, the City framed the Section 6409 issue as a subset of	7
Section 332 analysis and suggested that the Esquibel Letter satisfied its obligations	8
under both Section 332 and Section 6409. Applicant maintained that the two laws	9
were completely separate and the City had separate obligations under each. In the	10
order granting summary judgment, the district court concluded that Section 6409 did	11
not apply, and as a result, Applicant “must proceed to follow the application process	12
for a new tower.” The district court ordered that “the injunction will remain in place	13
until [Applicant] applies for and obtains the proper building permit” and that the	14
“case is dismissed.” Based on our review of the proceedings, as set forth in preceding	15
paragraphs, we conclude that the district court adopted the City’s view that	16
compliance with Section 6409 also included and satisfied the City’s Section 332	17
obligations. We will address the substance of the district court’s ruling shortly, but	18
for the purposes of finality, the district court resolved all issues of law and fact and	19
fully disposed the case. See Clinesmith, 2013-NMCA-024, ¶ 35 (explaining that the	20

17
general rule of finality “is not inflexible” and “is to be given a practical, rather than	1
a technical, construction” (internal quotation marks and citation omitted)). We	2
therefore turn to the merits of the appeal.	3
II. 	The Application of “Deemed Granted” Under Section 6409	4
{22} 	Applicant argues that the 60-day shot clock expired under Section 6409	5
because the Esquibel Letter (1) resulted in “a failure to act under Section 6409” and	6
47 C.F.R. § 1.6100(c)(4); and (2) was not a final appealable determination.6 The City	7
argues that the Esquibel Letter communicated to Applicant that Section 6409 did not	8
apply because in the City’s view, the application was for a new tower. We agree with	9
the City that the Esquibel Letter adequately communicated to Applicant the City’s	10
position that Section 6409 did not cover the request. See 47 C.F.R. § 1.6100(c)(2)	11
(requiring a locality to approve an application within 60 days unless “the application	12
is not covered by this section”). We further conclude that the Esquibel Letter was	13
sufficiently reviewable under Section 6409. Having communicated its decision that	14
Section 6409 did not apply with a sufficiently reviewable letter within 60 days, we	15
hold that the City complied with the Section 6409 shot clock. To explain these	16
conclusions, we return to the language of Section 6409 and its implementing	17
regulations.	18
6Applicant additionally argues that the Esquibel Letter did not toll the Section
6409 shot clock. Because the City does not rely on tolling, we do not engage in a
tolling analysis.

18
A. 	The Esquibel Letter Was a Notice That Section 6409 Would Not Apply	1
{23} 	The expedited process set forth in Section 6409 applies to “any eligible	2
facilities 	request 	for 	a 	modification 	of 	an 	existing 	wireless 	tower.” 	Section	3
6409(a)(1). An “existing” wireless tower is defined by the regulation: “A constructed	4
tower or base station is existing for purposes of this section if it has been reviewed	5
and approved under the applicable zoning or siting process, or under another [s]tate	6
or local regulatory review process.” 47 C.F.R. § 1.6100(b)(5). Thus, Section 6409	7
applies only to eligible facilities requests for existing wireless towers.	8
{24} 	In the request, Applicant stated, “This does not constitute a new tower;	9
however, a new tower would need to be built to collocate and consolidate the existing	10
two towers.” (Emphasis added.) The request included explicit references to Section	11
6409 and provided copies of the regulations. Despite having noted that a new tower	12
would need to be built, Applicant averred, “[A]s these are existing towers and we	13
are simply collocating them to a different location” the normal process pursuant to	14
the ordinance would not apply.	15
{25} 	In response, the Esquibel Letter stated the City’s position that the author had	16
“reviewed the information provided” and notified Applicant that (1) “[t]he proposed	17
new tower” would replace the existing two towers; and (2) Applicant would be	18
required to comply with setback requirements and obtain a variance. The Esquibel	19
Letter describes the setback requirements under the City’s ordinances, explains that	20

19
the proposed setback requires a waiver approved by the Planning Commission, and	1
indicates that “[t]his also shifts the authority of review pursuant to [Section] 14-	2
6.2(E)(3) to the Planning Commission.” In the context of these communications, the	3
Esquibel Letter communicated to Applicant that Section 6409, which Applicant	4
invoked and provided for the City’s consideration, did not apply to what the City	5
determined to be a “new tower.”	6
{26} 	Applicant contends that the Esquibel Letter was not a determination under	7
Section 6409 because (1) the letter “did not mention or show awareness of Section	8
6409” or request more information; (2) the letter looks like a “standard land use	9
letter;” and (3) Esquibel did not later characterize the letter as a Section 6409	10
determination. 	For 	these 	reasons, 	Applicant 	argues 	that 	the 	City 	made 	no	11
determination at all under Section 6409. This argument disregards the May 26, 2015	12
letter that Applicant sent in response to the Esquibel Letter. In the response letter,	13
Applicant disputed the City’s assertion that Applicant must “go through the entire	14
approval process to relocate his tower in the same manner as if approval for such a	15
structure had never been granted to him.” Despite the deficiencies in the Esquibel	16
Letter identified by Applicant on appeal, Applicant’s letter sent in response to the	17
Esquibel Letter demonstrates that Applicant understood that the City was refusing	18
to apply the Section 6409 expedited process. Having concluded that the Esquibel	19

20
Letter was notice to Applicant that Section 6409 would not apply, we next consider	1
the reviewability of the Esquibel Letter.	2
B. 	The Esquibel Letter Was Reviewable as a Claim Related to Section 6409	3
{27} 	Applicant maintains that the deemed grant determination was appropriate	4
because the Esquibel Letter was not a “final, appealable action” and instead sent the	5
request “into some kind of legal purgatory.” None of Applicant’s arguments,	6
however, acknowledge the limited finality requirements set forth in the Section 6409	7
corresponding regulations. Specifically, the “remedies” provision of 47 C.F.R.	8
§ 1.6100(c)(5) states that “[a]pplicants and reviewing authorities may bring claims	9
related to Section 6409(a) to any court of competent jurisdiction.” In FCC § 6409	10
Implementation Order, the FCC explained that appeals or claims related to Section	11
6409 “would appear likely to fall into one of three categories.” 29 FCC Rcd. 12865,	12
¶ 236.	13
First, if the [s]tate or local authority has denied the application, an	14
applicant might seek to challenge that denial. Second, if an applicant	15
invokes its deemed grant right after the requisite period of [s]tate or	16
local 	authority 	inaction, 	that 	reviewing 	authority 	might 	seek 	to	17
challenge the deemed grant. Third, an applicant whose application has	18
been deemed granted might seek some form of judicial imprimatur for	19
the grant by filing a request for declaratory judgment or other relief that	20
a court may find appropriate.	21

21
Id. Section 6409 does not appear to require a “final order” or “final determination”—	1
just a denial, a grant, or a “deemed grant.”7
2
{28} 	In the present case, as we have already determined, the Esquibel Letter was a	3
sufficient notice of noncoverage (or denial), which effectively communicated that	4
the City would not apply Section 6409. Applicant nevertheless contends that because	5
the City’s pleadings stated no final order had issued and the letter could not be	6
appealed under the City’s code, the Esquibel Letter was not a sufficient notice of	7
noncoverage. While the Esquibel Letter might not permit an administrative appeal	8
under the City’s code, the letter could support a claim in any “court of competent	9
jurisdiction” because the letter is “related to Section 6409(a).” See 47 C.F.R.	10
§ 1.6100(c)(5). We are therefore unpersuaded by Applicant’s argument that the	11
Esquibel Letter was insufficiently final or unreviewable and affirm the district	12
court’s ruling in this regard.	13
7We note that in the motion to reconsider, Applicant took umbrage with the
district court’s observation that had the City stamped “denied” on Applicant’s
request letter, the matter would have been resolved sooner. Applicant argued that the
district court’s order must have been referencing Section 332, “because you can’t
deny in [Section] 6409” and the order was “really confusing.” The FCC, however,
also has used the term “denial” when referring to a notice of noncoverage under
Section 6409. Therefore, while we understand Applicant’s position on the matter,
we purposefully use the term “denial” in accordance with the FCC’s guidance.

22
III. 	The Application of Section 332	1
{29} 	Applicant last argues that the City failed to comply with Section 332(c)(7)’s	2
procedural requirements. 8 Specifically, Applicant contends that the City did not	3
issue a final, appealable, written denial under Section 332, “supported by substantial	4
evidence contained in a written record.” Section 332(c)(7)(B)(iii). As a remedy for	5
these alleged deficiencies, Applicant seeks the issuance of the permit for the ground	6
tower. The City contends that Applicant failed to timely appeal Section 332 issues,	7
and regardless of the appeal’s timeliness, the Esquibel Letter was sufficient to satisfy	8
the procedural requirements of Section 332(c)(7). In reply, Applicant claims that the	9
City waived any argument that the Section 332 appeal is untimely by failing to plead	10
such a defense in the answer to Applicant’s counterclaims.	11
{30} 	We set out the parties’ appellate arguments to highlight the narrow decision	12
the district court made in this case and the resulting narrow window for our review.	13
Generally, our review is limited to whether the appellant meets the burden to	14
demonstrate 	error by the district court. 	See Farmers, Inc. 	v. 	Dal 	Mach. 	&	15
Fabricating, Inc., 1990-NMSC-100, ¶ 8, 111 N.M. 6, 800 P.2d 1063 (“[The	16
8Applicant solely challenges the Esquibel Letter’s adherence to the procedural
aspects of Section 332 and does not appear to challenge or argue that even if the
Esquibel Letter was procedurally sufficient under Section 332(c)(7), the letter was
substantively 	incorrect. 	Such 	a 	contention 	formed 	the 	basis 	for 	Applicant’s
Counterclaim One, which was dismissed by stipulation and therefore is not before
us.

23
a]ppellant must affirmatively demonstrate its assertion of error.”). In the present	1
case, the district court decided that the City complied with Section 6409 and	2
Applicant had to obtain a permit. As we have explained, we understand the district	3
court’s determination to rest on a legal conclusion that the City’s compliance with	4
Section 6409 and its timeframes also satisfied the requirements of Section 332. We	5
disagree with that legal conclusion because the two procedures are separate under	6
the applicable law. As we explain below, Applicant is entitled to a ruling on the	7
Section 332 claim.	8
{31} 	Section 6409(a)(1) begins by stating, in general, “[n]otwithstanding [S]ection	9
[332] or any other provision of law, a [s]tate or local government may not deny, and	10
shall approve, any eligible facilities request for a modification of an existing wireless	11
tower or base station that does not substantially change the physical dimensions of	12
such tower or base station.” The FCC has explained that when both Section 6409	13
and Section 332 apply, “if the reviewing [s]tate or municipality finds that Section	14
6409(a) does not apply (because, for example, it proposes a substantial change), we	15
provide that the presumptively reasonable timeframe under Section 332(c)(7) will	16
start to run from the issuance of the [s]tate’s or municipality’s decision that Section	17
6409(a) does not apply.” FCC § 6409 Implementation Order, 29 FCC Rcd. 12865,	18
¶ 220. The government may seek additional information to evaluate an application	19
under Section 332, “subject to the same limitations applicable to other Section	20

24
332(c)(7) reviews.” FCC § 6409 Implementation Order, 29 FCC Rcd. 12865, ¶ 220.	1
Thus, when the City sent the Esquibel Letter notifying Applicant of noncoverage,	2
the matter reverted to a Section 332 determination, and the associated timeframes	3
and requirements began to run.	4
{32} 	Viewing the proceedings as a whole, we conclude that the district court	5
conflated 	the 	Section 	6409 	determination 	with 	the 	necessary 	Section 	332	6
determination. We must therefore remand for further proceedings to allow the	7
district court to consider and resolve the Section 332 arguments that the parties have	8
raised on appeal.	9
CONCLUSION	10
{33} 	We hold that the district court properly denied Applicant’s “deemed granted”	11
motion as it pertains to Section 6409 and affirm the district court on that issue. We	12
remand to allow the district court to resolve in the first instance the issues raised by	13
the parties on appeal concerning the City’s compliance with Section 332 procedures.	14
{34} 	We 	therefore 	affirm 	in 	part, 	reverse 	in 	part, 	and 	remand 	for 	further	15
proceedings.	16
{35} 	IT IS SO ORDERED.	17
______________________________	18
KATHERINE A. WRAY, Judge	19

WE CONCUR:
Megan P Duffy
MEGAN P. DUFFY, Cudge
Mane B.4thales
JANE B. YOHALEM, Judge
25
1 2 3 4 5

Poursuivez vos recherches dans ChatGPT ou Claude

Connectez Omnilex pour rechercher dans le corpus juridique depuis votre assistant IA.