IndustryInsider From United States of America, joined Oct 2010, 31 posts, RR: 0 Posted (5 years 6 months 1 week 1 day 20 hours ago) and read 7368 times:
The aviation industry as a whole cannot schedule anymore than 9999 flight numbers per carrier code. With all the alliances, joint business agreements and codeshares within the industry, how are the major airlines allocating (conserving) their flight numbers? Specifically, how do Delta Airlines, United and American Airlines allocate and/or conserve their flight numbers knowing that each codeshare flight requires one flight number?
I know some airlines such as American Eagle have tried doing out and back flights using the same flight number, but are other airlines doing this too? What are the implications of this practice with codeshare flights? For example, can British Airways' internal systems handle the association between a BA marketing flight number on an out and back AA operating flight number? Can codeshare flight numbers, let's say a hypothetical UA codeshare on FRA-MUC-FRA be assigned as an out and back (e.g. UA 8877 FRA-MUC and UA 8877 MUC-FRA) even thought the LH operating flight has two different flight numbers?
What would prevent a carrier, let's use Delta as an example, from creating a secondary carrier code specifically for codeshare/alliance expansion? Let's say Delta would have a DL carrier code and a D2 carrier code which would be seen as one and the same but would allow Delta to double the number of codeshares available today. Is that type of step even possible/needed?
OH-LGA From Denmark, joined Oct 1999, 1436 posts, RR: 18
Reply 1, posted (5 years 6 months 1 week 1 day 4 hours ago) and read 7004 times:
United uses a lot of different ways of assigning and utilizing available flight numbers in their available range, some practices which I've seen other airlines use as well. (I'm using flight numbers from today for example's sake)
Out-and-back numbers are quite common, but usually only used in United Express flight number ranges (ie UA6923 SFO-ACV-SFO)
Also, "thru" flight numbers (ie UA930 SAN-SFO-LHR and UA931 LHR-SFO-LAX) save on separate flight numbers as well. In some cases they stretch even further, like UA839 which is assigned to ORD-LAX-SYD-MEL. This sort of flight number assignment has seen widespread deployment in UAX operations recently, offering SAT-SFO-YYJ under UA7024, or YHZ-ORD-ATL under UA7561, for example. While the allocated flight numbers on through flights or out-and-backs are always assigned to the same United Express carrier, change-of-gauges (COGs) are common (I've seen a SLC-SFO-SBA flight number allocated to SkyWest with a CRJ700 for the first leg and a EMB-120 for the second leg).
You can also find a limited number of flight numbers which look as if they operate hub-to-hub, but stop in an intermediate location. UA6414, for example, operates DEN-TUL-ORD.
On the codeshare side of things, airlines do have to be selective in which flights they would place codeshare numbers on if they are conserving their available numbers. A way to stretch these numbers is to place one codeshare number to match a "thru" flight number of the operating carrier. A current example would be CO6062, which overlays UA930 on the same routing SAN-SFO-LHR.
It is probably technically possible to use a single codeshare number on an out-and-back even though the operating carrier utilizes different numbers on those legs, but in practice I haven't seen it myself.
Assigning duplicate IATA 2-letter codes for the same airline purely for expansion purposes poses a problem mainly because the majority of the codes are already assigned to airlines around the world. IATA designators identify an airline for ALL commercial purposes, not just limited to flight numbers but also on tickets, airline tariff displays in ARC filings and GDS systems, and telecommunications (for example telex messaging). Overlapping in certain areas would prove costly. Plus it would be confusing for passengers.. In this case it would be smartest to just use the operating carrier rather than assigning a secondary identifier for codeshare purposes only.
Because all the combinations are for the most part completely assigned, IATA currently utilizes a "controlled duplicate" system where smaller airlines in different regions of the world are assigned the same two-letter code, to ensure that they cannot be mistaken for one another.
Airlines in alliances, JV agreements, etc. don't always have to put their flight number on every single leg, as fare filings' "flight applications" usually permit travel on other alliance members with their own code (usually seen with something like "ANY LH FLIGHT OPERATED BY LH" under a UA-filed transatlantic fare, for example), thus decreasing the need for additional codeshare number usage, while still providing the passenger benefit for a single filed through fare from origin to destination, along with airline loyalty program harmonization/cooperation.
Head in the clouds... yet feet planted firmly on the ground.