The Airspace Guide to Data Center Alley

Audience: data center developers, general contractors, commissioning firms, facility and critical-operations teams, and the referral partners who support them in Loudoun, Fairfax, and Prince William counties.

What this is: the airspace facts for this corridor, written plainly, with every regulatory sentence traced to a primary source. It exists because nearly every data center site in Data Center Alley sits inside a federal airspace structure that has no equivalent anywhere else in the United States, and because the answers to the questions that structure creates are not on any vendor page.

What this is not: a sales document. There is no pricing here, no client list, and no claim that a single answer covers every parcel. Ceilings and authorizations are per-parcel facts, and this guide is built around that.

The verdict, up front

Data Center Alley is servable with remotely piloted aircraft. It is also more constrained than almost any other commercial market in the country, and pretending otherwise is how schedules get broken.

• Ashburn, Sterling, Chantilly, Herndon, Reston, Manassas, Bristow, South Riding, and Brambleton sit inside the Washington DC Special Flight Rules Area (SFRA) - a 30-nautical-mile ring of national defense airspace. Aerial work there is lawful and routine, but it requires prior FAA authorization, a published altitude ceiling read cell by cell, and a NOTAM check on the day.
• Far western Loudoun, including Purcellville, sits outside the SFRA. Your authorization picture there is the ordinary Part 107 picture.
• The eastern tier - Arlington, Alexandria, the District core, and the Fairfax County addresses closest to the Potomac - sits inside the DC Flight Restricted Zone (FRZ). Small unmanned aircraft operations there are prohibited absent a federal TSA/FAA airspace waiver process. That airspace is out of scope for our aerial work, and we say so at intake rather than halfway through a schedule.
• Distances in this guide are nautical miles (NM) from the DCA VOR/DME, because that is the reference the regulation itself uses. Where statute miles help, they are in parentheses.

The eight facts this guide rests on

Each of these is the load-bearing claim of a section that follows, and each carries its citation.

1. Data Center Alley is inside the DC SFRA. Ashburn measures 23.8 NM from the DCA VOR/DME against a 30-NM boundary. (14 CFR 93.335; great-circle computation, 2026-09-23)
2. The FRZ is not a 15-NM circle. It is a 15/13-NM arc pair - 15 NM across the northern sector, 13 NM from the 064 degree radial clockwise around to the 276 degree radial - closed on the west by a straight line at roughly 77.31 degrees west. (14 CFR 93.335)
3. Unmanned aircraft operations in the FRZ are prohibited unless specifically authorized through the TSA/FAA airspace waiver process. (FDC NOTAM 4/1783, section I.B and section V.B)
4. UAS Facility Maps do not authorize anything. They show “the maximum altitudes around airports where the FAA may authorize part 107 UAS operations without additional safety analysis,” and the FAA states they “DO NOT authorize operations in these areas at the depicted altitudes - they are for informational purposes ONLY.” (FAA - UAS Facility Maps)
5. Ashburn-area ceilings differ cell by cell, and they move. A pull logged at 400 ft on the Waxpool side; a cell at the Route 28 and Route 7 interchange logged at 300 ft; a cell north of it at 400 ft; a cell south of Sterling at 0 ft. All four are inside the same 30-NM ring, within a few miles of one another. (FAA UAS Facility Map layer, MAP_EFF 2026-09-03, pulled 2026-09-23)
6. LAANC is fast but narrow, and above-ceiling work leaves it. Near-real-time approval applies at or below the published cell ceiling and under 400 ft; a “further coordination request” can be filed up to 90 days ahead and is coordinated manually; and if an operation needs a waiver and an airspace authorization, the FAA requires both to be filed through FAADroneZone. (FAA - LAANC)
7. Part 107’s ceiling is 400 ft above ground level, with one structure exception: within a 400-ft radius of a structure and no higher than 400 ft above that structure’s immediate uppermost limit. (14 CFR 107.51(b))
8. This is national defense airspace, and it is dynamic. The SFRA and FRZ “constitute national defense airspace,” and knowing or willful violations may be subject to criminal prosecution (14 CFR 93.331, 14 CFR 93.333). Restrictions “can occur on short notice,” so the standing instruction to every pilot is to check NOTAMs before every flight (FAASafety - DC SFRA and FRZ course notes).

1. Why airspace is the first question in Data Center Alley

Most industrial markets have a permitting story, a power story, and a fiber story. Data Center Alley has all three, and it also has a fourth problem that no other data center market in the country has: the campus sits inside the Washington DC Metropolitan Area Special Flight Rules Area.

That is not a marketing distinction. It is a regulatory one, and it changes the order in which work can be scheduled.

What the SFRA actually is

The rulebook is 14 CFR part 93, subpart V. It is not guidance, and it is not advisory. The FAA wrote it to make aircraft trackable and in contact, and the purpose section says why in plain terms: the area exists “to facilitate the tracking of, and communication with, aircraft to deter persons who would use an aircraft as a weapon, or as a means of delivering weapons, to conduct an attack on persons, property, or buildings in the area.” The same section states that the areas it describes “constitute national defense airspace.” (14 CFR 93.331)

Two consequences follow for anyone planning aerial work on a data center campus.

First, the airspace is monitored, and the consequences of getting it wrong are not administrative. Any violation - “whether inadvertent or intentional” - exposes a pilot to civil enforcement, civil penalties, and suspension or revocation of certificates. A knowing or willful violation of national defense airspace may be subject to criminal prosecution. (14 CFR 93.333)

Second, the airspace is layered, and the layers do not care about county lines, campus boundaries, or how the site was drawn on a plat. Two parcels on opposite sides of a road can have different published altitude ceilings and different authorization paths. This is the single most common source of schedule surprise in this market, and it is entirely avoidable with one check done at the right time.

