Date: 201511
Local time of day: 1201-1800
Location: BJC.Tower, CO
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Flight phase: Final Approach
Airspace: Class D BJC
ATC / advisory: Tower BJC
Reporter organization: Government
Reporter function: Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was working Ground Control and had 2-3 aircraft taxiing and just finished issuing an IFR clearance. My scan was focused on ensuring I had resolved a potential conflict between my taxiing aircraft. I then overheard Local Control (LC) issue 'go-around' instructions to an aircraft; but I did not initially know the reason or see which aircraft it was. I shifted my scan towards the finals but did not initially see an aircraft going around.I finally acquired a Cessna on the upwind for Runway 30R. Based on the LC controller's comment; I believe that aircraft was supposed to be on final for 30L; but for whatever reason; the aircraft was on final for 30R. The Cessna then went into left traffic for 30L. The CIC was in the process of completing the hourly weather observation and ATIS during the event; thus adding to their workload at the time. I can also recall the cab being very warm at the time; which was a bit of a distraction (but not unreasonable; in my opinion). This is another event emphasizing the importance of visual scanning and awareness. While I was working out my own traffic scenario; I did hear or observe an unusual situation on the finals until the go-around was issued.The CIC normally completes weather observations; and any steps that can be taken to reduce their workload to complete and transmit that observation may help the CICs maintain a better visual scan and situational awareness. There are multiple steps that presently must be taken for this observation; and improved AWOS equipment may help reduce those steps. Right now; the observer uses a combination of their own observations and the AWOS equipment to complete a manual observation. The process I use is as follows: 1) I enter the manual observation into the weather spreadsheet and save it on one computer. 2) I then have to go to the IDS-4 [Information Display System] and enter the same weather observation data into it. 3) I then have to proceed back to the other computer and fill out that same weather data into an online form; and then transmit it into the AISR system [Aeronautical Information System Replacement]. 4) I then have to verify at some point in the next few minutes that the information was transmitted successfully into the AISR system; and correct any typos or errors. 5) I then have to do the ATIS recording; and ensure that the correct observation and ATIS code was updated in the IDS-4. I recognize that the work in step 5 is required regardless of AWOS equipment. However; an upgraded AWOS that is allowed to transmit observations while the tower is open would allow us to meet LAWRS [Limited Aviation Weather Reporting Station] requirements and could reduce observer workload significantly. I believe better AWOS equipment would allow us to complete a weather observation and ensure it was entered correctly *once*; as opposed to three times as we do currently. In addition to reducing controller workload and distraction; new AWOS equipment could benefit aviation users and the NWS [National Weather Service] by reducing data entry errors that often occur when entering the observation multiple times.




Synopsis: BJC Ground Controller reported of an aircraft on final that was lined up for the incorrect runway that was told to go around by the Local Controller. Controller attributed the go around to a lack of scanning by the Local Controller. Controller also noted that the CIC was busy making and checking the ATIS recording.