Summary

  • Late-1990s records place Tom Sherwood inside an Aerotech team working on difficult aerospace-load research, while a later motor application names him among several inventors. That work establishes technical participation, not sole ownership of the research or its results.
  • KalScott Engineering, founded in 2002, used federally funded projects to move across marine communications, high-altitude uncrewed aircraft, an artificial-intelligence procurement tool and autonomous airfield vehicles. The pivots look less random when read as repeated systems-integration work inside one small research, development, test and evaluation company.
  • Sherwood's documented role changes from project to project. Some award records identify him as Principal Investigator; others identify him only as Business Contact while naming Brian Schaal or Suman Saripalli as Principal Investigator. Those distinctions are essential to a fair account of individual and company performance.
  • In 2020, KalScott, Sherwood and Saripalli paid $672,352 to settle federal false-claims allegations involving SBIR and STTR funds. The Justice Department expressly said the resolved claims were allegations and that there was no determination of liability. Later awards show institutional continuation, but they do not erase the settlement or turn the allegations into an adjudicated finding.

The line is continuity, not chronology

The easiest way to tell Tom Sherwood's story would be to arrange a list of projects by date. First aerospace loads, then an electromechanical invention, then shipboard communications, a high-altitude aircraft, an artificial-intelligence tool and autonomous vehicles. That list would be accurate at a superficial level and misleading at a deeper one. It would make technical change look like restlessness, and it would make Sherwood appear to own every project that passed through companies with which he was associated.

A more useful reading begins with the kind of work that persists when the product changes. The 1999 FAA record credits Sherwood on research into antisymmetric buffet loads on horizontal stabilizers in massively separated flows. An ICAS paper from the same research era identifies him as an R&D engineer at Aerotech Engineering and Research Corporation. The subject is highly specific, but the operating discipline is portable: measure a difficult physical environment, model what cannot be treated as a simple steady condition, connect the model to test evidence and produce something useful to an aviation customer.

The later KalScott projects change the environment while retaining parts of that discipline. A marine communications system has to work amid motion and interference. A high-altitude uncrewed aircraft has to join aerodynamics, sensing and control into a credible system. An autonomous airfield vehicle has to move beyond a laboratory concept into sustained operation around real aviation activity. None of those projects is the same technology. All require a small engineering organisation to integrate components, test against a demanding setting and explain progress to a public customer.

That is technical continuity, but it is not proof of an unbroken personal plan. The available record does not establish when Sherwood left Aerotech, whether his work there overlapped with KalScott's beginning or exactly how the new company's first opportunities were chosen. It does not reveal his private motives. It supports a narrower and stronger claim: the documented engineering work before KalScott helps explain why a small Kansas company could credibly pursue difficult research and development across several applied domains.

The funding mechanism is the other continuous line. KalScott's own company profile describes an RDT&E focus across aerospace, defence and remote sensing and dates the company's inception to 2002. Award records then show a long reliance on the Small Business Innovation Research program. The program entries do not describe one stable product business. They show a company repeatedly attaching its engineering capacity to a government-defined problem and trying to advance far enough to justify another phase, a related project or a new use.

That model can preserve a technical organisation through changing markets. It can also concentrate risk. Each funded pivot carries project-specific representations, cost treatment, performance claims and role assignments into a formal relationship with a public institution. When the same company depends on that mechanism over many years, compliance is not an administrative detail beside the engineering. It is part of the system that allows the engineering to continue.

Sherwood's record matters because it contains both sides of that operating model. There is documented technical work, repeated company adaptation and a return to Principal Investigator status on later autonomous-vehicle awards. There is also a federal settlement that must be described with exact restraint. Reading one side without the other would produce either a grant-success story or a legal morality play. The evidence supports neither. It supports an account of how continuity is built, divided among people and made answerable to the conditions of public funding.

Aerotech and the discipline of bounded credit

The Aerotech period supplies the strongest early evidence of Sherwood as an engineer rather than merely a company officer. The FAA record is not a biography. It identifies a technical report, its institutional contributors and its research subject. That narrowness is useful. It places Sherwood in a defined body of work without asking the record to prove employment dates, management authority or sole authorship that it does not contain.

