A landing air carrier medium large transport keeps a wary eye on light transport in the process of a...

Attributes
ACN	222731
Time
Date	199210
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : cvg
State Reference	OH
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : iad
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	landing other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	climbout : takeoff other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : atp pilot : commercial pilot : flight engineer
Experience	flight time last 90 days : 200 flight time total : 3500 flight time type : 270
ASRS Report	222731
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : ground less severe non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : rejected takeoff other
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 500
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

We were making a visual approach to runway 36L at cvg airport and had been cleared to land on runway 36L. Another aircraft had been cleared for takeoff on runway 27 (an light transport). When we were on short final approach, the tower instructed the light transport to cancel takeoff clearance. The light transport crew responded 'roger, we are aborting.' this caught our attention, but it was just prior to our landing on runway 36L. After landing on runway 36L we saw the air carrier light transport braking to a stop on runway 27 (which intersects runway 36L). We saw that the other aircraft was coming to a stop safely before the intersection so we continued the landing roll through the intersection and cleared the runway as instructed. After clearing the runway, we asked the tower controller if there was any problem, to which he responded, 'no -- it was my fault.' this situation did not cause a serious conflict, however, had the other aircraft been farther along in the takeoff roll and not been able to abort the takeoff or not stop before the intersection of runway 36L, it could have caused a very serious conflict. I think the tower controller thought he had a little more spacing in the traffic so he cleared the aircraft for takeoff after we had been cleared for landing, then realized it was closer than thought and had the other aircraft cancel the takeoff clearance. We contacted the controllers after arrival and discussed the situation just to verify that everything was ok and that we were not at fault. They verified that we had no fault and they were going to listen to the tapes just to review it to prevent this type of situation from occurring again. I believe to prevent this occurrence the tower controller could have waited to give the other aircraft takeoff clearance until we had landed. The other aircraft may have taken too much time initiating the takeoff roll -- which we do not know -- in which case the tower could have cancelled the takeoff clearance sooner. At any rate -- we are very thankful that there was not a closer conflict between us and the other aircraft.

Original NASA ASRS Text

Title: A LNDG ACR MLG KEEPS A WARY EYE ON LTT IN THE PROCESS OF ABORTING TKOF ON XING RWY.

Narrative: WE WERE MAKING A VISUAL APCH TO RWY 36L AT CVG ARPT AND HAD BEEN CLRED TO LAND ON RWY 36L. ANOTHER ACFT HAD BEEN CLRED FOR TKOF ON RWY 27 (AN LTT). WHEN WE WERE ON SHORT FINAL APCH, THE TWR INSTRUCTED THE LTT TO CANCEL TKOF CLRNC. THE LTT CREW RESPONDED 'ROGER, WE ARE ABORTING.' THIS CAUGHT OUR ATTN, BUT IT WAS JUST PRIOR TO OUR LNDG ON RWY 36L. AFTER LNDG ON RWY 36L WE SAW THE ACR LTT BRAKING TO A STOP ON RWY 27 (WHICH INTERSECTS RWY 36L). WE SAW THAT THE OTHER ACFT WAS COMING TO A STOP SAFELY BEFORE THE INTXN SO WE CONTINUED THE LNDG ROLL THROUGH THE INTXN AND CLRED THE RWY AS INSTRUCTED. AFTER CLRING THE RWY, WE ASKED THE TWR CTLR IF THERE WAS ANY PROBLEM, TO WHICH HE RESPONDED, 'NO -- IT WAS MY FAULT.' THIS SITUATION DID NOT CAUSE A SERIOUS CONFLICT, HOWEVER, HAD THE OTHER ACFT BEEN FARTHER ALONG IN THE TKOF ROLL AND NOT BEEN ABLE TO ABORT THE TKOF OR NOT STOP BEFORE THE INTXN OF RWY 36L, IT COULD HAVE CAUSED A VERY SERIOUS CONFLICT. I THINK THE TWR CTLR THOUGHT HE HAD A LITTLE MORE SPACING IN THE TFC SO HE CLRED THE ACFT FOR TKOF AFTER WE HAD BEEN CLRED FOR LNDG, THEN REALIZED IT WAS CLOSER THAN THOUGHT AND HAD THE OTHER ACFT CANCEL THE TKOF CLRNC. WE CONTACTED THE CTLRS AFTER ARR AND DISCUSSED THE SITUATION JUST TO VERIFY THAT EVERYTHING WAS OK AND THAT WE WERE NOT AT FAULT. THEY VERIFIED THAT WE HAD NO FAULT AND THEY WERE GOING TO LISTEN TO THE TAPES JUST TO REVIEW IT TO PREVENT THIS TYPE OF SITUATION FROM OCCURRING AGAIN. I BELIEVE TO PREVENT THIS OCCURRENCE THE TWR CTLR COULD HAVE WAITED TO GIVE THE OTHER ACFT TKOF CLRNC UNTIL WE HAD LANDED. THE OTHER ACFT MAY HAVE TAKEN TOO MUCH TIME INITIATING THE TKOF ROLL -- WHICH WE DO NOT KNOW -- IN WHICH CASE THE TWR COULD HAVE CANCELLED THE TKOF CLRNC SOONER. AT ANY RATE -- WE ARE VERY THANKFUL THAT THERE WAS NOT A CLOSER CONFLICT BTWN US AND THE OTHER ACFT.

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.

A landing air carrier medium large transport keeps a wary eye on light transport in the process of aborting takeoff on crossing runway.