Date: 201310
Local time of day: 1801-2400
Location: BWI.Airport, MD
Flight conditions: VMC
Light: Night
Aircraft: Beechjet 400
Operator: Air Taxi
Operating under: Part 135
Flight phase: Taxi
ATC / advisory: Ground BWI
Reporter organization: Air Taxi
Reporter function: Pilot Not Flying; First Officer
Human factors: Training / Qualification; Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure; Airport
Primary problem: Ambiguous

Narrative: As we were being vectored onto final we noticed that we were only five miles from the aircraft we were following; so we adjusted speed to maintain that after being cleared for the visual. On short final I realized the aircraft following us was about three miles behind us. After we touched down onto Runway 10 we were told 'no delay keep the speed up down the runway and exit onto Runway 4.' As we noticed we went passed Runway 4 slightly; the Controller told us that was Runway 4. During the Controllers' call he also told the aircraft behind us to go-around. We then made a hard left onto Runway 4 and the Controller told us to taxi northbound on Runway 4 and contact ground.  Nothing more was said about the event from the controllers.  There should've been more spacing between us and the aircraft that was following us. Also; there was no lead off lights onto Runway 4 and it can be difficult to see at night. You can't tell the difference between regular runway edge lights and embedded runway edge lights when you are told to keep the speed up at night.  It would've been a better option to give us instructions to exit onto Taxiway E that would have leadoff lights and centerline leadoff lines.


Second narrative: On approach into BWI in VMC we were given multiple speed assignments as were the aircraft in front of us and behind us. Once on final we had been slowed to 150 KTS and cleared for the visual with the aircraft in front of us as well as the runway in sight. In trail behind a 737 we made sure to maintain adequate spacing as the approaches were being run very closely together. We were landing Runway 10 and had briefed that we would most likely be told to turn off onto Runway 4. After touchdown Tower asked us to keep the speed up and make the turn off onto Runway 4 ASAP. From our approach briefing we knew it would be hard to find the correct turn off as you pass 15R and shortly after the correct runway 4; but there are no lead off lights or markings to give you an indication of when you are at the runway intersection. You are simply in a collection of white lights and have to figure out which ones are imbedded in the pavement of the intersecting runway; and which mark the boundary of the grass. We saw the appropriate runway sign but could not tell when we were supposed to turn; Tower advised us that we were in the intersection so we turned immediately and exited the runway. As this was happening Tower told the 737 behind us to go around. The taxi in continued with no other events.If an airport is going to use a runway as a taxiway especially at night; there should be some markings on the pavement leading you to the appropriate runway or lead off lights. Additionally; there should have been more spacing between aircraft so we wouldn't have to both 'keep the speed up' and make a complicated intersection with no markings.


Synopsis: BE400 flight crew reports being unable to rapidly identify Runway 4 after landing Runway 10 at BWI and the Tower issues go around instructions to the following B737. The flying Captain had slowed on final to maintain 5 miles in trail; reducing separation with the following B737.