Operation error as small transport Y was cleared to land on occupied runway, and did so.

Attributes
ACN	163466
Time
Date	199011
Day	Thu
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : dfw
State Reference	TX
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Widebody, Low Wing, 3 Turbojet Eng
Navigation In Use	Other
Flight Phase	ground : holding
Flight Plan	None
Aircraft 2
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Flight Phase	landing other
Person 1
Affiliation	government : faa
Function	controller : local
Qualification	controller : radar
Experience	controller radar : 8
ASRS Report	163466
Person 2
Affiliation	company : air carrier
Function	other personnel other
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : required legal separation non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Miss Distance	horizontal : 7000 vertical : 0
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

I was working at dfw tower. About xa:00 a widebody transport X requested an engine runup for maintenance. I put widebody transport X on runway 13L at the departure end. Runways 13R and 17R were closed (construction). Airport operations requested runway 17L be closed for lighting maintenance. At xa:25 small transport Y was inbound and I put him on runway 13L. After small transport Y landed I realized widebody transport X was on the runway. They missed by 2 mi but according to FAA 7110.65 this was illegal and a runway incursion. This incident was partially caused by just human error and I had worked that day and came back to work in 8 hours. 8 hours between shifts of work is not enough, especially when working other shift just once a week. Tests have proved this is not good for your health. Also with all the construction and runway closures at a major airport with the above factors involved also, we are asking for trouble. Controllers are only human too, yet the FAA will not acknowledge this. Visibility aids and procedures of the facility were followed to the letter!

Original NASA ASRS Text

Title: OP ERROR AS SMT Y WAS CLEARED TO LAND ON OCCUPIED RWY, AND DID SO.

Narrative: I WAS WORKING AT DFW TWR. ABOUT XA:00 A WDB X REQUESTED AN ENG RUNUP FOR MAINT. I PUT WDB X ON RWY 13L AT THE DEP END. RWYS 13R AND 17R WERE CLOSED (CONSTRUCTION). ARPT OPS REQUESTED RWY 17L BE CLOSED FOR LIGHTING MAINT. AT XA:25 SMT Y WAS INBND AND I PUT HIM ON RWY 13L. AFTER SMT Y LANDED I REALIZED WDB X WAS ON THE RWY. THEY MISSED BY 2 MI BUT ACCORDING TO FAA 7110.65 THIS WAS ILLEGAL AND A RWY INCURSION. THIS INCIDENT WAS PARTIALLY CAUSED BY JUST HUMAN ERROR AND I HAD WORKED THAT DAY AND CAME BACK TO WORK IN 8 HRS. 8 HRS BTWN SHIFTS OF WORK IS NOT ENOUGH, ESPECIALLY WHEN WORKING OTHER SHIFT JUST ONCE A WK. TESTS HAVE PROVED THIS IS NOT GOOD FOR YOUR HEALTH. ALSO WITH ALL THE CONSTRUCTION AND RWY CLOSURES AT A MAJOR ARPT WITH THE ABOVE FACTORS INVOLVED ALSO, WE ARE ASKING FOR TROUBLE. CTLRS ARE ONLY HUMAN TOO, YET THE FAA WILL NOT ACKNOWLEDGE THIS. VIS AIDS AND PROCS OF THE FAC WERE FOLLOWED TO THE LETTER!

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.