The part operators get wrong

The mistake is treating “Northern Virginia” as one airspace answer. It is not. It is at least four:

Holding the authority to fly a Kingstowne roof tells you nothing about a Sterling roof. That is why the check in section 8 runs on the parcel, not on the metro.

The one sentence worth taking from this section

Airspace in Data Center Alley is a per-parcel fact, it is verified against primary sources before any commitment, and the verification takes place before a schedule exists - not after one has been promised.

“Most of the way there” is not a status. Inside the SFRA, a missing authorization is not a delay to be absorbed on-site. It is a stop.

2. The two rings

There are two boundaries that matter in this corridor, and they nest. The outer one is generous. The inner one is the tightest airspace in the country, and the shape of it is the part that most published summaries get wrong.

Ring one: the DC SFRA

The regulation defines it as “that airspace, from the surface to, but not including, FL 180, within a 30-mile radius of Lat. 38°51’34” N., Long. 077°02’11” W., or the DCA VOR/DME.” The same definition states plainly that “the DC SFRA includes the DC FRZ.” (14 CFR 93.335)

Three details belong in every planning conversation about that sentence.

• The reference point is a navaid, not a city hall. All SFRA geometry measures from the DCA VOR/DME at 38°51’34” N, 077°02’11” W. That is what the 30 NM means, and it is why the ring is not centered on downtown Washington.
• The vertical extent starts at the surface. There is no floor to slip under. A parcel inside the 30 NM ring is inside the SFRA from the ground up to just below flight level 180.
• The ring is 30 NM, which is about 34.5 statute miles. Ashburn’s 23.8 NM puts it roughly 6 NM inside the boundary. Purcellville at 35.8 NM is outside it.

The FAA’s own public summary matches: the SFRA is “roughly a circular area with a 30 nautical mile (about 33 statute miles) radius around Washington, D.C., and surrounds the Flight-Restricted Zone (FRZ).” The same page notes that Leesburg Executive Airport sits on the SFRA boundary, and that the Leesburg Maneuvering Area exists to ease access in and out of that airport. (FAA - Restricted Airspace)

Ring two: the DC FRZ

This is the boundary that is routinely described as “a 15-mile circle around Washington.” That description is wrong in a way that matters to a parcel check, because the true shape is smaller than a 15 NM circle almost everywhere, and on the west side it is cut off by a straight line rather than an arc.

Here is the regulation, read as a boundary walk. The FRZ is the area bounded by:

(14 CFR 93.335)

Read that sequence as a shape and you get the working model:

• The northern sector between the 311° and 002° radials is the only part that reaches a full 15 NM. That is the bulge over Montgomery County.
• From the 064° radial clockwise through east, south, and around to the 276° radial, the boundary is the 13 NM arc. So southeast, south, southwest, and west of the airport the FRZ is 13 NM, not 15.
• The west side is not an arc at all. Step 6 draws a straight line from the 276° radial at 13 NM back up to the 311° radial at 15 NM. Both endpoints sit near 077°18’ W. That line is a near-meridian at roughly 77.31° W, and everything west of it is outside the FRZ no matter how close it is to the airport.

That last point is the one worth remembering. The FRZ’s western edge is a straight, roughly north-south line running between the Fairfax City area in the south and the Great Falls area in the north. It is not a curve, and a parcel does not have to be far from the airport to be outside the FRZ - it only has to be west of that line.

The FAA’s plain-language version is consistent, if coarser: “The Flight-Restricted Zone (FRZ) extends approximately 15 nautical miles (about 17 statute miles) around Ronald Reagan Washington National Airport.” (FAA - Restricted Airspace). Plan against the regulation’s geometry, not the summary’s.

The carve-out, and what sits inside

One parcel of airspace is carved back out of the FRZ: the rule excludes “the airspace within a one nautical mile radius of the Freeway Airport, W00, Mitchellville, MD from the surface up to but not including flight level (FL) 180.” (14 CFR 93.335) That carve-out is in Maryland. It does not affect any Northern Virginia parcel, and it is included here only so the shape of the rule is complete.

Inside the FRZ sit the two prohibited areas, and they are the most restricted airspace in the United States:

• P-56A covers approximately the area from west of the Lincoln Memorial (Rock Creek Park) to east of the Capitol (Stanton Square), between Independence Avenue and K Street, up to 18,000 feet.
• P-56B is a small circle with a radius of about one nautical mile (about 1.2 statute miles) around the Naval Observatory on Massachusetts Avenue, up to 18,000 feet.

Both are prohibited areas surrounding the White House, the National Mall, and the vice president’s residence, and the only aircraft permitted inside them are specially authorized flights in direct support of the Secret Service, the Office of the President, or a narrow set of government agencies. (FAA - Restricted Airspace). The FAA’s security-procedures page states the relationship directly: the FRZ is “highly restricted airspace that includes prohibited areas P56A and P56B.” (FAA - Security-Related Flight Information and Procedures)

The schematic

The diagram below is a schematic for orientation only. It is not to scale, and it is not a substitute for a chart or for the parcel check in section 8.

        west  <---------  distance from DCA VOR/DME  --------->  east

  0 NM                13 NM        15 NM                    30 NM
   |--------------------|------------|------------------------|
   |                    |            |                        |
   |   FRZ (13 NM arc   |  FRZ 15 NM |    DC SFRA (continuation)|
   |    east of chord)  |  N bulge   |                         |
   |                    |            |                         |
   |<-- DC SFRA  (30 NM ring, surface to FL 180) ------------->|

   The five FRZ vertices, in order around the boundary:
     311 deg / 15 NM  ->  002 deg / 15 NM  ->  049 deg / 14 NM
     ->  064 deg / 13 NM  ->  276 deg / 13 NM  ->  back to start

   The final leg (276 deg / 13 NM back to 311 deg / 15 NM) is a
   straight line at about 77.31 deg W. That is the west wall.

