Unauthorized runway entry by air carrier.

Attributes
ACN	198660
Time
Date	199201
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : cvg
State Reference	OH
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	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other
Flight Phase	ground other : taxi landing other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : flight engineer pilot : instrument
Experience	flight time last 90 days : 150 flight time total : 4000 flight time type : 2000
ASRS Report	198660
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	incursion : runway non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation other

Narrative:

Tower told us to exit runway 18R as soon as possible so he could launch one prior to the next arrival. The first available turn off once we reached taxi speed was runway 27/9. We turned there and tower did not appreciate it. We were committed however, once we started the turn as tower cleared the takeoff position aircraft to go and had we turned back on the runway 18R to exit at a taxiway, a real conflict would have occurred. Runway 27/9 was clear of aircraft. However we did not have specific tower permission to use the 27/9 runway and that made them mad. Callback conversation with reporter revealed the following information. PIC did call the tower supervisor by phone to review incident. There has been no FAA follow up. After touchdown the tower local controller said 'air carrier X turn off runway as soon as possible.' reporter and PIC could hear tower controller put aircraft in takeoff position behind them on 18R and also knew that there was another aircraft on final somewhere. There were no aircraft using runway 9/27 at that time. When air carrier X made left turn onto runway 9/27 the tower cleared aircraft Y for takeoff on 18R immediately. PIC of air carrier X was low time in type and first trip as captain. They were too fast for taxiway D4 exit so probably should have continued to taxiway 'M'.

Original NASA ASRS Text

Title: UNAUTH RWY ENTRY BY ACR.

Narrative: TWR TOLD US TO EXIT RWY 18R ASAP SO HE COULD LAUNCH ONE PRIOR TO THE NEXT ARR. THE FIRST AVAILABLE TURN OFF ONCE WE REACHED TAXI SPD WAS RWY 27/9. WE TURNED THERE AND TWR DID NOT APPRECIATE IT. WE WERE COMMITTED HOWEVER, ONCE WE STARTED THE TURN AS TWR CLRED THE TKOF POS ACFT TO GO AND HAD WE TURNED BACK ON THE RWY 18R TO EXIT AT A TAXIWAY, A REAL CONFLICT WOULD HAVE OCCURRED. RWY 27/9 WAS CLR OF ACFT. HOWEVER WE DID NOT HAVE SPECIFIC TWR PERMISSION TO USE THE 27/9 RWY AND THAT MADE THEM MAD. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO. PIC DID CALL THE TWR SUPVR BY PHONE TO REVIEW INCIDENT. THERE HAS BEEN NO FAA FOLLOW UP. AFTER TOUCHDOWN THE TWR LCL CTLR SAID 'ACR X TURN OFF RWY AS SOON AS POSSIBLE.' RPTR AND PIC COULD HEAR TWR CTLR PUT ACFT IN TKOF POS BEHIND THEM ON 18R AND ALSO KNEW THAT THERE WAS ANOTHER ACFT ON FINAL SOMEWHERE. THERE WERE NO ACFT USING RWY 9/27 AT THAT TIME. WHEN ACR X MADE L TURN ONTO RWY 9/27 THE TWR CLRED ACFT Y FOR TKOF ON 18R IMMEDIATELY. PIC OF ACR X WAS LOW TIME IN TYPE AND FIRST TRIP AS CAPT. THEY WERE TOO FAST FOR TAXIWAY D4 EXIT SO PROBABLY SHOULD HAVE CONTINUED TO TAXIWAY 'M'.

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.