# The Node Is Not the Service

*CRASAR's Pearlington Flights, iRobot's S-1, ScanEagle on a High-Speed Hull, and Unmanned Access Without a Federal Unit*

**Prepared as a capability and political-economy analysis**
Platform: Quiet Systems

---

> **Research premise.** September 2005 is when unmanned Sense and Move could be launched by a university consortium over a Mississippi disaster town, written onto a public-company registration statement, and hung on a high-speed Navy hull — without a federal UAS unit, without a finished hunter-killer initial operational capability, and without a contemporaneous primary for the claimed submarine launch. The trust object is not the airframe. It is whether the node that can launch is the service that would normally own the air, the tape, or the hull.

## Abstract

**Research premise.** A week in September is easy to file as five unmanned headlines. Read as a trust problem it is one node event. On 7 September 2005 the University of South Florida dated a release, carried the next day by ScienceDaily, claiming that the Center for Robot-Assisted Search and Rescue had flown a hand-launched four-foot fixed-wing aircraft and a Like90 T-Rex electric helicopter over Pearlington, Mississippi, after Hurricane Katrina, "the first known use of small UAVs for an actual disaster." Florida responders working from Stennis Space Center tasked the team after complete houses blocked Pearlington's main street; the aircraft launched from an open patch of road among downed trees and power lines; within two hours the data showed no trapped survivors and a Pearl River crest that was not an added threat. An 15 September National Science Foundation release, also via ScienceDaily, restated the pair as "one of the first deployments of such craft for disaster search and rescue" and named the Safety Security Rescue Research Center, an NSF industry-university partnership of USF, Minnesota, and firms. On 30 September iRobot filed Amendment No. 2 to Form S-1, File 333-126907. PackBot's manufacturer put more than 200 tactical robots sold to the U.S. military, 20.1 percent of 2004 revenue from the federal government, 35.9 percent of 2004 contract revenue from Future Combat Systems, a single Chinese plant for Roomba, a single U.S. plant for the military line, and a government right to use inventions and disclose technical data, on the public tape. A 28 February 2006 Boeing release, used here as the fetched primary for a September award, stated that "a $13 million contract modification was awarded in September 2005 to provide ScanEagle system support for Navy high-speed vessels and an afloat forward staging base." Defense Industry Daily later reprinted a $13.9 million modification to N00019-05-C-0045 in the same terms. Later encyclopedic summaries place a USS *Oklahoma City* Long-term Mine Reconnaissance System launch in September; no 2005 Navy release was fetched. No September MQ-9 initial operational capability appears in the fetched program file. The products are a civil orbit without a federal unit, a ground-robot manufacturer without a public market yet, a Skyhook orbit without a carrier deck, and two empty lines. FAA authorization, a named hull, a contemporaneous LMRS primary, and raw Pearlington video were not fetched; those Unknowns are not safe defaults.

_Keywords: unmanned aircraft systems, Hurricane Katrina, CRASAR, iRobot, PackBot, ScanEagle, Long-term Mine Reconnaissance System, MQ-9, Passport, Control Fabric, Sense-Move-Act_

## 1. Introduction: The Apparent Recap

A defense-industrial headline reduces September 2005 to a stack of firsts: a university team flies small unmanned aircraft over a Katrina town; a Massachusetts robot maker files to go public; the Navy hangs a tuna-spotter-derived aircraft on a high-speed hull; a submarine is later said to have launched a heavyweight undersea vehicle; the Air Force's hunter-killer remains unfinished. A reader who treats those as five events expects a highlight reel. The contemporaneous public record does not make that calculation. It describes a launch node that is a National Science Foundation consortium rather than a federal UAS unit, a manufacturer whose military line and consumer line are about to sit on the same equity tape, a runway-independent Skyhook hung on a non-aviation hull, and two plates that September's opened file cannot fill.1

The disparity is easiest to misunderstand when the month is read as a recap. Under that reading, Pearlington becomes a disaster anecdote, the S-1 a markets item, ScanEagle a contract win, the *Oklahoma City* launch a submarine first, and MQ-9 a program footnote. Later memory then supplies a type name, a Certificate of Authorization file, a named hull, a Navy trial report, and an initial-operational-capability memorandum that September's public file does not contain as 7 September facts. The opened September file runs the other way. The object is the node: a university team that can put Sense over wreckage from a road patch, a manufacturer that can register PackBot economics and a government right to shop the data, a Skyhook that can be bought for a high-speed hull, and two plates the opened file cannot fill.

