Drone delivery you see overhead is Part 135. It is not Part 108 — and not your Part 107 ticket.

The Brief

A remote pilot on a roof inspection hears the high whine first. Ladder still locked. Client on the driveway, tablet open to the statement of work. Then the aircraft slides past the ridge line — delivery shape, fixed transit, already gone before the client finishes asking whether “those autonomous ones” mean next week’s mapping job can go BVLOS without a waiver.

That mash-up is the story. Not the logo on the belly. The rule the sound invents in a Part 107 pilot’s head.

You feel the pressure in three beats: the aircraft looks routine; routine feels like precedent; precedent feels like permission. None of those beats is a certificate. The client is not being unreasonable. They are watching the same sky you are. Your job is to keep the conversation on the paper you hold — remote pilot certificate, any waiver you actually have, LAANC where it applies — not on the aircraft that just crossed the fence line.

Today’s delivery networks expand under Part 135 air carrier certificates, Operations Specifications, and case-specific tools such as 49 U.S.C. § 44807 exemptions and BVLOS waivers — the path the FAA still describes for small package delivery. Part 108 is still a draft final rule at OIRA (RIN 2120-AL82, received 10 July 2026, still Pending EO 12866 Regulatory Review on RegInfo rrid=1457213). Watching a carrier use its approvals is not the same as holding them.

The rest of this piece earns that distinction with FAA primaries: the package-delivery hub page, the five-phase Part 135 certification process, the July 2026 PEA/FONSI/ROD, the Part 108 NPRM, and the live OIRA record. Story first. Then the paper.

A delivery drone is not a general BVLOS rule

You are under Part 107. Delivery traffic has become ordinary furniture in that metro. Ordinary furniture feels like precedent. Precedent feels like permission.

It is not.

FAA’s package-delivery explainer is blunt about the current door: operators that want small package delivery use the existing Part 135 certification process and obtain an exemption or waiver for BVLOS delivery. That is a certificate-holder path with manuals, maintenance, named directors, and a risk showing — not a public corridor opened by proximity to someone else’s aircraft.

When the client points up and asks whether autonomy is “open,” translate the question. They are asking whether your next mission can leave visual line of sight. Under 14 CFR § 107.31, visual line of sight is still the default for Part 107. Under § 107.33, a visual observer is still a Part 107 tool when you use one. Under § 107.37, right-of-way rules do not rewrite themselves because a logistics brand got louder over the subdivision.

Fact: A delivery aircraft in shared low-altitude airspace is evidence of that operator’s approvals, not a general BVLOS rule.
Interpretation: The mash-up fails when you treat someone else’s OpSpecs as your waiver.

Part 135 is the delivery door open today

Compensated BVLOS package delivery — carrying the property of another for hire beyond visual line of sight — runs today through Part 135 (with the related Part 119 air carrier certificate and OpSpecs). The FAA’s July 2026 programmatic environmental decision for Part 135 drone package delivery states the same architecture in primary language: Part 135 certification is currently the only path for that use case, and delivery continues under Part 135 until a Part 108 final rule issues and prerequisite tasks are finished.

The package-delivery page is equally plain: drone operators that want small package delivery must use the existing Part 135 certification process and obtain an exemption or waiver to provide BVLOS package deliveries. All Part 135 applicants must go through the full five phases of the certification process. FAA’s Part 135 certification process page names those phases as Pre-application, Formal Application, Design Assessment, Performance Assessment, and Administrative Functions — the last of which is where the certificate and OpSpecs issue. This draft does not invent what happens inside each gate beyond what those FAA pages state.

What the package-delivery page does flag for UAS applicants, without turning this into a how-to: a concept of operations during pre-application; airworthiness evidence or a § 44807 petition; document compliance or petitions for exemption where traditional Part 135 text does not fit drones; NEPA review before the certificate issues; and, during phase 4, on-site facility inspection plus validation testing of flight and maintenance procedures, including practical tests for pilots in command and check pilots. That is a certificate-holder path. It is not a Part 107 remote pilot certificate with a louder motor.