What also applies, and who it applies to

Two adjacent pieces of the rulebook come up in site meetings often enough to name, with the caveat that both are written for manned aircraft rather than for small UAS, and should not be sold as unmanned-aircraft requirements.

• The 60-NM awareness ring. VFR flight within 60 NM of the DCA VOR/DME requires completion of the FAA’s special awareness training course - a 60-NM ring, twice the size of the SFRA itself. (14 CFR 91.161)
• The speed structure. Inside the SFRA, VFR operations are limited to 180 knots indicated or less; between 30 and 60 NM, 230 knots or less, unless ATC authorizes otherwise. (FAASafety - DC SFRA and FRZ course notes) These are manned-aircraft operating rules. They are useful context for how busy and how tightly managed this airspace is, and they are not the frame for a small UAS operation.

The standing obligation

Section 93.337 puts the last piece in place, and it is short: a pilot operating in the SFRA must comply with everything in subpart V and “all special instructions issued by the FAA in the interest of national security,” which the FAA may issue “in any manner the FAA considers appropriate, including a NOTAM.” (14 CFR 93.337)

That is the legal basis for the practical rule every operator in this corridor works under: the permanent boundaries are knowable in advance, and the operating picture on any given day is not. Sections 4 and 7 are about how that gap gets managed.

3. Reading a UASFM cell

The FAA’s UAS Facility Maps are the most misread document in this market. A ceiling number looks like a permission. It is not one.

What the layer is

The FAA describes the UAS Facility Maps as follows: they “show the maximum altitudes around airports where the FAA may authorize part 107 UAS operations without additional safety analysis. The maps should be used to inform requests for part 107 airspace authorizations and waivers in controlled airspace.” (FAA - UAS Facility Maps)

Read the words that carry the weight. “May authorize” - not “has authorized.” “Without additional safety analysis” - meaning the number is a threshold for how much FAA review a request will need, not a statement about what is airborne today.

And then the disclaimer, which the FAA states in capitals, because it keeps being ignored: “These maps DO NOT authorize operations in these areas at the depicted altitudes - they are for informational purposes ONLY. Operators must still apply to operate in controlled airspace (Class B, C, D, or surface area E) by completing a Part 107 Airspace Authorization request in LAANC or the FAADroneZone, or a Waiver Application in the FAADroneZone.” (FAA - UAS Facility Maps)

So the correct sentence about a UASFM cell is not “I can fly to 400 feet here.” It is “the FAA will approve a LAANC authorization up to 400 feet here without further analysis, provided everything else checks out.”

What a ceiling number means, precisely

A cell ceiling is the altitude up to which an automated authorization is available for that cell. It is not a flight altitude, and it is not a limit on what is legal.

• The operative altitude is the lower of two numbers. The cell ceiling caps what the automated authorization will cover. Part 107 separately caps altitude at 400 ft above ground level (14 CFR 107.51(b)). If the cell says 150 and Part 107 says 400, the working limit is 150 unless and until a further coordination request raises it.
• The structure exception is an operating limit, not an authorization. Part 107 allows flight within a 400-ft radius of a structure and no higher than 400 ft above that structure’s immediate uppermost limit (14 CFR 107.51(b)(1)-(2)). It does not raise a published cell ceiling. In controlled airspace, exceeding the cell ceiling is a separate problem from exceeding 400 ft, and it is solved by filing for it, not by finding an exception in Part 107.
• A ceiling above 400 ft does not exist for practical purposes. Some cells publish at 400. LAANC authorizations are for operations under 400 ft, and further coordination covers requests above the cell ceiling up to 400 ft. (FAA - LAANC)

Why adjacent cells differ

A call that begins “a data center in Ashburn needs 400 feet” is not answerable, because the Ashburn area is not one cell. Here is a pull from the FAA’s published layer, run on 2026-09-23 at the coordinates shown. The layer carries a MAP_EFF date of 2026-09-03 - that is the date the FAA last published the values, and it is the date that belongs next to every figure in this table.

Source: FAA UAS Facility Map data, ArcGIS FeatureServer FAA_UAS_FacilityMap_Data, point queries run 2026-09-23. MAP_EFF 2026-09-03.

Every number in that table came from the same layer queried the same afternoon. Within roughly 15 road miles the layer returns ceilings of 400, 300, 200, 150, 50, and two cells at 0. Sterling appears twice with different values.

The FAA does not publish the per-cell safety analysis, and no third party can reconstruct it reliably. What can be said without inventing anything is that the values track protected airspace around Dulles and Manassas - approach and departure corridors and traffic patterns - so the cells closest to the movement areas and the corridors carry the lowest ceilings. That is a description of the pattern, not a substitute for reading the cell.

One more honest note about movement in these numbers. Our own records include a prior pull that logged 350 ft at a point on the Waxpool / Beaumeade side of Ashburn, where the pull above returns 400 ft. Adjacent 1-NM cells can hold different values, so both observations can be correct. A prior record also logged 300 ft in the Bristow area, where the pull above at a different coordinate returns 50 ft; without a matching coordinate on the older entry we cannot say whether that is a different cell or a republished value. Both possibilities lead to the same discipline, and it is the discipline this guide is written around: read the cell, record the MAP_EFF date, and re-pull at the parcel before you commit.

Which is why we do not publish a single “Ashburn ceiling.” There is no such number.

What a 0-ft cell actually implies

A 0-ft cell is the most misunderstood value in the layer, and the misunderstanding runs in both directions.

