Happy to chat! We’re 100% focused on data collection, so partnering with folks downstream is right up our alley.

And yes-- certainly a tough problem to solve! There’s pattern we keep seeing in the utility inspection space where teams start with a great defect detection or analytics product, then try to verticalize by adding data collection, basically spinning up a small aviation operation inside a SaaS company. I'm sure you've seen this plenty of times. Our hope here is to make collection simple enough so that doesn't need to keep happening :)

I'll reach out!

There’s no real way around BVLOS regs right now. The real problem is BVLOS + need to recharge. If you only solve one, you get limited value. Distributed charging without BVLOS is kind of useless. If a human still has to be there to maintain visual line of sight, it doesn't make much of a difference if the drone can recharge itself in the field. BVLOS without distributed charging also hits a value ceiling. You’re still constrained by battery swaps.

So the solution here is a deep understanding of FAA BVLOS waiver processes + a drone/pad network that is actually scalable.

That said, this is another benefit of working with utilities. When you’re inspecting power line corridors, you’re often operating in what the FAA calls “shielded area.” In practice, that just means you’re flying close to infrastructure that other aircraft tend to avoid anyway. That makes deconfliction much simpler, which in turn makes BVLOS waivers more attainable under Part 107.

The bigger shift is Part 108, which is expected to be finalized relatively soon, and should lower the barrier to BVLOS at scale.