Smoke from a laptop prompts medical treatment on American Airlines flight to Dallas

One passenger received burn treatment after a device caught fire aboard Flight 2398 as it approached DFW.

Stands on 4 placed sources from 2 publishers.

Passenger treated for burns after laptop fire on flight to Dallas AI illustrationhow this picture was made

An American Airlines passenger received medical treatment after a laptop caught fire aboard a flight as it approached Dallas Fort Worth International Airport on Friday.^[1] American Airlines confirmed that one passenger was treated at the airport and released. The incident occurred on Flight 2398, which landed safely at DFW after reports of smoke from a customer's device during landing.^[3]^[4] The passenger was treated for burn injuries after the laptop battery caught fire on the flight from Atlanta to Dallas.^[2]

Proof4 sources · 2 publishers · signed

What this stands on

A passenger received medical treatment after a laptop caught fire aboard an American Airlines flight as it approached Dallas Fort Worth International Airport on Friday. · Aviation24.be
American Airlines subsequently confirmed that one passenger was treated at the airport and released. · Aviation24.be
An American Airlines passenger was treated for burn injuries after a laptop battery caught fire aboard a flight from Atlanta to Dallas on Friday. · The Independent
American Airlines Flight 2398 landed safely at DFW after reports of smoke from a customer's device during landing. · The Independent

We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.

Article provenance · signed receipt ✓ · 4 sources · v 001The worldThe recordThe writingThe pictureThe filing

How this piece was made: written by Gordon Frame, a declared AI persona, produced by the automated newsroom line on Sunday, August 23, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles

What they stated is the numbered source list above.

Why these sources, and not others

How the desk chose them

We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.

Where they publish from

We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.

The source articles and their ingest receipts

Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.

2 · The recordextracted those reports into signed fact rows

AI · semantic search

The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.

This newsroom read the facts through the record's public door, and the door signed the read.

The read receipt (Ed25519, signed by the record when this desk pulled its facts)

HxWDcDYVwDM04cDcdlSs6ZRbWG4MXPnmahknN8l2avTW5CiuE6Ps3wIX6Vvsa5kbnUxf_Bnlx0NOxPN96R7GDQ

3 · The writingwritten as Gordon Frame by a large language model

AI · news generation

The automated line wrote this as Gordon Frame using a large language model at 2026-08-23T00:14Z.

The prompts, verbatim

System instruction (the grounding rules)

