Air Traffic Control Fully Certified
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors; Procedure
I was working the Ground Control position and observed this event on Local West. The CIC was also observing and attempted to communicate instructions to the Local Controller; however; these suggestions went unused or were unwanted. Aircraft X; SR22; IFR; issued heading 230 and 2;000 FT; per LOA with Approach Control. Thirty seconds later; Aircraft Y; MO20; called 6 miles south inbound. Mooney was instructed to enter right downwind to runway; and issued a beacon code and traffic departing on a 230 heading. Mooney was on a 1200 code and was 5 miles southwest of the field tracking a Northeasterly course directly towards the path of the departing Cirrus. Mooney was descending. Traffic was called to the Cirrus with 'no joy.' Moony finally entered the correct code and the position from the Cirrus was approximately 2 miles. Cirrus was instructed to maintain 1;000 FT. Mooney was instructed to maintain 1;100 FT. The two aircraft had past each other by the time the Mooney said he had the Cirrus in sight. The Cirrus was advised traffic no factor and switched to Departure. I reminded the Local Controller in a loud tone to climb the Cirrus to 2;000 FT. The Local Controller complied; the Cirrus had not switched yet and received the climb instruction; [and] the MVA is 1;700 FT. No positive separation was being applied when several alternatives were available. This was a very dangerous situation that was completely preventable. Any type of positive control would have been preferable. Move the VFR Mooney immediately. Using assigned altitudes below MVA that are only 100 FT apart is not approved separation. Certainly this was at a minimum; a 'Traffic Alert' situation to both aircraft.
Tower Controller described an unsafe event when the Local Controller used questionable altitude assignments to separate a VFR from an IFR aircraft.