ZBW controller described a loss of separation event; the reporter noting routings were used where ve...

Attributes
ACN	975609
Time
Date	201110
Local Time Of Day	1801-2400
Place
Locale Reference	ZBW.ARTCC
State Reference	NH
Aircraft 1
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Narrative:

A B737 and a CRJ2 had crossing paths. The B737 requested higher altitude; starting slightly behind; but faster forward speed and climb rate than the CRJ2. The radar controller used radar separation; speed control and an early turn to the north to expedite crossing routes to keep the B737 behind the CRJ2. The B737 aircraft gained too much speed from a southerly tailwind as it turned north and caught the CRJ2 with less than 5 miles. I was the d-side attending to departure proposal flight plan review. I was making a route amendment as the above events were playing out. Recommendation; I would have used radar vectors instead of simply clearing direct to a down-stream fix on the B737 route to ensure separation. The idea would have worked without the extra strong southerly winds. A radar vector or 30 degree turn would have been an added measure to ensure separation.

Original NASA ASRS Text

Title: ZBW Controller described a loss of separation event; the reporter noting routings were used where vectors would have been more appropriate.

Narrative: A B737 and a CRJ2 had crossing paths. The B737 requested higher altitude; starting slightly behind; but faster forward speed and climb rate than the CRJ2. The RADAR Controller used RADAR separation; speed control and an early turn to the north to expedite crossing routes to keep the B737 behind the CRJ2. The B737 aircraft gained too much speed from a southerly tailwind as it turned north and caught the CRJ2 with less than 5 miles. I was the D-Side attending to departure proposal flight plan review. I was making a route amendment as the above events were playing out. Recommendation; I would have used RADAR vectors instead of simply clearing direct to a down-stream fix on the B737 route to ensure separation. The idea would have worked without the extra strong southerly winds. A RADAR vector or 30 degree turn would have been an added measure to ensure separation.

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.

ZBW controller described a loss of separation event; the reporter noting routings were used where vectors would have been more appropriate.