There are two Boston-bound flights that get into Logan around the same time each day. One is Aer Lingus 137 from Dublin. ATC calls this ‘13 Tango.’
The other is BA 213 from London. ATC calls this ‘13 Golf.’
I realize that ATC does this to avoid some sort of perceived ‘confusion’ while both are aloft.
But in this case, haven’t they made things worse rather than better?
Moderators: jsumali2, richierich, ua900, PanAm_DC10, hOMSaR
BOS-bound ‘13G’ And ‘13T’ same time with BA and EI
Next Trip:
JAL 7-8 BOS-NRT-BOS, 787-9
September
JAL 7-8 BOS-NRT-BOS, 787-9
September
Re: BOS-bound ‘13G’ And ‘13T’ same time with BA and EI
I'd have thought so, yes. At airports much busier than BOS the controllers seem to work just fine by using the real flight number and callsign not some locally made-up hybrid number.
Hard to confuse Shamrock 137 with Speedbird 213, I'd have thought, and that's exactly why callsigns exist worldwide.
Hard to confuse Shamrock 137 with Speedbird 213, I'd have thought, and that's exactly why callsigns exist worldwide.
Re: BOS-bound ‘13G’ And ‘13T’ same time with BA and EI
It would be in both airlines' interest to change both flight numbers.
-
- BostonBeau
- Posts: 547
- Joined:
Re: BOS-bound ‘13G’ And ‘13T’ same time with BA and EI
Confusion of flight numbers does happen (https://www.youtube.com/watch?v=b26NcJCLZl4). In the specific instance you cite, however, I would assume "13 Tango" is preceded by callsign Shamrock, and "13 Golf" by callsign "Speedbird" which lessens the possible confusion. I would REALLY get concerned if flights 4975, 4957 and 4579 were landing at the same time 
Re: BOS-bound ‘13G’ And ‘13T’ same time with BA and EI
It is not some locally made up hybrid callsign... It is the callsign assigned to the flights by BA and Aer Lingus. A simple look at FR24 or any ADSB tracker can confirm what they are sending out as callsign.
It might not even be for differentiation between these two flights, but with another flight around the same time. For example, I see a Southwest flight WN3317 that could be confused with 137 and there is perhaps something similar going on with the BA. Either way, having a different letter spoken clearly at the end of the callsign is a much more distinctive way to recognize if you are being talked to.
It might not even be for differentiation between these two flights, but with another flight around the same time. For example, I see a Southwest flight WN3317 that could be confused with 137 and there is perhaps something similar going on with the BA. Either way, having a different letter spoken clearly at the end of the callsign is a much more distinctive way to recognize if you are being talked to.
-
- GalaxyFlyer
- Posts: 6702
- Joined:
Re: BOS-bound ‘13G’ And ‘13T’ same time with BA and EI
Usually ATC, will day something like, “Shamrock 13T, there’s Speedbird 13G on the frequency. Over the ocean, it’s all CPDLC, much less chance of an error.
-
- Thenoflyzone
- Posts: 3047
- Joined:
Re: BOS-bound ‘13G’ And ‘13T’ same time with BA and EI
The callsigns could also have changed due to similar sounding callsigns at their departure airports in Europe. Not BOS.
us Air Traffic Controllers have a good record, we haven't left one up there yet !!
Re: BOS-bound ‘13G’ And ‘13T’ same time with BA and EI
Would have thought BAW13G(BA213) would be designated that to avoid potential confusion with BA217 and BA173 which depart at the same time from LHR.
Who is online
Users browsing this forum: 747classic, 747cllipper747, 9lflyguy, aaway, aerace, airzim, Antarius, B-HOP, behramjee, berty320, Bigant0408, capejet, CRJ200flyer, Cyrus, davies2911, dr1980, dstblj52, DylanHarvey, eastafspot, flight152, floridaflyboy, fsnuffer, GmoneyCO, Google Adsense [Bot], hvusslax, ILNFlyer, Joeblow, Jshank83, LHA320, lightsaber, MAH4546, MIflyer12, MrBren, n515cr, Niteflyr, NYCAAer, OGLOBAL, onwFan, Opus99, ORDPlanesTrains, OzarkD9S, Q, RalXWB, Raventech, Rookie87, ROSSIGNOL, sdbelgium, Spacepope, timf, tphuang, TWFlyGuy, ytib and 234 guests