Flight profile · Republic Airways
YX3540
Washington (IAD) to Pittsburgh (PIT) · scheduled 10:05 PM – 11:15 PM
How YX3540 performs
686 operations, May 2024 – July 2026.
YX3540 arrived on time 80.0% of the time, against 84.8% for all IAD → PIT flights, so this departure is 4.8 percentage points worse than the route as a whole. Against Republic Airways’ own flights on this route it is 4.4 points worse.
Source: US DOT Bureau of Transportation Statistics · 686 operations, May 2024 – July 2026 · If YX3540 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where YX3540 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 YX3540 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 |
|---|---|---|---|---|---|
| YX3540 | 80.0% | 2.19% | -8 min | 7.6% | 686 |
| Republic Airways on IAD → PIT | 84.4% | 1.58% | -9 min | 5.8% | 2,209 |
| All IAD → PIT flights | 84.8% | 1.42% | -8 min | 5.6% | 2,811 |
Source: FlyerIntel analysis of US DOT BTS data · May 2024 – July 2026
Why YX3540 runs late
Where US DOT attributed the delay minutes on this flight.
the inbound aircraft was late, so this flight started late
crew, maintenance, boarding and fueling, all within the carrier’s control
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 YX3540 on IAD → PIT. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering May 2024 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies YX3540 comes in late, and what that does to the departure.
The aircraft flying YX3540 came in 15 or more minutes late on 17% of the departures where its previous flight is known. There are not enough departures in both groups to say how the flight left after a late one and after an on-time one.
Each departure is matched to the flight the same aircraft flew into IAD just before it, using the tail number in the DOT file, 587 of 671 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 |
|---|---|
| YX3540 | 17% |
| Network, same turn | 18% |
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 45 to 59 minutes. How often YX3540’s aircraft landed 15 or more minutes late is about the same as the network’s. There are not enough departures in both groups to compare how it left.
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 May 2024 – July 2026
From pushback to gate
When it leaves IAD late, does that still matter by the time it reaches PIT?
YX3540 pushes back an average of 12.5 minutes late and reaches the gate at PIT an average of 7.2 minutes late. The 5.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. It spends 18.8 minutes on the taxiways at IAD, 2.0 minutes shorter than a typical IAD departure in the same hour.
On arrival at PIT, YX3540 spends 6.0 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 PIT 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 PIT. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 17,830 departures from IAD scheduled in the clock hour YX3540 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at PIT (132,905 flights), not just YX3540’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · May 2024 – July 2026
The hour it leaves IAD
Part of any flight’s record belongs to the clock rather than to the flight. YX3540 has one departure time, so this is what that time is worth.
On-time arrival rate. 17,830 departures from IAD are scheduled in the 10 PM–11 PM hour over the period, against 170,208 across the whole day.
YX3540 is scheduled out of IAD at 10:05 PM, in the 10 PM–11 PM bank. Departures from IAD in that hour arrive on time 78.7% of the time against 81.0% across the airport’s whole day, so the hour YX3540 leaves in is an ordinary one for IAD and explains nothing about its record either way.
The two airport figures cover every departure from IAD 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 · May 2024 – July 2026 · Hours below 120 departures are not scored.
Other routes YX3540 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 |
|---|---|---|---|
| LGA→IAD New York to Washington | March 31, 2024 – March 27, 2026 | 72 | — |
| ILM→EWR Wilmington to Newark | November 2, 2025 – December 1, 2025 | 27 | — |
| ORF→IAD Norfolk to Washington | June 26–30, 2025 | 5 | — |
| SYR→EWR Syracuse to Newark | January 7, 2025 – February 12, 2025 | 37 | — |
| ORD→ROC Chicago to Rochester | December 3–18, 2024 | 16 | — |
| EWR→MDT Newark to Harrisburg | January 9, 2024 – March 30, 2024 | 80 | — |
| MHT→EWR Manchester to Newark | July 1, 2023 – January 8, 2024 | 164 | 94.3% |
| EWR→DCA Newark to Washington | October 2–27, 2023 | 22 | — |
| EWR→ILM Newark to Wilmington | July 1–30, 2023 | 30 | — |
Because the same number has served different journeys, the statistics above describe only the route YX3540 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.
46 min late
against a median of 8 min early
Percentiles over 686 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering May 2024 – July 2026
Data and methodology
Calculated by FlyerIntel from 686 records of YX3540 operating IAD → PIT, 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