This distinction matters. Capability analysis can target what a system can perceive, who may command it, and whether the evidence chain would let a later operator trust the path from sensor to act. Political-economy analysis asks whether unmanned access is still a property of a federal unit, a finished program of record, or a traditional aviation hull — or something a university partnership, a public registrant, and a catapult-and-rope can hold without those properties. September 2005 answers that question more cleanly than it answers hours over Pearlington or sorties from a named ship. A university team launched. A robot maker filed. The Navy bought Skyhook for hulls that are not carriers. The tube and the hunter-killer stayed empty.

The argument developed here is that the node is not the service, and that the trust failure is dual: launch plus title. Pearlington is Sense without a federal UAS unit. The S-1 is military Move without a public market and without a government technical-data lock. ScanEagle is an orbit without a runway and without a fetched named hull. The Long-term Mine Reconnaissance System item is a claimed tube without a 2005 primary. MQ-9 is a hunter-killer without a September gate. LrrK's objects earn their place only where they keep those plates separate. Sibling files on 2001, 2004, 2007, 2008, 2009, 2010, and 2011 are not rebuilt.

## 2. A Hand Launch Over Pearlington

The first public plate is a university release, not a federal after-action. ScienceDaily, dated 8 September 2005 and sourced to the University of South Florida, carried a Tampa dateline of 7 September. "Using two types of small unmanned aerial vehicles (UAVs) — one fixed wing and one helicopter — scientists from the Center for Robot-Assisted Search and Rescue (CRASAR) at the University of South Florida worked with other Florida rescuers in hard-hit Mississippi immediately in the aftermath of Hurricane Katrina." The next sentence is the claim the month will be remembered by: "The first known use of small UAVs for an actual disaster."2

The airframes in that release are described, not typed to a program of record. "The small fixed wing vehicle, looking much like a four-foot-long model airplane, provided video and thermal imagery from 100 to 1,000 feet, giving rescuers an overview of the disaster area. The vehicle is launched by manually throwing it into the air. It requires only a small clearing, about the length of five cars, to take off or land." The rotorcraft is named. "Carrying a camera, the miniature, electric powered T-Rex helicopter from Like90 gave a hummingbird's eye view while hovering up to 250 feet high. It was also able to zoom its camera in to explore roof tops and look in windows." Robin Murphy, identified as CRASAR director, said the platforms "require less than 10 minutes to set up and fly" and "were designed to be easily carried by responders as they hike into the debris." The vehicles "were provided in partnership with a National Science Foundation industry/university consortium that focuses on new safety, security and rescue technology."2

The tasking chain is civil and state, not a federal UAS squadron. CRASAR, the release stated, had been "focusing on developing and testing small UAVs since being called up by Florida Task Force 3 during Hurricane Charley in 2004." Murphy's lesson from Charley was roof-beyond-the-flooded-road: "It takes too long for manned helicopters to get there — if the radios are working." At the request of the Louisiana State University Fire Emergency Training Institute, the team "was deployed Aug. 30 from Tampa to assist with rescue efforts just east of the French Quarter in New Orleans," then "had to turn around just short of the city limits" because of destroyed or flooded freeways and a lack of secure surface roads. Florida responders working out of Stennis Space Center then sent the team to Pearlington after reports of survivors stranded by flood waters. "With progress into Pearlington blocked by complete houses that had been pushed by the storm surge into the middle of the main street, the team launched from an open patch of road surrounded by downed trees and power lines. Within two hours, the responders had the data form the UAVs showing that no survivors were trapped and that the flood waters from the cresting Pearl River were not posing an additional threat." Murphy added, "Katrina was so much worse than Charley."4

A second date sits on the same plate and does not resolve. The USF/ScienceDaily text says Murphy and Chandler Griffin of Like90 "flew over Bay St. Louis Sept. 1 collecting data near the destroyed US 90 bridge while returning to Tampa." A 12 September Space Daily reprint via phys.org, otherwise the same body, says they flew "while returning to Tampa Sept. 6." The discrepancy is left standing. CRASAR's earlier identity in the same release is ground, not air: "CRASAR was responsible for the introduction of small ground mobile robots into emergency response at the World Trade Center in 2001."5

Those sentences are facts about what named outlets published on named days. They are not, without wreckage logs or a federal flight table, a finding that the two-hour negative search was complete, and they are not, without a type plate in the 7 September text, a finding that the fixed-wing aircraft was a named program-of-record airframe. Honesty requires four labels on that plate. Fact: USF dated a 7 September claim of two small unmanned types over Mississippi wreckage; ScienceDaily carried it on the 8th; the fixed-wing is a hand-launched four-foot airframe with video and thermal imagery; the rotorcraft is a Like90 T-Rex; tasking ran from a New Orleans abort to Florida responders at Stennis to a Pearlington road-patch launch; the two-hour product was a negative survivor find and a Pearl River assessment. Inference, moderate: the node that could launch on a blocked street was a university-industry consortium, not a federal UAS unit; the useful product is the negative find, not a technological miracle. Judgment: unmanned access entered U.S. wreckage as a civil research node. Unknown: FAA authorization text; raw video archive; an independently fetched USF.edu original; Bay St. Louis as 1 September or 6 September; any federal UAS unit flying the same town on the same days.

