Crew misinterped taxi clearance and taxied onto an active runway.

Attributes
ACN	491697
Time
Date	200011
Day	Wed
Local Time Of Day	1801 To 2400
Place
State Reference	CT
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : charter
Make Model Name	Learjet 35
Operating Under FAR Part	Part 135
Flight Phase	ground : taxi
Person 1
Affiliation	company : charter
Function	flight crew : captain oversight : pic
Qualification	pilot : instrument pilot : multi engine pilot : atp pilot : cfi
Experience	flight time last 90 days : 120 flight time total : 5800 flight time type : 3500
ASRS Report	491697
Person 2
Affiliation	company : charter
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial pilot : multi engine
Events
Anomaly	incursion : runway non adherence : clearance non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance none taken : anomaly accepted none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While taxiing at bdr, we were given a taxi clearance of 'taxi to runway 24, intersection D.' there are 2 exits off the FBO ramp. One being taxiway F, and the other taxiway D. I saw a note on the commercial airport diagram that noted taxiway D, north of taxiway H, is closed to aircraft other than single engines. I then used taxiway F to taxi off the ramp. Callback conversation with reporter revealed the following information: when ground cleared the crew to 'runway 24, intersection D,' the crew was distraction, assuming an intersection takeoff. The crew exited the north ramp at taxiway F not taxiway K, as originally stated in the narrative, then proceeded via taxiway D to the intersection of taxiway D and runways 29 and 24. Evidently, the aircraft was taxied onto runway 29 but short of runway 24. At this point, ground control advised the crew of the runway incursion. After landing at bgm, the crew contacted bdr tower and took full responsibility for the event.

Original NASA ASRS Text

Title: CREW MISINTERPED TAXI CLRNC AND TAXIED ONTO AN ACTIVE RWY.

Narrative: WHILE TAXIING AT BDR, WE WERE GIVEN A TAXI CLRNC OF 'TAXI TO RWY 24, INTXN D.' THERE ARE 2 EXITS OFF THE FBO RAMP. ONE BEING TXWY F, AND THE OTHER TXWY D. I SAW A NOTE ON THE COMMERCIAL ARPT DIAGRAM THAT NOTED TXWY D, N OF TXWY H, IS CLOSED TO ACFT OTHER THAN SINGLE ENGS. I THEN USED TXWY F TO TAXI OFF THE RAMP. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: WHEN GND CLRED THE CREW TO 'RWY 24, INTXN D,' THE CREW WAS DISTR, ASSUMING AN INTXN TKOF. THE CREW EXITED THE N RAMP AT TXWY F NOT TXWY K, AS ORIGINALLY STATED IN THE NARRATIVE, THEN PROCEEDED VIA TXWY D TO THE INTXN OF TXWY D AND RWYS 29 AND 24. EVIDENTLY, THE ACFT WAS TAXIED ONTO RWY 29 BUT SHORT OF RWY 24. AT THIS POINT, GND CTL ADVISED THE CREW OF THE RWY INCURSION. AFTER LNDG AT BGM, THE CREW CONTACTED BDR TWR AND TOOK FULL RESPONSIBILITY FOR THE EVENT.

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.