B737 flight crew has runway incursion at oma.

Attributes
ACN	583046
Time
Date	200306
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : oma.airport
State Reference	NE
Altitude	agl single value : 0
Environment
Flight Conditions	IMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 240 flight time total : 6000 flight time type : 2300
ASRS Report	583046
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	incursion : runway non adherence : clearance non adherence : far
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I landed runway 14R at oma. Wet runway. I initiated braking at 80 KIAS. After braking to less than approximately 30 KIAS, the captain came on the brakes and we initiated smooth xfer of control of the aircraft. Passing taxiway C, tower said 'exit runway at taxiway C.' at taxi speed, we were already passing taxiway C and we exited onto runway 18 at the intersection of runways 14R and 18. While turning onto runway 18, I immediately came on the radio to see if we could taxi onto runway 18. The tower replied to the effect, 'taxiing onto an active runway required ATC approval.' I immediately apologized and asked if we caused a problem and if there was any problem. Tower responded, 'no problem.' in hindsight, we briefed the landing runway for the quickest and most efficient landing and taxi. We discussed taxiway C turnoff but not runway 18. In hindsight, looking at the diagram of the airfield on the airport page, taxiway C appears to be at the intersection of runways 14R and 18. Actually, the intersection is 100 ft past taxiway C and I think there was an instinctive initiating of the turnoff at the intersection assuming that taxiway C was there. After initiating the turnoff, we were committed. This was not a hurried action to land and brake quick for the turnoff. Braking decreation was normal and deliberate with consideration for passenger comfort. We were surprised initially that taxiway C was not at the intersection and coming to a full stop with a radio call to tower would have alleviated the conflict.

Original NASA ASRS Text

Title: B737 FLT CREW HAS RWY INCURSION AT OMA.

Narrative: I LANDED RWY 14R AT OMA. WET RWY. I INITIATED BRAKING AT 80 KIAS. AFTER BRAKING TO LESS THAN APPROX 30 KIAS, THE CAPT CAME ON THE BRAKES AND WE INITIATED SMOOTH XFER OF CTL OF THE ACFT. PASSING TXWY C, TWR SAID 'EXIT RWY AT TXWY C.' AT TAXI SPD, WE WERE ALREADY PASSING TXWY C AND WE EXITED ONTO RWY 18 AT THE INTXN OF RWYS 14R AND 18. WHILE TURNING ONTO RWY 18, I IMMEDIATELY CAME ON THE RADIO TO SEE IF WE COULD TAXI ONTO RWY 18. THE TWR REPLIED TO THE EFFECT, 'TAXIING ONTO AN ACTIVE RWY REQUIRED ATC APPROVAL.' I IMMEDIATELY APOLOGIZED AND ASKED IF WE CAUSED A PROB AND IF THERE WAS ANY PROB. TWR RESPONDED, 'NO PROB.' IN HINDSIGHT, WE BRIEFED THE LNDG RWY FOR THE QUICKEST AND MOST EFFICIENT LNDG AND TAXI. WE DISCUSSED TXWY C TURNOFF BUT NOT RWY 18. IN HINDSIGHT, LOOKING AT THE DIAGRAM OF THE AIRFIELD ON THE ARPT PAGE, TXWY C APPEARS TO BE AT THE INTXN OF RWYS 14R AND 18. ACTUALLY, THE INTXN IS 100 FT PAST TXWY C AND I THINK THERE WAS AN INSTINCTIVE INITIATING OF THE TURNOFF AT THE INTXN ASSUMING THAT TXWY C WAS THERE. AFTER INITIATING THE TURNOFF, WE WERE COMMITTED. THIS WAS NOT A HURRIED ACTION TO LAND AND BRAKE QUICK FOR THE TURNOFF. BRAKING DECREATION WAS NORMAL AND DELIBERATE WITH CONSIDERATION FOR PAX COMFORT. WE WERE SURPRISED INITIALLY THAT TXWY C WAS NOT AT THE INTXN AND COMING TO A FULL STOP WITH A RADIO CALL TO TWR WOULD HAVE ALLEVIATED THE CONFLICT.

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.