Runway incursion by CL65 at cvg caused tower controller to cancel another CL65's takeoff and or abor...

Attributes
ACN	559646
Time
Date	200209
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : cvg.airport
State Reference	OH
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Regional Jet CL65, Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : cvg.tower
Operator	common carrier : air carrier
Make Model Name	Regional Jet CL65, Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground : takeoff roll
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 175 flight time total : 2050 flight time type : 450
ASRS Report	559646
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	incursion : runway other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew faa : investigated other
Miss Distance	horizontal : 5000 vertical : 0
Supplementary
Problem Areas	Airport Flight Crew Human Performance ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

We were cleared to land on runway 18R at cvg. During the rollout at approximately 80-90 KTS, the controller stated to take the second exit. I interpreted this to mean exit as soon as we could and got on the brakes for a maximum effort. After exiting the runway, we were instructed to taxi north on taxiway D and hold short of runway 27 and I read back these instructions. I also discussed the hold short instructions with the captain. We complied with the hold short instructions. As I understand it, a crj either had to abort a takeoff run or was given instructions to cancel a takeoff clearance from runway 27 as a result of conflict with us. I can state that at no time did we agree to a lahso (which is against company policy and also isn't done at cvg) or agree to take a specific exit from runway 18R. Also, when we were instructed to hold short of runway 27, I read this back to the controller and we did hold short of runway 27. As a result of the above described conflict, the FAA has initiated an incursion investigation.

Original NASA ASRS Text

Title: RWY INCURSION BY CL65 AT CVG CAUSED TWR CTLR TO CANCEL ANOTHER CL65'S TKOF AND OR ABORTED TKOF.

Narrative: WE WERE CLRED TO LAND ON RWY 18R AT CVG. DURING THE ROLLOUT AT APPROX 80-90 KTS, THE CTLR STATED TO TAKE THE SECOND EXIT. I INTERPED THIS TO MEAN EXIT AS SOON AS WE COULD AND GOT ON THE BRAKES FOR A MAX EFFORT. AFTER EXITING THE RWY, WE WERE INSTRUCTED TO TAXI N ON TXWY D AND HOLD SHORT OF RWY 27 AND I READ BACK THESE INSTRUCTIONS. I ALSO DISCUSSED THE HOLD SHORT INSTRUCTIONS WITH THE CAPT. WE COMPLIED WITH THE HOLD SHORT INSTRUCTIONS. AS I UNDERSTAND IT, A CRJ EITHER HAD TO ABORT A TKOF RUN OR WAS GIVEN INSTRUCTIONS TO CANCEL A TKOF CLRNC FROM RWY 27 AS A RESULT OF CONFLICT WITH US. I CAN STATE THAT AT NO TIME DID WE AGREE TO A LAHSO (WHICH IS AGAINST COMPANY POLICY AND ALSO ISN'T DONE AT CVG) OR AGREE TO TAKE A SPECIFIC EXIT FROM RWY 18R. ALSO, WHEN WE WERE INSTRUCTED TO HOLD SHORT OF RWY 27, I READ THIS BACK TO THE CTLR AND WE DID HOLD SHORT OF RWY 27. AS A RESULT OF THE ABOVE DESCRIBED CONFLICT, THE FAA HAS INITIATED AN INCURSION INVESTIGATION.

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.

Runway incursion by CL65 at cvg caused tower controller to cancel another CL65's takeoff and or aborted takeoff.