FAA UAS Test Sites Add Two Research Environments: What Operators Can Learn Without Overclaimi

The Federal Aviation Administration announced two new Unmanned Aircraft Systems test sites on January 8, 2026. The sites will be located with the Choctaw Nation of Oklahoma and the Indiana Economic Development Corporation. According to the FAA, they are the first new UAS testing grounds in nearly a decade, and they will become the eighth and ninth sites in the U.S. network.

That announcement is significant without being a shortcut to an operating approval. The FAA describes the UAS Test Site program as supporting development, testing, and evaluation of public and civil unmanned aircraft and related technologies. It also says the program helps advance safe integration of drones into the National Airspace System. Those are research and integration purposes. They are not a blanket statement that every aircraft, mission, or operating method tested at a site is ready for routine commercial use elsewhere.

For organizations that follow UAS policy closely, the useful response is to read the announcement at the right level. A test-site designation is evidence that the FAA is building places to gather data and assess systems. It is also a prompt for operators, manufacturers, and program managers to improve how they distinguish a promising capability from an established operating basis.

Start with what the FAA actually announced

The FAA named the Choctaw Nation of Oklahoma and the Indiana Economic Development Corporation as the locations of the two new sites. It said the FAA Reauthorization Act of 2024 authorizes the Administrator to designate up to two new UAS test ranges. With these designations, the FAA said there will be nine UAS test sites.

The other seven locations listed by the FAA are the Alaska Center for Unmanned Aircraft Systems Integration, the Northern Plains UAS Test Site in North Dakota, New Mexico State University, the State of Nevada, the New York UAS Test Site, Texas A&M University Corpus Christi Autonomy Research Institute, and the Mid-Atlantic Aviation Partnership in Virginia.

The agency says the nine sites will support development, testing, and scaling of American drone technologies. Its stated focus includes beyond visual line of sight operations, increasingly autonomous operations, advanced air mobility, and other advanced operations. The FAA also says the sites will help assess emerging technologies to modernize methods for cargo delivery, BVLOS operations, and multiple drone operations, while informing safety and security.

Those statements describe a broad research agenda. They do not identify a particular aircraft, sensor, operator, airspace design, communications architecture, or commercial service as approved. That distinction matters because headlines about new test sites can easily be converted into a stronger claim than the source makes.

A test environment is not a universal operating environment

Testing has value precisely because it is structured around questions that still need evidence. A research environment can allow teams to examine a system, a procedure, a communication link, or an interaction among them. The FAA's language about gathering critical data and testing new systems makes that point directly.

A commercial team should therefore resist treating the word "test" as interchangeable with "proven everywhere." Conditions that matter to an operation can include the mission, aircraft configuration, crew roles, location, airspace, communications, payload, weather limits, and the procedures used when something changes. The FAA announcement does not say that a result from one test site automatically carries across all of those conditions.

That is not a reason to dismiss test-site work. It is a reason to preserve context. When someone cites a test, the next questions should be basic: What was evaluated? In what environment? Under which procedures? What information was collected? Which parts of the result are directly relevant to the planned operation, and which parts still need their own evidence? Those questions keep a technical discussion connected to the decision being made.

A program can be excited by a capability and still be precise about its status. "A system was evaluated in a test environment" and "our planned operation has an established basis" are different statements. The first may be a useful input to the second. It is not a replacement for the second.

Treat the announcement as a signal about evidence

The FAA says the test-site network supports the development, testing, and evaluation of UAS and related technologies. For operators, that is a useful signal about the type of work that will remain important as missions become more complex: collecting credible information about how a system behaves and how the operation is managed.

A practical internal habit is to create an evidence register for any capability a team expects to scale. The register need not imitate a regulator's process or claim regulatory effect. It can simply state the operational question, the configuration involved, the planned environment, the available evidence, the remaining assumptions, and the person responsible for each open item.

For example, an organization considering a new workflow can separate what it knows from what it assumes. It may know the mission objective and the aircraft configuration it intends to use. It may have a vendor document, an internal evaluation, or a demonstration result. It may still need to establish whether the crew can execute the procedure consistently, whether communication arrangements work at the site, or whether a change in payload alters the plan. The purpose of the record is clarity, not paperwork for its own sake.

This approach also improves communication with decision-makers. A short update that says "testing is underway" can be useful, but it leaves too much unstated. A better update identifies the question being tested, the evidence expected, the conditions that limit the result, and the next decision. That lets operations, safety, procurement, and leadership discuss the same status without each group supplying its own assumptions.

Keep capability, permission, and readiness separate

The FAA's announcement identifies areas of focus, including BVLOS operations, increasingly autonomous operations, advanced air mobility, cargo delivery, and multiple drone operations. Each phrase can invite a broad conclusion. A more disciplined approach is to separate three questions.

