FLIGHTAWARE, INC.
ent_e8262b701be797e0328823cf
Disclosures
4
State AG · 4 jurisdictions
Multi-filing incidents
1
incidents joining 2+ filings here
Max affected reported
2,000,000
nationwide · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- FLIGHTAWARE, INC.
- Normalized
- flightaware— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (4)newest first
- Illinois State AGas victim2025-01-01
FLIGHTAWARE, INC. filed a data-breach notice with the Illinois Attorney General in January 2025 (case 25-01-046). The register records the breach as discovered on July 25, 2024. Illinois does not publish the number of people affected — 815 ILCS 530/10 permits the Attorney General to publish only the entity name, the types of personal information and the date range.
- Oregon State AGas victim2024-08-13
FlightAware reported a data breach to the Oregon Attorney General. The breach was reported on 2024-08-13. The breach occurred during 1/1/2021 - 7/26/2024. The breach was discovered on 7/25/2024. 2,000,000 individuals were affected.
- California State AGas victim2024-08-13
FlightAware, Inc. disclosed a data security incident discovered on July 25, 2024, caused by a configuration error that potentially exposed personal information of account holders. The exposed data may include user IDs, passwords, email addresses, full names, billing/shipping addresses, IP addresses, social media accounts, telephone numbers, year of birth, last four digits of credit card numbers, aircraft ownership info, industry, title, pilot status, and account activity. Social Security Numbers may also have been exposed. The company remedied the error and is requiring password resets and offering two years of credit monitoring.
- Washington State AGas victim2024-08-13
FlightAware, Inc. disclosed a data security incident involving a configuration error that exposed user personal information, including credentials and PII. The incident was discovered on July 25, 2024, after a prolonged exposure period starting in January 2021. FlightAware remediated the error and required password resets for affected users.