AuraSpark Drone Works

← Back to Part 108 readiness

FAA Part 108: Detailed technical background

Informational overview: Part 108 is proposed regulation and may change. This page is not legal advice. For official language, refer to FAA and Federal Register sources.

Where we are today

  • Most commercial UAS operations sit under Part 107 and are constrained by visual line of sight assumptions.
  • Routine BVLOS typically requires waivers, exemptions, or special approvals that do not scale well across fleets and regions.
  • Safety arguments are often re-created per operation, and evidence requirements are inconsistent.

What Part 108 is trying to enable

  • A more standardized pathway for routine BVLOS operations with clearer expectations.
  • Stronger alignment between aircraft capability, operator responsibilities, and ongoing safety management.
  • A system that can scale—without relying on “one-off” paperwork per mission.

Why this matters for autonomy

As BVLOS becomes routine, safety is no longer just a flight-performance question. It becomes a systems engineering question: how the aircraft detects hazards, how the autonomy behaves under uncertainty, what the human oversight model looks like, and what evidence exists to support reviews and incident reconstruction.

Operational approvals at a glance

Permits

Lower-risk, bounded scopes intended to streamline common BVLOS missions.

  • Defined operational envelopes and constraints
  • Clear operational procedures and contingency handling
  • Evidence and reporting expectations that support oversight

Certificates

Higher-risk operations that require deeper operational and organizational rigor.

  • More robust safety management and organizational controls
  • More demanding documentation and ongoing compliance obligations
  • Greater expectations for conformance and accountability

The operator-centric shift

The Part 108 direction is to place responsibility on the operator organization—not just an individual remote pilot. That implies defined roles, training, procedures, and auditability across the entire operation.

Operations leadership

Clear accountability for safety, readiness, and adherence to operational limits and procedures.

Flight monitoring

Defined oversight roles that can intervene or execute contingencies when the system goes off‑nominal.

Evidence & reporting

Logs and artifacts designed for review—so safety becomes measurable and improvable over time.

Aircraft, manufacturing, and maintenance implications

Airworthiness acceptance & limits

  • Aircraft are expected to have defined operating limitations and approved configurations
  • Clear maintenance instructions and life-limited parts policies
  • Design and manufacturing rigor that supports repeatable safety performance

Why platforms must be “autonomy-ready”

  • Stable sensing environments improve detect-and-avoid reliability
  • Reduced vibration improves payload integrity and autonomy stability
  • Integration-friendly airframes help standardize fleets and reduce configuration drift

Separation and airspace integration

Routine BVLOS requires a defensible approach to staying safely separated from other aircraft and hazards. Depending on mission profile, this may combine onboard sensing, cooperative surveillance, strategic deconfliction, conformance monitoring, and well-defined contingency behaviors.

The practical question

If an incident occurs, can you reconstruct what happened—what the aircraft sensed, what the autonomy decided, what the human supervisors saw, and what contingencies executed?

That “reconstruction” requirement is why audit-ready logging is not optional for scalable BVLOS.

How AuraSpark Drone Works aligns

Evidence-first autonomy patterns

  • Telemetry and health monitoring treated as first-class design outputs
  • Structured event logging for safety case support and post-flight review
  • Clear autonomy state transitions and contingency pathways

Platform design that supports sensing

  • Airframe features intended to reduce vibration and protect sensor fidelity
  • Integration-friendly architecture for payload and autonomy experimentation
  • Repeatability-focused flight behavior for safer test & evaluation

Traceability matrix

A high-level map of common Part 108 expectations to AuraSpark enabling patterns. This is non‑enabling and provided for context; detailed technical disclosures remain available only under mutual NDA.

Part 108 readiness: BVLOS compliance map

Part 108 challenge / requirement What the FAA expects Our enabling tech (patent anchor)
ADSP & conformance monitoring Scalable separation via ADSPs and alerts when trajectories deviate from plan. Strategic UTM deconfliction (MARL intent negotiation) and a Regulatory Compliance Monitor that enforces safety floors and conformance.
Detect & Avoid (DAA) Keep well‑clear of cooperating traffic and yield to manned ADS‑B aircraft. Cooperative deconfliction plus cross‑modal (LiDAR + thermal) geometric validation and health‑constrained avoidance.
Reliable C2 & lost‑link Coverage planning and clear procedures for loss of command and control. Health‑aware contingency management (RTH / divert / loiter) using remaining‑flight‑time constraints.
Navigation integrity / spoofing Maintain control and integrity during off‑nominal events. Neuromorphic sentinel that detects GPS spoofing in microseconds and rejects compromised fixes at the flight controller.
Cybersecurity Protection of networks/devices/data and incident response. Quantum‑secure links (with pointing–acquisition–tracking) and formation‑level geometric‑median consensus; automated countermeasures.
Airworthiness acceptance & fail‑operational behavior Evidence against consensus standards and reliable, predictable behavior. Hybrid, Redundant, Fail‑Safe Architecture (HRFSA) with proactive fault signatures and adaptive fusion.
Ops roles & SMS Operations Supervisor / Flight Coordinator roles and safety management. Auditable AI Safety & Compliance system that generates version‑correct reports and training/evidence artifacts.
Recordkeeping & reporting Flight/maintenance/personnel logs and incident reporting. AURA Evidence Ledger (WORM, tamper‑evident) with chain‑of‑custody.
Multi‑drone operations Scaled operations, reviewed for safety impact. Fail‑operational fleet re‑tasking and PHM‑aware handoffs to sustain service levels.
Operations over people Mitigations by population‑density category. Regulatory Compliance Monitor enforces density‑based constraints during route selection and intent negotiation.

Note: This mapping summarizes the proposed Part 108 direction and is intended for discussion and partner alignment. We update mappings as the rulemaking evolves.

Primary references

Links provided for convenience. Requirements and timelines may change as the rulemaking evolves.

Discuss Part 108 readiness