A Watch desk that records only "drones flew Katrina" has already lost the object. CRASAR is the operator. Pearlington is the air. The Passport event is a civil orbit whose enforcement, in the fetched releases, is a road patch, not a Certificate of Authorization file. Treating the 7 September claim as proof that a federal disaster UAS existed is a judgment the document does not support.

## 3. What a Later Foundation Release Restated

The second public plate is an 15 September National Science Foundation release, used here as same-month restatement, not as a new flight. ScienceDaily, sourced to NSF, opened: "Providing the benefits of speed, portability and access, a pair of unmanned aerial vehicles (UAVs) surveyed storm-damaged communities in Miss. as part of the search for trapped survivors of Hurricane Katrina." The claim is slightly softer than USF's "first known use." NSF called it "one of the first deployments of such craft for disaster search and rescue." United Press International, via phys.org the same day, hardened the line again: "the first domestic use of such surveillance vehicles." Those three phrasings are facts about what each outlet printed. They are not an independent adjudication that no earlier small-UAV disaster flight exists.6

Murphy's architecture sentence is the month's Sense split. "The two UAVs packed a one-two punch. The fixed-wing provided a quick overview of an area over several miles, but the use of the miniature helicopter to hover by buildings and on roofs — and to takeoff straight up — really offers new functionality." The NSF text names the institutional node more completely than the USF dateline. Florida emergency responders asked "the Safety Security Rescue Research Center (SSRRC) team to respond." Murphy "led the effort with other members of the SSRRC, an NSF-supported industry-university partnership among USF, the University of Minnesota and numerous defense and advanced technology companies." The fixed-wing is again "a 4-foot-long airplane with mounted video and thermal imagery cameras that can capture details from as far away as 1,000 feet," hand-launched, five-car-length landing. The T-Rex is "provided by SSRRC partner Like90." The two-hour Pearlington product is repeated.7

Honesty requires four labels on the NSF plate. Fact: a dated NSF release exists via ScienceDaily; it names SSRRC, USF, Minnesota, and Like90; it restates the road-patch launch and the two-hour negative find; it claims "one of the first" rather than "the first known." Inference, moderate: NSF is certifying a research-center deployment, not standing up a federal UAS unit; UPI's "first domestic use" is a wire hardening, not a new primary. Judgment: the foundation certified civil Sense as a dated event and left the authorization file empty. Unknown: an independently fetched nsf.gov original; any Certificate of Authorization number; any federal tasking order.

A later identification must stay later. A 2015 Murphy essay named an AeroVironment Raven loaned with Special Operations Command permission as the fixed-wing and treated a later FAA certificate-of-authorization "clarification" as a Katrina aftermath. Those sentences are 2015 speech. They are not used to type the four-foot airplane or to fill the FAA empty line. Later "Predator flew Katrina" tertiary lines are refused on the same rule. Until a dated pairing of a named tail, a named authorization, and a named federal unit exists, Watch records a university node that could launch. Treating the 2015 type name as a September primary would certify the wrong artifact.

## 4. PackBot Economics on the Public Tape

The third public plate is a registration statement, not a combat first. On 30 September 2005 iRobot Corporation filed Amendment No. 2 to Form S-1, File 333-126907, with the Securities and Exchange Commission. The registrant is a Delaware corporation at 63 South Avenue, Burlington, Massachusetts; Colin M. Angle is chief executive. The prospectus is subject to completion. The company has applied to list on the NASDAQ National Market under "IRBT." No public market yet exists. That last sentence is the Passport condition, not a trading fact.8

The industrial identity the filing puts on tape is dual. "Our Roomba floor vacuuming robot and recently announced Scooba floor washing robot perform time-consuming domestic chores, and our PackBot tactical military robots perform battlefield reconnaissance and bomb disposal." The company is "developing the Small Unmanned Ground Vehicle reconnaissance robot for the U.S. Army's transformational Future Combat Systems program and, in conjunction with Deere & Company, the R-Gator unmanned ground vehicle." Over the prior three years it "sold more than 1.2 million of our Roomba floor vacuuming robots" and "sold to the U.S. military during that time more than 200 of our PackBot tactical military robots, most of which have been deployed on missions in Afghanistan and Iraq." The National Defense Authorization Act of 2001 is recited as stating the goal that "by 2015, one-third of the operational ground combat vehicles of the Armed Forces are unmanned."9

