Flight profile · American Airlines
AA2568
Dallas–Fort Worth (DFW) to San Diego (SAN) · scheduled 10:59 PM – 11:59 PM
How AA2568 performs
826 operations, July 2023 – July 2026.
AA2568 arrived on time 57.5% of the time, against 66.3% for all DFW → SAN flights, so this departure is 8.8 percentage points worse than the route as a whole. Against American Airlines’ own flights on this route it is 8.5 points worse.
Source: US DOT Bureau of Transportation Statistics · 826 operations, July 2023 – July 2026 · If AA2568 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where AA2568 is right now
A live reading, only if you ask for it. It is not part of the reliability record above.
Ask for the position of AA2568 right now, if receivers on the ground are hearing it. Nothing is requested until you press the button.
Against the rest of the route
| Flight or route | On time | Cancelled | Median delay | Severe | Flights |
|---|---|---|---|---|---|
| AA2568 | 57.5% | 3.87% | 9 min | 14.4% | 826 |
| American Airlines on DFW → SAN | 66.0% | 2.20% | 2 min | 11.7% | 9,764 |
| All DFW → SAN flights | 66.3% | 2.16% | 2 min | 11.9% | 11,019 |
AA2568 has cancelled 3.87% of its scheduled departures (32 of 826), against 2.16% for all DFW → SAN flights — this specific departure cancels 1.7 percentage points more often than the route as a whole. Different flight numbers on the same route can carry different aircraft, crews and schedules, so this is a fact about AA2568 specifically, not about the route it flies.
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026
Why AA2568 runs late
Where US DOT attributed the delay minutes on this flight.
crew, maintenance, boarding and fueling, all within the carrier’s control
the inbound aircraft was late, so this flight started late
airspace and airport capacity, including weather-driven flow control
weather severe enough to stop this flight specifically
Share of the delay minutes US DOT attributed to each cause for AA2568 on DFW → SAN. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies AA2568 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, AA2568 pushed back an average of 61 minutes late; when it came in on time or early, an average of 20 minutes late.
Each departure is matched to the flight the same aircraft flew into DFW just before it, using the tail number in the DOT file, 748 of 795 departures in all. A departure is left out when that flight is unknown, was cancelled or diverted, or the aircraft had sat for more than 12 hours. A flight the airline cancelled never left and is not in the count, and one flown by a substitute aircraft is matched to the aircraft that flew it, not to the one first planned.
Against the network at the same turn length
| Share of departures | Inbound landed 15+ late | Left 15+ late after a late inbound | Left 15+ late after an on-time inbound |
|---|---|---|---|
| AA2568 | 34% | 74% | 27% |
| Network, same turn | 17% | 68% | 9% |
The schedule leaves a normal turn: enough time to clean and board if the aircraft is on time, little to spare if it is not.
The network row is every flight with a scheduled turn of 60 to 89 minutes. How often AA2568’s aircraft landed 15 or more minutes late is higher than the network’s and, once the aircraft was late, how often AA2568 left 15 or more minutes late is higher than the network’s.
More: Which Flight Numbers Pay for a Late Aircraft lists the flight numbers that pass a late aircraft on.
Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026
From pushback to gate
When it leaves DFW late, does that still matter by the time it reaches SAN?
AA2568 pushes back an average of 42.2 minutes late and reaches the gate at SAN an average of 36.5 minutes late. The 5.7 minutes between those two figures are slack the published schedule already carries, which is why a late pushback on this flight does not reliably become a late arrival. Its 18.2 minutes on the taxiways at DFW is about what any departure from the airport in that hour spends.
On arrival at SAN, AA2568 spends 5.6 min taxiing from touchdown to the gate — ground time a connecting passenger sits through before they can even leave the aircraft, on top of however late the flight itself ran. That is about what any arrival at SAN spends on the ground before reaching the gate.
Departure delay is averaged over every pushback and arrival delay over every completed arrival, so the two counts differ by the flights that never reached SAN. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 39,456 departures from DFW scheduled in the clock hour AA2568 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at SAN (297,664 flights), not just AA2568’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026
The hour it leaves DFW
Part of any flight’s record belongs to the clock rather than to the flight. AA2568 has one departure time, so this is what that time is worth.
On-time arrival rate. 39,456 departures from DFW are scheduled in the 10 PM–11 PM hour over the period, against 961,718 across the whole day.
AA2568 is scheduled out of DFW at 10:59 PM, in the 10 PM–11 PM bank. Departures from DFW in that hour arrive on time 65.7% of the time against 73.1% across the airport’s whole day — the slot alone is worth 7.4 points worse before anything about this particular flight is considered.
The two airport figures cover every departure from DFW to every destination, so they describe the slot rather than this journey — the like-for-like comparison against the route is above. Hours are scheduled local, and a number whose schedule moved between banks inside the period has no single hour and is not described here at all. Why the hour matters.
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · Hours below 120 departures are not scored.
Other routes AA2568 has flown
A flight number is a slot in a schedule, and carriers reassign it. These are the other city pairs this number served in the analysis period.
| Route | Operated | Flights | On time |
|---|---|---|---|
| PHL→PBI Philadelphia to West Palm Beach | January 6, 2026 – February 11, 2026 | 37 | — |
| PBI→PHL West Palm Beach to Philadelphia | January 6, 2026 – February 11, 2026 | 37 | — |
| FLL→PHL Fort Lauderdale to Philadelphia | December 3–17, 2025 | 15 | — |
| PHL→FLL Philadelphia to Fort Lauderdale | December 3–17, 2025 | 15 | — |
Because the same number has served different journeys, the statistics above describe only the route AA2568 currently operates. Blending them would produce an average of two different flights.
When it goes wrong
The average describes a usual day. This is the day that ruins a connection.
81 min late
against a median of 9 min late
AA2568 has an average that understates its risk: a typical arrival is 9 min late, but the worst tenth are 72 minutes worse than that. If the trip has something unmissable at the end of it, the median is the wrong number to plan against.
Percentiles over 826 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026
Data and methodology
Calculated by FlyerIntel from 826 records of AA2568 operating DFW → SAN, published by the US DOT Bureau of Transportation Statistics. A flight counts as delayed when it arrives 15 or more minutes after schedule. Cancelled and diverted flights are excluded from the on-time rate and reported separately. Flight numbers are resolved as carrier plus number plus route, because the same number serves different routes over time.
Full methodology · Data sources · Report a problem
Related research: Most and Least Reliable Flight Numbers · The Delay You Inherit · Making Up Time in the Air
Analysis last recomputed