BVLOS Drone Delivery and Operating Sites
Published
Law checked through .
BVLOS operations require authority that actually permits flight beyond the ordinary visual-line-of-sight limit. Commercial package delivery can also require Part 135 air-carrier certification and operation-specific exemptions or authorizations. A proposed Part 108 framework is not permission to begin flights. Texas operators must also address launch and landing rights, Chapter 423, appropriate local ground-site requirements, and any environmental review attached to federal approvals. [1, §§ 107.31 and 107.200 through 107.205; 2; 3]
Identify the operation before choosing the pathway
Delivery, pipeline inspection, agricultural dispensing, and public emergency response are different missions. Aircraft weight, payload, compensation, route, population exposure, airspace, and operator status affect the available pathway. A small aircraft carrying a camera within sight does not establish the approvals required for an unattended package-delivery network. [1; 2]
Under Part 107, § 107.31 establishes the visual-line-of-sight requirement. A video link does not itself satisfy it. Waiver relief under §§ 107.200 and 107.205 is tied to the particular regulations and a showing that the operation can be conducted safely under the proposed conditions. The operator must read the grant's geographic, aircraft, personnel, communications, and other limitations. [1]
Part 135 delivery approvals
The FAA identifies Part 135 as the certification route used for qualifying package-delivery air carriers. Certification and exemptions address different issues. An operator may need exemptions from particular requirements, authority for the aircraft, and approvals for the operational area. The FAA's delivery materials also identify environmental review and community considerations within the approval process. [2]
An individual operator's grant is useful as an example of the questions the FAA addresses, but it should not be copied as if it automatically covers another company. A new aircraft configuration, service region, or operating model may fall outside the granted authority. Commercial contracts and customer launch announcements should therefore distinguish a successful demonstration from authority for routine paid service.
Proposed routine BVLOS rules
The August 7, 2025 NPRM proposed a framework that includes Part 108, with operating requirements and authorization structures different from the ordinary Part 107 model. The proposal and subsequent docket actions inform planning. The final adopted text, effective date, transition rules, and actual grants control when available; a proposed rule or pending White House review does not itself authorize a Texas mission. [3]
A fleet planning against a proposed framework should maintain two records: the authority for present flights and the expected changes if the proposal becomes effective. Procurement assumptions about detect-and-avoid capability, communications, staffing, and aircraft approval should state which record supports them. This avoids representing an anticipated future pathway as a current entitlement.
Launch, landing, and ground facilities
Airspace authority does not supply a lease, easement, or right to enter private property. An operator should identify the owner or lawful occupier of each launch, landing, charging, storage, and customer-receipt location. Applicable building, fire, electrical, access, and land-use requirements need their own review. The FAA's state and local fact sheet distinguishes federal aviation authority from preserved state and local interests, while warning against conflicting flight regulation. [4]
Texas Government Code § 423.009 restricts political-subdivision regulation of unmanned-aircraft operation but preserves specified powers. Its text should be read alongside the particular municipal measure. A rule directed at a ground facility and a rule dictating flight routes present different questions. Neither all local rules nor all local concerns disappear because the aircraft has an FAA approval. [5, § 423.009; 4]
Texas imagery and infrastructure restrictions
Chapter 423 regulates image capture and particular protected-facility operations separately from FAA permission. A delivery route may collect incidental imagery or pass a facility covered by § 423.0045. The operator should examine the statutory definitions, conduct elements, and exceptions, including the qualified commercial-operation exception. The presence of a critical facility is not a complete statement of the rule, and the facility owner does not receive general authority to disable an aircraft. [5, §§ 423.001 through 423.006]
Remote ID, registration, and airspace authorization also remain separate inquiries. An approval for BVLOS does not necessarily waive every other requirement. A useful route file identifies the instrument satisfying each requirement and the person responsible for keeping it current. [1; 6]
Hypothetical suburban delivery network
A Texas retailer proposes deliveries from a parking-lot hub to residential properties. The route assessment should identify the aircraft and carrier pathway, BVLOS authority, airspace, communications coverage, launch-site rights, property permissions, customer handoff, and noise concerns. An apartment delivery point can create different ground-access and pedestrian risks from a fenced industrial receiving area. Each change should be tested against the actual approval, not merely the distance flown.
The incident plan should also identify who receives a lost-link alert, who can suspend service, how a downed aircraft is recovered without trespass, and which reporting thresholds apply. These are recommended program controls connecting the approval conditions and separate legal duties; they are not a claim that every drone approval contains identical procedures.
Sources
- 14 CFR Part 107, especially §§ 107.31, 107.41, 107.200, and 107.205.
- FAA Package Delivery by Drone
- 90 FR 38212
- FAA State and Local UAS Fact Sheet
- Texas Government Code Chapter 423, especially §§ 423.002, 423.0045, and 423.009.
- 14 CFR Part 89, Remote ID; 14 CFR Part 48, registration.