Wing received early Part 135 UAS air carrier authority in 2019; Amazon Prime Air and Zipline followed on the same certificate family in later years (FAA package-delivery timeline). Those names matter as examples of who walked the Part 135 door — not as a free pass for everyone else, and not as invented OpSpecs text or unverified city counts.

Fact: Part 135 (+ case-specific approvals) is the live scaling path for carrier package delivery.
Interpretation: Expansion headlines are usually OpSpec and exemption stories, not Part 108 stories.

July’s nationwide PEA streamlines review — it does not authorize flight

In July 2026 the FAA issued a Final Programmatic Environmental Assessment (PEA) and FONSI/ROD for Part 135 drone package delivery operations in the United States. Read that document for what it is: an environmental decision covering a defined proposed-action envelope, with mitigation measures that operators must follow. For operations that exceed the PEA’s analyzed limits, FAA says it will supplement through a separate NEPA document or tiering. The Federal Register notice of availability (91 FR 48208) describes the same action: commercial drone package deliveries under Part 135, with a FONSI when mitigation in the PEA is implemented.

What the PEA is not: a flight authorization. It does not replace Part 135 certification. It does not issue OpSpecs. It does not move Part 108 from OIRA into the Code of Federal Regulations. The PEA itself is clear that the operative approval enabling package-delivery flights in a specific operating area is the issuance (or amendment) of OpSpecs — after the certificate architecture is in place. In primary voice: Part 135 certification is currently the only path for drones to carry the property of another for compensation or hire BVLOS, and those operations continue under Part 135 until a Part 108 final rule issues and prerequisite tasks are finished.

Fact: The July 2026 PEA/FONSI/ROD finds no significant impact inside its analyzed envelope with required mitigation; it streamlines environmental review for covered Part 135 delivery proposals.
Interpretation: Faster NEPA inside that envelope is still not a ticket to fly — and still not Part 108.

A carrier’s OpSpecs stay on that carrier’s certificate

When a Part 135 delivery operator flies BVLOS without a human visual observer along the route, the privilege rides with FAA-validated detect-and-avoid systems, supporting approvals, and OpSpecs written for that certificate — including geographic limits. The July 2026 PEA states that when certificate holders change scope — new delivery areas, new hubs, modified times — they must apply for an OpSpec amendment. Environmental assessments for Amazon and Wing expansions show the same pattern in practice: the federal action is often an OpSpec amendment for a defined operating area, not a nationwide blank check from the certificate alone.

An independent Part 107 operator on an enterprise mapping job has no legal claim to those OpSpecs. Citing a competitor’s Part 135 delivery network is not a substitute for your own waiver or exemption.

Shared airspace is the practical sting. Part 107 commercial work and Part 135 delivery traffic both live in low-altitude volumes — often under 400 feet AGL in the same suburbs. The FAA’s own package-delivery materials discuss BVLOS delivery traffic in that low-altitude band and point toward UTM as a future traffic-management layer; direct ATC services are not what keeps those packages on the wire today. You share the sky whether you asked for the neighbor’s delivery network or not. Sharing airspace is not sharing certificates. Deconfliction on a Part 107 job still starts with eyes, observers where used, and the authorizations on your paperwork.

Part 108 is still at OIRA — not a street ticket

Part 108 (RIN 2120-AL82) is the FAA’s draft effort to normalize many BVLOS operations, including a longer-term home for package delivery after a final rule and implementation prerequisites. The August 2025 NPRM (90 FR 38212, Docket FAA-2025-1908) proposed that framework. The draft final rule was received by OIRA on 10 July 2026 and remains in Pending EO 12866 Regulatory Review on RegInfo record rrid=1457213.

Pending review does not create standardized Part 108 corridors. It does not wipe § 107.31 or § 107.33 for Part 107 flights. It does not launder a carrier’s approvals onto everyone else. Even FAA materials that anticipate a Part 135 → Part 108 transition put that transition after a published final rule and completed prerequisites — not after a delivery drone crossed your fence line.

