Narrative:

This is a continuing problem with the ZDC/pct LOA. Pct hands off traffic to ZDC sector 17 at 14 thousand. If ZDC sector 17 does not climb above ZDC sector 53; which adjoin laterally; pct is charged with a deviation. The text of the LOA reads; that 'unless otherwise specified; the 'transfer point'; doesn't say whether that means communication or control; is the airspace boundary. No 'otherwise' points are specified in the text. Well hidden in attachment 4 is a 'depiction' of transfer points at agard; and a couple other fixes. In this situation air carrier X was switched to the center past agard; but prior to the airspace boundary and they were unable to top traffic in sector 53. Traffic in my sector was heavy and complex at the time. Another air carrier flight who had accepted a clearance; but failed to program it correctly added to the workload. Additionally; traffic popped up VFR with low fuel and called multiple times after being asked to stand by. This prevented me from switching air carrier X in a timely fashion as I would normally have done. Recommendation; give pct the ability to climb above sector 53 after 17 takes the hand off; or change the procedure so that we don't have to. I should not have to depend on another controller; in another building to climb and prevent me from being charged with a deviation. Also spell out in the text of the LOA exactly what is expected. Don't hide it in some attachment with no explanation of whether it's transfer of 'control' or 'communication'.

Related reports:

Google
 

Original NASA ASRS Text

Title: PCT Controller voiced concern regarding a PCT/ZDC LOA provision that frequently results in a technical deviation; suggesting the LOA is in need of clarity and revision/s.

Narrative: This is a continuing problem with the ZDC/PCT LOA. PCT hands off traffic to ZDC Sector 17 at 14 thousand. If ZDC Sector 17 does not climb above ZDC Sector 53; which adjoin laterally; PCT is charged with a deviation. The text of the LOA reads; that 'unless otherwise specified; the 'transfer point'; doesn't say whether that means communication or control; is the airspace boundary. No 'otherwise' points are specified in the text. Well hidden in Attachment 4 is a 'depiction' of transfer points at AGARD; and a couple other fixes. In this situation Air Carrier X was switched to the Center past AGARD; but prior to the airspace boundary and they were unable to top traffic in Sector 53. Traffic in my sector was heavy and complex at the time. Another Air Carrier flight who had accepted a clearance; but failed to program it correctly added to the workload. Additionally; traffic popped up VFR with low fuel and called multiple times after being asked to stand by. This prevented me from switching Air Carrier X in a timely fashion as I would normally have done. Recommendation; give PCT the ability to climb above Sector 53 after 17 takes the hand off; or change the procedure so that we don't have to. I should not have to depend on another controller; in another building to climb and prevent me from being charged with a deviation. Also spell out in the text of the LOA exactly what is expected. Don't hide it in some attachment with no explanation of whether it's transfer of 'control' or 'communication'.

Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.