FirstAlerts

American Airlines Flight AA2398 Identified as Airbus A321 After Laptop Fire

The aircraft involved in the August 21 laptop fire at Dallas/Fort Worth has been identified as an Airbus A321, according to flight tracking data.

2 reports on this incident · first at Aug 22, 2026, 4:45 a.m. ET

By AI ReporterFirst reported Aug 22, 2026, 4:24 a.m. ETWritten Aug 22, 2026, 4:52 a.m. ET
Breaking news

This report went out within minutes of the first account of it. Early reports are provisional and are frequently revised; where sources disagree, both readings are given.

We have not yet searched for new coverage of this beyond the reports listed below.

The aircraft involved in the August 21 laptop fire aboard Flight has been identified as an , registration , according to flight tracking data. The registration has not been confirmed by an official record. The flight landed safely at /Fort Worth International Airport on after the pilot reported a cabin fire in the back of the aircraft from a passenger's laptop. injuries were reported, according to Simple Flying. One passenger was treated by medical teams on the ground. The flight was met by emergency personnel but taxied to the gate on its own power. Registry records list the registered owner as Inc; the owner of record is not necessarily the operator of the flight. The aircraft is an Airbus A321-211, according to registry records. The cause of the fire has not been determined.

Earlier reports

  1. Aug 22, 2026, 4:45 a.m. ETFirst report

    American Airlines Flight Lands Safely After Laptop Fire at Dallas/Fort Worth

    An American Airlines flight, AA2398, landed safely at Dallas/Fort Worth International Airport (DFW) on Friday evening, Aug. 21, 2026, after a passenger's laptop caught fire, according to Simple Flying. The pilot reported a cabin fire in the back of the aircraft from a passenger's laptop. The flight, an Airbus A321, was met by emergency personnel but taxied to the gate on its own power. One passenger was treated by medical teams on the ground. Five injuries were reported, according to Simple Flying. The aircraft carried 133 people on board.

    The aircraft's registration is N197UW, according to flight tracking data; this has not been confirmed by an official record. Registry records list the registered owner as American Airlines Inc; the owner of record is not necessarily the operator of the flight. The cause of the fire has not been determined.

    American Airlines has had several other incidents involving its aircraft in 2026, according to NTSB records. These include a Boeing 737-800 incident in Boston on June 20, a Boeing 737-823 incident in San Salvador on March 1, a Bombardier CL-600-2C10 incident in North Eleuthera on February 24, a Bombardier CL-600-2D24 incident in Exhuma on February 12, and an Airbus A319 incident in Charlotte on February 11. The Airbus A321-211 has been involved in three other NTSB cases since 2008, none of which involved a fatality. These records say nothing about the cause of this accident.

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.

Registration
N197UW
Type
Airbus A321-211 — twin-engine jet landplane
Engines
CFM INTL CFM56-5B3/P
Registered owner
American Airlines IncThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation
436 ft
Nearest aerodrome
5.6 miles SSE of Dallas Love Field (KDAL/DAL)

Sources

Revision history

  1. Version 122 Aug 2026, 08:52current

    First published.

  2. Version 122 Aug 2026, 08:45current

    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.