The economics are the month's supply object. Total 2004 revenue was $95.043 million. For the year ended 31 December 2004 the company "derived 73.8% of our revenue from our Roomba floor vacuuming robots" and "derived 20.1% ... of our revenue, directly or indirectly, from the U.S. federal government and its agencies." For the six months ended 2 July 2005 the federal share was 47.6 percent. "In the year ended December 31, 2004, 35.9% of our contract revenue was derived from our participation in the U.S. Army's Future Combat Systems program." Future PackBot sales "will depend largely on our ability to secure contracts with the U.S. Army under its robot programs." Those figures are facts about what the S-1 printed. They are not a 30 September award and they are not an initial-public-offering price.10

The manufacturing and rights language is the trust boundary. "We currently depend on one contract manufacturer, Jetta Company Limited, to manufacture our consumer products at a single plant in China and rely on one contract manufacturer, Gem City Engineering Corporation, to manufacture our military products at a single plant in the United States. Moreover, we do not have a long-term contract with Jetta Company Limited and the manufacture of our consumer products is provided on a purchase-order basis." PackBot export "require[s] a license from the U.S. federal government." Some contracts "allow the U.S. federal government rights to use, or have others use, patented inventions developed under those contracts on behalf of the government. Some of the contracts allow the federal government to disclose technical data without constraining the recipient in how that data is used. The ability of third parties to use patents and technical data for government purposes creates the possibility that the government could attempt to establish additional sources for the products we provide that stem from these contracts." Competitors named on the ground-robot line include Foster-Miller, "a wholly owned subsidiary of QinetiQ North America, Inc.," Allen-Vanguard, and Remotec, "a division of Northrop Grumman Corporation," plus Lockheed Martin, BAE Systems, and General Dynamics.11

Honesty requires four labels. Fact: Amendment No. 2, 30 September 2005, File 333-126907; more than 200 PackBots; the revenue and concentration figures as the filing states them; Jetta China on purchase order; Gem City as the single U.S. military plant; PackBot export license; government rights to use inventions and disclose technical data; named competitors including Foster-Miller/QinetiQ; NASDAQ application, no public market yet. Inference, moderate: the military line the government may shop and the consumer line that depends on a single Chinese plant are about to share one equity tape. Judgment: PackBot's manufacturer is a public registrant; unmanned ground Move is now a disclosure object. Unknown: offering price and share counts; a 30 September production-lot notice; Gem City's plant city, which this amendment does not name.

A Watch desk that records "iRobot is going public" has already lost the month. The artifact is an S-1, not a priced offering. Passport would record a registrant, not a listing. Control Fabric is the government-rights clause. Treating Amendment No. 2 as proof the company had a public market, or as proof the government had already created a second PackBot source, is a judgment the filing does not support. The 9 November pricing is after the collection cutoff and is left empty.

Foster-Miller's QinetiQ owner is a one-line pointer to the November 2004 sibling on title, not a second thesis. The S-1 names the competitor. It does not reopen that close.

## 5. Skyhook on a High-Speed Hull

The fourth public plate is a later company recitation of a September modification, not a same-day Defense Department daily. On 28 February 2006 Boeing announced that ScanEagle, "a long-endurance fully autonomous unmanned aerial vehicle developed by Boeing and The Insitu Group," had surpassed 10,000 combat flight hours. Buried in the architecture paragraph is the September sentence this paper needs: "A $13 million contract modification was awarded in September 2005 to provide ScanEagle system support for Navy high-speed vessels and an afloat forward staging base." The same release dates the Marine deployment to August 2004 and the Navy deployment to July 2005 for Expeditionary Strike Group missions and Persian Gulf oil-platform security. Peggy Holly, Boeing ScanEagle program manager, said the Navy had used the aircraft "to identify and target suspicious ships." Launch is "a pneumatic wedge catapult"; recovery is "a 'Skyhook' system ... with the UAV catching a rope hanging from a 50-foot high pole." "The patented system makes ScanEagle runway-independent." USS *Cleveland* is named as a past Expeditionary Strike Group host, not as the high-speed vessel in the September modification.12

An April 2005 Boeing release, used here only as established public context for the family the September modification extends, dated a $14.5 million Navy contract for Expeditionary Strike Group missions and Persian Gulf oil-platform security, ship-launched and recovered. Holly then called it "ScanEagle's first deployment aboard a Navy vessel." Those sentences are April facts, not September 2005 facts. They establish that Skyhook on a ship was already a sold product when the September modification added high-speed vessels and an afloat forward staging base.13

