2010-10 · NASA ASRS report 914715
DCA Controller described a runway incursion event resulting in a go around when an Air Carrier clearing Runway 1 failed to hold short of Runway 33; lack of maneuvering space was cited by one reporter as contributory.
I was working Local with the airport in a North configuration. I had an Assistant Local Controller (ALC). A B737 landed Runway 1 and was told to turn left on Taxiway S; left on J and hold short Runway 33. The B737 read back 'turn; turn and stay' and I cannot remember if the B737 came back with 'hold short Runway 33'. My Assistant Local Controller (ALC) contends the pilot did. The B737's nose gear crossed and stopped just after the hold short line for Runway 33 on Taxiway J and ALC alerted me to the fact. I had a CRJ200 on short final for Runway 33 and though there was no way the 2 aircraft would have touched or been in an unsafe distance with each other; I was afraid the Ground RADAR would alarm that the runway was occupied forcing me to send the CRJ200 around when that aircraft was at the critical point of touch-down or just rolling out. I sent the CRJ200 around; no alarm went off and gave the B737 instructions to cross Runway 33 on Taxiway J. Because all go-arounds are investigated; I worried that because I could not remember if the B737 actually said 'hold short' I decided to file a report. I remember I thought it was funny how the B737 initially read back my turn and hold short instructions 'turn; turn and stay' and I should have gone back to hear pilot say 'hold short'. This would have reiterated to the pilots to hold short and possibly have made them more aware of the hold short line. If indeed the B737 did not read back 'hold short'; since I can't remember; then it's also a matter of not letting oneself get complacent on position. Slow traffic and low complexity can allow the mind to wander and/or not pay as close attention to the operation as is necessary.
During roll out after landing Runway 01 DCA with First Officer in control of aircraft for landing; the aircraft was passing through runway intersections and approaching taxi speed. Tower issued clearance to turn left (Taxiway S) followed with second left (Taxiway J) and hold short of Runway 33 on taxiway and remain with Tower. This clearance was given coincidental while exchange of aircraft control was occurring to taxi clear of Runway 01 with other aircraft on final to land at DCA. With the objective in mind of completely clearing Runway 01; I was unable to maneuver aircraft and completely clear the runways and hold short of Runway 33 at Taxiway J in the space limitations afforded to keep clear of all runway hold bars. Inadvertently by about 3 FT; I crossed the Runway 33 hold bar while observing approaching landing traffic for Runway 33. This particular area of the airport layout is probably not adequate for transport size aircraft (737) and is not labeled as one of the airport /hot spots/ on airport diagram/s. The crew of this flight is highly experienced in all phases of DCA operations since we have both flown in and out as crew members for many years and have never encountered this situation to hold short of Runway 33 from this position previously. As a consequence; we both agree that is not advisable to accept a clearance on the runway while turning over control of the aircraft and trying to maneuver to a safe zone; and will make it a practice to avoid this type of situation again particularly at this point on the airport. Not realizing it till after the fact; that I couldn't place the aircraft clear of all runways; I called to let the DCA Tower Manager know that I was sorry for the conflict I created. He advised me that after review it was considered a 'non event'. Tempo of operations is always fraught with hazards of this nature; and it is always my practice to maintain the highest level of safety procedure to avoid this type of conflict.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.