Midshift tower controller not adhering to prescribed route and altitude departure procedures.

Attributes
ACN	275818
Time
Date	199406
Day	Thu
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : dfw
State Reference	TX
Altitude	msl bound lower : 2000 msl bound upper : 17000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : dfw tower : dfw
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	climbout : initial climbout : intermediate altitude
Route In Use	departure other
Flight Plan	IFR
Aircraft 2
Make Model Name	Baron 55/Cochise
Operating Under FAR Part	Part 91
Flight Phase	climbout : intermediate altitude climbout : initial
Route In Use	departure other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach controller : departure
Qualification	controller : radar
Experience	controller radar : 20
ASRS Report	275818
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure Operational Deviation other

Narrative:

I was working in the TRACON all position combined on the mid shift. I had one aircraft depart dfw and reported climbing to 17000 ft. I let it go because I had nothing in the way. At dfw jets all assigned 10000 ft and the propellers 2000 ft for departure. Tower next launched a BE55 who reported climbing to 8000 ft. Another jet departed climbing to 17000 ft. Because of the potential for altitude separation errors, I asked the tower controller was he assigning 8000 and 17000 ft. He said yes, I told him knock it off and assign the right altitude. He then asked me did I want him to assign the sids. I said yes (he is supposed to). I don't know what he was giving as clrncs then. He then asked me can't I just assign an interim altitude. I said yes, if I knew about it, but said stick to your job and assign the correct procedures. He asked me to call him on another phone. I told him he could talk to the supervisor because I didn't have time for idiots. The supervisor told this person's supervisor won't do anything about the controller. The issue is uncoord control actions and the tower controller who is not a radar controller understanding the potential deadly input of his actions.

Original NASA ASRS Text

Title: MIDSHIFT TWR CTLR NOT ADHERING TO PRESCRIBED RTE AND ALT DEP PROCS.

Narrative: I WAS WORKING IN THE TRACON ALL POS COMBINED ON THE MID SHIFT. I HAD ONE ACFT DEPART DFW AND RPTED CLBING TO 17000 FT. I LET IT GO BECAUSE I HAD NOTHING IN THE WAY. AT DFW JETS ALL ASSIGNED 10000 FT AND THE PROPS 2000 FT FOR DEP. TWR NEXT LAUNCHED A BE55 WHO RPTED CLBING TO 8000 FT. ANOTHER JET DEPARTED CLBING TO 17000 FT. BECAUSE OF THE POTENTIAL FOR ALT SEPARATION ERRORS, I ASKED THE TWR CTLR WAS HE ASSIGNING 8000 AND 17000 FT. HE SAID YES, I TOLD HIM KNOCK IT OFF AND ASSIGN THE RIGHT ALT. HE THEN ASKED ME DID I WANT HIM TO ASSIGN THE SIDS. I SAID YES (HE IS SUPPOSED TO). I DON'T KNOW WHAT HE WAS GIVING AS CLRNCS THEN. HE THEN ASKED ME CAN'T I JUST ASSIGN AN INTERIM ALT. I SAID YES, IF I KNEW ABOUT IT, BUT SAID STICK TO YOUR JOB AND ASSIGN THE CORRECT PROCS. HE ASKED ME TO CALL HIM ON ANOTHER PHONE. I TOLD HIM HE COULD TALK TO THE SUPVR BECAUSE I DIDN'T HAVE TIME FOR IDIOTS. THE SUPVR TOLD THIS PERSON'S SUPVR WON'T DO ANYTHING ABOUT THE CTLR. THE ISSUE IS UNCOORD CTL ACTIONS AND THE TWR CTLR WHO IS NOT A RADAR CTLR UNDERSTANDING THE POTENTIAL DEADLY INPUT OF HIS ACTIONS.

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