Air carrier landing Runway 17 at MSP; instructed to hold short of Runway 22 and later instructed to turn onto Runway 4 for inbound taxi; expressed concern regarding the ATC arrival procedures utilized.

2009-09 · NASA ASRS report 854036

Date: 2009-09 · Aircraft: EMB ERJ 170/175 ER/LR · Phase: taxi

Anomalies: atc-issue-all-types|conflict-ground-conflict|less-severe|deviation-discrepancy-procedural-published-material-policy

Synopsis

Air carrier landing Runway 17 at MSP; instructed to hold short of Runway 22 and later instructed to turn onto Runway 4 for inbound taxi; expressed concern regarding the ATC arrival procedures utilized.

Narrative

We were Landing Runway 17 in MSP. After being cleared to land Tower Controller asked us to let her know upon landing if we could hold short of Runway 22. First Officer landed and began breaking to hold short. I wasn't sure if we would stop and told Tower we may roll through. We did make the hold short and Tower Controller came back saying continue and then another Controller in the background said; 'They made the hold short'. Our Controller then said; 'Hold short Runway 22'. We complied and held on hold short line. While holding on Runway 17 an air carrier flight was cleared to go around behind us. Then the flight that we were holding for landed and turned off Runway 22. Radio congestion followed as they cleared four aircraft across Runway 22 up field. As another aircraft approached Runway 22 they were told to go around as an aircraft was departing on Runway 12R. After the aircraft landing Runway 22 executed the go around; we were cleared by Tower Controller to turn left on to Runway 4. We expedited off Runway 17 onto Runway 4 however another aircraft had to go around behind us. While taxing on Runway 4 no further instructions as to clear the runway were given. As a line of aircraft was approaching to land Runway 22 in front of us I expedited off Runway 4 at taxiway Sierra. When clear I set parking breaks and asked First Officer to let Tower know we were on taxiway Sierra. Tower Controller came on radio and instructed us then to use Sierra to Delta hold short Runway 12R. We complied with no further incidence. A LAHSO operation was not in effect or available for this runway and the Controllers request to let her know if we can hold short after landing did not seem appropriate due to the short distance in the roll out to hold short of Runway 22. Then the turn onto another active runway along with the radio congestion; and high controller work load; (3 runways with intersecting flight paths being used for departures and arrivals); will compromise safety margins. My suggestion would be to review the volume of aircraft being accepted when using this configuration of runways for arrivals and departures. This was a very uncomfortable position to be in; and being turned on to an active runway compromised safety.

Second reporter narrative

We landed and stopped short of Runway 4/22. Our Controller thought we were going to roll through so she told us to continue on 17 across Runway 4/22. We heard another Controller tell our Controller that we were holding short. She then instructed us to hold our position. We once again came to a stop. Meanwhile the aircraft who was landing behind us was issued go-around instructions since we were occupying Runway 17. Two aircraft landed on Runway 22 and exited while we remained stationary. An Airbus was on final for Runway 17 which we were occupying so she issued go-around instructions to him on about a 2 mile final. At about this same time an aircraft was cleared to depart Runway 12R. While they were on the roll; go-around instructions were issued for an aircraft landing on Runway 22. After this we were cleared to taxi onto Runway 4. We turned left and taxied on Runway 4 and took our first right to get off the active runway. At this time we were told to monitor the 12R tower and received normal taxi instructions to the gate. The runway configuration and traffic volume at the time seemed to cause flow issues with ATC.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.