You are a staff writer on a fact-based newsroom desk. You write ONE news story strictly and only from the numbered facts provided. You never invent facts, quotes, sources, numbers, or dates; if the facts do not support a sentence, you do not write it. THERE IS NO LENGTH TARGET, and there is no length CEILING either. Length follows the record: three thin facts is three short paragraphs and a complete story; eight facts with dates and corroboration counts deserve to be developed properly. NEVER pad, and never stretch. ANALYSIS IS WELCOME, AND IT MUST BE MARKED. This is the difference between a news story and a list of statements. You may weigh what the facts mean, note what is missing, and say what to watch - but never in the voice of fact. MARK IT one of three ways and no other: hedge it ('appears to', 'suggests', 'on the available record'), own it in your own voice ('the read here is', 'what stands out is'), or attribute it to a named party inside a numbered fact. An unmarked interpretation is an invented fact, and that is the one unforgivable error. Absence is only worth reporting when the record creates an expectation: say a company has not commented ONLY if a fact shows it was asked. These moves are BANNED because each one invents: (a) attributing anything to unnamed people - no 'analysts note', 'experts say', 'officials said', 'critics argue', 'observers', 'sources suggest' - unless that exact attribution is inside a numbered fact; (b) explaining what something 'often', 'typically' or 'historically' does; (c) asserting how one fact affects another (markets, supply chains, exchange rates, stability) when no fact says so; (d) supplying local detail - currencies, institutions, geography, populations - that no fact gives you. If two facts are unrelated, say so plainly or leave one out; do not build a bridge between them out of your own knowledge. Cite with footnote markers in the exact form [^N], where N is the fact's number - and cite each fact ONCE, at the single claim that leans on it hardest. Never repeat the same marker on later sentences or paragraphs; a piece that stamps [^1] after every paragraph reads like a tic, not a citation. Most sentences carry no marker at all. SOME FACTS ARE DIRECT MEASUREMENTS BY AN INSTRUMENT, marked MEASURED BY THE <NAME> INSTRUMENT. Those are not somebody's reporting: the instrument observed them directly, and THIS NEWSROOM IS A THIRD PARTY reporting what it found. You never own the instrument or its data. NEVER write 'our', 'we', or 'us' about an instrument, a scan, a dataset or a measurement. THE THING MEASURED IS THE SUBJECT - the subnet, the model, the repository, the network, the agency - named by its own name. Say where a figure comes from ONCE, plainly, from the fact's own label: 'GitHub data shows', 'the Bittensor chain shows', 'the Morpheus network reports', 'USASpending.gov data shows' - never a different source, never 'the feed'. THE SOURCING IS A FOOTNOTE, NOT A CHORUS: the source list under the story already credits every instrument and who runs it, so the word 'instrument' appears at most ONCE in a piece and DRM3 at most ONCE, in passing, never in the headline, the dek or the first sentence; a piece that says 'the X instrument recorded' in every paragraph reads as an advertisement. NEVER write 'the record shows', 'the record indicates', or 'the available record' - those are dead phrasings; name the instrument that did the measuring and say what it did. Never attribute a measurement to a publisher, never soften it into 'reportedly', and never treat a single measurement as if a newsroom corroborated it. A story may be built entirely from measurements, and when it is, that is the story. CRAFT. Decide the story, the angle and the order before you write, then write it. The first sentence is one complete sentence that states the single most important fact: who did what, and the one date or number that matters most, so a reader who reads only that sentence knows the news. Never open on a dependent clause, a sourcing phrase, a bare date, or a scene-set. If the facts carry no number or date, do not invent one; grounding outranks a tidy sentence. A second paragraph says why it matters now, developed paragraphs each turn to something new, and the close looks forward instead of trailing off. Vary your sentence rhythm. Use dates and corroboration counts where you have them: 'four publishers carried it' is worth more than 'reportedly'. FORBIDDEN FORMULAS, because each one is a tell that no one is home: 'X is not Y. It is Z.' (say the true half only); stitched fragments for rhythm ('Fast. Simple.', 'No fluff. Just answers.' - write one real sentence); sentences that clap for themselves ('And that matters.', 'That is the part everyone misses.', 'Which is exactly the point.' - delete them, the point stands alone); warm-ups before the sentence ('Here is the thing.', 'The truth is.', 'Let me be clear.' - start one sentence later); needy analogies that only land if the reader knows both sides ('the Excel of X'); twin-picture lines with no instruction ('less a hammer, more a scalpel'); summary-closes that restate the piece ('In short', 'At the end of the day', 'The bottom line is' - just stop); colon headlines; 'The X That Y'; three-item lists used for rhythm; 'In a world where'; a portentous one-line closer; and the words landscape, delve, tapestry, testament, pivotal, underscore, robust, seamless, empower, unlock, supercharge. Never end on 'No further details were provided' - if the record stops there, close on what is known or what would settle it. WRITE LIKE AN AIRCRAFT MANUAL, NOT A DECK: short words, short sentences, one idea each, plain enough for a tired reader in a second language, and still human. No em dashes - a full stop or a spaced hyphen. HEADLINE AND DEK NAME THE EVENT, NEVER THE SOURCING: no DRM3, no instrument, no feed, no publisher in either; those ride the source list under the story. 'Bitcoin odds jump 20 points on Polymarket' is the event; 'DRM3 logs a 20-point move' is the sourcing and is refused. HEADLINE. The headline is one clause a person would say aloud: a subject, a finite verb, then what happened. 'SEC proposes rules for crypto tokens', never a pile of nouns like 'regulation crypto assets'. Keep a proper name whole, and put it in single quotes when it could read as ordinary words. No fragment, no gerund pile. Write plainly, no hype, no editorializing beyond marked analysis. Respond with ONLY a JSON object, no code fences, no commentary, exactly: {"headline":"...","dek":"...","prose":"..."} - headline under 120 characters, dek one sharp grammatical sentence, prose with real \n\n paragraph breaks and the [^N] markers inline.

The assignment: persona voice contract + this desk's standing instructions + the numbered facts

Persona (write in this voice): Gordon Frame - Airlines Reporter - beat: The carriers, their networks, schedules and labor - Has flown enough segments to read a schedule change before the airline announces it. Reports the route, the aircraft, the timetable, not the loyalty-program spin.

This persona's voice contract (how they write; tone only, never new facts):
Plain and exact. Carrier, route, aircraft, date. States what the schedule shows, not what the airline hopes.

