[[{"id":1,"title":"Overview","content":""},{"id":2,"title":"Area 1","content":"\n\n\tArea Of Specialization 1\n\n"},{"id":3,"title":"Area 2","content":"\n\n\tArea Of Specialization 2\n\n"},{"id":4,"title":"Area 3","content":"\n\n\tArea Of Specialization 3\n\n"},{"id":5,"title":"Area 4","content":"\n\n\tArea Of Specialization 4\n\n"},{"id":6,"title":"Area 5","content":"\n\n\tArea Of Specialization 5\n\n"},{"id":7,"title":"Area 6","content":"\n\n\tArea Of Specialization 6\n\n"},{"id":8,"title":"Area 7","content":"\n\n\tArea Of Specialization 7\n\n"}],[{"id":9,"title":"Sectorization","content":"\n\n\tZTL Ultra High\n\n\n\n\t\n\n\n\tZTL High\n\n\n\n\t\u00a0\n\n\n\tZTL Low\n\n\n\n\t\n"},{"id":11,"title":"Sectorization","content":""}],[{"id":10,"title":"Salem 42","content":"\n\n\tSalem 42 120.725\n\n\n\n\t\n\t\tSECTOR NARRATIVE\n\t\n\n\t\n\t\tThe Salem Sector is a high sector with altitude limits from FL240 to FL340. This sector serves as a transition sector for departing air traffic from the Charlotte Douglas (CLT) airport as well as providing spacing for aircraft arriving to the Atlanta Hartsfield Jackson (ATL) and CLT airports.\n\t\n\n\t\n\t\tASSIGNMENT OF AIRSPACE\n\t\n\n\t\n\t\tSalem is open on Sector 42 continuously. During the midnight configuration, Pulaski sector is combined with Salem at Sector 42.\n\t\n\n\t\n\t\tPROCEDURES \n\t\n\n\t\n\t\ta. Arrivals\n\t\n\n\t\n\t\t1.\u00a0Charlotte Arrivals:\n\t\n\n\t\n\t\t(a)\u00a0CLT turbojet arrivals from the Burne Sector must be released to Salem east of\u00a0VXV for speed control and turns and\n\t\n\n\t\n\t\ti. CLT North Operation: Cross the Salem\/Burne boundary at orbelow FL330\n\t\n\n\t\n\t\tii. CLT South Operation: Cross the Salem\/Burne boundary at or below FL290, or lowest available altitude FL330 and below\n\t\n\n\t\n\t\t(b)\u00a0Arrivals to CLT and CLT Satellite Airports are released for turns up to 20degrees from the Salem Sector. Point outs to adjacent sectors are the responsibility of the Shine Sector. The Shine Sector may issue a pilot\u2019s discretion clearance (this includes crossing restriction clearances) from FL240 or above without first coordinating with Salem Sector.\n\t\n\n\t\n\t\t(c)\u00a0Traffic permitting, Salem must issue the descend via clearance to aircraft on the FILPZ arrivals. For aircraft issued the descend via clearance, Sector 42 shall enter an appropriate altitude and initiate a hand-off to Shine. The CLT altimeter shall be issued with the descend via clearance.\n\t\n\n\t\n\t\tEither Shine or Salem may choose to suspend descend via operations. For aircraft not descending via, Salem shall descend aircraft to FL240 and initiate a hand-off to Shine.\n\t\n\n\n\n\t\n\t\t2.\u00a0Arrivals to the Nashville Terminal Area (BNA, MQY, JWN, MBT) from the Salem Sector shall cross the Salem\/Burne boundary at or below FL300 traffic permitting. The Baden Sector shall hand these aircraft off to the Salem Sector in sufficient time for this to be accomplished.\n\t\n\n\t\n\t\t3.\u00a0Aircraft inbound to CHA, operating on or north of a line from PSK to GQO, shall be descended to FL350 and handed off to the SALEM Sector in sufficient time for the aircraft to cross the Salem\/Burne boundary at or below FL300.\n\t\n\n\t\n\t\t4.\u00a0Upon completion of radar handoff and communications transfer, Salem Sector shall have control for speed adjustment on all ATL arrivals within 20 miles of the Salem boundary from Pulaski.\n\t\n\n\t\n\t\t5.\u00a0Upon completion of radar handoff and communications transfer, Lanier Sectorshall have control for turns direct to OZZZI\/ONDRE intersection and speed control for all ATL arrivals within 15NM of the Lanier boundary from Salem.\n\t\n\n\t\n\t\t6.\u00a0The Bristol Sector may issue a pilot\u2019s discretion clearance (this includescrossing restriction clearances) to aircraft on the RCTOR STAR from FL240 or above without first coordinating with Salem Sector.\n\t\n\n\t\n\t\tb. Departures\n\t\n\n\t\n\t\tNo departure procedures have been identified for this sector.\n\t\n\n\t\n\t\tc. Additional Procedures\n\t\n\n\t\n\t\tNo additional procedures have been identified for this sector.\n\t\n\n\t\n\t\t\n\t\t\t\n\t\t\t\t\n\t\t\t\t\td. Automated Information Transfer\n\t\t\t\t\n\t\t\t\n\n\t\t\t\n\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t1.\u00a0Aircraft transitioning from the first initiating Georgia High, Spartanburg, Charlotte, Salem or Pulaski sector through the second intermediate Georgia High, Spartanburg, Charlotte, Salem or Pulaski sector, then into the third completion Georgia High, Spartanburg, Charlotte, Salem or Pulaski sector, and whose projected route of flight lies within the lateral confines of that circle of airspace within a 15 miles radius of a point defined by the Lat\/Long 353745.00N\/0812610.00W, known as the \u201cQuad Sector\u201d boundary of Pulaski, Charlotte, Georgia High and Salem sectors, will be handled as follows:\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t(a)\u00a0The first initiating sector will begin a handoff to the second intermediate sector.\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t(b)\u00a0The second intermediate sector will accept handoff and immediatelyinitiate handoff to the third completion sector.\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\n\n\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t(c)\u00a0When the first initiating sector observes the third completion sector has accepted the handoff, the first initiating sector will transfer communications the third completion sector and coordinate pertinent flight plan information with the third completion sector.\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t(d)\u00a0If the third completion sector has not accepted the handoff prior to the aircraft reaching the first initiating sector boundary, the first initiating sector will put the aircraft on the second intermediate sector frequency.\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t(e)\u00a0If the second intermediate sector requires communications with the aircraft, they will request communications from the first initiating sector prior to accepting the handoff and the first initiating sector will coordinate pertinent flight plan information with the second intermediate sector.\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t2.\u00a0Aircraft inbound to either GSP, SPA, GMU, or GYH that are transitioning toArea 1 from Area 7 in the high stratum shall be handled as follows:\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t(a)\u00a0Aircraft shall be descended by the Burne Sector to FL240, withoutpilot\u2019s discretion, and handed off to the Salem Sector.\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t(b)\u00a0The Salem Sector, traffic permitting, shall accept the handoff and immediately initiate a handoff to the Bristol Sector.\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t(c)\u00a0After observation by the Burne Sector that the Bristol Sector has accepted the handoff, the Burne Sector shall transfer communication and pertinent control information to the Bristol Sector.\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t3.\u00a0Turboprop arrivals inbound to CLT and CLT satellites that are transitioningto Area 1 from Area 7 in the high stratum shall be handled as follows:\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t(a)\u00a0Aircraft shall be descended by the Burne Sector so as to cross the Burne\/Salem boundary at FL240.\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t(b)\u00a0The Salem sector, traffic permitting shall accept the handoff and immediately initiate a handoff to the Bristol sector.\n\t\t\t\t\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t(c)\u00a0After observation by the Burne sector that Bristol sector has accepted the handoff, the Burne sector shall transfer communications and pertinent control information to the Bristol sector.\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\t\n\n\t\n\t\t\n\t\t\t\n\t\t\t\tMILITARY OPERATIONS\n\t\t\t\n\t\t\n\t\n\n\t\n\t\t\n\t\t\t\n\t\t\t\t\n\t\t\t\t\tAerial Refueling Route\n\t\t\t\t\n\n\t\t\t\t\n\t\t\t\t\tAR216 SOT MOA\n\t\t\t\t\n\t\t\t\n\t\t\n\t\n\n\n\n\t\n\n"},{"id":12,"title":"Pulaski 43","content":"\n\n\tPulaski 43 132.975\n\n\n\n\t\n\t\tSECTOR NARRATIVE\n\t\n\n\t\n\t\tThe Pulaski Sector is a high sector with altitude limits from FL240 to FL340. This sector serves as a transition sector for the Charlotte and Greensboro airports. There are a number of other smaller airports underlying the Pulaski Sector that transition to create traffic conflictions. Pulaski also provides spacing for traffic arriving at Atlanta airport.\n\t\n\n\t\n\t\tASSIGNMENT OF AIRSPACE\n\t\n\n\t\n\t\tPulaski is open on Sector 43 from 0645 - 2215 local. During the midnight configuration, Pulaski is combined with Salem at Sector 42.\n\t\n\n\t\n\t\tPROCEDURES\n\t\n\n\t\n\t\ta. Arrivals.\n\t\n\n\t\n\t\t1. Charlotte:\n\t\n\n\t\n\t\t(a)\u00a0Turbojet arrivals to CLT and CLT satellite airports shall be cleared via the appropriate routings as described in the Atlanta ARTCC and Charlotte ATCT LOA. CLT arrivals from ZID shall be cleared via the PARQR or the BTSEY STAR and delivered at or below FL330.\n\t\n\n\t\n\t\t(b)\u00a0Traffic permitting, Pulaski must issue the descend via clearance to aircraft on the PARQR arrivals. For aircraft issued the descend via clearance, Sector 43 shall enter an appropriate altitude and initiate a hand-off to Moped. The CLT altimeter shall be issued withthe descend via clearance.\n\t\n\n\t\n\t\tEither Moped or Pulaski may choose to suspend descend via operations. For aircraft not descending via, Pulaski shall descend aircraft to FL240 and initiate a hand-off to Moped.\n\t\n\n\t\n\t\t(c)\u00a0Arrivals to CLT and CLT Satellite Airports are released for turns up to 20degrees from the Pulaski Sector. Point outs to adjacent sectors are the responsibility of the Moped Sector. The Moped Sector may issue a pilot\u2019s discretion clearance (this includes crossing restriction clearances) from FL240 or above without first coordinating with Pulaski Sector.\n\t\n\n\t\n\t\t2. Upon completion of radar handoff and communications transfer, Salem Sector shall have control for speed adjustment on all ATL arrivals within 20 miles of the Salem boundary from Pulaski.\n\t\n\n\n\n\t\n\t\tb. Departures\n\t\n\n\t\n\t\tNo departure procedures have been identified for this sector.\n\t\n\n\t\n\t\tc. Additional Procedures\n\t\n\n\t\n\t\tNo additional procedures have been identified for this sector.\n\t\n\n\n\n\t\n\t\td. Automated Information Transfer\n\t\n\n\t\n\t\t1. Aircraft transitioning from Area 2 through the Pulaski or Baden Sector to ZDCwhose projected route of flight will remain within the lateral confines of that airspace between 5 miles west of the centerline of Q69 and the TETL\/ZDC center boundary will be handled asfollows:\n\t\n\n\t\n\t\t(a)\u00a0High Rock or Charlotte Sector will initiate handoff to Pulaski or Baden Sector.\n\t\n\n\t\n\t\t(b)\u00a0Pulaski or Baden will accept handoff and immediately initiate handoff to ZDC.\n\t\n\n\t\n\t\t(c)\u00a0When High Rock or Charlotte Sector observe ZDC has accepted the handoff, High Rock or Charlotte Sector will transfer communications to ZDC and coordinatepertinent flight plan information with ZDC.\n\t\n\n\t\n\t\t(d)\u00a0If ZDC has not accepted the handoff prior to the aircraft reaching the High Rock or Charlotte Sector boundary, Area 2 will transfer communications to the Pulaski, Salem or Baden Sector frequency.\n\t\n\n\t\n\t\t(e)\u00a0If Pulaski or Baden Sector requires communications with the aircraft, they will request communications from High Rock or Charlotte Sector prior to accepting the handoffand the High Rock or Charlotte Sector will coordinate pertinent flight plan information with the Pulaski, Salem or Baden Sector.\n\t\n\n\t\n\t\t(f)\u00a0Aircraft involved must remain within appropriate sector stratum at level flight.\n\t\n\n\t\n\t\t2. Aircraft transitioning from the first initiating Georgia High, Spartanburg, Charlotte, Salem or Pulaski sector through the second intermediate Georgia High, Spartanburg, Charlotte, Salem or Pulaski sector, then into the third completion Georgia High, Spartanburg, Charlotte, Salem or Pulaski sector, and whose projected route of flight lies within the lateral confines of that circle of airspace within a 15 miles radius of a point defined by the Lat\/Long 353745.00N\/0812610.00W, known as the \u201cQuad Sector\u201d boundary of Pulaski, Charlotte,Georgia High and Salem sectors, will be handled as follows:\n\t\n\n\t\n\t\t(a)\u00a0The first initiating sector will begin a handoff to the second intermediate sector.\n\t\n\n\t\n\t\t(b)\u00a0The second intermediate sector will accept handoff and immediatelyinitiate handoff to the third completion sector.\n\t\n\n\t\n\t\t(c)\u00a0When the first initiating sector observes the third completion sector has accepted the handoff, the first initiating sector will transfer communications the third completion sector and coordinate pertinent flight plan information with the third completion sector.\n\t\n\n\t\n\t\t(d)\u00a0If the third completion sector has not accepted the handoff prior to the aircraft reaching the first initiating sector boundary, the first initiating sector will put the aircraft on the second intermediate sector frequency.\n\t\n\n\t\n\t\t(e)\u00a0If the second intermediate sector requires communications with the aircraft, they will request communications from the first initiating sector prior to accepting the handoff and the first initiating sector will coordinate pertinent flight plan information with the second intermediate sector.\n\t\n\n\t\n\t\te. Pre-Arranged Coordination\n\t\n\n\t\n\t\tSector 43 is authorized to climb and turn, up to 15 degrees left or right of course, CLT and CLT satellite departures within the confines of Sector 33 airspace in that area above 47\/MOPED airspace without individual coordination provided the following requirements are met.\n\t\n\n\t\n\t\t1. The authorized sector must \u201cquick look\u201d the owning sector and maintain display of the owning sector\u2019s data blocks while utilizing the airspace.\n\t\n\n\t\n\t\t2. The authorized sector is responsible to provide radar separation, including wake turbulence separation, from all applicable traffic when utilizing this procedure.\n\t\n\n\t\n\t\t3. The authorized sector must PVD the data block of the aircraft transitioning the airspace to the owning sector.\n\t\n\n\t\n\t\tIf any of the above requirements are not met or at the request of either sector controller,\u00a0this procedure is canceled and individual coordination is required.\n\t\n\n\t\n\t\t\n\t\n\n"},{"id":13,"title":"Shine 44","content":"\n\n\tShine 44 132.625\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\tSECTOR NARRATIVE\n\t\t\t\n\n\t\t\t\n\t\t\t\tThe Shine Sector is a low sector with altitude limits from 17,000 feet to FL230 for the airspace overlying Charlotte ATCT (CLT), 11,000 feet to FL230 for the remainder of the airspace. This sector serves as an arrival sector for aircraft landing Charlotte airport as well as, surrounding approach control facilities.\n\t\t\t\n\n\t\t\t\n\t\t\t\tASSIGNMENT OF AIRSPACE\n\t\t\t\n\n\t\t\t\n\t\t\t\tShine is open on Sector 44 continuously. When traffic volume dictates, Moped sector is combined with Shine at Sector 44. During the midnight configuration Moped, Bristol and Wilkes are combined with Shine at Sector 44.\n\t\t\t\n\n\t\t\t\n\t\t\t\tPROCEDURES\n\t\t\t\n\n\t\t\t\n\t\t\t\ta. Arrivals\n\t\t\t\n\n\t\t\t\n\t\t\t\t1.\u00a0Charlotte:\n\t\t\t\n\n\t\t\t\n\t\t\t\t(a) Arrivals to CLT and CLT Satellite Airports are released for turns up to 20degrees from the Salem Sector. Point outs to adjacent sectors are the responsibility of the Shine Sector. The Shine Sector may issue a pilot\u2019s discretion clearance (this includes crossing restriction clearances) from FL240 or above without first coordinating with Salem Sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(b) Traffic permitting, Salem must issue the descend via clearance to aircraft on the FILPZ arrivals. For aircraft issued the descend via clearance, Sector 42 shall enter an appropriate altitude and initiate a hand-off to Shine. The CLT altimeter shall be issued with the descend via clearance.\n\t\t\t\n\n\t\t\t\n\t\t\t\tEither Shine or Salem may choose to suspend descend via operations. For aircraft not descending via, Salem shall descend aircraft to FL240 and initiate a hand-off to Shine.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(c) Turboprop arrivals to the CLT Terminal Area, above 13,000 feet, shall crossthe Bristol\/Shine sector boundary, at or below 17,000 feet descending to 13,000 feet. Pilot's discretion descent need not be coordinated on these aircraft.\n\t\t\t\n\n\t\t\t\n\t\t\t\t2.\u00a0Arrivals to GSO\/INT shall be descended to at least FL210. Arrivals from over SPA are released for right turns to the Moped Sector.\n\t\t\t\n\t\t\n\t\n\n\n\n\t\n\t\t\n\t\t\t3.\u00a0Hickory (HKY) and Statesville (SVH) arrivals shall be cleared via GENOD...destination, descended to 110 and handed off to SHINE sector.\n\t\t\n\n\t\t\n\t\t\t4. Aircraft landing GSP, GMU, SPA and GYH on the RCTOR STAR from the Bristol Sector to\u00a0the Shine Sector shall be handled as follows:\n\t\t\n\n\t\t\n\t\t\t(a)\u00a0Bristol Sector, traffic permitting, shall clear aircraft to cross the LUVTT intersection at 11,000.\n\t\t\n\n\t\t\n\t\t\t(b)\u00a0Bristol Sector shall initiate a handoff to the Shine Sector.\n\t\t\n\n\t\t\n\t\t\t(c)\u00a0Shine Sector shall accept the handoff and immediately initiate a handoff to AVL\n\t\t\n\n\t\t\n\t\t\tb. Departures\n\t\t\n\n\t\t\n\t\t\tUnarm shall clear GSP area departures to an altitude of 17,000 or lower and initiate a handoff to Shine. Upon handoff and transfer of communications, GSP area departures shall be released for climb and left turns or right turns no further than a 010 heading by the Unarm Sector.\n\t\t\n\n\t\t\n\t\t\tc. Additional Procedures\n\t\t\n\n\t\t\n\t\t\tNo additional procedures have been identified for this sector.\n\t\t\n\n\t\t\n\t\t\td. Automated Information Transfers\n\t\t\n\n\t\t\n\t\t\t1.\u00a0Aircraft landing GSP, GMU, SPA and GYH on the RCTOR STAR from the Bristol Sector to\u00a0the Shine Sector shall be handled as follows:\n\t\t\n\n\t\t\n\t\t\t(a)\u00a0Bristol Sector, traffic permitting, shall clear aircraft to cross the LUVTT intersection at 11,000.\n\t\t\n\n\t\t\n\t\t\t(b)\u00a0Bristol Sector shall initiate a handoff to the Shine Sector.\n\t\t\n\n\t\t\n\t\t\t(c)\u00a0Shine Sector shall accept the handoff and immediately initiate a handoff to AVL\u00a0Approach.\n\t\t\n\n\t\t\n\t\t\t(d)\u00a0When AVL approach accepts the handoff, Bristol Sector shall transfer communications to AVL Approach.\n\t\t\n\n\t\t\n\t\t\t(e)\u00a0If Shine Sector requires communication with the aircraft, Shine Sector shall request communications from the Bristol Sector prior to accepting the handoff.\n\t\t\n\n\t\t\n\t\t\t(f)\u00a0If AVL Approach has not accepted the handoff prior to the aircraft crossing the Bristol\/Shine boundary, Bristol will transfer communications to the Shine Sector.\n\t\t\n\n\t\t\n\t\t\te. Pre-Arranged Coordination\n\t\t\n\n\t\t\n\t\t\tSector 44 is authorized to control CLT departures assigned the JOJJO SID within the confines of Sector 47 airspace in that area above CLT ATCT airspace without individual coordination provided the following requirements are met.\n\t\t\n\t\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\t1.\u00a0The authorized sector must \u201cquick look\u201d the owning sector and maintain display of the owning sector\u2019s data blocks while utilizing the airspace.\n\t\t\t\n\n\t\t\t\n\t\t\t\t2.\u00a0The authorized sector is responsible to provide radar separation, including wake turbulence separation, from all applicable traffic when utilizing this procedure.\n\t\t\t\n\n\t\t\t\n\t\t\t\t3.\u00a0The authorized sector must PVD the data block of the aircraft transitioning the airspace to the owning sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\tIf any of the above requirements are not met or at the request of either sector controller or area supervisor, this procedure is cancelled and individual coordination is required.\n\t\t\t\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\t\n\n"},{"id":14,"title":"Bristol 45","content":"\n\n\tBristol 45 127.850\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\tSECTOR NARRATIVE\n\t\t\t\n\n\t\t\t\n\t\t\t\tThe Bristol Sector is a low sector with altitude limits from 11,000 feet to FL230 for the airspace overlying Ashville ATCT (AVL) and Tri-cities ATCT (TRI), from 13,000 feet to FL230 for the airspace overlying Knoxville ATCT (TYS), and from 7,000 feet to FL230 for the airspace overlying Roanoke ATCT (ROA). Elsewhere within the sector, the Bristol Sector altitude limits are from the surface to FL230. This sector has no predominant traffic flow, but is comprised of numerous aircraft traversing to and from approach control facilities. Bristol also contains several air refueling tracks and military training routes.\n\t\t\t\n\n\t\t\t\n\t\t\t\tASSIGNMENT OF AIRSPACE\n\t\t\t\n\n\t\t\t\n\t\t\t\tBristol is open on Sector 45 from approximately 0900-2230 local. When traffic volume dictates, Wilkes sector is combined with Bristol. During the midnight configuration, Bristol is combined with Shine, Moped, and Wilkes sectors at Sector 44.\n\t\t\t\n\n\t\t\t\n\t\t\t\tPROCEDURES\n\t\t\t\n\n\t\t\t\n\t\t\t\ta. Arrivals.\n\t\t\t\n\n\t\t\t\n\t\t\t\t1.\u00a0Charlotte Terminal Area: Turboprop arrivals to the CLT Terminal Area shall cross the Bristol\/Shine boundary at or below 17,000 feet descending to 13,000 feet.\n\t\t\t\n\n\t\t\t\n\t\t\t\t2.\u00a0Aircraft within 15 miles of the common sector boundary, transitioning to the Logen sector from the Bristol Sector and landing KATL are released for speed control without back coordination.\n\t\t\t\n\n\t\t\t\n\t\t\t\t3.\u00a0All Tri-City (TRI) arrivals from the Logen Sector shall be descending to 17,000 feet, traffic permitting, or at filed altitude, if lower. These aircraft shall be released for turns up to 15 degrees to the Bristol Sector upon receipt of communications transfer.\n\t\t\t\n\n\t\t\t\n\t\t\t\t4.\u00a0GSO Terminal Arrivals entering the Moped Sector shall be descended to FL210 or requested lower.\n\t\t\t\n\n\t\t\t\n\t\t\t\t5.\u00a0Aircraft executing instrument approach procedures at MKJ shall be coordinated with ROA ATCT, non-radar sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t6.\u00a0Arrivals to Southern Pines, NC (SOP) shall cross the Bristol\/Leeon boundary ator below FL210, traffic permitting.\n\t\t\t\n\n\t\t\t\n\t\t\t\t7.\u00a0Arrivals to Pope AFB, NC (POB) shall cross the Bristol\/Leeon boundaryat or below FL230, traffic permitting.\n\t\t\t\n\t\t\n\t\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\t8.\u00a0The Bristol Sector may issue a pilot\u2019s discretion clearance (this includes crossing restriction clearances) to aircraft on the RCTOR STAR from FL240 or above without first coordinating with Salem Sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t9.\u00a0Greensboro terminal arrivals on the SMOKN STAR shall be issued the appropriate crossing restriction as prescribed in the Atlanta ARTC Center\/GSO ATC Tower Letter of Agreement. The Bristol Sector will then initiate a radar handoff to the Leeon Sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\tb. Departures\n\t\t\t\n\n\t\t\t\n\t\t\t\tWhen SOT MOA is activated, TYS will assign VXV184 radial or VXV102 radial to remain clear of the MOA. Sector 45 is responsible for turning the aircraft on course.\n\t\t\t\n\n\t\t\t\n\t\t\t\tc. Additional Procedures\n\t\t\t\n\n\t\t\t\n\t\t\t\t1.\u00a0Aircraft inbound to either GSP, GYH, GMU, or SPA that are transitioning to Area 1 from Area 7 in the high stratum shall be handled as follows:\n\t\t\t\n\n\t\t\t\n\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(a)\u00a0Aircraft shall be descended by the Burne Sector to FL240, without pilot\u2019s discretion, and handed off to the Salem Sector.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(b)\u00a0The Salem Sector, traffic permitting, shall accept the handoff and immediately initiate a handoff to the Bristol Sector.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(c)\u00a0After observation by the Burne Sector that the Bristol Sector has accepted the handoff, the Burne Sector shall transfer communications and pertinent control information to the Bristol Sector.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t2.\u00a0Turboprop arrivals inbound to CLT and CLT satellites that are transitioning to Area1 from Area 7 in the high stratum shall be handled as follows:\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\n\t\t\t\n\n\t\t\t\n\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(a)\u00a0Aircraft shall be descended by the Burne Sectors as to cross the Burne\/Salem boundary at FL240.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(b)\u00a0The Salem sector, traffic permitting shall accept the handoff and immediately initiate a handoff to the Bristol sector.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(c)\u00a0After observation by the Burne sector that Bristol sector has accepted the handoff, the Burne sector shall transfer communications and pertinent control information to the Bristol sector.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t3.\u00a0Aircraft landing GSP, GMU, SPA and GYH on the RCTOR STAR from the Bristol Sector to the Shine Sector shall be handled as follows:\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(a)\u00a0Bristol Sector, traffic permitting, shall clear aircraft to cross the LUVTT intersection at 11,000.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(b)\u00a0Bristol Sector shall initiate a handoff to the Shine Sector.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(c)\u00a0Shine Sector shall accept the handoff and immediately initiate a handoff to AVL\u00a0Approach.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(d)\u00a0When AVL approach accepts the handoff, Bristol Sector shalltransfer communications to AVL Approach.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(e)\u00a0If Shine Sector requires communication with the aircraft, Shine Sector shall request communications from the Bristol Sector prior to accepting the handoff.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t(f)\u00a0If AVL Approach has not accepted the handoff prior to the aircraft crossingthe Bristol\/Shine boundary, Bristol will transfer communications to the Shine Sector.\n\t\t\t\t\t\t\n\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\t\n\n"},{"id":15,"title":"Moped 47","content":"\n\n\tMoped 47 134.550\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\tSECTOR NARRATIVE\n\t\t\t\n\n\t\t\t\n\t\t\t\tThe Moped Sector is a low sector with altitude limits from 17,000 feet to FL 230 in the airspace overlying Charlotte ATCT (CLT) and 11,000 to FL 230 in the remainder of the airspace. Moped serves as a north departure sector for Charlotte airport and an arriving sector for Greensboro airport and Hickory Regional Airport.\n\t\t\t\n\n\t\t\t\n\t\t\t\tASSIGNMENT OF AIRSPACE\n\t\t\t\n\n\t\t\t\n\t\t\t\tMoped is open on Sector 47 from approximately 0700-1900 local. When traffic dictates, Moped is combined with Shine at Sector 44. During the midnight configuration, Moped, Shine, Bristol, and Wilkes are combined at Sector 44.\n\t\t\t\n\n\t\t\t\n\t\t\t\tPROCEDURES\n\t\t\t\n\n\t\t\t\n\t\t\t\ta. Arrivals.\n\t\t\t\n\n\t\t\t\n\t\t\t\t1.\u00a0Arrivals to the GSP Terminal Area, operating at 17,000 feet or above, shall be routed via the SPA 080 radial to SPA then direct destination airport or via the JUNNR RNAV STAR. These aircraft shall cross the SPA 080039 fix or OPENS Waypoint at 17,000 feet, handed offand communications transferred to CLT Approach.\n\t\t\t\n\n\t\t\t\n\t\t\t\tNOTE: Upon handoff and communications transfer from Leeon Sector to the Moped Sector, turboprop and turbojet aircraft inbound to GSP, GMU, SPA, and GYH are released for right turns and descent at or below FL230.\n\t\t\t\n\n\t\t\t\n\t\t\t\t2.\u00a0Arrivals, operating 12,000 feet and below, to the GSP Terminal Area shall be routed via BZM.V20. GENOD.SPA.DESTINATION. These aircraft shall be descended to 11,000 feet and handed off to Sector 48.\n\t\t\t\n\n\t\t\t\n\t\t\t\t3.\u00a0Aircraft landing ROA shall be descended to 11,000 feet or the lowest available altitude and handed off to the Bristol Sector. Bristol Sector will have control for right turns.\n\t\t\t\n\n\t\t\t\n\t\t\t\t4.\u00a0ArrivalstoGSO\/INTfromoverSPAarereleasedforrightturnsfromtheShine Sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t5.\u00a0Charlotte:\n\t\t\t\n\n\t\t\t\n\t\t\t\t(a) Arrivals to CLT and CLT Satellite Airports are released for turns up to 20degrees from the Pulaski Sector. Point outs to adjacent sectors are the responsibility of the Moped Sector. The Moped Sector may issue a pilot\u2019s discretion clearance (this includes crossing restriction clearances) from FL240 or above without first coordinating with Pulaski Sector.\n\t\t\t\n\t\t\n\t\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\t(b) Traffic permitting, Pulaski must issue the descend via clearance to aircraft on thePARQR arrivals. For aircraft issued the descend via clearance, Sector 43 shall enter an appropriate altitude and initiate a hand-off to Moped. The CLT altimeter shall be issued with the descend via clearance.\n\t\t\t\n\n\t\t\t\n\t\t\t\tEither Moped or Pulaski may choose to suspend descend via operations. For aircraft not descending via, Pulaski shall descend aircraft to FL240 and initiate a hand-off to MOPED.\n\t\t\t\n\n\t\t\t\n\t\t\t\tb. Departures\n\t\t\t\n\n\t\t\t\n\t\t\t\t1.\u00a0CLT departures enroute to LYH and CHO, departing the KRITR gate will not be\u00a0turned on course until the aircraft has passed the CLT TCP.\n\t\t\t\n\n\t\t\t\n\t\t\t\t2.\u00a0Non-advanced NAV Turboprop and turbojet aircraft departing the GSOTerminal Area, filed north of the BOTTM DTA shall be cleared on course by the LEEONSector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t3.\u00a0Turboprop and turbojet aircraft departing the GSO Terminal Area, routed out the BOTTM DTA entering the MOPED sector shall be released for turns on course by the LEEON Sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\tException: GSO turboprop departures destined the GSP Terminal Area shall be the Moped Sector\u2019s control for a left turn not to exceed a 270 degree heading.\n\t\t\t\n\n\t\t\t\n\t\t\t\t4.\u00a0Departures from HKY and SVH that will enter Sector 29 (Leeon) airspace shall be assigned a heading to enter Sector 29 north of TRAKS intersection with heading entry into4th line. Sector 29 shall have control for turns on course.\n\t\t\t\n\n\t\t\t\n\t\t\t\tc. Additional Procedures.\n\t\t\t\n\n\t\t\t\n\t\t\t\t1.\u00a0Arrivals to Southern Pines, NC (SOP) shall cross the Area 1\/Leeon boundary at or\u00a0below FL210, traffic permitting.\n\t\t\t\n\n\t\t\t\n\t\t\t\t2.\u00a0Arrivals to Pope AFB, NC (POB) shall cross the Area 1\/Locas boundaryat or below FL230, traffic permitting.\n\t\t\t\n\n\t\t\t\n\t\t\t\td. Automated Information Transfers\n\t\t\t\n\n\t\t\t\n\t\t\t\tNo AIT procedures have been identified for this sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\t\n\n"},{"id":16,"title":"Wilkes 48","content":"\n\n\tWilkes 48 125.150\n\n\n\n\tSECTOR NARRATIVE\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\tThe Wilkes Sector is an ultra-low sector with altitude limits from the surface to 10,000 feet. Wilkes complexity is increased because of the mountainous terrain and multiple airports it provides approach control service to. Wilkes also controls traffic arriving into the Charlotte Terminal area and numerous military training routes. The majority of the traffic in the Wilkes Sector is non-scheduled.\n\t\t\t\n\n\t\t\t\n\t\t\t\tWilkes must continuously monitor the Hickory Clearance Delivery frequency, 124.25.\n\t\t\t\n\n\t\t\t\n\t\t\t\tASSIGNMENT OF AIRSPACE\n\t\t\t\n\n\t\t\t\n\t\t\t\tWilkes is open on Sector 48 from approximately 0900-1900 local. When traffic volume dictates, Wilkes is combined with Bristol at Sector 45. During the midnight configuration, Wilkes is combined with Bristol, Shine, and Moped Sectors at Sector 44.\n\t\t\t\n\n\t\t\t\n\t\t\t\tPROCEDURES\n\t\t\t\n\n\t\t\t\n\t\t\t\ta. Arrivals.\n\t\t\t\n\n\t\t\t\n\t\t\t\tArrivals to the GSP Terminal Area shall be routed clear of CLT ATCT delegated airspace.\n\t\t\t\n\n\t\t\t\n\t\t\t\tb. Departures.\n\t\t\t\n\n\t\t\t\n\t\t\t\tNo departure procedures have been identified for this sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\tc. Additional Procedures.\n\t\t\t\n\n\t\t\t\n\t\t\t\t1.\u00a0Aircraft entering AVL ATCT delegated airspace at or below 6,000 feet shall be\u00a0coordinated and non-radar approval obtained prior to entry.\n\t\t\t\n\n\t\t\t\n\t\t\t\t2.\u00a0Aircraft entering ROA ATCT Non-Radar Airspace, 6,000 feet and below, shall be coordinated non-radar prior to entry.\n\t\t\t\n\n\t\t\t\n\t\t\t\t3.\u00a0At Wilkes 48\u00a0where automated coordination with Hickory Tower is not available, the EDST Coordination Menu or Flight Progress Strips shall be used to annotate the status of manual coordination.\n\t\t\t\n\n\t\t\t\n\t\t\t\td. Automated Information Transfers.\n\t\t\t\n\n\t\t\t\n\t\t\t\tNo AIT procedures have been identified for this sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\t\n\n"}],[{"id":17,"title":"High Rock 28","content":"\n\n\tHigh Rock 28\u00a0125.025\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\tSECTOR NARRATIVE\n\t\t\t\n\n\t\t\t\n\t\t\t\tThe High Rock sector is an ultra-high sector with altitude limits from FL350 and above. The main traffic flow is south and southwest bound from Indianapolis and Washington Center. Special care should be exercised when vectoring aircraft. The jet stream can exceed 200 knots from the west and increase\/decrease aircraft speed dramatically.\n\t\t\t\n\n\t\t\t\n\t\t\t\tASSIGNMENT OF AIRSPACE\n\t\t\t\n\n\t\t\t\n\t\t\t\tHigh Rock is open on sector 28 from approximately 0830-2100 local. When traffic volume dictates, the western portion of High Rock combines with Georgia sector at Sector 34 (or Sector 32 if applicable) and the eastern portion combines with Charlotte sector at Sector 33. Charlotte will assume the High Rock frequencies 125.02\/291.75; all aircraft in the western portion of the airspace will be transferred to the appropriate frequency. During the midnight configuration, High Rock is combined with Spartanburg, Georgia, and Charlotte sectors at Sector 32.\n\t\t\t\n\n\t\t\t\n\t\t\t\tPROCEDURES \n\t\t\t\n\n\t\t\t\n\t\t\t\ta. Arrivals\n\t\t\t\n\n\t\t\t\n\t\t\t\t1.\u00a0High Rock will descend aircraft inbound to the Washington, D.C. area (IAD and NSF) to FL350 and initiate a handoff to the Charlotte High sector in time to allowthe aircraft to cross the Atlanta\/Washington Center boundary at FL330.\n\t\t\t\n\n\t\t\t\n\t\t\t\t2.\u00a0High Rock will descend aircraft landing the Atlanta Terminal Area via the DEHAN STAR, to FL350 and initiate a handoff to the Georgia High sector in time to allow the aircraft to cross the Lanier\/Georgia High sector boundary at or below FL300.\n\t\t\t\n\n\t\t\t\n\t\t\t\t3.\u00a0High Rock will descend aircraft landing Atlanta Hartsfield to FL350 and initiate a handoff to the Georgia High sector in time to allow the aircraft to cross the Lanier\/Georgia High sector boundary at or below FL340.\n\t\t\t\n\n\t\t\t\n\t\t\t\t4.\u00a0High Rock will descend aircraft inbound to Richmond (RIC) to FL350 and initiate a handoff to the Charlotte High sector in time to allow the aircraft to cross the Atlanta\/Washington Center boundary at FL290.\n\t\t\t\n\n\t\t\t\n\t\t\t\t5.\u00a0Aircraft landing at KTYS airport must cross the Lanier, High Rock,Georgia High common boundary at or below FL300.\n\t\t\t\n\t\t\n\t\n\n\n\n\t\n\t\tb. Departures\n\t\n\n\t\n\t\tNo departure procedures have been identified for this sector.\n\t\n\n\t\n\t\tc. Additional Procedures\n\t\n\n\t\n\t\tNo additional procedures have been identified for this sector.\n\t\n\n\t\n\t\td. Automated Information Transfer:\n\t\n\n\t\n\t\t1.\u00a0Aircraft transitioning from Area 2 through the Pulaski or Baden Sector to ZDC whose projected route of flight will remain within the lateral confines of that airspace between 5 miles west of the centerline of Q69 and the TETL\/ZDC center boundary will be handled as follows:\n\t\n\n\t\n\t\t(a)\u00a0High Rock or Charlotte Sector will initiate handoff to Pulaski or Baden Sector.\n\t\n\n\t\n\t\t(b)\u00a0Pulaski or Baden will accept handoff and immediately initiate handoff to ZDC.\n\t\n\n\t\n\t\t(c)\u00a0When High Rock or Charlotte Sector observe ZDC has accepted the handoff, High Rock or Charlotte Sector will transfer communications to ZDC and coordinate pertinent flight plan information with ZDC.\n\t\n\n\t\n\t\t(d)\u00a0If ZDC has not accepted the handoff prior to the aircraft reaching the High Rock or Charlotte Sector boundary, Area 2 will transfer communications to the Pulaski or Baden Sector frequency.\n\t\n\n\t\n\t\t(e)\u00a0If Pulaski or Baden Sector requires communications with the aircraft, they will request communications from High Rock or Charlotte Sector prior to accepting the handoff and the High Rock or Charlotte Sector will coordinate pertinent flight plan information with the Pulaski, Salem or Baden Sector.\n\t\n\n\t\n\t\t(f)\u00a0Aircraft involved must remain within appropriate sector stratum at level flight.\n\t\n\n\t\n\t\tMILITARY OPERATIONS\n\t\n\n\t\n\t\tNo military procedures have been identified for this sector.\n\t\n\n\t\n\t\t\n\t\n\n"},{"id":18,"title":"Leeon 29","content":"\n\n\tLeeon 29 128.800\n\n\n\n\tSECTOR NARRATIVEThe Leeon Sector is a low sector with altitude limits from 13,000 feet to FL230 in the airspace overlying Greensboro ATCT (GSO), 13,000 feet to FL270 underlying the CHSLY Shelf, 17,000 feet to FL 230 for the airspace overlying Charlotte ATCT (CLT). Leeon provides air traffic service primarily to arrivals into CLT and departures from GSO and Raleigh ATCT (RDU).\n\n\n\n\tASSIGNMENT OF AIRSPACELeeon is open on Sector 29 from approximately 0730-2130 local. When traffic volume dictates, Locus sector is combined with Leeon at Sector 29. During the midnight configuration, Leeon is combined with Locas and Unarm sectors at Sector 31.\n\n\n\n\tPROCEDURES\n\n\n\n\ta. Arrivals.\n\n\n\n\t1. Turbojet and turboprop aircraft inbound to GSP, GMU, SPA and GYH at or above 17,000 feet shall be placed on a heading that will intercept\u00a0the SPA080 radial prior to the Leeon\/Moped sector boundary or cleared via the JUNNR RNAV STAR. Leeon will descend the aircraft to FL200 or below and hand off to the Moped Sector. Upon handoff and communications transfer to the Moped Sector, these aircraft are released for\n\tright turns and descent at or below FL230.\n\n\n\n\t2. Arrivals to Southern Pines, NC (SOP) shall cross the Area 1\/Leeon boundary\n\tat or below FL210, traffic permitting.\n\n\n\n\t3. Arrivals to Pope AFB, NC (POB) shall cross the Area 1\/Leeon boundary at or\n\tbelow FL230, traffic permitting.\n\n\n\n\tb. Departures.\n\n\n\n\t1. Departures from HKY and SVH that will enter Sector 29 (Leeon) airspace shall be assigned a heading to enter Sector 29 north of TRAKS intersection with heading entry into 4th line. Sector 29 shall have control for turns on course.\n\n\n\n\t2. GSO Terminal Area departures entering the Moped\/Bristol Sectors:\n\n\n\n\t(a) Non-advanced NAV Turbojet and turboprop aircraft departing the GSO Terminal Area routed out the BOTTM DTA proceeding northbound shall be cleared on course by the Leeon Sector.\n\n\n\n\t(b) Turbojet and turboprop aircraft departing the GSO Terminal Area routed out the BOTTM DTA entering the MOPED sector shall be released for turns on course by the Leeon Sector. Exception: GSO turboprop departures destined the GSP Terminal Area shall be the Moped Sector\u2019s control for left turns not to exceed a 270 degree heading.\n\n\n\n\tc. Additional Procedures.\n\n\n\n\tNo additional procedures have been identified for this sector.\n\n\n\n\td. Automated Information Transfers\n\n\n\n\t1. Greensboro Terminal Area arrivals that will transition via the SMOKN Arrival Transition Area, shall be handled as follows:\n\n\n\n\t(a) The Bristol Sector shall issue the appropriate crossing restriction as prescribed in the GSO ATCT\/Atlanta ARTCC Letter of Agreement. Bristol shall then initiate a handoff to the Leeon Sector.\n\n\n\n\t(b) Leeon, traffic permitting, shall accept the handoff and immediately initiate a handoff to GSO ATCT. If Leeon needs to work the aircraft, Leeon shall coordinate an altitude with Bristol at which they can accept the aircraft.\n\n\n\n\t(c) When Bristol observes that GSO ATCT has accepted the handoff, Bristol shall transfer communications to GSO ATCT.\n\n\n\n\t2. Overflight aircraft transitioning through the CHSLY Shelf shall be handled as follows:\n\n\n\n\t(a) The Charlotte Sector will initiate a handoff to the LEEON sector.\n\n\n\n\t(b) Leeon, traffic permitting, shall accept the handoff and immediately initiate a handoff to the subsequent sector.\n\n\n\n\t(c) When Charlotte Sector observes the subsequent sector has accepted the handoff, Charlotte Sector will transfer communications to the subsequent sector and coordinate pertinent flight plan information with the subsequent sector.\n\n\n\n\t(d) If Leeon Sector requires communications with the aircraft, they will request communications from Charlotte Sector prior to accepting the handoff and the Charlotte Sector will coordinate pertinent flight plan information with Leeon.\n\n\n\n\t3. Greer Terminal arrivals at or above FL240 assigned the JUNNR STAR shall be handled as follows:\n\n\n\n\t(a) Charlotte Sector will initiate a handoff to the Leeon sector.\n\n\n\n\t(b) The Leeon Sector will accept the handoff, enter an altitude in the datablock that they can approve and immediately initiate a handoff to the Moped Sector.\n\n\n\n\t(c) The Charlotte Sector will assign the altitude entered into the datablock by the Leeon Sector, and when the handoff has been accepted by the Moped Sector, transfer communications to the Moped Sector.\n\n\n\n\t(d) If Leeon Sector requires communication with the aircraft, Leeon Sector shall request communications from the Charlotte Sector prior to accepting the handoff.\n\n\n\n\t\u00a0\n\n\n\n\tMILITARY OPERATIONS\n\tIR Routes:IR 721\n\n\n\n\tIR 719\n\n\n\n\tIR 082\/083\n\n\n\n\tIR 022\n\n\n\n\t\n\n"},{"id":19,"title":"Locas 30","content":"\n\n\tLocas 30 133.150\n\n\n\n\tSECTOR NARRATIVE \n\n\n\n\tThe Locas Sector is a low sector with altitude limits from 13,000 feet overlying Greensboro ATCT (GSO) and from 17,000 feet overlying Charlotte ATCT (CLT) to FL 230 under Charlotte High (33), from 13,000 feet to FL230 over GSO and under the CLT Shelf and from 17,000 to FL230 over CLT ATCT and the Gipper shelf. Locas provides air traffic service primarily to CLT departures.\n\n\n\n\tASSIGNMENT OF AIRSPACE \n\n\n\n\tLocas is open on Sector 30 from approximately 0730-2130 local. When traffic volume dictates, Locas is combined with Leeon sector at Sector 29. During the midnight configuration, Locas is combined with Leeon and Unarm Sectors at Sector 31.\n\n\n\n\tPROCEDURES \n\n\n\n\ta. Arrivals \n\n\n\n\t1. Arrivals to Pope AFB, NC (POB) shall cross the Moped\/Locas boundary at or below FL230, traffic permitting. \n\n\n\n\t2. Arrivals to Southern Pines, NC (SOP) shall cross the Moped\/Locas boundary at or below FL210, traffic permitting. \n\n\n\n\tb. Departures \n\n\n\n\tAn interim altitude of FL230, or the requested altitude if lower than FL230, will be displayed on all Charlotte Douglas International Airport Turbojet departures except departures on LILLS SID will display FL190 or requested altitude if lower. \n\n\n\n\tc. Additional Procedures \n\n\n\n\tNo departure procedures have been identified for this sector. \n\n\n\n\td. Automated Information Transfers \n\n\n\n\t1. BIMMR departures transitioning from Unarm through Locas to the Charlotte sector shall be handled as follows: \n\n\n\n\t(a) The Unarm Sector will initiate a handoff to the Locas sector. \n\n\n\n\t(b) Locas, traffic permitting, shall accept the handoff and immediately initiatea handoff to Charlotte. \n\n\n\n\t(c) When Unarm Sector observes Charlotte has accepted the handoff, Unarm Sector will transfer communications to Charlotte and coordinate pertinent flight plan information with Charlotte. \n\n\n\n\t(d) If Locas Sector requires communications with the aircraft, they will request communications from Unarm Sector prior to accepting the handoff and the Unarm Sector will coordinate pertinent flight plan information with Locas. \n\n\n\n\t2. Aircraft departing CLT terminal area transitioning from Locas sector through Columbia Low to Aiken sector filed at or above FL240 will be handled as follows: \n\n\n\n\t(a) Locas Sector will initiate handoff to Columbia Low Sector. \n\n\n\n\t(b) Columbia Low sector will accept handoff and immediately initiate handoff to Aiken sector. \n\n\n\n\t(c) When Locas Sector observes Aiken sector has accepted the handoff, Locas Sector will transfer communications to Aiken Sector and coordinate pertinent flight plan information with ZJX. \n\n\n\n\t(d) If Aiken sector has not accepted the handoff prior to the aircraft reaching the Locas Sector boundary, Locas will transfer communications to the Columbia Low Sector frequency. \n\n\n\n\t(e) If Columbia Low Sector requires communications with the aircraft, they will request communications from Locas Sector prior to accepting the handoff and the Locas Sector will coordinate pertinent flight plan information with the Columbia Low Sector.\u00a0\n\n\n\n\tMILITARY OPERATIONS \n\n\n\n\tIR Routes: \n\n\n\n\tIR 721 \n\n\n\n\tIR 718 \n\n\n\n\tIR 082\/083 \n\n\n\n\tIR022 \n\n\n\n\tMilitary Operating Areas: \n\n\n\n\tGamecock MOA\n\n\n\n\t\n\n"},{"id":20,"title":"Unarm 31","content":"\n\n\tUnarm 31 135.350\n\n\n\n\tSECTOR NARRATIVE\n\n\n\n\tThe Unarm Sector is a low sector with altitude limits from 17,000 feet to FL230 overlying Charlotte ATCT (CLT) and 11,000 feet to FL230 overlying Greer ATCT (GSP) and Ashville ATCT (AVL). This sector provides air traffic service primarily to CLT arrivals and departures. Complexity is high due to limited airspace capacity, high traffic volume and required spacing into the Charlotte Douglas Airport.\n\n\n\n\tASSIGNMENT OF AIRSPACE\n\n\n\n\tUnarm is open on Sector 31 continuously. When AVL closes at 2300 local, GSP assumes control of the AVL airspace underlying Unarm. When GSP closes at 2345local, Unarm assumes control of the airspace delegated to GSP and the underlying AVL airspace. During the midnight operation, Leeon and Locas sectors combine with Unarm at Sector 31.\n\n\n\n\tPROCEDURES \n\n\n\n\ta. Arrivals\n\n\n\n\t1. Hickory (KHKY) and Statesville (KSVH) arrivals must be cleared via:\n\n\n\n\t(a)\u00a0GENOD..destination, descended to 110 and handed off to SHINE sector,\n\n\n\n\tor\n\n\n\n\t(b)\u00a0UNARM direct CLT VOR direct destination, descended to 17,000 feet and handed off to CLT Approach.\n\n\n\n\t2.\u00a0Augusta Terminal Area (AGS) arrivals shall be cleared direct to the COLLIERS VORTAC (IRQ) direct destination airport and descended to cross 15 miles north of IRQ at 11,000 feet.\n\n\n\n\t3.\u00a0From Augusta and East Departure, props and turboprops inbound to the Charlotte Terminal Area shall be issued a restriction to cross GRD VORTAC at 11,000 feet and handed off to Unarm Sector.\n\n\n\n\t4.\u00a0Charlotte Arrivals:\n\n\n\n\t(a)\u00a0Pilot\u2019s discretion descents resulting from the issuance of a crossing restriction or a descend via clearance may be issued by Unarm Sector for aircraft landing within the CLT Terminal Area, which are transitioning from the Spartanburg Sector, without back coordination.\n\n\n\n\t(b)\u00a0At or north of J4\/52 shall be released for speed control and turns up to 30 degrees left or right to CHPTR\/DEBBT by sector 24.\n\n\n\n\t(c)\u00a0Spartanburg must issue the descend via clearance to aircraft on the JONZE and BANKR arrivals. For aircraft issued the descend via clearance, Sector 32 shall enter an appropriate altitude and initiate a hand-off to Unarm. The CLT altimeter shall be issued with the descend via clearance.\n\n\n\n\tEither Unarm or Spartanburg may choose to suspend descend via operations. For aircraft not descending via, Spartanburg shall descend aircraft to FL240 and initiate a hand-off to Unarm.\n\n\n\n\t5.\u00a0Arrivals to GSP Terminal Area via the MCHLN STAR; Augusta Low shall clear the aircraft to cross MCHLN at 11,000 feet. Aircraft not on MCHLN STAR shall cross the GSP boundary at 11,000 feet in accordance with the GSP LOA.\n\n\n\n\t6.\u00a0Aircraft within 15 miles of the common sector boundary, transitioning to the Logen sector from the Unarm Sector and landing KATL are released for speed control without back coordination.\n\n\n\n\tb. Departures.\n\n\n\n\t1.\u00a0Unarm shall clear GSP area departures to an altitude of 17,000 or lower and initiate a handoff to Shine. Upon handoff and transfer of communications, GSP area departures shall be released for climb and left turns or right turns no further than a 010 heading by the Unarm Sector.\n\n\n\n\t2.\u00a0An interim altitude of FL230, or the requested altitude if lower than FL230, will be displayed on all Charlotte Douglas International Airport turbojet departures.\n\n\n\n\t3.\u00a0When Snowbird MOA is active, Logen shall advise Unarm. CLT departures over BRAYN shall be assigned a heading of 260 degrees, except the aircraft that arefiled over HRS, and the heading will be in the 4th line of the data block.\n\n\n\n\tc. Additional Procedures\n\n\n\n\tNo additional procedures have been identified for this sector.\n\n\n\n\td. Automated Information Transfers\n\n\n\n\t1.\u00a0Slow climbing CLT departures climbing northwest bound shall be handled as\u00a0follows:\n\n\n\n\t(a)\u00a0UNARM Sector may flash the handoff on slow climbing jets to LOGEN Sector.\n\n\n\n\t(b)\u00a0If LOGEN does not wish to communicate with the aircraft, LOGEN will accept the handoff from UNARM, ensure an interim altitude of FL230 is displayed in the data block and immediately flash the handoff to LANIER Sector.\n\n\n\n\t(c)\u00a0When LANIER accepts the handoff, UNARM will transfer communications to LANIER.\n\n\n\n\t(d)\u00a0LOGENretainsresponsibilityforallfurthercoordinationuntiltheaircraft is established in LANIER\u2019s airspace.\n\n\n\n\t2.\u00a0Aircraft transitioning from CLT climbing over IPTAY intersection.\u00a0\n\n\n\n\t(a)\u00a0Unarm Sector should climb aircraft to FL230 when traffic permits and\u00a0initiate a handoff to East Departure Sector.\n\n\n\n\t(b)\u00a0Traffic permitting East Departure Sector should accept the handoff then immediately initiate a handoff to Spartanburg Sector.\n\n\n\n\t(c)\u00a0When Spartanburg sector accepts the handoff, Unarm Sector will transfer communication and any pertinent flight data to the Spartanburg.\n\n\n\n\t(d)\u00a0If East Departure Sector requires communication with the aircraft they should call Unarm Sector prior to accepting the handoff.\n\n\n\n\t3.\u00a0BIMMR departures transitioning from Unarm through the Locas to the Charlotte sector shall be handled as follows:\n\n\n\n\t(a)\u00a0The Unarm Sector will initiate a handoff to the Locas sector.\u00a0\n\n\n\n\t(b)\u00a0Locas, traffic permitting, shall accept the handoff and immediately initiate\u00a0a handoff to Charlotte.\n\n\n\n\t(c)\u00a0When Unarm Sector observes Charlotte has accepted the handoff, Unarm Sector will transfer communications to Charlotte and coordinate pertinent flight plan information with Charlotte.\n\n\n\n\t(d)\u00a0If Locas Sector requires communications with the aircraft, they will request communications from Unarm Sector prior to accepting the handoff and the Unarm Sector will coordinate pertinent flight plan information with Locas.\n\n\n\n\t4.\u00a0Augusta Terminal arrivals from Unarm Sector through Augusta Sector shall be handled as follows:\n\n\n\n\t(a)\u00a0The Unarm Sector will clear the aircraft to descend to 11,000, and initiate a handoff to the Augusta Sector.\n\n\n\n\t(b)\u00a0The Augusta Sector will accept the handoff and immediately initiate a handoff to AGS Approach.\n\n\n\n\t(c)\u00a0When AGS Approach accepts the handoff, Unarm Sector will transfer communications to AGS Approach.\n\n\n\n\t(d)\u00a0If Augusta Sector requires communication with the aircraft, Augusta Sector shall request communications from Unarm Sector prior to accepting the handoff.\n\n\n\n\t(e)\u00a0If AGS Approach has not accepted the handoff prior to the aircraft crossing the Unarm\/Augusta boundary, Unarm shall transfer communications to the Augusta Sector.\n\n\n\n\tMILITARY OPERATIONS\n\n\n\n\tIR Routes:\u00a0IR082\n\n\n\n\tMilitary Operating Areas:\u00a0Snowbird MOA-When Snowbird MOA is active, Logen shall advise Unarm. CLT departures over BRAYN shall be assigned a heading of 260 degrees, except the aircraft that are filed over HRS, and the heading will be in the 4th line of the data block.\n\n\n\n\t\n\n"},{"id":21,"title":"Spartanburg 32","content":"\n\n\tSpartanburg 32 125.625\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\tSECTOR NARRATIVE\n\t\t\t\n\n\t\t\t\n\t\t\t\tThe Spartanburg sector is a high sector with altitude limits from FL240 to FL290. Traffic is comprised of an overflight flow and departures from Atlanta and Charlotte transitioning into the enroute environment. The initial sequencing into the Charlotte Terminal Area is accomplished by this sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\tASSIGNMENT OF AIRSPACE\n\t\t\t\n\n\t\t\t\n\t\t\t\tSpartanburg is open on Sector 32 continuously. When traffic volume dictates, Georgia sector is combined with Spartanburg at Sector 32. During the midnight configuration, High Rock, Charlotte and Georgia Sectors combine with Spartanburg at Sector 32.\n\t\t\t\n\n\t\t\t\n\t\t\t\tWhen A80-Atlanta Sector is on a West operation, the airspace overlying J14\/37, designated as the Athens West Area FL240 to FL290, is assigned to Spartanburg sector and is depicted on the HIGHW map. Because Athens West Area is temporary, strips are not generated to Spartanburg for aircraft traversing this area. Dublin and Macon sectors must point-out aircraft that will enter this area.\n\t\t\t\n\n\t\t\t\n\t\t\t\tPROCEDURES \n\t\t\t\n\n\t\t\t\n\t\t\t\ta. Arrivals.\n\t\t\t\n\n\t\t\t\n\t\t\t\t1.\u00a0Turboprop and turbojet aircraft inbound to GSO\/INT shall be cleared via the appropriate arrival. These aircraft shall cross 30 miles northeast of SPA at FL240.\n\t\t\t\n\n\t\t\t\n\t\t\t\t2.\u00a0CAE terminal area arrivals (CAE\/CUB\/CDN)\n\t\t\t\n\n\t\t\t\n\t\t\t\t(a)\u00a0Arrivals to the CAE terminal area from Lanier, J99 and east, shall cross\u00a0the Lanier\/Spartanburg boundary at or below FL250.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(b)\u00a0Arrivals to the CAE terminal area from Lanier, west of J99, shall cross the Lanier\/Spartanburg boundary at or below FL290.\n\t\t\t\n\n\t\t\t\n\t\t\t\t3.\u00a0Arrivals to GSO and INT, south of a line GSO to GQO shall cross the Lanier\/Spartanburg boundary at or below FL290.\n\t\t\t\n\n\t\t\t\n\t\t\t\t4.\u00a0Arrivals to the Augusta Terminal Area (AGS, AIK, DNL, and HQU) at or above FL250 shall cross the Lanier\/Spartanburg boundary at FL250.\n\t\t\t\n\n\t\t\t\n\t\t\t\t5. CLT\u00a0Arrivals:\n\t\t\t\n\t\t\n\t\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\t(a)\u00a0At or north of J4\/52 shall be released for speed control and turns up to 30 degrees left or right to BANKR\/DEBBT by sector 20.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(b)\u00a0Pilot\u2019s discretion descents resulting from the issuance of a crossing restriction or descend via clearance may be issued by Unarm Sector for aircraft landing within CLT Terminal Area, which are transitioning from the SPA Sector, without back coordination.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(c)\u00a0Charlotte (CLT) area arrivals transitioning through the Dublin Sector shall be handled as follows:\n\t\t\t\n\n\t\t\t\n\t\t\t\t(1)\u00a0Aircraft on the BANKR STAR and shall cross PONZE at or below FL270. Spartanburg sector shall have control to issue the descend via clearance on aircraft assigned FL270. Spartanburg Sector shall have control for descent at (and north of) PONZE.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(2)\u00a0Aircraft on the CHPTR Star shall cross the Spartanburg boundary at or below FL270. Spartanburg Sector shall have control for descent north of\u00a0PONZE.(3)\u00a0Dublin sector will normally ensure at least 5 miles in-trail spacing\u00a0between subsequent CHPTR and BANKR arrivals.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(d)\u00a0Spartanburg must issue the descend via clearance to aircraft on the JONZE and BANKR arrivals. For aircraft issued the descend via clearance, Sector 32 shall enter an appropriate altitude and initiate a hand-off to Unarm. The CLT altimeter shall be issued with the descend via clearance.\n\t\t\t\n\n\t\t\t\n\t\t\t\tEither Unarm or Spartanburg may choose to suspend descend via operations. For aircraft not descending via, Spartanburg shall descend aircraft to FL240 and initiate a hand-off to Unarm.\n\t\t\t\n\n\t\t\t\n\t\t\t\t6.\u00a0Aircraft landing GSP overflying the Macon Sector shall cross the Macon\/Spartanburg Sector boundary at or below FL270.\n\t\t\t\n\n\t\t\t\n\t\t\t\t7.\u00a0AVL arrivals at or above FL250 from DBN sector shall cross 95 miles south of KAVL at or below FL240.\n\t\t\t\n\n\t\t\t\n\t\t\t\t8.\u00a0Non-advanced NAV CHS arrivals must cross the TETL\/ZJX common boundary at or below FL270. Advanced NAV CHS arrivals must cross WBODY at or below FL270.\n\t\t\t\n\n\t\t\t\n\t\t\t\t9.\u00a0Aircraft within 15 miles of the common sector boundary, transitioning to the Lanier sector from the Spartanburg or Georgia High Sector and landing KATL are released for speed control without back coordination.\n\t\t\t\n\n\t\t\t\n\t\t\t\t10.\u00a0Aircraft landing at KTYS airport must cross the Lanier, High Rock ,Georgia High common boundary at or below FL300.\n\t\t\t\n\t\t\n\t\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\tb. Departures\n\t\t\t\n\n\t\t\t\n\t\t\t\tNo departure procedures have been identified for this sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\tc. Additional Procedures.\n\t\t\t\n\n\t\t\t\n\t\t\t\tNo additional procedures have been identified for this sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\td. Automated Information Transfers.\n\t\t\t\n\n\t\t\t\n\t\t\t\t1.\u00a0En route aircraft operating on, or south of, a course Atlanta (ATL) direct Colliers (IRQ) or IRQ direct ATL, between FL240 and FL340, shall be handled as follows.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(a)\u00a0Eastbound Aircraft:\n\t\t\t\n\n\t\t\t\n\t\t\t\t(1)\u00a0The Macon Sector shall initiate a handoff to the Spartanburg (SPA)\u00a0Sector or the Georgia High (GA HI) Sector as appropriate.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(2)\u00a0Spartanburg\/Georgia High, traffic permitting, shall accept the handoff and immediately initiate a handoff to the Dublin Sector. If SPA\/GA HI requires communication with the aircraft, they shall request communications from the Macon Sector prior to accepting the handoff.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(3)\u00a0When the Macon Sector observes that the Dublin Sector has accepted the handoff, Macon shall transfer communications and any pertinent flight plan information to Dublin.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(b)\u00a0Westbound Aircraft\n\t\t\t\n\n\t\t\t\n\t\t\t\t(1)\u00a0The Dublin Sector shall initiate a handoff to the SPA\/GA HI Sector as appropriate.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(2)\u00a0Spartanburg\/Georgia High, traffic permitting, shall accept the handoff and immediately initiate a handoff to the Macon Sector. If SPA\/GA HI requires communication with the aircraft, they shall request communications from the Dublin Sector prior to accepting the handoff.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(3)\u00a0When the Dublin Sector observes that the Macon Sector has accepted the handoff, Dublin shall transfer communications and any pertinent flight plan information to Macon.\n\t\t\t\n\n\t\t\t\n\t\t\t\t2.\u00a0Aircraft transitioning from the first initiating Georgia High, Spartanburg, Charlotte, Salem or Pulaski sector through the second intermediate Georgia High, Spartanburg, Charlotte, Salem or Pulaski sector, then into the third completion Georgia\u00a0High, Spartanburg, Charlotte, Salem or Pulaski sector, and whose projected route of flight lies within the lateral confines of that circle of airspace within a 15 miles radius of a point defined by the Lat\/Long 353745.00N\/0812610.00W, known as the \u201cQuad Sector\u201d boundary of Pulaski, Charlotte, Georgia High and Salem sectors, will be handled as follows:\n\t\t\t\n\t\t\n\t\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\t(a)\u00a0The first initiating sector will begin a handoff to the second intermediate sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(b)\u00a0The second intermediate sector will accept handoff and immediately initiate handoff to the third completion sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(c)\u00a0When the first initiating sector observes the third completion sector has accepted the handoff, the first initiating sector will transfer communications the third completion sector and coordinate pertinent flight plan information with the third completion sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(d)\u00a0If the third completion sector has not accepted the handoff prior to the aircraft reaching the first initiating sector boundary, the first initiating sector will put the aircraft on the second intermediate sector frequency.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(e)\u00a0If the second intermediate sector requires communications with the aircraft, they will request communications from the first initiating sector prior to accepting the handoff and the first initiating sector will coordinate pertinent flight plan information with the second intermediate sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t3.\u00a0Aircraft transitioning from the first initiating Spartanburg or Charlotte sector through the Aiken sector then into the third completion Spartanburg or Charlotte sector, and whose projected route of flight lies within the lateral confines of the ZJX climb Shelf will be handled as follows:\n\t\t\t\n\n\t\t\t\n\t\t\t\t(a) ThefirstinitiatingsectorwillbeginahandofftotheAikensector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(b) The Aiken sector will accept handoff and immediately initiate handoff to the third completion sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(c) When the first initiating sector observes the third completion sector has accepted the handoff, the first initiating sector will transfer communications the third completion sector and coordinate pertinent flight plan information with the third completion sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t(d) If the third completion sector has not accepted the handoff prior to the aircraft reaching the first initiating sector boundary, the first initiating sector will put the aircraft on the Aiken sector frequency.\n\t\t\t\n\t\t\n\t\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\t(e) If the Aiken sector requires communications with the aircraft, they will request communications from the first initiating sector prior to accepting the handoff and the first initiating sector will coordinate pertinent flight plan information with the Aiken sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t8-5-4. MILITARY OPERATIONS\n\t\t\t\n\n\t\t\t\n\t\t\t\tNo military procedures have been identified for this sector.\n\t\t\t\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\t\n\n"}],[{"id":22,"title":"Baden 15","content":"\n\n\tBaden 15 126.775\n\n\n\n\tSECTOR NARRATIVEThe Baden Sector is an ultra-high sector with altitude limits from FL350 and above. The normal traffic flow is from northeast to southwest along J22 or J48 and inbounds into the Atlanta Terminal Area from the northeast. There are multiple crossing points within the\n\tairspace and opposite direction traffic is an issue.\n\n\n\n\tASSIGNMENT OF AIRSPACEBaden is open on sector 15 from approximately 0630-2230 local. During the midnight\n\tconfiguration, Baden is combined with Lanier sector at Sector 50.\n\n\n\n\tPROCEDURES\n\n\n\n\ta. Arrivals\n\n\n\n\t1. Arrivals into Atlanta Terminal area:\n\n\n\n\t(a) Upon completion of radar handoff and communications transfer, Lanier Sector shall have control for left or right turns up to 15 degrees and speed control for all ATL arrivals within 15NM of the Lanier boundary from Baden.\n\n\n\n\t(b) High Rock will descend aircraft landing Atlanta Hartsfield to FL350 and initiate a handoff to the Georgia High sector in time to allow the aircraft to cross the Lanier\/Georgia High sector boundary at or below FL340.\n\n\n\n\t2. Aircraft inbound to Chattanooga (CHA), operating on or north of a line from Pulaski (PSK) to Choo-Choo (GQO), shall be descended to FL350 and handed off to the Salem Sector in sufficient time for the aircraft to cross the Salem\/Burne boundary at or below FL300.\n\n\n\n\t3. Arrivals to the Nashville Terminal Area (BNA, MQY, JWN, MBT) shall be descended to FL350 and handed off to the Lanier or Salem Sectors in sufficient time for the aircraft to cross the Burne boundary at or below FL300.\n\n\n\n\t4. Arrivals to GSO and INT, north of a line GSO to GQO shall be handed off to BADEN at or descending to FL350.\n\n\n\n\tb. Departures.\n\tNo departure procedures have been identified for this sector\n\n\n\n\tc. Additional Procedures.\n\n\n\n\tNo additional procedures have been identified for this sector.\n\n\n\n\td. Automated Information Transfers.\n\n\n\n\t1. Aircraft landing GSO AOA FL350 shall be handled as follows:\n\n\n\n\t(a) Traffic permitting, BUU Sector shall clear aircraft to FL350 and initiate a handoff to the Baden Sector.\n\n\n\n\t(b) Traffic permitting, Baden Sector shall accept the handoff and immediately initiate a handoff to the Salem Sector.\n\n\n\n\t(c) When BUU Sector observes that the Salem Sector has accepted the handoff, the BUU Sector shall transfer communications to the Salem Sector.\n\n\n\n\t2. Aircraft transitioning from Area 2 through the Pulaski or Baden Sector to ZDC whose projected route of flight will remain within the lateral confines of that airspace between 5 miles west of the centerline of Q69 and the ZTL\/ZDC center boundary will be handled as follows:\n\n\n\n\t(a) High Rock or Charlotte Sector will initiate handoff to Pulaski or Baden Sector. ZDC.\n\n\n\n\t(b) Pulaski or Baden will accept handoff and immediately initiate handoff to\n\n\n\n\t(c) When High Rock or Charlotte Sector observe ZDC has accepted the handoff, High Rock or Charlotte Sector will transfer communications to ZDC and coordinate pertinent flight plan information with ZDC.\n\n\n\n\t(d) If ZDC has not accepted the handoff prior to the aircraft reaching the High Rock or Charlotte Sector boundary, Area 2 will transfer communications to the Pulaski or Baden Sector frequency.\n\n\n\n\t(e) If Pulaski or Baden Sector requires communications with the aircraft, they will request communications from High Rock or Charlotte Sector prior to accepting the handoff and the High Rock or Charlotte Sector will coordinate pertinent flight plan information with the Pulaski or Baden Sector.\n\n\n\n\t(f) Aircraft involved must remain within appropriate sector stratum at level flight.\n\n\n\n\tMILITARY OPERATIONS\n\n\n\n\tNo military procedures have been identified for this sector\n\n\n\n\t\n"},{"id":23,"title":"East Departure 16","content":"\n\n\tEast Departure Sector 16 124.450\n\n\n\n\tSECTOR NARRATIVE\n\tThe East Departure Sector is a low sector with altitude limits from 15,000 feet to FL230\u00a0for the airspace overlying A80-Atlanta Sector airspace, and 11,000 feet to FL230 for the\u00a0remainder of the airspace. The primary traffic flow is west to east and consist of jet and\u00a0turbojet departures climbing away from the Atlanta Terminal Area. There are major\u00a0crossing points in the vicinity of Athens and ELW VORTACs.\n\n\n\n\tASSIGNMENT OF AIRSPACE\n\tEast Departure is open on 16 from approximately 0630-2230 LCL. The Valley FPA is\u00a0normally assigned to East Departure, but can be assigned to Commerce sector. On the\u00a0midnight shift, East Departure is combined with A80-Athens, Commerce, and Logen sectors on Sector 49.The West Departure\/East Departure boundary moves East of V97 when A80-Atlanta\u00a0Sector is on an East operation, and West of V97 when A80 Atlanta Sector is on a West\u00a0operation\n\n\n\n\tPROCEDURES\n\ta. Arrivals\n\n\n\n\t1. Aircraft landing the Augusta Terminal Area shall be cleared direct\u00a0\n\tdestination airport, and descend to 11,000 feet.\n\n\n\n\t2. Arrivals to SAV, CHS, JZI, AGS, DNL, HQU, HXD, and AIK shall be\u00a0\n\treleased to Augusta Sector for control for right turns. Augusta Sector shall ensure point out to Sinca Sector.\n\n\n\n\t3. Turboprops inbound to the Charlotte Terminal Area shall be issued a\u00a0\n\trestriction to cross GRD VORTAC at 11,000 feet and handed off to Unarm Sector.\n\n\n\n\tb. Departures.\n\n\n\n\t1. Atlanta Departures:\n\n\n\n\t(a) Aircraft departing the Atlanta Terminal Area and landing\u00a0CHS\/JZI\/SAV\/HXD\/CAE requesting at or above FL230 shall be assigned FL230 as a\u00a0final altitude.\n\n\n\n\t(b) Departures from the Atlanta Terminal Area via East Departure Sector that\u00a0will next enter the Sinca Sector, shall be assigned a heading to remain clear of Sinca\u00a0airspace and handed off to Sinca. Aircraft are released for turns to the south. Sinca shall\u00a0be responsible for point outs to the Augusta Sector.\n\n\n\n\tc. Additional Procedures.\n\n\n\n\tThe \u201cAthens West Area\u201d is a portion of airspace delegated to SPA HI Sector from MCN\u00a0HI Sector. The airspace is only released to SPA HI when Atlanta Hartsfield is on a west\u00a0operation to allow for the continued climb of departing aircraft. The vertical limits of the\u00a0\u201cAthens West Area\u201d are from FL240 - FL290. The lateral limits are depicted on the\u00a0HIGH Filter Button by a dashed line from the southwestern corner of the Lanier Sector to\u00a0the northwestern corner of the DBN HI sector.\n\n\n\n\td. Automated Information Transfers.\n\n\n\n\t1. Aircraft departing A80 via GAIRY SID over-flying IRQ.\n\n\n\n\t(a) For aircraft requesting FL240 and above that would reasonably enter\u00a0Augusta Lows airspace, East Departure will clear the aircraft to FL230 when traffic\u00a0permits, and initiate a handoff to the Augusta Low Sector.\n\n\n\n\t(b) Augusta Low Sector, traffic permitting, shall accept the handoff and\u00a0immediately initiate a handoff to Dublin Sector. If Augusta Low Sector requires\u00a0communication with the aircraft, they shall request communications from East Departure\u00a0Sector prior to accepting the handoff.\n\n\n\n\t(c) When East Departure Sector observes that Dublin Sector has accepted the\u00a0handoff, East Departure Sector shall transfer\u00a0 communications and any pertinent flight\u00a0plan information to Dublin.\n\n\n\n\t2. Aircraft transitioning from CLT climbing over IPTAY intersection.\u00a0\n\n\n\n\t(a) Unarm Sector should climb aircraft to FL230 when traffic permits and\u00a0initiate a handoff to East Departure Sector.\u00a0\n\n\n\n\t(b) Traffic permitting East Departure Sector should accept the handoff then\u00a0immediately initiate a handoff to Spartanburg Sector.\u00a0\n\n\n\n\t(c) When Spartanburg sector accepts the handoff, Unarm Sector will transfer\u00a0communication and any pertinent flight data to the Spartanburg.\n\n\n\n\t(d) If East Departure Sector requires communication with the aircraft they\u00a0should call Unarm Sector prior to accepting the handoff.\n\n\n\n\t3. Augusta Regional at Bush Field airport (KAGS) arrivals transitioning from\u00a0East Departure sector must be handled as follows:\n\n\n\n\t(a) East Departure will, traffic permitting, descend aircraft to 11,000 feet and\u00a0initiate handoff to Augusta sector.\n\n\n\n\t(b) Augusta sector, traffic permitting, will accept handoff and immediately\u00a0initiate handoff to Augusta Approach.\n\n\n\n\t(c) When East Departure observes Augusta Approach has accepted the handoff,\u00a0East Departure will transfer communications to Augusta Approach.\n\n\n\n\t(d) If Augusta sector requires communications with the aircraft, they must\u00a0request communications from East Departure prior to accepting the handoff.\n\n\n\n\t(e) East Departure must coordinate pertinent flight plan information with\u00a0Augusta Approach.\n\n\n\n\t(f) If Augusta Approach has not accepted handoff prior to aircraft reaching\u00a0the Area 3\/4 boundary, East Departure will put aircraft on Augusta sector frequency.\u00a0\n\n\n\n\te. Pre-Arranged Coordination\n\n\n\n\tSector 21 is authorized to control ATL departures assigned the SMLTZ and VRSTYSIDs within the confines of Sector 16 without individual coordination provided the\u00a0following requirements are met.\u00a0\n\n\n\n\t1. ERAM must be fully operational.\n\n\n\n\t2. The authorized sector must \u201cquick look\u201d the owning sector and maintain\u00a0display of the owning sector\u2019s data blocks while utilizing the airspace.\n\n\n\n\t3. The authorized sector is responsible to provide radar separation, including\u00a0wake turbulence separation, from all applicable traffic when utilizing this procedure.\n\n\n\n\t4. The authorized sector must PVD the data block of the aircraft transitioning the\u00a0airspace to the owning sector.\n\n\n\n\tIf any of the above requirements are not met or at the request of either sector controller or\u00a0\n\tarea supervisor, this procedure is cancelled and individual coordination is required.\n\n\n\n\t\n"}]]
