C-172 takeoff on occupied runway had less than standard separation from air carrier Y. System error.

Attributes
ACN	303091
Time
Date	199504
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : bna
State Reference	TN
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	climbout : takeoff
Flight Plan	None
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : local
Qualification	controller : radar
Experience	controller radar : 12
ASRS Report	303091
Person 2
Affiliation	government : faa
Function	controller : ground
Qualification	controller : non radar
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	faa : investigated
Miss Distance	horizontal : 1000 vertical : 200
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Operational Error

Narrative:

The C172 had been put into position to hold on runway 31 following a departing MD80. Air carrier Y (MD80) had been approved to cross runway 31 behind the departing MD80 with the understanding the C172 would hold. I was working a couple other aircraft at the time. I was anticipating the timing of Y crossing the runway. While performing other duties, I was unaware ground controller #2 had delayed the crossing of Y when I cleared the C172 for takeoff. I failed to re-scan the situation. The C172 rolled and lifted off as the MD80 was clearing the runway. Obviously, the lack of scanning the runway a second time played a major role in this incident. A contributing factor was, as an instructor in the TRACON, I was not getting much tower time and had not been up in a week or more.

Original NASA ASRS Text

Title: C-172 TKOF ON OCCUPIED RWY HAD LTSS FROM ACR Y. SYS ERROR.

Narrative: THE C172 HAD BEEN PUT INTO POS TO HOLD ON RWY 31 FOLLOWING A DEPARTING MD80. ACR Y (MD80) HAD BEEN APPROVED TO CROSS RWY 31 BEHIND THE DEPARTING MD80 WITH THE UNDERSTANDING THE C172 WOULD HOLD. I WAS WORKING A COUPLE OTHER ACFT AT THE TIME. I WAS ANTICIPATING THE TIMING OF Y XING THE RWY. WHILE PERFORMING OTHER DUTIES, I WAS UNAWARE GND CTLR #2 HAD DELAYED THE XING OF Y WHEN I CLRED THE C172 FOR TKOF. I FAILED TO RE-SCAN THE SIT. THE C172 ROLLED AND LIFTED OFF AS THE MD80 WAS CLRING THE RWY. OBVIOUSLY, THE LACK OF SCANNING THE RWY A SECOND TIME PLAYED A MAJOR ROLE IN THIS INCIDENT. A CONTRIBUTING FACTOR WAS, AS AN INSTRUCTOR IN THE TRACON, I WAS NOT GETTING MUCH TWR TIME AND HAD NOT BEEN UP IN A WK OR MORE.

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.