Bri O'Neill spends her days making sure the sky stays boring in the best possible way. She's an ASTM F-38 standards author and founder of Altimitus, helping UAS, the industry, turn P108 from a proposed rule into safe everyday operations. If you didn't know what all of those words meant, don't worry, we're gonna talk about it. Bri is also our guest today on the skyzero.io podcast. Bri, thank you so much for being on the podcast today. I really appreciate you coming on. Thank you so much for having me, Kyle. It's great to be here. how did you get into the role? Like how did you start doing what you're doing? And what is that? Tell us more about you. so I'm a UAS systems engineer. this is how I've spent my career. started in the defense space working in battlefield radar, doing digital signal processing to detect drones, trying to retrofit really old radars that were used in the battlefield for large, fast, high altitude things to now Mm. find what we call low, slow, small or drones. so that was when I figured out what the radar signature of a drone looks like. and from there Mm. I went on to start developing drone platforms both in defense and commercial spaces. And as I moved from the defense to commercial space, the biggest challenge that I saw was integration into the NAS and the standards required in order to do that. So almost a decade ago, I was putting kind of the first tiny little Fordham radar onto the front of a scanny goal, seeing if we could do detect and avoid forward-facing. pretty beautifully but also the technology has come a long ways. And then on the standard side, trying to map that to like the C and Avoid advisory circular. How are we actually going to say that a radar counts as C and avoid when you don't have a pilot up there? Right, right, right, right. There's no one to see. Yeah. right, exactly. So I went from you know working on transitioning defense platforms to commercial platforms by enhancing those safety critical technologies like DAA or Detect and avoid Command and Control or C2 links, really to be able to fly beyond the visual line of sight of the operator. I also spent some time kind of diving deep into the technologies used for command and control, and hopefully eventually they will be used for things like electronic conspicuity that can be used for detect and avoid. And that was cellular, like terrestrial networks. So I worked with Verizon for a while on a program to test drones using the cellular network as the command and control link. Today, most drones that are flying Beyond Visual Line of Site are using cellular, and it's pretty reliable. robust, especially if you've got more than one carrier in there, more than one SIM card, or if you're using an electronic SIM. But at the time we were really just trying to figure out how does the existing terrestrial network perform at altitude. the results were actually really promising and that's why so many drones fly over cellular today. Cool. so since then been working on presenting to the FAA on means of compliance for uncrewed aircraft. so similarly the sea and avoid requirement, what are we gonna do about that in the standards world? getting all the way into things like cybersecurity and how do we secure the systems that don't have a pilot on. Yeah, yeah, yeah, yeah. Right. That's such a big s I I feel like uncovered part of it that people don't spend enough time on. the the more computers we put in these things, the more possible that becomes. Okay. when I I think about radar systems, they they normally sort of exclude the you know, the runways that they serve. And that's on purpose so that operators can like see what's coming at them. But what else is different when you're trying to reconfigure a radar to see low small and slow? I was on the digital signal processing side. So I was actually trying to figure out in our algorithms what tracks are really tracks that we're interested in and what aren't. And the hardware for the and software for these types of systems was developed based on intercontinental ballistic missiles. so I was really looking for an ICBM type signature, which is high in the higher in the sky, you know, not not gonna be within the trees or anything. it's gonna be moving really quickly because we're expecting to have to react to it really quickly. and then it's gonna move, yeah, really fast. because again, you wanna get there really quickly. and then they're large. That that's the other thing, is that you know, ICBMs or even Aircraft that you don't want to be in your space, then they're pretty large. and so as I wrote those filters, what I was looking for was exclude everything that's low down, because what's low down are helicopters. I wasn't really looking for helicopters. radar signature-wise, like a wind blowing through the trees or a like a big cloud formation, you know, those are the types of things that I want to be able to exclude so that I don't think that those are, you know, fast moving targets. But when you try to put slow moving targets that are low to the ground and small, they end up looking a lot like birds. Or moving leaves. And so getting more granular in how we analyze those radar signatures, it came down to things like studying how birds fly on thermals and seeing if we wow. could come up with ways to say that pattern looks a lot like a thermal. And I know that drones do not have that type of sensing to be able to fly on thermals. And so if we could see flocks of birds or even individual birds that were flying in a pattern that looked like a thermal, it would look really different than a drone's pattern. wow, wow, wow, wow. Okay, right. I hadn't I hadn't thought of that. But yeah, you're gonna have to filter out leaves too while you're at it. Like it's it's gonna be Right. all of the things, not to mention birds. Okay, cool. and this eventually brings you the other one that you okay, so UAS, which is uncrewed aviation systems and the NAS, right? So that is the national aviation system, airspace system, something? Go ahead. Yeah, yeah, yep, absolutely. Yep, I think of it as the Okay, cool. you know, in in my background it's really been in the US, but really any civil aviation authority, what your national airspace is, is the space that is regulated where you have to follow rules. I think they might call it like ATM air traffic management and other parts of the world. But yeah, that same concept. Okay, cool. And that brings us to Altimetis So tell me about that. Like what does Altimetis do? what's your role there? tell us more about how that be you becoming like an entrepreneur and a business leader, in in and amongst all the other hats that you're wearing. Tell us about that transition. Absolutely, Kyle. So as I mentioned, I've been spending time thinking about what drones flying beyond line of sight of the operator looks like in the commercial space for over a decade. So it's been about a decade since Part 107 came out, which allows commercial operators to operate in the national airspace in the US, but it does require waivers in order to fly beyond visual line of sight, over people at night, moving vehicles, that kind of thing. And so what really inspired me to start Altimidus was the release of the Proposed rulemaking for part 108 of BV LOS rule. I had been part of BVLOS ARC years prior, been part of remote ID. So been thinking about how to scale these technologies for a while. And then to see that validation from the regulator that the regulatory pathway is here, I knew there'd be a need. That's the thing, the technologies that have been developed for part 107, where there has been commercial viability for drones in the US, a lot of those technologies aren't going to scale. going require hardware changes, network changes, software changes, and some of those changes are deep in the architecture. So for example, a lot of folks who are using these systems, they're using open source software for flight controllers and for ground control stations, which are really great ways to design and test a new drone. they're not built for one to many. They're not built for beyond visual line of sight. And when I Mm. say that, I can get kind of granular about how how how deeply I mean that in that, for example, traditional RF links, right, they're line of sight. And so really what you're depending on is you know over-the-air waves. But now beyond visual line of sight, you're worrying about not just over-the-air waves, but then also you know wide area network. concerns. Right. Right. And and the reason that that matters is that even under the Part 108 requirement, you do still have to be able to communicate with the ground. We can't just throw your aircraft up there and say have a nice life and then I'll see you when you land. You have to maintain that connectivity and that connectivity requires software and hardware. Got I got I got it. Okay. So Altimetis is helping clients make these shifts. But also, so what's 107 versus 108? Like, help me understand in in the short version, but like I guess 108 is the new one or something, like help help. readers and I understand that better. Absolutely, absolutely. So as I mentioned, Part 108 is really written for line of sight, one-to-one commercial operations. So think like early days when this was used for like film and television or for like real estate photography. Those are the examples I can think of that go kind of far back. So how 107 started was, you know, there really wasn't a legal framework to fly your drone and make money while you do it. And Yeah. so that's what Part 107 was for. So it has a license approach. so you have to get a Part 107 license. there are requirements associated with that. Later on, the remote ID rules got rolled in as well. So now, you know, to make money with your drone, you not only have to have your Part 107 license, but you have to, you know, comply with some technical requirements. and then if you want to fly beyond visual line of sight, you need a waiver. And there's a bit of a maze to get through a waiver with Yeah. Right. the regulator because those are all you know reviewed and approved onesie twosie. and so if you need one of those for every BVLOS flight that you're gonna do versus wow, wow, wow, wow. Right. going like a route for a COA. You know, there have been waivers that are, location-independent waivers that have to do with the type of, for example, infrastructure inspection. Okay. but still it's a whole, it's a whole market today that just waivers. there's a lot of market today for accomplishing waivers, doing the content with the FAA to make sure that you're going to, you know, be allowed to fly in that space. The FAA staffs for that. And frankly, it's just not scalable at the scale that, Okay. you know, technology is gonna be able to keep up. So unlike something like general aviation where you, key up and talk to a controller and file a flight plan and maybe you did it in foreflight ahead of time, in in this world you're literally applying for waivers like before you take off. and it sounds like you're hinting at there's some concept of like, I'm I do pipeline inspections or I do you know transmission line inspections. So maybe I can get like a longer term waiver. I think you said location independent, but how like how and when we don't we got I don't want to dive too deep, but but help us understand these waivers a little bit. Yeah, yeah, absolutely. So the waivers that I've seen, some of them are as small as location dependent. So if you're doing routine inspections of like a bridge, and when your aircraft is gonna go underneath the bridge and no humans can see it, you're no longer flying line of sight. And so you need a waiver Right. to do that under part 107. you don't necessarily and if you're gonna do you know, repeatedly, then the waiver application would be, you know, we're gonna do it this many times a year. At that Wow. point you probably have to talk about, you know, what kind of weather we are gonna fly in versus what weather we're not gonna fly in, if you're gonna do it year-round. so be as small as that and then the waivers that can apply for operations that are location independent they often have to do with the use case. So the example I'll I'll mention is the utility inspection. I've seen waivers there that are location independent that will focus really on, safety. How do you know that there's not gonna be air and ground risk in that area? And utility companies really have an advantage here because they can use what's called shielding. so they'll essentially say, I'm gonna fly within a couple hundred feet of my wires. No should be flying there anyways because that's pretty unsafe to be flying right Okay. Right. next to power lines. And then also I have right of way underneath the power lines. So no one should be having their picnic right underneath my power line. I'm not going to have a ground risk concern. Right. Right. So really the liability goes back onto the operator and the utility company of if I ruin anyone's day it's going to be my own. Got it. that gets nuanced though, because a lot of utility lines are also mixed with agriculture. And agriculture has not only drone use cases, but obviously crewed aircraft use cases. And so that's the one that scares me most about those types of waivers that I'm talking about, is that you know I a lot of those are not equipped. So they don't have ADSB out in, a crop duster, for example. That's Mm. Right, right, right, right. exactly the type of risk that is not holistically addressed by Part 107 waivers today. Got it. Okay. So one eight is the replacement then? And it sounds like it's like but by the context I'm picking up its proposed rule right now. Like we're not yet there, I guess. That's right, that's right. In the United States, part one eight is a notice of proposed rulemaking. and it was released mid-year last year, and the intent is to have the final rule really any day now. would have expected it last month, but yeah, hang hanging on for that. And and what that will allow are routine BVLOS fights and a route for becoming an operator. so you'll need Okay. to kind of declare that you're going to be a part part 108 operator and meet all the requirements required thereof. It really puts the responsibility on the organization as an operator as opposed to an individual pilot, which you know in in aviation philosophy that's a really big change because a lot I'll Yeah. I'll kind of contrast it with mosaic rules. so for light sport aircraft in the United States, recent rules can't out and one of their requirements is that in order to avoid damage to people or property on the ground, the operator is required to have visual sight of where they would land in case of emergency at all times. Mm. Mm-hmm. So if you're flying in a space where it's like I don't really have an out here, that's on the pilot, it's on a person. Right, right. That's a that's really different than putting that requirement on a system. Right. But I guess that makes sense though. Like when we talked to Bobby Healy of Mana in in the last episode, like we were talking about fleets of these things and and I don't think Bobby intends to have like for seventy five drones, seventy five pilots. I I think we intend to have the system fly them. So right, that okay, so that is a big change then that we're talking about, but it enables a lot at the same time, so worth it. Totally worth it because the technology, some of them enabling technology has been around for a while, some of it's still being developed, and a lot of it really needs to be tested at scale. Got it. Right. Right. And that brings us back to Altimetis, like testing that at scale. Nice. Okay. Cool. when we think about safety it sounds like that would have been a lot of what's in one eight, and thinking about what makes it safe. How do you do beyond visual line of sight, BVLOS, operations, especially in a fleet context like we're talking about where there's no individual pilot responsible. So what does it look like? How do you go about ensuring safety in a situation like that? How do you avoid the crop duster? How do you avoid a bird? How do you like how do you avoid yeah, what does safety look like? Absolutely. There's two sections of part 108 that I think I'll reference to give the flavor of what it describes. The first one is a concept called simplified user interactions. So this is a requirement in part 108 that essentially the operator shouldn't be able to crash the airplane. Okay. And so this has been interpreted in standards body as put simply no stick to servo. Okay. Okay. right, which means you know, if if you're if you're sitting in front in an operations center and you're commanding a drone, this would be the difference between using a literal hand controller and and pointing and clicking on a user interface, on a graphical user interface to say go here. so under part 108, that hand controller requirement, it doesn't explicitly say no hand controllers and it doesn't explicitly say no stick to servo. that interpretation is for the industry. Okay. Okay. Yep. to document and require to say this is what we think simplified user interaction means. Got it. Okay, so I see. So it doesn't necessarily say that you can't specifically control it. But I guess the assumption there is if you can let any one human control a BVLOS drone which is like maybe two kilometers away and so on, then you know, they and they try to start connecting it. they might be dealing with information which is, you know, a couple of seconds behind and they might, you know is that sort of the why behind it? that that taking control over a specific drone mid flight is a bad idea because of the the the ability to sense or what's the why behind it? I my my interpretation is the why behind it really has to do with one that it's beyond visual line of sight and you can't see it. Yeah, yeah. therefore doing stick-to-servo type stuff that you would do with an aircraft that you're actually looking at in the sky is pretty different. and the other one is one to many, is that this rule is really intended so that you're not just operating one aircraft at a time. You can operating be operating tens of aircraft, a hundred aircraft at a time. Right. Yep. And so if you have stick to servo capabilities with a hundred aircraft at a time, the amount of concentration that it takes the operator to do stick to servo, even with just one, Right. Right. it it doesn't Okay, so this simplified user interaction on some level is about workload and about making sure that the the the device itself, the aircraft, ha UAS system has enough smarts on board to be able to control itself, I guess. Am I hitting it now? You said it so beautifully, Kyle, better than I could have said it, because your interpretation is exactly where we have kind of landed in the standards groups, is that Okay. what that requirement of simplified user action action simplified user interaction actually drives is the brain on the aircraft or the flight controller or autopilot. Yeah. Yeah. Yeah. Yeah. So it kind of forces you to be able to do it. There's no it's probably good enough. no, it it really has to be good enough and and and not depend on the human. when we talk about these kinds of safety implications. Does this drive anything else? I mean, we've talked a little bit about how, you know, operators shouldn't be able to crash, no stick to servo. okay, so that kind of gets like to piloting and and that aspect. What about other aspects of sort of the business of flight? what else might change? Yeah, so that that's the other area of part 108 that I'm really interested in right now. and that's the that's requirements around no probable failures shall result in a hazard. Okay. So that's regulatory text. there's a decent amount of preamble text in the Part 108 Notice of Proposed Rulemaking that describes the philosophy behind what what is considered probable and what is considered a hazard. but that's that's the requirement that is being kind of interpreted in industry standards bodies to say how do you determine what your hazards are? How do you determine whether they're probable, and then how Mm-hmm. do you show that you don't have a probable failure that's going to lead to a hazard? Right. Right. And that's pretty Part 108 specific, because that's how that language is written. There is an analogy here to Transport Canada. So Transport Canada, section 922 for remotely piloted aircraft systems, they talk about so not only no probable failure, but no single point of failure. Mm, okay. and I love that one because you know mixed common cause type failures can become probable if they're common, but you know, a single point might not necessarily drive it. not exactly how the the rules are written for part 108, but I think a really good safety philosophy to follow that single points of failure are exactly that. They're single points. that means you don't have a mitigation. Right. So this shapes the design of the aircraft, and the way that we have to think about power plant and steering abilities and and everything else. but also th that word hazard, you know, like wha how how might we predict what hazards we might be able to cause? Like, does that actually start to get into the context we're flying in, or is that mostly about the aircraft itself? It it's really both, Kyle. And actually there's even a third degree to it, which is that which regulation you're applying to. so I kind of Mm. think of three inputs when we're doing this type of analysis. One is the architecture of the aircraft. one is the concept of operations. Where are you flying? What kind of commission are you going to do? And then finally the regulatory approach. So what rule are you going to fly under? For example, Mm. it's not guaranteed that part 107 waivers won't be allowed after part 108 is out. So there could be operations that you still do BVLOS, but under Part 107 with a waiver. Those regulations are going to be really different than complying with Part 108. Got it. Okay. Interesting. when you and I talked before, you mentioned that there was an interesting connection between all of this and insurance. So help our help our audience understand that. Like what's what's the change there? Yeah, absolutely, Kyle. So I I came to this this topic because I've been helping, large enterprises who are using drones make procurement decisions. That's really the position that they're in right now. If you've seen US regulations around supplier management and foreign supplies, there are a lot of new rules to step around. I won't go in depth on those today because they're they're quite complex. But the idea is that your supply chain really matters, especially if you're going to be Mm-hmm, mm-hmm. spending taxpayer dollars. So for example, federal funding, you can't buy your drone from certain countries or your drone equipment from certain countries. And so that's really got kind of the spotlight in the supplier management and procurement activities. At these organizations who frankly are spending tens of millions of dollars on this type of equipment right now. And I think that's only going to continue to increase as these rules, these rules come out. And so as they're making these massive purchasing decisions, one of the areas that I'm that I am focusing on is how they're going to ensure their operations and their equipment. Hm. specifically from the liability perspective. so today the way that underwriters look at insuring Part 107 operations It's a lot like traditional aviation in that it has to do with your pilot certificate. Do you have your pilot Right. certificate? Have you had it revoked? Have you gotten into trouble flying? do you have experience flying the aircraft that we're going to ensure? It's not asking questions about how many incidents has that aircraft had and how autonomous really is that aircraft. But those are going to be the questions we need to answer under Part 108. And that pilot license question, because of the simplified user interaction requirement, it will be much less relevant in how we ensure. Interesting. Yeah. Because if there are failures in these, it's not going to be an individual with a license that's held accountable, it's going to be the organization. Right, right. That's a huge change. my gosh, wow, right. So it's not about ensuring pilots anymore. Right, how do you even begin to sort of gain enough information to be able to do underwriting? Like it it seems like there'd be a lot of like statistical analysis you'd want to do and it would be really helpful to have thousands of hours of flight time and these systems are new. It's it. Like how how's this gonna work? Exactly, exactly, Kyle. So I would say there doesn't really exist a good precedent for this yet. And so one of the goals at Altimetis and but I've seen some other new market entrants look after is how do we help underwriters really understand the risk without having to do it in retrospect? So today, for example, when shopped around for my own drone insurance and then I've asked them, like, you know, you cover a hundred different airframes. How do I know Yeah. if I select between one or the other? How Going to change my premium costs, for example, or my coverage. and right now the answer is well, it's all dependent on the cost of the system, which is a really interesting question because number one, okay, yeah, that makes sense. If I'm gonna file a claim for a hundred thousand dollar product, you I should have that much coverage. but the organizations, the OEMs who are developing these are trying to figure out how to price their systems right now. right. Right. So there's sort of a chicken and egg problem going on. Exactly, exactly. We we get we get a bit of a chicken and egg problem. and then yeah, what that doesn't take into consideration and that I've asked underwriters that do this today for part one seven is well what happens if that's an aircraft that is fresh off the production line and it doesn't have any service history? Are you gonna charge a little more for that? Because now your customer is probably the test fed for for that aircraft and Right. Right. they're gonna find out how many times it crashes. And I have gotten responses of, well, you know, once we start receiving claims for a certain airframe, then we will raise rates on that airframe. Until we, you know, Mm. find out that they've done, you know, we work with the OEM, I guess, to find out if they've been able to reduce the amount of incidences or the frequency of incidences or or even the severity of their incidents. but that's really that's got some lead time in it, the lag there. my my pitch here really is I would like to see some leading indicators for what the insurance cost is going to be for UAS, especially under Part 108, that are based on their system safety assessment, which is exactly written to describe the likelihood of incidents. Right. Okay. So in a way, I wonder like when you think about like what is it, NHTSA, the the national highway safety folks in the States, I I I don't understand this world as well as I should, but I think that they're sort of the ones doing the crash test dummy situation, you know, so that they're literally the ones testing the cars. So and and that obviously that the insurance companies I think are funding all of this so that they can understand better like how how it all works, when it does go wrong. so there could be a role for insurance to be more kind of active. I guess you would need sort of a technical nongovernmental group that or government group really that sits in between them that that ha that brings the know how. But insurance s could have more of a role, I guess, is is kind of what I'm hearing. And and maybe they're not doing much of it yet. And and I like tying it back to those that are making the procurement decisions because they are, you know, requesting larger and larger budgets each year for procuring this equipment or paying for services for someone to do this work. And so yeah, right now that it's kind of like flying blind. Yeah, yeah, for sure. So far it seems like the the risk is being measured in terms of replacement value, right? So it's it's it's about ensuring the vehicle. Is there not a liability question too? Like or or maybe that's different? There there is absolutely a liability question. yeah, yeah, exactly. what I what I would like to see is that liability calculation and how that is determined by underwriters. And I have not been able to get a lot of transparency into that. I would imagine, Got it. for example, yeah, if you're flying your own substation, then you probably need a policy that's going to cover your liability for busting your substation if your aircraft, you know, if there's a gust of wind and your aircraft takes down a substation. Right. Right. so that that's one example, but those are examples of, you know, kind of like the shielded example. I gave where we already know what we're flying over. And so there's so it's it's a little easier to quantify. That's not necessarily going to be true for all drone operations. I think about you know delivery operations in urban environments. they, you know, they might have to, for example, in insurance, they might be required to only fly over certain types of areas, and the second you go fly over a school, Then what happens? Yeah. and you're you're operating outside of the scope of what the insurance covers, and now we're not gonna cover it. That's one way to go about it. the other one I can think of is emergency use cases. so if you've got, you know, a drone operation that is bringing, you know, AEDs, Narcan, EpiPens to, Sure, yeah. Yep. you know, emergencies where they're needed, is you know, how how do you ensure that? And also like it's you know, God. God. if it's responding to an emergency, I would hope it's not gonna make the emergency worse. Right, right, right, right, right, right, for sure. Okay. Well and like the software developer in me kinda wants to listeners may know that my my day job is actually software development and that's that's most of my background. Kind of wants to build like a digital twin system of the operating system, right? Of the system which is controlling the fleet. UTMs, we call this, is that the right phrase? No. You know, I I I would think of that as command and control, Kyle. so Got it. Okay. yeah, yeah, the the centralized system that actually commands the aircraft. UTM or uncrewed traffic management or universal traffic management, depending on who you ask, it is really it it primarily has a strategic deconfliction focus right now. so it's more about planning. right, right, right. That's the one that you run in between the systems. Right. Okay. Yep. Yep. Right, exactly. Yep. Bobby talked a little bit about this in his man mano talk and using I've mixed up my acronyms. Yep. UTM and no worries. Okay. So if I'm if I'm mana, I participate in the UTM, but I have my own system, command and control system, I guess. and that's what participates in the UTM. Okay, fine. so yeah, to me, that system itself, command and control, would be something that definitely I would want that system under test. I would want to know what it does. I would want evals wrapped around it and you know, to be sort of hill climbing it with, you know, new LLM techniques towards you know, better and better capabilities to deal with like wind to deal with like a sudden obstruction, to deal with a p imminent collision and so on. So yeah, there's a lot of interesting sort of digital aspect there, I think. that's actually exactly the type of example I'm gonna be leading when I share the a system safety assessment approach with ASTM F-38 industry leaders next week. we're gonna talk through what a system safety assessment would look like for a top-level event of loss of separation. so loss of separation as in you've breached a well-clear volume of another aircraft. what are the cause what are the potential causes of that? And I do split it into, you know, strategic and where the failure points are in the strategic mitigations, the mostly things like route planning. And then also on the tactical. So if you have onboard detect and avoid capabilities or if you have some type of communication capability between your fleet such that they avoid each other that way, there's all sorts of failure points that could cause those to fail. And then the one that's even a little scarier is the common cause one. So if your strategic deconfliction of planning your route is based on a data source that is same the same as the data source that your tactical de-confliction is using for detect Mm. and avoid, then if you have a failure. In both, you can't really mitigate failures in the other one with failures Mm. Mm. Mm. on one. So this is an area that you know the industry is going to have to face around like strategic deconfliction is great if it works all the time, but the second you have a non-cooperative participant in the airspace, Mm. Yeah. as in someone who is not broadcasting ADSB or doesn't have remote ID out on, you know, you're not going to be able to see them. And so you are really forced to use, you know, sensors to be able to see what else is in the air. Interesting. Okay. Cool. Wow. Okay. So another another set of acronyms, F thirty eight and ASTM. Can you unwind those for us? Absolutely, absolutely. So ASTM is the industry standards body that is really tackling Part 108 right now. The other one that is most commonly used in the US is RTCA. the cool thing about what the F38 group in ASTM is doing, which is the UAS standards group body. So there's F-38 is UAS standards, F-37 is light sport aircraft. We work really closely together since we're developing industry standards together. But F-38 is all things uncrewed. And in particular, we're writing a specific standard that we're calling the Meta standard. And is a and the reason it is called the Meta Standard is because we want a standard that we can comply with for part one. oh eight on Mm-hmm. day one when the rule comes out. And there is so much in the proposed rulemaking to do from a standards development perspective that we want to kind of get, you know, as broad of a sweep as we can to make sure that we're covering the requirements. Of the regulation while making sure that we have industry feedback on it, because the whole point of working with an organization like ASTM and using those standards is that you can use a means of compliance with the FAA that has already been vetted by other by industry. So other folks have Okay. Yep. voted on it, they've given their input, you've gone through ballots, and something going through ASTM is much more likely to be an accepted means of compliance by the regulator than, you know, companies absolutely are allowed by the law. to come up with their own means of compliance if they want Right. R Right. to do it themselves. It will require a lot more review through the FAA and Right. probably a lot more scrutiny than if I say I'm going to comply with this standard that the industry already agreed on. Got it. So what kinds of companies would be or organizations would be members of of F thirty eight, of of all and that paying attention to all this? Yeah, I mean anyone who's flying today that wants to fly under part 108 should be involved. And a lot of them are. so I'm I'm not familiar with mana participants, but I'm sure Bobby's got some folks in there. the other delivery giants that he named, like Zipline, Google, Amazon, DoorDash, they're absolutely involved in these conversations. Interesting. and then there's a whole, whole boatload of work that's going on the UTM side. So I know ANRA is involved as well because they've got a you large taken. UTM market here in the US. And so yeah, anyone who's developing technology to comply with Part 108 should be involved here. And one of the reasons why it is such a good use of my time and really anyone else who wants to operate under Part 108 to be involved in these standards bodies. This part 108 is only a proposed rule, right? It's not finalized. And so it's very common today when I'm talking to current drone operators or current folks who make products for drone operators, for them to say, Well, I'm just gonna wait until the rule's out and then I'll decide how I'm gonna, you know, update my technology. The the way that the rule will probably change is not likely to impact the standards level. you know, they're not they're like unlikely to change the rule about no probable failure should can result in a hazard. And the amount of standards content related to that one little part of the rule is massive and unlikely to change. Mm. the other the other examples I would give are rule changes around the systems and equipment that are used for Part 108 and the reliability of those systems, that's unlikely to become less stringent at the rule Mm. level. Therefore, the standards that we're writing today will will more than likely still apply, regardless of how the final rule comes out. Okay, so in so it sounds like you're saying that the the process so far, you've got a lot of different operators at the table, big named operators that people have heard of. help me understand that relationship and what why one would impact the other and what they are a little more? Absolutely, Kyle. Absolutely. So I there is a part of the, you know, industry that looks at Part 108 and says all it is is proposed. It's not a final rule. There were thousands of comments submitted to the FAA after the notice for proposed rulemaking for 108 came out. And some of those comments might have said, you know, to the effect of, I actually think it's okay for the aircraft to fall out of the sky without a parachute or a mitigation. Right. Those comments are unlikely to be found persuasive and to make their way Into the rule changes. But Got it. Right. there are a host of you know comments that probably will drive rule changes, especially around electronic conspicuity and right of way between crewed and uncrewed aircraft. I don't want to dive too deep into that because it's a kind of a can of worms. But so there are probably going to be some changes. That said, those changes are very unlikely to impact the technical requirements of the products and the systems. And that technology roadmap that I'm writing today based on the NPRM, I see very little opportunity to change it once the final rule comes out. But what I do see is that once the final rule comes out, if you can start operating under that rule soon, you only have so much time then to update your technology to be able to operate under that new rule. And the testing Mm, mm-hmm. to prove that your system is safe, that's what takes time. So I can make a fancy user interface for a GCS pretty quickly, a ground control station for operating drones. I can make that really quickly. The amount of time that it takes me to test and prove that it is safe once integrated with hardware and once I'm using the scaled network designs, that's what takes time and resources. And that's what I'm trying to get started on now so that when Once the rule comes out, the technology and evidence that it's safe is ready. Got it. Nice. You another acronym check there. one which you walked us through. Thank you. But N P R notice for proposed rulemaking. this is the method of rulemaking that the FA uses. Got it, got it, got it, got it. Okay, got it. Okay, so this is the whole the the whole process. Nice. This is fantastic. So there's a lot going on in terms of rulemaking and in terms of new regulation coming out. And while it doesn't sound exciting, it enables really exciting things because the current regulations don't. But yeah, it sounds like command and control has got a lot of changes coming to it is is one of the the net impacts of all of this. Like we've gone from a piloted system to a not at all piloted system, right? So like and if I've got a fleet already out there, it seems like they might Be doing all sorts of different things. Like help help me understand what it's going to look like to migrate. are people gonna end up with mixed fleets? Like, how is this how's this gonna work? Yeah, absolutely, Kyle. So there's there's one problem here that I am really excited about solving, and that is the use of heterogeneous fleets. Okay. so when I when I say heterogeneous fleet, what I'm thinking of are airframes in particular that are different. Right. Right. Right. So not just operating under different rules, so I'm I'm thinking like multicopter. but like literally different architectures. Right. Okay. Yep. Exactly, exactly. Because these are these are robots with jobs. And so they Yeah. have different skills to do their jobs. And that can come in the form of performance differences, as in like aircraft that can fly at different altitudes based on their propulsion systems, versus you know, the kind of basic like size weight power, endurance, you know, how long they can be out there, how fast they can get to the emergency. and that all drives other other physics related disparities like fixed wing versus Multicopter versus electric VTOL. These types of airborne robots can work together to accomplish jobs that one type of airframe couldn't accomplish as well by itself, is more costly right. to accomplish by itself. And so even if you keep adding, you know, the same exact airframe over and over, you might not actually be getting more value in your use case as opposed to adding different types of airframes. Right. So wow. So okay, so when I think about like you mentioned ground control stations earlier, so probably there's like kinds of ground control stations that generally deal with fixed wing and another one that probably generally deals with something that shaped like a quadcopter. and and so you're gonna be able to have to run them like in the same software. But is that happening today? Is anybody doing that today? There are some instances of this happening today, but it's rare. And Yeah. this just has to do with the where the industry is in its maturity to on the commercial side. So I'm going to speak commercial very specifically because some of these concepts are really well proven in defense. But that's where safety requirements don't apply quite quite the way that they Okay. huh. Yep. do in commercial. So on the commercial side, and a UAS OEM who's been around for the last, you know, five to ten years, they've spent a lot of their effort, likely on the air. Dynamics of their aircraft because this is a really new space. And so while there are some really great reference designs, there's also brand new ones coming out. If you've seen the DARPA lifts challenge winners, you know, they're coming out Yeah. Crazy looking things. Yep. with some really interesting airframes and propulsion systems. Crazy looking things. And so, really, what they've been focusing on are those kind of my aircraft, you know, it needs to meet these performance requirements, and therefore I need to design the aerodynamics in this way and the propulsion in this way, and the payload capacity. In this way, that's really what they've been focusing on. And in order to not just develop but test that, usually what they use is a test ground control station. Okay. So that would be like those open source ones that you can just find available online because your flight controller is likely an open source flight controller like R2Pilot or PX4. And so they've been using what I would call test software. That test software is very engineer focused, right? It's like I'm trying to test this aircraft so that I can figure Mm. Yeah. out if I'm getting the aerodynamic performance that I was expecting. That's a very different use for ground control station software than operating Right. to go and inspect a utility line or to respond to an emergency in a police department. And so what I'm talking about there really starts with yeah, like the user interaction. So what the actual graphical user interface looks like for operating. Right. It's probably not gonna look like multi-UAS operation, like one-to-many type operation. And it's also probably not going to look like a mixed fleet because that's not the point at which you test different airframes through the GCS. You know, they kind of use their own their own GCSs to be tested. Mm-hmm. Getting those in getting those into an operational ground control station is going to be the next challenge that we face. So from you know, the police officer who's using this mixed fleet, they're not going to be switching between the test platforms of each of their hardware pieces. They want No. No. to be using the operational software. Right. Right. So okay, so we might have bought software from one OEM for our quadcopter and another piece of operational software for our conventional I I don't know, maybe the conventional is monitoring wildfire smoke and the quadcopter is is trying to pinpoint people inside of the fire zone or something. And these softwares don't necessarily work together. They weren't they they were purchased separately, right? So on some level you kind of need to start building systems for the operators themselves, which are somewhat distinct from the fleets that they're actually flying. So it's almost like a change of like who the customer is or but maybe I'm overreacting or underreacting to that. Yeah. I I think it's a huge change to who the customer is and and their concept of operations and how they work. Because so we're talking about, you know, a pretty challenging problem of having heterogeneous sleep from commanded from the same ground control station. But even today, I know some operators who, you know, they have their Part 107 waiver to do one to four. So they're applying four aircraft. But that aircraft that they chose is one of the less expensive ones. And it does not have a one-to-mini ground control station. And so that is the type of operator that's sitting here with four laptops. I'm no no Wow not kidding, Kyle. And that's how they're monitoring four, because not one of those GCSs is built to to be able to command more than one aircraft at a time. my god. And you can see how that would turn into a human factors nightmare. And so in some of those waivers, they not only have to say, yeah, I'm gonna have four computers in front of me, but if one of my aircraft, you know, has an alert on it or says that I need to go inspect something more closely, I have to come and do land, land, land, observe. So I have to go land yeah. all my other aircraft before I go and observe with the other one. One example my gosh. of the way these waivers are written today. But yeah, that's that's an example of someone who I know wants to go one to eight next. I don't think they want to hire any more pilots. They want to keep with No. one pilot, but I don't have a desk big enough for my eight laptops. No, I was just thinking, I could maybe imagine four laptops here, but there's no way like maybe the other four over here or something like no, this is not happening. and even virtual machines, that's a very large monitor. It's just it's just not happening. Okay. Wow. Okay, so so really the state of the art in terms of these like software systems, I'm sure they're very well tested and I'm sure they're very stable, but they're not necessarily purpose built for what we're doing with them on some level, maybe. Yep, yep, that that's exactly right, Kyle. when I think about, you know, robots that do jobs, you know, that's the other part of the coordination aspect that I don't want you know, a a typical end user to have to worry about. You know, if we're using the drones as first responders example, you know, they know that they need eyes in a certain area where there's an emergency. They shouldn't have to think about things like how far away the aircraft are stationed, because they're probably in docks, what altitude they're going to fly at, because if it is hetero heterogeneous fleet, it's going to be different altitudes. Aircraft to aircraft, what the performance characteristics are of each of those aircraft. So if one can get there faster, but one is getting there slower simply because it takes longer for its dock to open and for its autopilot to spin up, gosh, yeah. those are all things that influence how quickly you can respond to an emergency, not things that we should ever ask the operator to keep in their head. This No. is a ground, this is requires a ground control station that is performance aware of your robotic fleet. Right. Well, when I think about an operator here, I mean they're probably an expert in the thing that they are doing with the drone. They but we don't want them to also have to have a PhD in electronics engineering and everything else so that they can understand like all of these complexities. Okay, right. So the level of abstraction needs to come up. Okay, quite a bit. Did you mention like I wrote down swarms question mark? Like did you mention like operating multiple robots to do a job? Like should I imagine like passing things between them or like or or hold on, or am I d going too sci-fi there? Like when we're talking about multiple aircraft that could do something together that they couldn't have done alone, how did you mean that? I mean, I I so actually I love that example of passing things between each other. I don't really see like aircraft fuelers between drones these days. But what I can see, for example, in the delivery space, there's already a kind of change in the concept of operations in the delivery space, going from launching and recovering out of my pod, and other that I'm always in the air, to launching from your pod, landing at the restaurant, hanging out on the roof of the restaurant, waiting for so now you're actually not flying anymore. Is that the end of the mission? Right. right, right, right, Is that the beginning of the mission? right. I don't know. So then it's waiting for food. That example of how drones could work together could be I've waited too long for my food here. I want to s my battery's gonna die. Send out the backup aircraft to get the food and I'm gonna go back and charge up. That's that's one way that they could work together. the other example though that I think of for simultaneous operations is aircraft that have different jobs. so for example, in the first responder use case, if you know you have an aircraft with a highly performant payload, but then probably higher swap, it's probably going have to fly at higher altitude anyways, but it can get really good pictures because it's got the really nice heavy imager on it. If that air if that aircraft is spending all of its swap budget on carrying that imager, it has no more swap budget for detect and avoid. So it's not going to have a radar on it. So all it needs right. to do is call its buddy that does have a radar, an upward-facing radar on it to follow to fly below it and monitor its wow. airspace for it. wow. These are ways that I could see drones working together, but they have to have not just that performance awareness, but also the regulatory context of I need a I need to detect an avoidance system that is performant in this operational space. Yeah. Okay, so when I start to think about how that works, right? Like in in aviation today, we we talked about things like ADSB out and of course like mode C and mode S can be detected by ground stations, which gets fed into ADSB, but that's not happening in drones. Like the transponders are too heavy. So instead we have remote ID. And as I understand it, this is basically Bluetooth and Wi Fi. So the distances are less, right? And I guess that's because you have lower energy radios. just something like LoraWan? get involved or or or is it like no, we've got like Bluetooth Wi Fi and then we've got cellular, or are there middle ground players, or is that kind of the field? You know. one one thing that I do talk to Altimatous clients about that are trying to prepare for part 108 is part 89, which is the remote ID rules for UAS. And there will need to be updates to those rules. Mm. I the the one the one that I can think of that's really simple and obvious is the current kind of ICD for what you broadcast over remote ID. It includes the operators lat long. That's not going to be as interesting when you have an operator, Hm. right. Yeah. you know, a couple states over, you know, that's sitting in a what looks like a call center, you know, so you know something like an address on a floor level might be a little more interesting. So they're gonna have to update that rule in that regard. But what you're describing as far as how UAS see each other with what I would what I would call just electronic conspicuity, the the technology has far outpaced the limitations that the current Part 89 rules have put on it. Okay. so I see the future not just in having more performant radios than you know the Wi-Fi and Bluetooth solutions that we've come up with, but also having things like network capabilities as well as even like terrestrial and satellite networks, being able to provide that electronic conspicuity based on, you know, RF readings. Okay. So sort of networks of ground stations which are RF radio Okay, got it. And conspicuity, that's not an acronym and yet I almost feel like okay, I so that is the the property of being conspicuous? Is that where we're going? Got it. Exactly, exactly, yes. So you're not Okay. you're not stealth in the national airspace and no one should be. No, right, right, right. For safety. Okay. okay, so wait a minute. So right now today, like they're supposed to carry small Wi-Fi or Bluetooth beacons which can just sort of say I'm here, I'm here, I'm here. to your point, like you could imagine more like networks of ground stations then, I guess, which are being using radio signals to see, you know, that there are multiple aircraft in the area? Or or am I maybe I jumped too far with something you said? No, you no, you're you're absolutely on the right track there, Kyle. So I have Yeah. seen this worked in a so I see it a lot in the what would be called the counter UAS space. So in the counter UAS space, ground based systems that can determine where thing where things are in the air. and those are often a mix of radar, vision systems, acoustic systems, and then having the remote ID. Yeah. Yeah. capabilities. So you know between those mostly can see what's in their airspace. Those don't have great range usually because if you want really great range, you're gonna have a really expensive radar. And so those, you know, you'd have to kind of put those all over the place. I do think that there's a market for that. Where I'm really curious about the technology is, you know, my background is improving that a a network that was built for cell phones on the ground. could also be used for drones in the air. Similarly, I think that same network that is used for cell phones on the ground could be used for electronic conspicuity in the air. The FAA Department of Transportation has spent resources in the past couple of years investigating this capability with cellular network providers as well as with satellite providers. And that's more about, you know, things like triangulation. I can figure out Right. where that phone is on the ground using cell networks. Why couldn't I do the same thing with something at low altitude? right. Right, right, right, of course. Right. Okay. Okay. So on some level, 5G could give you some basic capabilities of just data transfer and being able to to make to say things. But to your point, like it also could give you can trilateralization. What's the there's a right word for this one, but triangulation, being able to try to figure out like where this thing is based on how many signals it's talking to and how far away it is. Okay, right. So not just sort of communication, but literal sort of detection and Placement in space. Got it. Okay. That definitely is is there is this like we have to wait for cell phone standards? I I just said it and now it's dropping out of my brain. Not LTE, but the something thank you. five G. Yes. Yes. Okay. Is is 5G enough, or do we need to wait for like 6G for all this? Or am I kind of overindexing on cell phone technologies and it's it's actually something else? Like how does that part work? So I'm a big true crime fan, Kyle. So I watch, you know, all the true crime documentaries on Netflix. I it is clear, you know, when you need to solve crime that you're gonna look at cellular records and you can determine where someone was located. it is often the exact same modem, the the small like modem that is used in an aircraft, similar to what would be on a phone. so all that to say, I don't think similar to how when you know Young Bri software engineer was trying to figure figure out if telemestrial networks could be used for command and control. And we find out, yeah, of course they can. I think it's a similar story for electronic conspicuity. We already know because police departments Yeah, yeah. have used it to find criminals, that they can figure out where someone was based on their cell records. Hundred percent. All the aircraft that are flying over BVLOS are gonna have to use cellular or SAT. And that's why working with cellular network providers and satellite network providers with the government or with whatever entity is going to have those come about, I think that's really the path there. And the technology, I don't think, is the barrier. I follow you. I thought you were trying to say, like, well, you know, if as long as we add a five G modem to all these aircraft, that will be fine. You're saying, no, no, they're going to have one. And so thereby that okay, right. So that now it's dawning on me what you're getting across. Okay, great. Okay, wow. So we yeah, that that obvious that seems very obvious on on a lot of levels then. So yeah, okay, that's how that's gonna work. Cool. Cool. hmm. There's a lot, there's a lot of precedent here too, which I'm sure you'll you'll know more about even than I do, in electric electric vehicles. Mm. So the technologies that are used right now to for V2V communication, it's very similar to the requirements for like airborne vehicle to vehicle type communication. And Yeah. I've found that even some of the hardware solutions that are used in ground vehicles Mm. for autonomous vehicles and electric vehicles, Yeah. it can have a lot of use in the low. Yeah. Constitute economy, especially what they do around, you know, around safety and assurance. So that type of equipment is already developed as though, you know, it's highly critical and therefore they're not, you know, just vibe coding or open sourcing everything. but then the other side is security, is that like, you know, I'm I'm sure you can find some interesting, well, I'll share with you some interesting stories that I've seen recently of Smart vehicles being hacked across the world. Mm-hmm. Yep. And the efforts that are being made to make that less available, I think, will translate really well to the low-altitude economy for the use of things Hm. like hardware security modules, trusted platform modules. Those are the types of things that don't even show up in drones today. right. Right. But that's really what you would need in order to secure your system. Right. Okay. So when I think about like TPM trusted platform modules, this is sort of cryptographic capabilities on motherboards that are able to sort of say, like, you know, this is who I am and and and thereby kind of validate which software is running on them as well and the other way around. So it makes it a little bit harder to take them over at a at a basic level. you can still sort of attack the higher level, but it's it's higher to get harder to get like down to the hardware level in terms of an attack. right, so right so right, and none of this stuff there's so much low hanging fruit. There's so much good stuff that we can apply. Okay. And to your point about the hardware side of things too, like what I think part of why I was fixating on 5G earlier is that it's it's my understanding that it's a lot lower latency and it's a lot lower energy somehow. maybe that means the masks have to be closer together. Probably does. but but yeah, that the capability to do collect, you know, detect and avoid in automobiles, an automotive on on some levels predicated on the fact that it's so low latency that you can go fast. Whereas you could get like high download speeds with four G, but the latency wasn't very good. So in five G, yeah, it's like much higher download speeds, but the latency's starting to get really, really useful for stuff like this. So I think that's that's part of what's so there's a lot of exciting stuff coming in the future. Okay. when we think about the defense side of things too, right? Like when I'm thinking about talking to people in Europe, working with an an operator or sorry, working with a company in the Netherlands called Blue Mark, that makes drone radios and things like that. Like I I get the sense that some of what they're working on is helping airports secure themselves against sort of drone harassment, right? And th this is bordering on warfare at times. You know, if if you're able to shut down a major airport by just harassing it with drones, like you've inflicted economic damage remotely. and so it seems like and even in North America, I think where we might I think I've yeah, something about like waterborne drones on Lake one of the Great Lakes. and I'm thinking that's probably you could detect that with AIS and I'm nerding out too much, so I'll probably edit this out. But it seems like the the sort of defense and side of this is do you think that's gonna start to impact us sort of onshore in North America, like where we don't have Yeah, I there's there's literally war has come to Europe, right? So I can totally see that technology being involved at every level. But do you think we're gonna see that like where we need to protect our own airports here? Help me help our listeners think through what might be coming soon there. yeah, absolutely, Kyle. You know, this is a huge this is a huge space, at least in the United States and where funding is being spent at state and local levels as well as certainly the federal level is on counter UAS, Yeah. is on being able to equip especially, you know, popular events. I'm thinking, Mm. you know, like FIFA and World Cup, Olympics, Yep. Twenty twenty eight Olympics, those types of events, being able yep. to yeah, being able to make sure that we can not only detect Protect and classify what's in the air, but then also to be able to mitigate if we need to. Huge amount of resources being put into this in the US right now. So that's kind of the you know, those sporting event examples are kind of the bigger picture. Smaller picture-wise, you know, prisons are buying these types of systems, right. churches are buying these types of systems. Anyone who wants to protect themselves against drones, the first step is Right. just to know that the drone is there. Right. And so that's these types of systems are incredibly they're becoming more popular, they're getting a lot of resources poured into them, and trying to find ones that are you know low cost enough that we can actually implement them in the commercial market. interesting. The the prisons use case that I'd heard was you don't want drones flying overhead and dropping contraband into the yard. those kind of things. So I can churches are s is somewhat more surprising, but but yes, I any organization that wants to have like perimeter of security, I I get it. Yeah. That's that's really what it is, is it's it's wild. I've been I've recently been reading some of the proposals for next year's exponential conference in Miami, kind of helping out the organization with triaging those proposals. And every time I hear one about security, I have to do a double take to understand, are we considering the cybersecurity of the platform or are we using the drone for physical security? Because Yeah. both of those things are really popular right now. using drones for physical security, it's a really, really valuable use case. Got it. Okay, so w how much of software dependability is a is a part of all of this? Because we we talk about all these wonderful technologies and how great they might be, but you know, I had to reboot my Windows laptop and and and or my Mac laptop yeah, more times than I care to admit this month. and I'm sure most people in the audience can can relate to that. But you know, you and I, it's it's often our job to make those systems more reliable. So like maybe that needs to be In the rules? Like help us think about that. Like what do you what would you suggest if you had the well, it sounds like you do have the ear of the regulator. Like what would you suggest? Yeah, absolutely, Kyle. So earl early in my career, the the thinking was that we'd have to put we'd have to apply traditional aviation practices to the UAS space. So for software Right. Right. dependability, that looks like DO178 from RTCA. Right. Right. this is the process for proving that essentially development assurance. so showing that the product does what you want it to do, it doesn't do things that you don't want it to do, and it doesn't have anything extra in there that wasn't specified. that's you know things like writing requirements and test cases, getting traceability, testing, you know, coverage of your code. Okay. So this is like a SOC two or and that's really PCI kind of audit being applied to it. I think I think you've heard stories about people being like called to explain lines of code in the software to to prove that it was all well understood. So I I can only imagine they've got their own sort of process here. Okay. So that's DO one Yes. seventy eight, right? Current aviation standards. Okay. Okay. Right. Precisely. So yeah, I'm glad that you actually mentioned SOC2 because this is where it gets really interesting. DO178, you know, was written for embedded software. It was written for software that's going to go on the aircraft and that's going to be isolated. So, you know, we're talking like air gapped solutions that we don't have to worry about what's going on in the cloud. that's not going to be the future for UAS. It's a totally different type of software that's being written, and the safety criticality and where it lives is not necessarily all going to be embedded code. No. and as a software developer, then you know what that means is that we're not just looking at you know the hardware that the code is running on, we're looking at the languages themselves and what they what they have for safety Yeah, yeah. Everything. Yep. Yep. and security. Well, and plus with the distributed system. So you're you I mean you can test your unit and you should, and you can test its integration capability inside of its application and you should, but th it's it's still like dealing with a network of things that they all have to be tested and they have to be tested from an integration standpoint. Yeah, okay. So there's there's a lot of change coming at them then. If they've been used to focusing on embedded, that's like the unit, the application. And now we're gonna have to get into a much broader world. The system might be distributed across multiple components now. Yeah. Right. It and it reminds me a little bit about if I think of like an AWS example, it reminds me of FedRAMP requirements, right? Like I'm not gonna Hm. start my program by using my AWS version that you know is more expensive and going to comply with FedRAMP. But if I have clients that are going to that are going to need f FedRAMP compliance, Yeah. Yeah. then I'm gonna, you know, go to this next tier of reliability from AWS. It's kind of similar for UAS in that, you know, where you choose to host this stuff is gonna have to follow these industry standards. for safety Mm. and you know most most cloud developers or folks who are gonna you know develop a solution in the cloud you know they're looking for cloud optimization cost optimization you know things that are not that need to take a backseat to safety and security in a UAS world Yeah, yeah. I I once had to to build a credit card processing system and and we had to take some PCI scope on because of decisions that, you know, w maybe you could have made differently, but but point being we had to figure out like how do you actually do PCI in the cloud, not just sort of sub it out to Stripe or something, but actually do it. And yeah, it's a it turns out to be a lot of work. The idea of handing it to a FedRAMP is a is a very Okay, wow. So there's a lot coming. There's a lot changing right now. Okay, nice. So the software stuff, Kyle, I'd like to talk about it more because if we think about all those different places that your software is running and then all the different you know languages and frameworks that you're using and then having to Mm-hmm. tie them all together to prove something safe, Yeah. this is where the the characteristic of the UAS industry of being one where It's so nascent and small that companies need to work together a lot to achieve what they want to achieve. I think that's gonna be particularly true in software. Yeah. Because if you're going to attest to the safety of the entire system, we can't be black boxing portions of our software without a lot of thought, you know, Yeah. especially as we go about designing it. So when I think about designing, you know, my high in the sky part 108 heterogeneous fleet compatibility. compatible GCS plus certified flight controllers. My trade space needs to extend not just the GCS UI. You know, my my trade space has to go into the cloud services that we're using. It has to go into the embedded code on board the aircraft that is actually Yeah. Yeah. commanding the aircraft. It has to go into any modules on board that are ensuring things like safety and security through things like route conformance monitoring, all the way down to the example that you used about TPMs. my GCS designs, they actually have a concept in them of Is this person who's commanding me allowed to command me? Right, right, right. Okay, wow. And that's really different when you can only command from your hand controller or from your laptop that has the local application running on it. Now it's an application in the cloud, and anyone can read it on the open internet. Mm-hmm. So, how do I know that the person who's in the open internet has been authenticated and also that their credential or their access controls exactly Right. And you sort of gotta pass all of that all the way through. Like I'm almost thinking like an OAuth bearer token style thing where you yes. can say, like, okay, I logged in at this system, like way over here, and then it sent a command here and took the token with it, and there and there and there and there and there and there all the way. And but then also on board on the device, they've gotta be able to authenticate that token very, very quickly and in a high security way, and hopefully in a way that doesn't use much battery, right? Like some of the original encryption algorithms, DES and triple des, for instance, The benefit of triple deads was that it was that it took three times longer, right? And so that way it made it harder to do the the computation, which meant it slowed down the attacker. But that means it's chewing through more battery, right? So like on so yeah, balancing all of this is going to get really interesting. And that kind of brings in the quantum space in terms of like quantum proof encryption capabilities suddenly become needed, right? Like, I mean, if you can attack a drone with a quantum computer and then thereby sort out its encryption much more quickly, God knows what you've just taken over. It it just gonna depend on the capabilities of that drone and where it is and how much energy is in the battery. Yeah, there's there's there's a lot of okay, I'm not turning I'm not doing a good job of turning this into questions. Like I feel like I'm following you, That's okay. but like did we get where you wanted to go or like what's another prompt I can hand you to get one more thing going? I mean just ask me about challenges in the space. Challenges with implementing anything that we've talked about, I can tell you about it. So yeah, I mean tell us about thank you. It's like host one one here. Thank you very much, Bri. I appreciate you. So Gotcha? so okay, but instead of me just making it up, like what what are some real challenges you've faced in the field? Like tell us about that. Real challenges that I've faced in the field. you know, the reason that the heterogeneous suite command and control problem interests me so much is because I have not seen an elegant solution from it. in fact, it's because I've seen a lot of solutions that are not elegant and have not stood to meet the requirements of the end user. Yeah. and often that's because companies are trying to go it alone. they're struggling like either to partner or to use, you know, companies that have a better subject matter expertise. What they're trying to solve, because a lot of companies that are drone companies today, 10 years ago, either they didn't exist or they were playing in a completely different technology space. So their background Right. Right. is in maybe traditional aviation, which for the reasons that we just talked about, things like cloud Doesn't fit. development doesn't fit, or it can be even the opposite if you like, you know, think about like a Google Amazon DoorDash, Right, right. right? They all started as web-based applications. But not aviation. Yeah. you know, right, but not aviation. And so trying to get into this aviation. Space where you're developing you know embedded code that is also safety critical, it can be a pretty big growing pain for these organizations, and that's just on the software side. If I think about the hardware side, when I've seen companies try to you know, start a new type of airframe. so I'll use the example I think you might have asked me about what my favorite aircraft is. The first aircraft that I ever worked on is the Scan Eagle at In situ, Boeing Incitu. and Okay. the Scan Eagle is a fixed wing rail launch system, so it's not EV tall. And it has a decent amount of ground-based equipment required for launch and recovery. At the time, Sounds like it. Yeah. super novel, but you know, these days with EVTOL like, you know, you can get a much smaller package to be able to launch. And taking, trying to take that fixed wing platform to a closer to EVTOL type set of launch and recovery equipment ended up with a system called Flares, Okay. Flying Launch and Recovery System. It is quite literally a multicopter that picks up the fixed wing aircraft, takes it to altitude, and then drops it so that the fixed wing can fly off. wow. Huh. Sort of no enable And it and if takeoff. Okay. right to enable takeoff. And then it does something similar on recovery where the multicopter actually raises the the rope, the cord that the aircraft is caught on, and the Scan Eagle flies into it and hooks on its hooks on the end of its wing and gets caught kind of like it would on the on a s what's a sky hook, usually a crane holding that. But if you look at how this happened in an engineering department, that you were asked to make your aircraft launch and recover, you know, front like by itself. And instead of adding equipment to the scan eagle fixed-wing aircraft, you built a second aircraft. We ended up with Right. Right. Holy cow. two aircraft. This is, I think, what happens when you try to do a different type of airframe with an organization that is used to building one type of airframe. Right. You're going to try to take as much as you can from your legacy aircraft to save time and money, but Uh-huh. often what you're taking is technical debt. Yeah. Yeah. my gosh. That now has to be resolved for a different use case. and so this is the challenge that I see, you know, companies that have proven out, you know, that they have an airframe that operates really well for multicopter use cases. If they try to get into fixed swing, they're gonna run into something similar and then similar Right. vice versa. And so as the end user, when I'm thinking, you know, I have these use cases that you know really fit multiple types of airframes, I might have to buy my airframes from different vendors. Yeah, yeah, yeah, yeah. And now you've got integration challenges and everything else. Okay. No, I have an integration problem. So Bree's talking about the concept of technical debt, and that's not an acronym, but I'll I'll fill it in. so this is a software term where we talk about how sometimes you need to go fast and that means you cut a certain corner. It might mean not a safety corner, right? And not a critical corner, but you might like release it without all the features. and this allows you to to go out faster. and this allows you to get to market faster. And we call this debt. It's like borrowing. It's like borrowing to to pay for your house. And you could wait twenty five years and and buy it when you have all the money, but how about we borrow instead? And the idea is you have to pay that back, right? Or else you just end up swamped with debt payments and you can't move. You can't do anything anymore. And it's a good analogy for for software development and technology development, because if you just keep cutting all those corners, like you can't innovate anymore. You're just surrounded by your debt payments and not able to do anything else. Okay. So to your point, like if I'm If I've been focused on just quadcopters for the for for the longest time and I have certain assumptions about how the way the world works, I'm gonna have certain capabilities and systems built up around those as well. And if I do move into a different kind of architecture, I'm probably gonna try to drag my old stuff with me, even when I shouldn't. And that's gonna make things worse. Interesting. Bri, I'm mindful of time. I've you've been very generous, questions I like to ask everybody, what do you see the future for electric aviation to be? The future for electric aviation, you know, the reason that I'm most interested in UAS is because that's where the regulations are moving the fastest right now. And so electric aviation in the low, slow, small or UAS low altitude economy, I see it really expanding. And the future that I see is yeah, drones in low altitude over urban areas kind of constantly and then kind of seeping out into suburban and rural areas as kind of a normal thing that. That you see. future-wise, I see, you know, at first we're gonna have problems with noise and safety. Those are gonna be the biggest public complaints, Yeah. is gonna be that thing landed where it wasn't supposed to, or it's loud over my house. and Mm-hmm. the technology will evolve. We we wrote a noise standard in ASTM. So meeting the noise standard is like, you know, that that'll be the way to I guess alleviate those concerns from the public. Yeah. Yeah. I like that. But yeah, in innovating on the safety side is really where I see, and I'm glad you mentioned electric aircraft because that that's really where you know safety and the use of battery management systems and the telemetry that you can get from battery management systems and how it can make these systems smarter, and how you know, things like heterogeneous fleets can can operate more efficiently and effectively using that type of telemetry. I I see that really opening up the possibilities to solve customer. use cases in just a more efficient and effective way. Cool. When I first got obsessed with electric aviation, I I went looking and expected to find that, you know, electric trainers would be the biggest use case. It was drones. I I don't know why I didn't expect that, but you know, the number Mm-hmm. of Amazon Prime drones in the FAA registry is just astronomical, right? And ZAG and and everybody else. Zipline, they're they're not always sometimes those are you find those registrations on Cessnas, which is weird. But but that's a whole other story. Okay, what about lessons you've learned? Stuff that you didn't think at first, right? And maybe it wasn't intuitive, but you came to realize, wait, that's how that works. Can you tell a story there? Absolutely. you know, it's gonna be more on the the business and commercial side than on the engineering side. I'm an engineer, so I would love to talk technology all day, but the biggest lessons for me have been about how to build a business in this space as regulations are evolving. if you show up and just say, I want to contribute to the drone economy, but I don't know how. you're gonna end up with too much trade space and it's gonna be really hard Yeah. Mm-hmm. to focus your time. I have worked for and worked with many drone companies that have been acquired or acquired by larger companies and shortly after shut down. I'm sorry, I've seen it happen. And I think really where it comes from is lack of focus. Lack of focus and lack of kind of eye on the funding comes from. That's Yeah. why we're in a really exciting time right now is that there are end users who actually are allocating budget to this. And so if you can kind of narrow in and find out what problems they have and what Right. Right. problems they're going to have soon, I think the success success will be a lot higher if you can do that as opposed to I just want to do cool drone stuff. Right, right, right, right. It's you so okay, so the the lesson there is you've you've got to sort of focus in, find your niche, find like a a customer and problem spot combination that you understand. Yeah. Yep. Instead of trying to solve it all. Nice. I like it. something you're most proud of. I'm most proud of? A little bit of a tangent. I've been a woman my whole life and an engineer my whole adult life and so promoting other women in engineering is something that I'm really proud of. when I have worked corporate I have you know really tried to create opportunities for other women engineers whether that's in technical leadership or people leadership or both. and then yeah as a business owner I really try to build up a diverse team with diverse backgrounds because especially entering such a new space it's really important to have different perspectives. one of the reasons that I think those you know, that some of the failures have happened in this space is because they have really focused on we're gonna use our traditional aviation skills to enter the new era or we're gonna use our SaaS skills to enter the new era. And really what you need is the combination. Yeah, yeah. It's interesting. In in software, I mean, the first, you know, fifteen, twenty years of my career, like it there was not a lot of women at all, right? And then more recently it felt like it was really improving, but still, if I'm honest, it felt like two, three, four out of twenty, you know. and and that's that's that's an improvement compared to where it was. Is aviation better than that? Or is it about the same? Like what's what's your experience there? Yeah, I'm afraid aviation is slightly worse than general software engineering as far as gender diversity goes. that said, you know, there's a lot of organizations, women in aviation type groups that that exist to try to support this. And then, you know, folks like me and the women that work on my team, we try to do a lot of outreach and working especially with, you know, younger generations so that they can see Yeah, yeah. that this is a space that you should consider as a career. Amen. Amen. I I I assume something that definitely works in software, I assume works in aviation, that teams that would that have a mixture of some diversity to it just work better than teams that don't. I don't know what it is, but you just get a group of all dudes and like sometimes this things just go the wrong way, right? And and so yeah, diversity is so important in so many ways. So yeah, I'll just put that in Espe especially in a space that is so ripe for innovation and that needs Yeah. really unusual innovation in innovative type approaches, Yep. Yep. because it's you know it's there's a lot of technical innovation that needs to happen, but there's also a lot of like policy and regulation and socializing type of innovation that we have to do in order to, Yeah. Yeah. you know, put robots in the sky and make that socially acceptable. Yeah, yep, a hundred percent. Okay, lightning round, favorite airport. I am so lucky to have grown up in Portland and PDX just always, if you've never been, I suggest you look at some pictures online because it is the most gorgeous airport. I will never be late to a flight because I show up hours early just to hang out there and enjoy it. Very nice. And I think you mentioned this already, but maybe talk about it a bit more. Favorite aircraft. Favorite aircraft is the Scan Eagle It just has such a cool story going from being something that was built to use off of boats for fishing, to being used in the military, and then having, you know, at the time this very innovative launch and recovery system that's runway independent. That was really what we were looking that they were looking for at the time is we need to be able to operate without a runway. And it this was pre-E VTOL. so yeah, that's my favorite. Amazing. Amazing. Bri, Thank you so much for spending time with us today on the Sky's Your I.O. podcast. It was an absolute pleasure, Kyle. Thanks for having me.