The research concerned the prediction of buffet loads on horizontal stabilizers under massively separated flow. Even at the level supported by the title and institutional record, the problem says something about the kind of engineering involved. Separated flow does not offer the simplicity of a smooth, steady aerodynamic condition. Buffet loads are dynamic, and a horizontal stabilizer must be considered as a structure exposed to changing forces. Prediction therefore sits between physical observation and practical design: the analysis has to represent a difficult environment well enough to inform how an aircraft component is understood.

Sherwood's credited participation belongs to an Aerotech, University of Kansas and FAA context. The ICAS record supports the R&D engineer title for that era. It does not make him the only researcher, the sole designer of the tests or the owner of the resulting method. Keeping the team visible is not a ceremonial qualification. It is the first demonstration of how this career has to be written. Complex engineering reaches the public through organisations and collaborations, even when one person's name provides the route into the story.

A separate invention record broadens the picture. The application for a bidirectional linear motor lists Sherwood among the inventors and Aerotech as the original assignee. It was filed on 5 December 2001 and published on 5 June 2003. A second patent record confirms the application metadata and identifies Sherwood as one of the inventors associated with Aerotech. The device is described in the fixed record as a bidirectional magnetostrictive linear motor, adding electromechanical actuation to the aerodynamic research already visible in his work.

The status matters as much as the technical subject. The application was abandoned. It should not be described as a granted patent, a protected commercial platform or proof that a product reached a customer. An application can demonstrate participation in a defined inventive effort while saying little about adoption, revenue or operational impact. Here it shows that Sherwood's Aerotech-era work was not confined to one report topic. It also shows again that he worked with other inventors inside a corporate assignee structure.

These two records together establish a credible technical base, but they do not provide a complete career bridge. The report belongs to 1999, the application was filed in late 2001 and KalScott says it began in 2002. Those dates place the activities close together. They do not establish the day or terms of a departure, whether Sherwood moved directly from one firm to the other or how responsibilities were divided during the transition. A neat sentence claiming that he "left Aerotech to found KalScott" would go beyond the available evidence.

The missing transition is not a defect that needs to be filled with inference. It is an important boundary. People profiles often turn adjacent dates into causal stories because chronology feels explanatory. In this case, the safer account is also more revealing: documented Aerotech technical participation precedes the public KalScott record, and the capabilities visible in the former are relevant to the latter. The exact personal move remains unknown.

That distinction prevents the Aerotech work from becoming an origin myth. KalScott was not simply one engineer's prior knowledge in corporate form. Its later work repeatedly includes Suman Saripalli, and individual project records name other investigators. The technical starting point gives Sherwood substance as a subject, but it does not make every later company capability an extension of his mind. Bounded credit at the beginning creates the standard that must hold throughout the rest of the story.

Moving into a small-company operating model

KalScott's public profile says the company began in 2002 and is based in Lawrence, Kansas. A 2014 local account identifies Sherwood and Suman Saripalli as co-owners and principals at that time. A commercial federal-award profile places founding and federal registration in 2002. The company account and local reporting are enough to establish the durable outline: KalScott was a small Kansas R&D business built to work across government technical problems.

KalScott's own contact page adds a narrower continuity signal: the Lawrence address, company domain and public Sherwood email link the SBIR records to the operating company. It does not state title or ownership, so it should not replace the dated local reporting or federal records. Its value is evidentiary hygiene, not a new claim about office.

A commercial SBIR database profile for KalScott Engineering also places the firm inside the small-business research-funding ecosystem and lists Sherwood among key people. Because it is a market database rather than the awarding agency, it should remain secondary context. It supports the scale and continuity of the SBIR footprint only where primary award pages and company material already make the pattern visible.

The organisational choice matters more than the founding label. A specialist research company does not need to wait for one large commercial market if it can assemble projects around public missions. It can keep engineers close to emerging problems, use funded phases to test whether an approach deserves more development and carry tools or knowledge from one domain into another. The company becomes less a seller of one finished entity than a platform for solving a sequence of bounded technical tasks.