A 0-ft cell means no near-real-time LAANC approval. The automated path is closed for that cell, because there is no altitude the system is authorized to approve.

A 0-ft cell does not mean the airspace is unfliable. The FAA states that certificated remote pilots “can use LAANC to obtain airspace authorization above UASFM grids, including 0’ grids by submitting a further coordination request.” (FAA - Part 107 Airspace Authorizations) That request is reviewed manually by the air traffic manager who owns the airspace, must be submitted at least 72 hours before the requested start time, and can be denied - and the facility may provide guidance so the request can be adjusted and resubmitted. (FAA - Part 107 Airspace Authorizations; FAA - LAANC)

The accurate formulation, and the one we use with clients, is this: a 0-ft cell means no LAANC; a request through the manual path is possible, and a denial should be planned for rather than assumed away.

The Manassas pair in the table above is the cleanest illustration in the corridor. The Manassas city cell north of the field publishes 400 ft and is LAANC-enabled. The airport core cell publishes 0 ft and is not LAANC-enabled at all - so even the further coordination path there runs through FAADroneZone, on a manual timeline. Two points roughly 2.5 NM apart, two different systems, two different schedules.

A blank is not a green light

Several localities in this corridor return no cell at all from the layer: Leesburg around the town and JYO, plus Gainesville, Aldie, Purcellville, Woodbridge, and all of the FRZ-tier addresses (Fairfax City, Tysons, McLean, Arlington, Alexandria, and the District core).

That blank means one thing and only one thing: the point is not inside a UASFM grid cell. It does not mean the airspace is unrestricted.

• For Purcellville, the absence of a cell and the absence of the SFRA line up - it is outside the 30-NM ring, and the ordinary Part 107 picture applies.
• For Leesburg, there is no charted UASFM ceiling, but the town is inside the SFRA at 29.0 NM, so the SFRA regime applies in full, including the security NOTAM.
• For the FRZ-tier addresses, a blank on the facility map is the least informative thing about them. Those points are inside the FRZ, where remotely piloted operations are prohibited absent a federal TSA/FAA airspace waiver process. Section 6 deals with that line directly.

A blank on a facility map is a blank. The check in section 8 is what turns it into an answer.

4. The authorization playbook

In uncontrolled airspace, a Part 107 flight needs no airspace authorization at all. In this corridor, that condition barely exists. Nearly every data center parcel in Loudoun, Fairfax, and Prince William is inside controlled airspace - Dulles Class B, Manassas Class D, or both overlaid by the SFRA - and that triggers a hard requirement.

The rule that starts everything

“No person may operate a small unmanned aircraft in Class B, Class C, or Class D airspace or within the lateral boundaries of the surface area of Class E airspace designated for an airport unless that person has prior authorization from Air Traffic Control (ATC).” (14 CFR 107.41)

Prior authorization. Not notification, not a log entry, not a courtesy call. Authorization obtained before the aircraft leaves the ground.

There are three doors through which that authorization arrives, and picking the wrong one is the most common scheduling error in this market.

Door one: LAANC, the automated path

LAANC - the Low Altitude Authorization and Notification Capability - is the automated authorization path. Requests are checked against airspace data including facility maps, special use airspace, airport and airspace class data, and current TFRs and NOTAMs, and “if approved, pilots can receive their authorization in near-real time.” The FAA also states the limit of the tool in one line: “LAANC provides airspace authorizations only. Pilots must still check NOTAMs, weather conditions, and abide by all airspace restrictions.” LAANC is available at 726 airports. (FAA - LAANC)

What LAANC is good for: a location, altitude, and time inside the published cell ceiling, under 400 ft, days or hours out.

What LAANC cannot do: exceed the cell ceiling, authorize a waivered operation, or substitute for reading the SFRA security NOTAM.

Door two: further coordination, the manual path inside LAANC

When the operation needs to go above the cell ceiling - up to 400 ft - the request becomes a “further coordination request.” The FAA’s published terms:

• It can be filed “up to 90 days in advance of a flight and the approval is coordinated manually through the FAA (available to Part 107 pilots only).” (FAA - LAANC)
• It “must be submitted at least 72 hours prior to requested start time of the operation,” and is reviewed by the Air Traffic Manager who manages the airspace. (FAA - Part 107 Airspace Authorizations)
• Facilities “can provide additional guidance for denied Further Coordination requests, allowing drone pilots to adjust operations and resubmit their request.” (FAA - Part 107 Airspace Authorizations)

The 90-day window is not a convenience feature. It is the only way to get a discretionary decision out of a human air traffic manager with enough runway left to plan a site visit around it. A 72-hour minimum is a floor for a request, not a service level for an answer.

Door three: FAADroneZone, the manual path outside LAANC

FAADroneZone “provides authorizations for airports that are not LAANC-enabled. It may also be used to process requests at LAANC enabled facilities, however it does not provide authorizations in near-real time. All requests are processed manually at the FAA Air Traffic Service Centers.” (FAA - Part 107 Airspace Authorizations)

Two operating details that matter when building a schedule:

• Lead time is published, and it is long. The FAA asks for airspace authorization requests “at least 60 days prior to the proposed operation date,” states that requests submitted inside that window “may result in cancellation or denial,” and processes them “on a first come, first served basis.” (FAA - Part 107 Airspace Authorizations)
• Waiver-plus-authorization routes here, by rule. The FAA states: “If you are planning an operation in controlled airspace that requires a waiver AND an airspace authorization you must apply for both through the FAA’s DroneZone.” (FAA - LAANC)

That second bullet is the routing rule for any operation whose profile does not fit the standard ruleset, because a waivered operation cannot ride an automated approval. When a waiver is in play, the timeline is measured in months and the outcome is discretionary.

Which door, in one table

