CRJ200 flight crew describes the events leading up to a taxiway excursion due to failure to read the latest NOTAMs. Breaking action had gone from good to poor and the crew was attempting to taxi on a closed taxiway.

2012-01 · NASA ASRS report 990347

Date: 2012-01 · Aircraft: Regional Jet 200 ER/LR (CRJ200) · Phase: taxi

Anomalies: ground-excursion-taxiway|inflight-event-encounter-loss-of-aircraft-control|inflight-event-encounter-weather-turbulence

Synopsis

CRJ200 flight crew describes the events leading up to a taxiway excursion due to failure to read the latest NOTAMs. Breaking action had gone from good to poor and the crew was attempting to taxi on a closed taxiway.

Narrative

On the ride over from the hotel it was thundering and lightning as a storm passed over. We arrived at the airport and began getting the aircraft ready and at this time and until we left the gate for our taxi it was just a light rain. The preflight was uneventful except for the need to call Dispatch for our weight and balance information because our ACARS has no reception; which I did. The taxiways and runways were reporting braking actions good and MU's of 40 on the departure runway. I did not notice NOTAM 21/1 that said to be careful when taxing at night due to closure of Taxiway C. While I was on the phone with Dispatch we received our close out and I glanced over it while I was still talking to them. I did not notice that the taxiways were now reporting poor braking and I should have looked it over while not on the phone with Dispatch. We completed our checklist and closed the door. On our taxi out the braking seemed to be pretty good on Taxiway E. We were taxing very slow and crossed 07/25 and began to join Taxiway C which was the closed runway. In the turn I could feel that we were beginning to slip a little so I slowed down even more. We made it through the turn and had just began to taxi straight onto C when we started sliding again; but this time it was starting to twist sideways. I then shut both engines down and we continued the turn and ended up spinning around 120 degrees to the right and came to a stop with our nose wheel in the snow off the taxiway. No taxi lights or signs where hit and no passengers were injured. We called Operations and they came out and took the passengers to the terminal and we stayed with the aircraft for another hour until we had made all the necessary phone calls. The event occurred because I; the Captain; did not thoroughly read through the close out paper work because I was on the phone with Dispatch and completely forgot to look it over better once off the phone. If I had I would have noticed that the taxiways and runways had deteriorated. I should have also noticed that Taxiway C was closed even though there were not cones or lights indicating that it was a closed taxiway.

Second reporter narrative

We arrived at the aircraft and I performed the preflight. At this time it was raining lightly. I returned to the aircraft and set up for the flight. ACARS was unavailable so the Captain contacted Dispatch for our takeoff data. When he was on the phone we received the closeout. We input the numbers; ran checklists; and started the engines. Then we began the taxi to Runway XX. After crossing Runway YY there was a slight turn on Taxiway C and we began to slide after coming out of the turn. The Captain made the appropriate actions attempting to stop the slide and regain control of the aircraft; but it wouldn't stop so he shut down the engines. The plane continued to slide and turned nearly 120 degrees as it came to a stop with the nose wheel in the snow. No lights or signs were hit and there were no injuries.The event occurred due to contaminated taxiway surfaces and our failure to thoroughly read the closeout paperwork containing deteriorating surface conditions and the closure of Taxiway C. The paperwork we had received prior had braking conditions reported good.

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.