That platform has limits. Project funding arrives with a defined customer, purpose, period and set of representations. A company that moves often must repeatedly explain what is new, what prior work contributes, who is responsible and what the requested funds will support. The ability to pivot is therefore inseparable from the ability to maintain distinctions. Reusing engineering knowledge can be efficient; blurring the boundaries among projects, roles or costs can be dangerous.

The public record does not expose KalScott's internal staffing, accounting, decision rights or revenue mix. It cannot show whether the founders thought of the company in these terms. What it does show is a pattern consistent with this operating model: Navy work on communications, NASA work on a high-altitude aircraft, Air Force work on an artificial-intelligence procurement tool and later Air Force work on autonomous ground vehicles. The company profile adds broader aerospace, defence and remote-sensing categories, but the individual award and news records provide the firmer anchors.

Sherwood's titles also change with the context. The 2014 account calls him a co-owner and principal. The Justice Department's 2020 announcement identifies him as president. Recent award pages identify him as either Principal Investigator or Business Contact, depending on the project. None of those date-bound descriptions should be silently converted into a claim about his current ownership or office. They show sustained association and varying responsibility, not an eternal title.

This is the central organisational shift from Aerotech. The earlier evidence shows Sherwood contributing inside an established aerospace research corporation. The KalScott evidence places him among the principals of a much smaller firm whose continuity depended on securing and executing distinct pieces of public R&D. Technical participation was now joined to company-level obligations. That combination makes the later record more consequential than a sequence of engineering topics alone.

SBIR was the business engine, not a trophy shelf

The Small Business Innovation Research awards in KalScott's record are often described through phase, dollar amount and agency. Those details matter, but a list of them would miss what the program did for the company. It offered a recurring structure for moving from an identified public problem toward a technical response. The specific problem could change while the organisation retained people, integration habits and the capacity to operate in government research settings.

An early visible example is the Navy topic "Wi-Fi From the Sea". The project addressed shipboard wireless communications using directional, stabilised antennas in a high-interference marine environment. The page names KalScott and lists Tom Sherwood as the firm contact. A later 2008 Phase II award page records $750,000 and a target of testing in a live, real environment.

The word "contact" is not a licence to call Sherwood the inventor or technical lead. The 2008 entry names Brian Schaal as Principal Investigator and Sherwood as Business Contact. That division is one of the most important facts in the entire record. Sherwood was visibly connected to the company's federal business, but the project page assigns the investigator role to someone else. A responsible profile has to preserve Schaal's place rather than letting the better-known company principal absorb it.

The distinction also reveals how a small R&D company functions. Technical work has to be proposed, contracted, administered and connected to a customer as well as designed and tested. A Business Contact can be consequential without being the Principal Investigator. Conversely, a Principal Investigator's named responsibility does not prove that the person alone performed every engineering task. The public fields are useful role boundaries, not a complete map of labour.

KalScott's 2006 Tibbetts Award confirms that its use of the program had become publicly notable. The local report says Sherwood and Saripalli were scheduled to receive the company award in Washington. The honour belongs to KalScott, and the planned receipt was shared. It can demonstrate early institutional recognition without being turned into an individual lifetime achievement.

The award also marks a temptation that the later history resists. Once a company has received public recognition for innovation, every subsequent grant can be arranged as another proof of ascent. KalScott's record is more complicated. The technical domains shift. Named responsibility moves among people. One public funding relationship later becomes part of a settlement. The same mechanism that supports experimentation also creates an accumulating compliance surface.

That surface grows because each project has at least two stories. One is technical: what problem is being addressed, what is being built and what the next phase is intended to demonstrate. The other is institutional: what entity received the funds, who held the recorded roles and what conditions governed the work. The first story is more exciting. The second determines whether public financing remains legitimate.

Sherwood appears on both sides. His early Aerotech work and later Principal Investigator entries support genuine technical standing. His Business Contact entries and company titles support an operating role around the funded enterprise. Those categories must not be collapsed, but their coexistence helps explain why he is a meaningful person to profile. He was not merely adjacent to KalScott's projects, and he was not the sole author of them. He occupied different positions inside a company whose main instrument of continuity was federally supported R&D.

