FirstAlerts
Plane CrashesVersion 6

Laptop Fire on American Airlines Flight to Dallas Injures Passenger

A laptop battery caught fire aboard an American Airlines flight from Atlanta to Dallas on Friday, August 21, 2026; the FAA is investigating.

By AI ReporterFirst reported Aug 21, 2026, 11:22 p.m. ETUpdated Aug 26, 2026, 2:23 a.m. ET
A laptop battery caught fire aboard an flight from Atlanta, Georgia, to Dallas on Friday, August 21, 2026, according to NBC DFW and paddleyourownkanoo.com. The flight number was reported as either by NBC DFW or by paddleyourownkanoo.com. The pilot reported a fire in the back of the cabin, and flight attendants worked to put out the fire. The aircraft landed safely and taxied to the gate using its own power, where emergency personnel met the aircraft. The flight arrived minutes off schedule. The number of injuries was reported as either 1 by NBC DFW or by paddleyourownkanoo.com. The phase of flight was reported as either by paddleyourownkanoo.com or by NBC DFW. The time of the incident was reported as either by NBC DFW or by paddleyourownkanoo.com. There were people on board, according to both outlets. The aircraft involved has not been identified. Registry records list as operating 208 aircraft, of which 118 match the reported type (), but these records do not identify the specific aircraft involved in this incident. The cause of the fire has not been determined.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Terrain elevation
564 ft
Nearest aerodrome
5.6 miles S of Dallas Love Field (KDAL/DAL)

Sources

Revision history

  1. Version 626 Aug 2026, 06:23current

    Updated to reflect the latest reporting, including the conflicting injury count and phase of flight.

  2. Version 525 Aug 2026, 02:23

    Updated operator fleet figures to 208 aircraft and 118 A321s per registry records.

  3. Version 424 Aug 2026, 00:40

    Updated operator fleet figures to 219 aircraft and 65 A321s per registry records; corrected phase of flight and time conflicts to include all reported values.

  4. Version 324 Aug 2026, 00:14

    Updated operator fleet figures to match reference data (218 aircraft, 128 A321s).

  5. Version 223 Aug 2026, 00:22

    Updated to reflect conflicting reports on flight number, injuries, phase of flight, and time, and corrected operator fleet count to 230.

  6. Version 122 Aug 2026, 23:44

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.