American Airlines Stopped Every Flight for 51 Minutes. The App Reviews Don't Know Yet.

American Airlines grounded every flight in its system for about 51 minutes on the evening of July 28, 2026, after a systemwide technology outage. It is exactly the kind of incident Crawlora is built to measure: a single, precisely timestamped shock, applied to a large population, with millions of the people affected holding the same app on their phones. So we pulled it — live, within hours — expecting an app-store review pattern to already show a mark. It doesn't. Not because the story is a non-event; Google Trends, Reddit, and American's own account all confirm it happened and confirm roughly when. It's because a review takes longer to write than a tweet, and this measurement window caught that gap directly, rather than the spike everyone assumed would already be there.

Fifty-one minutes, reconstructed from a live thread

American didn't announce this on its own terms — the fastest, most granular record of it is a single r/americanairlines post that a passenger sitting at O'Hare edited in real time as it happened, plus American's own account and same-night wire coverage.

Time (CDT / UTC)	Source	Event
5:16pm / 22:16	r/americanairlines live thread	"This appears to be across the US" — outage first reported nationwide, passengers deplaned at ORD
5:44pm / 22:44	FAA Air Traffic Control Command Center	Nationwide ground stop issued for American and its subsidiaries, in effect until 6:30pm CDT
6:07pm / 23:07	r/americanairlines live thread	Boarding resumes at O'Hare
6:21pm / 23:21	@AmericanAir (X)	"Systems are coming back online now and flights are departing again... we apologize to our customers for the inconvenience"
~6:30pm / 23:30	CNN, Reuters, CBS News	Ground stop confirmed lifted; outage widely described as "brief" and "less than an hour"

The FAA's own ground stop was scheduled to run until 6:30pm CDT but was lifted early, close to the 6:07–6:21pm window. Reddit's live thread also makes clear this wasn't a narrow, single-system glitch: one pilot for an American regional carrier described it as "all systems completely bricked. Even gate agents. I can't even sign into the company website or video training or anything." A passenger trying to check in at O'Hare at 5:05pm reported "an error on both website and app" — the outage took down the passenger-facing app and the airline's internal systems in the same failure, not one or the other.

Google Trends caught it inside the hour

"american airlines" (broad)24 → 47"american airlines ground stop"0 → 2

4:20p

24

0

5:00p

25

0

5:16p

37

0

5:32p

50

1

5:48p

75

9

6:04p

58

4

6:20p

75

5

6:28p

100

5

6:44p

71

3

7:16p

55

2

8:20p

45

1

9:40p

47

2

Two things worth separating out. First, the broad term "american airlines" had spent the entire day in the high teens and 20s on this shared 0–100 scale — a flat, ordinary baseline for a major airline's brand name. It broke that baseline the moment the outage started circulating (5:16pm), climbed through the ground stop itself, and hit its ceiling of 100 at 6:28pm — seven minutes after American's own apology posted, which is when the story crossed from "passengers noticing" to "a confirmed, resolved news event" that outlets could headline. Second, the exact phrase "american airlines ground stop" — the specific, diagnostic query — has no measurable volume at all until the outage is already underway, then peaks at 5:48pm, four minutes after the FAA's ground stop was formally declared. The search data's timestamp for "something is happening" and Reddit's timestamp for the same thing are four minutes apart. That's about as tight as two independent, unrelated measurement systems get.

The map matches the hub map

0100 no data

Show the data

North Carolina	100
Texas	72
Illinois	69
Arizona	68
Oklahoma	64
South Carolina	56
Florida	50
New Hampshire	50
West Virginia	50
Iowa	46
Pennsylvania	45
Virginia	43
New Mexico	43
Idaho	40
Tennessee	40
Connecticut	40
Massachusetts	40
New Jersey	37
Kentucky	34
Maryland	34
Indiana	34
Wisconsin	34
Missouri	33
Alabama	31
Colorado	30
Arkansas	29
Kansas	28
Georgia	28
Utah	27
Washington	25
Oregon	23
Louisiana	23
Nevada	23
New York	22
California	21
Ohio	21
Michigan	19
Minnesota	17
Alaska	no data
Rhode Island	no data
Nebraska	no data
South Dakota	no data
North Dakota	no data
Montana	no data
Mississippi	no data
Maine	no data
Vermont	no data
Hawaii	no data
Delaware	no data
District of Columbia	no data
Wyoming	no data

The radar report that flagged this incident predicted the regional skew should track American's hub airports — Dallas-Fort Worth, Charlotte, Phoenix, Miami — as a testable hypothesis rather than a vibe. It holds up well. North Carolina, home to American's Charlotte hub (which Reddit and aviation press describe as fully shut down during the stop), leads the country outright at 100. Texas, home to American's Fort Worth headquarters and its largest hub, is second at 72. Illinois — O'Hare, the single airport that produced the most live Reddit reporting in our pull — is third at 68. Arizona, home to the Phoenix hub, rounds out the top four. Miami's Florida sits mid-table at 50, likely diluted by the state's much larger general population relative to its one American hub. Thirteen low-population states, several with no scheduled American mainline hub presence, register no measurable search volume for this exact phrase at all.

The part that hasn't happened: zero app reviews

This is the question the radar report set out to answer, and the honest result is a null one. American's app is the primary self-service channel during any disruption — rebooking, boarding passes, gate changes — and a nationwide ground stop is exactly the kind of moment that should generate a review spike if one is coming. As of this pull, it hasn't.