Defense Industry Daily reprinted a contract paragraph in the same terms and a different dollar. "The Boeing Co. in St. Louis, MO received a $13.9 million modification to a previously awarded firm-fixed-price contract (N00019-05-C-0045) to provide persistent Intelligence, Surveillance, Reconnaissance UAV services for an Afloat Forward Staging Base, and on the High Speed Vessel, in direct support of Operation Iraqi Freedom and the Global War on Terrorism. Work will be performed onboard a Navy vessel in the Pacific, and is expected to be completed in September 2006." Naval Air Systems Command, Patuxent River, is the issuing activity. The original $14.5 million award on the same contract number, DID noted, was ScanEagle. DID then inferred that HSVX-1 *Joint Venture* was "almost certainly the vessel," and recorded that *Joint Venture*'s charter ended in July 2005. That hull inference is DID's, not a fetched Defense Department naming, and it sits poorly next to a July charter end and a "Navy vessel in the Pacific" work sentence. It is not used as a September fact.14

Honesty requires four labels. Fact: Boeing, 28 February 2006, recites a September 2005 $13 million modification for high-speed vessels and an afloat forward staging base; DID reprints a $13.9 million N00019-05-C-0045 modification in those terms, Pacific vessel, complete September 2006, Naval Air Systems Command; Skyhook and catapult as Boeing described them; USS *Cleveland* as a named past host, not as the September hull. Inference, moderate: the Navy is buying runway-independent Sense for hulls that are not carriers; the dollar discrepancy is a recitation problem, not proof of two awards. Judgment: Skyhook is now a product that can be hung on a high-speed vessel; the launch node is a catapult and a pole, not a carrier air wing. Unknown: the original DefenseLink daily-contracts text; the named hull; any September first flight from the modification.

A Passport that recorded ScanEagle as a carrier product, or as a named-hull fielding in September, would have certified the wrong artifact. The artifact is a modification for high-speed vessels and an afloat forward staging base, recited later, with a $13 million / $13.9 million split and an empty hull line. Control Fabric is Skyhook. Watch refuses a September first flight and refuses DID's *Joint Venture* certainty. Lab is a tuna-spotter-derived airframe already in Marine and Navy hours, now being bought for hulls that do not look like aviation platforms.

## 6. An Empty Tube and an Unfinished Hunter-Killer

The Long-term Mine Reconnaissance System item is contrast, not a fifth thesis. Later open summaries, including encyclopedic pages seen in search and not treated as primaries, state that USS *Oklahoma City* (SSN-723) successfully launched the 20-foot vehicle in September 2005 for covert mine countermeasures. No September 2005 Navy.mil release was fetched. A 26 November 2007 Boeing release describes a later submerged recovery by a named-as-Navy attack submarine and calls the vehicle AN/BLQ-11, formerly Long-term Mine Reconnaissance System; it does not date a September 2005 *Oklahoma City* launch. The 2004 Navy *Unmanned Undersea Vehicle Master Plan* is a sibling file's object and is not rebuilt. If a 2005 launch occurred, a submarine-launched autonomous 21-inch vehicle would match that plan's heavyweight class. The opened September file does not contain the launch as an A1 fact.15

Honesty requires four labels on the tube. Fact: later summaries repeat an *Oklahoma City* September 2005 launch; no contemporaneous Navy primary was fetched; the 2007 Boeing recovery release is a later event. Inference, low-moderate: a September at-sea event is widely repeated and remains uncertified here. Judgment: the trust boundary is the missing primary, not the pressure hull. Unknown: trial report, launch date as a Navy fact, recovery on that trial, vehicle serial. Until a dated Navy or Boeing 2005 pairing exists, Watch records an empty tube. Treating encyclopedic repetition as proof the launch occurred is a judgment this paper refuses. "Not established" is a gap. It is not a finding that the gap is safe.

MQ-9 is the other contrast: an unfinished hunter-killer, not a September fielding. The fetched GlobalSecurity program compilation records a February 2001 first flight, a June 2003 Air Combat Command concept of operations, and system development and demonstration beginning in FY05. It records no September 2005 initial operational capability. A 19 November 2004 Aeronautical Systems Center notice, already the object of the November 2004 sibling, had stated that the government did not own the data rights. That notice is not reopened. The September rhyme is iRobot's: the S-1 warns that the government may use inventions and disclose technical data. Two industrial models sit on paper this month. Neither is a September MQ-9 gate.16

A Watch desk that converted a later Reaper initial operational capability into a September 2005 fact would have certified the wrong event. The hunter-killer is still in development. The civil disaster aircraft has already flown. The node that could launch was not the program that still could not.

## 7. What a Passport Would Have Recorded