The SFRA layer sits on top of all of it

An airspace authorization from any of those three doors answers the controlled-airspace question. It does not answer the security question, because the SFRA has its own supplement for unmanned aircraft. The governing document is FDC NOTAM 4/1783, which states that the SFRA, including the FRZ, is established pursuant to 14 CFR 93.335, 93.337, 93.339, 93.341, and 99.7, and that all civil, including commercial, UAS operations “are prohibited within DC SFRA unless in compliance with title 14 CFR part 107 or the operator’s applicable FAA grant of exemption … and FAA certificate of authorization or waiver (COA).” (FDC NOTAM 4/1783, section III)

Read that as a two-lock door. Compliance with Part 107 is the first lock. The airspace authorization is the second. Both are required, and neither substitutes for the other.

Subpart V’s equipment and communication requirements - two-way radio, ATC communication, an operating altitude-reporting transponder, a discrete transponder code, a DC SFRA flight plan - are written for aircraft that carry radios and transponders (14 CFR 93.339). The FAA supplements them for unmanned aircraft by NOTAM, and the authorization in hand is what governs the specific operation. Do not build a checklist from the subpart alone, and do not build one from a facility map alone.

Why we file before we promise

Every authorization discussed above is location-specific and time-limited. A LAANC approval for a Sterling address is not an approval for a Chantilly address, and neither is an approval for next quarter. The FAA’s own framing of the authorization request asks for the start and end dates, the timeframe, the frequency, and the proposed location and maximum altitude (FAA - Part 107 Airspace Authorizations) - because each of those parameters is part of the decision.

The consequence is a rule we hold to, and it costs us work: dates are committed after the authorization is in hand, not before. The FAA does not promise outcomes on manual review, and neither do we. The honest version of the sequencing, in general terms, is:

1. Parcel geometry and airspace screening (section 8).
2. Cell pull with the MAP_EFF date recorded.
3. Authorization path selected and filed on the published timeline.
4. Authorization in hand.
5. Flight window published against the current NOTAM picture.
6. Flight flown and confirmed on the day.

Steps 1 through 3 are the part most schedules skip. They are the only part that cannot be recovered on-site.

5. What the parcels actually look like

This is the section clients forward. It is also the section that must be read with its caveat attached, so the caveat goes first.

Screening-grade only. The distances below are great-circle nautical miles from the DCA VOR/DME, computed from the coordinates published in 14 CFR 93.335 and from locality reference points. They are good enough to tell you which regime a site is in and to shape a schedule. They are not a parcel determination. Every address is re-verified at the parcel before any commitment, and the screening is what tells us when that verification is critical rather than routine.

The same screening, locality by locality, is published on our service-area pages - each one carries its own distance from DCA, its SFRA standing, and the cell evidence, rather than a blanket ceiling for the region.

One geometry detail that changes the answer

Plot the regulation’s own coordinates and something becomes obvious. The corner published as “the DCA 311° radial at 15 NM” computes to a true bearing of about 302 degrees. The “002° radial at 15 NM” corner computes to about 353 degrees. The “276° radial at 13 NM” corner computes to about 267 degrees. The consistent offset is about 9 degrees - which is the local magnetic variation.

The radials in the rule are magnetic radials. The coordinates beside them are their true positions. This matters to anyone testing a parcel, because the two constructions are not the same shape: drawing the arcs from true-north radials at 311, 002, 049, 064, and 276 moves the boundary by well over a nautical mile. The safe method is to build the polygon from the published coordinates, and to use the radials only to know which direction each arc sweeps.

It also explains the western chord plainly. That chord is a true north-south line at roughly 77.31° W, and it is where most boundary surprises live.

Per-locality airspace readings

Great-circle distance from the DCA VOR/DME (38°51’34” N, 077°02’11” W), computed 2026-09-23. The SFRA boundary is 30 NM. The FRZ boundary is 13 NM from the 064-degree radial clockwise around to the 276-degree radial, 14 NM at the 049-degree radial, 15 NM between the 311-degree and 002-degree radials, and the western chord between.

Every locality on that list is inside the SFRA except Purcellville, and none of them is inside the FRZ. That is the whole data center corridor in one table: generously inside the SFRA, and clear of the FRZ.

The FRZ edge of the market looks different, and it is worth publishing because it is counterintuitive.

Two entries there deserve a sentence each.

Great Falls is inside the FRZ at 14.5 NM. It is farther from the airport than Tysons, and it is still inside, because it sits east of the western chord and under the 15 NM arc sector. Distance from the airport is a bad proxy for the boundary on the northwest side of this market.

Fairfax City sits on the line. Screening places it roughly 0.4 NM inside the FRZ, which is inside the margin of error of a centroid-to-centroid computation. Any address in the western Fairfax corridor near 77.31° W gets a real parcel-geometry check before anyone says FRZ or not-FRZ out loud. We would rather report an unresolved screening than a confident wrong answer.

Per-jurisdiction table

How to use this table

Read it as a filter, not an answer. The three questions it answers are: is this site inside the SFRA, is it inside the FRZ, and does the controlled airspace above it have a published cell ceiling.

The one thing it cannot answer is what the ceiling is at a specific address, because the cells change on mile-scale lines - as the Ashburn and Sterling rows above show. That is what the per-parcel check in section 8 is for.

6. The FRZ line

This section exists because a guide that explains the FRZ without stating what it means for a vendor is not useful, and a vendor page that implies FRZ capability is worse than not useful.

The rule, stated plainly: remotely piloted aircraft operations inside the DC Flight Restricted Zone are prohibited absent a specific federal authorization through the TSA/FAA airspace waiver process. That airspace is out of scope for our aerial work, and we say so at intake.

The regulatory basis