Pivots that preserved a company, not one product

By 2014, KalScott had moved from the marine communications work visible in the Navy record to a NASA-backed high-altitude uncrewed aircraft project. The Lawrence Journal-World account described the project as worth approximately $1 million and identified Sherwood and Saripalli as co-owners and principals. The quoted explanation came from Saripalli, not Sherwood, which limits how the project can be used in a person profile.

The company result is still relevant. A high-altitude aircraft project fits KalScott's aerospace identity while demanding a different combination of work from shipboard wireless communication. The pivot did not discard all prior capability. It shifted the system boundary. Communications, sensing, control and vehicle integration can meet in an uncrewed aircraft even though the customer, platform and operating environment differ.

Two years later, local reporting described an Air Force decision to provide another $750,000 for SOPHIA, an artificial-intelligence procurement-assistant project. Again, Saripalli supplied the quoted voice, while Sherwood was named as co-owner and placed in the context of earlier company selections. The evidence supports a KalScott result and Sherwood's company role. It does not support describing him as SOPHIA's sole designer, investigator or executive sponsor.

This pivot is the sharpest test of the continuity thesis. A procurement-assistant tool is less obviously connected to wind-tunnel loads, marine antennas or an uncrewed aircraft than those physical systems are to one another. If continuity meant one technology, the sequence would break here. If it meant a small R&D organisation able to frame a government problem, assemble a response and move through a funded development process, the sequence remains coherent.

That coherence is organisational rather than magical. Nothing in the record proves that the same algorithm, component or engineering method moved from one project into the next. It would be improper to invent a common technical architecture. The continuity lies at a higher and more defensible level: KalScott repeatedly worked as a prime R&D contractor across aerospace, defence and related applied problems, and Sherwood remained associated with the company as its portfolio changed.

The distinction protects against two opposite errors. One is to call the pivots random, as if a small research company were changing identity every time a solicitation changed. The other is to claim a hidden master technology linking every award. The public evidence supports a middle position. KalScott preserved an operating capacity for systems-oriented research while changing the immediate entity of that research.

This is where small-company adaptation differs from the familiar story of a venture-backed product pivot. There is no evidence here of a consumer product failing and a founder discovering a new market. The visible sequence is customer- and mission-led. Public institutions define problems; the company competes for work; funded phases create opportunities to advance an approach. Survival depends not only on market persuasion but on the capacity to satisfy technical and administrative conditions attached to public money.

The model can produce durable expertise because difficult projects force an organisation to learn how to integrate, test and report. It can also make continuity fragile. If funding is delayed, a later phase does not arrive or compliance fails, the organisation cannot rely on recurring sales of one established product to carry it. Its technical future remains closely connected to its standing as a trustworthy entity in public programs.

Airfield autonomy makes the continuity visible

The autonomous-ground-vehicle awards from 2021 onward provide the clearest evidence of Sherwood moving from company principal to named technical responsibility. They also show why a project sequence has to be read carefully. The same broad vehicle effort appears across several records, but the Principal Investigator changes and later claims belong to the company and program, not automatically to Sherwood.

The 2021 Phase I entry concerns an autonomous electric ground vehicle for depot and flightline sustainment. It names Tom Sherwood as Principal Investigator and records an award of $49,441. At this point, the person-level claim is strong and bounded: Sherwood held the recorded investigator role on an early Air Force project aimed at improving maintenance-support activity around an airfield.

The amount is small beside the later awards, which helps reveal the staged character of the sequence. The record does not prove that Sherwood personally originated every idea or performed every test. It does show that the company placed him in the named investigator position at the initial phase. For a profile that begins with late-1990s aerospace research, the return to a defined technical role in aviation-related ground operations is significant.

A separate 2021 Phase II entry records $1,498,313 for an autonomous electric vehicle for airfield ground operations. This time Suman Saripalli is Principal Investigator and Sherwood is Business Contact. The purpose includes long-term demonstration of the autonomous electric ground vehicle. The larger amount and demonstration language indicate organisational progression, but the investigator credit belongs to Saripalli.

