Compliance scenario · Regulators, compliance officers, and aviation technical writers
FAA-2025-1908 Proposed rule · subject to change Compliance narrative

BVLOS Infrastructure Inspection

A 2.1 km power-line corridor inspection under proposed Part 108 BVLOS framework. One AI-proposed deviation mid-flight. A complete evidence bundle for post-flight regulatory review.

Source binding ✓ reconciled
Bound to
FAA NPRM FAA-2025-1908 (published Aug 7, 2025) · Flightworks Part 108 scenario doc v1.0
Scope
Governance evidence artifacts for one BVLOS mission. Not a certification claim or legal opinion.
Author
Stephen Sweeney — holds authority over accuracy
Drafting
AI-assisted under governed review. Regulatory facts pinned to docket; architecture claims bound to FlightLaw SP0 + Sentinel v0.2.0.

This document maps product architecture to a proposed federal rule under active revision. See revision policy and authoring trail.

Writing portfolio →

Regulatory status

EventDate
NPRM published (FAA-2025-1908)August 7, 2025
Initial comment period closedOctober 6, 2025
Record reopened (ROW + electronic conspicuity)Jan 28 – Feb 11, 2026
Planning assumption: final ruleMid-to-late 2026

Scenario overview

A utility operator flies a 2.1 km BVLOS corridor inspection along a power-line right-of-way. The aircraft runs a waypoint mission with AI obstacle avoidance. Mid-flight, the AI proposes a 25 m lateral deviation to avoid a construction crane. The governance system escalates to the Principal (the accountable human operator with Part 107 certificate authority). The operator approves with rationale. Battery reaches the return-to-launch threshold; the system denies further mission extension and initiates RTL automatically. The mission completes with a sealed evidence bundle.

Governance stack: Sentinel (edge MAVLink relay enforcing at wire speed) + FlightLaw (constitutional safety kernel evaluating Laws 3, 4, 7, 8).

Mission profile

ParameterValue
Mission typeInfrastructure inspection (power line corridor)
Distance2.1 km linear corridor
Altitude60 m AGL (ceiling: 120 m AGL / 400 ft)
Duration~12 minutes flight time
AircraftQuadrotor, MAVLink-compatible, 40-minute battery
Autonomy levelWaypoint mission with AI obstacle avoidance
Regulatory basisProposed FAA Part 108 BVLOS framework (FAA-2025-1908)

Governance rules

FlightLaw composes four deterministic Laws. Every telemetry frame and every AI proposal passes through all four. Any Law returning DENY blocks the action (deny-wins composition) — regardless of other Law verdicts.

Law 3: Observation (telemetry integrity)

Validates that the aircraft is producing reliable sensor data before and during flight.

RuleThresholdOn failure
GPS satellite count≥ 8 to arm; ≥ 6 in flightDENY (arm) / ESCALATE (degraded)
IMU / compass calibrationCalibrated before armDENY
Telemetry rate≥ 10 Hz in flightESCALATE after 3 misses; DENY after 10
Audit chain integrityHash chain unbrokenDENY (system halt)

Law 4: Resource (battery and thermal)

RuleThresholdOn failure
Battery RTL trigger≥ 20% remainingAUTO_DENY — force return-to-launch
Battery critical≥ 10% remainingAUTO_DENY — force land
Motor temperature≤ 50°CESCALATE at 45°C; DENY at 50°C
Power budgetSufficient for RTH + reserveDENY if reserve violated

Law 7: Spatial (geofence and airspace)

RuleThresholdOn failure
Geofence boundaryInside authorized corridor polygonAUTO_DENY — block command, trigger RTL
Altitude ceiling≤ 120 m AGL mission ceilingAUTO_DENY
Maximum path deviation≤ 50 m from planned waypoint pathESCALATE at 30 m; DENY at 50 m

Law 8: Authority (operator authorization)

Action classConditionVerdict
Pre-flight authorizationMission package approved by PrincipalRequired before arm
Low-risk navigationWithin all Law boundsAUTO_ALLOW
Medium-risk AI deviation< 30 m, within geofenceESCALATE (5 s timeout → DENY)
High-risk actions> 30 m or near Law boundaryESCALATE (no timeout)
Emergency overrideOperator identity + rationaleALLOW with full audit capture

Pre-flight authorization

Frame 0001 — Mission load. Operator loads mission package (corridor polygon, waypoints, weather). All Laws pass. Verdict: AUTO_ALLOW. Evidence hash recorded.

Frame 0002 | Action: AUTHORIZE_MISSION
  Law 8: PASS — principal authorization recorded
    (operator_id: "SS-107-2024", rationale: "Routine corridor inspection")
  Verdict: AUTO_ALLOW
  Evidence: { hash: "b7c2...", authority: { principal: "SS-107-2024" } }

Frame 0003 — Arm and takeoff. GPS 11 satellites, IMU calibrated, battery 97%, power budget sufficient for mission + RTH + 20% reserve. Verdict: AUTO_ALLOW.

In-flight governance

Routine navigation (Frame 3841)

