Small aircraft makes touch and go over a flight of 2 small aircraft in position on the runway.

Attributes
ACN	156055
Time
Date	199009
Day	Wed
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : ogd
State Reference	UT
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	climbout : takeoff descent : approach landing other
Flight Plan	None
Aircraft 2
Operator	general aviation : personal
Make Model Name	Small Aircraft, Low Wing, 1 Eng, Fixed Gear
Flight Phase	ground : holding
Flight Plan	None
Person 1
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
ASRS Report	156055
Person 2
Affiliation	Other
Function	flight crew : single pilot
Events
Anomaly	conflict : ground critical non adherence : far non adherence : required legal separation
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted none taken : detected after the fact
Consequence	Other
Miss Distance	horizontal : 0 vertical : 150
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Pilot Deviation Operational Error

Narrative:

Only 1 controller on duty performing duties of controller in charge, local control, ground control, flight data. Flight of 2 aircraft small aircraft Y were taxied into position and hold runway 16 while another aircraft cleared the runway. Small aircraft X aircraft was cleared for touch and go runway 16 and performed touch and go over the top of the small aircraft Y flight that were in position and holding. No evasive action was taken by small aircraft X. As small aircraft X lifted off departure end small aircraft Y advised the tower that they were still in position and holding. Numerous items contributed to the situation, in my opinion. 1) staffing (1 controller) - local traffic was increasing, sunset was near and visibility from the tower was difficult looking into the sun, the police had just called reference another aircraft (as controller in charge I was dealing with this officer), ground control and tower frequency combined therefore aircraft were stepping on each other, and flight data also combined (i.e., WX was due) requiring additional calls needing to be made as well as the need to cut an ATIS. 2) late coordination from approach control required quick action with another aircraft. This other aircraft was 2-3 mi right base on initial contact. Contact was made within seconds after he was coordination from approach.

Original NASA ASRS Text

Title: SMA MAKES TOUCH AND GO OVER A FLT OF 2 SMA IN POSITION ON THE RWY.

Narrative: ONLY 1 CTLR ON DUTY PERFORMING DUTIES OF CIC, LCL CTL, GND CTL, FLT DATA. FLT OF 2 ACFT SMA Y WERE TAXIED INTO POS AND HOLD RWY 16 WHILE ANOTHER ACFT CLRED THE RWY. SMA X ACFT WAS CLRED FOR TOUCH AND GO RWY 16 AND PERFORMED TOUCH AND GO OVER THE TOP OF THE SMA Y FLT THAT WERE IN POS AND HOLDING. NO EVASIVE ACTION WAS TAKEN BY SMA X. AS SMA X LIFTED OFF DEP END SMA Y ADVISED THE TWR THAT THEY WERE STILL IN POS AND HOLDING. NUMEROUS ITEMS CONTRIBUTED TO THE SITUATION, IN MY OPINION. 1) STAFFING (1 CTLR) - LCL TFC WAS INCREASING, SUNSET WAS NEAR AND VISIBILITY FROM THE TWR WAS DIFFICULT LOOKING INTO THE SUN, THE POLICE HAD JUST CALLED REF ANOTHER ACFT (AS CIC I WAS DEALING WITH THIS OFFICER), GND CTL AND TWR FREQ COMBINED THEREFORE ACFT WERE STEPPING ON EACH OTHER, AND FLT DATA ALSO COMBINED (I.E., WX WAS DUE) REQUIRING ADDITIONAL CALLS NEEDING TO BE MADE AS WELL AS THE NEED TO CUT AN ATIS. 2) LATE COORD FROM APCH CTL REQUIRED QUICK ACTION WITH ANOTHER ACFT. THIS OTHER ACFT WAS 2-3 MI RIGHT BASE ON INITIAL CONTACT. CONTACT WAS MADE WITHIN SECS AFTER HE WAS COORD FROM APCH.

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.