That change is not a minor metadata detail. It may reflect a change in technical leadership, proposal structure or administrative assignment, but the public page does not explain why. The only defensible account is the recorded one. Sherwood's Phase I investigator role cannot be carried forward by assumption. Saripalli must remain visible as the named investigator for Phase II, while Sherwood's Business Contact role keeps him connected to the company's side of the award.

The 2024 Phase II/TACFI record continues that assignment. It lists Saripalli as Principal Investigator and Sherwood as Business Contact on a $1,899,955 award for autonomous ground vehicles for airfield support. The page says the prior Phase II developed, demonstrated and delivered two autonomous ground vehicles. That is a substantial company result supported by the award entry. It is not a solo Sherwood result.

The delivery statement gives the continuity more substance than a series of selections. A concept had advanced into two vehicles that were developed, demonstrated and delivered. Even so, the record does not disclose their detailed performance, adoption beyond the stated work or long-term operational outcome. "Delivered" is a meaningful milestone, not a synonym for broad deployment or commercial success.

In 2025, a further Phase II award names Sherwood as Principal Investigator again. The $1,249,622 project is intended to expand the Wolverine vehicle into multipurpose airfield-support roles, and the listed end date is 17 March 2027. That future date imposes a firm limit. The award establishes funding, scope and named responsibility. It does not establish results that would occur after the evidence date.

The movement among these entries is more informative than any single award. Sherwood is Principal Investigator at the early 2021 stage, Business Contact while Saripalli leads the 2021 and 2024 Phase II records, then Principal Investigator on the 2025 expansion. The pattern resists a simple hierarchy in which one founder always leads and everyone else executes. It shows role allocation changing within a durable collaboration.

It also reveals how technical continuity can belong to an organisation while person-level responsibility remains episodic. KalScott carried the autonomous-airfield line across phases, demonstrations, delivery and a new multipurpose objective. Sherwood's documented participation is substantial at the beginning and again on the later project. Saripalli's investigator role is central in the middle. The company joins the episodes; the named fields divide credit and accountability within them.

The airfield setting ties the newer work back to the earlier career without proving that one technology descended directly from another. Sherwood's Aerotech record concerned aviation loads and actuation. The later work concerns autonomous electric vehicles supporting flightline and airfield operations. Both sit near aviation systems and difficult physical environments, but the intervening decades include marine communications, uncrewed aircraft and artificial intelligence. The continuity is an accumulated ability to move research toward testable systems, not a single invention surviving unchanged.

This sequence also shows what public R&D can do well. A small company can begin with a modest exploratory award, advance into a much larger demonstration effort, deliver physical systems and propose an expanded use. Public customers can support technical learning that might be difficult to finance through ordinary product sales. The record does not tell us whether every phase met every objective, but it does show a path from initial study to delivered vehicles and a subsequent expansion.

The same sequence shows why record discipline matters. Names, roles, amounts, dates and claims change from one entry to another. A profile that compresses them into "Sherwood won millions for his autonomous vehicle" would be wrong in several ways. The recipient was KalScott. Saripalli led two major entries. The amounts belonged to specific funded work. The 2025 effort was still ongoing. Accurate attribution is not an editorial courtesy added after the engineering story; it is part of understanding how federally funded engineering actually operates.

The settlement and its exact legal boundary

The most serious event in the public record arrived before the autonomous-airfield sequence. In 2020, the United States Attorney's Office for the District of Kansas announced that KalScott Engineering, company president Thomas Sherwood and vice president Suman Saripalli paid $672,352 to settle false-claims allegations. The allegations concerned SBIR and STTR grant funds from NASA, the Navy, the Air Force and the National Institutes of Health.

The same announcement supplies the boundary that every account must keep attached to those facts: the resolved claims were allegations only, and there was no determination of liability. A settlement is not a judicial finding that the allegations were proved. The record does not support calling Sherwood or Saripalli criminal, describing an admission that is not documented or treating the payment as a verdict.

Precision does not require minimising the event. The company and its two named officers made a substantial payment to resolve allegations connected to the public funding mechanism on which much of KalScott's visible work depended. That is a material operating and reputational fact. It belongs in a profile about how SBIR-supported continuity was built because it demonstrates that the funding relationship carried consequences beyond whether a device worked.