Three sources, in order of specificity.

The security NOTAM for unmanned aircraft. FDC NOTAM 4/1783 states it twice, in two sections, so there is no ambiguity to exploit. Section I.B: “UAS OPERATIONS ARE PROHIBITED IN THE DC FRZ UNLESS AN AIRSPACE WAIVER IS GRANTED.” Section V.B goes further: “UAS OPERATIONS ARE PROHIBITED IN THE DC FRZ UNLESS SPECIFICALLY AUTHORIZED VIA THE TSA/FAA AIRSPACE WAIVER PROCESS. CERTAIN COMMERCIAL AND PUBLIC UAS OPERATIONS ARE ELIGIBLE TO REQUEST AIRSPACE WAIVERS TO OPERATE IN THE DC FRZ.” (FDC NOTAM 4/1783, sections I.B and V.B)

The FAA’s DC airspace page, written for drone operators. “Flying an unmanned aircraft within the 15-mile radius inner ring is prohibited without specific FAA authorization.” The same page describes the access path as narrow and justification-based: experienced Part 107 and public aircraft operators with justification can file through the online Access Program, and “a TSA/FAA waiver and an SGI/COA is required.” (FAA - DC Area Prohibited and Restricted Airspace)

The regulation itself. Section 93.341(a) states that “no pilot may conduct any flight operation under part 91, 101, 103, 105, 125, 133, 135, or 137 of this chapter in the DC FRZ, unless the specific flight is operating under an FAA/TSA authorization,” with a short list of exceptions for Department of Defense, law enforcement, and air ambulance or lifeguard operations under an FAA/TSA authorization. (14 CFR 93.341)

One precision note, because this artifact is built on reading the rule rather than paraphrasing it: the enumeration in 93.341(a) does not itself name part 107. The prohibition as it applies to unmanned aircraft is stated expressly by the FAA’s DC airspace page and by the UAS security NOTAM quoted above. For a commercial aerial inspection operation the answer is the same either way, and it is no. We state the sources accurately rather than collapsing them into a quote that reads more cleanly than the rule does.

And inside the FRZ are the prohibited areas: P-56A over the White House and National Mall area, and P-56B, the roughly one-nautical-mile circle around the Naval Observatory, both up to 18,000 feet. The only aircraft permitted inside them are specially authorized flights in direct support of the Secret Service, the Office of the President, or a narrow set of government agencies. (FAA - Restricted Airspace)

Our position

• No operations inside the DC FRZ. Not at low altitude, not for a short duration, not for imagery the client says is harmless. The prohibition is not a threshold to negotiate.
• We do not hold out FRZ capability and we do not offer to obtain an FRZ airspace waiver for a client’s site. It is not a service we sell, and describing it as one would misrepresent both the process and our posture.
• We will not describe FRZ waiver eligibility criteria. The NOTAM points applicants to a TSA guideline document for that purpose. When we checked it on 2026-09-23 the referenced document did not load, and we do not publish regulatory claims we could not read at the source. This is a deliberate gap in this guide, and it is a gap we would rather name than fill with a summary of a summary.
• Portfolios get scoped site by site. If a portfolio spans FRZ and non-FRZ addresses, the intake answer names which addresses we can serve and which we cannot, in writing, before any proposal exists.

How we tell you at intake

The intake sequence is short, and it starts earlier than most vendors are willing to start.

1. Address first, before scope. The first question in an intake conversation is the site address, not the acreage, not the report format, not the timeline. No address means no answer.
2. Geometry before proposal. The parcel centroid and corners are tested against the SFRA ring and the FRZ boundary, using the coordinates published in 14 CFR 93.335.
3. Stated in writing, at intake. If the parcel screens inside the FRZ, the answer goes back in writing at intake as a declination, with the screening shown - the distance, the bearing, and which boundary element decided it. Not after a site visit. Not after a proposal.
4. Alternative where one exists. For a facility that spans or borders the FRZ, the conversation turns to what can be inspected from the ground or from outside the boundary, and to which site in the portfolio to work instead. Declining aerial work is not the same as having nothing to offer.

The reason this is stated so bluntly is that the cost of getting it wrong is asymmetric. A vendor who discovers an FRZ parcel during mobilization has a schedule problem and a credibility problem at once. A vendor who declines it at intake has told you something true about how they will treat everything else.

7. Operating in national-defense airspace

The permanent boundaries are knowable in advance. The daily operating picture is not. This section is about the second half of that sentence.

NOTAM discipline

The FAASafety SFRA course material is direct about where the authoritative, current information lives, and it makes two points that sit at the center of every schedule in this corridor.

• The SFRA itself “can only be changed by rulemaking, but operating procedures do change from time to time. These changes are always published in a NOTAM.” The course adds that the quickest and most reliable way to keep track of the latest changes is to always check NOTAMs.
• The area is dynamic by design. Restrictions and procedures “can occur on short notice,” and the standing guidance is to check NOTAMs before every flight. (FAASafety - DC SFRA and FRZ course notes)

This is not theoretical in this corridor. In the week this guide was written, the FAA’s temporary flight restriction list carried a VIP restriction over Sterling, Virginia and an air show restriction over Leesburg, Virginia - one locality squarely in the data center core, the other on the SFRA boundary. Both temporary, both inside the corridor. (FAA - Graphic TFRs, list retrieved 2026-09-23)

Four NOTAMs form the security frame around unmanned aircraft in this airspace, all indexed from the FAA’s security procedures page:

(FAA - Security-Related Flight Information and Procedures)

Weather minimums

Part 107 sets hard operating minimums that no authorization waives:

• Minimum flight visibility from the control station: 3 statute miles. (14 CFR 107.51(c))
• Minimum distance from clouds: 500 feet below and 2,000 feet horizontally. (14 CFR 107.51(d))
• Altitude: 400 ft above ground level, with the structure exception described in section 3. (14 CFR 107.51(b))

The SFRA adds its own conditions on top. The UAS NOTAM’s model-aircraft section requires operations to be conducted under visual meteorological conditions, states that operations “must not be conducted during night as defined in 14 CFR section 1.1,” and does not authorize special visual flight rules. Section V.D applies across all UAS operation types in the SFRA: “UAS OPERATIONS MUST NOT INTERFERE WITH AND MUST GIVE WAY TO MANNED AIRCRAFT.” (FDC NOTAM 4/1783, sections II and V.D)

We want to be precise about how we read that, because it is exactly the kind of place where an operator can talk themselves into a shortcut. The night and VMC conditions are written in the NOTAM section addressed to model aircraft, while the commercial section routes civil operations to Part 107 compliance. We do not read the difference as an opening. Our operating posture for SFRA parcels is daylight and civil twilight windows, and it stays that way.

Where a parcel has been verified as outside the SFRA, Part 107 night operations are lawful with anti-collision lighting visible for at least 3 statute miles and a current remote pilot in command (14 CFR 107.29). That is a capability boundary, not a coverage claim, and it is one more reason the FRZ and SFRA boundary work in section 5 has to be done at the parcel rather than at the ZIP code.

The FAA coordination point

UAS questions specific to this airspace have a named destination, and it is not the local tower. The NOTAM directs them to “the FAA National Capitol Region Coordination Center (NCRCC) at 866-598-9522.” (FDC NOTAM 4/1783, section VII.B)

That number belongs in a project’s escalation path before the first flight, not after something unexpected happens. It is the FAA’s stated route for UAS questions about SFRA and FRZ procedures.

What non-compliance actually looks like

The enforcement picture here is not ordinary. Three layers, all cited.

• Civil and criminal exposure. The FAA may take civil enforcement action for violations “whether inadvertent or intentional,” including civil penalties and suspension or revocation of certificates. Knowing or willful violations of national defense airspace may be subject to criminal prosecution. (14 CFR 93.333)
• Counter-UAS authority is real and federal. The UAS NOTAM warns that operators who do not comply with applicable airspace restrictions should be aware that under 10 U.S.C. section 130i and 6 U.S.C. section 124n, the Department of Defense, the Department of Homeland Security, or the Department of Justice “may take security action that results in the interference, disruption, seizure, damaging, or destruction of unmanned aircraft deemed to pose a credible safety or security threat to protected personnel, facilities, or assets.” (FDC NOTAM 4/1783, section I.C)
• The warning signal, and what follows it. NORAD uses a visual warning system to communicate with aircraft that enter the SFRA or FRZ without authorization: “highly focused red and green lights in an alternating red/red/green signal pattern.” A pilot not in communication with air traffic control who is illuminated by it should “turn to a heading away from the center of the FRZ/SFRA as soon as possible and immediately contact air traffic control,” and “failure to follow these procedures may result in interception by military aircraft and/or the use of force.” The FAA notes that this applies to all aircraft operating within the SFRA, including Department of Defense, law enforcement, and aeromedical operations. (FAA - Restricted Airspace)

Published windows, and why reschedules are a feature

The operational conclusion from all of the above is a scheduling practice, and it looks like this.

Windows are published in advance. A flight window is committed to in writing against the forecast and the current NOTAM picture, for a specific date range, at a specific location, with a specific altitude.

Every flight is confirmed on the day. The authorization is re-read, the NOTAMs are re-checked, and the TFR list is re-checked against the window. A window that has gone stale is not flown.

A reschedule is the correct outcome when the airspace changes. If a VIP movement puts a temporary restriction over the site, the honest options are to move the flight or to stand down. The dishonest option is to treat a published window as a right. A reschedule here is not a defect in the service; it is the service working. A vendor who never reschedules in this airspace has either stopped checking or is not telling you.

That is the whole posture, and it comes back to a single practice: this airspace is verified before it is promised.

8. How we verify before we commit

Everything in this guide is downstream of one procedure. It is not complicated, it is just done before the schedule exists rather than after.

This is also the difference between an airspace answer and a flight: the same discipline runs on data center and critical-facility inspections and on aerial thermal inspection - the parcel is checked, the cell is pulled, and the window is stated before anything is promised.

The per-parcel check

Step 1 - Parcel geometry. Take the parcel centroid and each corner. Test all of them against the SFRA ring and the FRZ boundary, building the boundary from the coordinates published in 14 CFR 93.335 rather than from the radials, for the reason given in section 5. Record every point and its result. A parcel that straddles a boundary is a different conversation from one that sits inside it.

Step 2 - Cell pull. Query the FAA UAS Facility Map layer at the centroid and at each corner, and record five fields for each: the ceiling, the airspace class, the controlling facility, whether the cell is LAANC-enabled, and the MAP_EFF date. The map is republished periodically, so a ceiling figure without its MAP_EFF date is not a fact - it is a memory. Our pull for this guide is dated MAP_EFF 2026-09-03, retrieved 2026-09-23, and it is already possible that it is out of date.

Step 3 - Authorization path. Decide the route from the cell data and the operating profile, and file on the FAA’s published timeline:

Step 4 - NOTAM review. Against the specific proposed window: FDC NOTAM 4/1783 and the companion SFRA, FRZ, and Leesburg Maneuvering Area security NOTAMs, plus the current temporary flight restriction list. This is repeated on the day of flight, not copied forward.

Step 5 - Record, then re-verify before commit. The MAP_EFF date goes next to every published ceiling figure. The geometry and the cell pull are re-run before an authorization is relied on and again before a window is flown. Where a parcel sits inside the margin of a boundary - the western Fairfax corridor near 77.31° W is the standing example - the screening is reported as unresolved until the parcel geometry decides it, and no commitment is made on an unresolved screening.