A September Passport, written the way LrrK would write it, would have recorded three property objects and left the rest empty. Pearlington: operator CRASAR / Safety Security Rescue Research Center; 7–8 September USF/ScienceDaily claim and 15 September NSF restatement; four-foot hand-launched fixed-wing plus Like90 T-Rex; road-patch launch; two-hour negative find; "first known use" as the center's own claim; FAA file, federal unit, and later Raven identification empty. iRobot: Amendment No. 2, 30 September, File 333-126907; more than 200 PackBots; revenue and concentration as filed; Jetta China; Gem City United States; export license; government-rights clause; NASDAQ application; priced offering empty. ScanEagle: September modification as recited 28 February 2006; $13 million in the Boeing sentence; $13.9 million and N00019-05-C-0045 as DID reprints it; high-speed vessels and afloat forward staging base; named hull empty. Long-term Mine Reconnaissance System: *Oklahoma City* launch as later summary, 2005 primary empty. MQ-9: September initial operational capability empty.

Campaign is the month unmanned access became something a university partnership can launch, a public registrant can disclose, and a high-speed hull can buy — without a federal UAS unit traveling with any of those nodes. Control Fabric is the missing Certificate of Authorization, the S-1 government-rights clause, and Skyhook on a non-carrier hull. Watch refuses a federal disaster fleet, a 30 September listing, a named hull, an *Oklahoma City* A1 launch, and a September MQ-9 gate. Lab is CRASAR as the node that could launch. Kestrel correlates the Pearlington flights with the 30 September filing and the ScanEagle modification, and stops. Sense is the Pearlington camera pair. Move is the hand throw, the PackBot hull, and Skyhook. Act is none on the civil plate.

The honest limit is the source filing's. An independently fetched USF.edu or nsf.gov original would move the Pearlington texts off ScienceDaily reprints. A Certificate of Authorization file would move the air off the empty line. A raw video archive would move the two-hour negative find off a release claim. A DefenseLink daily for N00019-05-C-0045 would move the $13 million / $13.9 million split and the named hull. A 2005 Navy or Boeing trial report would move *Oklahoma City* off encyclopedic repetition. A September MQ-9 gate notice would move the hunter-killer off contrast. Until those dispositions exist, "not established" is a gap. It is not a finding that the gap is safe.

## 8. Conclusion

September 2005 is misread when it is remembered as a month of firsts. A University of South Florida center launched a hand-thrown four-foot aircraft and a Like90 T-Rex over Pearlington from a road patch and claimed the first known small-UAV disaster use, while FAA authorization and a federal unit remained empty. iRobot filed Amendment No. 2 to Form S-1 on the 30th, putting PackBot economics, a China consumer plant, and a government right to disclose technical data on the public tape, while the priced offering remained ahead. Boeing later recited a September ScanEagle modification for high-speed vessels and an afloat forward staging base, while the named hull remained unfetched and the dollar sat at $13 million in one sentence and $13.9 million in another. Later summaries placed a Long-term Mine Reconnaissance System launch on USS *Oklahoma City*; no 2005 primary was fetched. MQ-9 still had no initial operational capability.

The trust failure is launch plus title. Unmanned Sense can now be flown over a U.S. disaster town without a federal UAS unit. Unmanned ground Move can now be registered as a public-company product whose data the government may shop and whose consumer twin depends on a single Chinese plant. Unmanned maritime Sense can now be bought for a high-speed hull without a carrier deck. Unmanned undersea Move can now be repeated as a September launch without a September primary. The airframes are what a photograph would show. The node is what a Passport would have to record.

LrrK's job on a month like this is not to reprint five signals. It is to name the property object and leave the empty lines empty. A Passport that recorded Pearlington as a federal disaster UAS, the S-1 as a priced listing, ScanEagle as a named-hull first flight, the Long-term Mine Reconnaissance System item as an A1 launch, or MQ-9 as initial operational capability, would have certified the wrong artifact. A Watch desk that converted a 2015 type name into a 7 September fact, or DID's *Joint Venture* inference into a September hull, would have certified the wrong event. The durable record is narrower: unmanned access became a node that is not the service in September 2005, the launch did not travel with a federal unit, and the gaps around authorization, hull, tube, and hunter-killer gate are not safe defaults.

Endnotes

1. University of South Florida, "USF Deploys Unmanned Aerial Vehicles To Katrina Rescue Operation," ScienceDaily, 8 September 2005. https://www.sciencedaily.com/releases/2005/09/050908081119.htm. National Science Foundation, "Small, Unmanned Aircraft Search For Survivors In Katrina Wreckage," ScienceDaily, 15 September 2005. https://www.sciencedaily.com/releases/2005/09/050915003020.htm. iRobot Corporation, Amendment No. 2 to Form S-1, File 333-126907, filed 30 September 2005. https://www.sec.gov/Archives/edgar/data/1159167/000095013505005611/b55709a2sv1za.htm. Boeing, "Boeing ScanEagle UAV Surpasses 10,000 Combat Flight Hours," 28 February 2006. https://boeing.mediaroom.com/2006-02-28-Boeing-ScanEagle-UAV-Surpasses-10-000-Combat-Flight-Hours.

