FAA Part 108: Normalizing UAS Beyond-Visual-Line-of-Sight Operations
[in effect]United States · safety standard · safety standard
Jurisdiction
United States
Classification
safety standard
Status
in effect
Effective Date
Active
Primary Sources
0 audited
Statutory Scope & Summary
The FAA's dedicated BVLOS rule for unmanned aircraft. NPRM released 2025-08-07 (Docket FAA-2025-1908); comment period reopened January 2026; not finalized as of mid-2026. Will normalize routine BVLOS drone operations (delivery, infrastructure inspection) without case-by-case waivers.
Covered Sectors & Application Domains
Regulatory Analysis & Inquiries
5 entriesWhat does FAA Part 108: Normalizing UAS Beyond-Visual-Line-of-Sight Operations cover?
The FAA's dedicated BVLOS rule for unmanned aircraft. NPRM released 2025-08-07 (Docket FAA-2025-1908); comment period reopened January 2026; not finalized as of mid-2026. Will normalize routine BVLOS drone operations (delivery, infrastructure inspection) without case-by-case waivers.
Where does FAA Part 108: Normalizing UAS Beyond-Visual-Line-of-Sight Operations apply?
FAA Part 108: Normalizing UAS Beyond-Visual-Line-of-Sight Operations is recorded as a safety_standard applying in United States on the DEPLOY registry.
Is FAA Part 108: Normalizing UAS Beyond-Visual-Line-of-Sight Operations still in effect?
FAA Part 108: Normalizing UAS Beyond-Visual-Line-of-Sight Operations is currently in effect and applies to covered operators in the named jurisdiction.
What types of robots does FAA Part 108: Normalizing UAS Beyond-Visual-Line-of-Sight Operations apply to?
FAA Part 108: Normalizing UAS Beyond-Visual-Line-of-Sight Operations is recorded as applying to drones on the DEPLOY registry.
Which robot models on the DEPLOY registry fall under FAA Part 108: Normalizing UAS Beyond-Visual-Line-of-Sight Operations?
8 robot models on the DEPLOY registry match the form-factor scope of FAA Part 108: Normalizing UAS Beyond-Visual-Line-of-Sight Operations: A200-XT, AEVEX Strike Drone, AIR ONE, ALIA-250 and 4 others. Form-factor scope match does not by itself establish compliance status; review the underlying primary sources for each operator.