What that means for a schedule

The verification sequence produces three honest answers, and only three:

1. Servable. Cell ceiling and controlled airspace are known, the authorization path is identified, and a date can be committed once the authorization is in hand.
2. Servable with constraints. The ceiling is low, the cell is 0 ft, the facility is not LAANC-enabled, or the parcel straddles a boundary. Work is possible; the profile and the timeline change.
3. Not servable by us. The parcel screens inside the FRZ. Stated at intake, in writing, with the screening shown.

There is no fourth answer, and there is no answer that arrives after the schedule.

Glossary

Primary sources

Regulation (eCFR, Title 14):

• Part 93 subpart V, Washington, DC Metropolitan Area Special Flight Rules Area: https://www.ecfr.gov/current/title-14/part-93/subpart-V
• 93.331, purpose and applicability (national defense airspace): https://www.ecfr.gov/current/title-14/section-93.331
• 93.333, failure to comply (civil enforcement; criminal exposure for knowing or willful violations): https://www.ecfr.gov/current/title-14/section-93.333
• 93.335, definitions (SFRA and FRZ geometry, coordinates, the W00 carve-out): https://www.ecfr.gov/current/title-14/section-93.335
• 93.337, compliance with special instructions including NOTAMs: https://www.ecfr.gov/current/title-14/section-93.337
• 93.339, requirements for operating in the DC SFRA, including the DC FRZ: https://www.ecfr.gov/current/title-14/section-93.339
• 93.341, aircraft operations in the DC FRZ: https://www.ecfr.gov/current/title-14/section-93.341
• 93.345, VFR outbound procedures for fringe airports: https://www.ecfr.gov/current/title-14/section-93.345
• 91.161, special awareness training within 60 NM of the DCA VOR/DME: https://www.ecfr.gov/current/title-14/section-91.161
• 107.29, operation at night: https://www.ecfr.gov/current/title-14/section-107.29
• 107.41, operation in certain airspace (prior authorization): https://www.ecfr.gov/current/title-14/section-107.41
• 107.51, operating limitations (400 ft, visibility, cloud clearance): https://www.ecfr.gov/current/title-14/section-107.51

FAA (faa.gov) and FAASTeam (faasafety.gov):

• FDC NOTAM 4/1783, UAS special security instructions, DC SFRA and FRZ: https://www.faa.gov/air_traffic/publications/us_restrictions/procedures/doc/SFRA%20UAS%20NOTAM%204-1783.pdf
• Security-related flight information and procedures (the index for all DC-area security NOTAMs): https://www.faa.gov/air_traffic/publications/us_restrictions/procedures
• DC area prohibited and restricted airspace, written for UAS operators: https://www.faa.gov/uas/resources/community_engagement/no_drone_zone/dc
• Restricted Airspace (SFRA and FRZ summary, P-56, visual warning system, interception): https://www.faa.gov/newsroom/restricted-airspace-0
• LAANC (UAS Data Exchange): https://www.faa.gov/uas/getting_started/laanc
• UAS Facility Maps: https://www.faa.gov/uas/commercial_operators/uas_facility_maps
• Part 107 airspace authorizations (lead times, further coordination, FAADroneZone): https://www.faa.gov/uas/commercial_operators/part_107_airspace_authorizations
• FAADroneZone portal: https://faadronezone.faa.gov/
• Graphic TFRs: https://tfr.faa.gov/
• FAASTeam DC SFRA and FRZ course notes, revision 2020-01-15: https://www.faasafety.gov/files/gslac/courses/content/405/1310/200115%20SFRA%20Course%20NOTES.pdf

Airspace data:

• FAA UAS Facility Map data, ArcGIS FeatureServer FAA_UAS_FacilityMap_Data, point queries (fields CEILING, AIRSPACE_1, APT1_NAME, APT1_LAANC, MAP_EFF). Retrieved 2026-09-23; MAP_EFF 2026-09-03. Endpoint: https://services6.arcgis.com/ssFJjBXIUyZDrSYZ/arcgis/rest/services/FAA_UAS_FacilityMap_Data/FeatureServer/0/query
• Distances and boundary tests in sections 2 and 5 computed 2026-09-23 from the coordinates published in 14 CFR 93.335, referenced to the DCA VOR/DME at 38°51’34” N, 077°02’11” W.

Open questions and review notes

This manuscript is a draft and it is not cleared for publication. Four items are carried forward deliberately rather than quietly closed.

1. Authorization scope. Several sentences describe Jinki as holding FAA airspace authorizations for DC SFRA operations. Before publication, the scope on the current authorization letters - locations, altitudes, and any waivers attached - should be confirmed against the text that is being claimed, so the sentence matches the paperwork.
2. Fairfax City boundary. Screening places Fairfax City roughly 0.4 NM inside the FRZ boundary. Any address near 77.31° W is treated as unverified until a parcel-level geometry check is run. This guide says so rather than asserting a side.
3. TSA FRZ waiver guidelines. The NOTAM-referenced TSA applicant guideline document did not load when checked on 2026-09-23. This guide therefore does not describe FRZ waiver eligibility criteria, and it should stay that way until that primary document is read at the source.
4. Cell drift. The UAS Facility Map is republished on a cycle. Every ceiling figure in this document carries its MAP_EFF date for that reason, and none of them should be quoted without it.

The one-line version

Ceilings and authorizations in Data Center Alley are per-parcel facts, the FRZ is a line we do not cross or sell across, and we check a parcel’s airspace before we promise anything. Send us an address and we will send back what the airspace says about it.