Sptv From United States of America, joined Dec 2000, 136 posts, RR: 0 Posted (13 years 6 months 2 weeks 2 days 11 hours ago) and read 2161 times:
I flew yesterday (7/19) on AA764 from LAX to Montreal. This is considered a direct, one-stop flight thru ORD. There is a change of planes in ORD, from a 738 to a 738.
1) why is this listed with only one flight number, even though in reality it is a connecting flight?
2) on my flight, we left LA two hours late due to weather in Chicago. Flight 764 from ORD to Montreal, however, left ORD on time, while we were still in the air (as flight 764) from LAX to ORD. Does this mean that AA operated two different flight 764s simultaneously? Is this legal? Is it safe?
OPNLguy From , joined Dec 1969, posts, RR:
Reply 1, posted (13 years 6 months 2 weeks 2 days 11 hours ago) and read 2131 times:
Lots of WX/ATC probs at ORD yesterday, and what it sounds like is that they "stubbed" the ORD-Montreal portion of the flight on-time with a different aircraft. If so, it would have been filed as similar number (like, say, adding 6000 to the flight number, i.e. 6764) to avoid ATC conflicts. Such a flight number modification may or may not have been mentioned to the passengers, as it probably confuses them more than it explains to them.
On a normal day, the same 738 aircraft would have just stopped in ORD before proceding to Montreal...
Pilottim747 From United States of America, joined Jul 2001, 1607 posts, RR: 5
Reply 3, posted (13 years 6 months 2 weeks 2 days 10 hours ago) and read 2092 times:
Some airlines do keep to the literal terms of a 1-stop flight (no change of planes) as I think AA intended in your case. I'll bet (as they mentioned above) that they just found an extra aircraft that could be used for the second portion of the flight to make those passengers happy.
I have, however, noticed some airlines using the same flight number, stopping, and making passengers change planes. For example, United Airlines currently has a direct flight to Sydney, Australia from Chicago O'Hare. It uses a B757 to LAX then changes to a B744 to SYD. My aunt and uncle where on this flight back to Australia but it got delayed in ORD (weather, of course). To their surprise their plane had already left when they got to LAX. Similar situation, but worse. They had to wait 24 hours until the next flight to SYD from LAX.
Aviation Photographers & Enthusiasts--Coordinate your life.
AAR90 From United States of America, joined Jan 2000, 3510 posts, RR: 46
Reply 4, posted (13 years 6 months 2 weeks 2 days 2 hours ago) and read 2067 times:
> why is this listed with only one flight number, even though
>in reality it is a connecting flight?
It _became_ a connecting flight because the LAX departure was delayed 1+28. Rather than delay all other pax, crew and flights the rest of the day, AA decided to "stub" the second leg with a different aircraft (crew change was already planned). This minimizes effects of delays as much as possible.
>on my flight, we left LA two hours late due to weather in Chicago.
1 hour 28 minutes late departure. 1 hour 17 minutes late arrival. At least according to the computer.
>Flight 764 from ORD to Montreal, however, left ORD on time,
>while we were still in the air (as flight 764) from LAX to ORD.
>Does this mean that AA operated two different flight 764s simultaneously?
Nope, the ORD-YUL flight operated as AA764x [x being a letter suffix "stubbed" onto all paperwork, flight plans and callsigns].
>Is this legal? Is it safe?
Yes and yes. Happens fairly regularly to all U.S. airlines this time of year. Some airlines add a suffix letter while others change flight numbers completely. In all cases, the information distributed to passengers remains the same (no new names/numbers to confuse the customers).
*NO CARRIER* -- A Naval Aviator's worst nightmare!
OPNLguy From , joined Dec 1969, posts, RR:
Reply 6, posted (13 years 6 months 2 weeks 1 day 18 hours ago) and read 2046 times:
>>>One question is still open:
- Why do airlines assign one flight number to what is really a connexion?
The only situation where I've seen this occur is when there is a "gauge change" involved, i.e., a change in aircraft type. For instance, Doofus Air flight 123 from MIA-IAH-LAX-HNL. It might be a narrowbody from MIA-IAH-LAX, and then a widebody from LAX-HNL (or wherever). With the advent of longer-range twins in the last 20 years, you really don't see this much, but I guess it still occurs in various places around the planet.
A more common occurence of a single flight number becoming a "connection" is when a scheduled through-flight (or direct flight, if you prefer) transits an airline's hub and the aircraft's schedule for te day must be changed to accomodate maintenance planning, or other operational variables.
For example, flight 123 runs LAX-DFW-JFK, and flight 456 runs SFO-DFW-MIA, and both will be on the ground at DFW at the same time. Assuming a perfect world, the JFK and MIA folks will stay on their respective aircraft as it transits DFW. If, say, 123's aircraft were to develop a problem that precluded using it from DFW-JFK (thunderstorms at JFK, and the weather radar inop), the aircraft would be (assuming it couldn't be fixed at DFW) swapped to the DFW-MIA flight, presuming no storms there. The DFW-JFK flight would continue with the aircraft that came in from SFO.
Thus, both sets of pax now have "connections" at DFW, but it wasn't necessarily originally planned that way, as most of this stuff is dynamic. Some these "broken through trips" are not dynamic, and are planned a couple of days in advance to accomodate overnight maintenance requirements (like maybe MIA was a MX base, and JFK wasn't), but they are almost never communicated to the pax, since everything is so subject to change...