Flight crew clears runway on to another runway rather than a taxiway without gaining tower approval.

Attributes
ACN	299305
Time
Date	199503
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bdr
State Reference	CT
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : corporate
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 91
Navigation In Use	Other Other
Flight Phase	ground other : taxi landing other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 90 flight time total : 5100 flight time type : 1000
ASRS Report	299305
Person 2
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Upon landing on runway 06 at kbdr I turned off on runway 29 (left turn) instead of using a proper taxiway. The problem arose because, this was the second test flight of the day and on the first test flight the local controller gave us the directions to turn onto runway 29 after landing on runway 06. I was not the PF the first flight. Upon landing the second time I assumed to do the same procedure. The controllers had changed shifts, and the local controller did not know what had taken place earlier. The local controller asked that I call the tower which I did and we discussed the problem. I believe it was my error because I assumed a procedure that is not the normal way things are done. My copilot also rated in the aircraft did not bring it to my attention that we should not taxi on the crossing runway. We had a plane load of passenger who were just going for a ride for fun. Some passenger were air sick and I was concerned with them instead of what I was supposed to be paying attention to and that was flying the aircraft. My copilot was also in the same mental state at the time. I think we both lost sight of what was going on and focused our attention in the wrong direction.

Original NASA ASRS Text

Title: FLC CLRS RWY ON TO ANOTHER RWY RATHER THAN A TXWY WITHOUT GAINING TWR APPROVAL.

Narrative: UPON LNDG ON RWY 06 AT KBDR I TURNED OFF ON RWY 29 (L TURN) INSTEAD OF USING A PROPER TXWY. THE PROB AROSE BECAUSE, THIS WAS THE SECOND TEST FLT OF THE DAY AND ON THE FIRST TEST FLT THE LCL CTLR GAVE US THE DIRECTIONS TO TURN ONTO RWY 29 AFTER LNDG ON RWY 06. I WAS NOT THE PF THE FIRST FLT. UPON LNDG THE SECOND TIME I ASSUMED TO DO THE SAME PROC. THE CTLRS HAD CHANGED SHIFTS, AND THE LCL CTLR DID NOT KNOW WHAT HAD TAKEN PLACE EARLIER. THE LCL CTLR ASKED THAT I CALL THE TWR WHICH I DID AND WE DISCUSSED THE PROB. I BELIEVE IT WAS MY ERROR BECAUSE I ASSUMED A PROC THAT IS NOT THE NORMAL WAY THINGS ARE DONE. MY COPLT ALSO RATED IN THE ACFT DID NOT BRING IT TO MY ATTN THAT WE SHOULD NOT TAXI ON THE XING RWY. WE HAD A PLANE LOAD OF PAX WHO WERE JUST GOING FOR A RIDE FOR FUN. SOME PAX WERE AIR SICK AND I WAS CONCERNED WITH THEM INSTEAD OF WHAT I WAS SUPPOSED TO BE PAYING ATTN TO AND THAT WAS FLYING THE ACFT. MY COPLT WAS ALSO IN THE SAME MENTAL STATE AT THE TIME. I THINK WE BOTH LOST SIGHT OF WHAT WAS GOING ON AND FOCUSED OUR ATTN IN THE WRONG DIRECTION.

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.