Narrative:

Confusing signage on ground in cle between runways 28 and 23L led to attempted takeoff on runway 28 when we were cleared for takeoff on runway 23L. Takeoff was stopped and we taxied back to runway 23L and departed uneventfully. It was my first time operating at cle, also I was in training for captain upgrade. The check airman doing my training was also new to cle. We should have done the basic thing and checked the HSI and matched it to the runway heading. I believe contributing to this incident was a runway sign that I believed indicated runway 23L. However it was located in such a way, that I did not see the runway 28 sign. Another factor contributing was a last min runway change from runway 23R to runway 23L. This may have contributed to the confusion. Callback conversation with reporter revealed the following information: reporter stated during callback that he had not been advised of any enforcement action pending toward the incident by FAA. Analyst briefed reporter on the cle incidents and what action the FAA had taken to eliminate the problem. Reporter stated he would contact ASRS if he hears of any enforcement action. Supplemental information from acn 341468: confusing runway marker signage led to initiating takeoff on runway 28 instead of runway 23L. Initial clearance was for runway 23R. Last min runway change and very confusing signs at the intersection of runway 23L and runway 23R and runway 28 and taxiway J.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLC AT CLE ATTEMPTED DEP ON RWY 28 INSTEAD OF RWY 23L. FLC STATES THAT THE SIGNAGE AT THE INTXN OF RWY 23L-R AND RWY 28 AT TXWY J IS CONFUSING. NEITHER CREW MEMBER HAD OPERATED AT CLE PRIOR TO THE INCIDENT.

Narrative: CONFUSING SIGNAGE ON GND IN CLE BTWN RWYS 28 AND 23L LED TO ATTEMPTED TKOF ON RWY 28 WHEN WE WERE CLRED FOR TKOF ON RWY 23L. TKOF WAS STOPPED AND WE TAXIED BACK TO RWY 23L AND DEPARTED UNEVENTFULLY. IT WAS MY FIRST TIME OPERATING AT CLE, ALSO I WAS IN TRAINING FOR CAPT UPGRADE. THE CHK AIRMAN DOING MY TRAINING WAS ALSO NEW TO CLE. WE SHOULD HAVE DONE THE BASIC THING AND CHKED THE HSI AND MATCHED IT TO THE RWY HDG. I BELIEVE CONTRIBUTING TO THIS INCIDENT WAS A RWY SIGN THAT I BELIEVED INDICATED RWY 23L. HOWEVER IT WAS LOCATED IN SUCH A WAY, THAT I DID NOT SEE THE RWY 28 SIGN. ANOTHER FACTOR CONTRIBUTING WAS A LAST MIN RWY CHANGE FROM RWY 23R TO RWY 23L. THIS MAY HAVE CONTRIBUTED TO THE CONFUSION. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED DURING CALLBACK THAT HE HAD NOT BEEN ADVISED OF ANY ENFORCEMENT ACTION PENDING TOWARD THE INCIDENT BY FAA. ANALYST BRIEFED RPTR ON THE CLE INCIDENTS AND WHAT ACTION THE FAA HAD TAKEN TO ELIMINATE THE PROB. RPTR STATED HE WOULD CONTACT ASRS IF HE HEARS OF ANY ENFORCEMENT ACTION. SUPPLEMENTAL INFO FROM ACN 341468: CONFUSING RWY MARKER SIGNAGE LED TO INITIATING TKOF ON RWY 28 INSTEAD OF RWY 23L. INITIAL CLRNC WAS FOR RWY 23R. LAST MIN RWY CHANGE AND VERY CONFUSING SIGNS AT THE INTXN OF RWY 23L AND RWY 23R AND RWY 28 AND TXWY J.

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.