\u201cHe walked into the laboratory and held his finger out and pointed directly at me,\u201d recalled Maj. Ray Tierney, the U-2 pilot who founded and now leads the lab. \u201cHe said, \u2018Ray, I got a challenge.\u2019 We didn\u2019t even say hello.\u201d<\/p>\n\n\n\n
Roper, a string theorist turned reluctant government bureaucrat who was known for his disruptive style and seemingly endless references to science-fiction, wanted the team to update the U-2\u2032s software during a flight. It was a feat the U.S. military had never accomplished, but to Tierney\u2019s exasperation, Roper wanted only to know how long it would take for the lab to pull off.<\/p>\n\n\n\n
The answer, it turns out, was two days and 22 hours.<\/p>\n\n\n\n
A month later, in mid-November, Roper laid out a second challenge: Create an AI copilot for the U-2, a collection of algorithms that would be able to learn and adapt in a way totally unlike the mindlessness of an autopilot that strictly follows a preplanned route.<\/p>\n\n\n\n
That task took a month, when an AI entity called Artu\u03bc (pronounced Artoo, as in R2-D2 of Star Wars fame) was given control of the U-2\u2032s sensors and conveyed information about the location of adversary missile launchers to the human pilot during a live training flight<\/a> on Dec. 15.<\/p>\n\n\n\n Now, the U-2 Federal Laboratory is at work again on another undisclosed challenge. Tierney and Roper declined to elaborate on the task in interviews with Defense News. But Roper acknowledged, more broadly, that a future where AI copilots regularly fly with human operators was close at hand.<\/p>\n\n\n\n \u201cArtu\u03bc has a really good chance of making it into operations by maybe the summer of this year,\u201d Roper told Defense News before his Jan. 20 departure from the service. \u201cI\u2019m working with the team on how aggressive is the Goldilocks of being aggressive enough? The goal is fairly achievable, but still requires a lot of stress and effort.\u201d<\/p>\n\n\n\n In order to ready Artu\u03bc for day-to-day operations, the AI entity will be tested in potentially millions of virtual training missions \u2014 including ones where it faces off against itself. The Air Force must also figure out how to certify it so that it can be used outside of a test environment, Roper said.<\/p>\n\n\n\n \u201cThe first time we fly an AI in a real operation or real world mission \u2014 that\u2019s the next big flag to plant in the ground,\u201d Roper said. \u201cAnd my goal before I leave is to provide the path, the technical objectives, the program approach that\u2019s necessary to get to that flag and milestone.\u201d<\/p>\n\n\n\n Meanwhile, the team has its own less formal, longer-term challenge: How do you prove to a giant organization like the Air Force, one that is full of bureaucracy and thorough reviews, that a small team of five people can quickly create the innovation the service needs?<\/p>\n\n\n\n No regulations, no rules<\/b><\/p>\n\n\n\n During a Dec. 22 interview, Tierney made it clear that he had little interest in discussing what the U-2 Federal Lab is currently working on. What he wanted to promote, he said, was the concept of how federal laboratories could act as innovation pressure chambers for the military \u2014 a place where operators, scientists and acquisition personnel would have the freedom to create without being hamstrung by red tape.<\/p>\n\n\n\n For those immersed in military technology, focusing on the promise of federal laboratories can seem like a bit of a letdown, if not outright academic, especially when compared to a discussion about the future of artificial intelligence. The U.S. government is rife with organizations \u2014 often named after tired Star Wars references that would make even the most enthusiastic fanboy cringe \u2014 created in the name of fostering innovation and rapidly developing new technologies. Many of those advances never make it over the \u201cvalley of death\u201d between when a technology is first designed and when it is finally mature enough to go into production.<\/p>\n\n\n\n Ultimately, that\u2019s the problem the U-2 Federal Lab was created to solve.<\/p>\n\n\n\n As a federally accredited laboratory, the team is empowered to create a technology, test it directly with users, mature it over time, and graduate it into the normal acquisition process at Milestone B, Tierney said. At that stage, the product is ready to be treated as a program of record going through the engineering and manufacturing development process, which directly precedes full-rate production.<\/p>\n\n\n\n \u201cWe\u2019re basically front loading all the work so that when we hand it to the acquisition system, there\u2019s no work left to do,\u201d Tierney said. The lab essentially functions as a \u201cblue ocean,\u201d as an uncontested market that does not normally exist in the acquisition system, he explained. \u201cThere\u2019s no regulations; there\u2019s no rules.\u201d<\/p>\n\n\n\n While that might sound similar to organizations the Air Force has started to harness emerging technologies, such as its Kessel Run software development factory, Tierney bristled at the comparison.<\/p>\n\n\n\n \u201cWe\u2019re basically developing on the weapon system, and then working our way back through the lines of production, as opposed to a lot of these organizations like Kessel Run, which is developing it on servers and server environments,\u201d he said.<\/p>\n\n\n\n That distinction is critical when it comes to bringing modern software technologies to an aging platform like the U-2, an aircraft that took its first flight in 1955 and is so idiosyncratic that high speed muscle cars are needed to chase the spyplane and provide situational awareness as it lands.<\/p>\n\n\n\n Because the team works only with the U-2, they understand the precise limitations of the weapon system, what its decades-old computers are capable of handling, and how to get the most out of the remaining space and power inside the airplane.<\/p>\n\n\n\n Besides Tierney, there are only four other members of the U-2 Federal Lab: a National Guardsman with more than a decade of experience working for IBM, and three civilians with PhDs in machine learning, experimental astrophysics and applied mathematics. (The Air Force declined to provide the names of the other employees from the lab.)<\/p>\n\n\n\n As the lone member of the team with experience flying the U-2, Tierney provides perspective on how the aircraft is used operationally and what types of technologies rank high on pilots\u2019 wish lists. But what most often drives the team are the projects that can make the biggest impact \u2014 not just for the U-2, but across the whole Defense Department.<\/p>\n\n\n\n Making it work<\/b><\/p>\n\n\n\n One of those projects was an effort to use Kubernetes, a containerized system that allows users to automate the deployment and management of software applications, onboard a U-2. The technology was originally created by Google and is currently maintained by the Cloud Native Computing Foundation.<\/p>\n\n\n\n \u201cEssentially, what it does is it federates or distributes processing between a bunch of different computers. So you can take five computers in your house and basically mush them all together into one more powerful computer,\u201d Tierney said.<\/p>\n\n\n\n The idea generated some resistance from other members of the lab, who questioned the usefulness of deploying Kubernetes to the U-2\u2032s simple computing system.<\/p>\n\n\n\n \u201cThey said, \u2018Kubernetes is useless to us. It\u2019s a lot of extra processing overhead. We don\u2019t have enough containers. We have one processing board, [so] what are you distributing against? You got one computer,\u2019\u201d Tierney said. But a successful demonstration, held in September, proved that it was possible for even a 1950s-era aircraft to run Kubernetes, opening the door for the Defense Department to think about how it could be used to give legacy platforms more computing power.<\/p>\n\n\n\n It also paved the way for the laboratory to do something the Air Force had long been aiming to accomplish<\/a>: update an aircraft\u2019s code while it was in flight.<\/p>\n\n\n\n \u201cWe wanted to show that a team of five in two days could do what the Department of Defense has been unable to do in its history,\u201d Tierney said. \u201cNobody helped us with this; there was no big company that rolled in. We didn\u2019t outsource any work, it was literally and organically done by a team of five. Could you imagine if we grew the lab by a factor of two or three or four, what that would look like?\u201d<\/p>\n\n\n\n The lab has also created a government-owned open software architecture for the U-2, a task that took about three months and involved no additional funding. Once completed, the team was able to integrate advanced machine learning algorithms developed by Sandia National Laboratories in less than 30 minutes.<\/p>\n\n\n\n \u201cThat\u2019s my litmus test for open architecture,\u201d Tierney said. \u201cGo to any provider that says I have open architecture, and just ask them two questions. How long is it going to take you to integrate your service? And how much is it going to cost? And if the answer isn\u2019t minutes and free, it\u2019s not quite as open as what people want.\u201d<\/p>\n\n\n\n The U-2 Federal Lab hopes to export the open architecture system to other military aircraft and is already in talks with several Air Force and Navy program offices on potential demonstrations.<\/p>\n\n\n\n Could the Air Force create other federal laboratories to create specialized tech for other aircraft? The U-2 lab was designed from the outset to be franchisable, but Tierney acknowledged that much of the success of future organizations will rest in the composition of the team and the level of expertise of its members.<\/p>\n\n\n\n \u201cCan it scale? Absolutely. How does it scale is another question,\u201d Tierney said. \u201cDo you have one of these for every weapon system? Do you have just a couple sprinkled throughout the government? Does it proliferate en masse? Those are all questions that I think, largely can be explored.\u201d<\/p>\n\n\n\n For now, it\u2019s unclear whether the Air Force will adopt this framework more widely. The accomplishments of the U-2 Federal Laboratory have been lauded by Air Force leaders such as Chief of Staff Gen. Charles \u201cCQ\u201d Brown, who in December wrote on Twitter<\/a> that the group \u201ccontinue[s] to push the seemingly impossible.\u201d<\/p>\n\n\n\n However, it remains to be seen whether the Biden administration will give the lab the champion it found in Roper, and continued pressure on the defense budget \u2014 and to retire older aircraft like the U-2 \u2014 could present greater adversity for the lab.<\/p>\n\n\n\n But as for the other challenge, the one Tierney and Roper didn\u2019t want to discuss, Tierney offered only a wink as to what comes next:<\/p>\n\n\n\n \u201cWhat I can say is that the future is going to be an interesting one.\u201d<\/p>\n\n\n\n![\"\"](\"\/wp-content\/uploads\/2026\/08\/201204-F-IF848-0013.jfif_.jpg\")
![\"\"](\"\/wp-content\/uploads\/2026\/08\/201215-F-WF370-1172.jfif_.jpg\")