An unhappy ATCT local controller does not agree with procedures used in giving den estimated departu...

Attributes
ACN	360384
Time
Date	199702
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : gjt
State Reference	CO
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : dlf
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	climbout : takeoff ground other : taxi
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	climbout : takeoff ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar pilot : private
ASRS Report	360384
Person 2
Affiliation	government : faa
Function	flight crew : first officer
Qualification	controller : non radar
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

Because there are certain individuals, including the supervisor, in this facility who are not intuitive enough to understand the consequences of their actions and because certain individuals insist on criticizing me for trivial, minor and insignificant issues/mistakes, every mistake made by these individuals which has any potential of endangering the lives of innocent people will be recorded on a NASA report to be made a public record. On feb/wed/97, at XA26 and XA29Z, the flight data controller informed den approach that air carrier X and air carrier Y were departing the airport to comply with den/gjt LOA and the 7110.65J to radar identify departing aircraft. These aircraft were still on the taxiway when the flight data controller told approach they were departing. There is no possible way the radar controller could have positively radar idented these 2 aircraft based on the flight data controller's report. Radar identing IFR aircraft based on these reports is an accident waiting to happen just like the XXXX accident. The existing LOA procedures which are being used to radar identify IFR aircraft contradict the methods of radar identify for beacon equipment aircraft as listed in FAA ATC manual 7110.65J paragraph 5-3-3. Furthermore there is no possible way den can insure positive radar identify solely on a rolling boundary notification when there are other beacon equipment aircraft operating in closed traffic pattern or in gjt class D airspace.

Original NASA ASRS Text

Title: AN UNHAPPY ATCT LCL CTLR DOES NOT AGREE WITH PROCS USED IN GIVING DEN ESTIMATED DEP TIMES ON ACFT THAT ARE TAXIING OUT FOR TKOF EVEN THOUGH THERE IS AN LOA BTWN GJT AND DEN WHICH PERMITS THIS.

Narrative: BECAUSE THERE ARE CERTAIN INDIVIDUALS, INCLUDING THE SUPVR, IN THIS FACILITY WHO ARE NOT INTUITIVE ENOUGH TO UNDERSTAND THE CONSEQUENCES OF THEIR ACTIONS AND BECAUSE CERTAIN INDIVIDUALS INSIST ON CRITICIZING ME FOR TRIVIAL, MINOR AND INSIGNIFICANT ISSUES/MISTAKES, EVERY MISTAKE MADE BY THESE INDIVIDUALS WHICH HAS ANY POTENTIAL OF ENDANGERING THE LIVES OF INNOCENT PEOPLE WILL BE RECORDED ON A NASA RPT TO BE MADE A PUBLIC RECORD. ON FEB/WED/97, AT XA26 AND XA29Z, THE FLT DATA CTLR INFORMED DEN APCH THAT ACR X AND ACR Y WERE DEPARTING THE ARPT TO COMPLY WITH DEN/GJT LOA AND THE 7110.65J TO RADAR IDENT DEPARTING ACFT. THESE ACFT WERE STILL ON THE TXWY WHEN THE FLT DATA CTLR TOLD APCH THEY WERE DEPARTING. THERE IS NO POSSIBLE WAY THE RADAR CTLR COULD HAVE POSITIVELY RADAR IDENTED THESE 2 ACFT BASED ON THE FLT DATA CTLR'S RPT. RADAR IDENTING IFR ACFT BASED ON THESE RPTS IS AN ACCIDENT WAITING TO HAPPEN JUST LIKE THE XXXX ACCIDENT. THE EXISTING LOA PROCS WHICH ARE BEING USED TO RADAR IDENT IFR ACFT CONTRADICT THE METHODS OF RADAR IDENT FOR BEACON EQUIP ACFT AS LISTED IN FAA ATC MANUAL 7110.65J PARAGRAPH 5-3-3. FURTHERMORE THERE IS NO POSSIBLE WAY DEN CAN INSURE POSITIVE RADAR IDENT SOLELY ON A ROLLING BOUNDARY NOTIFICATION WHEN THERE ARE OTHER BEACON EQUIP ACFT OPERATING IN CLOSED TFC PATTERN OR IN GJT CLASS D AIRSPACE.

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.

An unhappy ATCT local controller does not agree with procedures used in giving den estimated departure times on aircraft that are taxiing out for takeoff even though there is an LOA between gjt and den which permits this.