The takeaway: October 19 is the published deadline to request participation in TSA’s BVLOS security roundtables—not a deadline to comply with a new drone rule. Meanwhile, newly reported Ohio planning describes a phased digital network for sharing aviation information, not a live replacement for FAA air traffic control. Together, these developments show why scalable drone operations require both organizational security and dependable coordination, alongside aircraft capability.
TSA BVLOS roundtables: the participation deadline is here
The Transportation Security Administration’s September 4 notice sets October 19, 2026, for receipt of participation requests. It names Kristine Adams at BVLOS@tsa.dhs.gov as the contact. The agency says it may modify registration following publication of its final rule. No replacement deadline was located in this morning’s checks.
The notice seeks representatives of current beyond-visual-line-of-sight (BVLOS) operators and prospective operators or supporters of those operations, plus relevant associations. Attendance is capped at two people per company or association and remains subject to TSA selection. Participants need approval to access Sensitive Security Information and must sign a nondisclosure agreement.
Meetings are planned after publication of the FAA and TSA final rules. Their purpose is individual input on model security-program approaches, not consensus rulemaking. The official published PDF confirms these conditions. The notice itself grants no flight authority and establishes no October 19 compliance obligation.
Our September 7 coverage reported the opening of this process. The material update is that its stated request date has arrived. This is a decision point for organizations considering participation, rather than a fresh announcement that the roundtables have begun. Drone U’s October 16 reminder independently highlights the same distinction between applying now and meeting after the rules are published.
What interested operators can do today
An organization seeking a place should contact TSA promptly, explain its relationship to BVLOS operations and ask for participation instructions. The notice gives a calendar date, not a specific cutoff hour or time zone; this article does not invent one. A request should not be treated as acceptance, and a missed date should not be assumed either automatically waived or permanently closed. Ask the agency.
For internal preparation, nominate people who can explain both the operation and its security controls. A useful preliminary brief would identify who owns aircraft access, software administration, personnel processes, physical equipment protection and incident escalation. These are editorial preparation suggestions, not a newly issued TSA checklist or a claim that every operator faces identical requirements.
Keep sensitive technical details out of an unsolicited introductory email. Begin with a concise description of the organization and ask how information should be submitted. Participation in a security discussion is not a reason to distribute credentials, vulnerabilities or detailed site access arrangements through an unapproved channel.
Ohio planning focuses on information exchange
In a separate October 18 report, Unmanned Airspace describes DriveOhio’s 2026–2029 advanced-air-mobility plan. The reported digital enterprise concept would connect operators, service providers and agencies through a federated exchange of aircraft intent, position, weather, surveillance, infrastructure and emergency information.
The report describes initial information sharing and advisory “shadow mode,” followed by pilot activities and preparation for broader adoption. Its phases cover planning in 2026–2027, implementation in 2027–2028 and preparation to scale in 2028–2029. Those are planning periods—not promised dates for unrestricted commercial service.
Crucially, the architecture is described as complementing existing aviation services, not replacing them. All About UAVs could read the specialist report but could not retrieve the underlying Ohio plan page directly during this review. We therefore attribute the details to that reporting and do not characterize the network as commissioned, certified, funded in full or ready for every proposed use case.
Why the two developments belong together
Security programs and shared airspace data solve different problems. The first concerns how an organization controls and protects its operation. The second concerns how participants exchange useful information. Neither is a substitute for the other, and neither should be confused with permission to launch a particular mission.
For a buyer evaluating a future service, a sensible question is: who is responsible when the expected information is missing, late or inconsistent? Contracts and operating procedures should identify the decision-maker, fallback process and evidence retained after an abnormal event. A network diagram alone cannot answer those questions.
The FAA’s BVLOS proposal overview places security, authorizations, responsibility, reporting and aircraft separation within a broader operating framework. That context helps explain why buying a capable aircraft is only one part of building a repeatable service. It does not turn either item in this briefing into a new approval.
What happens next
Watch for TSA participation guidance and any revised dates, followed by published rules and meeting details. For Ohio, the useful milestones will be primary plan documentation, defined pilot scope, participating organizations and measured service performance. Operators should keep plans, demonstrations, approvals and routine operations separate when assessing progress.
Sources
- Federal Register: “Notice Soliciting Representatives for Technical Roundtables on Security of Unmanned Aircraft Systems” — TSA, Sept. 4, 2026; sets the October 19 participation-request deadline
- GovInfo: official published notice (91 FR 56894) — primary-source PDF confirming the contact, deadline and participation conditions
- Drone U: “TSA Part 108 BVLOS Security Roundtables: October 19” — Oct. 16, 2026, independent confirmation that meetings follow final-rule publication
- Unmanned Airspace: “DriveOhio Launches Pioneering Digital Network Plan for Drone, eVTOL Comms and Airspace Management” — Oct. 18, 2026
- FAA: Beyond Visual Line of Sight (BVLOS) proposal overview — background on the broader regulatory framework
- All About UAVs: “UAV Morning Update: BVLOS Security, Amritsar Airport Drone” — Sept. 7, 2026, our original coverage of this roundtable process
Reviewed October 19, 2026, using today’s Drive briefing as a lead and independently opened sources. No affiliate links, sponsorship or paid placement. Featured image: AI-generated conceptual illustration, not a TSA meeting or Ohio facility. Corrections: help@allaboutuavs.com.
Leave a Reply