Clustered 2 filings across 2 jurisdictions · filing window Jan 7, 2025 → May 19, 2026. View entity profile → Other incidents for this victim →
incident inc_6edb68ee416447a4 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
MD NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 1, 2024 → Jul 4, 2024
When the intrusion reportedly occurred, per the linked filings
Jul 4, 2024
Reported by NEW HAMPSHIRE AG, MARYLAND AG filings
Tronair notified New Hampshire residents of a data breach involving unauthorized network access occurring between July 1 and July 4, 2024. The company detected the activity on July 4, 2024, engaged third-party experts and law enforcement, and determined personal information was involved. The breach notification was filed with the NH DOJ on January 7, 2025.
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.
Affected (this filing):
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.