Store	Newest visible review at pull time	Time before the outage began	Lifetime rating (unchanged)
Apple App Store (US)	Jul 27, 2026, 11:06am PDT (18:06 UTC)	~28 hours before	4.78 / 5 (1,365,325 lifetime reviews)
Google Play (US, phone)	Jul 28, 2026, 2:15am UTC	~20 hours before	4.81 / 5 (228,945 lifetime ratings)

Neither store shows a single review posted after the outage began — the newest review in each feed is from well before 5:16pm CDT on July 28. American also didn't ship an emergency patch: appstore_version_history shows the app is still on version 2026.21, released July 20, eight days before the incident, with the standard "bug fixes and performance improvements" release note and nothing dated after it. The lifetime rating distributions we could pull — a 4.78 average on iOS across 1.37 million reviews, a 4.81 average on Google Play across 229,000 ratings, both overwhelmingly five-star — are the app's standing shape, not a day-by-day trend line, and we're not claiming they've shifted; we simply have no evidence yet that they have.

Reddit and X answered in minutes; reviews haven't answered at all

Set the review gap against how fast the other channels moved. The first "this appears to be across the US" Reddit report landed at 5:16pm CDT, inside the outage itself. American's own X account posted an apology at 6:21pm CDT, 14 minutes after boarding resumed. Google Trends' diagnostic query peaked at 5:48pm, four minutes after the FAA's ground stop was declared. All three of those channels reacted within the hour. A written app-store review — a few sentences, a star rating, a deliberate act you complete after you've already decided you're annoyed enough to say so in public — evidently takes longer than that, and the passengers most affected were, for most of that hour, standing at a gate or sitting on a taxiing plane rather than at a keyboard.

That's a real finding, even though it isn't the one the story went looking for. The original premise — split app-blaming reviews from airline-blaming reviews, the way the app-review cluster on this site has done for World Cup apps and neobanks — requires reviews to exist first. None do yet. What we can say from the Reddit thread itself is that passengers experiencing the outage in real time weren't distinguishing "the app" from "the airline" at all: the check-in failure hit "both website and app" simultaneously, framed as one system-wide collapse, not a passenger-app-specific complaint.

What one endpoint would have told you

Trends alone says a real, sharp, hub-shaped spike happened and mostly resolved within a few hours. Reddit alone gives the minute-by-minute mechanics no other source captures — who was on which tarmac, when boarding actually resumed. X gives the airline's own, much briefer version of the same timeline. App-store data alone, read without the other three, could easily be misread as "nothing happened" — and that would be wrong. The honest reading, with all four in view, is narrower and more useful: something happened, it was measurable and hub-shaped within the search data, and the review record — the one channel this site's app-review cluster usually leans on hardest — simply hasn't caught up to it yet. If we run this pull again in 48 hours, per the standard playbook for this kind of incident, that gap either closes or it doesn't, and either answer would be worth reporting.

How we measured this

App Store: appstore_reviews (ID 382698565, com.aa.AmericanAirlines, US storefront, sort mostRecent) and appstore_version_history. appstore_ratings returned a bare ERROR on two separate attempts; the 4.78/1,365,325-review lifetime figure instead comes from the appstore_search result for the app, which is the same underlying aggregate.

Google Play: googleplay_reviews (com.aa.android, sort newest, 50 results, no pagination) and googleplay_ratings for the device-level histogram (phone: 228,945 ratings, 969 one-star).

Reddit: reddit_search scoped to r/aviation, r/americanairlines, r/flying and r/travel, plus reddit_comments on the three most detailed live threads (1v9cz15, 1v9dkri, 1v9dfra). A real gotcha, consistent with what earlier radar runs on this repo have flagged: unscoped or broadly-worded queries return mostly-irrelevant recency-sorted noise; scoping to subreddit=americanairlines with the exact incident terms is what actually surfaced the live thread.

X: x_profile_posts for @AmericanAir, 20 most recent posts from the first public page payload. The handle @AmericanAirSupport returned an "invalid x username" error from the endpoint — it does not appear to be a live account under that exact handle, so we did not corroborate a second official account.

Google Trends: google_trends_explore_interest_over_time, keywords ["american airlines ground stop", "american airlines"], geo=US, time_range=now 1-d, tz=0 (UTC; chart labels above are converted to Central time for readability against the incident timeline). google_trends_explore_interest_by_region, same geo and time range, keyword ["american airlines ground stop"]. A gotcha worth recording for anyone repeating this: our first interest_over_time attempt was hard-rate-limited (429 after 12 attempts on 12 egress sessions) — the same failure the 2026-07-29 trending-topics radar hit on this exact query — but a second attempt roughly twenty minutes later succeeded cleanly. google_trends_explore_rising_queries stayed rate-limited on retry and returned nothing for the narrow incident phrase in a same-day window; we did not force it.

News verification: google_news and bing_news for "American Airlines ground stop," used to corroborate the outage's cause (a systemwide IT/connectivity issue, not a security incident, per American's own statement) and its resolution time, not for anything not already independently confirmed by Reddit or American's own account.

Scope note: this post measures search behavior, social posts, and the app-review record in the hours immediately following a brief, resolved operational incident. It is not a claim that no review will ever reference the outage — only that none did as of this pull. It also differs deliberately from our earlier FIFA 22 server-shutdown post, which measured review sentiment settling in after a permanent, pre-announced shutdown; this measures the first few hours after a brief, unscheduled, already-resolved outage, and the finding here is about how long that particular channel takes to respond, not about what it eventually says.

Pull app-store, social and search data across platforms yourself

App Store, Google Play, Reddit, X and Google Trends — all through one API, called live, no manual browsing. 2,000 free credits a month, no card required.

Reddit APIGoogle Trends APIPricing