HackingManufacturingManufacturingCustomer Data InvolvedEmployee Data InvolvedIdentity (basic)Government IDFinancial accountHealth (basic)MediumResolved

Tronair, Inc.

bd_6ba794299f4cf3ef · schema v1 · pii pii-v1

Severity

Medium

Discovered

Jul 4, 2024

Filed

May 19, 2026

To disclose

—

Affected

2state residents only

Linked

3 filings

Confidence

93%

Full breach record for Tronair, Inc. →2 incidents on file

Tronair, Inc., an Ohio manufacturer of aircraft ground support equipment, experienced unauthorized access to its network systems from July 1–4, 2024, discovered on July 4, 2024. The incident affected personal information including names, dates of birth, government IDs (SSN, driver's license), financial account details, and health insurance information. Two Maryland residents were affected. Data review results were received November 4, 2024; individual notifications began January 7, 2025.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 3 days

Jul 1, 2024

Begins

Jul 4, 2024

Discovered

Nov 4, 2024

Scope determined

May 19, 2026

Filed

This filing is one of 3 filings about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Nebraska State AGbd_8f0e732c841640522025-01-07 · +498dCandidate
New Hampshire State AGbd_a876a6091070429c2025-01-07 · +498dVerified

Name: Tronair, Inc.
norm: tronair
Industry: Aircraft ground support equipment manufacturing

Name: Tronair, Inc.
norm: tronair
Industry: Aircraft ground support equipment manufacturing
Industry: Manufacturingllm

Discovered: Jul 4, 2024
Breach occurred: Jul 1, 2024 – Jul 4, 2024
Undetected for: 3 daysoccurrence → discovery
Materiality determined: Nov 4, 2024
Notification sent: Jan 7, 2025
Affected individuals: 2state-resident count only
Data types: Identity (basic)Government IDFinancial accountHealth (basic)
Data elements: Social Security numberDate of birth
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Regulator citations: Notified Maryland Attorney GeneralNotified law enforcement

During the incident: Immediately took steps to begin investigating the incident and securing its environment
Promptly engaged Shook, Hardy & Bacon as outside counsel
Engaged a leading digital-forensics firm to assist in the investigation
Engaged a data-review firm to determine what personal information was in those files
Provided an initial notification to all current employees about the incident
Offered each employee and their beneficiaries a one-year membership to Experian IdentityWorks credit monitoring
Started mailing individual notification letters to all affected individuals on January 7, 2025
Established a toll-free call center to field any questions individuals have about the incident
Notified law enforcement
Changes made: Changed/strengthened passwords
Rebuilt the affected servers
Adopted additional technical safeguards
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Nebraska State AGJan 7 · first

New Hampshire State AGJan 7 · first

Maryland State AG+498d · this page

Pattern: first filing Jan 7 (NE), last May 19 (MD) — a 498-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.maryland.gov/resources-info/SBN%20Documents/2025/ITU-376120.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 19, 2026
Raw hash: 6a6c3499381577b46e0e8290cb63da9f4c65289d1d7b41631aead47ea06a2480

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityTronair, Inc.

Victim entityTronair, Inc.

Incidentdiscovered Jul 4, 2024

Stated responseImmediately took steps to begin investigating the incident and securing its environment

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.maryland.gov