2. University of South Florida via ScienceDaily, 8 September 2005. "First known use of small UAVs for an actual disaster," the two-type description, and the Tampa 7 September dateline are from this item.

3. Ibid. Fixed-wing hand launch and five-car-length landing, Like90 T-Rex, Murphy's ten-minute setup sentence, and the NSF industry/university consortium sentence are from this item.

4. Ibid. Charley / Florida Task Force 3, the LSU Fire Emergency Training Institute New Orleans abort, Stennis tasking, Pearlington road-patch launch, two-hour negative find, and "Katrina was so much worse than Charley" are from this item.

5. Ibid., Bay St. Louis "Sept. 1" and the World Trade Center 2001 ground-robot sentence. Space Daily / United Press International, "USF Deploys Mini Unmanned Search Aircraft After Katrina," phys.org, 12 September 2005. https://phys.org/news/2005-09-usf-deploys-mini-unmanned-aircraft.html. The "returning to Tampa Sept. 6" variant is from this reprint.

6. National Science Foundation via ScienceDaily, 15 September 2005. "One of the first deployments" is from this item. United Press International, "Unmanned planes look for Katrina survivors," phys.org, 15 September 2005. https://phys.org/news/2005-09-unmanned-planes-katrina-survivors.html. "First domestic use of such surveillance vehicles" is from this wire.

7. National Science Foundation via ScienceDaily, 15 September 2005. Murphy's "one-two punch," Safety Security Rescue Research Center naming, USF / Minnesota / industry partnership, and Like90 as partner are from this item.

8. iRobot Corporation, Amendment No. 2 to Form S-1, File 333-126907, 30 September 2005. Cover, registrant address, Angle as chief executive, NASDAQ "IRBT" application, and "no public market currently exists" are from this filing.

9. Ibid., Prospectus Summary. Roomba, Scooba, PackBot, Small Unmanned Ground Vehicle / Future Combat Systems, R-Gator / Deere, 1.2 million Roombas, more than 200 PackBots, and the National Defense Authorization Act of 2001 one-third-by-2015 sentence are from this filing.

10. Ibid., Summary Consolidated Financial Data and Risk Factors. $95.043 million 2004 revenue, 73.8 percent Roomba, 20.1 percent and 47.6 percent federal shares, 35.9 percent of 2004 contract revenue from Future Combat Systems, and PackBot sales depending on Army robot programs are from this filing.

11. Ibid., Risk Factors. Jetta / China / purchase-order, Gem City / single U.S. plant, PackBot export license, government rights to use inventions and disclose technical data, and the Foster-Miller / QinetiQ, Allen-Vanguard, Remotec / Northrop, Lockheed Martin, BAE Systems, and General Dynamics competitor list are from this filing.

12. Boeing, 28 February 2006. The September $13 million high-speed-vessel and afloat-forward-staging-base sentence, the August 2004 Marine and July 2005 Navy deployments as of that release, Holly's suspicious-ship sentence, Skyhook, catapult, and USS *Cleveland* as a past host are from this release.

13. Boeing, "Boeing Receives $14.5 Million Navy Contract For ScanEagle UAVs," 25 April 2005. https://boeing.mediaroom.com/2005-04-25-Boeing-Receives-14.5-Million-Navy-Contract-For-ScanEagle-UAVs. Expeditionary Strike Group and oil-platform purpose and "first deployment aboard a Navy vessel" are from this release, used as family context, not as a September 2005 award.

14. Defense Industry Daily, "UAVs, Blimps, and HSV-2, Oh My!" https://www.defenseindustrydaily.com/uavs-blimps-and-hsv2-oh-my-updated-01239/. The $13.9 million N00019-05-C-0045 paragraph, Pacific-vessel work sentence, September 2006 completion, Naval Air Systems Command as issuer, and the *Joint Venture* inference (not used as a September hull fact) are from this item. The original DefenseLink daily-contracts notice was not independently fetched.

15. Later encyclopedic summaries of AN/BLQ-11 / Long-term Mine Reconnaissance System, including pages seen in search and not treated as primaries, reciting a USS *Oklahoma City* (SSN-723) September 2005 launch. Boeing, "Boeing Achieves First Submerged Unmanned Undersea Vehicle Recovery by a Submarine," 26 November 2007. https://boeing.mediaroom.com/2007-11-26-Boeing-Achieves-First-Submerged-Unmanned-Undersea-Vehicle-Recovery-by-a-Submarine. The 2007 recovery is a later event and does not supply a 2005 *Oklahoma City* primary.

