Real occurrence · dated 2026-11-03 · Confirmed · Last meaningful update Nov 6, 2026, EST · time not recorded

Confirmed Steve-checked Updated Nov 6, 2026, EST · time not recorded

Filed at Steve's Desk · Editor & verifier

Airbus A321neo (N409AA): Returned to Phoenix after a reported brake issue en route to Honolulu; landed safely, no injuries reported.

Date2026-11-03

AircraftAirbus A321neo (N409AA) (Narrowbody)

OperatorAmerican Airlines — AA675

LocationPHX — Phoenix Sky Harbor (return)

Current summary

Returned to Phoenix after a reported brake issue en route to Honolulu; landed safely, no injuries reported.

Last meaningful update: Nov 6, 2026, EST · time not recorded

Jump to latest update

Known facts

Flight AA675 Phoenix → Honolulu, Airbus A321neo N409AA, 3 Nov 2026.
FAA: crew reported a brake issue; the aircraft returned safely to Phoenix Sky Harbor around 2:45 p.m. local; FAA investigating.
Flight-tracking data cited in aviation trade: climbed to about 28,000 ft, turned back near Palm Springs, and landed back at Phoenix; a later AA675 on another A321neo completed the Honolulu trip.
No injuries reported in sources reviewed.
American Airlines — AA675, Airbus A321.
Returned to Phoenix Sky Harbor International Airport after the crew reported a brake issue.

Unknown / not claimed

Nature of the brake issue — under FAA investigation.
Number of people on board (not in FAA statement reviewed).
Cause is not stated in the sources reviewed.
Injuries were not stated in the sources reviewed.

Updates

Newest first. Entries are retained; legacy date-only entries have no recorded time.

# Nov 6, 2026, EST · time not recorded · fact update

Sources were re-read. Known facts were corrected in this update; the earlier wording was left in place.
- https://www.faa.gov/newsroom/statements/accident_incidents#2026-11-03-faa-statement-phoenix-arizona-american-airlines-flight-675-r
- https://www.faa.gov/newsroom/statements/accident_incidents#:~:text=American%20Airlines%20Flight%20675%20returned%20safely%20to%20Phoenix
# Nov 5, 2026, EST · time not recorded · status change

Score 40. Partial official confirmation. Not enough yet for Steve-checked. Still open: injuries.
- https://www.faa.gov/newsroom/statements/accident_incidents#2026-11-03-faa-statement-phoenix-arizona-american-airlines-flight-675-r

Status history

Nov 5, 2026, EST · time not recorded · new → Developing

Score 40. Partial official confirmation. Not enough yet for Steve-checked. Still open: injuries.

Earliest retained published account

Preserved from the existing published card when timestamped history was enabled. Earlier original wording or publication time cannot be reconstructed.

Returned to Phoenix after a reported brake issue en route to Honolulu; landed safely, no injuries reported.

Flight AA675 Phoenix → Honolulu, Airbus A321neo N409AA, 3 Nov 2026.
FAA: crew reported a brake issue; the aircraft returned safely to Phoenix Sky Harbor around 2:45 p.m. local; FAA investigating.
Flight-tracking data cited in aviation trade: climbed to about 28,000 ft, turned back near Palm Springs, and landed back at Phoenix; a later AA675 on another A321neo completed the Honolulu trip.
No injuries reported in sources reviewed.

Not claimed at that time:

Nature of the brake issue — under FAA investigation.
Number of people on board (not in FAA statement reviewed).

Sources

FAA statement: Flight 675 (Nov 3, 2026) — Tier A — regulator statement
AeroCorner — AA675 track and N409AA — Tier B — aviation trade; Flightradar24 track
Passport News — FAA summary — Tier B — press summarizing FAA
FAA statement: Flight 675 (Nov 3, 2026) — Federal Aviation Administration official notice; full enough to score. It does not state injuries.

Confidence label

Labeled Confirmed (Steve-checked) per the TurbineWire methodology. Labels move up or down as sourcing improves or collapses; material changes append under Updates rather than silently rewriting the original card.

Comments

Professional discussion only. Every comment is held for moderation before it appears. See the comments policy.

Loading…

← Back to all incidents