The available evidence does not provide enough detail to reconstruct the underlying conduct. It should not be expanded with assumptions about particular invoices, hours, costs, certifications or projects. Nor can the settlement be used to declare that every KalScott award was tainted. The announcement identifies involved funding programs and agencies at a high level. It does not authorise a person profile to invent a broader pattern.

This creates a difficult but necessary dual statement. The settlement did not determine liability, and it cannot be written as proof of wrongdoing. It also did occur, involved the company and its named leaders and resolved federal allegations for $672,352. Omitting it would make KalScott's long reliance on public R&D look administratively frictionless. Overstating it would replace the legal record with a harsher conclusion that the government announcement expressly does not make.

The event matters analytically because SBIR funding performed two functions in KalScott's history. It financed technical movement across domains, and it placed that movement inside rules enforceable by the federal government. Innovation policy often presents small-business awards as bridges between ideas and deployment. The settlement is a reminder that the bridge also has guardrails: a recipient's relationship with public money is governed by more than technical promise.

For a company principal, that expands the meaning of operational responsibility. Engineering leaders in a small firm may work close to proposals, customer relations, staffing and project execution. The public record does not show KalScott's internal allocation of those duties, so it cannot assign a specific compliance act to Sherwood beyond the settlement announcement. It does show that his role was not confined to detached technical contribution. He was identified as company president in the federal matter and appears across award records in both investigator and business capacities.

The distinction between allegation and liability must therefore remain visible without making the settlement irrelevant. Legal restraint and organisational accountability are compatible. The first prevents claims beyond what was determined. The second asks what the existence of the settlement reveals about the risks carried by a small R&D company and its leaders.

Continuation after 2020 is not absolution

The chronology after the settlement is notable. The autonomous-vehicle records begin in 2021, continue through a 2024 award and extend into the 2025 project scheduled to run until 2027. KalScott plainly continued to participate in federally supported research after the 2020 announcement. Sherwood returned as a named Principal Investigator in 2021 and 2025, while appearing as Business Contact on the intervening awards.

Those later awards establish continuation. They do not establish that the settlement was insignificant, that every compliance issue was cured or that the government issued a general endorsement of past conduct. An award is authority for a particular funded project. It should not be treated as retrospective exoneration. By the same logic, the earlier allegations do not prove that the later work failed or was improperly awarded.

Holding both points at once is essential to a fair reputation account. Public narratives tend to force adverse legal events into one of two forms. One treats the event as the hidden truth that explains everything before and after it. The other treats later business activity as evidence that the event no longer matters. Neither approach fits this record. The settlement remains a material fact with no liability determination, and the later awards remain real project commitments with their own role assignments and limits.

The continuation does indicate institutional resilience. KalScott retained enough technical and administrative capacity to appear in successive Air Force award records, move an autonomous vehicle from an early phase toward demonstration and delivery, and pursue a broader airfield-support role. That achievement belongs to the company team. The evidence does not disclose the internal changes, controls or customer judgments that made continuation possible.

It would be tempting to fill that gap with a redemption story. One could imagine leaders confronting a failure, reforming processes and earning renewed trust. The public record provided here does not establish any of those steps. There is no documented account of remediation, changed governance or personal reflection. A publishable profile should not invent moral development where only institutional continuation is visible.

What can be said is more restrained. A small R&D company survived a serious federal settlement and continued to receive awards. Its later program entries preserved explicit distinctions between Sherwood and Saripalli as investigators and business contacts. The autonomous-ground-vehicle work produced a recorded company milestone in the development, demonstration and delivery of two vehicles. A later award put Sherwood back in the investigator role on an ongoing expansion.

Continuation also increases rather than reduces the importance of compliance. If the company had left federal R&D entirely, the settlement might mark the end of the funding model. By remaining inside that model, KalScott continued to depend on accurate representations and disciplined boundaries around public projects. The engineering opportunity and the administrative exposure remained joined.

