D10 controller providing OJT described a loss of separation event when failing to note the type of a...

Narrative:

I was conducting training on the ds position. We were moderately busy with a one runway operation taking place at dal. The developmental released a departure off of rbd giving him a right turn to 130 to avoid an MVA just east of rbd. Just before rbd called for the release the supervisor had just brought over a document detailing a fly-by event that was about to take place. The developmental answered the line to rbd to release the aircraft; I was reviewing the document and didn't catch that the release was a jet. Jet departures climb to 3;000 off of rbd where as props only climb to 2;000. When the departure came off of rbd the developmental radar identified him and I noticed pretty quickly that it was a jet and not a prop. About 3 miles away was an E135 on final to runway 31R at dfw descending out of 3;500 for 3;000. I did not give the developmental time to try and correct it; but keyed up immediately myself and gave the HA25 an immediate turn to heading 180 and called traffic trying to get him to see the E135. He never saw the E135; but we ended up with about 2 miles separation. The developmental then told me that he knew it was a jet; but thought they only climbed to 2;000 on departure. Recommendation; standardize altitudes off of rbd. I see no need for having two different altitudes for props and jets off of rbd. There are not that many departures off of rbd anyway and we also only have 3 usable altitudes in that part of the airspace. That airspace can get really congested and 2;000 is a much safer altitude than 3;000; usually.

Original NASA ASRS Text

Title: D10 Controller providing OJT described a loss of separation event when failing to note the type of aircraft released from RBD; not expecting a jet climbing to 3;000; the reporter suggested one altitude assignment off RBD.

Narrative: I was conducting training on the DS position. We were moderately busy with a one runway operation taking place at DAL. The developmental released a departure off of RBD giving him a right turn to 130 to avoid an MVA just east of RBD. Just before RBD called for the release the Supervisor had just brought over a document detailing a fly-by event that was about to take place. The developmental answered the line to RBD to release the aircraft; I was reviewing the document and didn't catch that the release was a jet. Jet departures climb to 3;000 off of RBD where as props only climb to 2;000. When the departure came off of RBD the developmental RADAR identified him and I noticed pretty quickly that it was a jet and not a prop. About 3 miles away was an E135 on final to Runway 31R at DFW descending out of 3;500 for 3;000. I did not give the developmental time to try and correct it; but keyed up immediately myself and gave the HA25 an immediate turn to heading 180 and called traffic trying to get him to see the E135. He never saw the E135; but we ended up with about 2 miles separation. The developmental then told me that he knew it was a jet; but thought they only climbed to 2;000 on departure. Recommendation; standardize altitudes off of RBD. I see no need for having two different altitudes for props and jets off of RBD. There are not that many departures off of RBD anyway and we also only have 3 usable altitudes in that part of the airspace. That airspace can get really congested and 2;000 is a much safer altitude than 3;000; usually.

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.

Attributes
ACN	910632
Time
Date	201009
Local Time Of Day	1801-2400
Place
Locale Reference	RBD.Airport
State Reference	TX
Aircraft 1
Make Model Name	HS 125 Series
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	EMB ERJ 135 ER&LR
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	Other Instrument Approach
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

D10 controller providing OJT described a loss of separation event when failing to note the type of aircraft released from rbd; not expecting a jet climbing to 3;000; the reporter suggested one altitude assignment off rbd.