At 10 Hz telemetry, Sentinel evaluates every frame. Mid-mission sample: battery 72%, position 3.2 m from planned path, all Laws passing. Verdict: AUTO_ALLOW. Key property: identical inputs and Law versions always produce identical verdicts — enabling deterministic replay.

AI deviation — ESCALATE (Frame 4200)

AI obstacle avoidance detects a construction crane and proposes 25 m lateral deviation (confidence 0.89).

Frame 4200 | Action: AI_DEVIATION_PROPOSAL { offset: 25m_lateral }
  Law 7: PASS — proposed path inside geofence
  Law 8: ESCALATE — medium-risk AI deviation requires operator confirmation
  Verdict: ESCALATE_TO_OPERATOR
  Evidence: { escalation: { law: 8, timeout: 5000ms } }

Operator sees: "AI proposes 25 m lateral deviation for obstacle avoidance. Approve? [5 s timeout, defaults to DENY]"

Frame 4201 — Operator approves. Principal identity and rationale captured: "Crane visible on camera feed." Verdict: AUTO_ALLOW. The evidence bundle records that AI proposed, system escalated, operator approved — the full decision chain is traceable.

Battery RTL — AUTO_DENY (Frame 6100)

Battery reaches 20%. Law 4 returns DENY; deny-wins overrides all other Laws. Aircraft initiates return-to-launch. No operator input required — constitutional enforcement, not advisory. Operator override would require identity and rationale, itself recorded in the chain.

Post-flight evidence bundle

The evidence bundle (the post-flight audit package an inspector reviews) contains 7,340 hash-chained frames, one escalation, one automatic denial, and sealed chain integrity.

{
  "mission_id": "FW-2026-04-15-001",
  "operator_id": "SS-107-2024",
  "mission_summary": {
    "total_frames": 7340,
    "verdicts": { "auto_allow": 7337, "escalate": 1, "auto_deny": 1 }
  },
  "hash_chain": {
    "algorithm": "SHA256",
    "chain_length": 7340,
    "integrity": "verified"
  }
}

Inspector verification:

sentinel verify --bundle FW-2026-04-15-001.json
# Chain intact. 7340 frames. SHA256 verified.

sentinel replay --bundle FW-2026-04-15-001.json
# 7340/7340 verdicts identical. Determinism verified.

NPRM compliance mapping (FAA-2025-1908)

This table maps Flightworks governance artifacts to proposed Part 108 provisions in the NPRM. Final rule language may differ.

Proposed Part 108 area (NPRM)Flightworks coverageEvidence artifact
Detect and avoid capabilityLaw 7 + Law 8 — AI proposals governed, not autonomousFrame 4200 escalation record
Geofence / airspace complianceLaw 7 — deterministic polygon enforcementPer-frame spatial verdicts
Lost link / endurance proceduresLaw 4 — RTL at 20%, land at 10%Frame 6100 AUTO_DENY record
Operator qualification / authorityLaw 8 — Principal identity, tiered authorizationPre-flight + escalation authority records
Flight data recordingLaw 3 — SHA256 hash-chained audit trail7,340-frame evidence bundle
Post-flight data availabilityPortable evidence bundle formatsentinel verify / replay output
Two-tier permit/certificate structure (NPRM)Law 8 pre-flight authorization + mission package bindingFrame 0002 authority record
Audit / evidence expectations (NPRM)Deterministic replay + Law version auditReplay verification + law_versions in bundle

Revision policy

Authoring trail

✓ chain intact · 4 entries

An AI drafted the prose from the Flightworks Part 108 scenario source document and NPRM public docket facts. Stephen Sweeney holds authority over correctness. Each entry below is a substantive human intervention — tied to a doc version or factual source.

e4a1…9f03 2026-07-07 10:42 AUTHOR EDIT
Replaced anticipated Part 108 requirements framing with NPRM-pinned mapping to FAA-2025-1908 including docket dates, reopened comment period, and explicit proposed-rule disclaimer.
Why: Regulatory accuracy. "Anticipated requirements" is vague; a compliance reviewer checks for docket number and proposed-rule status. This is the writing sample — the disclaimer is the point.
b8c2…41d7 2026-07-07 10:28 AUTHOR EDIT
Added industry equivalents on first use: Principal (the accountable human operator), evidence bundle (the post-flight audit package an inspector reviews).
Why: Standalone readability. A reader without AgentVector vocabulary must follow end-to-end. Terminology normalization against CONTENT-VOCABULARY.md.
3f90…22ae 2026-07-07 10:15 AI DRAFT
Generated mission walkthrough, Law rule tables, and evidence bundle JSON from Part-108-Compliance-Scenario.md v1.0.
Why: Scope given: adapt source doc for web; do not invent jurisdiction rules beyond Laws 3, 4, 7, 8.
0000…root 2026-07-07 10:08 SOURCE BOUND
Bound to Part-108-Compliance-Scenario.md v1.0, FlightLaw SP0, Sentinel v0.2.0, NPRM FAA-2025-1908.
Why: Establishes the root of the chain. Nothing below is authoritative except by reconciliation against these sources.