BreachScout BreachScout Breach Records

Regulator-posted notice

Breach notice filed by FlightAware (August 2024)

Organization named: FlightAware Provisional: identity as filed, not yet matched to the directory

What the sources say

Washington Attorney General data breach notifications Primary notice

Posted on the Washington Attorney General data breach notifications with a submission date of Aug. 13, 2024.

Organization as reported
FlightAware
Information types as reported
Name; Username and Password/Security Question Answers; Email Address and Password/Security Question Answers; Other
Incident dates as reported
Jan. 1, 2021
Submission date
Aug. 13, 2024
Observed by BreachRecords
2026-10-19 04:56 UTC (revision 25584, page:9:row:42)
Archived copy
Held in the private archive (provenance)

The listing records a filing with the agency; it is not a finding by the agency.

Washington data breach notifications dataset (data.wa.gov sb4j-ca4h) Duplicate filing

Posted on the Washington data breach notifications dataset with a submission date of Aug. 13, 2024.

Organization as reported
FlightAware, TX
Entity type as reported
Business
Category as reported
Unauthorized Access
Incident dates as reported
Jan. 1, 2021 to July 26, 2024
Discovery date as reported
July 25, 2024
Submission date
Aug. 13, 2024
Observed by BreachRecords
2026-11-01 20:03 UTC (revision 63514, row:1230)
Extraction
Parsed from a document; extraction confidence 0.85
Archived copy
Held in the private archive (provenance)

The listing records a filing with the agency; it is not a finding by the agency.

Figures, per source

  • 1,407 individuals affected (residents of the reporting state), according to the Washington Attorney General data breach notifications, source date Aug. 13, 2024, revision observed 2026-10-19.
  • 1,407 individuals affected (residents of the reporting state), according to the Washington data breach notifications dataset, source date Aug. 13, 2024, revision observed 2026-11-01.

Each figure is one source's figure with the basis that source gave. Figures from different sources are shown side by side and are not added, averaged or chosen between.

Timeline

Source dates are the dates the sources give. Observation dates are when BreachRecords recorded each revision.

  • Submission date (Washington Attorney General data breach notifications)
  • Submission date (Washington data breach notifications dataset)
  • Observed by BreachRecords (revision 25584)
  • Observed by BreachRecords (revision 63514)
  • Approved by a reviewer

Organizations linked by a reviewer

  • FlightAware Named as the filer Provisional: identity as filed, not yet matched to the directory Linked 2026-11-04, method manual.

Archived evidence

  • 264d45f73831ec8fc298837002b836f792a7cfd7f3d6b4d2128484a23223c042
    text/csv, 453,656 bytes, retrieved from Washington data breach notifications dataset, 2026-11-01 20:03 UTC. Archived privately · Provenance · Source page
  • 6877483fc5ae74a01265f3c256f318bf85dfef1350b962e5e17babb4c2d58fc3
    text/html, 156,511 bytes, retrieved from Washington Attorney General data breach notifications, 2026-10-19 04:56 UTC. Archived privately · Provenance · Source page

Records reflect source filings as of the dates shown. BreachRecords is not a regulator.

Request a correction

A record that disagrees with its source, names the wrong organization or duplicates another is corrected after review. This form is about Breach notice filed by FlightAware (August 2024). We acknowledge every request within two business days. We reply by email.

The form is being set up. Check back soon.