Narrative:

On or about XA46 on jun/sun/93, I started taxiing from gate to runway 29 at bridgeport, ct. The tower just made an announcement that it had just closed for the day. Just as I pulled out onto taxiway a, I announced I was doing so on frequency 120.9 (CTAF). As I pulled out onto the taxiway, I heard an announcement by an air carrier light transport that he was on a 10 mi final for runway 6. I pulled up to runway 29 to hold short to let an small aircraft land on runway 29. Just as the small aircraft landed, I pulled out onto runway 29 to back-taxi. As I did, I heard the air carrier light transport announce he was on a 3 mi final for runway 6. On this announcement, and the fact that my copilot and I didn't see him, I taxied across runway 6. When I got to the other side of runway 6, I heard the air carrier light transport say someone cut in front of him. At that time my copilot said he saw an aircraft about 50-100 ft above and on final to runway 6. That was the first anyone in my aircraft saw of him. I did not respond to his call of someone cutting him off, because at the time I wasn't sure I was the one who cut him off. After thinking on this, I feel he was talking about me. With the sequence of radio calls and the time frame of such, I feel there should have been enough room for me to cross runway 6, and the air carrier light transport to land on runway 6. I had just landed at bridgeport myself about 10 or 13 mins before, there were several aircraft in the pattern, all were using runway 29. The tower was open at the time. I had my radio on all the time I was at the airport, and the air carrier light transport was the first and only aircraft to use runway 6 while I was at the bridgeport airport that evening. At night one has to be alert for traffic, especially when one changes the active runway, whether it be himself or someone else. Supplemental information from acn 243645: air carrier light transport en route from philadelphia to bridgeport, ct (bdr). Since the tower was closed, we announced to all traffic at bdr a 15 mi final for runway 6 followed by several other position reports on frequency 120.9. During our approach to runway 6, another aircraft was approaching runway 29 for landing. After landing on runway 29, the aircraft called clear of all runways at bdr. Prior to our landing on runway 6, an unannounced aircraft taxied across runway 6. Although inconsiderate to cross runway 6 at the last moment, it did not cause a safety hazard to air carrier flight. After the aircraft cleared runway 6, air carrier flight landed. We announced clear of runway 6 and asked for aircraft number of aircraft which crossed the runway. Several attempts were made to determine aircraft number but were unsuccessful.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR ATX CROSSED THE RWY THAT AN ACR LTT WAS APCHING TO LAND.

Narrative: ON OR ABOUT XA46 ON JUN/SUN/93, I STARTED TAXIING FROM GATE TO RWY 29 AT BRIDGEPORT, CT. THE TWR JUST MADE AN ANNOUNCEMENT THAT IT HAD JUST CLOSED FOR THE DAY. JUST AS I PULLED OUT ONTO TXWY A, I ANNOUNCED I WAS DOING SO ON FREQ 120.9 (CTAF). AS I PULLED OUT ONTO THE TXWY, I HEARD AN ANNOUNCEMENT BY AN ACR LTT THAT HE WAS ON A 10 MI FINAL FOR RWY 6. I PULLED UP TO RWY 29 TO HOLD SHORT TO LET AN SMA LAND ON RWY 29. JUST AS THE SMA LANDED, I PULLED OUT ONTO RWY 29 TO BACK-TAXI. AS I DID, I HEARD THE ACR LTT ANNOUNCE HE WAS ON A 3 MI FINAL FOR RWY 6. ON THIS ANNOUNCEMENT, AND THE FACT THAT MY COPLT AND I DIDN'T SEE HIM, I TAXIED ACROSS RWY 6. WHEN I GOT TO THE OTHER SIDE OF RWY 6, I HEARD THE ACR LTT SAY SOMEONE CUT IN FRONT OF HIM. AT THAT TIME MY COPLT SAID HE SAW AN ACFT ABOUT 50-100 FT ABOVE AND ON FINAL TO RWY 6. THAT WAS THE FIRST ANYONE IN MY ACFT SAW OF HIM. I DID NOT RESPOND TO HIS CALL OF SOMEONE CUTTING HIM OFF, BECAUSE AT THE TIME I WASN'T SURE I WAS THE ONE WHO CUT HIM OFF. AFTER THINKING ON THIS, I FEEL HE WAS TALKING ABOUT ME. WITH THE SEQUENCE OF RADIO CALLS AND THE TIME FRAME OF SUCH, I FEEL THERE SHOULD HAVE BEEN ENOUGH ROOM FOR ME TO CROSS RWY 6, AND THE ACR LTT TO LAND ON RWY 6. I HAD JUST LANDED AT BRIDGEPORT MYSELF ABOUT 10 OR 13 MINS BEFORE, THERE WERE SEVERAL ACFT IN THE PATTERN, ALL WERE USING RWY 29. THE TWR WAS OPEN AT THE TIME. I HAD MY RADIO ON ALL THE TIME I WAS AT THE ARPT, AND THE ACR LTT WAS THE FIRST AND ONLY ACFT TO USE RWY 6 WHILE I WAS AT THE BRIDGEPORT ARPT THAT EVENING. AT NIGHT ONE HAS TO BE ALERT FOR TFC, ESPECIALLY WHEN ONE CHANGES THE ACTIVE RWY, WHETHER IT BE HIMSELF OR SOMEONE ELSE. SUPPLEMENTAL INFO FROM ACN 243645: ACR LTT ENRTE FROM PHILADELPHIA TO BRIDGEPORT, CT (BDR). SINCE THE TWR WAS CLOSED, WE ANNOUNCED TO ALL TFC AT BDR A 15 MI FINAL FOR RWY 6 FOLLOWED BY SEVERAL OTHER POS RPTS ON FREQ 120.9. DURING OUR APCH TO RWY 6, ANOTHER ACFT WAS APCHING RWY 29 FOR LNDG. AFTER LNDG ON RWY 29, THE ACFT CALLED CLR OF ALL RWYS AT BDR. PRIOR TO OUR LNDG ON RWY 6, AN UNANNOUNCED ACFT TAXIED ACROSS RWY 6. ALTHOUGH INCONSIDERATE TO CROSS RWY 6 AT THE LAST MOMENT, IT DID NOT CAUSE A SAFETY HAZARD TO ACR FLT. AFTER THE ACFT CLRED RWY 6, ACR FLT LANDED. WE ANNOUNCED CLR OF RWY 6 AND ASKED FOR ACFT NUMBER OF ACFT WHICH CROSSED THE RWY. SEVERAL ATTEMPTS WERE MADE TO DETERMINE ACFT NUMBER BUT WERE UNSUCCESSFUL.

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.