Takeoff wrong runway.

Attributes
ACN	260019
Time
Date	199312
Day	Thu
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : cle
State Reference	OH
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	IMC
Light	Night
Aircraft 1
Operator	other
Make Model Name	Medium Transport
Flight Phase	climbout : takeoff
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : instrument pilot : cfi pilot : commercial
Experience	flight time last 90 days : 100 flight time total : 1800 flight time type : 850
ASRS Report	260019
Person 2
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 18000 flight time type : 1000
ASRS Report	259951
Events
Anomaly	aircraft equipment problem : less severe incursion : runway non adherence : clearance other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were at cle and told to taxi into position and hold on runway 23L. As soon as we were into position, we were cleared for takeoff. After it was too late to make a safe abort, the captain and I realized that we might have been taking off on the wrong runway. It is the opinion of the flight crew that we might have taken off on runway 28, however, neither the tower nor the departure controllers complained. I believe that the runway layout, poor visibility, the compasses not slaving properly, and the fact that the runway lights on runway 28 were on high intensity, were contributing factors. I believe that future recurrences of this situation could be prevented by turning off or turning down the intensity of the runway lights on runway 28 when it's not in use, and controllers advising flcs of the possibility of lining up with the wrong runway during periods of reduced visibility. Supplemental information from acn 259951: crew had flown in excess of 9 hours (fatigue). Due to slow traffic and type of aircraft, no conflicts arose. I must be more careful in the future!

Original NASA ASRS Text

Title: TKOF WRONG RWY.

Narrative: WE WERE AT CLE AND TOLD TO TAXI INTO POS AND HOLD ON RWY 23L. AS SOON AS WE WERE INTO POS, WE WERE CLRED FOR TKOF. AFTER IT WAS TOO LATE TO MAKE A SAFE ABORT, THE CAPT AND I REALIZED THAT WE MIGHT HAVE BEEN TAKING OFF ON THE WRONG RWY. IT IS THE OPINION OF THE FLC THAT WE MIGHT HAVE TAKEN OFF ON RWY 28, HOWEVER, NEITHER THE TWR NOR THE DEP CTLRS COMPLAINED. I BELIEVE THAT THE RWY LAYOUT, POOR VISIBILITY, THE COMPASSES NOT SLAVING PROPERLY, AND THE FACT THAT THE RWY LIGHTS ON RWY 28 WERE ON HIGH INTENSITY, WERE CONTRIBUTING FACTORS. I BELIEVE THAT FUTURE RECURRENCES OF THIS SIT COULD BE PREVENTED BY TURNING OFF OR TURNING DOWN THE INTENSITY OF THE RWY LIGHTS ON RWY 28 WHEN IT'S NOT IN USE, AND CTLRS ADVISING FLCS OF THE POSSIBILITY OF LINING UP WITH THE WRONG RWY DURING PERIODS OF REDUCED VISIBILITY. SUPPLEMENTAL INFO FROM ACN 259951: CREW HAD FLOWN IN EXCESS OF 9 HRS (FATIGUE). DUE TO SLOW TFC AND TYPE OF ACFT, NO CONFLICTS AROSE. I MUST BE MORE CAREFUL IN THE FUTURE!

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.