16. GlobalSecurity.org, "MQ-9 Reaper / Predator B" program compilation. https://www.globalsecurity.org/military/systems/aircraft/mq-9-program.htm. February 2001 first flight, June 2003 concept of operations, FY05 system development and demonstration start, and the absence of a September 2005 initial operational capability are from this compilation. The 19 November 2004 data-rights notice is the November 2004 sibling's object and is pointed, not rebuilt.

Selected Bibliography

Boeing. "Boeing Receives $14.5 Million Navy Contract For ScanEagle UAVs." 25 April 2005. https://boeing.mediaroom.com/2005-04-25-Boeing-Receives-14.5-Million-Navy-Contract-For-ScanEagle-UAVs

Boeing. "Boeing ScanEagle UAV Surpasses 10,000 Combat Flight Hours." 28 February 2006. https://boeing.mediaroom.com/2006-02-28-Boeing-ScanEagle-UAV-Surpasses-10-000-Combat-Flight-Hours

Boeing. "Boeing Achieves First Submerged Unmanned Undersea Vehicle Recovery by a Submarine." 26 November 2007. https://boeing.mediaroom.com/2007-11-26-Boeing-Achieves-First-Submerged-Unmanned-Undersea-Vehicle-Recovery-by-a-Submarine

Defense Industry Daily. "UAVs, Blimps, and HSV-2, Oh My!" https://www.defenseindustrydaily.com/uavs-blimps-and-hsv2-oh-my-updated-01239/

GlobalSecurity.org. "MQ-9 Reaper / Predator B." https://www.globalsecurity.org/military/systems/aircraft/mq-9-program.htm

iRobot Corporation. Amendment No. 2 to Form S-1, File 333-126907. Filed 30 September 2005. https://www.sec.gov/Archives/edgar/data/1159167/000095013505005611/b55709a2sv1za.htm

National Science Foundation. "Small, Unmanned Aircraft Search For Survivors In Katrina Wreckage." ScienceDaily, 15 September 2005. https://www.sciencedaily.com/releases/2005/09/050915003020.htm

Space Daily / United Press International. "USF Deploys Mini Unmanned Search Aircraft After Katrina." phys.org, 12 September 2005. https://phys.org/news/2005-09-usf-deploys-mini-unmanned-aircraft.html

United Prest International. "Unmanned planes look for Katrina survivors." phys.org, 15 September 2005. https://phys.org/news/2005-09-unmanned-planes-katrina-survivors.html

University of South Florida. "USF Deploys Unmanned Aerial Vehicles To Katrina Rescue Operation." ScienceDaily, 8 September 2005. https://www.sciencedaily.com/releases/2005/09/050908081119.htm

Source note. This paper distinguishes three September 2005 property events (CRASAR / Safety Security Rescue Research Center Pearlington flights as claimed in the 7–8 September USF/ScienceDaily plate and restated 15 September by NSF; iRobot Amendment No. 2 to Form S-1 filed 30 September; ScanEagle high-speed-vessel and afloat-forward-staging-base modification as recited 28 February 2006 and as reprinted by Defense Industry Daily) from the Long-term Mine Reconnaissance System *Oklahoma City* launch and MQ-9 non-IOC as contrasts. It treats the February 2006 Boeing release and the Defense Industry Daily reprint as later or secondary sources for a September award and labels them as such. It treats the April 2005 $14.5 million Expeditionary Strike Group award as established public context for the ScanEagle family, not as a September 2005 award. It treats UPI's "first domestic use" as a wire hardening of the NSF/USF claim, not as independent adjudication. It refuses a 2015 AeroVironment Raven identification as a September type, later "Predator flew Katrina" tertiary lines, DID's HSVX-1 *Joint Venture* hull inference, a priced 9 November initial public offering as a September fact, and any encyclopedic LMRS launch as A1. Independent USF.edu and nsf.gov originals, FAA Certificate of Authorization text, raw Pearlington video, the DefenseLink daily-contracts notice for N00019-05-C-0045, a named high-speed hull, a 2005 Navy or Boeing LMRS trial report, and any September MQ-9 gate notice were not fetched and are left empty. Sibling papers on October 2001 Hellfire clearance, November 2004 unmanned access as title, June 2007 Fire Scout and HUGIN, April 2008 orbit as not airspace, January 2009 inherited covert command and control, January 2010 Haiti/FOIA, July 2010 Stuxnet Passport, and May 2011 Shabwa are one-line pointers only and are not rebuilt. The temporal frame is the September 2005 collection cutoff (30 September). The analysis should be revalidated against any independently fetched USF or NSF original, any Certificate of Authorization file, any raw video archive, any DefenseLink daily for the ScanEagle modification, any named-hull pairing, any 2005 LMRS trial report, and any September MQ-9 gate notice.