Horizon, labeled carefully: NPRM (August 2025) → draft final at OIRA (received 10 July 2026, still Pending) → eventual Federal Register final rule → then implementation prerequisites. The July 2026 PEA estimates that Part 108 package delivery operations may commence one to two years after rule issuance, pending development and acceptance of industry consensus standards and other prerequisite milestones. That is an FAA estimate in the PEA, not a hard DPB clock and not a promise that OIRA will finish on any particular date. Do not treat a PEA planning estimate as an operative deadline for Part 107 crews.

Fact: Part 108 is not operative law while it sits at OIRA.
Interpretation: Delivery growth proves Part 135 authorizations are being used. It does not prove Part 108 finished.

What a Part 107 mission still requires

In delivery-heavy suburbs, keep the visual scan honest. Deconflict against automated transit paths. Keep LAANC current where it applies. Brief observers on what local delivery traffic actually looks like — silhouette, sound, typical transit height — so a surprise transit does not become a mid-mission argument on the radio. Do not rewrite right-of-way under 14 CFR § 107.37 because a logistics brand got louder.

If the client asks whether “autonomy” means the visual observer can go home: answer from your certificate and your waiver — not from the aircraft that just crossed the fence line. Part 107 stays VLOS unless an individual waiver says otherwise.

Practical texture for the driveway conversation:

• Name the certificate on the table: Part 107 remote pilot (plus any waiver you hold), not Part 135 OpSpecs.
• Separate “I see delivery traffic” from “I am authorized to leave VLOS.”
• If the client wants BVLOS for this job, the path is their own CONOPS, risk showing, and waiver/exemption process — not a screenshot of a carrier marketing page.
• Before the next mission in a delivery-heavy grid: refresh NOTAMs and LAANC, brief the observer on transit patterns you have actually seen, and write the go/no-go in language that survives a phone call with insurance or the FSDO.

None of that is legal advice. It is the difference between flying the certificate you hold and flying the story the sky invents.

Flight-Ready — pull this into the mission brief

Delivery volume grows under Part 135 certificates, OpSpecs, and customized BVLOS safety cases — not under an operative Part 108. Part 107 commercial pilots share that low-altitude airspace whether they asked for the neighbor’s delivery network or not.

A carrier flying under its own approvals is not legal precedent for the next Part 107 mission. Do not treat Part 108 as in force. Do not assume regulation has eliminated visual observers for Part 107. Do not assume “autonomous delivery corridors” rewrite § 107.37. Do not treat the July 2026 PEA as a flight ticket.

Bottom Line

The sound overhead is usually a Part 135 story with OpSpecs attached. The July 2026 PEA streamlines environmental review inside a defined envelope; it still is not a flight authorization. Part 108 is still at OIRA. For ordinary Part 107 commercial work, visual line-of-sight stays the default unless your own waiver says otherwise — and a carrier’s OpSpecs never become that waiver by proximity.

Sources

• • FAA Package Delivery by Drone (Part 135): https://www.faa.gov/uas/advanced_operations/package_delivery_drone
• • FAA Part 135 Certification Process: https://www.faa.gov/licenses_certificates/airline_certification/135_certification/cert_process
• • FAA Part 135 Final PEA/FONSI/ROD (July 2026): https://www.faa.gov/uas/advanced_operations/nepa_and_drones/Part_135_Final_PEA_FONSI-ROD-NOA_Appendices_A-D_Final.pdf
• • Federal Register: Part 135 PEA/FONSI/ROD Notice of Availability (91 FR 48208): https://www.federalregister.gov/documents/2026/07/30/2026-15417/notice-of-availability-of-the-final-programmatic-environmental-assessment-and-fonsi-rod
• • Federal Register: Normalizing UAS BVLOS Operations (NPRM): https://www.federalregister.gov/documents/2025/08/07/2025-14992/normalizing-unmanned-aircraft-systems-beyond-visual-line-of-sight-operations
• • OIRA RIN 2120-AL82: https://www.reginfo.gov/public/do/eoDetails?rrid=1457213
• • 14 CFR Part 135: https://www.ecfr.gov/current/title-14/chapter-I/subchapter-G/part-135
• • 14 CFR Part 107: https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F/part-107
• • 49 U.S.C. § 44807: https://www.law.cornell.edu/uscode/text/49/44807

The Drone Pilot Brief does not accept payment for editorial coverage.