Originally Posted by
zdcatc12
So the "ID" in this case means Ireland as opposed to "I/D" which means International-Domestic. Thank you. I didn't know that the missing "/" meant that.
No, sorry, that's not what I meant.
Code:
STANDARD.D/D...D/I...I/D...I/I.
ONLINE .55 1.00 1.30 1.30
OFFLINE .55 1.00 1.30 1.30
** OR * ARE ALL
DL-DL ID 1.25 ALL - YYC 26DEC18 - INF
DL-DL ID 1.55 HAV - ALL
DL-DL ID 1.30 LOS - ALL
DL-DL ID 1.00 COUNTRY IE - ALL
DL-DL ID 1.25 02JUN20 - INF
**-DL ID SUP CDS N/A - ** HAV - ALL
**-DL ID SUP HAV - ALL
DL-** ID SUP CDS ** - N/A HAV - ALL
DL-** ID GLSUP CDS ** - N/A ALL - COUNTRY RU 26FEB22 - INF
DL-** ID SUP HAV - ALL
DL-** ID GLSUP ALL - COUNTRY RU 26FEB22 - INF
This is the first set of rows from the MCT table at ATL, filtered for I/D and DL-DL. There is no distinction in the EF format between "I/D" and "ID".
The baseline rule for ATL as an airport, failing all else, is 1h30 for an I/D connection.
The next most specific rule is that any I/D connection online in DL (that is DL to DL) has an MCT of 1h25, if made on/after 02-Jun-20. This is the prevailing rule for most cases.
There are more specific rules for Ireland arrivals ("Country IE"), Havana arrivals (HAV - ALL), and so-on. You'll note that some of these lines aren't actually applicable, since connecting to YYC isn't ID and you can't actually fly from HAV on DL right now.
The last lines suppress connections from HAV or to Russia, which likely aren't possible anyway (due to lack of flights operating to/from ATL) but exist just in case in order to comply with US regulations.