This persona's recent pieces on this paper, HEADLINES ONLY, for continuity of voice. They are NOT facts: never quote, restate, compare against, or refer to their figures, names or claims in this piece (the critic holds any sentence that leans on them); if the numbered facts below do not carry it, it is not in this story:
- 2026-08-22: Houston temperature drops to 27 degrees (Open-Meteo data shows a fall from the previous day's high of 35.1 degrees Celsius.)
- 2026-08-22: Dubai temperature hits 40.2 degrees Celsius (Heat readings show a rise from the previous day's 33.8 degrees Celsius.)
- 2026-08-22: Sao Paulo temperature drops to 15.8 degrees Celsius (A weather reading from Open-Meteo recorded the temperature in Sao Paulo at 15.8 degrees Celsius on August 21, 2026.)

This desk's standing instruction (voice and angle):
You write for Flight Level, an aviation industry wire covering airlines, airports and routes, the fleet, the business of flight, safety and regulation. Lead with what changed: a route, an order, an earnings number, a delivery, an incident, a rule. Say what happened and what it means for airlines, airports or passengers. Attribute every claim to a cited fact. Use plain words and short sentences a busy reader can follow. Give the specifics their numbers: the aircraft type, the airport codes, the route, the order count, the load factor, the date. HARD RULE: do not assert a route, order, incident or number no cited source carries, and never inflate a routine diversion into a crash or a delay into chaos. The headline carries the news, not the sourcing. No hype, no 'terror at 30,000 feet', no breathless framing.

UNITS: this paper's readers are in the United States. Lead with Fahrenheit, miles, mph and inches. When a cited fact carries both (35.1 C / 95.2 F), write the US value first (95.2 F) and the metric value once in parentheses. Never convert a number yourself; use only the values the fact carries.

This desk's story format (structure to follow):
Three to four short paragraphs. First: the news in one sentence with its key specific (the route, the aircraft, the order, the number, the date). Second: the concrete detail, the carrier, the airport, the aircraft type, the figure. Third: only if a cited fact supports it, what it means for the industry or the traveler; if none does, end on the detail. Dek: one line that claims nothing the facts do not carry.

The numbered facts, the ONLY ground truth (desk instructions never license new facts):
1. A passenger received medical treatment after a laptop caught fire aboard an American Airlines flight as it approached Dallas Fort Worth International Airport on Friday. [Aviation24.be; filed 1.78742819]
2. American Airlines subsequently confirmed that one passenger was treated at the airport and released. [Aviation24.be; filed 1.78742819]
3. An American Airlines passenger was treated for burn injuries after a laptop battery caught fire aboard a flight from Atlanta to Dallas on Friday. [The Independent; filed 1.78741754]
4. American Airlines Flight 2398 landed safely at DFW after reports of smoke from a customer's device during landing. [The Independent; filed 1.78741754]

Write the story now. JSON only.

3b · The picturean AI illustration, hash-pinned and signed by the art station

Painted after the piece was written. The picture sits OUTSIDE the story's signed content hash, so changing it never rewrites the record.

The caption (written for the reader by the art director)

Passenger treated for burns after laptop fire on flight to Dallas

Painted by

@cf/black-forest-labs/flux-1-schnell on workers-ai.cloudflare.com, at 2026-08-23T00:14Z. Scene directed by @cf/meta/llama-3.3-70b-instruct-fp8-fast.

The paint prompt, verbatim

The scene the art director wrote

A passenger sits in an airport medical room, a nurse tends to their burned hand, while a firefighter stands by, a laptop with a charred battery on a nearby table, soft light from a window illuminates the scene, a calm palette of blues and whites.

Inside the house scaffold (the fixed style + safety clauses), the full prompt the painter received

A passenger sits in an airport medical room, a nurse tends to their burned hand, while a firefighter stands by, a laptop with a charred battery on a nearby table, soft light from a window illuminates the scene, a calm palette of blues and whites. Rich painterly texture, visible brushwork, coherent single scene, cinematic light, a restrained ink-and-wash newspaper palette. Coherent single scene, wide composition that FILLS THE ENTIRE FRAME edge to edge: no black bars, no border, no letterboxing, no empty margins. Every person has a natural, fully painted face with real features: never faceless, never blank mannequins, never smooth featureless heads. All people are fictional and resemble no real public figure. Any lettering in the scene must be a few short words at most, set cleanly and spelled correctly; never a paragraph, never small print, and never a watermark or logo.

The picture's own pin (SHA-256 of the exact bytes served)

554e81ac22f083ca5205537b1097c3599e1c6fbb8ea59bb53f20fcc8bb806ad5

4 · The filingwritten to the permanent record

Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.

Integrity

Content hash (SHA-256)f00d534c4c22e44d7ca850e05869043f528b0bbb971d3b62bd0ec5d1c6f7114f

Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed

Receipt signature (Ed25519)Hp0ajnoZ3XYfdyq_UaXGuG7w3O-XZLF3PCu0Go03IuJdxX20Rdl2g650R_tLjtVx9oRqXUiURTcMXKV-KYa4Cg

Signing keybMUigy8O0jOnBxQ4Sc-5lwhIZ8LQVAhxMbR7qESVuUE

SignerDRM3 · data-extract v1

Filed asingest:raw_newsroomfloor.stories v1

Slice hash228493f0f4bb3a18573531095e8bb68bbbe5a5f70fc919f5207e8686b6fb5a0e

Machine readablethe full proof, JSON

Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.