Flight profile · United Airlines

UA2636

Cleveland (CLE) to Orlando (MCO) · scheduled 8:00 AM – 10:27 AM

This page describes how UA2636 has historically performed, which is a different and more useful question when you are deciding what to book. The live position below is a reading from receivers on the ground, not flight status. For today’s status, check with United Airlines.

How UA2636 performs

972 operations, July 2023 – July 2026.

On-time arrivals
92.2%
883 of 958 completed
Cancellation rate
1.34%
13 cancelled
Median arrival delay
-13 min
Average -6.2 min
Severe delays
2.7%
Arrived 60+ minutes late
Delay when late
76 min
Average, when 15+ min late
Departure punctuality
93.5%
Left the gate on time

UA2636 arrived on time 92.2% of the time, against 77.5% for all CLE → MCO flights, so this departure is 14.7 percentage points better than the route as a whole. Against United Airlines’ own flights on this route it is 3.3 points better.

Source: US DOT Bureau of Transportation Statistics · 972 operations, July 2023 – July 2026 · If UA2636 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.

What stands out

How UA2636 compares to other flight numbers, not just to itself.

Every day of the week performs about the same on this flight, steadier than 98% of 1,710 comparable flight numbers.

93.1% on time on the best day (Thursday) against 89.6% on the worst (Saturday).

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · The one thing about this specific departure that ranks most extreme against every other published flight number, out of everything FlyerIntel checks — shown only when something clears a real statistical bar, not for every flight.

Where UA2636 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 UA2636 right now, if receivers on the ground are hearing it. Nothing is requested until you press the button.

Against the rest of the route

Against the rest of the route
Flight or routeOn timeCancelledMedian delaySevereFlights
UA263692.2%1.34%-13 min2.7%972
United Airlines on CLE → MCO88.9%1.17%-12 min3.9%1,799
All CLE → MCO flights77.5%1.59%-9 min9.2%6,545

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026

Why UA2636 runs late

Where US DOT attributed the delay minutes on this flight.

Share of the delay minutes US DOT attributed to each cause for UA2636 on CLE → MCO. 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 UA2636 comes in late, and what that does to the departure.

Inbound aircraft late
21%
141 of 673 departures came in 15+ minutes late
Scheduled time on the ground
9.7 hours
Median at CLE between the inbound and this departure
Left 15+ late after a late inbound
11%
141 departures
Left 15+ late after an on-time inbound
4%
532 departures

UA2636 is usually the aircraft’s first flight of the day: the schedule gives it a median of 9.7 hours on the ground at CLE, so its “inbound” is mostly the aircraft’s arrival the evening before.

When the aircraft came in 15 or more minutes late, UA2636 pushed back an average of 3 minutes late; when it came in on time or early, an average of 4 minutes early.

Each departure is matched to the flight the same aircraft flew into CLE just before it, using the tail number in the DOT file, 673 of 960 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

UA2636 against all flights with a scheduled turn of 6 hours or more, usually overnight
Share of departuresInbound landed 15+ lateLeft 15+ late after a late inboundLeft 15+ late after an on-time inbound
UA263621%11%4%
Network, same turn29%12%9%

A night on the ground absorbs most of a late arrival, so a late inbound matters far less on a turn this long than on a same-day one.

The network row is every flight with a scheduled turn of 6 hours or more, usually overnight. How often UA2636’s aircraft landed 15 or more minutes late is lower than the network’s and, once the aircraft was late, how often UA2636 left 15 or more minutes late is about the same as 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 CLE late, does that still matter by the time it reaches MCO?

Leaves the gate
0.1 minutes late
Average over 960 pushbacks
Taxi out at CLE
15.4 min
16.0 min for the airport in this hour
Taxi in at MCO
7.9 min
10.9 min for a typical MCO arrival
Reaches the gate at MCO
6.2 minutes early
Average over 958 arrivals

UA2636 pushes back an average of 0.1 minutes late and reaches the gate at MCO an average of 6.2 minutes early. The 6.3 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 15.4 minutes on the taxiways at CLE is about what any departure from the airport in that hour spends.

On arrival at MCO, UA2636 spends 7.9 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 2.9 minutes shorter than a typical MCO arrival (10.9 min).

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 MCO. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 8,603 departures from CLE scheduled in the clock hour UA2636 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at MCO (498,229 flights), not just UA2636’s own. More on taxi time.

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026

The hour it leaves CLE

Part of any flight’s record belongs to the clock rather than to the flight. UA2636 has one departure time, so this is what that time is worth.

UA263692.2%
All CLE departures, 8 AM–9 AM86.2%
All CLE departures, whole day80.9%

On-time arrival rate. 8,603 departures from CLE are scheduled in the 8 AM–9 AM hour over the period, against 126,883 across the whole day.

UA2636 is scheduled out of CLE at 8:00 AM, in the 8 AM–9 AM bank. Departures from CLE in that hour arrive on time 86.2% of the time against 80.9% across the airport’s whole day — the slot alone is worth 5.3 points better before anything about this particular flight is considered.

The two airport figures cover every departure from CLE 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.

By day of week

Does UA2636 run worse on particular days?

Monday92.3%
Tuesday—
Wednesday92.7%
Thursday93.1%
Friday93.0%
Saturday89.6%
Sunday91.6%

Thursday is historically the most reliable day and Saturday the least, a gap of 3.5 percentage points.

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · Days with fewer than 120 operations are not scored.

Other routes UA2636 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.

Other routes UA2636 has flown
RouteOperatedFlightsOn time
DEN→ONT Denver to OntarioSeptember 30, 2025 – October 21, 20254—
RSW→DEN Fort Myers to DenverSeptember 30, 2025 – October 21, 20254—
PHX→LAX Phoenix to Los AngelesAugust 19, 20251—
IAH→SFO Houston to San FranciscoJanuary 7, 2025 – February 12, 202537—
MCO→IAH Orlando to HoustonJune 27, 2024 – January 6, 202511065.4%
IAH→LAS Houston to Las VegasDecember 19, 2024 – January 6, 202518—
IAH→SAT Houston to San AntonioOctober 27, 2024 – December 2, 202437—

Because the same number has served different journeys, the statistics above describe only the route UA2636 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.

One arrival in ten is worse than

8 min late

against a median of 13 min early

Arrived an hour or more late2.7%
Typical delay when late76 min
Cancelled1.34%
Landed somewhere else0.10%

Percentiles over 972 operations; cancelled and diverted flights are counted separately.

Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026

Other flights on this route

Same airports, same journey, different odds of arriving on time.

Other flights on this route
FlightAirlineOn timeMedian arrivalOperations
UA2636 this flightUnited Airlines92.2%13 min early972
F92668Frontier Airlines79.7%10 min early627

Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. UA2636 is placed in the same ordering rather than left out of it; the rows around it are the most punctual departures on the route, not all of them, so this is a comparison and not a rank. Schedules change; confirm the departure still operates before booking around this.

Data and methodology

Calculated by FlyerIntel from 972 records of UA2636 operating CLE → MCO, 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