This is why the article's subject is not scandal followed by recovery. It is a durable operating system tested by an adverse event. SBIR-supported pivots allowed KalScott to carry technical capacity from one problem to another. The 2020 settlement demonstrated that the same system could create concentrated legal and reputational risk. The post-2020 awards show that the system continued, not that either side of it disappeared.

Compliance is part of the technical system

Technical companies often describe compliance as overhead: necessary documentation and controls that sit outside the inventive work. KalScott's record suggests a more integrated view. In a small firm whose visible projects are repeatedly financed by public research programs, compliance is one of the mechanisms that converts engineering capacity into authorised work.

The award pages illustrate why. Each identifies a recipient, phase, amount, topic and named roles. Those fields establish boundaries around who is being funded to do what under a particular project. They also prevent a later narrator from merging several awards into one pool of money or one person's achievement. The public record is not the whole contract, but its structure reflects the importance of keeping projects distinct.

Technical continuity creates legitimate reasons to reuse knowledge. Engineers do not begin every project with empty hands. Experience with sensing, actuation, communications, autonomy, testing and federal customers can make a new proposal more credible and execution more efficient. A company may carry tools, habits and people forward. That is precisely how public R&D can accumulate value beyond one award.

The compliance challenge is to preserve that learning without confusing what each award supports. The record does not show how KalScott handled those internal boundaries, and the settlement announcement does not provide enough detail to describe a specific failure. The broader operating risk is nonetheless clear. When public funds support several efforts across agencies and years, technical overlap can coexist with separate legal obligations. Continuity has to be documented as carefully as it is engineered.

Role attribution is part of the same discipline. Calling Sherwood Principal Investigator on the marine Phase II work would erase Brian Schaal. Carrying Sherwood's 2021 Phase I title into the 2021 or 2024 Phase II entries would erase Saripalli. Assigning the 2024 delivery of two vehicles to Sherwood alone would convert a company result into a personal one. These would be writing errors, but they mirror the kind of boundary failure that a research organisation must avoid in its own records.

The amounts also require context. $49,441, $750,000, $1,498,313, $1,899,955 and $1,249,622 are not prizes added to a founder's score. They are award amounts tied to defined work. They do not equal profit, personal compensation or enterprise value. Presenting them as a cumulative personal haul would misunderstand both public funding and corporate attribution.

Likewise, technical milestones need precise verbs. The 2024 page says two autonomous ground vehicles were developed, demonstrated and delivered under the prior Phase II. It does not say they became standard equipment across the Air Force. The 2025 page says the Wolverine vehicle project aims to expand into multipurpose support roles and remains scheduled through March 2027. It does not establish that the expansion has succeeded. Compliance with evidence begins by preserving those tense and scope boundaries.

Sherwood's early Aerotech record offers an instructive parallel. A research report credits him as a contributor; an application names him among inventors; neither gives him ownership of the whole institutional result. The same bounded method applies at KalScott. Continuity becomes more credible, not less, when the surrounding team remains visible.

For leaders of small technical firms, this integrated view has practical force. The person who can discuss the engineering but not the funding obligations understands only half the enterprise. The person who can administer an award but cannot distinguish technical responsibility from corporate visibility also creates risk. Sherwood's varying recorded roles place him near both halves, even though the evidence does not reveal his day-to-day duties.

The settlement makes the integration impossible to ignore. It does not establish liability, but it records the federal government's willingness to pursue and resolve allegations involving the funding programs central to the company's history. It turns compliance from an abstract best practice into a concrete part of KalScott's public record.

The person visible inside the organisation

What, then, can the record establish about Tom Sherwood himself? First, he had documented technical standing before KalScott. The FAA and ICAS materials place him in a demanding aerospace research setting, and the motor application places him among inventors on an Aerotech-assigned electromechanical concept. These are stronger anchors than a general executive biography because they connect his name to defined work.

Second, he moved into a durable operating role at KalScott. Local reporting identifies him with Saripalli as co-owner and principal in 2014. The federal settlement identifies him as president in 2020. Award pages continue to list him in project-facing roles through 2025. The dates matter. They support continuity of association without proving his title or ownership today.

