Narrative:

Working sector 18 in ZDC. 15 mi in trail required by new york approach for ewr arrs. Relieved fpl from position who just provided approximately 8-10 mi between 5 ewr arrs. The decrease in mi in trail requirement was caused by 2 'questionable' releases from the washington metropolitan area by the tmu. Sector 17 in ZDC was holding an additional 2 aircraft for ewr; 1 at FL230 and 1 at FL180 over kerno. Both aircraft were pointed out to me. Placed into a 'no notice' hold by approach. Put 8 aircraft into holding over ard and stefi. The erj involved was the aircraft holding at kerno. Descended the HS25 through the erj; when attempting to get the HS25 to meet a future crossing restr that lies below the holding pattern at stefi. The error was discovered when the machine flashed. Instructed aircraft to stop descent and return to FL240. Aircraft in holding was diverging; so no action was taken with him. Error in judgement I believed caused this error. Contributing factors; I believe; were tmu's 2 previous 'questionable' releases caused the previous controller to provide reduced mi in trail to approach. 3 additional releases were approved by tmu; 2 were currently holding at kerno; 1 was en route. (The reduced mi in trail provided to approach triggered the 'no notice' hold.) the controller holding the aircraft at kerno was holding the aircraft high; which hindered any teb arrs which have to meet a crossing restr in approximately 40 mi. It was a teb arrival (HS25) that was involved in the error.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZDC CTLR EXPERIENCED OPERROR AT FL230 WHEN DSNDING ACFT BELOW HOLDING PATTERN TFC AND MISJUDGING SPACING.

Narrative: WORKING SECTOR 18 IN ZDC. 15 MI IN TRAIL REQUIRED BY NEW YORK APCH FOR EWR ARRS. RELIEVED FPL FROM POS WHO JUST PROVIDED APPROX 8-10 MI BTWN 5 EWR ARRS. THE DECREASE IN MI IN TRAIL REQUIREMENT WAS CAUSED BY 2 'QUESTIONABLE' RELEASES FROM THE WASHINGTON METRO AREA BY THE TMU. SECTOR 17 IN ZDC WAS HOLDING AN ADDITIONAL 2 ACFT FOR EWR; 1 AT FL230 AND 1 AT FL180 OVER KERNO. BOTH ACFT WERE POINTED OUT TO ME. PLACED INTO A 'NO NOTICE' HOLD BY APCH. PUT 8 ACFT INTO HOLDING OVER ARD AND STEFI. THE ERJ INVOLVED WAS THE ACFT HOLDING AT KERNO. DSNDED THE HS25 THROUGH THE ERJ; WHEN ATTEMPTING TO GET THE HS25 TO MEET A FUTURE XING RESTR THAT LIES BELOW THE HOLDING PATTERN AT STEFI. THE ERROR WAS DISCOVERED WHEN THE MACHINE FLASHED. INSTRUCTED ACFT TO STOP DSCNT AND RETURN TO FL240. ACFT IN HOLDING WAS DIVERGING; SO NO ACTION WAS TAKEN WITH HIM. ERROR IN JUDGEMENT I BELIEVED CAUSED THIS ERROR. CONTRIBUTING FACTORS; I BELIEVE; WERE TMU'S 2 PREVIOUS 'QUESTIONABLE' RELEASES CAUSED THE PREVIOUS CTLR TO PROVIDE REDUCED MI IN TRAIL TO APCH. 3 ADDITIONAL RELEASES WERE APPROVED BY TMU; 2 WERE CURRENTLY HOLDING AT KERNO; 1 WAS ENRTE. (THE REDUCED MI IN TRAIL PROVIDED TO APCH TRIGGERED THE 'NO NOTICE' HOLD.) THE CTLR HOLDING THE ACFT AT KERNO WAS HOLDING THE ACFT HIGH; WHICH HINDERED ANY TEB ARRS WHICH HAVE TO MEET A XING RESTR IN APPROX 40 MI. IT WAS A TEB ARR (HS25) THAT WAS INVOLVED IN THE ERROR.

Data retrieved from NASA's ASRS site as of January 2009 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.