Aero Turbine and Gallant: Our Private Equity Owner Helped Handle Defense Data

Private equity defense contractor false claims can involve the owner’s own employees: Aero Turbine and Gallant Capital Partners agreed to a $1.75 million civil settlement over alleged failures to protect Air Force data. The government alleged that a Gallant employee helping the contractor improve its software gave controlled defense information to unauthorized personnel in Egypt. If you work in IT, engineering or compliance, that allegation may sound familiar: an owner’s employee helping with a contractor’s system.

The Air Force Bought Engine Repairs With Security Attached

Aero Turbine repaired and maintained General Electric J85 turbojet engines under the Air Force’s Management of Items Subject to Repair contract, which also required protection of defense information. Aero Turbine supported that work with its Aero Turbine Online Management System, known as ATOMS, which held controlled unclassified information for the contract. The settlement agreement describes the security promise: the contract’s safeguarding clause required implementation of NIST SP 800-171 security requirements by December 31, 2017.

That is the connection to defense cybersecurity fraud. The government alleged that Aero Turbine knowingly submitted or caused false claims for payment under the engine contract while the required protections were missing. An employee who understood ATOMS could see a part of contract performance that the engine repair itself would never show.

The Alleged Failures Began Before Gallant’s Ownership

The alleged control failures began before Gallant’s investment funds took their controlling stake. The government’s allegations cover January 1, 2018, through February 29, 2020. Gallant, through funds for which it acted as adviser, held a controlling stake from January 2019 to August 2024.

The alleged transfer to unauthorized personnel occurred in June and July 2019, during Gallant’s ownership. The government’s account puts the owner’s employee in the data transfer, not just the owner on the investment papers.

ATOMS Had an Assumption Where Verification Belonged

The government alleged that Aero Turbine had not fully implemented the required cybersecurity controls for ATOMS. It also alleged that, before disclosing the problem, the contractor had assumed its export controls for technical data satisfied the contract’s cybersecurity obligations. According to the agreement’s account of the allegations, neither Aero Turbine nor Gallant had verified whether ATOMS met the specific NIST controls.

We find that alleged substitution telling. Protecting technical data under one set of rules became the assumed answer to a separate promise about the system holding it. The missing work was the verification that would have tested the assumption.

The alleged unauthorized foreign access makes the problem concrete. According to the government’s allegations, a software company with personnel in Egypt was engaged to improve ATOMS. A Gallant employee assisting Aero Turbine allegedly provided those personnel with ATOMS data containing controlled unclassified information, even though the software company and its personnel were not authorized to receive it under the contract.

For someone involved in that work, the useful comparison is between the permission to improve the software and the authorization to receive the defense information inside it. We would want to understand who approved the work, who selected the data and what access the recipient actually had. The agreement puts both the flow of information and access to ATOMS at the center of the allegation.

Why the Owner Appears Beside the Contractor

Gallant appears in the settlement as a named party alongside Aero Turbine, with its employee’s alleged participation described in the government’s account. The agreement identifies both the controlling investment and the alleged operational act: a sponsor employee helping the contractor allegedly supplied the data. For an insider, those are different pieces of the story, and both deserve their own records.

There is a broader industry reason to follow the businesses behind the work. In its 2022 report Hidden Costs: US Private Military and Security Companies and the Risks of Corruption and Conflict, Transparency International Defence and Security identified gaps in government vetting of subcontractors in private military and security work. It recommended connecting subcontractor identities, ownership and the value of their services to invoices. Applied here, that is a useful question for us to pursue with an insider: how did the contractor, its owner and the software provider each participate in the work the Air Force was paying for?

Disclosure Credit and a Shared Payment Obligation

Aero Turbine made two written disclosures about cybersecurity noncompliance under the engine contract. Both companies cooperated with the government’s investigation. Aero Turbine also represented that it promptly put mechanisms in place to correct the issues and prevent their recurrence.

The Justice Department credited disclosure, cooperation and remediation in reaching the settlement announced on July 31, 2025. Of that civil settlement, $1,150,000 was designated as restitution. The payment term makes each company responsible for the full settlement obligation, rather than assigning the owner and contractor separate shares.

For an employee involved in the company’s disclosure, the underlying work matters: what the investigation found, which sources supported it and which changes the company said it made. Those records connect the original access decision to the company’s later account of the problem. If the company’s account leaves out what you saw, or a promised correction never reached the system, talk with us about that difference.

The settlement also bars Aero Turbine and Gallant from charging the settlement payment and other costs covered by the agreement to government contracts, directly or indirectly. We think that provision gets the point right: taxpayers should not finance the resolution through another contract’s bill. For a finance employee, the relevant comparison is where those costs landed and whether they reached a government charge.

What Proof Do You Need as a Whistleblower?

We help you connect the contract’s security promise to the system doing the work, the actual controls and access, and the claims for payment. In this case, the named system and the sponsor employee’s alleged transfer give that comparison a specific starting point. We work with you to connect what you saw to what the contractor told the government.

An IT employee may know which users and providers could reach the data. An engineer may know what information the software improvement required. A compliance employee may know what verification was performed, while someone in finance can connect the work to the claims for payment. We bring those views together around the same contract and system.

A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. If your concern involves decisions by the owner as well as the contractor, we examine both roles with you and the defense cybersecurity whistleblower lawyers your case needs.

Another Contractor’s Audit Plan Shows Why the Daily Records Matter

MORSECORP’s cybersecurity case supplies a useful comparison between the assessment reported to the government and the condition of the system. In its civil settlement admissions, the company acknowledged reporting a score of 104, later receiving a consultant assessment of -142 and leaving its reported score uncorrected until after a government subpoena.

The whistleblower’s complaint described a separate alleged management proposal about how to handle audits. It alleged:

That alleged plan aimed at the audit date while leaving the everyday work exposed. The complaint says the whistleblower objected that some controls required a continually generated body of data, which would reveal the gaps between audits. For an insider at a contractor or its owner, the same practical question is worth discussing with us: what did the control records show during the work the government paid for?

When the Owner Helped Make the Access Decision

If you saw a sponsor employee arrange access to defense data or accept a compliance assumption you knew was wrong, speak with our whistleblower experts about the people and systems involved. We build the case with you around the contract promise, the access decision and the government money, and bring in defense cybersecurity whistleblower lawyers who understand those connections. You bring the knowledge of what happened inside the business, and we stay beside you as your partners through the case.