GentFromAlaska From United States of America, joined Feb 2005, 3119 posts, RR: 1 Posted (1 year 1 day 6 hours ago) and read 3931 times:
I noticed today (Wednesday) UA has a departing flight 726 which operates DCA-IAH. Which is in flight which my wife happens to be on as I write. Connecting in IAH to a ANC flight later today.
F9 also operates an inbound flight # 726 between DEN-DCA. F9 flight # 726 is in DCA airspace or landing at about the same time UA 726 is taxiing out or would have just departed. Both are A319
From an ATC perspective is having two airlines operating the same flight numbers (except for the company designator) at on or over the same airport at the same time on the same equipment an accident waiting to happen?
Last year I saw WN flying two flights with the same flight number into PVD. The second was to replace a delayed aircraft at PVD. One flight was PVD-BWI while the other was a good 2 hours out flying from either RSW or FLL to PVD.
[Edited 2013-08-28 09:45:17]
[Edited 2013-08-28 10:00:10]
[Edited 2013-08-28 10:39:08]
Man can be taken from Alaska. Alaska can never be taken from the man.
TimRees From United Kingdom, joined Aug 2001, 354 posts, RR: 0
Reply 1, posted (1 year 1 day 6 hours ago) and read 3821 times:
Quoting GentFromAlaska (Thread starter): From an ATC perspective is having to airlines operating the same flight numbers (except for the company designator) at on or over the same airport at the same time on the same equipment an accident waiting to happen?
More and more often European carriers use alpha-numeric call-signs to avoid this problem. If you look at flight radar 24 or similar you will see just how many aircraft use these call-signs. They seem much less used in other parts of the world however, except when a flight is operating long-haul. BA uses such call-signs into the US as does VS.
GCT64 From United Kingdom, joined Nov 2007, 1389 posts, RR: 1
Reply 2, posted (1 year 1 day 6 hours ago) and read 3821 times:
In Europe, where a specific flight number conflict has been reported by pilots/ATC etc. as possibly leading to some confusion, the airlines have changed to an alphanumeric callsign for ATC (while retaining the flight number for pax).
This has now reached the point where, for example, most FR flights are now alphanumeric. Some examples (currently airborne over the UK):
atcsundevil From Germany, joined Mar 2010, 1199 posts, RR: 2
Reply 3, posted (1 year 1 day 4 hours ago) and read 3541 times:
ATC typically will notify supervisors of similar call signs so that the carriers can be notified if there's a trend. You're right in that similar sounding call signs can be dangerous, not to mention annoying having to notify all aircraft on frequency of the similar call signs. Those issues are typically resolved fairly quickly if they're scheduled flights.
ytib From United States of America, joined Nov 2004, 571 posts, RR: 1
Reply 4, posted (1 year 1 day 4 hours ago) and read 3496 times:
When listening to channel 9 on UA, I have noticed every so often if there is an aircraft with the same flight number on frequency or even close they will announce that to both airlines. Something like "United 1234 caution American 1234 also on frequency"
roseflyer From United States of America, joined Feb 2004, 9611 posts, RR: 52
Reply 6, posted (1 year 1 day 4 hours ago) and read 3309 times:
If similar sounding flight numbers are on the same frequency at the same time, the controller will typically notify the pilots of each airplane. This sometimes varies based on workload of the controller.
If the same call sign may end up in the air at the same time or within a short period of time, typically a letter is added to one of the call signs. United 726 and then United 726Charlie so that there wouldn’t be any confusion.
If you have never designed an airplane part before, let the real designers do the work!
wagz From United States of America, joined Mar 2003, 516 posts, RR: 16
Reply 7, posted (1 year 1 day 2 hours ago) and read 3061 times:
Funny story I can add to this.
I work in ATC at PHL. For a few months a year or so ago there were both AA and US flights numbered 1776 (airlines love employing that number at PHL for obvious reasons) arriving around the same time. The kicker is, they both operated DFW-PHL at almost exactly the same time. So almost every day they'd at least both be in our airspace at the same time. On several occasions I actually worked them both back to back over the arrival fix. Our arrival flight strips don't show the origin point or anything else besides an arrival fix, so I actually found out from one of the crews that they both originated at DFW. I advised one of them that the other would be on frequency momentarily and mentioned that "you probably already heard them back on Washington Center's frequency". Their response was along the lines of "Yeah, we've been following them all the way here since we took off at Dallas".
That went on for months until US was forced to change the flight number (we were told AA apparently had that flight number on that route first). AWE1776 changed to some other flight at another time of day after that, but I just saw AAL1776 arriving the other day.
Officially our rule book says in this situation we should repeat the airline callsign as in "American 1776 American", but nothing is a perfect solution as pilots will still sometimes take the wrong instruction even when the flight number isn't the same but sounds similar.
I think Big Foot is blurry, Its not the photographers fault. Theres a large out of focus monster roaming the countryside
skipness1E From United Kingdom, joined Aug 2007, 3238 posts, RR: 1
Reply 8, posted (1 year 1 day 1 hour ago) and read 2996 times:
ATC in the US use a differing terminology. At LHR we used to have AA173 and AA137 on frequency at the same time and we still have AC889 and AC899. In the UK the numbers are to be said seperately so "one three seven" and "one seven three" sound confusingly similar. However Stateside it's "one thirty seven heavy" and "one seventy three heavy" which don't sound the same at all. Oddly enough, BA still hang onto their old callsigns / flight numbers as much as possible whereas easyJet and Ryanair are alpha numeric.
GentFromAlaska From United States of America, joined Feb 2005, 3119 posts, RR: 1
Reply 9, posted (1 year 1 day 1 hour ago) and read 2978 times:
Quoting wagz (Reply 7): Their response was along the lines of "Yeah, we've been following them all the way here since we took off at Dallas".
I've noticed on flghtaware.com 800 feet and 1,100 feet seem to be the two most commonly used altitudes separating two airframes flying in the same direction and operating in the same vicinity of each other. I realize there other variables
To bad the flight you speak of couldn't have been separated by 1776 feet ATC response could have been yeah and you're following them separated by 1776 feet. You almost have to think a controller has thought about it.
Man can be taken from Alaska. Alaska can never be taken from the man.
NBGSkyGod From United States of America, joined May 2004, 811 posts, RR: 1
Reply 12, posted (1 year 22 hours ago) and read 2740 times:
The other day I had two aircraft, a G4 and a King Air going to the same place, the same route, and same altitude, and their transponder codes and CID's were transposed. The only difference was the tail number and type aircraft.
"I use multi-billion dollar military satellite systems to find tupperware in the woods."
Speedbird128 From Pitcairn Islands, joined Oct 2003, 1648 posts, RR: 2
Reply 14, posted (12 months 1 day 3 hours ago) and read 2280 times:
Quoting GentFromAlaska (Thread starter): From an ATC perspective is having two airlines operating the same flight numbers (except for the company designator) at on or over the same airport at the same time on the same equipment an accident waiting to happen?
It is dangerous when crews don't pay attention even after being warned there are similar callsigns on frequency.
I regularly used to have Etihad 455, KLM 455, and Singapore 455 on freq at the same time. Strangely enough it was always the same airline i renamed XXX999. LOL.
If I get more than "was that for us" transmission over a proper readback then I rename the flight. And that's the confusion solved.