First, can the aircraft and supporting system perform the task under the conditions being evaluated? That is a capability question. It concerns equipment, procedures, people, and the way they work together.

Second, what operating authority or requirements apply to the intended activity? That is a permission question. It cannot be answered solely by pointing to a test-site announcement, a manufacturer demonstration, or a general industry trend.

Third, is the organization ready to conduct its own planned work reliably? That is a readiness question. It includes the practical details that make an operation repeatable: responsible people, training, records, communications, maintenance, mission planning, and a way to stop or change the work when the plan no longer fits conditions.

These questions are related, but they should not be collapsed into a single label such as "approved" or "ready." A team might have a technically capable system and still need to resolve its operating basis. It might have an allowable mission concept and still need to establish internal readiness. Conversely, a disciplined crew and sound records do not transform an untested capability into a proven one.

Keeping the three questions separate makes planning more honest. It also makes it easier to assign work. Engineering can own the capability evidence. The responsible compliance function can own the applicable operating requirements. Operations can own the readiness package. Leadership can then make a decision with the boundaries visible.

Use research claims carefully in customer and stakeholder conversations

The FAA announcement is a public policy and research signal. It should not become a marketing shortcut. Organizations discussing advanced drone work with customers, community partners, or internal stakeholders should use wording that describes the source accurately.

It is appropriate to say that the FAA has designated two additional UAS test sites and that the agency says the network will support testing and scaling in areas including BVLOS and autonomous operations. It is not appropriate to imply that the designation itself authorizes a particular commercial mission, validates a particular vendor's claims, or changes the requirements for a specific operation.

This restraint is practical. Overstated claims create downstream problems for the people who must plan, insure, contract, and execute the work. If an early conversation suggests that a capability is settled, the operational team may inherit a deadline without the time or evidence needed to support it. Clear language protects everyone involved.

A simple review step helps. Before a statement is published or shared, identify the source sentence that supports it. Then identify whether the proposed statement adds a conclusion that the source does not make. If it does, rewrite it as a question, an internal objective, or a clearly labeled expectation rather than as a fact.

Build a local learning loop

The UAS Test Site program is national, but the operating discipline it suggests can be local. A small commercial team can borrow the logic of structured evaluation without pretending to be a test range.

For each new mission type, create a defined learning loop. State the objective. Describe the aircraft and payload configuration. Identify the crew and their roles. Record the planned environment and the conditions that would invalidate the plan. Document what happened, including changes and unexpected events. Review the result before treating the workflow as routine.

The output can be compact. A one-page record is often more useful than an unstructured collection of messages and photos. The important point is that a future decision can see what was actually done, not merely that something was tried.

Configuration control is especially valuable. If the aircraft, payload, software, communications equipment, or procedure changes, link that change to the record. A result produced with one configuration should not be quietly applied to another configuration without considering whether the change matters. The FAA announcement does not prescribe an internal template, but its emphasis on testing and evaluation reinforces the value of knowing what was evaluated.

The same applies to people and procedures. If a result depended on a particular crew structure, observation method, communication plan, or site arrangement, record that fact. Otherwise a later team may repeat the headline without repeating the conditions that made the evaluation useful.

Decide what a test result changes

A useful evaluation ends with a decision, not just a finding. The decision may be to continue evaluation, revise the procedure, restrict the use case, train a different role, gather more evidence, or stop pursuing the approach. That is normal. A result that identifies a boundary is still valuable because it prevents a team from treating uncertainty as a solved problem.

Decision records should be specific. Instead of saying "the trial was successful," write what the trial demonstrated, what it did not demonstrate, the conditions that applied, and the next action. That format is resilient when the work is reviewed months later by someone who was not present.

This is also how a team avoids importing conclusions from broader UAS developments without a bridge to its own work. The FAA's new sites may create opportunities for research and learning across the industry. An individual operator still needs a deliberate chain from an external development to its own equipment, procedures, and operating decisions.

The practical takeaway

The FAA's addition of the Choctaw Nation of Oklahoma and Indiana Economic Development Corporation sites expands the U.S. UAS Test Site network to nine locations. The agency says the network will support development, testing, and scaling in advanced areas such as BVLOS operations, increasingly autonomous operations, cargo delivery, and multiple drone operations.

That is an important development for the UAS ecosystem. It is also a reminder that advanced operations progress through evidence and context, not through headlines alone. Commercial teams can respond constructively by recording what they are evaluating, separating capability from permission and readiness, preserving the conditions behind a result, and communicating only what the source and their own records support.

A test site can help the industry answer important questions. A disciplined operator makes sure the questions, evidence, and decision boundaries remain visible when those answers are brought into day-to-day work.