B737-200 captain did not set qne at the transition level in ZID class a airspace.

Attributes
ACN	510689
Time
Date	200104
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : cvg.airport
State Reference	KY
Altitude	msl single value : 23000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zid.artcc tower : bur.tower
Operator	common carrier : air carrier
Make Model Name	B737-200
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zid.artcc
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : multi engine pilot : instrument pilot : flight engineer pilot : cfi pilot : commercial
Experience	flight time last 90 days : 130 flight time total : 10600 flight time type : 1480
ASRS Report	510689
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : company policies non adherence : published procedure other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : detected after the fact other
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We were flying a revenue passenger flight, air carrier X, flight abcd from cvg to phl. The first officer was flying and had been cleared to climb from 15000 ft to FL230. After the climb was initiated, but before reaching FL180 (positive control area), I got distraction with a frequency change, a warning from the controller that air carrier X efgh was also operating on frequency, a turn direct to johnstown VOR, and a call from the back. After responding to the calls, I looked down at my chart for the jst frequency, dialed it in, switched frequencys and checked in with the new controller. While doing so, I looked at my altimeter and said 'good morning, flight abcd out of FL230 for...' (and looked to see the altitude window on the MCP was FL230!) and realized my altimeter was at approximately FL232+ with an altimeter setting of 30.47. The first officer was level at FL230 and HSI altimeter was set on 29.92. So, while we were level at our assigned altitude of FL230, my altimeter may have indicated higher. I didn't hear his '29.92' call with all the noise and distrs, and got overloaded worrying about flight efgh on the frequency. No comment from the controller. Rest of flight uneventful.

Original NASA ASRS Text

Title: B737-200 CAPT DID NOT SET QNE AT THE TRANSITION LEVEL IN ZID CLASS A AIRSPACE.

Narrative: WE WERE FLYING A REVENUE PAX FLT, ACR X, FLT ABCD FROM CVG TO PHL. THE FO WAS FLYING AND HAD BEEN CLRED TO CLB FROM 15000 FT TO FL230. AFTER THE CLB WAS INITIATED, BUT BEFORE REACHING FL180 (PCA), I GOT DISTR WITH A FREQ CHANGE, A WARNING FROM THE CTLR THAT ACR X EFGH WAS ALSO OPERATING ON FREQ, A TURN DIRECT TO JOHNSTOWN VOR, AND A CALL FROM THE BACK. AFTER RESPONDING TO THE CALLS, I LOOKED DOWN AT MY CHART FOR THE JST FREQ, DIALED IT IN, SWITCHED FREQS AND CHKED IN WITH THE NEW CTLR. WHILE DOING SO, I LOOKED AT MY ALTIMETER AND SAID 'GOOD MORNING, FLT ABCD OUT OF FL230 FOR...' (AND LOOKED TO SEE THE ALT WINDOW ON THE MCP WAS FL230!) AND REALIZED MY ALTIMETER WAS AT APPROX FL232+ WITH AN ALTIMETER SETTING OF 30.47. THE FO WAS LEVEL AT FL230 AND HSI ALTIMETER WAS SET ON 29.92. SO, WHILE WE WERE LEVEL AT OUR ASSIGNED ALT OF FL230, MY ALTIMETER MAY HAVE INDICATED HIGHER. I DIDN'T HEAR HIS '29.92' CALL WITH ALL THE NOISE AND DISTRS, AND GOT OVERLOADED WORRYING ABOUT FLT EFGH ON THE FREQ. NO COMMENT FROM THE CTLR. REST OF FLT UNEVENTFUL.

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.