Third, his role cannot be summarised with one label. On the marine Phase II award he is Business Contact while Schaal is Principal Investigator. On the 2021 and 2024 airfield Phase II records he is Business Contact while Saripalli is Principal Investigator. On the 2021 Phase I and 2025 Phase II entries he is Principal Investigator. That variation is not noise. It is the clearest public evidence of how his responsibility changed across the company's work.

Fourth, the company results should remain company results. The Tibbetts Award, NASA selection, SOPHIA funding and delivery of two autonomous vehicles all belong to KalScott and the teams attached to the relevant efforts. Sherwood's ownership, leadership or project role makes them pertinent to his profile, but not personally exclusive. Saripalli's quoted and investigator roles, and Schaal's earlier investigator role, are necessary parts of the account.

Fifth, the legal event must remain both present and bounded. Sherwood was named in the $672,352 settlement, and that fact bears directly on an article about operating a federally funded R&D company. The claims were allegations only, with no determination of liability. The profile can recognise a reputational and organisational burden without inventing a judgment.

The evidence does not supply personality traits, private conversations or a statement of personal philosophy. It does not say Sherwood saw every pivot as part of one plan. It does not show how he responded internally to the settlement or what controls changed afterward. Leaving those spaces empty is part of writing a credible person profile. Character emerges here through observable positions and decisions, not imagined thought.

One decision is visible in the sustained company model itself. Sherwood remained associated with a firm that repeatedly pursued public R&D across changing domains. Another is visible in his return to named investigator responsibility on the autonomous-vehicle work. These are institutional decisions inferred from formal roles, not claims about motive. Their results can be evaluated only to the extent the public record allows.

The result is neither a hero nor a cautionary symbol. Sherwood appears as an engineer-operator whose career moved from collaborative aerospace research into the leadership and project structure of a small dual-use R&D company. The company used federal programs to preserve technical capacity across pivots. That capacity produced awards, demonstrations and delivered vehicles. It also carried compliance exposure that became public in a settlement.

A durable company has to preserve more than technology

Technical continuity is often described as an intellectual achievement: an idea survives a change of product, market or institution. KalScott's history shows that a small company has to preserve several other things at the same time. It needs people who can move among problems, role definitions that keep credit and responsibility intelligible, customer confidence that supports another phase and administrative discipline that keeps public funding usable.

Sherwood's Aerotech work supplies the technical beginning of this account, but not a proprietary seed from which every later result automatically grew. The KalScott record supplies continuity, but not a solo-founder narrative. The autonomous vehicle sequence supplies measurable progress, but not proof of broad adoption. The settlement supplies a serious adverse fact, but not a determination of liability.

Those limits are not obstacles to a strong conclusion. They are the conclusion. A long-lived R&D organisation is built by maintaining boundaries while carrying knowledge across them. It has to know what can be reused and what remains project-specific, who leads and who supports, what has been delivered and what is still proposed, what an allegation means and what it does not.

For Sherwood, the public record shows repeated proximity to those boundaries. He contributed to Aerotech research, joined the inventive group on a motor application, became a KalScott principal and president, represented the company on awards and served as investigator on selected projects. His name crosses technical and corporate roles. The evidence never makes those roles unlimited.

For KalScott, SBIR-funded pivots created a form of institutional endurance. The firm could move from sea-based communications to aircraft, software and airfield autonomy while retaining an identity as a small research and engineering contractor. The strongest later evidence is not another selection but a sequence that reached developed, demonstrated and delivered vehicles before seeking a wider use.

The same funding engine also carried a compliance burden that cannot be separated from the technical story. The 2020 settlement did not determine liability, yet it made the cost of contested compliance public. Later awards show that the company continued. They do not rewrite the earlier event, and the earlier event does not invalidate later work.

That balanced record is why Sherwood is worth examining. His career does not offer a simple lesson that adaptability guarantees success or that a settlement defines a person. It shows something more useful for technology companies that live on difficult public problems: continuity is manufactured through repeated, bounded commitments. Engineering can move across domains, but trust has to move with it. When public funding is the bridge, compliance is part of the load the bridge must carry.