An interview with Reliable Robotics co-founder and CEO Robert Rose about building a plane that flies itself and getting the FAA to certify it: 25,000 pages of regulations, testifying before Congress, why the U.S. has to lead, and how autonomy could bring back service to small airports. Plus a little SpaceX history. And why software just needs to rally.
A podcast exploring the life arcs of smart, creative, driven people who helped Elon Musk and SpaceX revolutionize the space industry. How did they get there? What was it like? What world are they creating now?
[Countdown]
Robert Rose: Software, of course, was delayed as software was at SpaceX, and Elon got the whole team together and went around the room. Elon just kinda is like, sounds like software just needs to rally. It's... Everyone's, like, looking at each other, trying to suppress awkward laughter.
Robert Rose: But it it became kind of the meme, the running joke of the software team. You know, whenever anything was hard, it was like, well, I guess we just need to rally.
[Liftoff]
Jeff Ward: While we were producing this episode of It's Not Rocket Science, my guest Robert Rose took his company Reliable Robotics through a $115 million funding round that pushed its valuation past $1 billion. About a week later, Reliable's autonomous plane flew on instruments from Albuquerque to Shreveport, 750 miles, four hours, flying itself through the National Airspace System. Not bad for a guy who started out writing game engines for PlayStation.
Robert Rose: My name's Robert Rose, and I was part of the software organization at SpaceX. And we were originally under avionics, under you.
Jeff Ward: And how was that? That work out for you?
Robert Rose: It worked out. I'm still here. I'm alive. I survived.
Jeff Ward: Well, if I if I get the sequence correctly, you're also somebody who... You worked for me for a while, but then after I left, you then worked directly for Elon, didn't you?
Robert Rose: Yes. Yes. I was. Yeah. There were...
Robert Rose: There was a series of events that resulted in a series of organizational changes. And I remember one day, a very close friend colleague, Paul McInerney, came to me and said, Elon wants software to report directly to him, and we're nominating you to represent the software work. And I I seriously was just too young and naive at the time, to know what I was getting myself into. And so I kinda... I remember shrugging my shoulders kinda like, yeah.
Robert Rose: So what? I just had no idea how crazy things were going to get, but it was a wonderful learning experience. I learned a ton.
Jeff Ward: Yeah. Learning experience. That's what we call those things.
Robert Rose: Learning experiences. Yes. Life experiences. I don't know. I think sometimes, you know, when I do it again, yeah, I would do it again.
Robert Rose: When I do it again now, I don't know. That's a much tougher question. But, you know, if I had to go back and do things over again, I I I would do it again. It was a it was a great growing experience for me.
Jeff Ward: Well, I think it's kind of amusing that the the team decided who they would sacrifice.
Robert Rose: Yeah. At the time, you know, I'd I'd been in a number of meetings with Elon. Software was frequently recognized as the long pole in the tent, And so oftentimes found myself in stressful situations explaining software status to Elon. And I figured the job would continue much like that. Oh, how naive I was.
Robert Rose: It all worked out in the end.
Jeff Ward: Yeah. I think that... I mean, worked out for me in the end too, but I do think that, the software long pole was part of my demise at SpaceX. You know, the the... Getting the first Dragon software through all of the NASA hurdles proved to be something that, you know, it took how long it was gonna take, and that wasn't the answer that Elon wanted to hear.
Robert Rose: No. I spent a lot of my time managing up, as they say. And, they they talk about in software management, making the invisible more visible, and there was a tremendous amount of energy spent explaining software development, software development process, and the associated schedule, especially tests, and also a lot of calories spent explaining how change elsewhere in the organization impacted software schedule. I remember there was a NASA article that came out. I wish I could find this.
Robert Rose: I went looking for it recently, but couldn't find it. But the headline was something like, the software is the system, as in systems engineering is now really software engineering. And I remember thinking, reading that going, yes.
Jeff Ward: Yes. Yeah. Because the software pulls together all the parts.
Robert Rose: Yeah. Yeah. And so anytime propulsion department wanted to change something about the engine, anytime the structures department wanted to change something, that might flow through the guidance navigation and control team. Ultimately, it would come to the software team to implement the change and test the change and and get it taken to Texas or The Cape to fully integrate and test. And so that that made the software schedule extremely unpredictable because we didn't have great insight into the development processes of the other departments.
Robert Rose: And I originally, in the early days, felt very much like a... It's kind of a victim mentality, I guess. Like, why is this always happening to me? Why is propulsion doing... Why is avionics doing this?
Robert Rose: And it it took me a long time to kinda realize it falls on me to pull this together. I'm gonna have to be like a technical program manager and go ask these other departments. Okay. Where are your risk areas? And what might ultimately drive schedule?
Robert Rose: And that was really hard because I would then have to go to Elon and say, I'm sorry. The software is delayed. And after the emotional reaction calmed down, I could gently explain. This is because this other department has decided to change something, and we can debate the merits of that change, but I'm gonna take on faith that they're doing the right things, and so I'm impacting the software. And after two or three times of people saying, Robert, why are you throwing me under the bus?
Robert Rose: Then I eventually learned, to not only look ahead and reach out, but then to give people a heads up, say, hey, you know, I'm gonna have to explain this to Elon because this will result in a delay in the schedule. And it took a really long time, Jeff. But after maybe 18, 24 months of this, I felt like the machinery started to get into place. And we really started to gel as a team, and that lowered the temperature a little bit. But then, of course, Elon found other ways to raise the temperature back.
Jeff Ward: Yeah. And it's not like he didn't understand software. You know? He came from a software background, and, actually, there's some argument that that's one of the things he understood more. And, you know, I can imagine that getting the successes under your belt of Dragon and Falcon 9 lent some credibility to the schedules that you put out there.
Jeff Ward: I hope that that at least happened.
Robert Rose: Yeah. Having a boss like him that understands software is definitely a double edged sword.
Jeff Ward: Doesn't that cover a boss like you too?
Robert Rose: I was about to say, the team that I'm working with at the moment is experiencing a bit of that, and I I try to laugh about it and recognize the situation for what it is and coach people. You realize when you say this about the software schedule, you know who you're talking to. Right? So maybe go back and think about... Before you open your mouth, think about what you're about to say.
Robert Rose: Or maybe... You know what? I'll give you 48 hours to go back and look at that again.
Jeff Ward: Yeah. Just like you say, it's a two edged sword if your boss knows a little bit of what you're doing, and that was always the Elon method anyway. Is the... He tried to know as much about everything as possible so that if you're in a meeting, he could call into question any number that was put in front of him.
Robert Rose: Yeah. I mean, it seems to be working for SpaceX. I mean, the evidence is in the launch record and all the great successes that they've had.
Jeff Ward: It's certainly true about the the launch record of Falcon 9 and Dragon is pretty spectacular over the years since you and I were there.
Robert Rose: It blows my mind. Absolutely blows my mind. When you're in the thick of it, you know, when you're in the sausage factory and you see all of the problems every day, all of the challenges, both technical and organizational, just getting it working once felt like a miracle. Did we get lucky or was the skill? I don't know.
Robert Rose: Some combination. And after I left, yeah, the launch rate just continued to increase. I left in mid-2014, continued to increase. Now I don't I don't even know how many launches there have been. It just blows my mind.
Robert Rose: It's it's amazing.
Jeff Ward: I often wonder how much DNA there is left in the system from the early phases from the 2010s, you know, whether it's all been wiped or whether there's a lot of legacy software and hardware that's still flying Falcon 9 and Dragon.
Robert Rose: I wonder about that too. But even if it's different, I feel like that's okay. Organizations go through phases, and I imagine the type of organization that is cranking out rocket after rocket like a production factory is gonna behave very differently from an organization that is trying to just launch one, just get it done. Yeah. You know, there was a lot of technical risk, regulatory risk in the early years, and, you know, we just needed to prove that we could build something that makes orbit, and then take something to orbit, and then take two things to orbit.
Jeff Ward: Yeah. Exactly.
Robert Rose: And it's just a... And then reuse the rocket. That's a very different problem from, like, launching whatever they're doing now, 40, 50 rockets per year.
Jeff Ward: Yeah. I'd love to talk to Chris Sloan. He's somebody that's on my shortlist of people I'd like to interview.
Robert Rose: Yeah. It's been a long time.
Jeff Ward: The guy who was gatekeeper to the code repository for many years. Single point reviewer of every line of code.
Robert Rose: Yeah. I I I love Chris. I can say that now. I I did not love him when I first started at SpaceX. I I think I think you heard a bit about this, Jeff.
Robert Rose: I, we had some serious run ins because I'd I'd come from the the game industry, video games, and my idea of software process was very different. And I didn't understand why I couldn't just check-in code and get it done. Come on, man. Let's go.
Jeff Ward: It's true. And if I remember, there was... Ended up being kind of a two phase system where we had a lot of code that was integrated and running, but hadn't been allowed to be checked in. And that was one of the backlogs for Dragon that put me at odds with Elon. Big backlog of stuff that sort of worked, but it needed to go through all the the systems that Chris had involved evolved since Falcon 1.
Jeff Ward: Yeah. You can't... What kind of computer gaming, were you doing before you came to SpaceX?
Robert Rose: So I worked at Sony PlayStation, and Sony is the big company. PlayStation is the division that manages the PlayStation product portfolio. And then inside PlayStation, I worked at a game studio based in Oregon, And our mandate was to publish games that helped sell consoles, which generally meant it had to be fun, number one, but also had to maximally exploit all of the new whiz bang features that were present in the console. And so I spent most of my time as a game engine programmer doing low level code optimization and memory management and graphics rendering, things of that nature. And it was a lot of fun, very intense, which I think actually prepared me very well for SpaceX.
Robert Rose: In the game industry, it was normal for the head of the studio to say, alright, everybody. For the next two months, we're gonna work hundred hours a week. And everyone would go, yeah. And you would just survive on pizza for weeks and weeks at a time. And so going into, like, hardcore rally mode at SpaceX was like,
Jeff Ward: yeah.
Robert Rose: Okay. I know what we're doing.
Jeff Ward: It's funny. The word rally was going through my mind just at that moment too is that that, I think, became the keyword for it. It came... The keyword for, like, software is in the spotlight, and you're gonna rally, which means you're not gonna go home.
Robert Rose: Yeah. Well, there was... Do you know the story? There was a meeting, when software, of course, was delayed as software was at SpaceX, and Elon got the whole team together and went around the room. And I think Alen Kirecci was talking.
Robert Rose: Alen's a great guy. And he was trying to, as matter of factly as possible, just gently explain, you know, we have a lot of work ahead of us. Like, a lot of work, and there's only so many hours in the day. And Elon just kinda is like, sounds like software just needs to rally. It's...
Robert Rose: Everyone's like looking at each other, trying to suppress awkward laughter, but it it became kind of the meme, the running joke of the software team. You know, whenever anything was hard, it was like, well, I guess we just need to rally. Alright.
Jeff Ward: Gotta make that baby in a month, you nine guys. Did you... Like, when you moved to working with Elon, did you have, quintessential Elon moments, or was was life full of them? I I think for me, I can't necessarily name a quintessential Elon moment because every day was one.
Robert Rose: Yeah. There's probably many that I have erased from my memory.
Jeff Ward: Survival instinct.
Robert Rose: Yeah. Actually, one of the quintessential Elon moment... I'll share this. So I'm running a company now, and people see my resume, and they know what I've done previously. And so, oftentimes, when I'm talking with candidates, or new employees in the company, they'll ask me a culture question.
Robert Rose: What's the culture like at at Reliable? And I'll explain to them what we're about. And some candidates, I would say, probably one in three kinda timidly open up the SpaceX door and they go, well, you know, I... I'm asking about culture because, you know, you came from SpaceX and you used to work for Elon. So, you know, I'm just kinda wondering, are there are there things you've learned from SpaceX that you've taken with you to Reliable or not taken with you?
Robert Rose: And I just cut them off. I'm like, okay. I see what you're asking here. Like, look, this is not this is not SpaceX. This is a very different business.
Robert Rose: And and I I say, look, like, we're dealing with very different timelines than SpaceX is. It's not in our interest at all, to burn people out. Let me tell you a story. And there was a time, I think this was around... I think we were in the crunch for Dragon 2.
Robert Rose: So this was the first Dragon to the space station. And I was having one of my regular one on ones with Elon, and one of the things I later learned not to do was open my mouth and share my feelings, and I was telling him, kinda bemoaning, like, we've got... The team's under a lot of stress, like, we're pushing really hard, we're we're rallying, and I said, I'm worried we've got some people on the team that are on the verge of burnout, which was my thought, and people openly would talk to me about this. I I had two or three people, I had to pull aside at one point. I said, dude, do not sleep in your car.
Robert Rose: Like, go home. Go do laundry. Like, this this company is just gonna ask more and more and more of you, but you need to set boundaries for yourself. Like, we can't have you burnout. Of course, I didn't say that to Elon.
Robert Rose: So I just tell Elon, you know, I'm I'm concerned we've got people that are burning out or on the verge of burnout. And Elon stops, and he looks at me just very matter of fact, and he goes, well, Robert, if if we have people that are burning out, we we need to fire them and replace them. And it was just this... I don't... I can't really express the...
Robert Rose: His facial expression. It was just like a very matter of fact logical conclusion. Like, burnout bad.
Jeff Ward: Yeah.
Robert Rose: We should not have people that are burned out in the organization.
Jeff Ward: Right.
Robert Rose: Therefore, you should remove them from the organization. And and I remember breaking out in a in a sweat and getting really nervous. I'm getting nervous right now recalling this, thinking, okay, what do I say in response to this?
Robert Rose: Like, don't blurt out agreement because then they'll expect me to go fire people. And so I don't know. Look, the best thing that came out of my mouth was, well, that would be one way to deal with the situation.
Jeff Ward: And did he let you out of the room with that statement?
Robert Rose: I don't know. I don't remember. I don't remember what happened after that. I blacked it out, my memory. But
Jeff Ward: But it does... I think it, is a a way of working that really was embedded in Elon's mind, that you could always get another good person. And that's held him in good stead till now. There's probably a giant stack of great resumes. And I think that one of the surprising things for me is that he's been able to create sustained technical success out of that.
Jeff Ward: Somehow there are enough people around who know what's going on that that method works.
Robert Rose: Yeah. I mean, SpaceX is a great brand.
Jeff Ward: For sure.
Robert Rose: Yeah.
Jeff Ward: And people still wanna work there. I think there are people at a certain point in their career with a certain amount of drive are happy to rally.
Robert Rose: Oh, yeah. If I don't think they're a fit for my company, I will certainly recommend people go to SpaceX. You know, you'll learn a ton. Like, I think a year at SpaceX is worth five, six, seven years at any other regular company.
Jeff Ward: Definitely. How did you come to the end of your time at SpaceX?
Robert Rose: Yeah. It's it's complicated. There's no simple answer.
Jeff Ward: Never is.
Robert Rose: So I I kinda felt like I'd done a lot of things there, and it wasn't really clear, like, well, what's next? And I didn't feel as... The same kind of excitement about the stuff that was next. I felt, I mean, the the the expression that was bouncing around my head was I've seen this movie before.
Jeff Ward: Yeah. And I feel that way about the space industry as a whole. Not to to... Like, again, I feel the same awkwardness as you do, but I'd... You know, I was in the alternative space industry for 35 years, and it succeeded.
Jeff Ward: And, okay. You know, why build another satellite kind of question goes through my mind from time to time.
Robert Rose: Yeah. Yeah. So that that was a lot. And then personal life, was also getting really hard.
Jeff Ward: Mhmm.
Robert Rose: My my wife and I, our kids, had gotten older. We had three boys. One was just born. And so the work hours like that was really press... Placing a huge strain.
Robert Rose: And every year, we would go home for the holidays and seriously, every year, we would renegotiate. Like, are we gonna go back to LA? Are we gonna go back to SpaceX? And, it was like I'd get a one year lease with my wife. Like, You know, I'll do LA for one more year.
Robert Rose: And then one winter, she's like, I'm done. I I don't wanna do this anymore. This this is the last year.
Jeff Ward: Was your family living in LA with you or were they...
Robert Rose: Yeah. Yeah. And we all... Yeah. And part of the pressure too was we had an amazingly weird, like, rental situation when we first landed there.
Robert Rose: Just... We just totally lucked out and got a great deal on this home that was walking distance from the beach, and we had a great relationship with the landlords. And then the landlord decided that he wanted his house back, and so we had to move. And we just moved into this dumpster fire of a house. And so my wife...
Robert Rose: It was like every other day, she was calling me about something that was wrong with the house, and we need to get out of here. This sucks. LA's... I'm done.
Jeff Ward: Yeah. And I think that that's, you know, the flip side of the burnout within SpaceX is the impact that it has on your family, especially if you have young kids.
Robert Rose: Yeah. So all those factors stacked up, and I I went to Gwen, and I tried to, as tactfully as possible, communicate to her that I think we should look for a replacement software leader and for the next phase of growth. I think... Oh, the next phase of growth. That was another thing too.
Robert Rose: So, you know, I... SpaceX was my first management job. And so this is weird, like, going from zero to 60 plus people. And I had a lot of doubts about my ability to sustain through 100, 150. So that that was going through my head, and we were starting to hit the kinds of organizational structure train...
Robert Rose: Strains that people talk about. And it was kinda working because we had a lot of very high EQ, incredibly intelligent people, on the team. But as we entered this phase of rapid growth and continued growth to get ready for Crew Dragon, I had a lot of self doubt about my ability to continue riding the wave.
Jeff Ward: How does that end up with you founding a company, which presumably is a company that needs growth and, you know, a large... A larger staff? Did you do a transition phase where you learned a little bit more about what you could do in management, or did you just go for it?
Robert Rose: So, ironically, I left SpaceX to go to a startup, and so saw very, very early stage startup stuff. And then Elon called me and, recruited me over to Tesla, and I worked for him a second time. And the autopilot org was... I wanna say we were about 110 or so. Yeah.
Robert Rose: Somewhere around 100, 110. And so then I got a taste of larger organization management as well as, like, publicly traded comp... At least an Elon managed publicly traded company, which is a little bit different. And then after that, went to Google and was also involved in, I mean, not directly, but several other larger organizations. I don't know.
Robert Rose: My my attitude at Reliable, you know, we started with just a couple of us in the garage. We're now 250, and my attitude is I'm just gonna be as aware as I can of my limitations and shortcomings and try to surround myself with great people. And so far, I've managed to stay on the wave this long. And I think I've been very fortunate here to have some great people around me that have been able to support me and the organization through various phases of growth and seems to be working so far, knock on wood.
Jeff Ward: I I really wanna have Juerg on the show if he'll, if he'll consent to an interview at some point.
Robert Rose: Yeah.
Jeff Ward: Juerg Frefel is one of the guys that worked with us at SpaceX, and now he's with you at Reliable.
Robert Rose: Yeah. I I got to know Juerg through the development of the Dragon avionic system for Dragon 2. That was a real slog to get the fault tolerant compute architecture and all the avionics, fault detection isolation recovery working. Juerg was one of several absolutely key people. There were interfaces between software and avionics to make make the dream reality.
Jeff Ward: Has that technology become any easier?
Robert Rose: No.
Jeff Ward: Because certainly, was one of the long running challenges during my tenure at SpaceX was how to get fault detection, isolation, and recovery working and how to get what I would call redundant compute systems working.
Robert Rose: It was that experience actually. It was a big inspiration for starting Reliable and replicating a bit of what we learned in the space industry in aviation. And it's... It is definitely not a solved problem. Definitely not.
Robert Rose: It's it's still today, even after having gone through the experience of building the FDIR and the fault tolerant computing stack at SpaceX. Doing it again here doesn't doesn't make it any easier. And I'd say it's even a bit harder because we have to demonstrate to a regulator, that it formally satisfies an an extremely high level of safety.
Jeff Ward: Yeah. It seems from the outside watching the progress at Reliable that you guys are managing the regulatory environment constantly and effectively. And yet I assume that a lot of the time that you've spent and a lot of the elapsed time for your program is to do with regulation. Is that a fair fair statement?
Robert Rose: Yeah. The the quick way to explain this is aviation has 25,000 plus pages of regulatory guidance material that the FAA has published or the FAA has recognized. And the burden of proof... The burden to demonstrate that, a system complies with all those regulations falls on you, the applicant. The government doesn't do this work for you.
Robert Rose: And so it's like you have to come up first with a a legal argument for why your new technology or component or whatever it is, has a right to be placed onto an aircraft. And you make that argument by auditing this 25,000 plus pages of material and then meticulously determining on your own applicability or inapplicability of these requirements. And then once something is determined applicable, then you have to propose how you demonstrate that you're going to comply, with that regulatory requirement. And that... You know, those things that can sound relatively simple can fork off into thousands of pages of documentation.
Robert Rose: And the company, I would say we spent probably six or seven... First six or seven years of the company was really just focused on that. It was just regular meeting cadences with the FAA, slogging through, all this regulatory material and proposing to them how we were gonna comply and then taking their feedback. And in some some cases, it's a very, methodical and logical process. And other times, they kind of run out of reasons to say no.
Jeff Ward: I've been through that part of the process. Yeah. You just have to keep bringing answers until they run out of questions. Yeah. And you're probably the first person I talked to who's, like, testified in front of congress.
Robert Rose: Yeah. That was an experience. That's... I I put that on the list of things that I never thought I would do at Reliable. That was really interesting.
Robert Rose: And that that came about for, I guess, the benefit of your listeners. The the FAA is not perfect. No government agency is, and congress has the power to do things to attempt to help, various government agencies, by helping them reorganize or supplying funding for various things. And we were really involved in the 2024 FAA Reauthorization Act, which is the five year bill that reauthorizes the FAA and helps them organize and funds the FAA. And so that...
Robert Rose: I I would describe that meeting, the testimony that I gave. It was it was kind of like a victory lap for the FAA reauth as the intent. And so I I gave a status update on what's working, what's not working out of that. Of course, I try to be positive and focus on the things that are working.
Jeff Ward: Did anybody ask you to run the FAA during that process?
Robert Rose: Yeah. No.
Jeff Ward: Because I know people who were asked. So... And coming to Reliable Robotics, like, what's the what's the thesis? And has the thesis evolved for you over the years as autonomous and semi autonomous drones have become more everyday object.
Robert Rose: The thesis has not really changed. I mean, the idea first came about... Juerg and I were talking, like, late 2016, early 2017 about autonomy autonomy in aviation and asking questions like, why don't we have autonomous aircraft? There's all this energy going into self driving cars and autonomous warehousing systems and whatnot. It just seems like a miss that nobody's focused on self flying planes or autonomous safety enhancing highly automated systems for aircraft.
Robert Rose: And I didn't even think initially about starting a company. I thought I was gonna join a company to work on this, and I I went... I'm not gonna name who, but I went to a bunch of companies and begged them to hire me to work on autonomy for aircraft. And everyone said, oh, no. This is impossible.
Robert Rose: This is never gonna happen, or it's never gonna happen in our lifetimes. People said, the FAA is too slow. They're too bloated. They're too bureaucratic. This is never gonna happen in The United States.
Robert Rose: And initially, when I heard this, I thought, well, these are really smart people I'm talking to. They must know more than me. So I believed him. But then kept talking to people, and eventually, this is where the SpaceX resume doesn't hurt. I I ended up getting connected with some people that worked in the in the FAA in aircraft certification, and I spoke with some people in NASA that worked on advanced safety technologies for aircraft and asked them, you know, why don't we have more advanced automation systems and planes?
Robert Rose: And the answer I got from them was essentially a readback of what I shared earlier, that many people in the industry don't understand how the certification process actually works. Like, you can't go to the FAA and say, hey, tell me how to certify autonomy. It doesn't work that way. You have to go to them and say, hey, if I had an aircraft that was autonomous, this is how I would propose to certify it. And then they're kinda like an umpire at a baseball game.
Robert Rose: It's like they they call balls and strikes.
Jeff Ward: Mhmm.
Robert Rose: And the reason nobody has ever attempted this before is because it's a lot of work to take, I mean, all functions, like everything that an airplane does, including the pilot, is a massive set of functions. And to first identify what all these functions are is hard. There's a lot of what airplanes do today.
Robert Rose: When I say airplanes, I'm including the pilot in this definition that that we take for granted, and we defer to pilot training. And when there's an accident, unfortunately, we often blame the pilot. Oh, it's because the pilot didn't use the system correctly. Oh, they didn't recognize this error. They didn't respond correctly.
Robert Rose: And so the solution then is, oh, we should improve pilot training. We should improve the manuals. We should make sure that pilots are tested for this thing. And that works up to a point. The problem now is if you're transferring those functions, that responsibility for those functions from the pilot into the automation, the bar is much higher.
Robert Rose: It's orders and orders of magnitude higher. Because now you're you're literally transferring the legal responsibility for the correct operation of the function from a human being to the manufacturer of the equipment and the US government. And that's an uncomfortable place for the US government to be, and so they take this responsibility very seriously. And so the thesis was somebody needs to do this. This needs to happen.
Robert Rose: Like, humanity must develop this technology. And I also felt quite strongly that The United States needs to develop this. If we're gonna be, a leading force in aerospace exports and aviation exports going into the later part of the 21st century, we have to we have to develop these technologies. We have to create the standards. We have to devise how to certify the equipment.
Robert Rose: We have to manufacture the equipment. If we don't do it, Europeans might do it. Chinese might do it. Like, those are basically the options. And and I felt, no.
Robert Rose: This needs to happen in The US. And I was really disappointed that many of the other companies I spoke with had given up on The United States. They said this is never gonna happen here. And so they were gonna go to another country to seek approval.
Jeff Ward: And given that... The height of that hurdle, like, what's the endpoint vision that drives it to be worth jumping over that higher regulatory hurdle?
Robert Rose: I mean, av... moving things through the air should be the default mode of transportation. I wanna I wanna live in the future. I wanna live in... The Fifth Element is probably the closest positive science fiction example of, like, lots and lots of flying stuff and being...
Robert Rose: Like, just being able to instantaneously move around the planet. You have to move through the air. Like, we're... Our roads are saturated. It's impossible to build new rail systems as we've seen.
Robert Rose: We're not gonna dig holes through the Earth to go to all the various places that we need to go. The only way to do this is through the air. It has to be air. And, unfortunately, we have an air transportation system that while it is very sophisticated, it's it's bursting at the seams here. We're seeing the limits of the traffic densities that humans can manage.
Robert Rose: It's it's pilots. It's air traffic controllers. It's the way the airspace is designed. It's the whole system. And if you wanna change that system, you have to start with how the aircraft are operated.
Robert Rose: You can't you can't start to push air traffic densities up until you can trust the onboard systems more. A lot of everything in aviation, not a lot of everything, it it comes down to margins and margins of safety. So we we layer all these
Jeff Ward: You're trying to design a system that then is more trustworthy and reliable than the human pilot.
Robert Rose: Yes. Yeah.
Jeff Ward: Right.
Robert Rose: Yeah. And when you can say, with a very high degree of certainty, I'm talking, like, one e minus seven, one e minus eight levels of reliability, like one failure in a hundred million hours of operation, when you can say, like, that aircraft will be within meters of the location I'm saying it is, and I... And you can trust that answer to one... Less than one failure in a hundred million hours of operation. Now you can start to push air traffic densities much further.
Robert Rose: You can increase frequencies of operations. You can throw a lot more aircraft in the sky. There's also a lot of limitations in aviation, go to margins of safety around just human workload and, the number of hours that a person can safely manage a safety critical system. So for good reason, we have limits on, how many hours per day people can work in this... In these environments.
Robert Rose: And that also drives a lot of the architecture of the system. When you start to remove these constraints, you can start to operate aircraft more throughout the day. You can operate them at more frequencies... Higher frequencies. You can go access more airports.
Robert Rose: That's another limitation too. Like, you have to think about all of the aspects of managing the people after they reach the destination. I'm talking about the people that operate the aircraft, the pilots.
Jeff Ward: Mhmm.
Robert Rose: And that just naturally, over decades of optimization, has driven us to this hub and spoke system that we have today. And this is why over the last decade or two, we've seen dramatic reductions in service across The United States. We've seen airports have complete... Some airports have completely lost service. COVID made things worse.
Robert Rose: We haven't really recovered. We've recovered the number of flights, but not to the diversity of locations.
Jeff Ward: Right.
Robert Rose: And then internationally, we have a pilot training problem. There's thousands of aircraft on order across the globe, yet the the planet is not producing pilots at the rate necessary in order to operate all of those planes. So what are we gonna do? Yeah. We've been trying to produce more pilots, but
Jeff Ward: Yeah. I guess maybe I've been deceived by watching your development program and haven't picked up on the size of the vision because it sounds from what you're describing that the vision is civil aviation as a whole.
Robert Rose: Yeah. And I I can appreciate how, as an outsider, you might not pick up on this vision. We're not the best at marketing.
Jeff Ward: No. It's not about... It's not necessarily even a marketing question. It's like watching technically the work that you're doing. Like, you guys are using a commercial airframe, and that doesn't telegraph 787.
Robert Rose: Yeah. This this is something that took me many months to appreciate when the idea for Reliable started to form. And this goes back to the certification basis, the means of compliance to demonstrate, how you comply with these regulations. That's... You've solved that problem once, and you've almost solved it permanently.
Robert Rose: Like, at the end of the day, like, most airplanes have wings and engines and landing gear, and they land on runways. And most of what goes into an airplane from a regulatory standpoint is the same aircraft to aircraft, and that that part is transferable. And this playbook, if you will, for how to certify an autonomous aircraft, that's the most valuable intellectual property that we've created at the company. Nobody else has that, at least as far as I know.
Jeff Ward: Yeah. That makes sense. That...
Robert Rose: And we've uncovered problems in this that we didn't foresee that I know others in the industry are not even thinking about. It's it's only when you get insanely deep in this problem space you start to realize how how much we take for granted about what people do today. And we've had to build requirements. And then once you have a requirement, we've had to invent methods for demonstrating compliance to these requirements. And many in the industry don't even know that these requirements exist or even should exist.
Jeff Ward: Yeah. And I I think now I see it, differently than I did going in because, of course, these planes are already built to be highly reliable and redundant downstream of the pilot. And to some extent, what I'm seeing now is that you're trying to build a highly reliable automated pilot because the rest of the plane has already been certified. And what you need to do now is not by any means trivial, but it's it's basically to automate and improve on the pilot activities of... In the in the plane.
Robert Rose: Yeah. That... That's a question I frequently get. Like, why aren't we just building a new clean sheet aircraft design? Wouldn't that be easier?
Robert Rose: And people often go to, like, wouldn't this be easier if you had a fly by wire system already on the plane? It... Fly by wire is like a fraction of a fraction of the problem. And
Jeff Ward: Mhmm.
Robert Rose: Taking on...
Robert Rose: In addition to the autonomy and certification basis for the autonomy, also taking off on an aircraft design would be huge. And and in my view, not the interesting part.
Jeff Ward: Yeah. It doesn't seem to help you in the problem space.
Robert Rose: No.
Jeff Ward: And you mentioned the interesting part. Are you still having fun?
Jeff Ward: I mean, you're embarked on a a long project that involves a lot of bureaucracy, which isn't by definition fun. But are you still enjoying yourself technically?
Robert Rose: It's weird to say this. But, yeah, I'm actually... I look forward to every day. This project has been an absolute blast. I think what works for me is it's a new challenge every day.
Robert Rose: I I also feel like the work that we're doing is very important and will be... I believe that this is going to be more impactful than anything I ever did at SpaceX or Tesla. I think autonomous aviation is gonna be one of the most important developments of the 21st century. I also love airplanes. I love flying.
Robert Rose: And so it's this really interesting Venn diagram of stuff that Robert just... Like, if I wasn't working, I would be flying. It's this interesting Venn diagram of, like
Jeff Ward: Was that before you got into space? Was that something you did all along? Or is it
Robert Rose: Yeah. I was in civil air patrol when I was in high school, and my mom flew. And
Jeff Ward: Right.
Robert Rose: My grandparents were pilots. And so I I heard a lot of flying stories growing up and used to go tool around a 172 with my mom and always knew one day I would be a pilot. I I just really love it.
Jeff Ward: There's so many former SpaceX people who are into flying.
Robert Rose: Yeah. It's also, it's the closest I'm ever gonna get to space. So... But I don't know. It's just such a beautiful thing.
Robert Rose: I think many people take it for granted getting on a commercial plane, just how special and unique that is that you can just be teleported to another place on the planet and go meet different people. And then when you're in a small plane especially, you have a much more direct understanding of what it is that you're doing and a view of planet Earth. It's... Right now, wanna go flying. I just really enjoy it.
Jeff Ward: Yeah. I understand. I think we've covered a lot of ground. Also, my dog is trying to convince me that it's time for me to finish.
Jeff Ward: But I'm gonna... Let me ask you my my popcorn round questions and see where where we get to. So what's your favorite science fiction?
Robert Rose: Oh, my favorite science fiction. God, Doctor Who is probably the first thing that pops into mind. The new Doctor Who. I think I've seen that whole entire series two and a half times. Watched it when it came out and then watched it, know, my boys.
Jeff Ward: And on a different tack, you know, we... I know a lot of kids that are trying to get into aerospace and... Or high-tech activities one way or the other. What would you recommend for them now? People who are like coming out of high school into college or like getting into a college career, what do you look for when you're interviewing people for Reliable that you could like hint at for people who are just getting started?
Robert Rose: Just build things. If you have an idea for something, just go try to build it. Whenever I look at a resume, the first place I go is I look at projects. Like, what what have you actually done? Coursework, helpful.
Robert Rose: Sure. Why not? GPA, sure. Why not? But usually, the strongest indicator of whether or not somebody's gonna be successful here is...
Robert Rose: And and this this is the same... This was true at SpaceX too. The strongest indicator was... Have you actually built things on your own? Have you actually shipped things on your own?
Robert Rose: If you're a software engineer, have you actually published software? Have you... Do you have a website? Do you have web apps? Do you have apps on the Apple App Store or Android App Store?
Robert Rose: Show me your code, that kind of thing. If you're an electrical engineer, have you actually built electronics? Do you have a website that shows the electronics that you build? If you're a mechanical engineer, have you actually built mechanisms and structures? And for a young person, they...
Robert Rose: We usually have a pretty strong sense if someone's gonna be successful early in the process, if they have pictures of projects on their resume or a portfolio website or something. And sometimes people put up, like, short YouTube videos of explaining the things that they built, and you just know, like, alright. If somebody's actually, like, building stuff and... Okay. That's what we want.
Jeff Ward: I I feel like it's hard to overemphasize that point. It's something that I try to say to every kid that I'm mentoring. Go build things. Yeah. Do projects.
Robert Rose: Go make mistakes. It's okay too if you're not successful building something, but go go try. You'll learn a lot.
Jeff Ward: And do you think we can make the world a better place apart from with autonomous airplanes, or is that your your diagnosis?
Robert Rose: Well, there's actually another set of technologies that I'm really excited about. You know, we we know a number of people who've gone into work, in nuclear. Like, Doug Bernauer started a nuclear energy company, and I feel like that's kind of the other big piece of the puzzle is ubiquitous lower cost electricity and better energy security and energy abundance. I feel like the combination of those two things is gonna make for a very exciting end of the 21st century.
Jeff Ward: Yeah. I see that. I think that makes makes sense because it's energy scarcity kind of drives a lot of other things.
Robert Rose: Yeah. There's a lot of strife in the world that, is caused by disagreements over how energy should be allocated.
Jeff Ward: Actually, I've really enjoyed catching up and going over this arc. I appreciate that you took some time out and stepped into the silent booth to talk to me.
Robert Rose: Well, I appreciate you doing this. It's neat to document this history. Thank you.
Jeff Ward: Yeah. No. You're welcome. Thank you. This episode was produced with assistance from Devan Schwartz, and you can find us at itsnotrocketscience.space.