Narrative:

I was cleared into position and hold, runway 24R at dayton, oh, xx:10Z. Aircraft had been landing on both runways 24L and 18 with departures on runway 24L and 24R. Runway 24R was clear, and nobody on final. Copilot readback position and hold runway 24R. As the nose of my medium large transport was about to cross the runway side line, my copilot jammed the brakes on, and pointed out an light transport twin. On short final, about 200' from the approach end of runway 24R. The tower controller at this time cleared us for takeoff, still unaware of the commuter aircraft about to land on my runway. The copilot asked if she was aware of the aircraft landing and she immediately cancelled our takeoff clearance. A subsequent phone call to the tower supervisor revealed that approach control forgot to handoff to tower; the pilot of the commuter forgot to get switched over and landed west/O clearance; the tower controller saw the aircraft on the tower radar (bright display?) but she became sidetracked with traffic on runway 24L and forgot about the light transport. I always check for traffic prior to entering a runway. In this case, the windshield side post blocked the small target. Supplemental information from acn 149504. Upon arrival at grr the captain called the tower supervisor. He stated there were 3 errors made. First the approach controller forgot to handoff the light transport to the tower. Second the pilot never switched to the tower and finally the tower controller forgot he was coming. The reason I did not see the aircraft the first time I looked was due to a blind spot. I think a very simple fix to this is to split the tower frequency between 2 controllers. I think it is too much for one person to handle both runways for arrs and departures at a major hub.

Google
 

Original NASA ASRS Text

Title: POTENTIAL CONFLICT AND NEAR IMPACT BETWEEN AN LTT LNDG WITHOUT CLRNC AND AN MLG GIVEN CLRNC INTO POSITION BY TWR WHO OVERLOOKED LTT ON SHORT FINAL. PROBLEM STARTED WITH LTT NOT BEING HANDED OVER TO TWR BY APCH AND FLT CREW NOT CALLING TWR.

Narrative: I WAS CLRED INTO POS AND HOLD, RWY 24R AT DAYTON, OH, XX:10Z. ACFT HAD BEEN LNDG ON BOTH RWYS 24L AND 18 WITH DEPS ON RWY 24L AND 24R. RWY 24R WAS CLR, AND NOBODY ON FINAL. COPLT READBACK POS AND HOLD RWY 24R. AS THE NOSE OF MY MLG WAS ABOUT TO CROSS THE RWY SIDE LINE, MY COPLT JAMMED THE BRAKES ON, AND POINTED OUT AN LTT TWIN. ON SHORT FINAL, ABOUT 200' FROM THE APCH END OF RWY 24R. THE TWR CTLR AT THIS TIME CLRED US FOR TKOF, STILL UNAWARE OF THE COMMUTER ACFT ABOUT TO LAND ON MY RWY. THE COPLT ASKED IF SHE WAS AWARE OF THE ACFT LNDG AND SHE IMMEDIATELY CANCELLED OUR TKOF CLRNC. A SUBSEQUENT PHONE CALL TO THE TWR SUPVR REVEALED THAT APCH CTL FORGOT TO HDOF TO TWR; THE PLT OF THE COMMUTER FORGOT TO GET SWITCHED OVER AND LANDED W/O CLRNC; THE TWR CTLR SAW THE ACFT ON THE TWR RADAR (BRIGHT DISPLAY?) BUT SHE BECAME SIDETRACKED WITH TFC ON RWY 24L AND FORGOT ABOUT THE LTT. I ALWAYS CHK FOR TFC PRIOR TO ENTERING A RWY. IN THIS CASE, THE WINDSHIELD SIDE POST BLOCKED THE SMALL TARGET. SUPPLEMENTAL INFO FROM ACN 149504. UPON ARR AT GRR THE CAPT CALLED THE TWR SUPVR. HE STATED THERE WERE 3 ERRORS MADE. FIRST THE APCH CTLR FORGOT TO HDOF THE LTT TO THE TWR. SECOND THE PLT NEVER SWITCHED TO THE TWR AND FINALLY THE TWR CTLR FORGOT HE WAS COMING. THE REASON I DID NOT SEE THE ACFT THE FIRST TIME I LOOKED WAS DUE TO A BLIND SPOT. I THINK A VERY SIMPLE FIX TO THIS IS TO SPLIT THE TWR FREQ BTWN 2 CTLRS. I THINK IT IS TOO MUCH FOR ONE PERSON TO HANDLE BOTH RWYS FOR ARRS AND DEPS AT A MAJOR HUB.

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.